Made changes throughout book to update for F19, according to RHEL7 content

8 files changed, 205 insertions, 156 deletions

diff --git a/en-US/Advantages.xml b/en-US/Advantages.xml
index 1e0bec9..36551ee 100644
--- a/en-US/Advantages.xml
+++ b/en-US/Advantages.xml
@@ -115,8 +115,12 @@
 				<title>sVirt</title>
 				<para>sVirt is a technology included in Fedora that integrates SELinux and virtualization. It applies Mandatory Access Control (MAC) to improve security when using virtual machines, and improves security and hardens the system against bugs in the hypervisor that might be used as an attack vector for the host or to another virtual machine.</para>
 			</formalpara>
-	<note><para>For more information on sVirt, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.</para></note>
-		</section>
+               <note>
+                  <para>
+                     For more information on security for virtualization, refer to the <citetitle>Fedora Virtualization Security Guide</citetitle>.
+                  </para>
+               </note>
+            </section>
 		
 	</section>
 	
diff --git a/en-US/Introduction.xml b/en-US/Introduction.xml
index 7b64f7e..4bed90b 100644
--- a/en-US/Introduction.xml
+++ b/en-US/Introduction.xml
@@ -5,7 +5,7 @@
     <title>Introduction</title>
     
     <para>
-       The Virtualization Getting Started Guide introduces the basics of virtualization and assists with the navigation of other virtualization documentation and products that Fedora provides.
+       The  <citetitle>Virtualization Getting Started Guide</citetitle> introduces the basics of virtualization and assists with the navigation of other virtualization documentation and products that Fedora provides.
     </para>
       
     <para>
@@ -38,28 +38,21 @@
 
       </itemizedlist>
     </section>
-<!--     Should there be a description of RHEL Virt here? In both RHEL and Fedora guides? -->
-    <section> <!--Remove section? IS there a Fedora equivalent?
-                  *REMOVED FOR NOW AND ADDED VIRTUALIZATION RESOURCES TITLE & PARA-->
-     <!-- <title>Red Hat Enterprise Virtualization (RHEV)</title>
-      <para>
-	Red Hat Enterprise Virtualization for Servers is an end-to-end virtualization solution that is designed to enable pervasive datacenter virtualization and significantly enhance capital and operational efficiency. Red Hat Enterprise Virtualization 3.0 introduces several new features, including desktop virtualization with the Red Hat Enterprise Virtualization for Desktop add-on subscription.
-      </para>
-      
-      <para>
-	With Red Hat Enterprise Virtualization for Desktops, complete desktop environments are hosted as virtual desktops on servers located in a centralized datacenter. 
-      </para>
-      
-      <para>
-	Information on both these products can be found at <ulink url="http://www.redhat.com/products/virtualization/"/>.
-      </para>
-	
-      <para>
-	The full collection of Red Hat Enterprise Virtualization (RHEV) documentation can be found at <ulink url="http://docs.redhat.com/"/>. 
-      </para>
-	<para>
-         In addition to the documentation for Red Hat Enterprise Virtualization products and this guide, the following titles cover virtualization with Fedora:
-	</para>-->
+    <section> 
+       <title>Virtualization in Fedora&nbsp;19</title>
+       <para>
+         Fedora contains packages and tools to support a variety of virtualized environments.
+       </para>
+       <para>
+         Virtualization in Fedora is carried out by KVM (Kernel-based Virtual Machine). KVM is a full virtualization solution built into Fedora. 
+       </para>
+       <para>
+         Refer to <xref linkend="chap-Virtualization_Getting_Started-Products"/> for more about the virtualization products available in Fedora&nbsp;19. 
+       </para>
+   </section>
+
+    <section> 
+       
            <title>Virtualization resources</title>
            <para>
               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 <xref linkend="chap-Virtualization_Getting_Started-Products"/> for more information about the virtualization products available in Fedora.
@@ -68,11 +61,11 @@
                In addition to this guide, the following books cover virtualization with Fedora: 
             </para>
             <itemizedlist>
-               <listitem>      
+<!--               <listitem>      
                      <para>
                         <citetitle>Virtualization Deployment Guide</citetitle>: This guide provides information on system requirements and restrictions, package details, host configuration and detailed instructions for installing different types of guests. 
                      </para>
-               </listitem>
+               </listitem>-->
                <listitem>
                      <para>
                         <citetitle>Virtualization Administration Guide</citetitle>: This guide provides information on servers, security, KVM, remote management of guests, KSM, administration tasks, storage, volumes, <application>virt-manager</application>, guest disk access with offline tools, virtual networking, and troubleshooting.
diff --git a/en-US/Products.xml b/en-US/Products.xml
index 71c9f0f..369e724 100644
--- a/en-US/Products.xml
+++ b/en-US/Products.xml
@@ -23,7 +23,7 @@
                               </para>
                               <important>
                                     <para>
-                                       Overcommitting involves possible risks to system stability. For more information on overcommitting with KVM, and the precautions that should be taken, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
+                                       Overcommitting involves possible risks to system stability. <!--For more information on overcommitting with KVM, and the precautions that should be taken, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.-->
                                     </para>
                               </important>
                         </listitem>
@@ -36,7 +36,7 @@
                                  </para>
                                  <important>
                                        <para>
-                                          Thin provisioning involves possible risks to system stability. For more information on thin provisioning with KVM, and the precautions that should be taken, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
+                                          Thin provisioning involves possible risks to system stability. <!--For more information on thin provisioning with KVM, and the precautions that should be taken, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.-->
                                        </para>
                                  </important>        
                         </listitem>
@@ -47,18 +47,31 @@
                                  <para>
                                        <firstterm>Kernel SamePage Merging (KSM)</firstterm>, used by the KVM hypervisor, allows KVM guests to share identical memory pages. These shared pages are usually common libraries or other identical, high-use data. KSM allows for greater guest density of identical or similar guest operating systems by avoiding memory duplication.
                                  </para>
-                                 <note>
+<!--                                 <note>
                                        <para>
                                              For more information on KSM, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
                                        </para>
-                                 </note>
+                                 </note>-->
+                        </listitem>
+               </varlistentry>
+               <varlistentry><!--Added to RHEL 6.4, adding for F19-->
+                        <term>QEMU Guest Agent</term>
+                        <listitem>
+                                 <para>
+                                       The <firstterm>QEMU Guest Agent</firstterm> runs on the guest operating system and allows the host machine to issue commands to the guest operating system.
+                                 </para>
+                             <!--    <note>  verify for RHEL7 - 
+                                       <para>
+                                             For more information on the QEMU Guest Agent, refer to the <citetitle>Red Hat Enterprise Linux&nbsp;6 Virtualization Host Configuration and Guest Installation Guide</citetitle>.
+                                       </para>
+                                 </note>-->
                         </listitem>
                </varlistentry>
                <varlistentry>
-                        <term>KVM Guest VM Compatibility</term>
+                        <term>KVM guest virtual machine compatibility</term>
                         <listitem>
                                  <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>
+                                       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 Deployment and Administration Guide.</citetitle>
                                  </para>
          <!-- REMOVED AS THERE IS NO FEDORA SUPPORT MATRIX. <para>
         Fedora servers have certain support limits.
@@ -135,7 +148,7 @@
             </variablelist>
                <note>
                      <para>
-                        For more information on <command>virsh</command> and <application>virt-manager</application>, 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 Deployment and Administration Guide</citetitle>.
                      </para>
                   </note>
 </section>
@@ -143,6 +156,7 @@
             <title>Virtualized hardware devices</title>
             <para>
                Virtualization on Fedora presents three distinct types of system devices to virtual machines. The three types include:
+                              <!-- Revisit this with the PCI device assignment definitions for RHEL 6.5 and 7. Redfine? -->
             </para>
                <itemizedlist>
                      <listitem>
@@ -235,8 +249,8 @@
                            <varlistentry> 
                               <term>Emulated sound devices</term>  <!--What is the Fedora equivalent for all of this?-->
                               <listitem>
-                                    <para> <!--FIX THIS PART! VERIFY WITH SMEs-->
-                                       <!--Red Hat Enterprise Linux&nbsp;6.1 and above--> Fedora&nbsp;18 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 - commented out '18'-->
+                                       <!--Red Hat Enterprise Linux&nbsp;6.1 and above--> Fedora<!--&nbsp;18--> provides an emulated (Intel) HDA sound device, <systemitem>intel-hda</systemitem>. <!--This device is supported on the following guest operating systems:-->
                                     </para>
                                     <!--<itemizedlist>
                                           <listitem>
@@ -283,7 +297,7 @@
                            <term>Emulated watchdog devices</term>                              <!-- Verify for Fedora with SMEs! Removed questionable bits for now. -->
                               <listitem>
                                     <para>
-                                       <!--Red Hat Enterprise Linux&nbsp;6.0 and above--> Fedora&nbsp;18 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&nbsp;6.0 and above--> Fedora<!--&nbsp;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. 
@@ -366,11 +380,11 @@
                         <para>
                            The para-virtualized devices must be installed on the guest operating system. <!--Fedora equivalent? By default, the para-virtualized drivers are included in Red Hat Enterprise Linux 4.7 and newer, Red Hat Enterprise Linux 5.4 and newer and Red Hat Enterprise Linux 6.0 and newer.--> The para-virtualized drivers must be manually installed on Windows guests.
                         </para>
-                        <note>
+<!--                        <note>
                               <para>
-                                 For more information on using the para-virtualized drivers, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>.
+                                 For more information on using the para-virtualized drivers, refer to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>.
                               </para>
-                        </note>
+                        </note>-->
                         <variablelist>
                            <varlistentry>
                               <term>The para-virtualized network driver (virtio-net)</term>
@@ -437,11 +451,11 @@
                                     <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.
                                     </para>
-                                       <note>
+<!--                                       <note>
                                           <para>
                                              For more information on device assignment, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>.
                                           </para>
-                                       </note> 
+                                       </note> -->
                               </listitem>
                            </varlistentry>
                            <varlistentry>
@@ -450,11 +464,11 @@
                                     <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.
                                     </para>
-                                       <note>
+<!--                                       <note>
                                           <para>
                                              For more information on USB passthrough, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
                                           </para>
-                                       </note>
+                                       </note>-->
                               </listitem>
                            </varlistentry>
                            <varlistentry>
@@ -466,11 +480,11 @@
                                     <para>
                                        An SR-IOV capable PCI-e device, provides a Single Root Function (for example, a single Ethernet port) and presents multiple, separate virtual devices as unique PCI device functions. Each virtual device may have its own unique PCI configuration space, memory-mapped registers, and individual MSI-based interrupts.
                                     </para> 
-                                       <note>
+<!--                                       <note>
                                           <para>
                                              For more information on SR-IOV, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>.
                                           </para>
-                                       </note>
+                                       </note>-->
                               </listitem>
                            </varlistentry>
                            <varlistentry>
@@ -482,11 +496,11 @@
                                     <para>
                                        NPIV can provide high density virtualized environments with enterprise-level storage solutions.
                                     </para>
-                                       <note>
+<!--                                       <note>
                                           <para>
                                              For more information on NPIV, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
                                           </para>
-                                       </note>
+                                       </note>-->
                               </listitem>
                            </varlistentry>
                         </variablelist>
@@ -510,85 +524,12 @@
             of current processor models are now included by default, allowing users to specify 
             features more accurately and migrate more safely.
          </para>
-            <note>
+<!--            <note>
                <para>
                   For more information on guest CPU models, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>.
                </para>
-            </note>
-         
+            </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>.
-            </para>
-
-         <para>
-            Configuration details for all of these CPU models can be output with the 
-            <command>/usr/libexec/qemu-kvm -cpu ?dump</command> command, but they are also stored in the
-            <filename>/usr/share/qemu-kvm/cpu-model/cpu-x86_64.conf</filename> file
-            by default. Each CPU model definition begins with <literal>[cpudef]</literal>, as shown:
-         </para>
-   <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)"</screen>
-
-            <para>
-               The four CPUID fields, <literal>feature_edx</literal>, <literal>feature_ecx</literal>,
-               <literal>extfeature_edx</literal> and <literal>extfeature_ecx</literal>, accept
-               named flag values from the corresponding feature sets listed by the
-               <command>/usr/libexec/qemu-kvm -cpu ?cpuid</command> command, as shown:      
-            </para>
-   <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</screen>
-            <para>
-               These feature sets are described in greater detail in the appropriate Intel
-               and AMD specifications.
-            </para>
-            <para>
-               It is important to use the <code>check</code> flag to verify that all
-               configured features are available.
-            </para>
-   <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]</screen>
-            <para>
-               If a defined feature is not available, those features will fail silently
-               by default.
-            </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>
-   <screen># /usr/libexec/qemu-kvm -cpu Nehalem,enforce
-warning: host cpuid 0000_0001 lacks requested flag 'sse4.2|sse4_2' [0x00100000]
-warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]
-  Unable to support requested x86 CPU definition</screen>-->
 
             </section>
 </section>      
@@ -615,7 +556,7 @@ warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]
                               <term>Networked (shared) storage pools</term>
                                 <listitem>
                                     <para>
-                                       Networked storage pools include storage devices shared over a network using standard protocols. Networked storage is required for migrating virtual machines between hosts. Networked storage pools are managed by <application>libvirt</application>.
+                                       Networked storage pools include storage devices shared over a network using standard protocols. Networked storage is required when migrating virtual machines between hosts with <application>virt-manager</application>, but is optional when migrating with <command>virsh</command>. Networked storage pools are managed by <application>libvirt</application>.
                                     </para>
                                 </listitem>
                            </varlistentry>
@@ -627,11 +568,11 @@ warning: host cpuid 0000_0001 lacks requested flag 'popcnt' [0x00800000]
                                        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>
+<!--            <note>
                <para>
                   For more information on storage and virtualization, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
                </para>
-            </note>
+            </note>-->
         </section>
 </section>
 </chapter>
\ No newline at end of file
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index 2911f73..9bec64d 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -8,6 +8,20 @@
 	<simpara>
 		<revhistory>
 			<!--EDIT MY REVNUMBER AND DESCRIPTION AT RELEASE TIME FOR MAJOR REVISION-->
+                        <revision>
+                                <revnumber>1.0-06</revnumber>
+                                <date>Friday May 3, 2013</date>
+                                <author>
+                                        <firstname>Dayle</firstname>
+                                        <surname>Parker</surname>
+                                        <email>dayleparker@redhat.com</email>
+                                </author>
+                                <revdescription>
+                                        <simplelist>
+                                          <member>Made initial general updates for Fedora 19.</member>
+                                        </simplelist>
+                                </revdescription>
+                        </revision>
                          <revision>
                                 <revnumber>1.0-05</revnumber>
                                 <date>Monday October 22, 2012</date>
diff --git a/en-US/Revision_History.xml~ b/en-US/Revision_History.xml~
new file mode 100644
index 0000000..2911f73
--- /dev/null
+++ b/en-US/Revision_History.xml~
@@ -0,0 +1,83 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Virtualization_Getting_Started_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<appendix id="appe-Virtualization_Getting_Started_Guide-Revision_History">
+	<title>Revision History</title>
+	<simpara>
+		<revhistory>
+			<!--EDIT MY REVNUMBER AND DESCRIPTION AT RELEASE TIME FOR MAJOR REVISION-->
+                         <revision>
+                                <revnumber>1.0-05</revnumber>
+                                <date>Monday October 22, 2012</date>
+                                <author>
+                                        <firstname>Dayle</firstname>
+                                        <surname>Parker</surname>
+                                        <email>dayleparker@redhat.com</email>
+                                </author>
+                                <revdescription>
+                                        <simplelist>
+                                          <member>Branch for Fedora 18 Beta.</member>
+                                        </simplelist>
+                                </revdescription>
+                        </revision>
+                        <revision>
+                                <revnumber>1.0-04</revnumber>
+                                <date>Monday October 22, 2012</date>
+                                <author>
+                                        <firstname>Dayle</firstname>
+                                        <surname>Parker</surname>
+                                        <email>dayleparker@redhat.com</email>
+                                </author>
+                                <revdescription>
+                                        <simplelist>
+                                          <member>Added virtio-scsi feature description to 4.3.2. Para-virtualized devices.</member>
+                                        </simplelist>
+                                </revdescription>
+                        </revision>
+			<revision>
+                                <revnumber>1.0-03</revnumber>
+                                <date>Thursday September 6, 2012</date>
+                                <author>
+                                        <firstname>Dayle</firstname>
+                                        <surname>Parker</surname>
+                                        <email>dayleparker@redhat.com</email>
+                                </author>
+                                <revdescription>
+                                        <simplelist>
+                                          <member>In Chapter 3: Advantages, added Flexibility point for (<ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=853826">BZ#853826</ulink>).</member>
+                                        </simplelist>
+                                </revdescription>
+                        </revision>
+                        <revision>
+                                <revnumber>1.0-02</revnumber>
+                                <date>Thursday August 23 2012</date>
+                                <author>
+                                        <firstname>Dayle</firstname>
+                                        <surname>Parker</surname>
+                                        <email>dayleparker@redhat.com</email>
+                                </author>
+                                <revdescription>
+                                        <simplelist>
+                                          <member>In Tools: deleted virt-inspector2, virt-cat warning, clarified --r/w warning as per feedback.</member>
+                                        </simplelist>
+                                </revdescription>
+                        </revision>
+			<revision>
+                                <revnumber>1.0-01</revnumber>
+                                <date>Tuesday August 14 2012</date>
+                                <author>
+                                        <firstname>Dayle</firstname>
+                                        <surname>Parker</surname>
+                                        <email>dayleparker@redhat.com</email>
+                                </author>
+                                <revdescription>
+                                        <simplelist>
+					  <member>Initial creation of book for Fedora.</member>
+                                        </simplelist>
+                                </revdescription>
+                        </revision>
+		</revhistory>
+	</simpara>
+</appendix>
\ No newline at end of file
diff --git a/en-US/Tools.xml b/en-US/Tools.xml
index 3673859..82e9350 100644
--- a/en-US/Tools.xml
+++ b/en-US/Tools.xml
@@ -14,13 +14,13 @@
    <section>
       <title><command>virsh</command></title>
       <para>
-        <firstterm>virsh</firstterm> is a command line interface (CLI) tool for managing guests and the hypervisor. The <command>virsh</command> command line tool is built on the <application>libvirt</application> management API and operates as an alternative to the <command>qemu-kvm</command> command and the graphical <application>virt-manager</application> application. The <command>virsh</command> command can be used in read-only mode by unprivileged users or, with root access, full administration functionality. The <command>virsh</command> command is ideal for scripting virtualization administration. In addition the <command>virsh</command> tool is a main management interface for <command>virsh</command> guest domains and can be used to create, pause, and shut down domains, as well as list current domains. This tool is installed as part of the <package>libvirt-client</package> package.
+        <firstterm>virsh</firstterm> is a command line interface (CLI) tool for managing the hypervisor and guest virtual machines. The <command>virsh</command> command line tool is built on the <application>libvirt</application> management API and operates as an alternative to the <command>qemu-kvm</command> command and the graphical <application>virt-manager</application> application. The <command>virsh</command> command can be used in read-only mode by unprivileged users or, with root access, full administrative functionality. The <command>virsh</command> command is ideal for scripting virtualization administration. In addition the <command>virsh</command> tool is a main management interface for <command>virsh</command> guest domains and can be used to create, pause, and shut down domains, as well as list current domains. This tool is installed as part of the <package>libvirt-client</package> package.
       </para>
-          <note>
+<!--          <note>
               <para>
                 Refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle> for more information about managing virtual machines with <command>virsh</command>.
               </para>
-          </note>
+          </note>-->
    </section>
    
    <section>
@@ -32,11 +32,11 @@
          machines, and view performance statistics. This tool ships in its own
          package called <package>virt-manager</package>.
       </para>
-            <note>
+<!--            <note>
               <para>
                 Refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle> for more information about managing virtual machines with <command>virt-manager</command>.
               </para>
-            </note>
+            </note>-->
    </section>
    
    <section>
@@ -49,11 +49,11 @@
          complete, allowing for easy automation of installation. This tool is
          installed as part of the <package>python-virtinst</package> package.
        </para>
-              <note>      
+<!--              <note>      
                 <para>
                   Refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle> for more information about <command>virt-install</command>.
               </para>
-            </note>
+            </note>-->
    </section>
    
    <section>
@@ -64,11 +64,6 @@
          exposes all functionality provided by the <literal>guestfs</literal> API.
          This tool ships in its own package entitled <package>guestfish</package>.
       </para>
-         <note>
-            <para>
-               Refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle> for more information about <command>guestfish</command>.
-            </para>
-         </note>
       <warning>
          <para>
             Using <command>guestfish</command> on running virtual machines can
@@ -76,6 +71,11 @@
             option if the disk image is being used by a running virtual machine.
          </para>
       </warning>
+          <!--     <note>
+            <para>
+               Refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle> for more information about <command>guestfish</command>.
+            </para>
+         </note>-->
    </section>
    
    
@@ -209,18 +209,16 @@
              <package>libguestfs-tools</package> package.
           </para>
        </listitem>
-      </varlistentry>
-      <!-- wont make 6.2 
+      </varlistentry> 
       <varlistentry>
-       <term><command>virt-p2v</command></term>
+       <term><command>virt-p2v</command></term><!-- confirm with mbooth if it's in Fedora 19.-->
        <listitem>
          <para>
             A graphical tool to convert physical machines into virtual machines.
-            This tool is installed as part of the <package>virt-v2v</package> package
-            in Red Hat Enterprise Linux 6.2 and later.
+            This tool is installed as part of the <package>virt-v2v</package> package.
          </para>
        </listitem>
-     </varlistentry>-->
+     </varlistentry>
       <varlistentry>
        <term><command>virt-rescue</command></term>
        <listitem>
@@ -300,7 +298,7 @@
        <listitem>
           <para>
              A command line utility similar to <command>top</command>, which shows
-             stats related to virtualized domains. This tool ships in its own package:
+             statistics related to virtualized domains. This tool ships in its own package:
              <package>virt-top</package>.
           </para>
        </listitem>
diff --git a/en-US/Virtualization_Getting_Started_Guide.xml~ b/en-US/Virtualization_Getting_Started_Guide.xml~
new file mode 100644
index 0000000..3502de0
--- /dev/null
+++ b/en-US/Virtualization_Getting_Started_Guide.xml~
@@ -0,0 +1,16 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "Virtualization_Getting_Started_Guide.ent">
+%BOOK_ENTITIES;
+]>
+<book status="draft"> 
+	<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="What_Is_It.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Advantages.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Products.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Tools.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+	<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
+
diff --git a/en-US/What_Is_It.xml b/en-US/What_Is_It.xml
index 756e53d..241f354 100644
--- a/en-US/What_Is_It.xml
+++ b/en-US/What_Is_It.xml
@@ -13,7 +13,7 @@
                      <varlistentry><term><emphasis role="strong">Full virtualization</emphasis></term>
                         <listitem>
                               <para>
-                                 Full virtualization uses the hardware features of the processor to provide guests with total abstraction of the underlying physical system. This creates a new virtual system, called a <firstterm>virtual machine</firstterm>, that allows guest operating systems to run without modifications. The guest operating system and any applications on the guest are unaware of their virtualized environment and run normally. Hardware-assisted virtualization is the technique used for full virtualization with KVM (Kernel-based Virtual Machine) in Fedora.
+                                 Full virtualization uses the hardware features of the processor to provide guests with total abstraction of the underlying physical system. This creates a new virtual system, called a <firstterm>virtual machine</firstterm>, that allows guest operating systems to run without modifications. The guest operating system and any applications on the guest virtual machine are unaware of their virtualized environment and run normally. Hardware-assisted virtualization is the technique used for full virtualization with KVM (Kernel-based Virtual Machine) in Fedora.
                               </para>
                         </listitem>
                      </varlistentry>
@@ -32,16 +32,16 @@
                         </listitem>
                      </varlistentry>
                 </variablelist>
-                     <note>
+<!--                     <note> Include once VDAG is published.
 			<para>
-				For more information and detailed instructions on guest installation, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>.
+				For more information and detailed instructions on guest installation, refer to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>.
 			</para>
-                     </note>
+                     </note>-->
 	</section>
         <section id="sec-migration">
         <title>Migration</title>
                   <para>
-                     <firstterm>Migration</firstterm> describes the process of moving a 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.
+                     <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>
@@ -49,7 +49,7 @@
                                     <term><emphasis role="strong">Offline migration</emphasis></term>
                                     <listitem>
                                        <para>
-                                          An offline migration suspends the guest, and 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 used by the guest on the source host is freed.
+                                          An offline migration suspends the guest virtual machine, and then moves an image of the virtual machine's memory to the destination host. The virtual machine is then resumed on the destination host and the memory used by the virtual machine on the source host is freed.
                                        </para>
                                     </listitem>
                               </varlistentry>
@@ -57,7 +57,7 @@
                                     <term><emphasis role="strong">Live migration</emphasis></term>
                                     <listitem>
                                        <para>
-                                          Live migration is the process of migrating an active guest from one physical host to another.
+                                          Live migration is the process of migrating an active virtual machine from one physical host to another.
                                        </para>
                                     </listitem>
                               </varlistentry>
@@ -70,7 +70,7 @@
                                        <term><emphasis role="strong">Load balancing</emphasis></term>
                                           <listitem>
                                                 <para>
-                                                   When a host machine is overloaded, one or many of its virtual machines could be migrated to other hosts.
+                                                   When a host machine is overloaded, one or many of its virtual machines could be migrated to other hosts using live migration.
                                                 </para>
                                           </listitem>
                                     </varlistentry>
@@ -102,11 +102,11 @@
                               <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>
+<!--                              <note>
                                  <para>
-                                    For more information on migration, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
+                                    For more information on migration, refer to the <citetitle>Fedora Virtualization Depolyment and Administration Guide</citetitle>.
                                  </para>
-                              </note>
+                              </note>-->
                      </section>
         </section>
 <!--        <section id="Virtualized_to_virtualized">