From 96f3fbd3fdd95e36e6069ac31e733fc1d2ce982d Mon Sep 17 00:00:00 2001 From: Dayle Parker Date: Mon, 20 Aug 2012 16:28:50 +1000 Subject: Changed Sec 1.2 to Virt Resources; various edits throughout --- en-US/Advantages.xml | 19 +- en-US/Author_Group.xml | 4 +- en-US/Introduction.xml | 48 +++--- en-US/Products.xml | 63 ++++--- en-US/Revision_History.xml | 422 +-------------------------------------------- en-US/What_Is_It.xml | 12 +- 6 files changed, 80 insertions(+), 488 deletions(-) diff --git a/en-US/Advantages.xml b/en-US/Advantages.xml index ea5df7b..54d6bed 100644 --- a/en-US/Advantages.xml +++ b/en-US/Advantages.xml @@ -12,7 +12,7 @@ Virtualization costs - A common misconception is that virtualization is too expensive to justify the change. Virtualization can be expensive to introduce but often it saves money in the long term. It is important to perform a Return on Investment (ROI) analysis to determine the best use of virtualization in your environment. Consider the following benefits: + A common misconception is that virtualization is too expensive to justify the change. Virtualization can be expensive to introduce but often it saves money in the long term. It is important to perform a Return on Investment (ROI) analysis to determine the best use of virtualization in your environment. Consider the following benefits: @@ -51,16 +51,7 @@ --> - - Less space @@ -106,7 +97,7 @@ - A virtual machine uses SELinux to improve security in virtualization. This section includes an overview of the security options available. + A virtual machine uses SELinux and sVirt to improve security in virtualization. This section includes an overview of the security options available.
@@ -121,11 +112,11 @@ For more information on SELinux, refer to the SELinux documentation at . For more information on security within virtualization, refer to the Fedora Virtualization Security Guide. --> - + For more information on sVirt, refer to the Fedora Virtualization Administration Guide.
diff --git a/en-US/Author_Group.xml b/en-US/Author_Group.xml index 00a1e36..5ed9546 100644 --- a/en-US/Author_Group.xml +++ b/en-US/Author_Group.xml @@ -6,8 +6,8 @@ - Red Hat - Engineering Content Services + Fedora + Documentation Project diff --git a/en-US/Introduction.xml b/en-US/Introduction.xml index 9c1e030..7b64f7e 100644 --- a/en-US/Introduction.xml +++ b/en-US/Introduction.xml @@ -60,27 +60,35 @@ In addition to the documentation for Red Hat Enterprise Virtualization products and this guide, the following titles cover virtualization with Fedora: --> - Virtualization Resources + Virtualization resources - In addition to this guide, the following titles cover virtualization with Fedora: + Fedora contains packages and tools to support a variety of virtualized environments. Fedora virtualization provides the upstream development for virtualization in Red Hat Enterprise Linux. Refer to for more information about the virtualization products available in Fedora. + + + In addition to this guide, the following books cover virtualization with Fedora: - - - - Virtualization Deployment Guide: This guide provides information on system requirements and restrictions, package details, host configuration and detailed instructions for installing different types of guests. - - - - - Virtualization Administration Guide: This guide provides information on best server practices, security, KVM, remote management of guests, KSM, administration tasks, storage, volumes, virt-manager, guest disk access with offline tools, virtual networking, and troubleshooting. - - - - - Virtualization Security Guide: This guide provides information on virtualization security technologies including sVirt, configuration and best practices for host and guest security, and network security. - - - - + + + + Virtualization Deployment Guide: This guide provides information on system requirements and restrictions, package details, host configuration and detailed instructions for installing different types of guests. + + + + + Virtualization Administration Guide: This guide provides information on servers, security, KVM, remote management of guests, KSM, administration tasks, storage, volumes, virt-manager, guest disk access with offline tools, virtual networking, and troubleshooting. + + + + + Virtualization Security Guide: This guide provides information on virtualization security technologies including sVirt, configuration and recommendations for host and guest security, and network security. + + + + + Red Hat Enterprise Virtualization (RHEV) is another virtualization option for servers and desktops. Red Hat Enterprise Virtualization provides an end-to-end datacenter virtualization solution developed from the upstream oVirt project. Visit for more information about oVirt. + + + Documentation for Red Hat Enterprise Virtualization and virtualization with Red Hat Enterprise Linux can be found at . + diff --git a/en-US/Products.xml b/en-US/Products.xml index bdbbdc3..9aeaeaa 100644 --- a/en-US/Products.xml +++ b/en-US/Products.xml @@ -58,7 +58,7 @@ To verify whether your processor supports the virtualization extensions and for information on enabling the virtualization extensions if they are disabled, refer to the Fedora Virtualization Administration Guide. - . + Fedora supports libvirt and included libvirt-based tools as its default method for virtualization management. The libvirt package is available as free software under the GNU Lesser General Public License. The libvirt project aims to provide a long term stable C API to virtualization management tools, running on top of varying hypervisor technologies. @@ -133,7 +133,7 @@ - For more information on virt-manager, refer to the Fedora Virtualization Administration Guide. + For more information on virsh and virt-manager, refer to the Fedora Virtualization Administration Guide. @@ -145,7 +145,7 @@ - Virtualized and emulated software devices + Virtualized and emulated devices @@ -230,13 +230,13 @@ - - - Red Hat Enterprise Linux 6.1 and above provides an emulated (Intel) HDA sound device, intel-hda. This device is supported on the following guest operating systems: + + Fedora 18 provides an emulated (Intel) HDA sound device, intel-hda. - + The following two emulated sound devices are also available, but are not recommended due to compatibility issues with certain guest operating systems: @@ -275,12 +275,13 @@ - --> - - Red Hat Enterprise Linux 6.0 and above provides two emulated watchdog devices. A watchdog can be used to automatically reboot a virtual machine when it becomes overloaded or unresponsive. + Fedora 18 provides two emulated watchdog devices. A watchdog can be used to automatically reboot a virtual machine when it becomes overloaded or unresponsive. The watchdog package must be installed on the guest. @@ -291,20 +292,20 @@ - i6300esb, an emulated Intel 6300 ESB PCI watchdog device. It is supported in guest operating system Red Hat Enterprise Linux versions 6.0 and above, and is the recommended device to use. + i6300esb, an emulated Intel 6300 ESB PCI watchdog device. - ib700, an emulated iBase 700 ISA watchdog device. The ib700 watchdog device is only supported in guests using Red Hat Enterprise Linux 6.2 and above. + ib700, an emulated iBase 700 ISA watchdog device. - + - --> + Emulated network devices @@ -368,7 +369,7 @@ - Para-virtualized network driver (virtio-net) + The para-virtualized network driver (virtio-net) The para-virtualized network driver can be used as the driver for existing network devices or new network devices for virtual machines. @@ -376,7 +377,7 @@ - Para-virtualized block driver (virtio-blk) + The para-virtualized block driver (virtio-blk) The para-virtualized block driver is a driver for all storage devices, is supported by the hypervisor, and is attached to the virtual machine (except for floppy disk drives, which must be emulated). @@ -419,7 +420,7 @@ PCI device assignment - The KVM hypervisor supports attaching PCI devices on the host system to virtual machines. PCI device assignment allows guests to have exclusive access to PCI devices for a range of tasks. It allows PCI devices to appear and behave as if they were physically attached to the guest operating system. + The KVM hypervisor supports attaching PCI devices on the host system to virtual machines. PCI device assignment allows guests to have exclusive access to PCI devices for a range of tasks. It allows PCI devices to appear and behave as if they were physically attached to the guest virtual machine. Device assignment is supported on PCI Express devices, with the exception of graphics cards. Parallel PCI devices may be supported as assigned devices, but they have severe limitations due to security and system configuration conflicts. @@ -497,13 +498,19 @@ of current processor models are now included by default, allowing users to specify features more accurately and migrate more safely. - - + + + For more information on guest CPU models, refer to the Fedora Virtualization Deployment Guide. + + + + + + class. The CPU models that Red Hat Enterprise Linux supports can be found in the qemu-kvm Whitelist chapter in the Virtualization Administration Guide. @@ -562,7 +569,7 @@ warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000] If a defined feature is not available, those features will fail silently by default. - + --> - 0.2-83 - Mon June 18 2012 + 1.0-01 + Tuesday August 14 2012 Dayle Parker @@ -18,424 +18,10 @@ - Version for 6.3 GA release + Initial creation of book for Fedora. - - 0.2-82 - Mon June 18 2012 - - Dayle - Parker - dayleparker@redhat.com - - - - Corrected "64 vCPUs" to "160 vCPUs" for BZ#832415. - - - - - 0.2-80 - Tues June 12 2012 - - Dayle - Parker - dayleparker@redhat.com - - - - Clarified emulated watchdog device section for BZ#827307. - - - - - 0.2-78 - Fri June 8 2012 - - Dayle - Parker - dayleparker@redhat.com - - - - Corrected typos and markup for BZ#827305. - General corrections made to Chapter 4 BZ#827307. - - - - - 0.2-73 - Mon 23 April 2012 - - Laura - Novich - lnovich@redhat.com - - - - Corrections made to chapter 5 (BZ#798108). - - - - - 0.2-72 - Mon 23 April 2012 - - Laura - Novich - lnovich@redhat.com - - - - Corrections made to chapter 4 (BZ#798106). - - - - - 0.2-71 - Thur 19 April 2012 - - Laura - Novich - lnovich@redhat.com - - - - Corrections made to chapter 5 (BZ#798108). - - - - - 0.2-69 - Wed 18 April 2012 - - Laura - Novich - lnovich@redhat.com - - - - Corrections made to chapter 4 (BZ#798106). - - - - - 0.2-68 - Tue 17 April 2012 - - Dayle - Parker - dayleparker@redhat.com - - - - Corrected terminology to "virtual machine" where needed (BZ#798063). - - - - - 0.2-64 - Mon 2 April 2012 - - Laura - Novich - lnovich@redhat.com - - - - BZ#800401 Corrections to Chapter 2 - - - - - 0.2-61 - Fri 30 March 2012 - - Dayle - Parker - dayleparker@redhat.com - - - - Made corrections in Chapter 3: Advantages (BZ#800409). - Adjusted terms to "virtual machine" and "virtualized guest" where appropriate; corrected outdated link in 4.1; corrected terms in Emulated network devices (from drivers) in (BZ#798063). - - - - - 0.2-52 - Wed 11 January 2012 - - Jacquelynn - East - jeast@redhat.com - - - - BZ#772859 clarified acronym. - - - - - 0.2-51 - Fri 04 November 2011 - - Jacquelynn - East - jeast@redhat.com - - - - BZ#750969 minor typos. - - - - - 0.2-47 - Fri 14 October 2011 - - Jacquelynn - East - jeast@redhat.com - - - - BZ#744156 add paragraph about emulated watchdogs. - - - - - 0.2-45 - Sun 18 September 2011 - - Scott - Radvan - sradvan@redhat.com - - - - Minor wording issues. - - - - - 0.2-44 - Fri 16 September 2011 - - Jacquelynn - East - jeast@redhat.com - - - - BZ#734614 - - - - - 0.2-43 - Fri 16 September 2011 - - Jacquelynn - East - jeast@redhat.com - - - - BZ#734618 minor edit - - - - - - 0.2-37 - Fri 2 September 2011 - - Jacquelynn - East - jeast@redhat.com - - - - BZ#734619, BZ#734614 - - - - - - 0.2-34 - Thu 1 September 2011 - - Jacquelynn - East - jeast@redhat.com - - - - BZ#734619, BZ#734511, BZ#734618, BZ#734616, BZ#715476, BZ#734613 - - - - - - 0.2-33 - Wed 31 August 2011 - - Jacquelynn - East - jeast@redhat.com - - - - BZ#734618, BZ#734613, BZ#734619 - - - - - - 0.2-34 - Thu 25 August 2011 - - Scott - Radvan - sradvan@redhat.com - - - - 6.2 development. - - - - - - - - - - 0.2-24 - Fri July 29 2011 - - Jacquelynn - East - jeast@redhat.com - - - - Extensive edits, combine security section into advantages - - - - - - - 0.2-22 - Wed July 27 2011 - - Jacquelynn - East - jeast@redhat.com - - - - Advantages chapter completed BZ#715476 - - - - - - 0.2-20 - Tue July 26 2011 - - Jacquelynn - East - jeast@redhat.com - - - - More of the Advantages draft - - - - - - 0.2-17 - Mon July 25 2011 - - Jacquelynn - East - jeast@redhat.com - - - - Minor edits for BZ#715473 and BZ#715474 - - - - - - 0.2-15 - Mon July 25 2011 - - Jacquelynn - East - jeast@redhat.com - - - - Chapter 4 draft BZ#715476 - - - - - - 0.2-4 - Thu June 23 2011 - - Jacquelynn - East - jeast@redhat.com - - - - Completed chapter 1 - - - - - - - - - 0.1-01 - Wed May 4 2011 - - Scott - Radvan - sradvan@redhat.com - - - - Arrange basic layout and book infrastructure. Import introductory text. - - - - - 0.0-01 - Wed May 4 2011 - - Scott - Radvan - sradvan@redhat.com - - - - Initial creation of book by Publican. - - - - - + \ No newline at end of file diff --git a/en-US/What_Is_It.xml b/en-US/What_Is_It.xml index 743e799..b307d6c 100644 --- a/en-US/What_Is_It.xml +++ b/en-US/What_Is_It.xml @@ -7,7 +7,7 @@
What is virtualization? - Virtualization is a broad computing term used for running software, usually multiple operating systems, concurrently and in isolation from other programs on a single system. Most existing implementations of virtualization use a hypervisor, a software layer or subsystem that controls hardware and provides guest operating systems with access to underlying hardware. The hypervisor allows multiple operating systems, called guests, to run on the same physical system by offering virtualized hardware to the guest operating system. There are various methods for virtualizing operating systems: + Virtualization is a broad computing term used for running software, usually multiple operating systems, concurrently and in isolation from other programs on a single system. Most existing implementations of virtualization use a hypervisor, a software layer or subsystem that controls hardware and provides guest operating systems with access to underlying hardware. The hypervisor allows multiple operating systems, called guests, to run on the same physical system by offering virtualized hardware to the guest operating system. There are various methods for virtualizing operating systems: Full virtualization @@ -27,7 +27,7 @@ Software virtualization (or emulation) - Software virtualization uses slower binary translation and other emulation techniques to run unmodified operating systems. Software virtualization is unsupported by Fedora. + Software virtualization uses slower binary translation and other emulation techniques to run unmodified operating systems. @@ -94,14 +94,14 @@ - + + It is important to understand that the migration process moves the virtual machine's memory. This process is done using live migration. + Shared, networked storage must be used for storing guest images to be migrated. Without shared storage, migration is not possible. It is recommended to use libvirt-managed storage pools for shared storage. - For more information on migration refer to the Fedora Virtualization Administration Guide. + For more information on migration, refer to the Fedora Virtualization Administration Guide.
-- cgit