Bug 520417 - Don't run hwclock on guests running kvmclock
Summary: Don't run hwclock on guests running kvmclock
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: ktune
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On: 519771
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-31 12:12 UTC by Glauber Costa
Modified: 2013-01-09 21:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-06 10:34:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Glauber Costa 2009-08-31 12:12:08 UTC
In the spirit of #518039, I think we should provide users with a script that disables invocation of hwclock at boot time, when we are running kvmclock.

The problem that it fixes has been reported for Fedora in #512376.

To summarize, all tricks done by hwclock are quite expensive. It means that by the time hwclock sets guest time, one or two seconds (sometimes even three) has already elapsed, and users will then see time in guest always behind (although with a constant delta, because of kvmclock). This leads to the need of an unnecessary ntp invocation on the guest to keep the time in sync.

The simple solution is, upon finding we're running kvmclock, do an mv /sbin/hwclock to /sbin/hwclock.old, or something like that. A reversal script can also be provided if we feel like it.

Note that this will not work on x86_64 until #519771 is fixed (it's in POST state)


Note You need to log in before you can comment on or make changes to this bug.