Re: [Xen-devel] [PATCH] [Xend] Move some backend configuration

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel