From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@kamp.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: qemu block <qemu-block@nongnu.org>, Fam Zheng <famz@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] Block Migration and CPU throttling
Date: Tue, 19 Sep 2017 16:41:47 +0200 [thread overview]
Message-ID: <eb8d6f5c-ad08-500f-7d89-70d109deaa21@redhat.com> (raw)
In-Reply-To: <6cc4a99c-0212-6b7b-4a12-3e898215bea9@kamp.de>
On 19/09/2017 15:36, Peter Lieven wrote:
> Hi,
>
> I just noticed that CPU throttling and Block Migration don't work
> together very well.
> During block migration the throttling heuristic detects that we
> obviously make no progress
> in ram transfer. But the reason is the running block migration and not a
> too high dirty pages rate.
>
> The result is that any VM is throttled by 99% during block migration.
>
> I wonder what the best way would be fix this. I came up with the
> following ideas so far:
>
> - disable throttling while block migration is in bulk stage
> - check if absolute number of num_dirty_pages_period crosses a threshold
> and not if its just
> greater than 50% of transferred bytes
> - check if migration_dirty_pages > 0. This slows down throttling, but
> does not avoid it completely.
If you can use nbd-server and drive-mirror for block migration (libvirt
would do it), then you will use multiple sockets and be able to migrate
block and RAM at the same time.
Otherwise, disabling throttling during the bulk stage is the one that
seems nicest and most promising.
Paolo
next prev parent reply other threads:[~2017-09-19 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 13:36 [Qemu-devel] Block Migration and CPU throttling Peter Lieven
2017-09-19 14:38 ` Dr. David Alan Gilbert
2017-09-19 14:40 ` Peter Lieven
2017-09-19 14:41 ` Dr. David Alan Gilbert
2017-09-20 19:15 ` Peter Lieven
2017-09-21 12:36 ` Dr. David Alan Gilbert
2017-09-21 12:42 ` Peter Lieven
2017-10-12 13:41 ` Peter Lieven
2017-12-12 17:05 ` Dr. David Alan Gilbert
2017-12-13 16:26 ` Peter Lieven
2018-02-06 11:46 ` Peter Lieven
2018-02-07 18:29 ` Dr. David Alan Gilbert
2018-02-07 20:56 ` Peter Lieven
2018-02-16 20:20 ` Dr. David Alan Gilbert
2017-09-19 14:41 ` Paolo Bonzini [this message]
2017-09-20 19:16 ` Peter Lieven
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=eb8d6f5c-ad08-500f-7d89-70d109deaa21@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@redhat.com \
/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).