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@lists.xensource.com http://lists.xensource.com/xen-users
On Mon, Oct 04, 2010 at 11:01:10AM +0100, 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.Some further info on this, It appears the HVM domU (windows server 2008) unexpectedly shut down at 18:51, after the unstable clocksource error. qemu-dm logs show a reset "reset requested in cpu_handle_ioreq." and xend.log shows a reboot [2010-10-02 18:51:03 1759] INFO (XendDomainInfo:2088) Domain has shutdown: name=ha-dc1 id=2 reason=reboot. This is like someone issuing "xm reboot domain" is it not? Is it possible that xen could have issued this reboot itself due to a crash? I can''t see any crash logs. Cheers, Mark> > Cheers, > Mark > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com > http://lists.xensource.com/xen-users >-- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov 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@lists.xensource.com http://lists.xensource.com/xen-users
Hi Steven, Both are 64bit. dom0 is amd64 and windows server 2008 R2 has to be 64 bit. Regards, Mark 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@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > -- > ------------------------------------------------------------------ > Steven C. Timm, Ph.D (630) 840-8525 > timm@fnal.gov 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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
No-one had any similar issues? What do people do to ensure stable time across dom0 and all domU''s?? Regards, Mark On Mon, Oct 04, 2010 at 01:00:51PM +0100, Mark Adams wrote:> On Mon, Oct 04, 2010 at 11:01:10AM +0100, 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. > > Some further info on this, It appears the HVM domU (windows server 2008) > unexpectedly shut down at 18:51, after the unstable clocksource error. > qemu-dm logs show a reset "reset requested in cpu_handle_ioreq." and > xend.log shows a reboot > > [2010-10-02 18:51:03 1759] INFO (XendDomainInfo:2088) Domain has shutdown: name=ha-dc1 id=2 reason=reboot. > > This is like someone issuing "xm reboot domain" is it not? Is it > possible that xen could have issued this reboot itself due to a crash? I > can''t see any crash logs. > > Cheers, > Mark > > > > > Cheers, > > Mark > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Oct 5, 2010 at 14:02, Mark Adams <mark@campbell-lange.net> wrote:> No-one had any similar issues? > > What do people do to ensure stable time across dom0 and all domU''s??NTP for dom0. What I use for domU depends on whether it''s HVM or PVM, but NTP by choice. -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn''t become a monster. Friedrich Nietzsche _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I use ntp in dom0 but it didn''t help in this event. It must have crashed out as was running before the time change but not after! Regards, Mark On 5 Oct 2010, at 18:06, Rob MacGregor <rob.macgregor@gmail.com> wrote:> On Tue, Oct 5, 2010 at 14:02, Mark Adams <mark@campbell-lange.net> wrote: >> No-one had any similar issues? >> >> What do people do to ensure stable time across dom0 and all domU''s?? > > NTP for dom0. What I use for domU depends on whether it''s HVM or PVM, > but NTP by choice. > > -- > Please keep list traffic on the list. > > Rob MacGregor > Whoever fights monsters should see to it that in the process he > doesn''t become a monster. Friedrich Nietzsche > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users