From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Alexander Graf <agraf@suse.de>
Cc: Waldemar Brodkorb <mail@waldemar-brodkorb.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-system-sparc64 hang (possibly virtio related?) with 2.1
Date: Wed, 03 Sep 2014 12:38:41 -0500 [thread overview]
Message-ID: <871trsfvtq.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140903104121.GF28095@stefanha-thinkpad.redhat.com>
Stefan Hajnoczi <stefanha@gmail.com> writes:
> On Tue, Sep 02, 2014 at 02:12:45PM +0100, Mark Cave-Ayland wrote:
>> Fortunately I can reproduce the issue with a debug-enabled build of
>> qemu-system-sparc64, and I've posted a backtrace obtained during the hung
>> state at http://www.ilande.co.uk/tmp/sparc64-gdb-bt.txt. I can't see
>> anything too obvious, other than that the ppoll() could possibly be waiting
>> for a bad file descriptor?
>
> The backtrace looks like a normal QEMU run. Nothing obvious there.
>
> This suggests the QEMU monitor is still operational and the guest is
> still executing code.
>
> Does the I/O time out inside the guest? Normally messages are printed
> in dmesg if I/O requests are pending for too long.
I am also finding this on ppc64. The system hang even with virtio-9p, so
it may not be virtio blk related. git bisect is complicated because few
commits in between cause other boot failures with ppc64.
-aneesh
next prev parent reply other threads:[~2014-09-03 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 13:12 [Qemu-devel] qemu-system-sparc64 hang (possibly virtio related?) with 2.1 Mark Cave-Ayland
2014-09-03 10:41 ` Stefan Hajnoczi
2014-09-03 17:38 ` Aneesh Kumar K.V [this message]
2014-09-03 21:21 ` Aneesh Kumar K.V
2014-09-03 22:20 ` Alexander Graf
2014-09-03 23:13 ` Aneesh Kumar K.V
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=871trsfvtq.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=mail@waldemar-brodkorb.de \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).