From: Sander Eikelenboom <linux@eikelenboom.it>
To: Paul Durrant <paul.durrant@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: io.c:164:d25v0 Weird HVM ioemulation status 1. domain_crash called from io.c:165
Date: Fri, 24 Apr 2015 14:02:36 +0200 [thread overview]
Message-ID: <286185080.20150424140236@eikelenboom.it> (raw)
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.
(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
next reply other threads:[~2015-04-24 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 12:02 Sander Eikelenboom [this message]
2015-04-24 12:14 ` io.c:164:d25v0 Weird HVM ioemulation status 1. domain_crash called from io.c:165 Olaf Hering
2015-04-24 13:31 ` Konrad Rzeszutek Wilk
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=286185080.20150424140236@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=andrew.cooper3@citrix.com \
--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.