RE: [Xen-users] Problems upgrading to Xen 3.1

["Fischer, Anna" <anna.fischer@xxxxxx>]

I've tried capturing the screen output now and in fact I don't see any error 
messages. The boot process simply stops before loading Dom0 initrd and kernel. 
I've used the kernel+initrd successfully with Xen 3.0.4 before, so why does 
upgrading to Xen 3.1 stop the machine from booting up at all? Is there anything 
else I could try out?

Thanks,
Anna

PS: Attached a screenshot of where Xen hangs, sorry I can't provide it as text 
right now...

> -----Original Message-----
> From: Age_M [mailto:Age_M@xxxxxx]
> Sent: 04 April 2008 19:41
> To: Fischer, Anna
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Problems upgrading to Xen 3.1
>
> Hi Anna,
>
> try "*noreboot*" in your kernel-line (where xen.gz is) in grub.conf.
> Maybe this will give you a clue on what's going on.
>
> Greetz Age_M
>
>
> Fischer, Anna schrieb:
> > I've upgraded my Xen system from Xen 3.0.4 to Xen 3.1 by installing a
> new xen.gz, new xen-tools and new xen-libs for my SLES10 system (using
> RPMs provided through Novell). However, now the system doesn't boot up
> any more. Basically, it seems to boot the Xen hypervisor (I can see all
> the (XEN) messages), but then suddenly reboots instead of booting the
> Dom0 kernel. When upgrading to 3.1, do I actually also need to upgrade
> the Dom0 kernel somehow? If yes then how can I do that? I don't see any
> errors in the boot logs, as the kernel doesn't even seem to start up at
> all before the system suddenly reboots.
> >
> > Thanks,
> > Anna
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> >

Attachment: xen_log.bmp
Description: xen_log.bmp

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