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/
Home Products Support Community News


Re: [Xen-users] Clock (time) issue

To: Steven Timm <timm@xxxxxxxx>
Subject: Re: [Xen-users] Clock (time) issue
From: Mark Adams <mark@xxxxxxxxxxxxxxxxxx>
Date: Mon, 4 Oct 2010 15:37:35 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 04 Oct 2010 07:38:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.64.1010040906460.28703@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20101004100110.GA28376@xxxxxxxxxxxxxxxxxx> <Pine.LNX.4.64.1010040906460.28703@xxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
Hi Steven,

Both are 64bit. dom0 is amd64 and windows server 2008 R2 has to be 64


On Mon, Oct 04, 2010 at 09:08:07AM -0500, Steven Timm wrote:
> Mark, are your domU's 32-bit or 64-bit, likewise with dom0?
> We have seen the domU clock on a 32-bit instance jump forward
> by 40-80 minutes for no good reason and stay stuck there until
> the outside world catches up (and any time set commands fail).
> But never saw dom0 clock jump.
> Steve
> On Mon, 4 Oct 2010, Mark Adams wrote:
>> Hi All,
>> Im running Xen 4.0.1-rc6 Debian squeeze with pvops 2.6.32-21 kernel.
>> Today I noticed (when kerberos to the domain controllers stopped
>> working..) that the clock was 50 minutes out in dom0 -- This caused the
>> HVM windows domain controllers to have the wrong time.
>> I'm not sure if this is a kernel issue or a xen issue, but the only
>> thing related is I can see the following in the kernel log:
>> Oct  2 18:50:33 havhost1 kernel: [623480.977748] Clocksource tsc unstable 
>> (delta = -2999660303788 ns)
>> But I also see in the dmesg log that xen is using it's own clock.
>> [    7.676563] Switching to clocksource xen
>> I can't identify anything else in the logs to indicate when the time
>> might have changed. I have a few other dom0 at the same level that
>> haven't decided to change the time.
>> Can anyone confirm whether xen controls the time or the kernel? Also
>> when I corrected the time in dom0 it was still wrong in HVM domU -- How
>> long does it take for this to propogate? (I rebooted the VM's to correct
>> it immediately).
>> Any other pointers on how to ensure stability of clocks from dom0 to
>> domU HVM hosts (and pv for that matter..) would be appreciated.
>> Cheers,
>> Mark
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
> -- 
> ------------------------------------------------------------------
> Steven C. Timm, Ph.D  (630) 840-8525
> timm@xxxxxxxx  http://home.fnal.gov/~timm/
> Fermilab Computing Division, Scientific Computing Facilities,
> Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>