This bug has been copied from bug #659310 and has been proposed
to be backported to 6.0 z-stream (EUS).
Fixed in libvirt-0.8.1-27.el6_0.2
I can not reproduce this bug on old version - libvirt-0.8.1-27.el6.x86_64.
Here is my steps:
1. Individually create a vm on 2 server.
2. On one of two servers, do "virsh list" repeatly
# while [ "1" ]; do virsh list --all; sleep 1; done
3. Running concurrent bidirectional migration.
On server 1:
# virsh migrate --p2p vm1 qemu+ssh://server2/system
On server 2:
# virsh migrate --p2p vm2 qemu+ssh://server2/system
4. Check the output of step 2, virsh list works fine.
Is there some steps missing?
(In reply to comment #5)
> I can not reproduce this bug on old version - libvirt-0.8.1-27.el6.x86_64.
> Here is my steps:
> 1. Individually create a vm on 2 server.
> 2. On one of two servers, do "virsh list" repeatly
> # while [ "1" ]; do virsh list --all; sleep 1; done
> 3. Running concurrent bidirectional migration.
> On server 1:
> # virsh migrate --p2p vm1 qemu+ssh://server2/system
> On server 2:
> # virsh migrate --p2p vm2 qemu+ssh://server2/system
> 4. Check the output of step 2, virsh list works fine.
> Is there some steps missing?
well, it requires larger scale then 2 vms..
I did it with concurrent migration of 20 vms (10 on each side).
this bug is consistent in our environment, and was a test blocker for quit some time (till we got a fix).
Verify this bug in plain libvirt environment (libvirt-0.8.1-27.el6_0.2.x86_64), this bug is fixed.
Steps is almost the same as comments 5, only the difference is concurrent migration of 20 vms (10 on each side).
Thanks for Haim's help.
verified it PASSED on build :
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
A deadlock occurred in the libvirt service when running concurrent bidirectional migration because certain calls did not release their local driver lock before issuing an RPC (Remote Procedure Call) call on a remote libvirt daemon. A deadlock no longer occurs between two communicating libvirt daemons.