Date: Mon, 02 Nov 2015 15:09:25 +0000 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: freebsd-xen@freebsd.org Subject: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions? Message-ID: <151F73F1EF071C3C48F17866@[10.12.30.106]>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?151F73F1EF071C3C48F17866>