On Wed, Oct 04, 2006 at 05:34:05PM -0500, Hollis Blanchard wrote:
> On Mon, 2006-10-02 at 11:46 -0400, Amos Waterland wrote:
> > This patch has been in use by an internal IBM project for some time.
> > It enables two important things: allowing developers and cluster
> > administrators the option of overriding the bootargs supplied by
> > firmware, and the ability to take a single gold master xen binary and
> > customize its bootargs across a cluster with a simple and well-tested
> > post-processing tool.
> 
> Thanks for your patience Amos; I believe the commits I just made should
> solve your problem. Basically removing the boot wrapper (and that's
> bugged me for a while for other reasons) allows us to collapse three
> command line buffers into one, and that makes me happy. :)
> 
> bicl (http://www.cs.unm.edu/~k42/tools/bicl) acts directly on the
> command line that was built in at compile time. If that buffer is empty
> at runtime, firmware arguments will be used.
> 
> Note that changing the CMDLINE at compile time does not properly replace
> the previous CMDLINE; you would have to make clean or remove
> xen/arch/powerpc/cmdline.o by hand. I'd happily accept a Makefile patch
> for that.

I have tested the commits pretty heavily and things work fine.  Thanks.

I am doing automated reliability runs now like this:

 $ bicl xen "xen dom0_mem=%M --"
 $ for i in 128M 192M 1G 2G 7G; do 
     cp xen xen.$i &&
       bicl xen.$i "$(bicl xen | sed "s,%M,$i,")" &&
         netboot-js21-blade -f xen.$i; done


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

Reply via email to