From owner-freebsd-xen@FreeBSD.ORG Wed Jan 14 20:42:10 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 24D67414 for ; Wed, 14 Jan 2015 20:42:10 +0000 (UTC) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E9DE28A8 for ; Wed, 14 Jan 2015 20:42:09 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 82565206C7 for ; Wed, 14 Jan 2015 15:42:07 -0500 (EST) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Wed, 14 Jan 2015 15:42:07 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:x-sasl-enc:from:to :mime-version:content-transfer-encoding:content-type:subject :date:in-reply-to:references; s=smtpout; bh=l7/y0YJ0FE1RGtKDsHfG 05oS3+8=; b=HQ8m+5ILLuQl1bujbKBKyF7iKSAggJlPyEmcyfVhIIPBarlFESm4 TwHK63h1w7jFEK2izpPuTEz5c7Y6MvUrjv/F62Bz2Pa63ApfXbfLN8+Mq1fVoHTL Hiup5PQJHWxBPXeWmnYqfd3iTvi4uuu3iNNLxGVrqCn5nX2cYZeADlk= Received: by web3.nyi.internal (Postfix, from userid 99) id 5D5CF10F80C; Wed, 14 Jan 2015 15:42:07 -0500 (EST) Message-Id: <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> X-Sasl-Enc: C1dkI3VmG7sxxva6kAm7CxvSlDEKS+7k0fjK/1btzPS8 1421268127 From: Mark Felder To: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-46f3f2c7 Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? Date: Wed, 14 Jan 2015 14:42:07 -0600 In-Reply-To: <70A0A91F47C63040B165812D@[10.12.30.106]> References: <70A0A91F47C63040B165812D@[10.12.30.106]> X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 14 Jan 2015 20:42:10 -0000 On Wed, Jan 14, 2015, at 09:16, Karl Pielorz wrote: > > Hi, > > This has been seen before e.g. see > > > > We're now seeing this now we've started using 10.x boxes under XenServer > 6.5 > > Is there any work around for it? > > The 'hit' rate for us seems to be quite high (+70%?) i.e. the clock > resets > most of the time we do even just a storage migration. > > The guests are running NTP - and that continues running after the event, > but is obviously unwilling to make such a big clock adjustment to drag > the > guests time from 1970 to present day. > > Unfortunately - this also causes various other things on the box to break > as well :( > > Is there no 'after migration' hook or script I can lodge some code to > shutdown NTP, do an ntpdate - then restart NTP again? > When I ran into this I manually stopped NTP, migrated, ran ntpdate, started NTP again. It was painful. The problem as I recall is in the PVHVM code and is fixed upstream in Xen but wasn't pulled into XenServer. Roger will know more details, but if you have a Citrix support contract you should pressure them to open a bug / regression on this. Unfortunately I'm no longer in a position to do so...