Ryan Golhar wrote:
9.2.2.2 says xen just passed the time-related calls to Dom0, but that
can't be the case because the times are different.
That is because if you do run ntpd inside the VM, this can create the
problem.
noselect? inside the VM?
Yes on the guest system, and run ntpd normally on the Dom0.
We are running on a Sun SunFire X4150.
What I stated was on a Dell 2950 PowerEdge, but I shall get hold of a
SunFire and repeat the test, see if I get the same issue. It does state
that there might be some kernel parameters that need tweaking, but, I am
curious to find out what's going on, as we will be using SunFire kit
with Xen soon.
GM
George Magklaras wrote:
This page might offer some help:
http://support.ntp.org/bin/view/Support/KnownOsIssues#Section_9.2.2.
To recap, we use the 'noselect' keyword to avoid the running ntpd on
the client to attempt to sync with the defined servers and ntpq does
not report any disturbing drifts on the client...and we do run ntpd
normally (no 'noselect') on Dom0.
What happens (happened if you have already tried) if you try and do
this? And what's your hardware platform?
GM
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
