From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41588) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wnalm-0004Q9-Hg for qemu-devel@nongnu.org; Thu, 22 May 2014 17:43:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wnalf-0002Wl-0Z for qemu-devel@nongnu.org; Thu, 22 May 2014 17:43:22 -0400 Received: from mx.beyond.pl ([92.43.117.49]:57716) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wnale-0002Wd-Q6 for qemu-devel@nongnu.org; Thu, 22 May 2014 17:43:14 -0400 Received: from localhost (localhost [127.0.0.1]) by mx.beyond.pl (Postfix) with ESMTP id 427652A05 for ; Thu, 22 May 2014 23:43:10 +0200 (CEST) Received: from mx.beyond.pl ([127.0.0.1]) by localhost (mw.beyond.pl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnW43yj5nM6y for ; Thu, 22 May 2014 23:43:09 +0200 (CEST) Received: from [192.168.1.121] (src75-20.unii.maverick.com.pl [194.187.75.20]) (Authenticated sender: m.gibula@beyond.pl) by mx.beyond.pl (Postfix) with ESMTPSA id D567BC9E for ; Thu, 22 May 2014 23:43:09 +0200 (CEST) Message-ID: <537E6F68.1010100@beyond.pl> Date: Thu, 22 May 2014 23:43:04 +0200 From: =?UTF-8?B?TWFyY2luIEdpYnXFgmE=?= MIME-Version: 1.0 References: <537E62CE.2050302@beyond.pl> <537E6B51.306@redhat.com> In-Reply-To: <537E6B51.306@redhat.com> 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org >> 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