--Sig_/TUWmnFEJa_n_v8qGNXuhObh Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 27 Sep 2016 13:22:29 -0400 (EDT) Michal wrote: MS> > On 27 Sep 2016, at 19:12, aleksey.maksimov@it-kb.ru wrote: MS> >=20 MS> > I'm afraid that in the future OS time may get out of sync because of = kvm-clock MS> > And as a result Kerberos may stop working MS> > I hope I explained clearly =20 MS>=20 MS> Sorry, not really. You said you set up ntpd/chrony correctly. So how ca= n the time get out of sync? Why do you think it can be because of kvmclock = anyway? Do you refer to some specific bug? I'd guess that it's a misunderstanding of what kvmclock is. Someone guessing based on the name might think that it keeps the vm time in sync with the host. Which might lead one to think it would conflict with ntp (two different things trying to manage time). If you know that kvmclock is essentially just a way to monitor the passage of time (tick-tock-tick-tock) using the host's timer, then it makes sense that you need also need ntp to tweak the current time to adjust for the minor drift inherit in any clock. Robert --=20 Senior Software Engineer @ Parsons --Sig_/TUWmnFEJa_n_v8qGNXuhObh Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlfrsysACgkQ7/fVLLY1mnhMXgCfbzyHji6THaKG6Fw7qefTm1lu PyAAmwRkM62aK+s7b/eK0hF8lEOofaY3 =iLc2 -----END PGP SIGNATURE----- --Sig_/TUWmnFEJa_n_v8qGNXuhObh--