Bug 744978 - Timer drift in win2k8R2 VM
Summary: Timer drift in win2k8R2 VM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Ronen Hod
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-11 04:09 UTC by Teruaki Ishizaki
Modified: 2014-12-15 00:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-26 08:51:33 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Teruaki Ishizaki 2011-10-11 04:09:52 UTC 
Description of problem:
Timer drift in win2k8R2 64bit VM on KVM.
VM uses SNTP client(AdjustPC) and we verified timer drift with AdjustPC's event log.(drift over 1000msec)
We tried default clocksource and PMTIMER, but it didn't solve problem.
(/set {default} USEPLATFORMCLOCK on)

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/chap-Virtualization-KVM_guest_timing_management.html

Version-Release number of selected component (if applicable):
Hypervisor: kernel-2.6.18-164.11.1.el5, kvm-83-105.13
Guest VM: Windows2008R2 64bit

How reproducible:
That problem is reproducible on our customer's environment but we can't reproduce it now.
Our customer's VM has 8 VCPUS and 10G memory.
  
Actual results:
Timer drift in Windows2008R2
Comment 1 Ronen Hod 2012-02-01 14:26:48 UTC 
Does the problem still exist?
If you failed to reproduce it, can you tell the differences?
The problem was reported in 5.4. If we fix it, will your customer switch to RHEL5.9 or even RHEL6.3?
It looks like this bug is not worth the effort, and it might have already been solved in one of our recent releases.
Please let me know what you think.

Thanks, Ronen.
Comment 2 Ronen Hod 2012-02-26 08:51:33 UTC 
It seems as if there isn't much interest in this bug. Closing.
Note You need to log in before you can comment on or make changes to this bug.