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.

Created attachment 513773 [details]
vdsm.log

Description of problem:
When connection between hosts (SPM and non-SPM) crashes during a VM migration, there's no timeout - the VM stays in locked mode, vdsm on SPM host tries to migrate the vm repeatedly (possibly forever).

Version-Release number of selected component (if applicable):
vdsm-4.9-82.el6.x86_64
libvirt-0.9.2-1.el6.x86_64
qemu-kvm-0.12.1.2-2.171.el6.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. Have a working setup - 2 hosts (without fencing), NFS storage (probably irrelevant) 
2. Start a vm (on SPM host), when it's up perform migration to the non-SPM host
3. Right after it starts block communication between SPM and non-SPM host using iptables (but not between hosts and storage!)
  
Actual results:
Vdsm keeps trying to migrate the vm (possibly forever), vm is in locked mode

Expected results:
Migration fails with proper error shown to user after some timeout - when data transferred to the second host stays on 1% for more then 10 mins it definitely means that something isn't ok.

Additional info:
Attaching vdsm.log

http://gerrit.usersys/#change,732

Verified - vdsm-4.9-86.el6 - timeout was set in vdsm therefore migration (from vdsm point of view) can't be proceeding forever.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1782.html