From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46999)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1WnsHz-0000Um-Bq
	for qemu-devel@nongnu.org; Fri, 23 May 2014 12:25:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1WnsHr-00067r-TL
	for qemu-devel@nongnu.org; Fri, 23 May 2014 12:25:47 -0400
Received: from mx.beyond.pl ([92.43.117.49]:33767)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <m.gibula@beyond.pl>) id 1WnsHr-00067j-Mp
	for qemu-devel@nongnu.org; Fri, 23 May 2014 12:25:39 -0400
Message-ID: <537F767B.9090206@beyond.pl>
Date: Fri, 23 May 2014 18:25:31 +0200
From: =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= <m.gibula@beyond.pl>
MIME-Version: 1.0
References: <537E62CE.2050302@beyond.pl>
	<20140523125847.GD5990@stefanha-thinkpad.hitronhub.home>
In-Reply-To: <20140523125847.GD5990@stefanha-thinkpad.hitronhub.home>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] qemu 2.0, deadlock in block-commit
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

> If you see a pending request on a RADOS block device (rbd) then it would
> be good to dig deeper into QEMU's block/rbd.c driver to see why it's not
> completing that request.
>
> Are you using qcow2 on top of rbd?

Hi,
I've already recreated this without rbd and with stock qemu 2.0.

-- 
mg