Rearranged Migration section and included storage migration feature description for BZ#953341;Added xHCI host controller to Emulated system components list

5 files changed, 34 insertions, 11 deletions

diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml
index 3b43cb9..4e0d555 100644
--- a/en-US/Book_Info.xml
+++ b/en-US/Book_Info.xml
@@ -8,7 +8,7 @@
 	<subtitle>Virtualization Documentation</subtitle>
 	<productname>Fedora Draft Documentation</productname>
 	<productnumber></productnumber>
-	<edition>18.0.1</edition>
+	<edition>19.0.1</edition>
 	<pubsnumber>03</pubsnumber>
 	<abstract>
 		<para>
diff --git a/en-US/Products.xml b/en-US/Products.xml
index 369e724..9f4b374 100644
--- a/en-US/Products.xml
+++ b/en-US/Products.xml
@@ -243,6 +243,9 @@
                                           <listitem>
                                              <para>EHCI controller, virtualized USB storage and a USB mouse</para>
                                           </listitem>
+                                          <listitem> <!--for BZ952527 (RHEL7 and F19) - correct usage? IBM calls it USB 3.0 eXtensible Host Controller-->
+                                             <para>USB 3.0 xHCI host controller</para>
+                                          </listitem>                                          
                                     </itemizedlist>
                              </listitem>
                            </varlistentry>
@@ -563,7 +566,7 @@
                         </variablelist>
                      </section>
                      <section>
-                              <title>Storage Volumes</title>
+                              <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 virtual machines as local storage devices regardless of the underlying hardware.
                                     </para>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index 9bec64d..c506911 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -9,6 +9,21 @@
 		<revhistory>
 			<!--EDIT MY REVNUMBER AND DESCRIPTION AT RELEASE TIME FOR MAJOR REVISION-->
                         <revision>
+                                <revnumber>1.0-07</revnumber>
+                                <date>Monday May 6, 2013</date>
+                                <author>
+                                        <firstname>Dayle</firstname>
+                                        <surname>Parker</surname>
+                                        <email>dayleparker@redhat.com</email>
+                                </author>
+                                <revdescription>
+                                        <simplelist>
+                                          <member>Rearranged Migration section and included storage migration feature description.</member>
+                                          <member>Added xHCI host controller to Emulated system components list.</member>
+                                        </simplelist>
+                                </revdescription>
+                        </revision>
+                        <revision>
                                 <revnumber>1.0-06</revnumber>
                                 <date>Friday May 3, 2013</date>
                                 <author>
diff --git a/en-US/Virtualization_Getting_Started_Guide.ent b/en-US/Virtualization_Getting_Started_Guide.ent
index 3de4653..fed1363 100644
--- a/en-US/Virtualization_Getting_Started_Guide.ent
+++ b/en-US/Virtualization_Getting_Started_Guide.ent
@@ -1,4 +1,4 @@
 <!ENTITY PRODUCT "Fedora 18">
 <!ENTITY BOOKID "virtualization-getting-started-guide">
-<!ENTITY YEAR "2012">
+<!ENTITY YEAR "2012-2013">
 <!ENTITY HOLDER "Red Hat, Inc. and others.">
diff --git a/en-US/What_Is_It.xml b/en-US/What_Is_It.xml
index 241f354..fc08e88 100644
--- a/en-US/What_Is_It.xml
+++ b/en-US/What_Is_It.xml
@@ -7,9 +7,10 @@
 	<section id="sec-what_is_virtualization">
 	<title>What is virtualization?</title>
                   <para>
-                     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 <firstterm>hypervisor</firstterm>, a software layer or subsystem that controls hardware and provides <firstterm>guest operating systems</firstterm> with access to underlying hardware. The hypervisor allows multiple operating systems, called <firstterm>guests</firstterm>, to run on the same physical system by offering virtualized hardware to the guest operating system. There are various methods for virtualizing operating systems:
+                     <firstterm>Virtualization</firstterm> 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 <firstterm>hypervisor</firstterm>, a software layer or subsystem that controls hardware and provides <firstterm>guest operating systems</firstterm> with access to underlying hardware. The hypervisor allows multiple operating systems, called <firstterm>guests</firstterm>, to run on the same physical system by offering virtualized hardware to the guest operating system. There are several methods for virtualizing operating systems.
                   </para>
                   <variablelist>
+                  <title>Virtualization methods</title>
                      <varlistentry><term><emphasis role="strong">Full virtualization</emphasis></term>
                         <listitem>
                               <para>
@@ -39,12 +40,12 @@
                      </note>-->
 	</section>
         <section id="sec-migration">
-        <title>Migration</title>
+        <title>What is migration?</title>
                   <para>
                      <firstterm>Migration</firstterm> describes the process of moving a guest virtual machine from one host to another. This is possible because guests are running in a virtualized environment instead of directly on the hardware. There are two ways to migrate a virtual machine: live and offline.
                   </para>
                   <variablelist>
-                        <title>Migration Types</title>
+                        <title>Migration types</title>
                               <varlistentry>
                                     <term><emphasis role="strong">Offline migration</emphasis></term>
                                     <listitem>
@@ -97,19 +98,21 @@
                                     </varlistentry>
                               </variablelist>
                               <para>
-                                 It is important to understand that the migration process moves the virtual machine's memory. <!--and from Red Hat Enterprise Linux&nbsp;6.3, the disk volume associated with the virtual machine is also migrated.--> This process is done using live migration.
+                                 It is important to understand that the migration process moves the virtual machine's memory, and the disk volume associated with the virtual machine is also migrated. This process is done using live block migration.
                               </para>
                               <para>
-                                 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 <application>libvirt</application>-managed storage pools for shared storage.
+                                 In Fedora 19, shared storage is not necessary for storing guest images to be migrated. With storage migration, a running virtual machine (as well as its in-use storage) can be migrated from one host to another with no downtime. This capability can be used to optimize performance of virtual machines.
                               </para>
+            <!--  F18 WAS:    <para>
+                                 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 <application>libvirt</application>-managed storage pools for shared storage.
+                              </para>-->
 <!--                              <note>
                                  <para>
                                     For more information on migration, refer to the <citetitle>Fedora Virtualization Depolyment and Administration Guide</citetitle>.
                                  </para>
                               </note>-->
                      </section>
-        </section>
-<!--        <section id="Virtualized_to_virtualized">
+         <!--        <section id="Virtualized_to_virtualized">
                 <title>Virtualized to virtualized migration (V2V)</title>
                 <para>
                      Fedora provides tools for converting virtual machines from other types of hypervisors to KVM. The <command>virt-v2v</command> tool converts and imports virtual machines from Xen, other versions of KVM, and VMware ESX.
@@ -117,5 +120,7 @@
                 <!--<para> IS THERE A V2V Guide for Fedora? Does virt v2v work in Fedora?
                         For more information on V2V, refer to the <citetitle>Red Hat Enterprise Linux&nbsp;6 V2V Guide</citetitle>.
                 </para>
-        </section>-->
+                     </section>-->
+        </section>
+
 </chapter>
\ No newline at end of file