Hi, first some infos about my system: Debian Lenny (Xen 3.3.1 / 2.6.26-2-xen-amd64 ) running ~8 PV-DomUs (Debian Etch / 2.6.18.8-xen [i686] ) DomU-sysctl.conf: xen.independent_wallclock=1 DomU: cat /sys/devices/system/clocksource/clocksource0/available_clocksource jiffies tsc pit cat /sys/devices/system/clocksource/clocksource0/current_clocksource jiffies All DomUs are 100% equal, they execute some cronjobs every X minutes. The following problem is not limited to only one cronjob. It looks like the time is going crazy under load. This job should be executed every 2 minutes: ... Jun 9 23:54:01 host /USR/SBIN/CRON[13042]: (root) CMD (nice -n 15 -command-) Jun 9 23:56:01 host /USR/SBIN/CRON[13219]: (root) CMD (nice -n 15 -command-) Jun 9 23:58:01 host /USR/SBIN/CRON[13380]: (root) CMD (nice -n 15 -command-) ... Jun 10 03:11:03 host /USR/SBIN/CRON[32711]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:10 host /USR/SBIN/CRON[403]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:14 host /USR/SBIN/CRON[541]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:17 host /USR/SBIN/CRON[594]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:18 host /USR/SBIN/CRON[631]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:18 host /USR/SBIN/CRON[699]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:19 host /USR/SBIN/CRON[746]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:20 host /USR/SBIN/CRON[1450]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:20 host /USR/SBIN/CRON[6659]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:20 host /USR/SBIN/CRON[1518]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:21 host /USR/SBIN/CRON[1686]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:24 host /USR/SBIN/CRON[1881]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:24 host /USR/SBIN/CRON[1887]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:24 host /USR/SBIN/CRON[1989]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:25 host /USR/SBIN/CRON[2170]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:29 host /USR/SBIN/CRON[2366]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:30 host /USR/SBIN/CRON[2584]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:31 host /USR/SBIN/CRON[2941]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:32 host /USR/SBIN/CRON[3336]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:33 host /USR/SBIN/CRON[3506]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:33 host /USR/SBIN/CRON[3665]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:33 host /USR/SBIN/CRON[3884]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:34 host /USR/SBIN/CRON[4108]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:34 host /USR/SBIN/CRON[4323]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:34 host /USR/SBIN/CRON[4367]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:35 host /USR/SBIN/CRON[4700]: (root) CMD (nice -n 15 -command-) Jun 10 03:11:45 host /USR/SBIN/CRON[316]: (root) CMD (nice -n 15 -command-) Jun 10 03:12:12 host /USR/SBIN/CRON[929]: (root) CMD (nice -n 15 -command-) Jun 10 03:12:37 host /USR/SBIN/CRON[7162]: (root) CMD (nice -n 15 -command-) Jun 10 03:13:09 host /USR/SBIN/CRON[10560]: (root) CMD (nice -n 15 -command-) Jun 10 03:13:11 host /USR/SBIN/CRON[7368]: (root) CMD (nice -n 15 -command-) Jun 10 03:14:05 host /USR/SBIN/CRON[12202]: (root) CMD (nice -n 15 -command-) Jun 10 03:16:06 host /USR/SBIN/CRON[15341]: (root) CMD (nice -n 15 -command-) Jun 10 03:18:03 host /USR/SBIN/CRON[17821]: (root) CMD (nice -n 15 -command-) Jun 10 03:20:01 host /USR/SBIN/CRON[20941]: (root) CMD (nice -n 15 -command-) Jun 10 03:22:01 host /USR/SBIN/CRON[24310]: (root) CMD (nice -n 15 -command-) This is killing my DomUs, because they kill themself with OOM. I will now try to disable independent_wallclock and disable the DomU-ntp. What else could I do/check? Why do I don''t have a "xen" clocksource? Thanks, Fabian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, What I did: I disabled independent_wallclock, removed all ntp-packages (ntpdate, ntp). Now I found the following strange behavior: My DomU-time, compared with Dom0-time, is running away (+1s / 30s). I also tried to change the clocksource to "pit|tsc", but after: - echo -n ''pit'' > current_clocksource - echo ''pit'' > current_clocksource - echo -n ''tsc'' > current_clocksource - echo ''tsc'' > current_clocksource - Bootparam: clocksource=pit|tsc clocksource was still jiffies. I also compiled 2.6.18.8-xen (linux-2.6.18-xen.hg) again, nothing changed. I tried to set "timermode=0" and/or "hpet=1", nothing changed. Thanks for any hints, Fabian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, i also enabled HPET and used different Kernel/Xen-combinations, but still the time is running away and I don''t have a xen-clocksource in DomU. In Dom0 the xen-clocksource is avaiable. I just added ''consistent_tscs'' to xen.gz , but I still have no "xen" clocksource in DomU. I installed a clone on different hardware (i686 and amd64) and got xen-clocksource in DomU. What do I need to get xen-clocksource in DomU? or What could disable xen-clocksource in DomU? Thanks, Fabian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi again, I cloned both Hardwaresettings (HPET, ACPI) and Softwareconfiguration (bootparam, Xen-Config, Xen-Version), but I still have no Xen-Clocksource in DomU on one of the maschines. Is there really nobody who could give me a hint, why A has Xen-cocksource in DomU and B - not? Thanks, Fabian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, the "B" use a Xen kernel in with PV ? Olivier Fabian Zimmermann a écrit :> Hi again, > > I cloned both Hardwaresettings (HPET, ACPI) and Softwareconfiguration > (bootparam, Xen-Config, Xen-Version), but I still have no > Xen-Clocksource in DomU on one of the maschines. > > Is there really nobody who could give me a hint, why A has > Xen-cocksource in DomU and B - not? > > Thanks, > Fabian > > _______________________________________________ > 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
Hi Oliver,> the "B" use a Xen kernel in with PV ?yes, A and B use a "xen-kernel" in DomU. I tried "2.6.26 (Lenny), 2.6.18 (Etch) and 2.6.18.8 (Xen.org)", always the same: No Xen-Clocksource in DomU on B, but A has xen-clocksource with all kernels. Fabian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,>> the "B" use a Xen kernel in with PV ?I checked again every kernel. Now I found the following: Dom0 DomU xen-clocksource (DomU) 2.6.26-2-amd64 2.6.18-6 x 2.6.26-2-amd64 2.6.18.8 (old-32) x 2.6.26-2-amd64 2.6.26-1-686 ok 2.6.26-2-amd64 2.6.26-2-686 ok 2.6.26-2-amd64 2.6.18.8 (new-32) x 2.6.26-2-amd64 2.6.18.8 (new-64) x x = false ok = true (new = xen-2.6.18.hg ~ 19th Jun 15:00 CET) Did I miss something? When introduced xen a "Dom0-Version have to be DomU"-Binding? I''m really amazed. Is there somebody, who could explain it to me? I will repeat this test on server A and post the results, too. Thanks, Fabian FYI: I also detected, that every kernel is reporting other clocksources (on same hardware/xen/dom0-kernel). Sometimes only "Jiffies"; sometimes "jiffies tsc pit". _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi,> Dom0 DomU xen-clocksource (DomU) > 2.6.26-2-amd64 2.6.18-6 x > 2.6.26-2-amd64 2.6.18.8 (old-32) x > 2.6.26-2-amd64 2.6.26-1-686 ok > 2.6.26-2-amd64 2.6.26-2-686 ok > 2.6.26-2-amd64 2.6.18.8 (new-32) x > 2.6.26-2-amd64 2.6.18.8 (new-64) x > > x = false ok = true > (new = xen-2.6.18.hg ~ 19th Jun 15:00 CET)some further tests: Host Dom0 DomU clocksource(DomU) sk 2.6.26-2-xen-686 2.6.18-6-xen-686 jiffies pit sk 2.6.26-2-xen-686 2.6.18.8-xen (i386) jiffies tsc pit sk 2.6.26-2-xen-686 2.6.26-2-xen-686 xen jiffies bo 2.6.26-2-xen-amd64 2.6.18.8-xenU (amd64) jiffies tsc pit bo 2.6.26-2-xen-amd64 2.6.18.8-xenU (i386) jiffies tsc pit bo 2.6.26-2-xen-amd64 2.6.18-6-xen-686 jiffies pit bo 2.6.26-2-xen-amd64 2.6.26-2-xen-686 xen jiffies sk 2.6.18.8-xen0 (686) 2.6.18.8-xenU (686) jiffies tsc pit sk 2.6.18.8-xen0 (686) 2.6.26-2-xen-686 xen jiffies Even xen.org Dom0 = xen.org DomU is not enabling xen-clocksource. Is xen as clocksource obsolete, or is there something strange happening? Fabian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fabian Zimmermann
2009-Jun-19 18:40 UTC
[CLOSED][Xen-users] Sometimes xen-Clocksource in DomU
Hi,> Even xen.org Dom0 = xen.org DomU is not enabling xen-clocksource. Is > xen as clocksource obsolete, or is there something strange happening?So, after reading some code and asking google about some functions I think there was never a "xen"-clocksource in xen.org-kernels. It looks like it''s only in patched kernels like Lenny. ( http://lists.xensource.com/archives/html/xen-devel/2007-03/msg00242.html ) I found "clocksource_register(&clocksource_xen);" in 2.6.26 (Lenny) and 2.6.29, but there is no "xen" clocksource in 2.6.18-6-xen (Etch) and 2.6.18.8 (xen.org). So, back to beginning... If somebody has hints/answers to the following questions: Dom0 is updating Xens clock every minute, isn''t it? When will DomU "reread" the clock out of Xen? Why is cron/clock going crazy in high-load-situations, if I run ntpd-service on DomU and set independent_wallclock=1? Thanks, Fabian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fabian Zimmermann
2009-Jun-24 07:30 UTC
[Xen-users] possible solution for DomU time problem(s)
Hi, just for the archive: If you have trouble with DomU-time try different kernel in Dom0 and install ntpd in Dom0. I had the problem reproducealbe with 2.6.26 (Lenny), but with 2.6.18.8 and/or 2.6.29.5-xen (suse/gentoo-patched) the problem is gone. Bye, Fabian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users