diff options
| author | cl349@firebug.cl.cam.ac.uk <cl349@firebug.cl.cam.ac.uk> | 2005-05-31 13:14:42 +0000 |
|---|---|---|
| committer | cl349@firebug.cl.cam.ac.uk <cl349@firebug.cl.cam.ac.uk> | 2005-05-31 13:14:42 +0000 |
| commit | acbaea9bb990ca64e788a1eccff03528843fbb6d (patch) | |
| tree | 9662ba4d079a4a6c561d4f27ca56656d7452784d /README | |
| parent | f2070412f6aa3d403271a715802e64596dce1a41 (diff) | |
| download | xen-acbaea9bb990ca64e788a1eccff03528843fbb6d.tar.gz xen-acbaea9bb990ca64e788a1eccff03528843fbb6d.tar.bz2 xen-acbaea9bb990ca64e788a1eccff03528843fbb6d.zip | |
bitkeeper revision 1.1159.258.159 (429c6342A2HJ4wUj0nM5MNauX7azZQ)
vnet-xend.txt, user.tex, README:
Update the Linux kernel version number from 2.6.9 to 2.6 or 2.6.11
in several places in documentation.
Original patch provided by Andrew Thompson <andrewkt@aktzero.com>
Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -50,16 +50,16 @@ performed with root privileges.] alternatives such as LILO are *not* supported. You can most likely find your GRUB menu file at /boot/grub/menu.lst: edit this file to include an entry like the following: - # title Xen 2.0 / XenLinux 2.6.9 - # kernel /boot/xen.gz dom0_mem=<mem-kb> console=vga - # module /boot/vmlinuz-2.6.9-xen0 root=<root-dev> ro console=tty0 + # title Xen 2.0 / XenLinux 2.6 + # kernel /boot/xen-2.0.gz dom0_mem=<mem-kb> console=vga + # module /boot/vmlinuz-2.6-xen0 root=<root-dev> ro console=tty0 For <mem-kb> you should specify the amount of memory, in kilobytes, to allocate for use by your initial XenLinux virtual machine. Note that Xen itself reserves about 32MB memory for internal use, which is not available for allocation to virtual machines. For <root-dev>, specify your usual root partition (e.g., /dev/hda1). -3. Reboot your system and select the "Xen 2.0 / XenLinux 2.6.9" menu +3. Reboot your system and select the "Xen 2.0 / XenLinux 2.6" menu option. After booting Xen, XenLinux will start and your initialisation scripts should execute in the usual way. |