[Dovecot] "Time just moved backwards" in Dovecot in a Xen DomU

i've

dovecot --version
	1.2.5
hg log | grep changeset | head -n 1
	changeset:   9407:a3e16df805e3

in my logs, i'm seeing

...
Oct 05 16:51:40 dovecot: Error: Time just moved backwards by 1

seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards Oct 05 17:07:22 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards Oct 05 17:23:15 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards Oct 05 17:38:23 dovecot: Error: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards ...

i'm running Dovecot in a Xen DomU,

uname -a
	Linux mail 2.6.27.29-0.1-xen #1 SMP 2009-08-15 17:53:59 +0200 x86_64

x86_64 x86_64 GNU/Linux

reading @, http://wiki.dovecot.org/TimeMovedBackwards

Bugs/Issues
    * With Xen you should run ntpd only in dom0. Other domains should

synchronize time automatically (see this Xen FAQ).

@ my Dom0,

ps ax | grep ntp\.conf
	 5696 ?        Ss     1:05 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid

-g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf

and,

grep localtime /etc/xen/vm/mail.cfg
	localtime    = 0

looking at my ntp logs around the same time(s).

... 5 Oct 16:41:17 ntpd[5696]: synchronized to 64.125.78.85, stratum 1 5 Oct 16:51:38 ntpd[5696]: time reset -2.140133 s 5 Oct 16:56:40 ntpd[5696]: synchronized to 66.220.9.122, stratum 1 5 Oct 17:01:28 ntpd[5696]: synchronized to 64.125.78.85, stratum 1 5 Oct 17:07:20 ntpd[5696]: time reset -2.137760 s 5 Oct 17:11:49 ntpd[5696]: synchronized to 204.152.184.72, stratum 1 5 Oct 17:15:01 ntpd[5696]: synchronized to 207.200.81.113, stratum 1 5 Oct 17:20:49 ntpd[5696]: synchronized to 66.220.9.122, stratum 1 5 Oct 17:23:14 ntpd[5696]: time reset -2.221749 s 5 Oct 17:27:57 ntpd[5696]: synchronized to 64.125.78.85, stratum 1 5 Oct 17:32:52 ntpd[5696]: synchronized to 207.200.81.113, stratum 1 5 Oct 17:38:22 ntpd[5696]: time reset -2.104476 s 5 Oct 17:42:48 ntpd[5696]: synchronized to 66.220.9.122, stratum 1 ...

1 second is not a terribly big deal, but it IS an error ...

not clear to me as to what/where the problem actually is. i've not seen an other dameons report any time issues; of course, i'm not sure they're _checking_ :-/

any suggestions as to what/how to fix?

thanks!