From: Atom2 <ariel.atom2@web2web.at>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
David Vrabel <david.vrabel@citrix.com>,
xen-users@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-users] substantial shutdown delay for PV guests with PCI -passthrough
Date: Tue, 22 Apr 2014 14:02:46 +0200 [thread overview]
Message-ID: <53565A66.7090208@web2web.at> (raw)
In-Reply-To: <CAFLBxZYCJ-=HrfS-SacRqc3odPQko=DX=tSWFogbaZXOz4wKHA@mail.gmail.com>
Am 22.04.14 12:44, schrieb George Dunlap:
> On Sat, Apr 19, 2014 at 7:59 PM, Atom2 <ariel.atom2@web2web.at> wrote:
>> Am 19.04.14 02:12, schrieb Konrad Rzeszutek Wilk:
>>> 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).
>>
>> For me it makes no difference timewise whether I issue a
>> xl shutdown guest
>> from dom0 or whether I issue
>> shutdown -h now
>> from a connection (i.e. ssh or screen or console) to the guest. The main
>> difference being that for the latter the delay is visible whereas for the
>> former, the delay is not so obvious because 'xl shutdown guest' from dom0
>> due to its asynchronous nature returns immediately even when the guest is
>> still alive.
>>
>> One difference that I have noticed however is that for the shutdown from
>> _within_ the guest (i.e. shutdown -h now) the state of the guest remains 's'
>> in 'xl list' from the time the "system halted" message appears on screen
>> until the prompt returns in dom0 whereas for a shutdown from dom0 with 'xl
>> shutdown guest' the state changes from 's' to 'ps' for a number of seconds
>> before it is finally gone.
>
> Does it look anything like this?
>
> marc.info/?i=<CAFLBxZbOdU=uSwNBVRTB7_7yhPyRShda0asSOvv9J+xfoGxRnA@mail.gmail.com>
>
> (the log in question is /var/log/xen/xl-$DOMAINNAME.log)
>
> -George
Not really (unless there's a specific command line option required to
get your output) - at least to my eye the messages in my log file look
rather different:
_______________________________________________________________________
Waiting for domain voip (domid 3) to die [pid 2274]
Domain 3 has shut down, reason code 0 0x0
Action for shutdown reason code 0 is destroy
Domain 3 needs to be cleaned up: destroying the domain
libxl: error: libxl_pci.c:1250:do_pci_remove: xc_domain_irq_permission
irq=17
libxl: error: libxl_device.c:1134:libxl__wait_for_backend_deprecated:
Backend /local/domain/0/backend/pci/3/0 not ready (state 7)
libxl: error: libxl_device.c:1138:libxl__wait_for_backend_deprecated: FE
/local/domain/3/device/pci/0 state 6
libxl: error: libxl_pci.c:1250:do_pci_remove: xc_domain_irq_permission
irq=16
libxl: error: libxl_device.c:1134:libxl__wait_for_backend_deprecated:
Backend /local/domain/0/backend/pci/3/0 not ready (state 7)
libxl: error: libxl_device.c:1138:libxl__wait_for_backend_deprecated: FE
/local/domain/3/device/pci/0 state 6
libxl: error: libxl_pci.c:1250:do_pci_remove: xc_domain_irq_permission
irq=23
libxl: error: libxl_device.c:1134:libxl__wait_for_backend_deprecated:
Backend /local/domain/0/backend/pci/3/0 not ready (state 7)
libxl: error: libxl_device.c:1138:libxl__wait_for_backend_deprecated: FE
/local/domain/3/device/pci/0 state 6
libxl: error: libxl_device.c:894:device_backend_callback: unable to
remove device with path /local/domain/0/backend/pci/3/0
libxl: error: libxl.c:1452:devices_destroy_cb: libxl__devices_destroy
failed for 3
Done. Exiting now
Please note: some of my messages may be the result of Ian Jackson's
(debug) patches which are still active in my environment.
Thanks Atom2
prev parent reply other threads:[~2014-04-22 12:02 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
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 [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=53565A66.7090208@web2web.at \
--to=ariel.atom2@web2web.at \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xen-users@lists.xenproject.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).