From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: xl shutdown --wait "racy" Date: Wed, 16 Apr 2014 13:08:39 -0400 Message-ID: <20140416170839.GB26054@phenom.dumpdata.com> References: <415828617.20140416160821@eikelenboom.it> <20140416151934.GA27066@phenom.dumpdata.com> <1022190423.20140416172157@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1022190423.20140416172157@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sander Eikelenboom Cc: xen-devel , Ian Jackson , Ian Campbell List-Id: xen-devel@lists.xenproject.org On Wed, Apr 16, 2014 at 05:21:57PM +0200, Sander Eikelenboom wrote: > > Wednesday, April 16, 2014, 5:19:34 PM, you wrote: > > > On Wed, Apr 16, 2014 at 04:08:21PM +0200, Sander Eikelenboom wrote: > >> Hi Ian (C|J) Konrad, > >> > >> I'm currently trying to workaround the pci-(detach|assignable-remove) issues i > >> reported earlier. > >> > >> The workaround i thought of was: > >> - shutting down the guest > >> - starting it without 1 of the original devices passed through > >> - use xl pci-assignable-remove and bind the device to the dom0 driver. > >> > >> But during this i noticed that a "xl shutdown --wait" does wait .. but returns: > >> - Before the domain is removed from for instance "xl list", it still listed there in > >> "--ps--" state. > >> - before pciback has done it's restore config space magic. > > > Which reminds me - when you do this - are you (or any processes) in the /sysfs directory? > > I've been having a hard-time reproducing the issue. Sometimes I see it, but then if I try > > again the problem does not show up again. > > When i do *what* ? (it's not exactly clear if you are referring to the problem > i'm trying to workaround .. or the problems i'm finding when trying to > workaround :-) ) Whoa. Looking back at my response it is pretty vague. I was refering to the http://lists.xen.org/archives/html/xen-devel/2014-04/msg02237.html issue. But that is unrelated to this problem you are reporting so lets just skip my question.