[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: force option of xm block-detach


  • To: Keir Fraser <keir.xen@xxxxxxxxx>
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
  • Date: Mon, 21 Mar 2011 14:42:22 +0100
  • Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 21 Mar 2011 06:43:00 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=rBuumWBpqX9JxlTrhLQZgkczHqqC5Z9OJcVWtTaMTncnGi/LjQj5pgSlAjUERU5g9i Tl7MsQIucCuReAj3zoHW1Nws6l5DAQ5rKHetZCBXp1MZdf+0Jn8YNKQfzfftOkCguSDa gK4fKio6LLdaQtSouDq7NEmUJJ4Il6wc7xd8A=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 03/21/2011 09:27 AM, Keir Fraser wrote:
>  How does the 'force' option to block-detach differ to not using it? Can
>  DomU PV drivers tell if this is a forceful detach request?

I believe it means after a timeout we will simply delete the xenstore info
relating to the VBD, rather than wait an arbitrary time for the xenbus
connection to get driven into disconnected state. Thus it's not something
that is made visible to frontend/backend drivers.

That's correct, the drivers just see it as a transition to XenbusStateUnknown.

Paolo

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.