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? Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 21/03/2011 05:30, "James Harper" <james.harper@bendigoit.com.au> 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. -- Keir> Thanks > > James > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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@lists.xensource.com http://lists.xensource.com/xen-devel