WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Where do xenstore entries get removed during "xm block-detac

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Where do xenstore entries get removed during "xm block-detach"?
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Thu, 18 Nov 2010 15:38:08 +0000
Delivery-date: Thu, 18 Nov 2010 07:39:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>