This guide is currently x86-centric as that's the platform I've set up the Xen

This guide is focused on installing Xen on x86 processors. While Xen is

on. It'd be great if someone adds notes about using Xen on different platforms.

supported on other architectures, this guide does not yet cover them.

  <dd>An instance of your "virtual computer", running its own kernel and user

    <dd>

  level applications</dd>

      An instance of your "virtual computer", running its own kernel and user

      level applications

    </dd>

  <dd>The "primary" domain that is running all the time and is usually

    <dd>

  responsible for things like setting up another domains and other management

      The "primary" domain that is running all the time and is usually

  tasks. It's "automatically" launched by the Xen hypervisor during the boot

      responsible for things like setting up another domains and other

  process. When the dom0 exists, Xen by default reboots the machine.

      management tasks. It's "automatically" launched by the Xen hypervisor

  </dd>

      during the boot process. When the dom0 exists, Xen by default reboots the

      machine.

    </dd>

  <dd>"Regular" instances of the unprivileged virtual machines. Each of them can

    <dd>

  be running different kernel version with wildly differing userspace

      "Regular" instances of the unprivileged virtual machines. Each of them can

  environment, even another operating system.

      be running a different kernel version with a wildly differing userspace

  </dd>

      environment, or even another operating system.

    </dd>

  <dd>A Xen-supplied software that runs at the "bare metal" of your computer and

    <dd>

  is responsible for low-level tasks like CPU scheduling, memory management and

      A Xen-supplied software that runs at the "bare metal" of your computer and

  dom0 launching upon boot.

      is responsible for low-level tasks like CPU scheduling, memory management

  </dd>

      and dom0 launching upon boot.

    </dd>

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>.

as it's out of scope of this guide.

as it's beyond the scope of this guide.

Installing the Xen hypervisor under Gentoo is a breeze, as usually :). The

Installing the Xen hypervisor under Gentoo is a breeze, as usual :). The

following will install both the hypervisor and a userspace management tools:

following will install both the hypervisor and userspace management tools:

usually want to strip the domU kernels to the bare minimum that's required for a

usually want to strip the domU kernels to the bare minimum that's required for

proper function. Unlike the dom0 which is generally responsible for tasks like

proper functionality. Unlike the dom0 which is generally responsible for tasks

I/O to hard drives, networking stuff and graphics output, the domUs don't

like I/O to hard drives, networking, and graphics output, the domUs don't

require to worry about your HW devices at all. There's simply no need to include

require you to worry about your hardware devices at all. There's simply no need

a driver for your SCSI controller into domU kernel as it's already handled by

to include a driver for your SCSI controller into the domU kernel as it's

dom0.

already handled by dom0.

a TV-capture card. Such setups, usually called <b>Driver Domains</b>, are out of

a TV-capture card. Such setups, usually called <b>Driver Domains</b>, are

scope of this guide, so you should better consult the <uri

outside the scope of this guide, so you should consult the <uri

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

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:

  (<comment>Set to "Xen-compatible"</comment>)

  <comment>(Set to "Xen-compatible")</comment>

  <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>

<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>

Now thaty you've configured your dom0 kernel, it's time to build it. Standard

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 systems apply here

<c>make</c> suggestions like <c>-j3</c> when on a two-way SMP system apply here

<comment>(Only if you've included module support:)</comment>

<comment>(Only if you've included module support)</comment>

<note>

<p>

FIXME: when you use LILO, you're screwed as I haven't worked with it. Just go

Next, we'll add an entry to our bootloader (<c>grub</c>) so that we can boot

and search the web, I'm sure you'll find a manual about how to set it up.

into our Xen system.

</note>

</p>

<pre caption="Editting the /boot/grub/grub.conf">

<pre caption="Editing /boot/grub/grub.conf">

<comment>(Please make sure you include the correct names of the Xen and kernel images:)</comment>

<comment>(Please make sure you include the correct names of the Xen and kernel images)</comment>

After you've double-checked that everything at least <i>seems</i> to be okay

After you've double-checked that everything at least <e>seems</e> to be okay

<title>Ttroubleshooting</title>

<title>Troubleshooting</title>