qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Debugging io deadlock
Date: Fri, 8 Dec 2017 11:01:44 +0000	[thread overview]
Message-ID: <20171208110144.GI23880@stefanha-x1.localdomain> (raw)
In-Reply-To: <alpine.BSF.2.21.1712051856040.96903@zero.eik.bme.hu>

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

On Tue, Dec 05, 2017 at 07:35:36PM +0100, BALATON Zoltan wrote:
> On Tue, 5 Dec 2017, Stefan Hajnoczi wrote:
> > On Mon, Dec 04, 2017 at 08:22:48PM +0100, BALATON Zoltan wrote:
> I don't really know what to look for
> so if anyone has any more ideas then please share.

I don't have a specific idea, but two general techniques for debugging
guest hangs:

1. Enable tracing or add printfs to monitor hardware register writes and
   interrupts.  This way you can figure out which devices were most
   recently accessed.  They are probably involved in the hang.

2. Peek at QEMU device state from GDB.  For example, look at virtio
   device vrings to see which requests are currently in-flight.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      reply	other threads:[~2017-12-08 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 19:22 [Qemu-devel] Debugging io deadlock BALATON Zoltan
2017-12-05 13:54 ` Stefan Hajnoczi
2017-12-05 18:35   ` BALATON Zoltan
2017-12-08 11:01     ` Stefan Hajnoczi [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=20171208110144.GI23880@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=balaton@eik.bme.hu \
    --cc=qemu-devel@nongnu.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).