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):
  N.A.

How reproducible:
  Easy


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
help'.

And ntp may be the wrong place for this but I did not find a better bucket.