From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ronald G Minnich Subject: Re: Xen bootloader Date: Fri, 14 Jul 2006 09:21:47 -0600 Message-ID: <44B7B68B.6060903@lanl.gov> References: <200607131408.00480.mark.williamson@cl.cam.ac.uk> <86802c440607132212l1a38c6b9v6ff01d93dea2491b@mail.gmail.com> <200607141248.32241.mark.williamson@cl.cam.ac.uk> <1152879004.17163.8.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1152879004.17163.8.camel@localhost.localdomain> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Rob Bradford Cc: Ian Pratt , Anthony Liguori , xen-devel@lists.xensource.com, yhlu , Michael Loehr List-Id: xen-devel@lists.xenproject.org Rob Bradford wrote: > On Fri, 2006-07-14 at 12:48 +0100, Mark Williamson wrote: > >>The default for config files would be to boot the kboot kernel+initrd, which >>would then load the correct kernel+initrd for that guest, according to a >>configuration file or a user menu choice. > > > Could we use initramfs rather than a separate initrd? If I understand > correctly this is just the kind of use case it would work well for. we've had the same discussion on olpc, and I even built initramfs images for olpc. There are a number of bugs in initramfs up to and including 2.6.17, which you will want to make sure are fixed. They all related to building -- things just don't work correctly, due to broken build scripts. I just fixed said bugs and kept going, and offered my patches up but was told 'those bugs just got fixed', so YMMV. But xen seems to be at 2.6.13 right now, so I expect they're still there. Modulo those bugs, it ought to work fine -- it did for me. ron