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] [Xend] Move some backend configuration

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [Xend] Move some backend configuration
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 30 Sep 2008 16:09:49 +0100
Cc: Pascal Bouchareine <pascal@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 30 Sep 2008 08:10:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080930145818.GC22049@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckjDpTQ0yKZzo8BEd2zgAAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] [Xend] Move some backend configuration
User-agent: Microsoft-Entourage/
On 30/9/08 15:58, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

>> Which guaranteed API would that be? These paths are private to the toolstack
>> implementation. Perhaps the only exception is the
> Precisely the problem, there's absolutely no idea or indication what is
> and isn't private. Thus you get libvirt looking in places it maybe
> shouldn't, but how are they supposed to know?
> I'm pretty sure this patch breaks libvirt again.

I don't really see why it would. Beyond the console-client-to-daemon
interface change (which we can make not depend on the /vm_path stuff) the
rest is changing things which I believe are internal to xend.

If libvirt is really going in at this private state, perhaps we could patch
xend so that it writes to the new locations *in addition to* the old
locations. It then has its own guaranteed-private and -consistent state,
while libvirt can still read from old locations.

 -- Keir

Xen-devel mailing list