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] libxl: error handling before xenstored runs

To: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] libxl: error handling before xenstored runs
From: Vincent Hanquez <vincent.hanquez@xxxxxxxxxxxxx>
Date: Fri, 11 Feb 2011 11:16:46 +0000
Cc: Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Gianni, Tedesco <gianni.tedesco@xxxxxxxxxx>
Delivery-date: Fri, 11 Feb 2011 03:17:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110211094949.GF18135@xxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <201102091213.06591.Christoph.Egger@xxxxxxx> <4D52B5DD.2060900@xxxxxxxxx> <201102091652.09218.Christoph.Egger@xxxxxxx> <201102091654.29318.Christoph.Egger@xxxxxxx> <1297273192.29419.7.camel@xxxxxxxxxxxxxxxxxxxxxx> <1297328120.1047.21.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D53AF37.9010204@xxxxxxxxxxxxx> <1297337081.20491.132.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D545EBE.1060501@xxxxxxxxxxxxx> <20110211094949.GF18135@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100821 Icedove/3.1.2
On 11/02/11 09:49, Tim Deegan wrote:
At 21:55 +0000 on 10 Feb (1297374910), Vincent Hanquez wrote:
On 10/02/11 11:24, Ian Campbell wrote:
Right but this approach doesn't work with xenstored in a stubdomain.

yeah I know. xenstored in a stubdom is just an experiment, when it
become a serious feature, this argument would hold. however it's not
going to be use in 4.1, and in any production settings.

You seem to be arguing that we shouldn't fix a bug in the kernel.  I
don't understand that.  How is it going to become a "serious feature" if
we don't fix the bugs that affect it?

If you want to fix the behaviour which is present since xen 3.0 (you can understand why i'm not holding my breath anymore), all the best.

What I'm arguing is that behaviour should not exists in the next stable version of xen, specially for a feature that is not serious yet (at least upstream).

In any case, I can think of three projects off the top of my head that
are using stub domains aggressively, one of which I know is using
xenstore stub domains in particular.  I'm sure there are others.

Good for them. I'm sure they can carry a 2 liner patch to connect to the ring instead of the unix socket, until they actually submit upstream their stuff that make xenstored stubdomain great.

--
Vincent

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