• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 826
  • Last Modified:

Redhat Enterprise 5.4 Clock/Time issue when running as a VM under MS Hyper-V Server 2008 R2

We have a Hyper0V Server 2K8 R2.  We created a virtual machine and loaded Redhat Enterprise 5.4.   It seems like the VM will not keep proper time.   We have set up a cron job that will update the clock every 15 minutes or so, but that obviously is not the solution.   Does any one have any fixes for this issue?
0
BladesAway
Asked:
BladesAway
  • 3
2 Solutions
 
Kerem ERSOYPresidentCommented:
Hi,

This is a known problem with some Virtual systems especilly guests under Hyper-V. A clock chip can not be emulated for obvious reasons (it is by definition a piece of hardware there's no point in emulating it since the emulation wount be as acurate as the hardware). You'd better start the ntpd service over the RedHAT Server.

To enable the ntpd over redhat you'd issue these commands:

chkconfig --list ntpd

(to make sure that ntpd is installd)
If not pelase install it first :

yum install ntp

then you'd turn on the service with this command:

chkconfig ntpd on

and you'd start it with this command (Since the above comand will only enable it to be run next time the ssytem reboots)

service ntpd on


This should be enough and your system should stay up-to-date afterwards.

You can check the accuracy of your clock using the command

ntpq and issuing
>lop

Or

ntpdc
> sysinfo

Cheers,
K.

comand
0
 
Kerem ERSOYPresidentCommented:
Oops sorry this command for starting the ntpd should read:
service ntpd start

not

service ntpd on

Cheers,
K.
0
 
JordanH155Commented:
You can try appending "clock=pit" to the end of the kernel line in grub.  

There is actually a Microsoft KB article here: http://support.microsoft.com/kb/918461  with instructions on how to add it for grub and lilo.

0
 
Kerem ERSOYPresidentCommented:
I'll have another suggestion that I've myself applied for some time now. Though you can synchronize using the pit clock it is also a hardware emulation clock which would lead some errors now and then. The only thing it fixes is to prevent the clock gain 50 seconds in 1 minute !! Apart from that it is not an accurate time.

My suggestion is to apply the changes to your hyper-v system and convert it to an NTP time source then use NTP and synchronize time with this system . This has another advantage that all your systems will have a synchronized clock and if you use, you'll have consistent logs all over your network.

Here's the article:  http://support.microsoft.com/kb/816042

Cheers,
K.
0
 
BladesAwayAuthor Commented:
I am working the suggestions.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now