From: Keir Fraser Subject: Re: [PATCH] Add a --force option to detach operations Date: Thu, 14 Dec 2006 13:29:43 +0000 Message-ID: References: <5d6222a80612140452k5a90bd2ep4a5dd0e59698f9e0@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5d6222a80612140452k5a90bd2ep4a5dd0e59698f9e0@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Glauber de Oliveira Costa , Keir Fraser Cc: xen-devel@lists.xensource.com, Glauber de Oliveira Costa List-Id: xen-devel@lists.xenproject.org On 14/12/06 12:52, "Glauber de Oliveira Costa" wrote: > How can we be more brutal than that ? The only non-brutal thing I've put there > is denying disconnection when still in Connected state. But if for > some reason the frontend does not want to disconnect, then the tools > have no power over it. It can simply crash guest. > > Example: attach a device, mount it at guest, and try to detach it > using --force. It should not force it, as it crashes the guest. Don't use --force if you don't know what you're doing is a reasonable caveat. You're on flakey ground if you have to use it in any case as something is obviously screwed. -- Keir