Bug 1441165

Summary: Operation failed when migrate VM back to source host unless restart libvirtd
Product: Red Hat Enterprise Linux 7 Reporter: Yanqiu Zhang <yanqzhan>
Component: libvirtAssignee: Jiri Denemark <jdenemar>
Status: CLOSED ERRATA QA Contact: yafu <yafu>
Severity: high Docs Contact:
Priority: high    
Version: 7.4CC: dyuan, dzheng, fjin, jdenemar, lizhu, mzhan, pezhang, rbalakri, xuzhang, yafu, yanqzhan, zpeng
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-3.2.0-4.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-02 00:05:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Yanqiu Zhang 2017-04-11 11:31:00 UTC
Description of problem:
Operation failed when migrate VM back to source host unless restart libvirtd

Version-Release number of selected component (if applicable):
libvirt-3.2.0-2.el7.x86_64
qemu-kvm-rhev-2.8.0-6.el7.x86_64

How reproducible:
100%

Steps to Reproduce:

1.prepare migration env

2.start a vm on source
[root@source ~]# virsh start V
Domain V started

[root@source ~]# virsh dumpxml V|grep graphic
    <graphics type='spice' port='5900' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>
...


3.migrate from source to target
[root@source ~]# virsh migrate V --live qemu+ssh://target_ip/system --unsafe --verbose
Migration: [100 %]

4.try to migrate from target to source
[root@target ~]# virsh list --all
 Id    Name                           State
----------------------------------------------------
 22    V                              running

[root@target ~]# virsh dumpxml V|grep graphic -A3
    <graphics type='spice' port='5900' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>
...

[root@target ~]# virsh migrate V --live qemu+ssh://source_ip/system --unsafe --verbose
error: operation failed: migration job: is not active

5.restart libvirtd and try to migrate back again:
[root@target ~]# systemctl restart libvirtd
[root@target ~]# virsh migrate V --live qemu+ssh://source_ip/system --unsafe --verbose
Migration: [100 %]


Actual results:
As in step4, operation failed when migrate VM back to source. 
In step5, after restart libvirtd, the migration back operation can succeed.

Expected results:
VM should be migrated back to source host successfully, without restart libvirtd.


Additional info:

Comment 4 Jiri Denemark 2017-04-11 12:15:50 UTC
This seems to be similar to the issue reported in bug 1439841.

Comment 5 Xuesong Zhang 2017-04-18 10:03:09 UTC
*** Bug 1442705 has been marked as a duplicate of this bug. ***

Comment 6 Yanqiu Zhang 2017-04-18 10:54:58 UTC
the graphics xml are redundant in comment0 description, this issue has no relationship with graphics, please ignore it.

Comment 7 Jiri Denemark 2017-04-26 20:04:17 UTC
*** Bug 1444785 has been marked as a duplicate of this bug. ***

Comment 8 Jiri Denemark 2017-04-28 14:31:18 UTC
Patch sent upstream for review: https://www.redhat.com/archives/libvir-list/2017-April/msg01479.html

Comment 9 Jiri Denemark 2017-05-02 10:30:51 UTC
This is now fixed upstream by

commit fc48fc7930f560c4341f4afe1285848dfdb60278
Refs: v3.3.0-rc1-2-gfc48fc793
Author:     Jiri Denemark <jdenemar>
AuthorDate: Fri Apr 28 15:56:44 2017 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Tue May 2 12:26:35 2017 +0200

    qemu: Don't reset "events" migration capability

    When creating v3.2.0-77-g8be3ccd04 commit, I completely forgot that one
    migration capability is very special. It's the "events" capability which
    tells QEMU to report "MIGRATION" events. Since libvirt always wants the
    events, it is enabled in qemuConnectMonitor and the rest of the code
    should not touch it.

    https://bugzilla.redhat.com/show_bug.cgi?id=1439841
    https://bugzilla.redhat.com/show_bug.cgi?id=1441165

    Messed-up-by: Jiri Denemark <jdenemar>
    Signed-off-by: Jiri Denemark <jdenemar>

Comment 12 yafu 2017-05-05 05:39:27 UTC
Reproduced with libvirt-3.2.0-2.el7.x86_64.

Verified pass with libvirt-3.2.0-3.el7.x86_64.

Comment 13 yafu 2017-05-05 08:00:25 UTC
(In reply to yafu from comment #12)
> Reproduced with libvirt-3.2.0-2.el7.x86_64.
> 
> Verified pass with libvirt-3.2.0-3.el7.x86_64.


Sorry for the mistake. 

The bug is verified pass with libvirt-3.2.0-4.el7.x86_64.

Comment 14 errata-xmlrpc 2017-08-02 00:05:54 UTC
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.

https://access.redhat.com/errata/RHEA-2017:1846

Comment 15 errata-xmlrpc 2017-08-02 01:30:05 UTC
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.

https://access.redhat.com/errata/RHEA-2017:1846