From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [Xen-users] substantial shutdown delay for PV guests with PCI -passthrough Date: Fri, 18 Apr 2014 20:12:38 -0400 Message-ID: <20140419001237.GA16683@localhost.localdomain> References: <5329A3C0.3000609@web2web.at> <21289.48007.604643.322509@mariner.uk.xensource.com> <532A530D.1050504@web2web.at> <21290.54937.269235.163107@mariner.uk.xensource.com> <532B425F.4010701@web2web.at> <21292.32952.592138.804266@mariner.uk.xensource.com> <532C9556.9070806@web2web.at> <21308.8800.653127.798603@mariner.uk.xensource.com> <533C29FD.1030809@web2web.at> <53519D82.9020002@web2web.at> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <53519D82.9020002@web2web.at> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Atom2 Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Fri, Apr 18, 2014 at 11:47:46PM +0200, Atom2 wrote: > This is just a (very) gentle ping ... or have I missed out on a reply? I ran an PV guest with PCI passthrough this week and it had no trouble - didn't see 10 seconds or so. But I did the shutdown from within the guest (poweroff). What is the kernel you are running as your dom0? Is it the same as frontend? > > Thanks Atom2 > > Am 02.04.14 17:17, schrieb Atom2: > > > >Am 02.04.14 16:44, schrieb Ian Jackson: > >>Atom2 writes ("Re: [Xen-devel] [Xen-users] substantial shutdown delay > >>for PV guests with PCI -passthrough"): > >>>Am 21.03.14 19:11, schrieb Ian Jackson: > >>>>Can you run it again with this, on top of the previous patch, please ? > >>> > >>>Sure, the new output of xl -vvv create -F domain is again attached to > >>>this e-Mail. > >> > >>Sorry for the delay replying. I have been ill :-(. > >Sorry to hear that. Though I noticed your absence from the list I simply > >assumed that you were off on vacation. In any case good to see you back. > >> > >>> > >>>libxl: error: libxl_device.c:1134:libxl__wait_for_backend_deprecated: > >>>Backend /local/domain/0/backend/pci/4/0 not ready (state 7) > >>>libxl: error: libxl_device.c:1138:libxl__wait_for_backend_deprecated: > >>>FE /local/domain/4/device/pci/0 state 6 > >>>libxl: debug: libxl_pci.c:204:libxl__device_pci_remove_xenstore: pci > >>>backend at /local/domain/0/backend/pci/4/0 is not ready > >>>libxl: error: libxl_pci.c:1250:do_pci_remove: > >>>xc_domain_irq_permission irq=16 > >> > >>So the backend here is in state 7 (Reconfiguring), but the frontend is > >>in state 6 (Closed). I think this is a bug in pciback. > >> > >>I looked at drivers/xen/xen-pciback/xenbus.c in Linux 3.13 and found > >>xen_pcibk_frontend_changed which seems to do roughly what I would > >>expect. > >> > >>Has this changed at some point ? > >> > >>Atom, what kernel are you using ? > >All the error messages stem from kernel 3.11.7. In the meantime 3.13.2 > >became stable for gentoo and I installed that a few days ago. I have not > >run the debug output yet or timed the shutdown process, but there's > >still a delay with that kernel and it feels as long as before. I you > >want, I can clearly provide new debug output or timing information. > > > >Thanks Atom2 > >> > >>Thanks, > >>Ian. > >> > >>_______________________________________________ > >>Xen-devel mailing list > >>Xen-devel@lists.xen.org > >>http://lists.xen.org/xen-devel > >> > > > >_______________________________________________ > >Xen-devel mailing list > >Xen-devel@lists.xen.org > >http://lists.xen.org/xen-devel > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel