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 1278727 - "virsh domjobinfo" hangs on destination host during migration.
Summary: "virsh domjobinfo" hangs on destination host during migration.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-06 09:57 UTC by Fangge Jin
Modified: 2016-11-03 18:30 UTC (History)
4 users (show)

Fixed In Version: libvirt-1.3.3-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 18:30:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
libvirtd log on target host (203.53 KB, application/x-gzip)
2015-11-06 09:57 UTC, Fangge Jin 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2577 0 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2016-11-03 12:07:06 UTC

Description Fangge Jin 2015-11-06 09:57:12 UTC 
Created attachment 1090546 [details]
libvirtd log on target host

Description of problem:
"virsh domjobinfo" hangs on destination host during migration.

Version-Release number of selected component (if applicable):
libvirt-1.2.17-13.el7.x86_64
qemu-kvm-rhev-2.3.0-31.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a running guest on source host.
# virsh list
 Id    Name                           State
----------------------------------------------------
 35    ceph-admin                     running

2.Set the migration speed to a small value: 1
# virsh migrate-setspeed ceph-admin 1

3.Migrate the guest to another host:
# virsh migrate ceph-admin qemu+ssh://10.66.85.92/system --live --verbose
root.85.92's password:
Migration:[1%]

Before migration completed, get the domjobinfo on target host, the command hangs for a while, then returns with error:
# virsh domjobinfo ceph-admin
error: Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainMigratePrepare3Params)

After migration completed, get the domjobinfo on target host again:
# virsh domjobinfo ceph-admin --completed
Job type:         Completed  
Time elapsed:     408155       ms
Time elapsed w/o network: 408144       ms
Data processed:   417.593 MiB
Data remaining:   0.000 B
Data total:       1.102 GiB
Memory processed: 417.593 MiB
Memory remaining: 0.000 B
Memory total:     1.102 GiB
Memory bandwidth: 1.026 MiB/s
Constant pages:   220266      
Normal pages:     106204      
Normal data:      414.859 MiB
Total downtime:   73           ms
Downtime w/o network: 62           ms
Setup time:       22           ms


Actual results:
Can't get domjobinfo on target host before migration completed.

Expected results:
"Get domjobinfo" successfully on target host before migration completed.


Additional info:
"virsh domjobinfo <domain>" can get domjobinfo successfully on source host during migration.
Comment 1 Jiri Denemark 2016-03-01 15:44:12 UTC 
This is fixed upstream by commit v1.3.2-47-g3ecd73c:

commit 3ecd73c4d8962acfbc4bac05bcd47663f2bd791f
Author:     Jiri Denemark <jdenemar>
AuthorDate: Mon Feb 29 12:34:08 2016 +0100
Commit:     Jiri Denemark <jdenemar>
CommitDate: Tue Mar 1 15:59:00 2016 +0100

    qemu: Don't try to fetch migration stats on destination
    
    Migration statistics are not available on the destination host and
    starting a query job during incoming migration is not allowed. Trying to
    do that would result in
    
        Timed out during operation: cannot acquire state change lock (held
        by remoteDispatchDomainMigratePrepare3Params)
    
    error. We should not even try to start the job.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1278727
    
    Signed-off-by: Jiri Denemark <jdenemar>
Comment 2 Mike McCune 2016-03-28 22:45:31 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 4 zhe peng 2016-04-11 08:37:59 UTC 
I can reproduce this.
verified with build:
libvirt-1.3.3-1.el7.x86_64
qemu-kvm-rhev-2.5.0-4.el7.x86_64

step same as bug's description

during the migration, check domjobinfo in target machine.
#virsh domjobinfo test
error: Operation not supported: migration statistics are available only on the source host
worked as expect. move to verified.
Comment 6 errata-xmlrpc 2016-11-03 18:30:27 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://rhn.redhat.com/errata/RHSA-2016-2577.html
Note You need to log in before you can comment on or make changes to this bug.