'Live' Migrate messes up NTP on FreeBSD domU - any suggestions?

[Roger Pau Monné]

El 02/11/15 a les 16.09, Karl Pielorz ha escrit:
> 
> 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
> "

I'm sorry, but I have no idea about ntpd, what does the above mean? The
offset is too big with other peers and ntpd simply disconnects?

There were some issues that I fixed some time ago regarding migration
and PVHVM guests:

http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=f8e8fd56bd7d5675e8331b4ec74bae76c9dbf24e
http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=32c864a35ece2c24a336d183869a546798a4b241

You should make sure XenServer has both of this commits.

Roger.