summaryrefslogtreecommitdiffstats
path: root/system/xen/dom0/README.dom0
diff options
context:
space:
mode:
Diffstat (limited to 'system/xen/dom0/README.dom0')
-rw-r--r--system/xen/dom0/README.dom047
1 files changed, 20 insertions, 27 deletions
diff --git a/system/xen/dom0/README.dom0 b/system/xen/dom0/README.dom0
index 7c451ef1c2..326b7bfef6 100644
--- a/system/xen/dom0/README.dom0
+++ b/system/xen/dom0/README.dom0
@@ -1,21 +1,22 @@
kernel-xen.sh: This script builds the Linux Kernel for a Xen Hypervisor.
The configuration files included here are based on generic Slackware configs.
-For 32bit systems, SMP based config was used. You can run "make menuconfig"
-before compiling a Xen kernel by passing the "MENUCONFIG=yes" to the script.
+For 32bit systems, SMP based config was used. To run "make menuconfig" before
+compiling a Xen kernel, use "MENUCONFIG=yes" variable.
-Originaly, booting a Xen kernel with LILO bootloader is not supported, so GRUB
-has to be used. Since some of us still preffer LILO over GRUB, there is a way
-to accomplish this with mbootpack. Basicaly mbootpack takes Linux kernel, initrd
-and Xen VMM, and packages them up as a single file that looks like a bzImage
+Originally, booting a Xen kernel with LILO bootloader is not supported, so GRUB
+has to be used. Because some might preffer LILO over GRUB, there is a way to
+accomplish this with mbootpack. Basicaly, mbootpack takes Linux kernel, initrd
+and Xen VMM, and packages them up into a single file that looks like a bzImage
Linux kernel. To select how kernel is packed use "BOOTLOADER=" variable. Valid
-options are "lilo" and "grub".
+options are "lilo" and "grub". Because generic kernel requires an initrd image,
+there are aditional variables that can be used; ROOTMOD (takes a list of
+colon-delimited modules to build into initrd), ROOTFS (takes a name of a module
+to use for root filesystem) and ROOTDEV (takes a name of root filesystem
+device).
-Since generic kernel requires an initrd image, there are aditional variables that
-can be used, such as ROOTMOD (list of root filesystem modules), ROOTFS (name of a
-module to use) and ROOTDEV (name of root filesystem device).
-
-After a new kernel image is created, add something like the folowing to lilo.conf:
+After a new kernel image is created, and if bootloader of choice is LILO,
+include these lines in /etc/lilo.conf:
image = /boot/vmlinuz-xen
root = /dev/sda2
@@ -26,17 +27,9 @@ image = /boot/vmlinuz-xen
Note: everything before "--" is passed to Xen, and everything after "--" is
passed to the Linux kernel.
-If for some reason LILO is not good enough, you can always use GRUB.
-GRUB may be installed from Slackware's extra repository. The GRUB package
-is not available from the Slackware x86_64 distribution, but the source
-and a SlackBuild may be found in its extra/source repository.
-
-grubconfig that comes with Slackware's GRUB package may give a starting point
-to configure GRUB. Moreover, the Xen User Manual and its README file installed
-with the Xen package include details on which parameters to include in the GRUB
-configuration file. For example, include these lines in /boot/grub/menu.lst:
+For GRUB, for example, include these lines in /boot/grub/menu.lst:
-title Slackware XenLinux 14.0
+title Slackware XenLinux 14.1
root (hd0,0)
kernel /boot/xen.gz dom0_mem=524288 console=vga
module /boot/vmlinuz-xen root=/dev/sda2 ro console=tty0 nomodeset
@@ -44,12 +37,12 @@ title Slackware XenLinux 14.0
Note that dom0_mem parameter is critical for a 32bit install.
-If your dom0 kernel crashes or freezes at boot, either with an automatic reboot
-or with the blank screen, here are some things to try:
+Here are some notes/guidances if your dom0 crashes, freezes or maybe the
+screen goes blank on boot:
- Specify an out of range number to "fbcon" to disable framebuffer altogether,
- for an example append fbcon=map:9 to the Linux kernel.
- (To see a list of available devices in your system: cat /proc/fb)
+ which, for example, is done by appending fbcon=map:9 to the Linux kernel (To
+ see a list of available devices in your system check /proc/fb).
- Blacklist framebuffer module from loading. This one requires a bit of
digging arround in dmesg/lsmod to find out wich module is in use.
- Disable framebuffer devices by setting CONFIG_FB=n in kernel config.
-- Try another VGA card (sorry).
+- Try booting with another VGA card (sorry).