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] problem about changing state to XenbusStateClosed result

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] problem about changing state to XenbusStateClosed resulting in vbd entry removed from xenstore
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 19 May 2006 09:47:43 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Max Zhen <Max.Zhen@xxxxxxx>
Delivery-date: Fri, 19 May 2006 01:48:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060518230034.GE30245@xxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <446CA038.2080009@xxxxxxx> <20060518230034.GE30245@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 19 May 2006, at 00:00, Ewan Mellor wrote:

+ This doesn't seem correct since vbd's are created and destroyed from
Dom0 as part of domain creation 'xm create' or explicitly by executing
'xm block-attach'. Therefore, it would seem that devices should be
removed either when a domU terminates or the device is explicitly
removed from dom0 by 'xm block-detach'.

You could argue that you ought to be able to remove the frontend driver
module, and then load that module again and have all the devices reconnect.
I've no idea whether that would have knock-on consequences though.

I think we really ought to be able to support this, but it hardly sounds a priority. OTOH if it's simply a case of stopping the hotplug scripts from zapping the xenstore entries, and instead do that in the domain-destruction and vbd-remove paths of xend, then maybe it's not so hard to fix. Anyway, I'd certainly consider the current behaviour to be a bug, albeit perhaps a minor one.

 -- Keir

Xen-devel mailing list