From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: io.c:164:d25v0 Weird HVM ioemulation status 1. domain_crash called from io.c:165
Date: Fri, 24 Apr 2015 09:31:28 -0400 [thread overview]
Message-ID: <20150424133128.GB9192@l.oracle.com> (raw)
In-Reply-To: <286185080.20150424140236@eikelenboom.it>
On Fri, Apr 24, 2015 at 02:02:36PM +0200, Sander Eikelenboom wrote:
> Hi,
>
> On Xen-unstable I encountered this non stopping logspam while trying to shutdown an HVM domain with
> pci-passthrough:
>
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
And I saw as well with the latest unstable. Hadn't tried to narrow it down.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> (XEN) [2015-04-24 11:55:47.802] domain_crash called from io.c:165
> (XEN) [2015-04-24 11:55:47.802] io.c:164:d25v0 Weird HVM ioemulation status 1.
> etc. etc. etc.
>
> The domain had shutdown perfectly well on earlier occasions, but this time it
> kept running. It did drop from it's assigned 3 vpcu's to 1 vpcu, but it stalled
> there.
> The log spam only stopped by destroying the guest.
>
> Since i haven't seen it before, it's probably hard to replicate.
>
> --
> Sander
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2015-04-24 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 12:02 io.c:164:d25v0 Weird HVM ioemulation status 1. domain_crash called from io.c:165 Sander Eikelenboom
2015-04-24 12:14 ` Olaf Hering
2015-04-24 13:31 ` Konrad Rzeszutek Wilk [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=20150424133128.GB9192@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=linux@eikelenboom.it \
--cc=paul.durrant@citrix.com \
--cc=xen-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.