RE: [Xen-users] Xen 3 and SuSE 10

["Petersson, Mats" <mats.petersson@xxxxxxx>]

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Hubertus A. Haniel
> Sent: 04 January 2006 10:07
> To: Brian Fetcie
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Xen 3 and SuSE 10
> 
> On Tue, 03 Jan 2006 14:04:44 -0500, Brian Fetcie wrote
> > Like I say, I'm a newbie at this...
> > 
> > Here is my config...
> > 
> > ###Xen 3.0###
> > title Xen 3.0 / XenLinux 2.6
> >     root (hd0,1)
> >     kernel /boot/xen-3.0.gz dom0_mem=256000
> >     module /boot/vmlinuz-2.6.13-15-xen root=/dev/cciss/c0d0p2 
> > selinux=0
> > resume=/dev/cciss/c0d0p1 splash=silent showopts
> > 
> > This is running on a dual-processor ProLiant DL380 with 4 
> local disks 
> > in RAID5.  When I try to boot to Xen, the display zips by 
> at light speed.
> > The last thing I see is that the memory is being scrubbed moments 
> > before the server reboots.  I can boot into SuSE 10 without issue.
> > ummmm....help?
> > Thanks..
> > 
> 
> I am afraid I am at a loss there - this config works for me 
> on and IBM x360 and on the IBM LS20 blades. - I am also 
> running SuSE 9.3 with Garloffs Xen 2.0.7 on an old dual 
> pentium pro with a similar config without any problems. - I 
> am at a loss why your box reboots - you could try disabling 
> acpi on the boot command line but that is just a far fetched 
> idea so I would not necessarely expect that to fix your problem.
> 
> Regards
> Hubba
> 
Sounds like you're using some less standard disk system. The Xen kernel
may not have the same setup when it comes to device drivers as the
distro's kernel. Also, if you haven't rebuilt your kernel to have
modules turned off, you'll have to have a line like this:

        module /boot/initrd-2.6.13-15-xen

Giving the option "noreboot" on the kernel line in your grub.conf file
would also help to give some more information on what's going wrong -
most likely it will complain that it's not finding the root-device. The
noreboot option tells the Xen kernel to not reboot when there's crash,
and it allows you to read what the last thing that it printed was,
rather than it being lost in the process of rebooting. 

Obviously, using serial port to output the data, as per what I sent
earlier, would also solve the "text disappears before I can read it"
problem. 

--
Mats


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users