From owner-freebsd-xen@freebsd.org Mon Nov 2 18:56:42 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 BCA78A24276 for ; Mon, 2 Nov 2015 18:56:42 +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 40F141B1B for ; Mon, 2 Nov 2015 18:56:41 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.100] (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 tA2Iud3x043253 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Nov 2015 18:56:40 GMT (envelope-from kpielorz_lst@tdx.co.uk) Date: Mon, 02 Nov 2015 18:56:30 +0100 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: <84EFB0608568EE976A48039C@Mac-mini.local> In-Reply-To: <5637A01B.1010307@citrix.com> References: <151F73F1EF071C3C48F17866@[10.12.30.106]> <5637A01B.1010307@citrix.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) 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, 02 Nov 2015 18:56:42 -0000 --On 2 November 2015 at 18:40:43 +0100 Roger Pau Monn=C3=A9=20 wrote: >> remote refid st t when poll reach delay offset = jitter >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> =3D=3D=3D 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? Sorry for being so vague (I half hoped someone must have run into this=20 before and posted a "Yes, we noticed the same - this fixes it" reply :) The above seems to show that time moved forward on the VM by a few seconds. = This doesn't always happen - I just moved another VM and that shows 'offset = =3D 8000'. Yet another VM moved at the same time is fine. Comparing the output of 'date' for that offset 8000 VM with a known 'good'=20 clock - it shows the VM is indeed 8 seconds in the future after the move. ntp is fussy - and kind of understandably decides that's too much time=20 difference to slowly ebb away - so just gives up and leaves the VM clock=20 'as is'. The XenServer the VM was residing on (and the new one it's resident on)=20 both on their server consoles show the correct time (i.e. neither are 8=20 seconds 'ahead') - so it looks like the move somehow gained us 8 seconds=20 (or 5 seconds in the original example). > There were some issues that I fixed some time ago regarding migration > and PVHVM guests: > > = http://xenbits.xen.org/gitweb/?p=3Dxen.git;a=3Dcommit;h=3Df8e8fd56bd7d5675e8= 331 > b4ec74bae76c9dbf24e > = http://xenbits.xen.org/gitweb/?p=3Dxen.git;a=3Dcommit;h=3D32c864a35ece2c24a3= 36d > 183869a546798a4b241 > > You should make sure XenServer has both of this commits. I'll have a look at those - we might be a bit stuck for implementing them=20 if they're XenServer changes, as we run the XenServer ISO's (6.5 SP1=20 w/hotfixes). -Karl