From: Peter Lieven <pl@dlh.net>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Qemu-KVM 0.12.3 and Multipath -> Assertion
Date: Mon, 03 May 2010 23:26:44 +0200 [thread overview]
Message-ID: <4BDF3F94.1080608@dlh.net> (raw)
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.
Any ideas? I remember this was working with earlier kernel/kvm/qemu
versions.
Thanks,
Peter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlh.net>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu-KVM 0.12.3 and Multipath -> Assertion
Date: Mon, 03 May 2010 23:26:44 +0200 [thread overview]
Message-ID: <4BDF3F94.1080608@dlh.net> (raw)
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.
Any ideas? I remember this was working with earlier kernel/kvm/qemu
versions.
Thanks,
Peter
next reply other threads:[~2010-05-03 21:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 21:26 Peter Lieven [this message]
2010-05-03 21:26 ` [Qemu-devel] Qemu-KVM 0.12.3 and Multipath -> Assertion Peter Lieven
2010-05-04 5:38 ` André Weidemann
2010-05-04 5:38 ` [Qemu-devel] " André Weidemann
2010-05-04 8:35 ` [Qemu-devel] " Kevin Wolf
2010-05-04 8:35 ` Kevin Wolf
2010-05-04 11:38 ` Peter Lieven
2010-05-04 11:38 ` Peter Lieven
2010-05-04 12:20 ` Kevin Wolf
2010-05-04 12:20 ` Kevin Wolf
2010-05-04 13:42 ` Peter Lieven
2010-05-04 13:42 ` Peter Lieven
2010-05-04 14:01 ` Kevin Wolf
2010-05-04 14:01 ` Kevin Wolf
2010-05-04 17:07 ` Christoph Hellwig
2010-05-18 11:13 ` Peter Lieven
2010-05-18 12:14 ` Kevin Wolf
2010-05-18 12:14 ` Kevin Wolf
2010-05-12 14:01 ` qemu-kvm hangs if multipath device is queing (was: Re: [Qemu-devel] Qemu-KVM 0.12.3 and Multipath -> Assertion) Peter Lieven
2010-05-14 9:26 ` qemu-kvm hangs if multipath device is queing Kevin Wolf
2010-05-14 9:26 ` [Qemu-devel] " Kevin Wolf
2010-05-18 11:10 ` Peter Lieven
2010-05-18 11:10 ` [Qemu-devel] " Peter Lieven
2010-05-18 13:22 ` Kevin Wolf
2010-05-18 13:22 ` [Qemu-devel] " Kevin Wolf
2010-05-19 7:29 ` Christoph Hellwig
2010-05-19 7:29 ` [Qemu-devel] " Christoph Hellwig
2010-05-19 7:48 ` Kevin Wolf
2010-05-19 7:48 ` [Qemu-devel] " Kevin Wolf
2010-05-19 8:18 ` Peter Lieven
2010-05-19 8:18 ` [Qemu-devel] " Peter Lieven
2010-05-23 10:30 ` Peter Lieven
2010-05-08 9:53 ` [Qemu-devel] Qemu-KVM 0.12.3 and Multipath -> Assertion André Weidemann
2010-05-08 9:53 ` André Weidemann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BDF3F94.1080608@dlh.net \
--to=pl@dlh.net \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.