From: Peter Lieven <pl@dlhnet.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Block Migration Assertion in qemu-kvm 1.2.0
Date: Tue, 18 Sep 2012 12:28:22 +0200 [thread overview]
Message-ID: <50584CC6.2030207@dlhnet.de> (raw)
In-Reply-To: <5057842F.6090506@dlhnet.de>
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
WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlhnet.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Block Migration Assertion in qemu-kvm 1.2.0
Date: Tue, 18 Sep 2012 12:28:22 +0200 [thread overview]
Message-ID: <50584CC6.2030207@dlhnet.de> (raw)
In-Reply-To: <5057842F.6090506@dlhnet.de>
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
next prev parent reply other threads:[~2012-09-18 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-16 10:13 Block Migration Assertion in qemu-kvm 1.2.0 Peter Lieven
2012-09-16 10:13 ` [Qemu-devel] " Peter Lieven
2012-09-17 8:41 ` Kevin Wolf
2012-09-17 8:41 ` Kevin Wolf
2012-09-17 14:35 ` Peter Lieven
2012-09-17 14:35 ` Peter Lieven
2012-09-17 20:12 ` Peter Lieven
2012-09-17 20:12 ` Peter Lieven
2012-09-18 10:28 ` Peter Lieven [this message]
2012-09-18 10:28 ` Peter Lieven
2012-09-18 10:31 ` Kevin Wolf
2012-09-18 10:31 ` Kevin Wolf
2012-09-19 5:49 ` Peter Lieven
2012-09-19 5:49 ` Peter Lieven
2012-09-25 14:00 ` Kevin Wolf
2012-09-17 20:20 ` Peter Lieven
2012-09-17 20:20 ` Peter Lieven
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=50584CC6.2030207@dlhnet.de \
--to=pl@dlhnet.de \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--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.