From: Alex Bligh <alex@alex.org.uk>
To: qemu-devel@nongnu.org
Cc: Alex Bligh <alex@alex.org.uk>
Subject: [Qemu-devel] When does live migration give up?
Date: Wed, 04 Sep 2013 16:24:20 +0100 [thread overview]
Message-ID: <A35D54FFEC699EB4F69642B7@nimrod.local> (raw)
We have seen a situation when migrating about 50 VMs at once where some
of them fail. I think this is because they are dirtying pages faster than
they can be transmitted.
What algorithm controls when migration fails in this way, and is it
tunable?
I am fully aware one answer to this question is "do not attempt to
migrate 50 busy VMs through a single 1GB/s NIC".
--
Alex Bligh
next reply other threads:[~2013-09-04 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 15:24 Alex Bligh [this message]
2013-09-04 17:07 ` [Qemu-devel] When does live migration give up? Paolo Bonzini
2013-09-04 18:05 ` Alex Bligh
2013-09-04 18:34 ` Paolo Bonzini
2013-09-04 22:37 ` Alex Bligh
2013-09-04 18:35 ` Alex Bligh
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=A35D54FFEC699EB4F69642B7@nimrod.local \
--to=alex@alex.org.uk \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).