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.

Description of problem:
Concurrent migration will hang on  libvirt-0.9.10-6.el6.x86_64.rpm

Version-Release number of selected component (if applicable):
kernel-2.6.32-250.el6.x86_64
qemu-kvm-0.12.1.2-2.262.el6.x86_64
libvirt-0.9.10-6.el6.x86_64

How reproducible:
90%

Steps to Reproduce:
1. Start 15 guests with empty disk
2. Do migration with
# for i in {1..15}; do virsh migrate --live mig-$i qemu+ssh://{target ip}/system --unsafe & sleep 1; done
3. Do virsh list
  
Actual results:
virsh list will hang, and migration will not finished

Expected results:
virsh will not hang, migration succeed without error

Additional info:

Created attachment 572163 [details]
libvirtd.log

Created attachment 572164 [details]
backtrace

How is this different from bug 803186, is the only difference in removing virsh migrate-setmaxdowntime command from the loop?

This is very likely a dup of that bug but I'll wait for the additional info before closing it.

I report it because the bug 803186 is reported on rhel 6.2 but I can only reproduce this bug on rhel6.3, and on rhel6.2 concurrent migration will not cause virsh command hang

It's a race so you were not probably lucky enough to hit it on rhel6.2. I wasn't able to reproduce this bug even on rhel6.3 (until I saw the backtrace and logs).

*** This bug has been marked as a duplicate of bug 803186 ***

Please have a look at bug 803186 comment 17