system/xen: Updated for version 4.5.0 and more.

1 files changed, 32 insertions, 47 deletions

diff --git a/system/xen/domU/README.domU b/system/xen/domU/README.domU
index 712a555f14b5..25a281ecd328 100644
--- a/system/xen/domU/README.domU
+++ b/system/xen/domU/README.domU
@@ -1,56 +1,41 @@
-		HOW TO INSTALL A SLACKWARE domU XEN GUEST
+domU.sh: This script builds a Slackware domU guest.
 
-After the ordeal of installing and configuring LILO/GRUB, Xen, kernel-xen and
-initrd, editing rc.local and rc.local_shutdown and finally booting on your
-Slackware XenLinux, you might be wondering how are you to load you guest OS.
-If you look around, you might find Xen domU (unprivileged) guest that you can
-download from the Internet, but some of us might want to roll their own. This
-MINI-HOWTO shows how to install a Slackware domU guest. The fastest way is to
-mount your Slackware DVD on /media/SlackDVD, normally this is the mount point
-chosen by HAL.
-Then run the included domU.sh script:
+After the ordeal of installing, configuring and booting Slackware XenLinux,
+you might be wondering how to load a guest OS. If you look around, you can
+find Xen domU (unprivileged) guest images to download from the Internet, but
+some of us might want to roll their own.
 
-# ./domU.sh
+Start by mounting Slackware DVD to /media/SlackDVD and run:
 
-This will install Slackware onto an 8GB file called slackware.img and a 500MB 
-swap file called swap_file. By default, a typical server installation ensues.
+  ./domU.sh
 
-Have a good look at the "mydom" file as you need to fill in the full path to
-the slackware.img and swap_file files.
+This script will install Slackware into 8GB file called slackware.img and a
+also create 500MB swap file called swap_file.
 
-Then run the following command:
+Once the install is complete, have a look at the "mydom" file. Fill in the
+full path to slackware.img and swap_file, and run:
 
-# xl create -c mydom
+  xl create -c mydom
 
 Your Slackware XenLinux domU should boot instantly.
 
-Since Xen domU support has been in mainline kernel for a while now, those that
-wish to have the best performance can compile a seperate domU kernel based on a
-stock Slackware kernel config.
-This is what you have to select/unselect when building domU only kernel:
-
----
-Processor type and features  --->
-  [*] Paravirtualized guest support  --->
-    [*]   Xen guest support
-
-Bus options (PCI etc.)  --->
-  [ ] PCI support
-
-Device Drivers  --->
-  < > Serial ATA and Parallel ATA drivers  --->
-  SCSI device support  --->
-    < > SCSI device support
----
-
-Disabling SCSI support frees up the /dev/sd* device names for use as Xen
-virtual block devices. Basicly, this changes their names from /dev/sd* to a
-Xen device name format /dev/xvd*. If this is left enabled, ocasionaly domU can
-get stuck with this error: "XENBUS: Waiting for devices to initialise..."
-Naturaly, to get the best performance you can disable everything that you
-don't need in a domU kernel.
-
-Note that these files are not intended for a production environment. Users who
-have particular requirements will need to set up their own methods, but these
-files might provide a good starting point. Refer to the Xen manual and 
-http://xen.org for more details and options.
+Getting the best performance out of your domU is usually done with trimmed
+down kernels. Here are a few things to (de)select when building such kernel:
+
+  Processor type and features  --->
+    [*] Paravirtualized guest support  --->
+      [*]   Xen guest support
+
+  Bus options (PCI etc.)  --->
+    [ ] PCI support
+
+  Device Drivers  --->
+    < > Serial ATA and Parallel ATA drivers  --->
+    SCSI device support  --->
+      < > SCSI device support
+
+Removing SCSI device support will expose /dev/xvd* block device names, and
+prevent "XENBUS: Waiting for devices to initialise..." error.
+
+These files are not intended for production enviroment use, and should serve
+only as a good starting point.