From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: force option of xm block-detach Date: Mon, 21 Mar 2011 14:42:22 +0100 Message-ID: <4D8755BE.9010701@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: James Harper , xen devel List-Id: xen-devel@lists.xenproject.org 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