Clone the original bug to qemu-kvm-rhev component for rhel7.1
hit it with qemu-kvm-rhev-2.1.2-8.el7.x86_64
Please try waiting ~15mins after the migration_cancel command is issued and see whether it eventually cancels (I think the TCP timeouts should happen by then).
(In reply to Dr. David Alan Gilbert from comment #3)
> Please try waiting ~15mins after the migration_cancel command is issued and
> see whether it eventually cancels (I think the TCP timeouts should happen by
Yes, after long time, it change to cancelled.
*** Bug 1168790 has been marked as a duplicate of this bug. ***
It is easy to reproduce this bug on ppc64 build, so set Hardware to Unspecified.
Version-Release number of selected component:
Verified on qemu-kvm-rhev-2.3.0-2.el7.x86_64:
/usr/libexec/qemu-kvm -enable-kvm -M pc -smp 4 -m 4G -name rhel6.3-64 -uuid 3f2ea5cd-3d29-48ff-aab2-23df1b6ae213 -drive file=/root/RHEL-Server-7.2-64-virtio.qcow2,cache=none,if=none,rerror=stop,werror=stop,id=drive-virtio-disk0,format=qcow2,aio=native -device virtio-blk-pci,drive=drive-virtio-disk0,id=device-virtio-disk0,bootindex=1 -netdev tap,script=/etc/qemu-ifup,id=netdev0 -device virtio-net-pci,netdev=netdev0,id=device-net0,mac=aa:54:00:11:22:33 -boot order=cd -monitor stdio -usb -device usb-tablet,id=input0 -chardev socket,id=s1,path=/tmp/s1,server,nowait -device isa-serial,chardev=s1 -monitor tcp::1234,server,nowait -vga qxl -global qxl-vga.revision=3 -spice port=5920,disable-ticketing -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -vnc :10 -qmp tcp:0:5555,server,nowait
2. start migration, on des host, drop migration incoming packet with:
iptables -A INPUT -p tcp -d 10.66.84.12 --dport 5556 -j DROP
3. cancel migration on src host, migration cancelled immediately:
(qemu) info migrate
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off
Migration status: cancelled
total time: 0 milliseconds
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.