qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 17 Sep 2012 16:35:05 +0200	[thread overview]
Message-ID: <50573519.7090206@dlhnet.de> (raw)
In-Reply-To: <5056E221.8020106@redhat.com>

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.
It seems that it only happens if a vServer that has been block migrated 
earlier is block migrated the next time.
> 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.?
Here is my cmdline:
/usr/bin/qemu-kvm-1.2.0  -net 
tap,vlan=164,script=no,downscript=no,ifname=tap0  -net nic,vlan
=164,model=e1000,macaddr=52:54:00:ff:01:19   -drive 
format=host_device,file=/dev/7cf58855099771c2/lieven-storage-migration-t-hd0,if=virtio,cache=none,aio=nat
ive  -m 2048 -smp 2,sockets=1,cores=2,threads=1  -monitor 
tcp:0:4001,server,nowait -vnc :1 -qmp tcp:0:3001,server,nowait  -name 
'lieven-storage-migration-test'  -boot or
der=dc,menu=off  -k de  -incoming tcp:172.21.55.34:5001  -pidfile 
/var/run/qemu/vm-254.pid  -mem-path /hugepages  -mem-prealloc  -rtc 
base=utc -usb -usbdevice tablet -no
-hpet -vga cirrus  -cpu host,+x2apic,model_id='Intel(R) Xeon(R) 
CPU           L5640  @ 2.27GHz',-tsc

I have seen other errors as well in the meantime:
block-migration.c:471: flush_blks: Assertion `block_mig_state.read_done 
 >= 0' failed.
qemu-kvm-1.2.0[27851]: segfault at 7f00746e78d7 ip 00007f67eca6226d sp 
00007fff56ae3340 error 4 in qemu-system-x86_64[7f67ec9e9000+418000]

I will now try to catch the situation in the debugger.

Thanks,
Peter

> Kevin

  reply	other threads:[~2012-09-17 14:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-16 10:13 [Qemu-devel] Block Migration Assertion in qemu-kvm 1.2.0 Peter Lieven
2012-09-17  8:41 ` Kevin Wolf
2012-09-17 14:35   ` Peter Lieven [this message]
2012-09-17 20:12   ` Peter Lieven
2012-09-18 10:28     ` Peter Lieven
2012-09-18 10:31       ` Kevin Wolf
2012-09-19  5:49         ` Peter Lieven
2012-09-25 14:00           ` Kevin Wolf
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=50573519.7090206@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).