WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] time jumping back and forth

To: christian mock <cm@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] time jumping back and forth
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 20 Sep 2004 22:50:28 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Mon, 20 Sep 2004 22:53:04 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Fri, 17 Sep 2004 22:39:08 +0200." <20040917203908.GB9462@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> I'm running a 2.0 snapshot from sept 11 with 2.6.8.1, and the system
> time is jumping back and forth in a domain -- partly it is
> synchronized with Dom0's time (which is set via ntpd), but then it
> jumps ahead, and then back again, as seen in these consecutive lines
> from syslog:
> 
> Sep 17 09:22:39 [...]
> Sep 17 10:34:24 [...]
> Sep 17 09:23:40 [...]
> 
> 9:22/9:23 is the correct time. I've got the impression (but have not
> analyzed it systematically) that a few minutes after boot, everything
> turns normal.

Very odd.

Presumably you're running your un-priv domains with
/proc/sys/xen/independent_wallclock set to the default of 0?

In this event, any attempt to set or adjust the wall clock time
in an unpriv domain should be ignored: it should remain slaved to
dom0's wall clock time, which will either be free running from
the hardware RTC, or synchronised via NTP if you're running ntpd.

This certainly all seemed to work fine for 2.4. 

Are you 100% sure you haven't got ntpdate running in your startup
scripts or crontab? It should be ignored, but its possible that
the port from 2.4 to 2.6 wasn't quite right.
 

Ian


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel