From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: Dietmar Maurer <dietmar@proxmox.com>,
Anthony Liguori <anthony@codemonkey.ws>,
kvm <kvm@vger.kernel.org>
Subject: Re: migrate_set_downtime bug
Date: Mon, 05 Oct 2009 15:17:24 +0200 [thread overview]
Message-ID: <4AC9F1E4.4070101@redhat.com> (raw)
In-Reply-To: <20091005130409.GD8092@mothafucka.localdomain>
On 10/05/2009 03:04 PM, Glauber Costa wrote:
> On Mon, Oct 05, 2009 at 02:17:30PM +0200, Avi Kivity wrote:
>
>> On 09/30/2009 08:41 PM, Dietmar Maurer wrote:
>>
>>> I just think of common scenarios like 'maintanace mode', where all VM should migrate to another host. A endless migrate task can make that fail.
>>>
>>> For me, it is totally unclear what value I should set for 'max_downtime' to avoid that behavior?
>>>
>>>
>>>
>> We used to have a heuristic that said 'if an iteration transfers more
>> pages than the previous iteration, we've stopped converging'. Why
>> wouldn't that work?
>>
> Because it seems people agreed that mgmt tools would be the place for those heuristics.
>
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).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-10-05 13:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 13:00 migrate_set_downtime bug Dietmar Maurer
2009-09-29 14:36 ` Dietmar Maurer
2009-09-29 15:09 ` Dietmar Maurer
2009-09-29 15:39 ` Anthony Liguori
2009-09-29 16:23 ` Glauber Costa
2009-09-29 16:36 ` Dietmar Maurer
2009-09-30 4:48 ` Glauber Costa
2009-09-30 6:58 ` Dietmar Maurer
2009-09-30 8:55 ` Dietmar Maurer
2009-09-30 11:23 ` Glauber Costa
2009-09-30 14:11 ` Dietmar Maurer
2009-09-30 16:39 ` Glauber Costa
2009-09-30 18:41 ` Dietmar Maurer
2009-10-05 12:17 ` Avi Kivity
2009-10-05 13:04 ` Glauber Costa
2009-10-05 13:17 ` Avi Kivity [this message]
2009-10-05 14:09 ` Dietmar Maurer
2009-10-05 15:32 ` Glauber Costa
2009-10-06 8:30 ` Dietmar Maurer
2009-10-06 17:33 ` Glauber Costa
2009-10-07 4:42 ` Dietmar Maurer
2009-10-07 12:32 ` Glauber Costa
2009-10-07 19:40 ` Dietmar Maurer
2009-10-05 14:01 ` Dietmar Maurer
2009-10-05 14:06 ` Avi Kivity
2009-10-05 14:08 ` Dietmar Maurer
2009-10-05 14:15 ` Avi Kivity
2009-10-05 14:11 ` Dietmar Maurer
2009-10-05 14:18 ` Dietmar Maurer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AC9F1E4.4070101@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=dietmar@proxmox.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox