From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>, qemu-block@nongnu.org
Cc: qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] strange crash in tracked_request_begin
Date: Mon, 7 Mar 2016 14:35:21 +0100 [thread overview]
Message-ID: <56DD8399.1000504@redhat.com> (raw)
In-Reply-To: <56DD7414.9080306@de.ibm.com>
On 07/03/2016 13:29, Christian Borntraeger wrote:
> Folks,
>
> I had a crash of a qemu guest in tracked_request_begin.
> The testcase was a guest with ramdisk/kernel that reboots in a
> loop. (about 10 times per second) with a single null-co disk
> attached.
Does it use a separate iothread?
Paolo
next prev parent reply other threads:[~2016-03-07 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 12:29 [Qemu-devel] strange crash in tracked_request_begin Christian Borntraeger
2016-03-07 13:35 ` Paolo Bonzini [this message]
2016-03-07 13:40 ` Christian Borntraeger
2016-03-07 17:01 ` Stefan Hajnoczi
2016-03-07 19:00 ` Christian Borntraeger
2016-03-08 10:06 ` Stefan Hajnoczi
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=56DD8399.1000504@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).