From: "Marcin Gibuła" <m.gibula@beyond.pl>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu 2.0, deadlock in block-commit
Date: Thu, 22 May 2014 23:43:04 +0200 [thread overview]
Message-ID: <537E6F68.1010100@beyond.pl> (raw)
In-Reply-To: <537E6B51.306@redhat.com>
>> I've encountered deadlock in qemu during some stress testing. The test
>> is making snapshots, committing them and constantly quering for block
>> job info.
>
> What is the exact command you used for triggering the block-commit? Was
> it via direct HMP or QMP, or indirect via libvirt?
Via libvirt.
> Were you trying to
> commit the active layer?
No. Commit was to intermediate file. I'm aware that libvirt does not
support active layer commit yet.
Plus, judging from backtrace, hang seems to be deep inside qemu. The VM
is unresponsive after this.
--
mg
next prev parent reply other threads:[~2014-05-22 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 20:49 [Qemu-devel] qemu 2.0, deadlock in block-commit Marcin Gibuła
2014-05-22 21:05 ` Marcin Gibuła
2014-05-23 8:19 ` Paolo Bonzini
2014-05-23 8:21 ` Marcin Gibuła
2014-05-23 9:25 ` Marcin Gibuła
2014-05-23 12:29 ` Kevin Wolf
2014-05-23 12:38 ` Marcin Gibuła
2014-05-23 13:14 ` Marcin Gibuła
2014-05-23 13:18 ` Marcin Gibuła
2014-05-23 22:02 ` Marcin Gibuła
2014-05-22 21:25 ` Eric Blake
2014-05-22 21:43 ` Marcin Gibuła [this message]
2014-05-23 12:58 ` Stefan Hajnoczi
2014-05-23 16:25 ` Marcin Gibuła
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=537E6F68.1010100@beyond.pl \
--to=m.gibula@beyond.pl \
--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).