Added conditional nak on 'design' There are various factors that influence migration: 1 - VM's memory size 2 - bandwidth to destination 3 - source CPU load 4 - destination CPU load 5 - concurrent migrations (actually this one influence #2 & #3) Since bandwidth is only one consideration among all the rest, and there can't be 1 migration policy that fits all, we need to come out with few migration policies and let the administrator determine which one to use. This needs design in both VDSM & RHEVM
Scott, please look into this issue and see if we can understand the needs based on existing migration priority.
Once we implement Host-Level Network QoS (RHEV BZ 1043226), won't that provide a solution for this?
Yes, proper QoS per physical interface/VLAN device should provide a solution for this. There is also this one [1] which can be relevant here. -Nir [1] https://bugzilla.redhat.com/show_bug.cgi?id=1043809
Based on comment 7, pushing to 3.6, to revisit if needed.
regardless QoS on the network we want to improve migration behavior in general aligned with comment #2, see bug 1252426
setting bug 1252426 as Depends On, even though it doesn't really depend on that. QoS could be done independently. One can look at it as part of a general migration improvement, but I don't plan to track it under bug 1252426, so keeping this bug open for further consideration
Following live migration improvements happened on 4.0 and continued on 4.1, we currently don't see a need from the field to prioritize this functionality. please reopen if this still an issue.