http://bugzilla.novell.com/show_bug.cgi?id=545191
User pgnet.dev@gmail.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=545191#c2
account disabled
Did you force the clocksource to jiffies
yes. but, it doesn't matter. in the kernel-default case, the default clocksource is "hpet", and available_clocksource includes {hpet, tsc, acpi_pm & jiffies} with currrent_clocksource = "hpet", all's fine. in the kernel-xen case, the Dom0's default clocksource is "xen", and available_clocksource includes {xen, jiffies} with BOTH currrent_clocksource = "xen" & "jiffies", the jitter's unacceptably large, preventing sync to timesources. docs are at best, unclear as to whether Dom0's clocksource should be == "xen" or "jiffies" when using ntpd fpr clock sync. i.e. any/all clocksource in Xen Dom0 +ntpd can't sync due, apparently, to excessive jitter.
explanation of the "noisy" part of the problem description
per above, case (1) jitter = {658.318, 652.232, 650.788} <- noisy, can't sync case (2) jitter = {2.679, 3.322, 2.906} <- typical/'quiet', sync is OK -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.