Hide Forgot
Description of problem: Migration will failed with "error: server closed connection" when restart libvirt on source host during live migration. Version-Release number of selected component (if applicable): libvirt-0.8.2-20.el5 kvm-qemu-img-83-232.el5 kernel-2.6.18-259.el5 How reproducible: 5/5 Steps to Reproduce: 1.Execute that commands on source and targect hosts. # iptables -F # mount 10.66.5.181:/var/lib/libvirt/images/ /mnt 2. Define and start a domain. # virsh start win7 3. Start a live migration. # virsh migrate --live win7 qemu+ssh://10.66.5.181/system 4. While the migration is happening, reboot libvirtd on the source of the migration. # service libvirtd restart Actual results: Migration will failed with "error: server closed connection"when restart libvirt on source host during live migration. Expected results: The migration should finish successfully.
Could reproduce this bug on the following components of rh5.6: kernel-2.6.18-238.el5 libvirt-0.8.2-15.el5 kvm-83-224.el5 virt-manager-0.6.1-13.el5 Steps: 1. build the environment of migration; #iptables -F #setsebool -P virt_use_nfs 1 2. Define and start a domain. # virsh start rh5 3. Start a live migration. # virsh migrate --live rh5 qemu+ssh://10.66.6.149/system 4. While the migration is happening, reboot libvirtd on the source of the migration. # service libvirtd restart(source) error: server closed connection: # virsh list --all(source host) Id Name State ---------------------------------- 1 rh5 running
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Migration successful when migration with restart destination libvirtd. Version-Release number of selected component (if applicable): libvirt-0.8.2-24.el5 libvirt-python-0.8.2-24.el5 How reproducible: always Steps to Reproduce: 1.Configure a migration environment on el5. 2.On Source,start a live migration: #virsh migrate --live rhel6.2rc qemu+ssh://10.66.5.10/system 3.On target,while the migration is happening, reboot libvirtd on the destination of the migration; # service libvirtd restart Actual results: On source: virsh migrate rhel6.2rc --live qemu+ssh://10.66.5.10/system error: cannot send data: Broken pipe error: Reconnected to the hypervisor On target: virsh list Id Name State ---------------------------------- 5 rhel6.2rc paused Expected results: Guest will still running on source and no guest trace on target, migration failed gracefully with error error: Cannot write data: Broken pipe error: Reconnected to the hyperviso