Attachment 102579 Details for Bug 105177 – xen.xml.patch

[patch] xen.xml.patch

xen.xml.patch (text/plain), 7.86 KB, created by nm (RETIRED) on 2006-11-22 16:15:53 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: nm (RETIRED)

Created: 2006-11-22 16:15:53 UTC

Size: 7.86 KB

patch

obsolete

>--- xen.xml.orig	2006-11-22 00:05:02.000000000 -0800
>+++ xen.xml	2006-11-22 16:09:41.000000000 -0800
>@@ -27,8 +27,8 @@
> <body>
> 
> <impo>
>-This guide is currently x86-centric as that's the platform I've set up the Xen
>-on. It'd be great if someone adds notes about using Xen on different platforms.
>+This guide is focused on installing Xen on x86 processors. While Xen is
>+supported on other architectures, this guide does not yet cover them.
> </impo>
> 
> 
>@@ -38,31 +38,37 @@
> 
> <dl>
> <dt>Domain</dt>
>- <dd>An instance of your "virtual computer", running its own kernel and user
>- level applications</dd>
>+ <dd>
>+ An instance of your "virtual computer", running its own kernel and user
>+ level applications
>+ </dd>
> <dt>Dom0</dt>
>- <dd>The "primary" domain that is running all the time and is usually
>- responsible for things like setting up another domains and other management
>- tasks. It's "automatically" launched by the Xen hypervisor during the boot
>- process. When the dom0 exists, Xen by default reboots the machine.
>- </dd>
>+ <dd>
>+ The "primary" domain that is running all the time and is usually
>+ responsible for things like setting up another domains and other
>+ management tasks. It's "automatically" launched by the Xen hypervisor
>+ during the boot process. When the dom0 exists, Xen by default reboots the
>+ machine.
>+ </dd>
> <dt>DomU</dt>
>- <dd>"Regular" instances of the unprivileged virtual machines. Each of them can
>- be running different kernel version with wildly differing userspace
>- environment, even another operating system.
>- </dd>
>+ <dd>
>+ "Regular" instances of the unprivileged virtual machines. Each of them can
>+ be running a different kernel version with a wildly differing userspace
>+ environment, or even another operating system.
>+ </dd>
> <dt>Hypervisor</dt>
>- <dd>A Xen-supplied software that runs at the "bare metal" of your computer and
>- is responsible for low-level tasks like CPU scheduling, memory management and
>- dom0 launching upon boot.
>- </dd>
>+ <dd>
>+ A Xen-supplied software that runs at the "bare metal" of your computer and
>+ is responsible for low-level tasks like CPU scheduling, memory management
>+ and dom0 launching upon boot.
>+ </dd>
> </dl>
> 
> 
> Xen comes with extensive <uri
>-link="http://www.cl.cam.ac.uk/research/srg/netos/xen/documentation.html">documetnation</uri>.
>+link="http://www.cl.cam.ac.uk/research/srg/netos/xen/documentation.html">documentation</uri>.
> It's a good idea to read through it to get familiar with its internal structure
>-as it's out of scope of this guide.
>+as it's beyond the scope of this guide.
> 
> 
> </body>
>@@ -75,8 +81,8 @@
> <body>
> 
> 
>-Installing the Xen hypervisor under Gentoo is a breeze, as usually :). The
>-following will install both the hypervisor and a userspace management tools:
>+Installing the Xen hypervisor under Gentoo is a breeze, as usual :). The
>+following will install both the hypervisor and userspace management tools:
> 
> 
> <pre caption="Installing the Xen hypervisor">
>@@ -113,19 +119,19 @@
> 
> 
> As Xen requires each domain to have its own kernel image loaded into memory, you
>-usually want to strip the domU kernels to the bare minimum that's required for a
>-proper function. Unlike the dom0 which is generally responsible for tasks like
>-I/O to hard drives, networking stuff and graphics output, the domUs don't
>-require to worry about your HW devices at all. There's simply no need to include
>-a driver for your SCSI controller into domU kernel as it's already handled by
>-dom0.
>+usually want to strip the domU kernels to the bare minimum that's required for
>+proper functionality. Unlike the dom0 which is generally responsible for tasks
>+like I/O to hard drives, networking, and graphics output, the domUs don't
>+require you to worry about your hardware devices at all. There's simply no need
>+to include a driver for your SCSI controller into the domU kernel as it's
>+already handled by dom0.
> 
> 
> <note>
> Xen itself supports a delegating of some device directly to the domU instance.
> You can, for example, have a domain with a dedicated NIC or another one handling
>-a TV-capture card. Such setups, usually called Driver Domains, are out of
>-scope of this guide, so you should better consult the <uri
>+a TV-capture card. Such setups, usually called Driver Domains, are
>+outside the scope of this guide, so you should consult the <uri
> link="http://wiki.xensource.com/xenwiki/DriverDomain">Xen wiki page</uri> and/or
> the official documentation.
> </note>
>@@ -143,7 +149,7 @@
> 
> 
> Now you should configure the kernel for dom0. Please note that there are some
>-differences from the general kernel config and don't forget to customize the
>+differences from the general kernel config. Don't forget to customize the
> examples according to your needs, especially with regard to kernel versions and
> file paths.
> 
>@@ -154,7 +160,7 @@
> </pre>
> 
> 
>-Here are the most importand Xen-related settings that should take care about:
>+Here are the most important Xen-related settings that should take care about:
> 
> 
> <pre caption="dom0 configuration">
>@@ -164,13 +170,13 @@
> 
> Processor type and features ---&gt;
> Subarchitecture Type
>- (<comment>Set to "Xen-compatible"</comment>)
>+ <comment>(Set to "Xen-compatible")</comment>
> 
> XEN ---&gt;
> [*] Privileged Guest (domain 0)
> &lt;*&gt; PCI device backend driver
> &lt;*&gt; Block-device backend driver
>- <comment>(You usually want your domUs to be able to access some kind of storage :) )</comment>
>+ <comment>(You usually want your domUs to be able to access some kind of storage)</comment>
> &lt;*&gt; Network-device backend driver
> &lt;*&gt; Network-device loopback driver
> &lt; &gt; TPM-device backend driver
>@@ -182,19 +188,19 @@
> [*] Disable serial port drivers
> &lt;*&gt; Export Xen attributes in sysfs
> 
>-<comment>FIXME: add a blurb about various config options and their meaning</comment>
>+<comment>(FIXME: add a blurb about various config options and their meaning)</comment>
> </pre>
> 
> 
>-Now thaty you've configured your dom0 kernel, it's time to build it. Standard
>-<c>make</c> suggestions like <c>-j3</c> when on a two-way SMP systems apply here
>+Now that you've configured your dom0 kernel, it's time to build it. Standard
>+<c>make</c> suggestions like <c>-j3</c> when on a two-way SMP system apply here
> as well.
> 
> 
> <pre caption="Building a dom0 kernel">
> # make O=~/xen-build/2.6.16.28-dom0
> 
>-<comment>(Only if you've included module support:)</comment>
>+<comment>(Only if you've included module support)</comment>
> # make O=~/xen-build/2.6.16.28-dom0 modules modules_install
> </pre>
> 
>@@ -208,13 +214,13 @@
> # cp ~/xen-build/2.6.16.28-dom0/vmlinuz /boot/linux-2.6.16.28-xen0-vmlinuz
> </pre>
> 
>-<note>
>-FIXME: when you use LILO, you're screwed as I haven't worked with it. Just go
>-and search the web, I'm sure you'll find a manual about how to set it up.
>-</note>
>+
>+Next, we'll add an entry to our bootloader (<c>grub</c>) so that we can boot
>+into our Xen system.
>+
> 
>-<pre caption="Editting the /boot/grub/grub.conf">
>-<comment>(Please make sure you include the correct names of the Xen and kernel images:)</comment>
>+<pre caption="Editing /boot/grub/grub.conf">
>+<comment>(Please make sure you include the correct names of the Xen and kernel images)</comment>
> 
> # Example Xen settings for Grub
> title=Xen-3.0.2, Linux 2.6.16.28
>@@ -223,7 +229,7 @@
> </pre>
> 
> 
>-After you've double-checked that everything at least seems to be okay
>+After you've double-checked that everything at least <e>seems</e> to be okay
> and/or that you have console access to the box being Xenized, try to reboot it.
> If it comes back up, chances are that you can proceed with the real joy,
> creating virtual domains.
>@@ -232,7 +238,7 @@
> </body>
> </section>
> <section>
>-<title>Ttroubleshooting</title>
>+<title>Troubleshooting</title>
> <body>
> 
> TODO

Actions: View | Diff

Attachments on bug 105177: 101602 | 102579 | 125262 | 125875 | 125954 | 129096