[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Clock problems on Squeeze/Xen4 (clock jumps 50 minutes ahead)

  • To: Aleix Dorca Josa <adorca@xxxxxx>
  • From: Stephan Seitz <s.seitz@xxxxxxxxxxx>
  • Date: Mon, 27 Aug 2012 08:30:42 +0000
  • Accept-language: de-DE, en-US
  • Cc: "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
  • Delivery-date: Mon, 27 Aug 2012 08:33:13 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>
  • Thread-index: AQHNhC4+3TpCPjO4GEObx0oPSO+caw==
  • Thread-topic: [Xen-users] Clock problems on Squeeze/Xen4 (clock jumps 50 minutes ahead)

Am Montag, den 27.08.2012, 08:29 +0200 schrieb Aleix Dorca Josa:

I see that the clocksource=pit on the grub command line does not seem to fix the problem. Any other hints? Change to Ubuntu server? Build my own xen binary? Use Debian's backports to change the kernel version?

This is kind of a big problem for me since the error kills ntpd on DomU's and then Dovecot's processes stop themselves when time is corrected. Scripts to workaround this are fine but I would rather much prefer for the clock not to jump ahead.


as a quick fix, you could handle your domU's independent from xen:

echo "jiffies" > /sys/devices/system/clocksource/clocksource0/current_clocksource
echo "1" > /proc/sys/xen/independent_wallclock

take a look at /sys/devices/system/clocksource/clocksource0/available_clocksource to see which clock sources are possible.



Attachment: signature.asc
Description: This is a digitally signed message part

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.