From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] [Xend] Move some backend configuration Date: Tue, 30 Sep 2008 16:09:49 +0100 Message-ID: References: <20080930145818.GC22049@totally.trollied.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080930145818.GC22049@totally.trollied.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Levon Cc: Pascal Bouchareine , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 30/9/08 15:58, "John Levon" 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