From: Atom2 <ariel.atom2@web2web.at>
To: xen-devel@lists.xen.org
Subject: Re: [Xen-users] substantial shutdown delay for PV guests with PCI -passthrough
Date: Wed, 02 Apr 2014 17:17:17 +0200 [thread overview]
Message-ID: <533C29FD.1030809@web2web.at> (raw)
In-Reply-To: <21308.8800.653127.798603@mariner.uk.xensource.com>
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.
>
>> <NOTE: at this point a 10s pause happens>
>> 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
>
next prev parent reply other threads:[~2014-04-02 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5325B828.1060303@web2web.at>
[not found] ` <1395050430.4122.29.camel@kazak.uk.xensource.com>
[not found] ` <53273B3C.40707@web2web.at>
2014-03-18 10:15 ` [Xen-users] substantial shutdown delay for PV guests with PCI -passthrough Ian Campbell
2014-03-18 13:01 ` Atom2
2014-03-18 15:07 ` Ian Campbell
2014-03-19 0:25 ` Atom2
2014-03-19 11:26 ` Ian Campbell
2014-03-19 13:00 ` Konrad Rzeszutek Wilk
2014-03-19 14:03 ` Atom2
2014-03-19 15:45 ` Ian Jackson
2014-03-20 2:31 ` Atom2
2014-03-20 11:52 ` Ian Jackson
2014-03-20 13:53 ` Pasi Kärkkäinen
2014-03-20 15:28 ` Ian Jackson
2014-03-20 19:34 ` Atom2
2014-03-20 19:32 ` Atom2
2014-03-21 18:11 ` Ian Jackson
2014-03-21 19:39 ` Atom2
2014-04-02 14:44 ` Ian Jackson
2014-04-02 15:17 ` Atom2 [this message]
2014-04-18 21:47 ` Atom2
2014-04-19 0:12 ` Konrad Rzeszutek Wilk
2014-04-19 18:59 ` Atom2
2014-04-22 10:44 ` George Dunlap
2014-04-22 12:02 ` Atom2
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=533C29FD.1030809@web2web.at \
--to=ariel.atom2@web2web.at \
--cc=xen-devel@lists.xen.org \
/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).