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

[Xen-devel] RE: Default Xen Kernel Builds (was Re: Modules in domU kerne

To: "Sean Dague" <japh@xxxxxxxxxx>
Subject: [Xen-devel] RE: Default Xen Kernel Builds (was Re: Modules in domU kernel config?)
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 14 Mar 2006 14:57:32 -0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 14 Mar 2006 14:58:32 +0000
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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZHbfDMSnz394v8RqmofcYIa9URfwACLLeg
Thread-topic: Default Xen Kernel Builds (was Re: Modules in domU kernel config?)
> > These days, most of the testing is on -xen kernels rather 
> than -xen0/U.
> The default xen-unstable builds -xen0 and -xenU kernels, so 
> as far as I know, no one around these parts is testing -xen 
> kernels.  If you believe that -xen0 / -xenU are deprecated, 
> it would be good to change the build defaults.

The binary tar balls and RPMs that are built nightly (and for each
release) have all been based around the -xen kernel (for over a year
now). 

I've suggested changing the defult when building from source to just
build -xen before, but a number of developers complained loudly about
the build times going up masively and the inconvenience of needing to
install modules etc. Every developer would end up with a local patch to
change the default etc.

Is it time to revist this? 
NB: we got caught out by this with the 3.0.0 release whereby a config
option enabled in -xen and not in -xen0 caused the "insufficient tx
headroom" bug that effected some configurations and hastened the relase
of 3.0.0-1

Ian

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

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