From: Espen Berg <espen@monsternett.no>
To: kvm@vger.kernel.org
Subject: Re: Timedrift in KVM guests after livemigration.
Date: Mon, 19 Apr 2010 11:21:47 +0200 [thread overview]
Message-ID: <4BCC20AB.3090908@monsternett.no> (raw)
In-Reply-To: <20100418095659.GC4550@redhat.com>
Den 18.04.2010 11:56, skrev Gleb Natapov:
>> That's two different things here:
>> The issue that Espen is reporting is that the hosts have different
>> frequency and guests that relay on the tsc as a source clock will
>> notice that post migration. The is indeed a problem that -tdf does
>> not solve. -tdf only adds compensation for the RTC clock emulation.
>>
> It's -rtc-td-hack. -tdf does pit compensation, but since usually kernel
> pit is used it does nothing.
So this "hack" will not solve our problem?
Espen
next prev parent reply other threads:[~2010-04-19 9:21 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
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 [this message]
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=4BCC20AB.3090908@monsternett.no \
--to=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