Red Hat Bugzilla – Bug 476075
use KVM pvclock code to detect/correct lost ticks
Last modified: 2015-10-26 07:56:50 EDT
Description of problem:
The upstream pvclock code is not directly applicable to RHEL5, because of the changes in timer infrastructure code. However, it should be possible to use the infrastructure from the vmware patches (from bug #463573) to use the pvclock code to detect and correct for lost ticks - potentially even better.
Justification: it is important that timekeeping on ovirt be at least as good as timekeeping on vmware.
Updating PM score.
You can download this test kernel from http://people.redhat.com/dzickus/el5
Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so. However feel free
to provide a comment indicating that this fix has been verified.
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~
RHEL 5.5 Beta has been released! There should be a fix present in this
release that addresses your request. Please test and report back results
here, by March 3rd 2010 (2010-03-03) or sooner.
Upon successful verification of this request, post your results and update
the Verified field in Bugzilla with the appropriate value.
If you encounter any issues while testing, please describe them and set
this bug into NEED_INFO. If you encounter new defects or have additional
patch(es) to request for inclusion, please clone this bug per each request
and escalate through your support representative.
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.