Re: [CentOS-virt] Time

On Wed, Jan 2, 2013 at 12:53 AM, Robert Dinse nanook@eskimo.com wrote:

 Friday, I moved our servers to a new co-lo facility and ran into an

interesting problem with virtual machines.

 I did an orderly shutdown of the CentOS 6.3 host, and it in turn suspends

all the guests. It took about an hour and a half to move and fire up the host.

 The guests, being suspended, were then an hour and a half behind and it

seems ntpd does not want to correct more than 1000 seconds of error so it would not automatically adjust the clocks.

 I tried the -g argument which is supposed to override the 1000 second

limit but it did not. I ended up having to manually set the clocks close enough for ntpd to correct.

 Since there is no hardware clock for the virtual machines to use when they

boot, it seems that shutdown and reboot of the virtual machines probably would not have avoided this.

 Any suggestions for addressing this particular scenerio other than having

to manually set a bunch of clocks?

Maybe related to this bug report:

http://bugs.centos.org/view.php?id=5726

Not sure if the "tinker panic 0" trick works or not as a workaround (see note 15092). No one has reported back with success or fail.

The bug was filed upstream but was closed as CANTFIX :

https://bugzilla.redhat.com/show_bug.cgi?id=821988

Akemi