tested this in is35 Seems like migration_max_time_per_gib_mem is not counted in timeout Steps to reproduce: 1. Set migration_max_time_per_gib_mem to 1 on hosts in vdsm config 2. service restart vdsm 3. Start VM in WA (VM with ~1GB of memory) 4. Migrate to other host result events: 1st test: 2014-Mar-19, 17:10 Migration started (VM: a, Source: host2, Destination: host1, User: admin@internal). 2014-Mar-19, 17:11 Migration completed (VM: a, Source: host2, Destination: host1, Duration: 56 sec). 2nd test: 2014-Mar-19, 17:06 Migration started (VM: a, Source: host1, Destination: host2, User: admin@internal). 2014-Mar-19, 17:06 Migration completed (VM: a, Source: host1, Destination: host2, Duration: 32 sec). In both cases time of migration is bigger than 1s (56s, 32s) and migration finished successfully.
Regression patch merged to ovirt-3.3 as http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=commit;h=188f72dd0d5bd0fc724e9ba08aff8a2b9a7ec6fc
This bug is currently attached to errata RHBA-2014:17276. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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/RHBA-2014-0392.html