similar to: Heavy clock drifts inside of KVM guests (qemu-kvm 2.1.2)

I installed CentOS 4.4 32 bit on a dual core AMD64 motherboad. Its a Tyan Tomcat K8E motherboard with socket 939. The clock keeps drifting off like 5+ minutes an hour. Run ntpupdate hourly to compensate. Any ideas why or how to fix? Matt

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

This must be documented somewhare but I checked the Xen 3.0 manual and the word "clock" doesn''t even exist in it. I checked the FAQ as well. I am running Xen 3.0.1 and an AMD64 CPU. I found that DOMUs time clock drifts ahead. I installed ntpdate and it reports to change the time but it does not. David _______________________________________________ Xen-users mailing list

I was wondering if someone could help with selinux context for the portable openntpd library on centos7. I compiled openntpd-6.0p1 and it runs great on centos7, but have not had much luck with selinux contexts for it. This is what I tried- semanage fcontext -a -t ntp_conf_t /usr/local/etc/ntpd.conf # seems to work semanage fcontext -a -t ntpd_exec_t /usr/local/sbin/ntpd # gets reset on

Hello. I''m a long time cfengine user, some might say sufferer, and I have finally managed to get around to experimenting with Puppet. So far I''m very impressed. I am trying to get puppet to configure the openntpd config file, from an ERB template, based on the node definition in the site config. What I''m trying to understand is why when I define a variable in a child

Hello, I am currently attempting to run some windows games through wine, specifically Fable - The Lost Chapters and The Elder Scrolls III - Morrowind and I am experiencing problems with my cursor drifting during game play. When I start the game (as soon as the menu screen) the mouse is initially stable, but after I move the mouse it will begin to drift vertically down at a constant speed

Processing commands for control at bugs.debian.org: > reassign 674907 xen Bug #674907 [openntpd] shifts the clock by 50 minutes unexplicably under a Xen dom0 Bug reassigned from package 'openntpd' to 'xen'. No longer marked as found in versions 3.9p1+debian-8~bpo60+1. Ignoring request to alter fixed versions of bug #674907 to the same values previously set > found 674907

Hi, FYI, Red Hat released an advisory today about a vulnerability in Ruby. So far it doesn't appear in the VuXML, but am I correct in presuming it will soon? https://rhn.redhat.com/errata/RHSA-2006-0604.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3694 cheers, -- Joel Hatton -- Infrastructure Manager | Hotline: +61 7 3365 4417 AusCERT - Australia's national

Hi everyone, I''m working in a firm that monitor wan networks. We have several nagios installed on virtual machines. Recently we noticed that the DomU''s clocks are not synced with the Dom0 and the clocks are wrong. So we tried to sync DomU''s via openntpd but it generates errors in nagios. Logs indicate "Time goes back". So we want to sync DomU with Dom0 and

Hi, We have a little over 100 servers, almost all running CentOS 5.7. Virtually all are Dell servers, generally a mix of 1950s, R610s, and R410s. We use NTP and/or PTP to sync their clocks. One phenomenon we've noticed is that (1) on reboot, the clocks are all greatly out of sync, and (2) if the PTP or NTP process is stopped, the clocks start drifting very quickly. If it was isolated to

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

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

On Debian Squeeze (2.6.32-5) running Xen 4.0, I have created 2 Ubuntu Lucid Lynx (Ubuntu 10.04) vms. The vms, in a stress test, pass a large file between them via nfs file sharing. A previous entry in this forum helped to establish that some ethernet cards improve VM IO performance. However, our box installed with better intel nics is still rebooting under heavy VM IO loads. The kernel call

Processing commands for control at bugs.debian.org: > user debian-qa at lists.debian.org Setting user to debian-qa at lists.debian.org (was anbe at debian.org). > affects 774889 + xfswitch-plugin Bug #774889 [gdm3] gdm3: fails to upgrade squeeze -> wheezy -> jessie - trying to overwrite /usr/share/gdm/BuiltInSessions/default.desktop Added indication that 774889 affects xfswitch-plugin

Package: logcheck-database Version: 1.2.37 Severity: normal Hello again, openntpd gives messages like these failry often: Apr 7 14:25:55 terminus ntpd[673]: peer 204.17.42.202 now invalid Apr 7 14:26:10 terminus ntpd[673]: peer 204.17.42.202 now valid I am not sure if this is something that an admin may find relevant but they happen fairly often and they do not offer a lot of info for me.

My dom0 systems all run ntpd to keep their clock synchronized, and I just noticed my domU systems all have a little different clock, and that happens right after boot. IE, right after xm create domU, I did a quick''n''dirty check this way: luca@dom0 ~ $ ssh domU "uptime; date"; date Password: 16:11:31 up 0 min, 0 users, load average: 0.43, 0.12, 0.04 Thu Dec 8

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support re-using pvclock_page VVAR as VCLOCK_PVCLOCK is mutually exclusive with VCLOCK_HVCLOCK at run time. Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> --- arch/x86/entry/vdso/vclock_gettime.c | 48

hello, a big time drift appears along time on a guest VM (time is going too slow on the guest). here the setup: ~ physical machine ~ Centos 6.0 x86_64 time set with ntpd Intel(R) Xeon(R) CPU X5650 /proc/cpuinfo shows the "constant_tsc" bit. ~ guest OS ~ Centos 6.0 x86_64 /proc/cpuinfo : processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support by adding hvclock_page VVAR. Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> --- arch/x86/entry/vdso/vclock_gettime.c | 36 +++++++++++++++++++++++++++++++++++ arch/x86/entry/vdso/vdso-layout.lds.S | 3 ++-

Hi. I''ve got a strange problem with xen migration under Ubuntu Gutsy 7.10. I have two machines set up with a DRBD 8.2.4 partition shared between them. This uses the new block-drbd feature where you can set a disk partition using something like this disk = [ ''drbd:storm,sda1,w'' ] in the .cfg file. This allows me to do live migration now. However,