Date: Wed, 14 Jan 2015 15:48:47 -0500 From: Adam McDougall <mcdouga9@egr.msu.edu> To: freebsd-xen@freebsd.org Subject: Re: XenServer 6.5 migrate FBSD 10/11 results in clock reset to 1970? Message-ID: <54B6D62F.9090002@egr.msu.edu> In-Reply-To: <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com> References: <70A0A91F47C63040B165812D@[10.12.30.106]> <1421268127.1109646.213984377.0E5EC646@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/14/2015 15:42, Mark Felder wrote: > > > 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... > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > I really thought this was fixed in Creedence alphas that I tested... I still have those test systems up but I need to make a test environment for 6.5. Are you using AMD or Intel? I don't know if it makes a difference but I've only seen the problem on AMD so far.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54B6D62F.9090002>