Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Sometimes
[root@source ~]# virsh migrate --live kvm qemu+ssh://10.66.93.106/system
root.93.106's password:
error: server closed connection:
error: Reconnected to the hypervisor
[root@target ~]# service libvirtd restart
Stopping libvirtd daemon: [ OK ]
Starting libvirtd daemon: [ OK ]
[root@dhcp-93-134 ~]# virsh list --all
Id Name State
----------------------------------
sometimes
[root@source ~]# virsh migrate --live kvm qemu+ssh://10.66.93.106/system
root.93.106's password:
error: server closed connection:
error: Reconnected to the hypervisor
[root@target ~]# service libvirtd restart
Stopping libvirtd daemon: [ OK ]
Starting libvirtd daemon: [ OK ]
[root@dhcp-93-134 ~]# virsh list --all
Id Name State
----------------------------------
5 kvm paused
Version-Release number of selected component (if applicable):
libvirt-0.8.7-1.el6.x86_64
How reproducible:
always
Expected results:
guest could be migrated successfully
Additional info:
libvirt is not able to cope with such situation since during migration, the client (or source libvirtd) has open connections to both sides through which the migration is controlled... if any of the connection is dropped, something will fail; how it fails depends on what libvirtd is restarted and in which migration phase that happens
So this is the expected result . Close this bug as NOTABUG