From: Paolo Bonzini <pbonzini@redhat.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: James Harper <james.harper@bendigoit.com.au>,
xen devel <xen-devel@lists.xensource.com>
Subject: Re: force option of xm block-detach
Date: Mon, 21 Mar 2011 14:42:22 +0100 [thread overview]
Message-ID: <4D8755BE.9010701@redhat.com> (raw)
In-Reply-To: <C9ACBC6D.151DE%keir.xen@gmail.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
prev parent reply other threads:[~2011-03-21 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 5:30 force option of xm block-detach James Harper
2011-03-21 8:27 ` Keir Fraser
2011-03-21 13:42 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8755BE.9010701@redhat.com \
--to=pbonzini@redhat.com \
--cc=james.harper@bendigoit.com.au \
--cc=keir.xen@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).