Re: [XenPPC] Problems with Xen in hg tree

On Wed, 2007-02-07 at 17:37 -0500, Jimi Xenidis wrote:
> On Feb 7, 2007, at 12:48 PM, 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 ;-)
> 
> Thats not user error, that should work, its not smart but is should  
> work, stripped or not stripped.
> So vmlinux can be like 64M which is bigger that our boo_of allocator  
> can currently handle.
> This is our bug, we should simply exit gracefully.
> 
> Jerone, could you file a bug with the specifics?

I can though adding a check to try and catch the size (as suggested by
Hollis) does not look like it got far enough in the code to catch it. I
think it's the tftp limit being 64MB (though I could be wrong). I'll
file a bug never the less.

> 
> -JX
> 


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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [XenPPC] boot failure with large dom0, Hollis Blanchard

Next by Date:

[XenPPC] [PATCH 1/2] xen: remove start_info_t from dom0 building, Ryan Harper

Previous by Thread:

Re: [XenPPC] Problems with Xen in hg tree, Jimi Xenidis

Next by Thread:

Re: [XenPPC] Problems with Xen in hg tree, Jimi Xenidis

Indexes:

[Date] [Thread] [Top] [All Lists]