From: Andrey Korolyov <andrey@xdel.ru>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Marcelo Tosatti" <mtosatti@redhat.com>,
"Marcin GibuÅ a" <m.gibula@beyond.pl>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)
Date: Sat, 6 Sep 2014 03:05:33 +0400 [thread overview]
Message-ID: <CABYiri_Fc7EbnHBR5oyC0poUSVpFjRcPy35KdGfoveKjpwZp9A@mail.gmail.com> (raw)
In-Reply-To: <540A35D5.4050708@redhat.com>
On Sat, Sep 6, 2014 at 2:14 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Il 05/09/2014 21:35, Andrey Korolyov ha scritto:
>> - boot up a VM, make sure to feed it heavy long task, for example
>> kernel compilation,
>> - neither migrate once in the middle of process (with fallback to
>> non-live migration which is available in libvirt, else it may take
>> forever) or just wait up to the end,
>> - live migration time degrades from sub-10s value to larger values
>> forever, not regarding if workload is still presented or not.
>
> Are you sure you aren't simply doing migration with a low bandwidth
> limit (the default is 32 MB/s), and moving over a gigabyte worth of page
> cache data to the new machine?
>
> Paolo
As far as I can see setspeed does not change anything over stdev
variation for gigabit, but rss size does. Will check if this part is
actually broken, because we are overriding default speed value every
time and if it started being constant, it may explain such a
difference.
next prev parent reply other threads:[~2014-09-05 23:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 13:52 [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3) Marcelo Tosatti
2014-09-05 13:52 ` [Qemu-devel] [patch 1/3] kvmclock: Ensure time in migration never goes backward Marcelo Tosatti
2014-09-09 15:12 ` Marcelo Tosatti
2014-09-09 21:16 ` Alexander Graf
2014-09-09 23:07 ` Marcelo Tosatti
2014-09-05 13:52 ` [Qemu-devel] [patch 2/3] Introduce cpu_clean_all_dirty Marcelo Tosatti
2014-09-05 13:52 ` [Qemu-devel] [patch 3/3] kvmclock: Ensure proper env->tsc value for kvmclock_current_nsec calculation Marcelo Tosatti
2014-09-05 18:16 ` [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3) Andrey Korolyov
2014-09-05 18:26 ` Marcelo Tosatti
2014-09-05 18:29 ` Paolo Bonzini
2014-09-05 18:35 ` Andrey Korolyov
2014-09-05 19:35 ` Andrey Korolyov
2014-09-05 22:14 ` Paolo Bonzini
2014-09-05 23:05 ` Andrey Korolyov [this message]
2014-09-09 17:54 ` Andrey Korolyov
2014-09-16 9:14 ` Paolo Bonzini
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=CABYiri_Fc7EbnHBR5oyC0poUSVpFjRcPy35KdGfoveKjpwZp9A@mail.gmail.com \
--to=andrey@xdel.ru \
--cc=m.gibula@beyond.pl \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--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).