FYI
---------- Forwarded message ----------
Date: Fri, 14 Apr 2006 23:02:33 -0600
From: Clyde Griffin <[EMAIL PROTECTED]>
Subject: Fix for Xen Paravirtualized Guest Installation (SLES 10 Beta 10 /
SL 10.1 RC1)
There are two major Xen issues in SLES 10 Beta 10 and SUSE Linux 10.1 RC1.
Workarounds are described below. Please pass this email on to anyone
doing SUSE Linux testing with Xen.
First Issue:
The /boot/grub/menu.lst entry for booting the Xen hypervisor may not get
created automatically.
Workaround:
1) Run the YaST "Virtual Machine Management (Xen)" tool in the YaST
"System" category to install the Xen hypervisor and kernel modules.
(One time only.)
2) Add an entry to /boot/grub/menu.lst that looks like the example below.
(Please refer to your existing menu.lst for specifics.)
3) Reboot and select Xen at the Grub menu.
###Don't change this comment - YaST2 identifier: Original name: xen###
title XEN
root (hd0,1)
kernel /boot/xen.gz
module /boot/vmlinuz-xen root=/dev/hda2 vga=0x317 selinux=0
resume=/dev/hda1 splash=silent showopts
module /boot/initrd-xen
Second Issue:
SLES 10 Beta 10 and SUSE Linux 10.1 RC1 paravirtualized guest
installations do not work in the official builds.
Workaround:
1) Create an install source.
2) Replace the install-initrd... RPM in your install source tree with the
appropriate RPM located on the Novell/SUSE Xen Technical Preview site
at http://forge.novell.com/modules/xfmod/project/?xenpreview
(install-initrd-1.0-14.i586.rpm or install-initrd-1.0-14.x86_64.rpm.)
3) Run the YaST "Virtual Machine Management (Xen)" tool in the YaST
"System" category to install a paravirtualized guest.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
