release-notes/devel/en_US Virtualization.xml,1.13,1.14

[Paul W. Frields (pfrields)]

Author: pfrields

Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23796

Modified Files:
	Virtualization.xml 
Log Message:
Import diffs from wiki for final release



Index: Virtualization.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Virtualization.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- Virtualization.xml	4 Apr 2007 04:28:34 -0000	1.13
+++ Virtualization.xml	22 Apr 2007 01:54:52 -0000	1.14
@@ -5,39 +5,47 @@
   <title>Virtualization</title>
 
   <para>
-    Virtualization in Fedora 7 is based on Xen 3.0.4 and is integrated
-    within the Fedora installer. Refer to
-    <ulink url='http://fedoraproject.org/wiki/Tools/Xen'>http://fedoraproject.org/wiki/Tools/Xen</ulink>
-    for more information about Xen.
+    Virtualization in Fedora 7 supports both Xen and KVM virtualization
+    platforms.  The <systemitem class="library">libvirt</systemitem> API
+    and its corresponding tools, <package>virt-manager</package> and
+    <command>virsh</command>, have been updated to support both KVM and
+    Xen.  Users can choose which virtualization platform to install, and
+    use the same tools without regard to that choice.
+  </para>
+  <para>Xen in Fedora 7 is based on version 3.0.4.</para>
+  <para>KVM in Fedora 7 is based on version 19-1.</para>
+  <para>
+    For more information on the differences between Xen and KVM, refer
+    to <ulink url="http://virt.kernelnewbies.org/TechComparison"/>.  For
+    more information on installing and using virtualization in Fedora 7,
+    refer to <ulink
+      url='http://fedoraproject.org/wiki/Docs/Fedora7VirtQuickStart'/>.
   </para>
 
   <section id="sn-Types-of-Virtualization">
     <title>Types of Virtualization</title>
     <para>
-      Under Fedora using Xen 3.0.4, both paravirtualization and full
-      virtualization can be implemented. Full virtualization requires a
-      VT-capable processor. Paravirtualization does not require special
-      hardware, but does require the guest OS to be modified. To learn
-      more about how to configure and use Xen, refer to
-      <ulink url='http://fedoraproject.org/wiki/FedoraXenQuickstartFC6'>http://fedoraproject.org/wiki/FedoraXenQuickstartFC6</ulink>.
+      Using Xen 3.0.4, both paravirtualization and full virtualization
+      can be implemented. Under KVM, only full virtualization is
+      supported.  Full virtualization requires a VT-capable processor.
+      Paravirtualization does not require special hardware, but does
+      require the guest OS to be modified.
     </para>
   </section>
 
   <section id="sn-Guest-Operating-Systems">
     <title>Guest Operating Systems</title>
     <para>
-      The Fedora 7 development team has tested Xen with Fedora 7 and Red
-      Hat Enterprise Linux 5 guests. Other guests have not been tested.
-      With paravirtualization, however, users can expect reasonable
-      success running any Linux guest OS that was built for Xen 3.0.4.
-      With full virtualization using VT hardware, users can expect
+      The Fedora 7 development team has tested Xen with Fedora 6, Fedora
+      7 and Red Hat Enterprise Linux 4.5 and 5.0 guests. Other guests
+      have not been tested. With full virtualization, users can expect
       reasonable success with a larger variety of operating systems,
       including some proprietary operating systems.
     </para>
   </section>
 
   <section id="sn-Changes-to-the-Xen-Packages">
-    <title>Changes to the Xen Packages</title>
+    <title>Changes to the Virtualization Packages</title>
     <para>
       The following improvements have been made in the virtualization
       packages in Fedora 7:
@@ -47,13 +55,14 @@
         <para>
           The applications <command>virt-manager</command> and
 	  <command>virsh</command> can now work with inactive domains.
-	  Previously, only <command>xm</command> could handle inactive domains
+	  Previously, only <command>xm</command> could handle inactive
+	  domains.
         </para>
       </listitem>
       <listitem>
 	<para>
 	  The mouse cursor problems with the virtual frame buffer have been
-	  fixed, for a better user experience in GUI modes
+	  fixed, for a better user experience in GUI modes.
 	</para>
       </listitem>
       <listitem>