Re: migrate_set_downtime bug

[Glauber Costa <glommer@redhat.com>]

On Mon, Oct 05, 2009 at 04:09:43PM +0200, Dietmar Maurer wrote:
> > Heuristics like number of pages, maybe.  But since we don't export
> > iteration information, we can't expect management tools to stop the
> > guest if migration doesn't converge.
> > 
> > I suppose it could issue a 'stop' after some amount of time (constant *
> > memory size / bandwidth).
> 
> 'bandwidth' is something that changes dynamically (or by user settings), so why don't we simply abort after some amount of transferred memory (constant * memory size). This can be implemented by the management application without problems, although it's much easier inside kvm.
> 
Easier, yes.

But then once it is done, people wanting a different behaviour for some valid reason are stuck with that.
This is the very reason we expose information about migration in the monitor to begin with.

Again, I believe the fix for this convergence problem does not belong here.