* [gentoo-doc-cvs] cvs commit: xen-guide.xml
@ 2007-07-20 7:18 swift
0 siblings, 0 replies; 6+ messages in thread
From: swift @ 2007-07-20 7:18 UTC (permalink / raw
To: gentoo-doc-cvs
swift 07/07/20 07:18:24
Added: xen-guide.xml
Log:
Adding Xen draft (bug #105117), still needs work (like the comments on the bug state)
Revision Changes Path
1.1 xml/htdocs/doc/en/draft/xen-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml?rev=1.1&content-type=text/plain
Index: xen-guide.xml
===================================================================
<?xml version='1.0' encoding='UTF-8'?>
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml,v 1.1 2007/07/20 07:18:24 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/draft/xen-guide.xml" disclaimer="draft">
<title>Configuring Gentoo with Xen</title>
<author title="Author">
<mail link="swift@gentoo.org">Sven Vermeulen</mail>
</author>
<abstract>
This guide describes how to start using Xen on your Gentoo system
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
<version>0.1</version>
<date>2007-07-14</date>
<chapter>
<title>Introduction</title>
<section>
<body>
<p>
The <uri link="http://www.xensource.com/">Xen</uri> technology allows you to run
multiple operating systems on a single physical system, govern resource
consumption and even migrate domains (which are the virtual environments in
which a guest operating system runs) from one Xen-powered system to another. Xen
requires the host operating system to support Xen (which, in this case, will be
a Linux kernel) but guest operating systems can run unmodified <e>if</e> your
hardware supports Intel Virtualization Technology (VT-x) or AMD Virtualization
Technology (SVM). Otherwise your guest operating systems must also support Xen.
</p>
<p>
This guide will talk you through the configuration steps necessary to get Xen up
and running on Gentoo Linux. We will not discuss Xen itself (the Xen project has
<uri
link="http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user">decent
documentation</uri> available) nor will we talk about specialized setups that
might be very interesting for Xen setups but are not Xen-related (like exporting
Portage through NFS, booting Linux using PXE, etc.)
</p>
</body>
</section>
</chapter>
<chapter>
<title>Preparing Domain0</title>
<section>
<title>Introduction</title>
<body>
<p>
<e>Domain0</e> is the primary domain under Xen, hosting the host operating
system which governs all other domains. In this chapter we will prepare an
existing Gentoo installation to become the host operating system in this domain
and build the Xen-powered kernel so that Gentoo is ready to host other Xen
domains.
</p>
</body>
</section>
<section>
<title>Rebuilding the Gentoo Installation ?</title>
<body>
<p>
A drastic change that might be necessary is to rebuild the entire Gentoo
installation with a different <c>CFLAGS</c> setting. Guest operating systems
running under Xen might otherwise see major performance degradation. If you,
however, are planning on checking out Xen rather than installing it for
production use and are not terribly fond of rebuilding all programs, you can
skip this step. In this case you will notice performance degradation but you
will still be able to use Xen.
</p>
<impo>
It is advised that, if you change your <c>CFLAGS</c> and build your system with
a gcc lower than version 4, you do not have <c>-Os</c> set as it has been
reported to produce broken code.
</impo>
<pre caption="Editing the CFLAGS and rebuild the Gentoo installation">
~# <i>nano -w /etc/make.conf</i>
<comment>(Add -mno-tls-direct-seg-refs)</comment>
CFLAGS="-O2 -march=pentium4 -pipe -mfpmath=sse <i>-mno-tls-direct-seg-refs</i>"
~# <i>emerge -e world</i>
</pre>
<p>
If you boot your system using an initial ramdisk (initrd) you need to
rebuild the initrd as well (which is best done by running all steps you would do
when you rebuild your kernel).
</p>
</body>
</section>
<section>
<title>Installing Xen</title>
<body>
<p>
Xen actually contains many components, so you'll need to install a couple of
packages. Because it is still <uri
link="/doc/en/handbook/handbook-x86.xml?part=3&chap=3#doc_chap2">~arch
masked</uri> you first need to unmask it by adding the following lines to
<path>/etc/portage/package.keywords</path>:
</p>
<pre caption="Unmasking Xen">
app-emulation/xen
app-emulation/xen-tools
sys-kernel/xen-sources
</pre>
</body>
</section>
<section>
<title>Building the Kernel</title>
<body>
<p>
Next we'll build the Linux kernel with Xen support. This kernel, whose sources
are available at <path>/usr/src/linux-2.6.x.z-xen</path>, will be our main
running kernel (i.e. the one running domain 0). In the <c>XEN</c> section you'll
find drivers for all kinds of input/output, each driver having a <e>backend</e>
and <e>frontend</e> implementation available. For the domain 0 kernel you need
to select the <e>backend</e> implementation: these are used by the other
domains (who use the <e>frontend</e> drivers) to communicate directly with
the hardware.
</p>
<p>
Of course, don't forget to select <c>Xen-compatible</c> at <c>Processor type and
features</c>. If you're wondering about networking: each interface in a domain
has a point-to-point link to an interface on domain 0 (called
<path>vifX.Y</path> where X is the domain number and Y the Yth interface of that
domain), so you can configure your network the way you want (bridging, NAT,
etc.)
</p>
<p>
Once the kernel is built you'll find the kernel image immediately in the kernel
source directory (not inside <path>arch/</path> or any other directory) called
<path>vmlinuz</path>. Copy it to <path>/boot</path> and then configure your
bootloader to use the Xen hypervisor (one of the components installed
previously) which is stored as <path>/boot/xen.gz</path>. In the bootloader
configuration, add your newly built kernel as the kernel that Xen should
boot. For instance, for GRUB:
</p>
<pre caption="GRUB Configuration for Xen">
title Xen 3.0 / Gentoo Linux 2.6.x.y
root (hd0,0)
kernel /xen.gz
module /kernel-2.6.x.y-xen0 root=/dev/hda3
</pre>
<p>
Now reboot your system into Xen. Once you are booted, you need to load the Xen
daemon:
</p>
<pre caption="Loading the Xen daemon">
~# <i>/etc/init.d/xend start</i>
</pre>
<p>
Now check if you can do whatever you normally do on your system. If this is the
case, you can edit your bootloader configuration to always boot into Xen and add
the Xen deamon to the default runlevel so that it is started automatically the
next time you boot.
</p>
</body>
</section>
</chapter>
<chapter>
<title>Creating an Unpriviledged Domain</title>
<section>
<title>Building the Kernel</title>
<body>
<p>
Go to the Xen-powered Linux kernel source and update the configuration. It is
wise to keep as many topics as possible similar to the main kernel except the
<c>XEN</c> settings where drivers should now have their <e>frontend</e>
implementation selected instead of the <e>backend</e>. Then build the kernel
and place the resulting <path>vmlinuz</path> file where you want (we assume this
is <path>/mnt/data/xen/kernel</path>):
</p>
<pre caption="Building the guest kernel">
~# <i>make</i>
~# <i>cp vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen</i>
</pre>
</body>
</section>
<section>
<title>Creating the Domain Disks</title>
<body>
<p>
For best performance, it is best to dedicate a partition (or logical volume) to
a domain rather than a file based filesystem. However, if you are going to use
Xen primarily for tests using a file based filesystem does have its advantages
(especially regarding maintenance).
</p>
<p>
You can create a file based filesystem using <c>dd</c> and <c>mke2fs</c> (or
any other file system creation tool). For instance, to create a 2Gbyte ext3
filesystem:
</p>
<pre caption="Creating a file based filesystem">
~# <i>dd if=/dev/zero of=/mnt/data/xen/disks/ext3root.img bs=1M count=2048</i>
~# <i>mke2fs -j /mnt/data/xen/disks/ext3root.img</i>
</pre>
</body>
</section>
<section>
<title>Configuring a Domain</title>
<body>
<p>
Next we create a Xen configuration file for a domain. You can store these
configuration files where you want, for instance at
<path>/mnt/data/xen/configs</path>. As an example, we create a configuration
file for a small Gentoo environment which uses the disk image we created
previously:
</p>
<pre caption="Creating a domain configuration file">
~# <i>nano -w /mnt/data/xen/configs/gentoo</i>
kernel = "/mnt/data/xen/kernel/kernel-2.6.x.y-xen"
memory = 512
name = "gentoo"
<comment>(Map the disk image to the virtual /dev/sda1)</comment>
disk = ['file:/mnt/data/xen/disks/ext3root.img,sda1,w']
root = "/dev/sda1 ro"
</pre>
</body>
</section>
<section>
<title>Launching the New Domain</title>
<body>
<p>
Now we're all set and we can launch the new domain. If the disk image contained
an operating system, we could just create and attach the domain using the
<c>xm</c> command (Xen manager):
</p>
<pre caption="Creating and starting a new domain">
~# <i>xm create /mnt/data/xen/configs/gentoo -c</i>
</pre>
<p>
The domain would be booted inside the terminal in which you executed the
command. However, in our case, the disk image is empty so the domain wouldn't be
able to do much. To fix this, you can loop-mount the image and install Gentoo as
you're used to.
</p>
<p>
If you want to disconnect from the domain, press <path>Ctrl+]</path>. You can
always reconnect to the domains' console using <c>xm console gentoo</c>.
However, there is only one console per domain, so only use it when you can't
access the domain otherwise (for instance, through SSH).
</p>
</body>
</section>
</chapter>
<chapter>
<title>Networking on Unpriviledged Domains</title>
<section>
<title>Introduction</title>
<body>
<p>
Xen supports at least two ways of configuring your (virtual) network:
<e>routed</e> and <e>bridged</e>.
</p>
<p>
When selecting the <e>routed</e> approach, the interface inside your
unpriviledged domain is connected to a virtual interface on your
administrative domain. On your administrative domain (domain 0), the virtual
interface has the same IP address as <path>eth0</path> whereas the
interface inside your unpriviledged domain has an IP address on the same
network. Any communication to that IP address can only occur from the
administrative domain, unless you set up specific routing rules.
</p>
<p>
When selecting the <e>bridged</e> approach, <brite>TODO</brite>.
</p>
</body>
</section>
<section>
<title>Regular Routed Interfaces</title>
<body>
<p>
Before you set up the interface on your unpriviledged domain, make sure that
Xen's <path>netloop</path> and <path>netbk</path> drivers are loaded. A quick
hint: if you have <path>netloop</path> as a module, load it with
<c>nloopbacks=0</c> so that it doesn't create pointless interfaces to the
loopback device. Then, edit your domain configuration file and add a <c>vif</c>
instruction to it.
</p>
<pre caption="Configuring a virtual interface">
~# <i>nano -w /mnt/data/xen/configs/gentoo</i>
<comment>(Add the vif instruction)</comment>
vif = [ 'ip=192.168.1.101, vifname=veth1' ]
</pre>
<p>
In the above example, the interface will be created for the unpriviledged domain
(in which it will be called <path>eth0</path>) and Xen will link the address
192.168.1.101 with the domain 0 <path>eth0</path> interface through interface
<path>veth1</path>. That doesn't mean that the virtual <path>eth0</path>
interface will automatically have IP 192.168.1.101 assigned to it, but rather
that, if you don't give it that IP, it will not be connected with the
administrative domain and thus cannot be reached.
</p>
<p>
Now edit <path>/etc/xen/xend-config.xsp</path> as follows to select routed
network configuration:
</p>
<pre caption="Editing xend-config.xsp">
~# <i>nano -w /etc/xen/xend-config.xsp</i>
<comment>(Comment out the following lines)</comment>
<i>#</i>(network-script network-bridge)
<i>#</i>(vif-script vif-bridge)
<comment>(Enable the following lines)</comment>
(network-script network-route)
(vif-script vif-route)
</pre>
</body>
</section>
</chapter>
</guide>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gentoo-doc-cvs] cvs commit: xen-guide.xml
@ 2007-07-25 19:14 swift
0 siblings, 0 replies; 6+ messages in thread
From: swift @ 2007-07-25 19:14 UTC (permalink / raw
To: gentoo-doc-cvs
swift 07/07/25 19:14:01
Modified: xen-guide.xml
Log:
Updates and patch from bug #105117
Revision Changes Path
1.2 xml/htdocs/doc/en/draft/xen-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml?r1=1.1&r2=1.2
Index: xen-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xen-guide.xml 20 Jul 2007 07:18:24 -0000 1.1
+++ xen-guide.xml 25 Jul 2007 19:14:01 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml,v 1.1 2007/07/20 07:18:24 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/xen-guide.xml,v 1.2 2007/07/25 19:14:01 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -20,7 +20,7 @@
<license/>
<version>0.1</version>
-<date>2007-07-14</date>
+<date>2007-07-24</date>
<chapter>
<title>Introduction</title>
@@ -90,7 +90,7 @@
<pre caption="Editing the CFLAGS and rebuild the Gentoo installation">
~# <i>nano -w /etc/make.conf</i>
<comment>(Add -mno-tls-direct-seg-refs)</comment>
-CFLAGS="-O2 -march=pentium4 -pipe -mfpmath=sse <i>-mno-tls-direct-seg-refs</i>"
+CFLAGS="-O2 -march=pentium4 -pipe <i>-mno-tls-direct-seg-refs</i>"
~# <i>emerge -e world</i>
</pre>
@@ -111,16 +111,21 @@
Xen actually contains many components, so you'll need to install a couple of
packages. Because it is still <uri
link="/doc/en/handbook/handbook-x86.xml?part=3&chap=3#doc_chap2">~arch
-masked</uri> you first need to unmask it by adding the following lines to
-<path>/etc/portage/package.keywords</path>:
+masked</uri> you first need to unmask it by adding the necessary lines to
+<path>/etc/portage/package.keywords</path> and then install them.
</p>
-<pre caption="Unmasking Xen">
+<pre caption="Unmasking and Installing Xen">
+~# <i>nano -w /etc/portage/package.keywords</i>
app-emulation/xen
app-emulation/xen-tools
sys-kernel/xen-sources
+
+~# <i>emerge xen xen-tools xen-sources</i>
</pre>
+
+
</body>
</section>
<section>
@@ -147,9 +152,73 @@
etc.)
</p>
+<pre caption="Enabling Xen Support for i386 Kernels">
+Processor type and features --->
+ Subarchitecture Type (Xen-compatible)
+</pre>
+
+<pre caption="Enabling Xen Support for x86_64 Kernels">
+Processor type and features --->
+ Subarchitecture Type (PC-compatible)
+ [*] Enable Xen compatible kernel
+</pre>
+
+<pre caption="Domain-0 Kernel Config">
+Bus options (PCI etc.) --->
+ [*] PCI support
+ [*] Xen PCI Frontend (NEW)
+ [ ] Xen PCI Frontend Debugging
+
+Networking --->
+ Networking options --->
+ <*> 802.1d Ethernet Bridging
+ <comment>Only required by bridged networking.</comment>
+
+XEN --->
+ [*] Privileged Guest (domain 0)
+ <*> Backend driver support
+ <*> Block-device backend driver
+ <*> Network-device backend driver
+ [*] Scrub memory before freeing it to Xen
+ [*] Disable serial port drivers
+ Xen version compatibility (3.0.4 and later)
+</pre>
+
+<pre caption="Domain-U Kernel Config">
+Bus options (PCI etc.) --->
+ [ ] PCI support
+
+Device Drivers --->
+ SCSI device support --->
+ < > SCSI device support
+ <comment>Disabling SCSI support frees up the /dev/sd* device names
+ for use as Xen virtual block devices.</comment>
+
+XEN --->
+ [ ] Privileged Guest (domain 0)
+ <*> Block-device frontend driver
+ <*> Network-device frontend driver
+ [*] Scrub memory before freeing it to Xen
+ [*] Disable serial port drivers
+ Xen version compatibility (3.0.4 and later)
+</pre>
+
<p>
-Once the kernel is built you'll find the kernel image immediately in the kernel
-source directory (not inside <path>arch/</path> or any other directory) called
+A nice hint is to have the kernel make process store its intermediate object
+files elsewhere so that you can reuse the same kernel tree to build different
+configurations:
+</p>
+
+<pre caption="Building the Kernel">
+~# <i>mkdir -p ~/build/dom0 ~/build/domU</i>
+~# <i>make O=~/build/dom0 menuconfig</i>
+<comment>(Configure the kernel)</comment>
+~# <i>make O=~/build/dom0 && make O=~/build/dom0 modules_install</i>
+</pre>
+
+<p>
+Once the kernel is built you'll find the kernel image immediately in the
+build directory (not inside <path>arch/</path> or any other directory) called
<path>vmlinuz</path>. Copy it to <path>/boot</path> and then configure your
bootloader to use the Xen hypervisor (one of the components installed
previously) which is stored as <path>/boot/xen.gz</path>. In the bootloader
@@ -160,8 +229,8 @@
<pre caption="GRUB Configuration for Xen">
title Xen 3.0 / Gentoo Linux 2.6.x.y
root (hd0,0)
-kernel /xen.gz
-module /kernel-2.6.x.y-xen0 root=/dev/hda3
+kernel /boot/xen.gz
+module /boot/kernel-2.6.x.y-xen0 root=/dev/hda3
</pre>
<p>
@@ -176,7 +245,7 @@
<p>
Now check if you can do whatever you normally do on your system. If this is the
case, you can edit your bootloader configuration to always boot into Xen and add
-the Xen deamon to the default runlevel so that it is started automatically the
+the Xen deamon to the default runlevel so that it is started automatically
next time you boot.
</p>
@@ -199,10 +268,16 @@
</p>
<pre caption="Building the guest kernel">
-~# <i>make</i>
-~# <i>cp vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen</i>
+~# <i>make O=~/build/domU</i>
+~# <i>cp ~/build/vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen</i>
</pre>
+<p>
+It is also possible to create a single kernel image for both the administrative
+domain and the unpriviledged domain. More information about this can be found
+in the Xen user manual.
+</p>
+
</body>
</section>
<section>
@@ -252,6 +327,10 @@
root = "/dev/sda1 ro"
</pre>
+<p>
+You can find example configuration files in <path>/etc/xen</path>.
+</p>
+
</body>
</section>
<section>
@@ -298,12 +377,13 @@
<p>
When selecting the <e>routed</e> approach, the interface inside your
-unpriviledged domain is connected to a virtual interface on your
+unpriviledged domain is connected to the virtual interface on your
administrative domain. On your administrative domain (domain 0), the virtual
-interface has the same IP address as <path>eth0</path> whereas the
-interface inside your unpriviledged domain has an IP address on the same
-network. Any communication to that IP address can only occur from the
-administrative domain, unless you set up specific routing rules.
+interface is linked together with <path>eth0</path>. The
+interface inside your unpriviledged domain should have an IP address on the same
+network as the interface on the administrative domain. Any communication to
+that IP address can only occur from the administrative domain, unless you set
+up specific routing rules.
</p>
<p>
@@ -334,12 +414,16 @@
<p>
In the above example, the interface will be created for the unpriviledged domain
-(in which it will be called <path>eth0</path>) and Xen will link the address
-192.168.1.101 with the domain 0 <path>eth0</path> interface through interface
-<path>veth1</path>. That doesn't mean that the virtual <path>eth0</path>
-interface will automatically have IP 192.168.1.101 assigned to it, but rather
-that, if you don't give it that IP, it will not be connected with the
-administrative domain and thus cannot be reached.
+(in which it will be called <path>eth0</path>) and Xen will ensure that address
+192.168.1.101 will be reachable from the administrative domain through interface
+<path>veth1</path>.
+</p>
+
+<p>
+This doesn't mean that the virtual <path>eth0</path> interface will
+automatically have IP 192.168.1.101 assigned to it, but rather that, if you
+don't give it that IP, it will not be connected with the administrative domain
+and thus cannot be reached.
</p>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gentoo-doc-cvs] cvs commit: xen-guide.xml
@ 2007-09-13 17:09 Sven Vermeulen
0 siblings, 0 replies; 6+ messages in thread
From: Sven Vermeulen @ 2007-09-13 17:09 UTC (permalink / raw
To: gentoo-doc-cvs
swift 07/09/13 17:09:06
Modified: xen-guide.xml
Log:
Fix #190689 - Add resources for Xen
Revision Changes Path
1.2 xml/htdocs/doc/en/xen-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?r1=1.1&r2=1.2
Index: xen-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xen-guide.xml 29 Aug 2007 18:46:34 -0000 1.1
+++ xen-guide.xml 13 Sep 2007 17:09:06 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.1 2007/08/29 18:46:34 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.2 2007/09/13 17:09:06 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -19,8 +19,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.0</version>
-<date>2007-08-29</date>
+<version>1.1</version>
+<date>2007-09-13</date>
<chapter>
<title>Introduction</title>
@@ -533,4 +533,41 @@
</body>
</section>
</chapter>
+<chapter>
+<title>Further Resources</title>
+<section>
+<title>Xen Documentation</title>
+<body>
+
+<ul>
+ <li>
+ <uri link="http://tx.downloads.xensource.com/downloads/docs/user/">Xen
+ Users' Manual</uri>
+ </li>
+ <li>
+ <uri link="http://xen.xensource.com/documentation.html">Xen Community
+ Documentation</uri>
+ </li>
+ <li>
+ <uri link="http://wiki.xensource.com/xenwiki/">Xen Wiki</uri>
+ </li>
+</ul>
+
+</body>
+</section>
+<section>
+<title>Xen Tools</title>
+<body>
+
+<ul>
+ <li>
+ <uri
+ link="http://virt-manager.et.redhat.com/">app-emulation/virt-manager</uri>
+ is a graphical tool for administering virtual machines
+ </li>
+</ul>
+
+</body>
+</section>
+</chapter>
</guide>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gentoo-doc-cvs] cvs commit: xen-guide.xml
@ 2007-12-10 15:37 Sven Vermeulen
0 siblings, 0 replies; 6+ messages in thread
From: Sven Vermeulen @ 2007-12-10 15:37 UTC (permalink / raw
To: gentoo-doc-cvs
swift 07/12/10 15:37:10
Modified: xen-guide.xml
Log:
Update to kernel config, thx to Pierre (coldev.org)
Revision Changes Path
1.3 xml/htdocs/doc/en/xen-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?r1=1.2&r2=1.3
Index: xen-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xen-guide.xml 13 Sep 2007 17:09:06 -0000 1.2
+++ xen-guide.xml 10 Dec 2007 15:37:10 -0000 1.3
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.2 2007/09/13 17:09:06 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.3 2007/12/10 15:37:10 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -19,8 +19,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.1</version>
-<date>2007-09-13</date>
+<version>1.2</version>
+<date>2007-12-10</date>
<chapter>
<title>Introduction</title>
@@ -166,8 +166,7 @@
<pre caption="Domain-0 Kernel Config">
Bus options (PCI etc.) --->
[*] PCI support
- [*] Xen PCI Frontend (NEW)
- [ ] Xen PCI Frontend Debugging
+ [ ] Xen PCI Frontend Debugging
Networking --->
Networking options --->
@@ -179,6 +178,8 @@
<*> Backend driver support
<*> Block-device backend driver
<*> Network-device backend driver
+ <*> PCI-device backend driver
+ PCI Backend Mode (Virtual PCI) --->
[*] Scrub memory before freeing it to Xen
[*] Disable serial port drivers
Xen version compatibility (3.0.4 and later)
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gentoo-doc-cvs] cvs commit: xen-guide.xml
@ 2008-04-10 15:01 Camille Huot
0 siblings, 0 replies; 6+ messages in thread
From: Camille Huot @ 2008-04-10 15:01 UTC (permalink / raw
To: gentoo-doc-cvs
cam 08/04/10 15:01:50
Modified: xen-guide.xml
Log:
Fixed domU vmlinuz path
Revision Changes Path
1.4 xml/htdocs/doc/en/xen-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?r1=1.3&r2=1.4
Index: xen-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- xen-guide.xml 10 Dec 2007 15:37:10 -0000 1.3
+++ xen-guide.xml 10 Apr 2008 15:01:50 -0000 1.4
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.3 2007/12/10 15:37:10 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.4 2008/04/10 15:01:50 cam Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -19,8 +19,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.2</version>
-<date>2007-12-10</date>
+<version>1.3</version>
+<date>2008-04-10</date>
<chapter>
<title>Introduction</title>
@@ -277,7 +277,7 @@
<pre caption="Building the guest kernel">
~# <i>make O=~/build/domU</i>
-~# <i>cp ~/build/vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen</i>
+~# <i>cp ~/build/domU/vmlinuz /mnt/data/xen/kernel/kernel-2.6.x.y-xen</i>
</pre>
<p>
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gentoo-doc-cvs] cvs commit: xen-guide.xml
@ 2008-08-11 16:25 Sven Vermeulen
0 siblings, 0 replies; 6+ messages in thread
From: Sven Vermeulen @ 2008-08-11 16:25 UTC (permalink / raw
To: gentoo-doc-cvs
swift 08/08/11 16:25:22
Modified: xen-guide.xml
Log:
SXP, not XSP extension
Revision Changes Path
1.5 xml/htdocs/doc/en/xen-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.5&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?rev=1.5&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/xen-guide.xml?r1=1.4&r2=1.5
Index: xen-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- xen-guide.xml 10 Apr 2008 15:01:50 -0000 1.4
+++ xen-guide.xml 11 Aug 2008 16:25:22 -0000 1.5
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.4 2008/04/10 15:01:50 cam Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/xen-guide.xml,v 1.5 2008/08/11 16:25:22 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -19,8 +19,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.3</version>
-<date>2008-04-10</date>
+<version>1.4</version>
+<date>2008-08-11</date>
<chapter>
<title>Introduction</title>
@@ -450,12 +450,12 @@
</p>
<p>
-Now edit <path>/etc/xen/xend-config.xsp</path> as follows to select routed
+Now edit <path>/etc/xen/xend-config.sxp</path> as follows to select routed
network configuration:
</p>
-<pre caption="Editing xend-config.xsp">
-~# <i>nano -w /etc/xen/xend-config.xsp</i>
+<pre caption="Editing xend-config.sxp">
+~# <i>nano -w /etc/xen/xend-config.sxp</i>
<comment>(Comment out the following lines)</comment>
<i>#</i>(network-script network-bridge)
@@ -492,12 +492,12 @@
</pre>
<p>
-Next edit <path>/etc/xen/xend-config.xsp</path> as follows to select bridged
+Next edit <path>/etc/xen/xend-config.sxp</path> as follows to select bridged
network configuration:
</p>
-<pre caption="Editing xend-config.xsp">
-~# <i>nano -w /etc/xen/xend-config.xsp</i>
+<pre caption="Editing xend-config.sxp">
+~# <i>nano -w /etc/xen/xend-config.sxp</i>
<comment>(Enable the following lines)</comment>
(network-script network-bridge)
@@ -512,11 +512,11 @@
By default, the bridge will contain whatever interface is configured to be the
default interface (the device that is listed under the default route through
<c>ip route list</c>). If you want to alter this behavior, edit the
-<path>xend-config.xsp</path> as follows:
+<path>xend-config.sxp</path> as follows:
</p>
-<pre caption="Editing xend-config.xsp to change bridge configuration">
-~# <i>nano -w /etc/xen/xend-config.xsp</i>
+<pre caption="Editing xend-config.sxp to change bridge configuration">
+~# <i>nano -w /etc/xen/xend-config.sxp</i>
<comment>(Edit the network-script line)</comment>
(network-script <i>'</i>network-bridge <i>netdev=eth0 bridge=xenbr0 vifnum=0'</i>)
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2008-08-11 16:25 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-10 15:37 [gentoo-doc-cvs] cvs commit: xen-guide.xml Sven Vermeulen
-- strict thread matches above, loose matches on Subject: below --
2008-08-11 16:25 Sven Vermeulen
2008-04-10 15:01 Camille Huot
2007-09-13 17:09 Sven Vermeulen
2007-07-25 19:14 swift
2007-07-20 7:18 swift
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox