Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 660239

Summary: clock drift when migrating a guest between mis-matched CPU clock speed
Product: Red Hat Enterprise Linux 5 Reporter: RHEL Program Management <pm-rhel>
Component: kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.5.zCC: bcao, cpelland, cww, danken, dougsland, gcosta, iheim, jwest, mjenner, mkenneth, pm-eus, spurrier, tburke, virt-maint, xtian, zamsden
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kvm-83-164.el5_5.28 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-20 17:37:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 655990    
Bug Blocks: 556823, 580948    

Description RHEL Program Management 2010-12-06 08:22:15 UTC
This bug has been copied from bug #655990 and has been proposed
to be backported to 5.5 z-stream (EUS).

Comment 9 Xiaoli Tian 2010-12-14 02:31:43 UTC
It has been verified on AMD host with kernel-2.6.18-194.26.1.el5 with kvm-83-164.el5_5.29

the result is as following:
ntpdate -q clock.redhat.com
server 66.187.233.4, stratum 1, offset 1.878373, delay 0.29205
14 Dec 09:26:15 ntpdate2601: step time server 66.187.233.4 offset 1.878373 sec
ntpdate -q clock.redhat.com
server 66.187.233.4, stratum 1, offset 1.879503, delay 0.29243
14 Dec 09:26:22 ntpdate2602: step time server 66.187.233.4 offset 1.879503 sec
ntpdate -q clock.redhat.com
server 66.187.233.4, stratum 1, offset 1.879385, delay 0.28969
14 Dec 09:26:38 ntpdate2603: step time server 66.187.233.4 offset 1.879385 sec
ntpdate -q clock.redhat.com
server 66.187.233.4, stratum 1, offset 1.849693, delay 0.27289
14 Dec 09:30:29 ntpdate2610: step time server 66.187.233.4 offset 1.849693 sec
ntpdate -q clock.redhat.com
server 66.187.233.4, stratum 1, offset 1.837023, delay 0.27748
14 Dec 09:32:33 ntpdate2615: step time server 66.187.233.4 offset 1.837023 sec
ntpdate -q clock.redhat.com
server 66.187.233.4, stratum 1, offset 1.829853, delay 0.27637
14 Dec 09:34:21 ntpdate2619: step time server 66.187.233.4 offset 1.829853 sec
vi ntpdate.result
ntpdate -q clock.redhat.com
server 66.187.233.4, stratum 1, offset 1.774460, delay 0.30309

Comment 10 Mike Cao 2010-12-14 02:53:23 UTC
On Intel host with different TSC rate ,Verified on
# uname -r
2.6.18-194.30.1.el5
# rpm -q kvm
kvm-83-164.el5_5.29

Actual Results:
No time shift after migration.

Base on above and comment #9, this issue has been fixed ald.

Comment 13 errata-xmlrpc 2010-12-20 17:37:10 UTC
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-0998.html