Date: Wed, 14 Jan 2015 14:42:07 -0600 From: Mark Felder <feld@FreeBSD.org> To: freebsd-xen@freebsd.org Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? Message-ID: <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> In-Reply-To: <70A0A91F47C63040B165812D@[10.12.30.106]> References: <70A0A91F47C63040B165812D@[10.12.30.106]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 14, 2015, at 09:16, Karl Pielorz wrote: > > Hi, > > This has been seen before e.g. see > > <https://lists.freebsd.org/pipermail/freebsd-xen/2013-December/001825.html>; > > 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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1421268127.1109646.213984377.0E5EC646>