release-notes/devel/en_US Virtualization.xml,1.18,1.19
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Sat Sep 15 17:49:24 UTC 2007
Author: pfrields
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17596
Modified Files:
Virtualization.xml
Log Message:
Import changes from wiki for F8
Index: Virtualization.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Virtualization.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- Virtualization.xml 22 Jun 2007 02:14:14 -0000 1.18
+++ Virtualization.xml 15 Sep 2007 17:49:22 -0000 1.19
@@ -13,109 +13,64 @@
</tip>
<para>
- Virtualization in Fedora 7 supports both Xen and KVM virtualization
+ Virtualization in Fedora 8 supports both Xen and KVM virtualization
platforms. The <systemitem class="library">libvirt</systemitem> API
and its corresponding tools, <application>virt-manager</application>
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.1.0.</para>
- <para>KVM in Fedora 7 is based on version 19-1.</para>
+ <para>Xen in Fedora 8 is based on version 3.1.0.</para>
+ <para>KVM in Fedora 8 is based on version 36-2.</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,
+ more information on installing and using virtualization in Fedora 8,
refer to <ulink
- url='http://fedoraproject.org/wiki/Docs/Fedora7VirtQuickStart'/>.
+ url='http://fedoraproject.org/wiki/Docs/Fedora8VirtQuickStart'/>.
</para>
- <section id="sn-Types-of-Virtualization">
- <title>Types of Virtualization</title>
- <para>
- 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 Core 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 Virtualization Packages</title>
<para>
The following improvements have been made in the virtualization
- packages in Fedora 7:
+ packages in Fedora 8:
</para>
<itemizedlist>
<listitem>
<para>
- The applications <application>virt-manager</application> and
- <command>virsh</command> can now work with inactive domains.
- Previously, only <command>xm</command> could handle inactive
- domains.
+ Secure remote management of guest domains. Features include:
+ <itemizedlist>
+ <listitem>
+ <para>Secure remote management of guest VM lifecycle</para>
+ </listitem>
+ <listitem>
+ <para>Secure remote access to the guest virtual consoles</para>
+ </listitem>
+ <listitem>
+ <para>For more information on secure remote management,
+ refer to <ulink
+ url="http://fedoraproject.org/wiki/Releases/FeatureVirtSecurity">http://fedoraproject.org/wiki/Releases/FeatureVirtSecurity</ulink>.</para>
+ </listitem>
+ </itemizedlist>
</para>
</listitem>
<listitem>
- <para>
- The mouse cursor problems with the virtual frame buffer have been
- fixed, for a better user experience in GUI modes.
- </para>
- </listitem>
- <listitem>
- <para>
- Miscellaneous other small improvements and fixes have been made.
- </para>
- </listitem>
- <listitem>
- <para>32-bit paravirtualized guests can run on a 64-bit
- hypervisor.</para>
- </listitem>
- <listitem>
- <para>Fully virtualized guests support save, restore, and
- migration.</para>
- </listitem>
- <listitem>
- <para>When migrating guests, the guest config is saved on
- the destinaton host.</para>
- </listitem>
- <listitem>
- <para>The Xen <command>network-bridge</command> script does not
- use the <systemitem>netloop</systemitem> kernel module
- anymore. The default bridge device is now called
- <systemitem>eth0</systemitem> instead of
- <systemitem>xenbr0</systemitem>. The physical device is still
- renamed to <systemitem>peth0</systemitem>.</para>
- </listitem>
- <listitem>
- <para>The <application>virt-manager</application> utility
- provides a virtual network enabling NAT for guests on laptops,
- instead of the Xen <command>network-bridge</command> script.
- </para>
- </listitem>
- <listitem>
- <para>The <application>virt-manager</application> utility is
- translated into more languages.</para>
+ <para>Introduction of <application>Virt Viewer</application>, a
+ lightweight, minimal UI for interacting with the graphical
+ console of virtual machines. <application>Virt
+ Viewer</application> serves as a replacement for
+ <command>vncviewer</command>.</para>
</listitem>
<listitem>
- <para>The <application>virt-manager</application> can add and
- remove disks and interfaces to existing guests.</para>
+ <para>The <systemitem class="library">LibVNCServer</systemitem>
+ implementation has been removed from Xen and replaced with
+ <application>QEMU</application>.</para>
</listitem>
<listitem>
- <para>The <application>virt-manager</application> utility
- provides progress feedback when downloading images, creating
- disks, and starting guests.</para>
+ <para>Introduction of GTK-VNC, a GTK widget which provides a VNC
+ client. For more information on GTK-VNC refer to <ulink
+ url="http://gtk-vnc.sourceforge.net/">http://gtk-vnc.sourceforge.net/</ulink>.</para>
</listitem>
</itemizedlist>
</section>
More information about the docs-commits
mailing list