+++ This bug was initially created as a clone of Bug #599590 +++ Description of problem: Clone of a corresponding bug fixed in RHEL-6... trying out concurrent bi-directional migration causes libvirt to hang. this is reproducible and happened 3 times so far. scenario goes as follows: - 2 running hosts - 2 running vms == vm 1 is on host 1 == vm 2 is on host 2 - using rhev-m - perform concurrent migration meaning: == vm 1 which runs on host 1 is destined to run on host 2 == vm 2 which runs on host 2 is destined to run on host 1
Fix built into libvirt-0.8.2-4.el5
The bug 599590 is reported with vdsm, should this bug be verified with vdms or not, or both ? Thanks YuanDan
The original bug was found during vdsm testing but it still was a bug in libvirt. You don't need vdsm for verification, you can use virsh migrate --p2p for migrating the vms.
tested with RHEL5.6-Server-x86_64-kvm kvm-83-202.el5 kernel-2.6.18-227.el5 libvirt-0.8.2-7.el5 steps to verify - 2 running hosts - 2 running vms == vm 1 is on host 1 == vm 2 is on host 2 - using virsh command to do migration together in the two hosts - perform concurrent migration meaning: == vm 1 which runs on host 1 is destined to run on host 2 == vm 2 which runs on host 2 is destined to run on host 1 [root@dhcp-66-93-70 ~]# virsh migrate --p2p --live hello qemu+tcp://10.66.92.136/system [root@localhost ~]# virsh list --all Id Name State ---------------------------------- - hello shut off 4 test running [root@dhcp-66-92-136 ~]# virsh migrate --p2p --live test qemu+tcp://10.66.93.70/system [root@dhcp-66-92-136 ~]# virsh list --all Id Name State ---------------------------------- 1 hello running - test shut off From the above , we can see the bi-directional migration works fine . After migration , vms keeps running . So set bug status to VERIFIED
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. http://rhn.redhat.com/errata/RHEA-2011-0060.html