WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] Now available: xm-test-0.2.0

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Now available: xm-test-0.2.0
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Fri, 7 Oct 2005 14:40:27 -0500
Cc: Dan Smith <danms@xxxxxxxxxx>
Delivery-date: Fri, 07 Oct 2005 19:38:53 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200510071238.12478.hollisb@xxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <87k6gu43jf.fsf@xxxxxxxxxx> <200510071238.12478.hollisb@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.2
On Friday 07 October 2005 12:38, Hollis Blanchard wrote:
> On Monday 03 October 2005 17:52, Dan Smith wrote:
> > We would like some feedback from the community on the usefulness of
> > our framework, in hopes that it might be hosted by xensource so that
> > everyone can contribute tests to help harden xm and xend.
>
> Building xm-test takes a very long time, because among other things it
> takes it upon itself to download and build its very own toolchain. That is
> extremely silly; please have it use the existing toolchain instead.

To summarize IRC conversation:
- xm-test creates an initrd that's used to boot the test DomUs.
- That initrd is created with buildroot[1], which uses uClibc, which requires 
building a whole new toolchain to use.
- If they know how, users can manually copy the initrd from one xm-test 
directory to another, avoiding the need to rebuild it.
- The initrd is plain busybox, which could easily be statically linked with 
the user's GNU libc.
- In the future, people want to install other tools (like e2fsprogs) into the 
ramdisk. These could also be statically linked with GNU libc.
- Other than statically linking, the user's libc.so could be copied to the 
initrd, which doesn't make for a very reliable testing environment.
- Using uClibc makes the initrd smaller, which is of dubious value in this 
environment.
- initrd images are limited in size, while initramfs images are not.

[1] http://buildroot.uclibc.org/

-- 
Hollis Blanchard
IBM Linux Technology Center

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