On 25/06/14 10:43, Rob Heemskerk wrote:
Not sure what it's worth and how it is implemented on other virtualisation
platforms but according to vmware docs they have a virtual tsc. It is set when
the vm is powered on but when the vm is moved to a different host (or resumed
more generally) it kee
Part of this thread has gone OT.
I don't think this is the right list to be discussing this. the Leap Second
Discussion List is available for exactly this debate.
However, that said, here's my 2 cents.
As has been mentioned, UTC with leaps seconds, has been defined to track UT1
and thus sol
Op maandag 23 juni 2014 15:54:13 UTC+2 schreef David Woolley:
> On 23/06/14 13:12, Miroslav Lichvar wrote:
>
> > I think it all depends on the VM implementation and what clocksource
> > is used in the guest. If the guest is using tsc (i.e. its frequency is
> > independent of the host clock), it wi
On Tue, Jun 24, 2014 at 06:13:17PM -0500, Mike S wrote:
> On 6/24/2014 5:59 AM, Miroslav Lichvar wrote:
> >To me, it seems the reasonable thing to do would be to decouple UTC and
> >UT1 completely and make the adjustment at a higher level like
> >timezones if necessary.
>
> You're doing it wrong.
On Tue, Jun 24, 2014 at 06:25:37PM +0200, Jochen Bern wrote:
> On -10.01.-28163 20:59, Miroslav Lichvar wrote:
> > Agreed, but wouldn't switching to TAI everywhere be much more
> > difficult than stopping messing with UTC and keep it a fixed offset
> > from TAI?
>
> Having computer clocks run on U
