|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] dom0 clock skew
Hi Ulrich,
thanks for the reply. But I found something that seems to be related to my
clock issue. I posted it on xen-devel, see below. So I guess my clock skew is
just a symptom...
<quote>
Hi all,
I have a very strange clock skew problem on my Server since running Xen 3.0.3
that I have never seen before on the same machine running Xen 2.0.x.
Now I compared boot messages from the old and new installation and I saw a
huge difference in the reported CPU speeds under 3.0.3 hypervisor. Could this
be a reason for the clock skew?
Xen 2.0.x:
Boot1: <6>Xen reported: 498.762 MHz processor
Boot2: <6>Xen reported: 498.765 MHz processor
Xen 3.0.3:
Boot1: <6>Xen reported: 556.714 MHz processor
Boot2: <6>Xen reported: 621.840 MHz processor
Hardware is a Dual CPU Intel 440BX Server Board with 2 PIII 500 Cpu's (I know,
it's veery oooold...)
</quote>
Answer by Keir Fraser:
<quote>
It does seem likely. The old messages were correct and the new ones are
wrong, for some reason. I don;t think the calibration code has changed
significantly but I'd have to check that.
-- Keir
</quote>
On Monday 08 January 2007 15:25, Ulrich Windl wrote:
> On 29 Dec 2006 at 0:09, Alexander Wilms wrote:
> > Hello all,
>
> As I'm unsure what hwclock is actually doing, try to replace "hwclock" with
> "cat /proc/driver/rtc | head -2 | awk '{ print $3 }' | tr '\012' ' '".
> Maybe also replace "date" with "date +'%D %T.%N'".
>
> On my Dom0 I see this:
> # cat /proc/driver/rtc | head -2 |awk '{ print $3 }' | tr '\012' ' '; date
> +'%D %T.%N'
> 14:22:15 2007-01-08 01/08/07 15:23:04.345571000
>
> It seems the system time is OK, but the RTC isn't updated. I run NTP and
> independent clocks. (RTC is UTC, local timezone is 1h ahead of UTC)
>
> Ulrich
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|