Bug 487467 - Third system date time case may be needed to address RTC Virtualization (RFE)
Third system date time case may be needed to address RTC Virtualization (RFE)
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-02-26 01:55 EST by Tom Mitchell
Modified: 2009-07-27 16:51 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-27 16:51:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tom Mitchell 2009-02-26 01:55:08 EST
Description of problem:
In a virtual world the virtual host can have trouble with local time not equal
to UTS or the 'local' time for the hosting OS.   Today we address
the case of the RTC running at local time or at UTS.   In a virtual
world a third notion of RTC or local time is possible where the virtual machine
is neither site local or UTS.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Build a system that host numerous virtual systems in a non UTS time zone.
2. Add multiple hosted services for customers in other time zones.
3. Add users on the hosted services that reside in other time zones.
Actual results:
  The only time zone that works "cleanly" may be the domain zero local time.

Expected results:
  The expectation is that time for remote users and customers is 
  more transparent.

Additional info:

 The easy way to address this might be $TZ in the environment for local users but useradd and friends do not currently address time zone issues.

See the check box at the bottom of System --> Administration --> Date Time
and the "Time Zone" tab (system-config-date).  
  Two cases are addressed: 1)'System clock uses UTS' or 2)not.   There is 
a third case where the system clock is virtualized and not equal
to UTS or the local TZ.  

If this was only addressed in xen other virtual machines could do it differently thus the need to address a third case administratively.

I encountered this third case on a web hosting site that was east coast,
with a client in Utah and I was in Calif....  None of the 'users' saw 
the correct time of day including those paying the bill without 'per user

And ntp may be the wrong place for this but I did not find a better bucket.
Comment 1 Tom Mitchell 2009-07-27 16:51:15 EDT
No need to clutter the system with a possible issue.
As the original author -- Closing....

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