From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: [Qemu-devel] Qemu-KVM 0.12.3 and Multipath -> Assertion Date: Tue, 04 May 2010 10:35:16 +0200 Message-ID: <4BDFDC44.9030808@redhat.com> References: <4BDF3F94.1080608@dlh.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Peter Lieven Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44386 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755801Ab0EDIfu (ORCPT ); Tue, 4 May 2010 04:35:50 -0400 In-Reply-To: <4BDF3F94.1080608@dlh.net> Sender: kvm-owner@vger.kernel.org List-ID: Am 03.05.2010 23:26, schrieb Peter Lieven: > 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 != (uint8_t)-1' failed. > > after the multipath has reestablisched at least one path. Can you get a stack backtrace with gdb? > Any ideas? I remember this was working with earlier kernel/kvm/qemu > versions. If it works in the same setup with an older qemu version, bisecting might help. Kevin