similar to: real time clock drift

Displaying 20 results from an estimated 3000 matches similar to: "real time clock drift"

2006 Nov 24
19
Time/clock issues with Xen 3.0.3?
The time appears to be perfect inside dom0, however all the domU''s tend to have a slightly faster date which gets further out of sync every day. I''m currently using Xen 3.0.3 with Gentoo Linux, under 3.0.2 I had no problems with domU clocks. Are there any known issues which could cause this? I''d strongly prefer not to run ntpd in every domU, having all domU clocks in
2010 Apr 25
2
hardware clock drift and CDR
Hi, I've noticed that one of my new servers (new mobo) if drifting slowly backwards in time (in aprox. 24 hours, system time drifts back 5 minutes). I have an ntpd process which is supposed to sync with a lan time server but it's not quite working. So I'm launching a manual ntpdate or ntp-client once an hour and that seems to work. However, suppose I update system time at every hour
2009 Jul 01
5
Xen time drift issues
Hello everyone! I been observing some peculiar time drift on my Xen domains (dom0 and domUs). The time (as returned by timeofday) on my domains drifts at an almost steady rate from the real time ( as read from the time stamp counter ). The drift is so constant that it makes me think there should be some simple explanation for it in the way Xen keeps time. Some info about my set up: guest OS:
2007 Sep 03
5
Dom0 <> DomU clock sync
Hello ! Just a quick question about time synchronization between xen dom0 and domUs... We''re running Xen 3.1 64-bit, with 32 and 64 bits linux guests. It''s up since 89 days and the domU''s time is around 5 minutes behind the dom0, which is updated via ntpdate... Any idea why it doesn''t sync the guests even that /proc/sys/xen/independent_wallclock is 0 ?
2009 Jan 11
2
drifting clock in domUs
Hello, On a xenserver with several (39) domUs, we experience problems with the system clock of the domUs. The clock seems to drift away several seconds up to two minutes from the dom0 clock. We do have set independent_wallclock=0. According to the docs (i.e. http://wiki.xensource.com/xenwiki/InstallationNotes) that way domUs should use the dom0 clock, but apparently that''s not the case.
2008 Nov 19
1
domUs Clock synchronisation
Hi everybody! I know this is an ultraknown issue, but in my case i think it is going beyond. As you may guess my domUs clocks go faster or slower They come with the same OS (Centos 5 2.6.18-92.1.18.el5 ) but each of them have a different clock speed. Why? Dom0 does not syncronize domUs : So i watched out looking for any solution.... First attempt: /proc/sys/xen/independent_wallclock = 0
2012 Jun 28
8
GPLPV, clock drift and PVUSB in Windows XP HVM
1. Shouldn''t the GPLPV drivers take care of the (bad) clock drift I''m experiencing in my Windows XP HVM? Or is there some other way around this problem that I haven''t been able to find on Google? How can I tell if the GPLPV drivers are active? I''ve added the /gplpv switch to the boot.ini file and the virtual NIC is definitely using the GPLPV version but other
2007 Nov 06
6
dom0 and domU differs after ntpdate
Hi all, I''m experiencing problems with time: after I sync time both into dom0 and dom1 with public ntp servers, times are not the same. Do you have the same problem? Thanks Marco _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2006 Feb 26
17
domU clock over 23s off
Hey, I have rather new installation of xen, dom0 is running ntpd and is perfectly in time. All domU''s are ~23s in future. Running ntpd on the domU''s seem to have no effect, /proc/sys/xen/independent_wallclock appears to have no effect. I''m running xen-unstable and 2.6.16-rc4 in AMD64 box. Any tip would be appricated. Thanks, -- ++ytti
2006 Oct 11
9
time synchronization problem (using NTP)
Hi, using SLES10 I''m unable to synchronize the time of DomU with that of Dom0. There is a persistent offset of about 3 seconds! Here''s a small history (not actual output): remote refid st t when poll reach delay offset jitter rkdvmso1.dvm.kl 192.168.0.11 5 u - 64 1 0.136 -2977.1 0.099 *rkdvmso1.dvm.kl 192.168.0.11 5 u 2 64
2012 Apr 09
4
guest os time drift wild
HI, guys Recently,I met a problem. Xen''s version: 3.4.3 guest os:redhat 4.8 32bit And xen.independent_wallclock = 1 has been set. The time of guest os change to be fast suddenly, about 2000 second. because the change is too wild, ntp didn''t sync to the ntp server''s time. my application is dependent on the systme time. And this occurs a lot of times. I don''t
2006 Feb 07
11
date in domU
Hi all, where can I set the date in domU. ''ntpdate -u ...'' works but dosn''t set the date. date MMDDhhmm has also no effect. What can I do? -- cu Roland Kruggel  mailto: rk-liste@gmx.de System: Intel 3.2Ghz, Debian etch, 2.6.15, KDE 3.4 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com
2008 Dec 26
7
Installing domU from ISO image file
I am trying to install CentOS from an ISO image file but the installer does not see a CD-ROM drive. The VNC viewer works but the CentOS installer indicates "Unable to find any devices of the type needed for this installation type." Then it prompts with "[Select driver] [Use a driver disk] [Back]". I have tried several variations of the "disk" paramater, all
2008 Jan 08
1
Xen clock drift
Hello All, Consider a CentOS-5.1 Xen server (2.6.18-53.1.4.el5xen) hosting two domains running CentOS-5.1 (2.6.18-53.1.4.el5). One domain has a fairly accurate clock, the other domain has a clock that gains ungodly amounts of time, roughly one minute every two or three minutes. For a fix, one suggestion is to run this command in DomU: echo 1 > /proc/sys/xen/independent_wallclock This
2011 Dec 15
2
time issue with puppet
Hi, I have the following manifest that basically syncs the time for nodes really out of sync and ntpd can''t drift the time back fast enough. The problem is that when puppet executes the catalog, and puppet changes the time, puppet never finishes because it can''t calculate the "run time" since puppet changed the time during the puppet run. Is this a bug? Should I do
2008 Apr 22
0
guest clock
I have numerous problems with my para- and hardware- virtualizated guests. Clock in guests drifts up to many days. Sometimes it happens after xendomains service saves and restores state on reboot, sometimes not, sometimes it happens when I am sleeping :). I use latest fedora 8 with latest updates (I have had problem since fedora 6 ...) My proc settings: /proc/sys/xen/permitted_clock_jitter is
2016 Jun 21
0
Heavy clock drifts inside of KVM guests (qemu-kvm 2.1.2)
Dear list(s), we are running a cluster of virtual machines on ganeti 2.15.2 on top of qemu-kvm 2.1.2. Hosts are Debian jessie (Kernel 3.16). We have big trouble with timekeeping on guests, no matter if these guests are lenny, squeeze, wheezy or jessie. Clock drifts heavily on some, others are fine. There is no obvious pattern on which guest this happens and on which not, but it seems the clock
2016 Jun 21
0
Heavy clock drifts inside of KVM guests (qemu-kvm 2.1.2)
Dear list(s), we are running a cluster of virtual machines on ganeti 2.15.2 on top of qemu-kvm 2.1.2. Hosts are Debian jessie (Kernel 3.16). We have big trouble with timekeeping on guests, no matter if these guests are lenny, squeeze, wheezy or jessie. Clock drifts heavily on some, others are fine. There is no obvious pattern on which guest this happens and on which not, but it seems the clock
2005 Aug 04
1
PolyCom SoundPoint 300 and distinctive ring
I am looking for clues on how to configure distinctive ring for a PolyCom SoundPoint 300. Does ALERT_INFO apply? If so, how? Thanks, David Koski david.nospham@kosmosisland.com
2011 May 14
9
DomU clock out of sync
Hey all, I was watching some logs on a domU today and i suddenly noticed that the timestamps were off by something on the order of 47 seconds. I was surprised because *I don''t* run independent wall clocks. I checked some other domUs and the "drift" was also very close to that of the first domU. I also checked another dom0, Here the domUs were "only" out of sync by