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] /sys/hypervisor/uuid

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] /sys/hypervisor/uuid
From: Jeremy Katz <katzj@xxxxxxxxxx>
Date: Mon, 22 May 2006 11:09:52 -0400
Cc: Chris Wright <chrisw@xxxxxxxxxxxx>, Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>, Christian Limpach <chris@xxxxxxxxxxxxx>, Markus Armbruster <armbru@xxxxxxxxxx>, Christian.Limpach@xxxxxxxxxxxx
Delivery-date: Mon, 22 May 2006 08:10:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <dbee8296d0ee5e494a8350d291e30749@xxxxxxxxxxxx>
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>
References: <87y7wzmeqb.fsf@xxxxxxxxxxxxxxxxx> <a74fd46bb61fffb16ab812859d83d8e8@xxxxxxxxxxxx> <20060519074112.GF2724@xxxxxxxxxxxxxxxxx> <3d8eece20605190243v626b894bp1f5e6f4ff23e56d1@xxxxxxxxxxxxxx> <871wuqkk1n.fsf@xxxxxxxxxxxxxxxxx> <0a750dd5943e811cacdb572f5b51c0d2@xxxxxxxxxxxx> <878xouinqh.fsf@xxxxxxxxxxxxxxxxx> <1a37aa1f8eeddca05257eefe8803f415@xxxxxxxxxxxx> <1148301867.2532.10.camel@xxxxxxxxxxxxxx> <dbee8296d0ee5e494a8350d291e30749@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2006-05-22 at 14:24 +0100, Keir Fraser wrote:
> On 22 May 2006, at 13:44, Jeremy Katz wrote:
> >> If we allowed unprivileged read access to xenstore, that would require
> >> only a smaller and more general patch to the kernel. Then you could 
> >> put
> >> the uuid extraction logic in user space?
> >
> > But if you still require xs transactions, then it remains complicated
> > and a potential way to introduce fun problems for dom0 from a domU.
> > Especially as I would expect that then people will start coding their
> > own stuff instead of bringing a dep on libxs into domUs
> Well, the bottom line is: I will apply the uuid patch for sysfs if you 
> want it. But don't be surprised if the whole lot goes in the bin at 
> some point when we have the inevitable fight with the kernel 
> maintainers. In contrast, libxs presents a stable supported interface.

I really think the "do transactions via xenstore in domU" is going to
have as much or more of a fight involved.

Having the UUID easily accessible via sysfs definitely seems like it
would be advantageous to more than just me based on the comments here.  


Xen-devel mailing list