All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Thomas Shao <huishao@microsoft.com>,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	driverdev-devel@linuxdriverproject.org, apw@canonical.com,
	jasowang@redhat.com, kys@microsoft.com, haiyangz@microsoft.com
Subject: Re: [PATCH] Drivers: hv: util: Implement Time Synchronization using host time sample
Date: Thu, 25 Sep 2014 07:07:45 +0100	[thread overview]
Message-ID: <20140925060745.GA9450@sucs.org> (raw)
In-Reply-To: <20140923075610.GA10933@aepfle.de>

On Tue, Sep 23, 2014 at 09:56:10AM +0200, Olaf Hering wrote:
> On Tue, Sep 23, Thomas Shao wrote:
> 
> > In current hyper-v time sync service,it only gets the initial clock time
> > from the host. It didn't process the following time samples. This change
> > introduced a module parameter called host_time_sync. If it is set to true,
> > the guest will periodically sychronize it's time with the host clock using
> > host time sample. By default it is disabled, because we still recommend
> > user to configure NTP for time synchronization.

You [Microsoft?] do? Can you link to public sources where is this stated
please? I don't see any mention of doing this on
http://technet.microsoft.com/en-us/library/dn720239.aspx .. The only
official Microsoft information with respect to Hyper-V guest time
synchronisation I've seen has been for Windows guests but perhaps I've
looked in the wrong places.

The reason I ask is because regular ntpd is not enough to discipline a
Linux Hyper-V guest's clock. So much drift can occur under load that
ntpd can't bring the clock under sync. For now, I've been using Chrony
which has a higher tolerance for correcting drifting clocks. I'm not the
only one seeing this either (see http://serverfault.com/a/488528/203726
and
http://serverfault.com/questions/523389/linux-clock-loses-10-minutes-every-week
).

It would be good to something official about this issue as it is painful
when happens.

-- 
Sitsofe | http://sucs.org/~sits/

  parent reply	other threads:[~2014-09-25  6:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1411451081-13423-1-git-send-email-huishao@microsoft.com>
2014-09-23  7:56 ` [PATCH] Drivers: hv: util: Implement Time Synchronization using host time sample Olaf Hering
2014-09-23  9:47   ` Thomas Shao
2014-09-25  6:07   ` Sitsofe Wheeler [this message]
2014-09-25  9:40     ` Thomas Shao
2014-09-25 13:28       ` Time keeps on slipping... on Hyper-V Sitsofe Wheeler
2014-09-26  6:57         ` Thomas Shao
2014-09-26  9:24           ` Mike Surcouf
2014-09-26  9:46             ` Thomas Shao
2014-09-26 10:02 [PATCH] Drivers: hv: util: Implement Time Synchronization using host time sample Thomas Shao
2014-09-26 11:53 ` Mike Surcouf
2014-09-26 12:30   ` Thomas Shao
2014-09-26 13:07     ` Mike Surcouf
2014-09-26 13:52       ` Mike Surcouf
2014-09-26 15:13         ` Thomas Shao

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=20140925060745.GA9450@sucs.org \
    --to=sitsofe@gmail.com \
    --cc=apw@canonical.com \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=huishao@microsoft.com \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.