diff options
Diffstat (limited to 'en-US/Products.xml')
| -rw-r--r-- | en-US/Products.xml | 63 |
1 files changed, 35 insertions, 28 deletions
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 @@ <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 <citetitle>Fedora Virtualization Administration Guide.</citetitle> </para> - <!--<para> + <!-- REMOVED AS THERE IS NO FEDORA SUPPORT MATRIX. <para> Fedora servers have certain support limits. </para> <para> Is there a corresponding matrix for Fedora? @@ -105,10 +105,10 @@ </listitem> </itemizedlist> <para> - The <package>libvirt</package> package is designed as a building block for higher level management tools and applications, for example, <command>virt-manager</command> and the <command>virsh</command> command line management tools. With the exception of migration capabilities, <application>libvirt</application> focuses on managing single hosts and provides APIs to enumerate, monitor and use the resources available on the managed node, including CPUs, memory, storage, networking and Non-Uniform Memory Access (NUMA) partitions. The management tools can be located on separate physical machines from the host using secure protocols. + The <package>libvirt</package> package is designed as a building block for higher level management tools and applications, for example, <command>virt-manager</command> and the <command>virsh</command> command-line management tools. With the exception of migration capabilities, <application>libvirt</application> focuses on managing single hosts and provides APIs to enumerate, monitor and use the resources available on the managed node, including CPUs, memory, storage, networking and Non-Uniform Memory Access (NUMA) partitions. The management tools can be located on separate physical machines from the host using secure protocols. </para> <para> - Fedora supports <application>libvirt</application> and included <application>libvirt</application>-based tools as its default method for virtualization management<!-- (as in Red Hat Enterprise Virtualization Management)-->. + Fedora supports <application>libvirt</application> and included <application>libvirt</application>-based tools as its default method for virtualization management. </para> <para> The <package>libvirt</package> package is available as free software under the GNU Lesser General Public License. The <package>libvirt</package> project aims to provide a long term stable C API to virtualization management tools, running on top of varying hypervisor technologies. <!--The <package>libvirt</package> package supports Xen on Red Hat Enterprise Linux 5, and it supports KVM on both Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6.--> @@ -133,7 +133,7 @@ </variablelist> <note> <para> - For more information on <command>virt-manager</command>, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>. + For more information on <command>virsh</command> and <application>virt-manager</application>, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>. </para> </note> </section> @@ -145,7 +145,7 @@ <itemizedlist> <listitem> <para> - Virtualized and emulated software devices <!--(was: Emulated software devices - is this correct? hardware/software?)--> + Virtualized and emulated devices </para> </listitem> <listitem> @@ -230,13 +230,13 @@ </itemizedlist> </listitem> </varlistentry> -<!-- <varlistentry> What is the Fedora equivalent for all of this? - <term>Emulated sound devices</term> + <varlistentry> + <term>Emulated sound devices</term> <!--What is the Fedora equivalent for all of this?--> <listitem> - <para> - Red Hat Enterprise Linux 6.1 and above provides an emulated (Intel) HDA sound device, <systemitem>intel-hda</systemitem>. This device is supported on the following guest operating systems: + <para> <!--FIX THIS PART! VERIFY WITH SMEs--> + <!--Red Hat Enterprise Linux 6.1 and above--> Fedora 18 provides an emulated (Intel) HDA sound device, <systemitem>intel-hda</systemitem>. <!--This device is supported on the following guest operating systems:--> </para> - <itemizedlist> + <!--<itemizedlist> <listitem> <para> Red Hat Enterprise Linux 6, for i386 and x86_64 architectures @@ -262,7 +262,7 @@ Windows 2008 R2, for the x86_64 architecture </para> </listitem> - </itemizedlist> + </itemizedlist>--> <para> The following two emulated sound devices are also available, but are not recommended due to compatibility issues with certain guest operating systems: </para> @@ -275,12 +275,13 @@ </listitem> </itemizedlist> </listitem> - </varlistentry>--> - <!-- <varlistentry> What is the Fedora equivalent? - <term>Emulated watchdog devices</term> + </varlistentry> + + <varlistentry> + <term>Emulated watchdog devices</term> <!-- Verify for Fedora with SMEs! Removed questionable bits for now. --> <listitem> <para> - 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. + <!--Red Hat Enterprise Linux 6.0 and above--> Fedora 18 provides two emulated watchdog devices. A watchdog can be used to automatically reboot a virtual machine when it becomes overloaded or unresponsive. </para> <para> The <package>watchdog</package> package must be installed on the guest. @@ -291,20 +292,20 @@ <itemizedlist> <listitem> <para> - <systemitem>i6300esb</systemitem>, 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. + <systemitem>i6300esb</systemitem>, 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.--> </para> </listitem> <listitem> <para> - <systemitem>ib700</systemitem>, an emulated iBase 700 ISA watchdog device. The <systemitem>ib700</systemitem> watchdog device is only supported in guests using Red Hat Enterprise Linux 6.2 and above. + <systemitem>ib700</systemitem>, an emulated iBase 700 ISA watchdog device. <!--The <systemitem>ib700</systemitem> watchdog device is only supported in guests using Red Hat Enterprise Linux 6.2 and above.--> </para> </listitem> </itemizedlist> - <para> + <!-- <para> Both watchdog devices are supported in i386 and x86_64 architectures for guest operating systems Red Hat Enterprise Linux 6.2 and above. - </para> + </para>--> </listitem> - </varlistentry>--> + </varlistentry> <varlistentry> <term>Emulated network devices</term> <listitem> @@ -368,7 +369,7 @@ </para> <variablelist> <varlistentry> - <term>Para-virtualized network driver (virtio-net)</term> + <term>The para-virtualized network driver (virtio-net)</term> <listitem> <para> The para-virtualized network driver <!--is a Red Hat branded virtual network device. It--> can be used as the driver for existing network devices or new network devices for virtual machines. @@ -376,7 +377,7 @@ </listitem> </varlistentry> <varlistentry> - <term>Para-virtualized block driver (virtio-blk)</term> + <term>The para-virtualized block driver (virtio-blk)</term> <listitem> <para> 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 @@ <term>PCI device assignment</term> <listitem> <para> - 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. </para> <para> 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. </para> - - <para> + <note> + <para> + For more information on guest CPU models, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>. + </para> + </note> + + + <!-- REMOVE FROM THIS GUIDE - NEEDS TO GO INTO THE VIRT DEPLOYMENT GUIDE <para> A list of supported CPU models can be viewed with the <command>/usr/libexec/qemu-kvm -cpu ?model</command> command. This command outputs the <parameter>name</parameter> used to select the CPU model at the command line, and a model identifier that corresponds to a commercial instance of that processor - class. <!--The CPU models that Red Hat Enterprise Linux supports can be found in the <citetitle>qemu-kvm Whitelist</citetitle> chapter in the <citetitle>Virtualization Administration Guide</citetitle>.--> + class. The CPU models that Red Hat Enterprise Linux supports can be found in the <citetitle>qemu-kvm Whitelist</citetitle> chapter in the <citetitle>Virtualization Administration Guide</citetitle>. </para> <para> @@ -562,7 +569,7 @@ warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]</screen <para> If a defined feature is not available, those features will fail silently by default. - </para> + </para> --> <!--Use the <code>enforce</code> flag to force QEMU to exit in error when an explicit or implicit feature flag is not supported: </para> @@ -605,7 +612,7 @@ warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000] <section> <title>Storage Volumes</title> <para> - Storage pools are further 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 <application>libvirt</application>. Storage volumes are presented to virtualized guests as local storage devices regardless of the underlying hardware. + Storage pools are further 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 <application>libvirt</application>. Storage volumes are presented to virtual machines as local storage devices regardless of the underlying hardware. </para> <note> |