https://bugzilla.novell.com/show_bug.cgi?id=655516 https://bugzilla.novell.com/show_bug.cgi?id=655516#c0 Summary: kvm time drift seen in virtuals (winxp, win7 32 & 64) Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: bruno@ioda-net.ch QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=401805) --> (http://bugzilla.novell.com/attachment.cgi?id=401805) Smolt profile (smolt server done) User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-1.2 Firefox/3.6.12 Actually we saw time drifts in virtuals machine. Not always the same. Varying from vm to vm, activity or not. Reproducible: Always Steps to Reproduce: 1.install kvm oss+update or /repositories/Virtualization/openSUSE_11.3/ 2.build an windows xp32 vm with 2Gb ram, and lvm disk virtio driver for disk & net 3.start the vm, and apply the tests describe here https://bugzilla.redhat.com/show_bug.cgi?id=555727 Actual Results: net time \\dumbo /set /Y Y:\>ntpdate -b -q dumbo.disney.interne server 192.168.50.1, stratum 3, offset 0.983696, delay 0.02554 23 Nov 15:31:50 ntpdate[2580]: step time server 192.168.50.1 offset 0.983696 sec Y:\>ntpdate -b -q dumbo.disney.interne server 192.168.50.1, stratum 3, offset 28.509063, delay 0.02554 23 Nov 15:43:38 ntpdate[3004]: step time server 192.168.50.1 offset 28.509063 se c during that time drift_test.exe is running alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second alarm_handler called, interrupt rate = 999.50 interrupts/second stable at 999.50 Expected Results: no time drift ( or something like <=1minutes/hour Will attach also a qemu xml definition file. We see that with 0.12.5 and now 0.13 Booting windows with the /usepmtimer or without doesn't change fondamentaly the pb. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.