Re: [XenPPC] boot failure with large dom0

[Jerone Young <jyoung5@xxxxxxxxxx>]

So it looks like the problem has to do with tftp which apears to have a
64MB send limit. The file is over this and so everything does not make
it. Adding a check for dom0 image size does not good since the image
itself is not fully transfered. Which make since why you get the error:
boot_of_alloc_init: pg :0x2000 of our image is different
at bootup.

On Wed, 2007-02-07 at 11:59 -0600, Hollis Blanchard wrote:
> 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");
> 


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