summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDayle Parker <dayleparker@redhat.com>2012-07-20 15:20:37 +1000
committerDayle Parker <dayleparker@redhat.com>2012-07-20 15:20:37 +1000
commitfa7de08705918cea1a6d09d4d450ef659ce87f35 (patch)
tree22e2026eda4684f850c9a7c70238b9f564c948b9
parent9f529cbc47f6d367e032bd79b14cf77179d8cf78 (diff)
downloadvirtualization-getting-started-guide-fa7de08705918cea1a6d09d4d450ef659ce87f35.tar.gz
virtualization-getting-started-guide-fa7de08705918cea1a6d09d4d450ef659ce87f35.tar.xz
virtualization-getting-started-guide-fa7de08705918cea1a6d09d4d450ef659ce87f35.zip
Fixed typos and formatting
-rw-r--r--en-US/Advantages.xml2
-rw-r--r--en-US/Products.xml20
2 files changed, 11 insertions, 11 deletions
diff --git a/en-US/Advantages.xml b/en-US/Advantages.xml
index 5859d92..ea5df7b 100644
--- a/en-US/Advantages.xml
+++ b/en-US/Advantages.xml
@@ -115,7 +115,7 @@
<title>SELinux</title>
<para>SELinux was developed by the US National Security Agency and others to provide Mandatory Access Control (MAC) for Linux. Under control of SELinux, all processes and files are given what is known as a <emphasis>type</emphasis>, and access is limited by fine-grained controls. SELinux limits the abilities of an attacker and works to prevent many common security exploits such as buffer overflow attacks and privilege escalation.</para>
</formalpara>
- <para>SELinux strengthens the security model of Red Hat Enterprise Linux hosts and virtualized Red Hat Enterprise Linux guests. SELinux is configured and tested to work, by default, with all virtualization tools shipped with Red Hat Enterprise Linux&nbsp;6.</para>
+ <para>SELinux strengthens the security model of Fedora hosts and virtualized Fedora guests. SELinux is configured and tested to work, by default, with all virtualization tools shipped with Fedora.</para>
<!--<note> Ask mprpic - owner of F17 SELinux User Guide - what to refer to here?
<para>For more information on SELinux, refer to the SELinux documentation at <ulink url="http://docs.redhat.com/docs/" />. For more information on security within virtualization, refer to the <citetitle>Fedora Virtualization Security Guide</citetitle>.
diff --git a/en-US/Products.xml b/en-US/Products.xml
index 79aa32c..bdbbdc3 100644
--- a/en-US/Products.xml
+++ b/en-US/Products.xml
@@ -376,7 +376,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>>Para-virtualized block driver (virtio-blk)</term>
+ <term>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).
@@ -384,7 +384,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>>The para-virtualized clock</term>
+ <term>The para-virtualized clock</term>
<listitem>
<para>
Guests using the Time Stamp Counter (TSC) as a clock source may suffer timing issues. KVM works around hosts that do not have a constant Time Stamp Counter by providing guests with a para-virtualized clock.
@@ -392,7 +392,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>>The para-virtualized serial driver (virtio-serial)</term>
+ <term>The para-virtualized serial driver (virtio-serial)</term>
<listitem>
<para>
The para-virtualized serial driver is a bytestream-oriented, character stream driver, and provides a simple communication interface between the host's user space and the guest's user space.
@@ -400,7 +400,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>>The balloon driver (virtio-balloon)</term>
+ <term>The balloon driver (virtio-balloon)</term>
<listitem>
<para>
The balloon driver can designate part of a virtual machine's RAM as not being used (a process known as balloon <emphasis>inflation</emphasis>), so that the memory can be freed for the host (or for other virtual machines on that host) to use. When the virtual machine needs the memory again, the balloon can be <emphasis>deflated</emphasis> and the host can distribute the RAM back to the virtual machine.
@@ -432,7 +432,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>>USB passthrough</term>
+ <term>USB passthrough</term>
<listitem>
<para>
The KVM hypervisor supports attaching USB devices on the host system to virtual machines. USB device assignment allows guests to have exclusive access to USB devices for a range of tasks. It allows USB devices to appear and behave as if they were physically attached to the virtual machine.
@@ -445,7 +445,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>>SR-IOV</term>
+ <term>SR-IOV</term>
<listitem>
<para>
SR-IOV (Single Root I/O Virtualization) is a PCI Express standard that extends a single physical PCI function to share its PCI resources as separate, virtual functions (VFs). Each function is capable of being used by a different virtual machine via PCI device assignment.
@@ -461,7 +461,7 @@
</listitem>
</varlistentry>
<varlistentry>
- <term>>NPIV</term>
+ <term>NPIV</term>
<listitem>
<para>
N_Port ID Virtualization (NPIV) is a functionality available with some Fibre Channel devices. NPIV shares a single physical N_Port as multiple N_Port IDs. NPIV provides similar functionality for Fibre Channel Host Bus Adapters (HBAs) that SR-IOV provides for PCIe interfaces. With NPIV, virtual machines can be provided with a virtual Fibre Channel initiator to Storage Area Networks (SANs).
@@ -481,7 +481,7 @@
</section>
<section id="para-CPU_Models">
<title>Guest CPU models</title>
- <para>t
+ <para>
Historically, CPU model definitions were hard-coded in
<application>qemu</application>. This method of defining CPU models was
inflexible, and made it difficult to create virtual CPUs with feature sets
@@ -581,7 +581,7 @@ warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]
<section>
<title>Storage pools</title>
<para>
- A <firstterm>storage pool</firstterm> is a file, directory, or storage device managed by <application>libvirt</application> for the purpose of providing storage to virtual machines. Storage pools are divided into storage <firstterm>volumes</firstterm> that store virtual machine images or are attached to virtual machines as additional storage. Multiple guests can share the same storage pool, allowing for better allocation of storage resources. Refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle> for more information.
+ A <firstterm>storage pool</firstterm> is a file, directory, or storage device managed by <application>libvirt</application> for the purpose of providing storage to virtual machines. Storage pools are divided into storage <firstterm>volumes</firstterm> that store virtual machine images or are attached to virtual machines as additional storage. Multiple guests can share the same storage pool, allowing for better allocation of storage resources.
</para>
<variablelist>
<varlistentry>
@@ -600,7 +600,7 @@ warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]
</para>
</listitem>
</varlistentry>
- </variablelist>
+ </variablelist>
</section>
<section>
<title>Storage Volumes</title>