--- 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 @@
@@ -38,31 +38,37 @@
Xen comes with extensive
-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:
@@ -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.
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 @@ -143,7 +149,7 @@Driver Domains, are +outside the scope of this guide, so you should consult the Xen wiki page and/or the official documentation.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 @@
-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:
@@ -164,13 +170,13 @@ Processor type and features ---> Subarchitecture Type - (Set to "Xen-compatible" ) +(Set to "Xen-compatible") XEN ---> [*] Privileged Guest (domain 0) <*> PCI device backend driver <*> Block-device backend driver -(You usually want your domUs to be able to access some kind of storage :) ) +(You usually want your domUs to be able to access some kind of storage) <*> Network-device backend driver <*> Network-device loopback driver < > TPM-device backend driver @@ -182,19 +188,19 @@ [*] Disable serial port drivers <*> Export Xen attributes in sysfs -FIXME: add a blurb about various config options and their meaning +(FIXME: add a blurb about various config options and their meaning)
-Now thaty you've configured your dom0 kernel, it's time to build it. Standard
-
# make O=~/xen-build/2.6.16.28-dom0 -@@ -208,13 +214,13 @@ # cp ~/xen-build/2.6.16.28-dom0/vmlinuz /boot/linux-2.6.16.28-xen0-vmlinuz -(Only if you've included module support:) +(Only if you've included module support) # make O=~/xen-build/2.6.16.28-dom0 modules modules_install
+Next, we'll add an entry to our bootloader (
-(Please make sure you include the correct names of the Xen and kernel images:) ++(Please make sure you include the correct names of the Xen and kernel images) # Example Xen settings for Grub title=Xen-3.0.2, Linux 2.6.16.28 @@ -223,7 +229,7 @@-After you've double-checked that everything at least seems to be okay +After you've double-checked that everything at least
seems 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 @@- Ttroubleshooting +Troubleshooting TODO