search for: msg01269

Hi, Sometimes, seemingly randomly, long-running Xen domains, using clocksource xen, have their clock shift by ~3000 or ~36000 seconds, often with the dom0 complaining about clocksource tsc. The number changes if the hypervisor is explicitly told to use clocksource=pit, but it still happens. It doesn''t seem to be particularly hardware-specific. See also http://bugs.debian.org/599161 I

I have built on clean system with xen-unstable 25374 and stops with this error: gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -D__XEN_TOOLS__ -MMD -MF .libxl.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls -Werror -Wno-format-zero-length