xen discuss - Dec 2009 - System Clock Offset in b129 dom0

James Lee wrote:
> Since upgrading to b129, I''ve noticed that my system clock is
ahead by
> five hours, exactly how much I am behind UTC (US Eastern Time).  The
> strange thing is it only happens when I have xen enabled.  If I
''svcadm
> disable milestone/xvm; reboot'' the clock is correct again.  If I
correct
> the time manually, ntp knocks it right back ahead again.
It looks like I''m the only one:
http://www.opensolaris.org/jive/thread.jspa?threadID=120016&tstart=0

In that thread someone posted a link to
http://southbrain.com/south/2009/09/rtc-sun-xvm-wrong-timezone-off.html
which solved my problem.  It''s interesting that I''ve never had
to do
that before.  Must be something new with Xen 3.4 vs 3.3.

James

Since upgrading to b129, I''ve noticed that my system clock is ahead by
five hours, exactly how much I am behind UTC (US Eastern Time).  The
strange thing is it only happens when I have xen enabled.  If I ''svcadm
disable milestone/xvm; reboot'' the clock is correct again.  If I
correct
the time manually, ntp knocks it right back ahead again.  Oddly enough,
even ntp knows my system clock is ahead:
> # ntpq -p
>      remote           refid      st t when poll reach   delay   offset 
jitter
>
=============================================================================>
+ntp1.Rescomp.Be 169.229.128.214  3 u   58   64  377  101.594  -179996 142.747
> +clock.trit.net  192.12.19.20     2 u   62   64  377  126.475  -179996
151.771
> +xanadu.fnerk.or 132.236.56.250   3 u   56   64  377   46.302  -179996
146.168
> *198.186.191.229 199.165.76.11    2 u   48   64  377  100.007  -179996
144.046
(see the huge offset)

My /etc/TIMEZONE and /etc/rtc_config files are correct compared with the
rest of my OpenSolaris systems.

Any ideas as to what''s going on?

Thanks,

James

James Lee wrote:
> James Lee wrote:
>> Since upgrading to b129, I''ve noticed that my system clock is
ahead by
>> five hours, exactly how much I am behind UTC (US Eastern Time).  The
>> strange thing is it only happens when I have xen enabled.  If I
''svcadm
>> disable milestone/xvm; reboot'' the clock is correct again.  If
I correct
>> the time manually, ntp knocks it right back ahead again.
> 
> It looks like I''m the only one:
> http://www.opensolaris.org/jive/thread.jspa?threadID=120016&tstart=0
> 
> In that thread someone posted a link to
> http://southbrain.com/south/2009/09/rtc-sun-xvm-wrong-timezone-off.html
> which solved my problem.  It''s interesting that I''ve
never had to do
> that before.  Must be something new with Xen 3.4 vs 3.3.
This is
   http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6908973

It''s being looked at..



Thanks,

MRJ

Hi,

> This is
>   http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6908973
As the documented workarounds (set RTC to UTC) don''t work for me and
because the
bug is quite annoying (mostly because emails carry wrong timestamps while using
Xvm), does anyone know about a more reliable workaround or even a fix?

Thank you, Nils

Same problem on my xVM enabled OpenSolaris dom0.
Bad workaround is to disable ntp and set time manually by hand (using date
command) and than restart Window... ups OpenSolaris.  :)  (restart as solution
sounds so Windows)
Because without restart time moves exacly 2 hours back from set time.
Also the solution from
http://southbrain.com/south/2009/09/rtc-sun-xvm-wrong-timezone-off.html does not
work for me.

Regards
Andrej
-- 
This message posted from opensolaris.org

Hello,

On May 10, 2010, at 12:40 PM, Andrej Javorsek wrote:
> Same problem on my xVM enabled OpenSolaris dom0.
> Bad workaround is to disable ntp and set time manually by hand (using date
command) and than restart Window... ups OpenSolaris.  :)  (restart as solution
sounds so Windows)
> Because without restart time moves exacly 2 hours back from set time.
> Also the solution from
http://southbrain.com/south/2009/09/rtc-sun-xvm-wrong-timezone-off.html does not
work for me.
This is what I did:

- set BIOS time to UTC

- set zone_info=UTC and zone_lag=0 in /etc/rtc_config

- set TZ=UTC in /etc/TIMEZONE

- enable ntpd

- after reboot the dom0''s time should be the correct UTC time

- shutdown all domUs; for each xVM domain remove the rtc_timeoffset

xm list -l domain | grep -v rtc_timeoffset > domain.sxp
xm new -F domain.sxp

- reconfigure each guest domain with BIOS time set to UTC

Hope this helps.

Kind regards,
Cristian

Thank you, this seems to solve the problem.

Best Regards!
Andrej
-- 
This message posted from opensolaris.org

Hi Christian,

thanks for describing your workaround.

Does anyone have a solution for having the dom0 opensolaris live in some other
timezone than UTC?

Nils

Oh,

things can be so simple. In my case, I added

TZ=Europe/Berlin
export TZ

to /etc/profile:

     gdm(1m)

     Before  launching  gdm-binary,  the  gdm  wrapper
     script sources the system profile(4) file  to  set  standard
     system   environment   variables ...

... so all processes I really care about for desktop use now live in CEST.

Christian, thanks again.

Nils