diff options
Diffstat (limited to 'system/xen/dom0/README.dom0')
-rw-r--r-- | system/xen/dom0/README.dom0 | 16 |
1 files changed, 7 insertions, 9 deletions
diff --git a/system/xen/dom0/README.dom0 b/system/xen/dom0/README.dom0 index 326b7bfef6..f9cc00c340 100644 --- a/system/xen/dom0/README.dom0 +++ b/system/xen/dom0/README.dom0 @@ -1,12 +1,12 @@ 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. To run "make menuconfig" before -compiling a Xen kernel, use "MENUCONFIG=yes" variable. +The configuration file included here is based on a generic Slackware64 kernel +config. To run "make menuconfig" before compiling a Xen kernel, use the +"MENUCONFIG=yes" variable. 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 +has to be used. For those that preffer LILO over GRUB, there is a way to +accomplish this with mbootpack. Basically, 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". Because generic kernel requires an initrd image, @@ -27,7 +27,7 @@ image = /boot/vmlinuz-xen Note: everything before "--" is passed to Xen, and everything after "--" is passed to the Linux kernel. -For GRUB, for example, include these lines in /boot/grub/menu.lst: +When using GRUB, you might want to include these lines in /boot/grub/menu.lst: title Slackware XenLinux 14.1 root (hd0,0) @@ -35,10 +35,8 @@ title Slackware XenLinux 14.1 module /boot/vmlinuz-xen root=/dev/sda2 ro console=tty0 nomodeset module /boot/initrd-xen.gz -Note that dom0_mem parameter is critical for a 32bit install. - Here are some notes/guidances if your dom0 crashes, freezes or maybe the -screen goes blank on boot: +screen goes blank at boot: - Specify an out of range number to "fbcon" to disable framebuffer altogether, 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). |