From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:53753) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TDWtM-0003H9-HS for qemu-devel@nongnu.org; Mon, 17 Sep 2012 04:41:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TDWtG-000242-VL for qemu-devel@nongnu.org; Mon, 17 Sep 2012 04:41:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60043) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TDWtG-000232-N1 for qemu-devel@nongnu.org; Mon, 17 Sep 2012 04:41:14 -0400 Message-ID: <5056E221.8020106@redhat.com> Date: Mon, 17 Sep 2012 10:41:05 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <5055A643.8060505@dlhnet.de> In-Reply-To: <5055A643.8060505@dlhnet.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Block Migration Assertion in qemu-kvm 1.2.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: Paolo Bonzini , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" Am 16.09.2012 12:13, schrieb Peter Lieven: > Hi, > > when trying to block migrate a VM from one node to another, the source > VM crashed with the following assertion: > block.c:3829: bdrv_set_in_use: Assertion `bs->in_use != in_use' failed. > > Is this sth already addresses/known? Not that I'm aware of, at least. Block migration doesn't seem to check whether the device is already in use, maybe this is the problem. Not sure why it would be in use, though, and in my quick test it didn't crash. So we need some more information: What's you command line, did you do anything specific in the monitor with block devices, what does the stacktrace look like, etc.? Kevin