From owner-freebsd-xen@freebsd.org Mon Nov 2 15:20: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 E6D94A03126 for ; Mon, 2 Nov 2015 15:20: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 8955A1259 for ; Mon, 2 Nov 2015 15:20:02 +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 tA2F9Pnw028293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 2 Nov 2015 15:09:26 GMT (envelope-from kpielorz_lst@tdx.co.uk) Date: Mon, 02 Nov 2015 15:09:25 +0000 From: Karl Pielorz To: freebsd-xen@freebsd.org Subject: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions? Message-ID: <151F73F1EF071C3C48F17866@[10.12.30.106]> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 15:20:04 -0000 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 " It *never* recovers from this (you have to log into the box, and restart ntpd). I realise this may be more a 'ntpd' than Xen question - but does anyone have any suggestions for avoiding this happening? - i.e. Some option for ntp.conf or something? Thanks, -Karl