Date: Tue, 12 Jul 2016 14:04:12 +0200 From: "Hoyer-Reuther, Christian" <Christian.Hoyer-Reuther@cac-chem.de> To: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org> Subject: Re: 'Live' Migrate messes up NTP on FreeBSD domU - any suggestions? Message-ID: <41E487BC91654544B2B8F31096F2D9D4D1514D1D8E@ex1>
next in thread | raw e-mail | index | archive | help
Hello list, I know this is old but I discovered the same problem and found this thread = but no newer information. --On Mon Nov 9 10:23:04 UTC 2015 Karl Pielorz <kpielorz_lst at tdx.co.uk> w= rote: > I've tested this on two pools now. The original production pool (Xeon=20 > E3-1220 v3 @ 3.10GHz) has the issue. >=20 > Our office / test pool (Xeon L5630 @ 2.13Ghz) also -has the issue-. Both= =20 > are setup pretty much identical (same storage solution, both running=20 > FreeBSD 10.1/10.2-R with 'xe-guest-utilities' installed). Running or not= =20 > running NTP doesn't make a difference. >=20 > Live migrates result in the domU gaining several seconds (thus breaking N= TP=20 > if it is running) else leaving the host 'running in the future' vs. both= =20 > external clocks, and NTP sync'd clocks on the xenserver. >=20 > As it's easily reproducible I guess I'll file it as a bug... We run a XenServer 6.5 SP1 pool with all patches up to XS65ESP1033 on Fujit= su Primergy RX300 S6 servers. My test VM is FreeBSD 10.3 with xe-guest-util= ities-6.2.0_2 and xen-guest-tools-4.6.1 installed. After live migration the VM's clock is also several seconds in future. I use "tinker panic 0" in /etc/ntp.conf as workaround. Then some minutes af= ter the migration the time is in sync again. Here is some output from a peerstats log: ... VM running on "old" host 57581 41601.319 172.30.99.31 965a 0.000911290 0.000156970 0.437525532 0.000= 079273 57581 41603.285 172.30.99.31 965a 0.000931010 0.000158095 0.187527895 0.000= 087612 ... VM migrated to "new" host 57581 41675.500 172.30.99.31 965a -6.986332827 0.000539032 0.062950133 6.98= 7199663 57581 41744.489 172.30.99.31 905a -6.984444823 0.000480657 0.000739123 6.46= 7141976 57581 41811.509 172.30.99.31 905a -6.982751485 0.000298934 0.000864689 5.90= 2246019 57581 41879.519 172.30.99.31 905a -6.980983259 0.000466260 0.000933010 5.27= 7805891 57581 41945.518 172.30.99.31 905a -6.979267346 0.000409787 0.000950354 4.56= 9599170 57581 42014.502 172.30.99.31 905a -6.977464766 0.000497814 0.000979475 3.73= 0107446 57581 42080.531 172.30.99.31 905a -6.975764545 0.000413500 0.000969749 2.63= 6950596 57581 42148.485 172.30.99.31 905a -6.973984885 0.000336825 0.000977892 0.00= 7845778 57581 42211.541 172.30.99.31 9024 0.036648577 0.000355228 7.937500599 0.000= 000238 57581 42213.518 172.30.99.31 963a 0.037403812 0.000173852 3.937508397 0.000= 755235 ... VM still running on the "new" host, now synced Regards, Christian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41E487BC91654544B2B8F31096F2D9D4D1514D1D8E>