From: Amos Kong <akong@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: owasserm@redhat.com, aliguori@us.ibm.com, mst@redhat.com,
juzhang@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] migrate cancel bug in latest qemu upstream
Date: Mon, 18 Mar 2013 21:20:03 +0800 [thread overview]
Message-ID: <20130318132003.GA4153@t430s.nay.redhat.com> (raw)
In-Reply-To: <20130312025854.GA4876@t430s.nay.redhat.com>
On Tue, Mar 12, 2013 at 10:58:54AM +0800, Amos Kong wrote:
> Hi quintela, I found a migrate bug in Autotest result, not sure if
> it's already known.
>
> | commit fa3889162ff724d09eb6b6bd06ba54769100a77f
> | Merge: 6e72a00 a4960ef
> | Author: Anthony Liguori <aliguori@us.ibm.com>
> | Date: Sun Mar 10 20:39:17 2013 -0500
>
Bug was introduced between v1.1.0..v1.2.0
----
This bug could not be reproduced in current latest qemu.git
| commit 225dc991b03f0f034aa348f5cf499de9d0979107
| Author: Cornelia Huck <cornelia.huck@de.ibm.com>
| Date: Fri Mar 15 10:57:40 2013 +0100
|
| s390: Fix cpu refactoring fallout.
|
> It can be caught by migrate.mig_cancel case in Autotest framework.
> Manual reproduce method: cancel migrate before migration completes
>
> (src monitor) migrate -d tcp:0:1234
> (src monitor) migrate cancel
>
> Destination vm exits expectedly
> qemu: warning: error while loading state section id 2
>
> Problem:
> The migrate status of source vm is 'failed' (it should be 'canceled')
> (monitor hmp1) Response to 'info migrate'
> (monitor hmp1) capabilities: xbzrle: off
> (monitor hmp1) Migration status: failed
> (monitor hmp1) total time: 0 milliseconds
>
>
> Long cmdline: (can reproduce)
> # qemu-system-x86_64 --enable-kvm -name 'vm0' -nodefaults -chardev
> socket,id=serial_id_serial1,path=/tmp/serial-serial1-20130311-182651-kfslPrch,server,nowait
> -device isa-serial,chardev=serial_id_serial1 -chardev
> socket,id=seabioslog_id_20130311-182651-kfslPrch,path=/tmp/seabios-20130311-182651-kfslPrch,server,nowait
> -device isa-debugcon,chardev=seabioslog_id_20130311-182651-kfslPrch,iobase=0x402
> -device ich9-usb-uhci1,id=usb1 -drive
> file='/tmp/kvm_autotest_root/images/RHEL-Server-6.3-64-virtio.qcow2',if=none,id=virtio0
> -device virtio-blk-pci,drive=virtio0 -device
> e1000,netdev=idkrCwff,mac='9a:87:88:89:8a:8b',id='idxiFFqe' -netdev
> tap,id=idkrCwff -m 2048 -smp 4,maxcpus=4,cores=1,threads=1,sockets=4
> -cpu 'Penryn' -M pc -device
> usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 -vnc :1 -vga std -rtc
> base=utc,clock=host,driftfix=none -boot order=cdn,once=c,menu=off
>
> Simple cmdline: (can reproduce)
> # qemu-system-x86_64 --enable-kvm
> /tmp/kvm_autotest_root/images/RHEL-Server-6.3-64-virtio.qcow2 -m
> 2048 -vnc :1 -monitor stdio -net none
>
> Thanks, Amos
next prev parent reply other threads:[~2013-03-18 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 2:58 [Qemu-devel] migrate cancel bug in latest qemu upstream Amos Kong
2013-03-18 13:20 ` Amos Kong [this message]
2013-03-19 4:49 ` Amos Kong
2013-03-19 9:39 ` Paolo Bonzini
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=20130318132003.GA4153@t430s.nay.redhat.com \
--to=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=juzhang@redhat.com \
--cc=mst@redhat.com \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).