added information about boxes in the products.xml file

2 files changed, 160 insertions, 135 deletions

diff --git a/en-US/Products.xml b/en-US/Products.xml
index 1d0178d..bbc299f 100644
--- a/en-US/Products.xml
+++ b/en-US/Products.xml
@@ -120,7 +120,7 @@
 		</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. <application>libvirt</application> is the the foundation of the Gnome application: <application>gnome-boxes</application> is built apon.
         </para>
         <para>
            Fedora supports <application>libvirt</application> and included <application>libvirt</application>-based tools as its default method for virtualization management.
@@ -561,8 +561,26 @@
             </note>
 
             </section>
-</section>      
+</section> 
 <section>
+<title>Boxes</title>
+<para>
+<application>Boxes</application> A simple GNOME 3 application to access local and remote virtual systems.
+</para>
+	<para>
+	Features:
+	</para>
+	<itemizedlist>
+		<listitem><para>View, access, and use: remote machines, remote and local virtual machines, and access for applications on virtual machines </para></listitem>
+<listitem><para>View, access, and use: remote machines, remote and local virtual machines, and access for applications on virtual machines </para></listitem>
+		<listitem><para>View, access, and use virtual machines on removable media </para></listitem>
+		<listitem><para>View, access, and use shared connection / machines </para></listitem>
+		<listitem><para>Upload / publish virtual machines </para></listitem>
+		<listitem><para>Select favorites </para></listitem>		
+		<listitem><para>Search for connections </para></listitem>
+		</itemizedlist>
+</section> 
+<section>		
                 <title>Storage</title>
                         <para>
                            Storage for virtual machines is abstracted from the physical storage used by the virtual machine. It is attached to the virtual machine using the para-virtualized or emulated block device drivers.
diff --git a/en-US/Products.xml~ b/en-US/Products.xml~
index 79aa32c..5927ecd 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 Deployment and 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 Deployment and Administration Guide</citetitle>.-->
                                        </para>
                                  </important>        
                         </listitem>
@@ -47,18 +47,33 @@
                                  <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>
+                                       <para>
+                                             For more information on KSM, refer to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>.
+                                       </para>
+                                 </note>
+                        </listitem>
+               </varlistentry>
+               <varlistentry><!--Added to RHEL 6.4, adding for F19-->
+                        <term>QEMU guest agent</term>
+                        <listitem>
                                  <para>
-                                       For more information on KSM, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
+                                       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> 
+                                       <para>
+                                             For more information on the QEMU guest agent, refer to the <citetitle>Fedora Virtualization Deployment and Administration 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>
-         <!--<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 +120,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. <application>libvirt</application> is the the foundation of the Gnome application: <application>gnome-boxes</application> is built apon.
         </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&nbsp;5, and it supports KVM on both Red Hat Enterprise Linux&nbsp;5 and Red Hat Enterprise Linux&nbsp;6.-->
@@ -133,7 +148,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 Deployment and Administration Guide</citetitle>.
                      </para>
                   </note>
 </section>
@@ -141,11 +156,12 @@
             <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>
                               <para>
-                                 Virtualized and emulated software devices <!--(was: Emulated software devices - is this correct? hardware/software?)-->
+                                 Virtualized and emulated devices
                               </para>
                      </listitem>
                      <listitem>
@@ -213,30 +229,30 @@
                                                    <para>PS/2 mouse and keyboard</para>
                                           </listitem>
                                           <listitem>
-                                                   <para>EvTouch USB Graphics Tablet</para>
+                                                   <para>EvTouch USB graphics tablet</para>
                                           </listitem>
                                           <listitem>
                                                    <para>PCI UHCI USB controller and a virtualized USB hub</para>
                                           </listitem>
-                                          <!-- removed to fix BZ798106 <listitem>
-                                                   <para>PCI network adapters</para>
-                                          </listitem>-->
                                           <listitem>
                                                    <para>Emulated serial ports</para>
                                           </listitem>
                                           <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>
-<!--                           <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&nbsp;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 - 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>
+                                    <!--<itemizedlist>
                                           <listitem>
                                              <para>
                                                 Red Hat Enterprise Linux 6, for i386 and x86_64 architectures
@@ -262,7 +278,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 +291,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&nbsp;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&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. 
@@ -291,20 +308,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&nbsp;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&nbsp;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&nbsp;6.2 and above.
-                                    </para>
+                                    </para>-->
                               </listitem>
-                           </varlistentry>-->
+                           </varlistentry>
                            <varlistentry>
                               <term>Emulated network devices</term>
                               <listitem>
@@ -358,17 +375,19 @@
                               Para-virtualized devices are drivers for virtual devices that increase the I/O performance of virtual machines. 
                         </para>
                         <para>
-                              Para-virtualized devices decrease I/O latency and increase I/O throughput to near bare-metal levels. It is recommended to use the para-virtualized drivers for virtual machines running I/O intensive applications.
-                        </para>
-                        <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-virtualized devices decrease I/O latency and increase I/O throughput to near bare-metal levels. It is recommended to use the para-virtualized device drivers for virtual machines running I/O intensive applications.
                         </para>
                         <para>
-                           For more information on using the para-virtualized drivers, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>.
+                           The para-virtualized devices must be installed on the guest operating system. The para-virtualized device drivers must be manually installed on Windows guests.
                         </para>
+                        <note>
+                              <para>
+                                 For more information on using the para-virtualized drivers, refer to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>.
+                              </para>
+                        </note>
                         <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 +395,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).
@@ -384,7 +403,15 @@
                               </listitem>
                            </varlistentry>
                            <varlistentry>
-                              <term>>The para-virtualized clock</term>
+                              <term>The para-virtualized controller device (virtio-scsi)</term>
+                              <listitem>
+                                    <para>
+                                      The para-virtualized SCSI controller device provides a more flexible and scalable alternative to virtio-blk. A virtio-scsi guest is capable of inheriting the feature set of the target device, and can handle hundreds of devices compared to virtio-blk, which can only handle 28 devices.
+                                    </para>
+                              </listitem>
+                           </varlistentry>
+                           <varlistentry>
+                              <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 +419,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,13 +427,21 @@
                               </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.
                                     </para>
                              </listitem>
                            </varlistentry>
+                           <varlistentry>
+                              <term>The para-virtualized random number generator (virtio-rng)</term>
+                              <listitem>
+                                    <para>
+                                          The para-virtualized random number generator enables virtual machines to collect entropy, or randomness, directly from the host to use for encrypted data and security. Virtual machines can often be starved of entropy because typical inputs (such as hardware usage) are unavailable. Sourcing entropy can be time-consuming; virtio-rng makes this process faster by injecting entropy directly into guest virtual machines from the host.
+                                    </para>
+                             </listitem>
+                           </varlistentry>
                         </variablelist>                         
                 </section>
                 <section>
@@ -419,33 +454,33 @@
                               <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.
                                     </para>
                                        <note>
                                           <para>
-                                             For more information on device assignment, refer to the <citetitle>Fedora Virtualization Deployment Guide</citetitle>.
+                                             For more information on device assignment, refer to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>.
                                           </para>
                                        </note> 
                               </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.
                                     </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>
-                              <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. 
@@ -453,15 +488,15 @@
                                     <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>.
+                                             For more information on SR-IOV, refer to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>.
                                           </para>
                                        </note>
                               </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).
@@ -469,19 +504,40 @@
                                     <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>
  
 </section>
 <section id="para-CPU_Models">
-        <title>Guest CPU models</title>
-         <para>t
+        <title>CPU models</title>
+         <para>
+            CPU models define which host CPU features are available to
+               the guest operating system. <application>qemu-kvm</application>
+               and <application>libvirt</application> contain definitions for a
+               number of current processor models, allowing users to enable 
+               features that are available only in newer CPU models.
+               The CPU feature set available to guests depends on
+               support in the host CPU kernel. The <application>qemu-kvm</application>
+               code must also allow the feature to be enabled.
+            </para>
+            <para>
+               To safely migrate virtual machines between hosts with different CPU
+               feature sets, <application>qemu-kvm</application> does not expose all CPU features
+               from the host CPU to guest operating systems by default. Instead, CPU features are 
+               exposed to virtual machines based on the chosen CPU model. 
+            </para>
+            <para>
+               It is also possible to enable or disable specific CPU features in a virtual machine's
+               XML configuration. However, it is safer to use predefined CPU models, as incorrect
+               configuration can cause compatibility issues with the guest operating system.
+            </para>
+         <!--   WAS:
             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 
@@ -496,84 +552,35 @@
             with configuration file based CPU model definitions. Definitions for a number 
             of current processor models are now included by default, allowing users to specify 
             features more accurately and migrate more safely.
-         </para>
-
-         <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>-->
+         </para>-->
+            <note>
+               <para>
+                  For more information on CPU model availability and configuration, refer 
+                  to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>.
+               </para>
+            </note>
 
             </section>
-</section>      
+</section> 
 <section>
+<title>Boxes</title>
+<para>
+<application>Boxes</application> A simple GNOME 3 application to access remote or virtual systems.
+</para>
+	<para>
+	Features:
+	</para>
+	<itemizedlist>
+		<listitem><para>View, access, and use: remote machines, remote and local virtual machines, and access for applications on virtual machines </para></listitem>
+<listitem><para>View, access, and use: remote machines, remote and local virtual machines, and access for applications on virtual machines </para></listitem>
+		<listitem><para>View, access, and use virtual machines on removable media </para></listitem>
+		<listitem><para>View, access, and use shared connection / machines </para></listitem>
+		<listitem><para>Upload / publish virtual machines </para></listitem>
+		<listitem><para>Select favorites </para></listitem>		
+		<listitem><para>Search for connections </para></listitem>
+		</itemizedlist>
+</section> 
+<section>		
                 <title>Storage</title>
                         <para>
                            Storage for virtual machines is abstracted from the physical storage used by the virtual machine. It is attached to the virtual machine using the para-virtualized or emulated block device drivers.
@@ -581,7 +588,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>
@@ -596,21 +603,21 @@ 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>
-                        </variablelist>                           
+                        </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 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>
                <para>
-                  For more information on storage and virtualization, refer to the <citetitle>Fedora Virtualization Administration Guide</citetitle>.
+                  For more information on storage and virtualization, refer to the <citetitle>Fedora Virtualization Deployment and Administration Guide</citetitle>.
                </para>
             </note>
         </section>