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/
Home Products Support Community News


[Xen-devel] "Old method" bootloader failing with large ramdisk

To: "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] "Old method" bootloader failing with large ramdisk
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Fri, 24 Apr 2009 16:09:34 -0700 (PDT)
Delivery-date: Fri, 24 Apr 2009 16:10:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I'm trying to boot a PV guest using the "old method"
of passing kernel= and ramdisk= and it appears to
work fine with a "small" initrd but not with a "large"
one. (Small is 4MB, large is 154MB.)  I'm sure both
of the initrd's are properly gzip'ed etc.  Unpacked,
the large one approaches 400M.

By doing some kernel startup debugging, it appears
that the large initrd never finds its way into memory.
Or at least not completely or properly.

So I'm guessing that the "old method bootloader"
is having problems with the large initrd.  Silently,
I think, as I can't find anything that looks like errors
in /var/log/xen/domain-builder-ng.log.

Should this be expected to work?  Has anyone else
been successful with a large initrd doing this?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>