RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1441165 - Operation failed when migrate VM back to source host unless restart libvirtd
Summary: Operation failed when migrate VM back to source host unless restart libvirtd
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: yafu
URL:
Whiteboard:
: 1442705 1444785 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-11 11:31 UTC by Yanqiu Zhang
Modified: 2017-08-02 01:30 UTC (History)
12 users (show)

Fixed In Version: libvirt-3.2.0-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-02 00:05:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1846 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2017-08-01 18:02:50 UTC

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
Note You need to log in before you can comment on or make changes to this bug.