public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Espen Berg <espen@monsternett.no>
Cc: kvm@vger.kernel.org
Subject: Re: Timedrift in KVM guests after livemigration.
Date: Sun, 18 Apr 2010 00:17:26 +0400	[thread overview]
Message-ID: <4BCA1756.6060800@msgid.tls.msk.ru> (raw)
In-Reply-To: <4BCA1164.1030808@monsternett.no>

17.04.2010 23:52, Espen Berg wrote:
> Den 15.04.2010 09:35, skrev Espen Berg:
>> We have three KVM hosts that supports live-migration between them, but
>> one of our problems is time drifting. The three frontends has different
>> CPU frequency and the KVM guests adopt the frequency from the host
>> machine where it was first started.

What do you mean by "adopts" ?  Note that the cpu frequency
means nothing for all the modern operating systems, at least
since the days of common usage of MS-DOS which relied on CPU
frequency for its time functions.  All interesting things are
now done using timers instead, and timers (which don't depend
on CPU frequency again) usually work quite well.

What complicates things is that the most cheap and accurate
enough time source is TSC (time stamp counter register in
the CPU), but it will definitely be different on each
machine.  For that, 0.12.3 kvm and 2.6.32 kernel (I think)
introduced a compensation.  See for example -tdf kvm option.

[]
>> Is there any solution to our problems, or is a reboot the only safe
>> solution?

Well, reboot is definitely a safe solution.

> Is there no one with similar problems here? :\ Guess I should file a bug
> report or something if the same problems occur in the latest version. I
> can't se any changes in change log after 0.11.x that relate to this
> problem. We can't be the only one that uses different CPUs in a
> migration environment.

Actually there is a difference in 0.12.

> Since this is a cluster in production, I'm not able to try the latest
> version either.

Well, that's difficult one, no?  It either works or not.
If you can't try anything else, why to ask? :)

/mjt

  reply	other threads:[~2010-04-17 20:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15  7:35 Timedrift in KVM guests after livemigration Espen Berg
2010-04-17 19:52 ` Espen Berg
2010-04-17 20:17   ` Michael Tokarev [this message]
2010-04-17 23:21     ` Espen Berg
2010-04-18  9:22       ` Dor Laor
2010-04-18  9:33         ` Espen Berg
2010-04-22  7:40           ` Thomas Treutner
2010-04-18  9:56         ` Gleb Natapov
2010-04-19  9:21           ` Espen Berg
2010-04-19  9:29             ` Gleb Natapov
2010-04-19 11:57               ` Dor Laor

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=4BCA1756.6060800@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=espen@monsternett.no \
    --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