This bug has been copied from bug #543137 and has been proposed to be backported to 5.4 z-stream (EUS).
Created attachment 383438 [details] testscript and results under kvm-83-105.el5_4.13/18 with windows guests
Steps for Windows guests: 1. under cygwin, run "ntpdate -b clock.redhat.com" to adjust time. 2. run drift_test.exe as noted in https://bugzilla.redhat.com/show_bug.cgi?id=543137#c13 3. under cygwin, run "./checktime.sh <min> > out_file", which shall last for <min> minutes Results: ------------------------------------------------------------------- guests | kvm-83-105.el5_4.13 (sec) | kvm-83-105.el5_4.18 ------------------------------------------------------------------- win2k3-unp | ~127 | ok win2k3-smp2 | ~120 | ok (tested for 120 mins) win2k8-unp | ~115 | ok win2k8-smp2 | ~123 | ok ------------------------------------------------------------------- Notice cases in the above table all run for 10mins unless specially noted ,and "~127" means time drifted for around 127 seconds within 10 mins for instances. Details can be seen via #7.
Created attachment 384555 [details] Intel host: test results under kvm-83-105.el5_4.13/18 with windows guests
host: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm ------------------------------------------------------------------- guests | kvm-83-105.el5_4.13 (sec) | kvm-83-105.el5_4.18 ------------------------------------------------------------------- win2k3-32-unp | ok | ok win2k3-32-smp2 | ~47 (5min) | ok win2k3-64-unp | ~167 (10min) | ok win2k3-64-smp2 | ~175 (10min) | ok ------------------------------------------------------------------- win2k8-32-unp | ~50 (4min) | ok win2k8-32-smp2 | ~42 (5min) | ok win2k8r2-unp | ~40 (4min) | ok win2k8r2-smp2 | ok | ok ------------------------------------------------------------------- Notice "~47 (5min)" means time drifted for around 47 seconds within 5 mins for instance. Details can be seen via #9. p.s. In comment #8, host is AMD, win2k3 is win2k3-64, and win2k8 is win2k8r2 to be exact.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0088.html