From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Lieven Subject: Re: [Qemu-devel] Block Migration Assertion in qemu-kvm 1.2.0 Date: Tue, 18 Sep 2012 12:28:22 +0200 Message-ID: <50584CC6.2030207@dlhnet.de> References: <5055A643.8060505@dlhnet.de> <5056E221.8020106@redhat.com> <5057842F.6090506@dlhnet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , Paolo Bonzini To: Kevin Wolf Return-path: Received: from ssl.dlhnet.de ([91.198.192.8]:56587 "EHLO ssl.dlh.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751619Ab2IRK2Y (ORCPT ); Tue, 18 Sep 2012 06:28:24 -0400 In-Reply-To: <5057842F.6090506@dlhnet.de> Sender: kvm-owner@vger.kernel.org List-ID: On 09/17/12 22:12, Peter Lieven wrote: > On 09/17/12 10:41, Kevin Wolf wrote: >> 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, it seems that i can very easily force a crash if I cancel a > running block migration. if I understand correctly what happens there are aio callbacks coming in after blk_mig_cleanup() has been called. what is the proper way to detect this in blk_mig_read_cb()? Thanks, Peter