WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [XenPPC] boot failure with large dom0

To: jyoung5@xxxxxxxxxx
Subject: Re: [XenPPC] boot failure with large dom0
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Wed, 07 Feb 2007 11:59:19 -0600
Cc: xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 07 Feb 2007 09:58:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1170870524.3172.7.camel@thinkpad>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <1170806294.12947.1.camel@thinkpad> <1170870524.3172.7.camel@thinkpad>
Reply-to: Hollis Blanchard <hollisb@xxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
I use a vmlinux as dom0, but it's a stripped vmlinux. A vmlinux with
full debug symbols is 55MB here, which probably explains this problem.

Could you see how easy it would be to catch this problem at runtime and
have a nice panic? Checking dom0_len in __start_xen() would probably do
the trick, maybe something like:
        if (dom0_start + dom0_len > (32<<20))
                panic("dom0 is too big");

-- 
Hollis Blanchard
IBM Linux Technology Center

On Wed, 2007-02-07 at 11:48 -0600, Jerone Young wrote:
> OK all is well...no fire here...move along. I figured out what happened.
> I included the vmlinux as the DOM0_IMAGE and not the zImage. It compiled
> through .. it is a bit surprising the Xen died though and not during
> loading of Dom0. So ultimately this is a USER error ;-)
> 
> On Tue, 2007-02-06 at 17:58 -0600, Jerone Young wrote:
> > So cloning the Xen tree as of today .. you can no longer bootup Xen :-).
> > Here is the output on a JS21
> > 
> > The currently active flashside is: 1 (temporary)
> > Stopping BMC watchdog...
> > Trying to load: sync_console debug || root=/dev/sda3 debug from:
> > net ... 
> > 
> >  Bootloader 1.5 
> >   Reading MAC address from device: 00:14:5E:9C:1C:C5
> >   Requesting IP address via BOOTP: 9.3.189.7
> >   Requesting file "leaf4" via TFTP
> >   Receiving data: ####A#######A|
> >   TFTP: Received leaf4 (65359 KBytes)
> >   Successfully loaded 
> > ---------------------------------------------------
> > OF: Xen/PPC version 3.0-unstable (root@xxxxxxxxxxxxxx) (gcc version
> > 4.1.0 (SUSE Linux)) Tue Feb  6 17:18:51 CST 2007
> > boot_of_init args: 0x0 0x0 0xe11027c 0xe28bed2 0x2a
> > boot msr: 0x1000000000003000
> > boot_of_init: _start 00000000004000d0 _end 00000000042b0310 0xe28bed2
> > boot_of_alloc_init: pg :0x2000 of our image is different
> > 
> > HANG
> > 
> > 
> > I'll be looking into this in the morning. But just an FYI to everybody.
> > 
> > 
> > _______________________________________________
> > Xen-ppc-devel mailing list
> > Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-ppc-devel
> 
> 
> _______________________________________________
> Xen-ppc-devel mailing list
> Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ppc-devel


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