From: Paolo Bonzini <pbonzini@redhat.com>
To: Mohammed Gamal <mohammed.gamal@profitbricks.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kvmclock, Migration, and NTP clock jitter
Date: Thu, 15 Jan 2015 18:27:54 +0100 [thread overview]
Message-ID: <54B7F89A.80107@redhat.com> (raw)
In-Reply-To: <CAHTgm8+8y7e5nNBi-0Aed-zbsa4P22TmJ3Oywcc672VLP4VuRg@mail.gmail.com>
On 15/01/2015 17:39, Mohammed Gamal wrote:
> The increase in the jitter and offset values is well within the 500 ppm
> frequency tolerance limit, and therefore are easily corrected by
> subsequent NTP clock sync events, but some live migrations do cause much
> higher jitter and offset jumps, which can not be corrected by NTP and
> cause the time to go way off. Any idea why this is the case?
It might be fixed in QEMU 2.2.
See https://lists.gnu.org/archive/html/qemu-devel/2014-09/msg01239.html
Paolo
next prev parent reply other threads:[~2015-01-15 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 16:39 [Qemu-devel] kvmclock, Migration, and NTP clock jitter Mohammed Gamal
2015-01-15 17:27 ` Paolo Bonzini [this message]
2015-01-16 10:21 ` Mohammed Gamal
2015-01-21 10:20 ` Mohammed Gamal
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=54B7F89A.80107@redhat.com \
--to=pbonzini@redhat.com \
--cc=mohammed.gamal@profitbricks.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).