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

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2012-08-27 at 09:38 +0100, Aleix Dorca Josa wrote:
> Hi Stephan,
> 
> thanks for your suggestion but unfortunately what you propose only works in 
> Xen 3. I am using Xen 4.

What makes you say that? independent wallclock is a feature of the guest
kernel not the hypervisor.

Older kernels might have /proc/sys/xen/independent_wallclock instead, or
I think you can specify it on the guest kernel command line (you'll have
to google the syntax, I don't know it offhand).

Ian.

> 
> cheers,
> 
> Aleix.
> 
> El 27/08/2012, a les 10:30, Stephan Seitz <s.seitz@xxxxxxxxxxx> va escriure:
> 
> > 
> > 
> > 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.
> >> 
> > 
> > Hi,
> > 
> > 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.
> > 
> > cheers,
> > 
> > Stephan
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users