| Summary: | Migration will failed with "error: server closed connection"when restart libvirt on source host during live migration | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | wangyimiao <yimwang> |
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.7 | CC: | dallan, dyuan, hjiang, llim, yoyzhang, yupzhang |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-08-15 19:45:29 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
wangyimiao
2011-05-19 08:53:21 UTC
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 |