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
--
--
George Magklaras BSc Hons MPhil
RHCE:805008309135525
Senior Computer Systems Engineer/UNIX-Linux Systems Administrator
EMBnet Technical Management Board
The Biotechnology Centre of Oslo,
University of Oslo
http://folk.uio.no/georgios
Ryan Golhar wrote:
I've seen a ton of messages like this but no solution that works. I
have a 64-bit RHEL 5 machine running multiple guests. Dom0 keeps time
using ntp and works well.
I initially had the virtual machines do the same thing, but they failed
to keep time properly. I've since disabled ntp on the guests and
haven't found a solution.
I saw messages regarding setting /proc/sys/xen/independent_wallclock to
0, but I only see this file on Dom0, not the guests so I'm not quite
sure how this works for the guests keeping proper time.
Has anyone figured out how to keep 64-bit guests in sync with Dom0?
Ryan
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
