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


Re: [Xen-devel] [PATCH] Add xl domUs default configuration file

To: Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Add xl domUs default configuration file
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Mon, 6 Jun 2011 16:01:46 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Fabio Fantoni <fantonifabio@xxxxxxxxxx>
Delivery-date: Mon, 06 Jun 2011 08:09:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1106061427210.12963@kaball-desktop>
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>
Organization: Citrix Systems, Inc.
References: <4DECB9C6.2040208@xxxxxxxxxx> <alpine.DEB.2.00.1106061427210.12963@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2011-06-06 at 14:30 +0100, Stefano Stabellini wrote:
> What do you mean? Xl already provides defaults for almost
> everything...
> In any case the idea of a default xl config file is not bad.

Wouldn't something need to read this file for it to be controlling the
defaults? Would that "something" replace the libxl_*_init and other
places where the library provides a default? How does this work with
other toolstacks using libxl?

Or is this intended to be an xl version of the existing xmexample.*
files? In which case calling it xlexample.* might help people towards
this conclusion. Also avoiding the term "default" would help -- a
default is different to an example.

> > +# Define the disk devices you want the domain to have access to,
> and
> > +# what you want them accessible as.
> > +# For example can be put here a default installation cd.
> > +# disk = [ 'tap2:aio:/var/images/min-el3-i386.img,hdc:cdrom,r' ]
> tap2 shouldn't be the default, probably is better to specify just
> file: here

If this file really is supposed to contain defaults and not examples
then I don't think a default makes sense for this kind of setting.

There is no sane default for disks other than None, they are always
going to have to be in the guest specific config file. Similarly for
nics, kernels, ramdisk etc.


Xen-devel mailing list