Hi everybody! I use Debian Etch with XEN. I get many of these messages the whole time: *********************************** Timer ISR/0: Time went backwards: delta=-10532651 delta_cpu=1467349 shadow=818028104078088 off=981700934 processed=818029096311513 cpu_processed=818029084311513 0: 818029084311513 1: 818029095679124 *********************************** Both in the Dom0 and the DomUs.... I found other people having this problem, but couldnt find a solution yet... Thank you in advance _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
h9802641@wu-wien.ac.at wrote:> Hi everybody! > > I use Debian Etch with XEN. I get many of these messages the whole time: > > > *********************************** > Timer ISR/0: Time went backwards: delta=-10532651 delta_cpu=1467349 > shadow=818028104078088 off=981700934 processed=818029096311513 > cpu_processed=818029084311513 > 0: 818029084311513 > 1: 818029095679124 > > *********************************** > > Both in the Dom0 and the DomUs.... > > I found other people having this problem, but couldnt find a solution > yet... > > Thank you in advanceAre you running NTP on DomU''s? Or have you set up your time systems to use UTC? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Zitat von Nico Kadel-Garcia <nkadel@gmail.com>:> h9802641@wu-wien.ac.at wrote: >> Hi everybody! >> >> I use Debian Etch with XEN. I get many of these messages the whole time: >> >> >> *********************************** >> Timer ISR/0: Time went backwards: delta=-10532651 delta_cpu=1467349 >> shadow=818028104078088 off=981700934 processed=818029096311513 >> cpu_processed=818029084311513 >> 0: 818029084311513 >> 1: 818029095679124 >> >> *********************************** >> >> Both in the Dom0 and the DomUs.... >> >> I found other people having this problem, but couldnt find a solution yet... >> >> Thank you in advance > Are you running NTP on DomU''s? Or have you set up your time systems to > use UTC?I am running this command hourly (cron) within the Dom0. ntpdate -s ts1.univie.ac.at at.pool.ntp.org ptbtime1.ptb.de I havent touched the time / date settings of the DomUs anyhow. Should I? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, On Sat, Oct 06, 2007 at 10:26:48AM +0200, h9802641@wu-wien.ac.at wrote:> I am running this command hourly (cron) within the Dom0. > > ntpdate -s ts1.univie.ac.at at.pool.ntp.org ptbtime1.ptb.deI would strongly advise not doing this, and instead running an ntpd. That goes for both Xen and non-Xen machines. Not only can ntpdate cause the clock to step backwards, but if one of the servers you list had its clock set wildly wrong then yours would get set wildly wrong too if it ever ran ntpdate against it.> I havent touched the time / date settings of the DomUs anyhow. Should I?In theory a domU is supposed to keep its clock locked to that of the dom0, so one only needs to run ntpd in dom0. However I have never found that to be reliable so have had to set /proc/sys/xen/independent_wallclock to 1 and run ntpd in every domU also. Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users