From owner-freebsd-xen@freebsd.org  Mon Nov  2 17:40:54 2015
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AB7AA24328
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon,  2 Nov 2015 17:40:54 +0000 (UTC)
 (envelope-from prvs=741c8dfce=roger.pau@citrix.com)
Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63])
 (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 4D7CF160F
 for <freebsd-xen@freebsd.org>; Mon,  2 Nov 2015 17:40:53 +0000 (UTC)
 (envelope-from prvs=741c8dfce=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.20,234,1444694400"; d="scan'208";a="315101778"
Subject: Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions?
To: Karl Pielorz <kpielorz_lst@tdx.co.uk>, <freebsd-xen@freebsd.org>
References: <151F73F1EF071C3C48F17866@[10.12.30.106]>
From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5637A01B.1010307@citrix.com>
Date: Mon, 2 Nov 2015 18:40:43 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <151F73F1EF071C3C48F17866@[10.12.30.106]>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-DLP: MIA2
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Nov 2015 17:40:54 -0000

El 02/11/15 a les 16.09, Karl Pielorz ha escrit:
> 
> Hi,
> 
> We run a number of 10.x boxes under XenServer 6.5. On those boxes we run
> NTP  as a client with a few local time servers on the network to keep
> the time in sync on that VM.
> 
> There's a number of big threads on the Citrix forums about whether you
> should, or shouldn't run NTP in domU's - but the consensus seems to be
> you need to in order to keep the domU's clock accurately in sync.
> 
> This works fine.
> 
> However if we run a live migrate (to another XenServer node) or Xen
> Storage Motion migration - the domU's ntp gets messed up. The time on
> the domU is generally "ok" - but ntpq gives output like:
> 
> "
> ntpq> pe
>     remote        refid      st t when poll reach   delay   offset jitter
> ===========================================================================
> ntp0      193.67.79.202    2 u  931 1024  377    0.232  -4977.5 4207.29
> ntp1       66.228.38.73    3 u  890 1024  377    0.267  -4988.5 4616.94
> ntp2      64.246.132.14    2 u  990 1024  377    0.324  -4978.0 4207.98
> "

I'm sorry, but I have no idea about ntpd, what does the above mean? The
offset is too big with other peers and ntpd simply disconnects?

There were some issues that I fixed some time ago regarding migration
and PVHVM guests:

http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=f8e8fd56bd7d5675e8331b4ec74bae76c9dbf24e
http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=32c864a35ece2c24a336d183869a546798a4b241

You should make sure XenServer has both of this commits.

Roger.