From owner-freebsd-xen@freebsd.org Mon Nov 9 10:23:03 2015 Return-Path: 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 E4F91A2AFCB for ; Mon, 9 Nov 2015 10:23:03 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.krpservers.com", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 881961292 for ; Mon, 9 Nov 2015 10:23:03 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213] (may be forged)) (authenticated bits=0) by smtp.krpservers.com (8.14.9/8.14.9) with ESMTP id tA9AMnwj076701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Nov 2015 10:22:51 GMT (envelope-from kpielorz_lst@tdx.co.uk) Date: Mon, 09 Nov 2015 10:22:48 +0000 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= , freebsd-xen@freebsd.org Subject: Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions? Message-ID: <2CCED8DD6371A49B7BA2F909@[10.12.30.106]> In-Reply-To: <563898B0.5040100@citrix.com> References: <151F73F1EF071C3C48F17866@[10.12.30.106]> <5637A01B.1010307@citrix.com> <8448B4CE863936ADEF762C0F@[10.12.30.106]> <563898B0.5040100@citrix.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 10:23:04 -0000 --On 03 November 2015 12:21 +0100 Roger Pau Monn=C3=A9 = =20 wrote: > Is XenServer also synchronized using ntpd? When a guest resumes from > migration is updates it's current time based on the time provided by the > hypervisor, so if the hosts themselves are not synchronized you could > see skews like that. I've tested this on two pools now. The original production pool (Xeon=20 E3-1220 v3 @ 3.10GHz) has the issue. Our office / test pool (Xeon L5630 @ 2.13Ghz) also -has the issue-. Both=20 are setup pretty much identical (same storage solution, both running=20 FreeBSD 10.1/10.2-R with 'xe-guest-utilities' installed). Running or not=20 running NTP doesn't make a difference. Live migrates result in the domU gaining several seconds (thus breaking NTP = if it is running) else leaving the host 'running in the future' vs. both=20 external clocks, and NTP sync'd clocks on the xenserver. As it's easily reproducible I guess I'll file it as a bug... -Karl