From: =?ISO-8859-1?Q?Andr=E9_Weidemann?= <Andre.Weidemann@web.de>
Subject: Re: Qemu-KVM 0.12.3 and Multipath -> Assertion
Date: Tue, 04 May 2010 07:38:09 +0200
Message-ID: <4BDFB2C1.5050802@web.de>
References: <4BDF3F94.1080608@dlh.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1;
	format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
To: Peter Lieven <pl@dlh.net>
Return-path: <kvm-owner@vger.kernel.org>
Received: from fmmailgate01.web.de ([217.72.192.221]:34771 "EHLO
	fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751352Ab0EDFiP (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 4 May 2010 01:38:15 -0400
In-Reply-To: <4BDF3F94.1080608@dlh.net>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi Peter,
On 03.05.2010 23:26, Peter Lieven wrote:

> Hi Qemu/KVM Devel Team,
>
> i'm using qemu-kvm 0.12.3 with latest Kernel 2.6.33.3.
> As backend we use open-iSCSI with dm-multipath.
>
> Multipath is configured to queue i/o if no path is available.
>
> If we create a failure on all paths, qemu starts to consume 100%
> CPU due to i/o waits which is ok so far.
>
> 1 odd thing: The Monitor Interface is not responding any more ...
>
> What es a really blocker is that KVM crashes with:
> kvm: /usr/src/qemu-kvm-0.12.3/hw/ide/internal.h:507: bmdma_active_if:
> Assertion `bmdma->unit !=3D (uint8_t)-1' failed.
>
> after the multipath has reestablisched at least one path.
>
> Any ideas? I remember this was working with earlier kernel/kvm/qemu
> versions.


I have the same issue on my machine, although I am using local storage=20
(LVM or a physical disk) to write my data to.
I reported the "Assertion failed" on March 17th to the list. Marcello=20
and Avi had asked some question back then, but I don't know if they hav=
e=20
come up with a fix for it.

Regards
  Andr=E9