Xen devel - Nov 2010 - Where do xenstore entries get removed during "xm block-detach"?

In trying to find out why, other than for file/tap, tap2 detaches leave
/vm/<id>/device/tap2/* around (which I assume is [part of] the
reason one can''t later run block-attach again for the same device), I
tried to locate where these get removed for file/tap devices, and I
can only see them getting removed once during block-attach
(presumably for cleanup purposes) in xstransact._remove.

xl, as far as I was able to see, doesn''t properly attach/detach
altogether, and mixing xl and xm doesn''t seem to work either
(based on a seemingly successful "xl block-attach" followed by
a seemingly successful "xl block.detach", which left the device
visible, followed by an unsuccessful "xm block-detach").
Shouldn''t that all be more consistent?

Thanks for pointers, Jan


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

Jan Beulich writes ("[Xen-devel] Where do xenstore entries get removed
during "xm block-detach"?"):
> and mixing xl and xm doesn''t seem to work either
Yes, if mixing xl and xm works then it''s by luck rather than design.
(Although it can be a very useful piece of luck.)

I think we need to keep it working at least roughly as well as it does
right now, because there is a potential xend to libxl migration path
which involves stopping xend and then using "xl migrate".

Ian.

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