Re: [Xen-devel] time does not move forward in HVM guests

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 05.07.17 at 09:25, <olaf@xxxxxxxxx> wrote:
> On Wed, Jul 05, Jan Beulich wrote:
> 
>> > clock_getres(CLOCK_MONOTONIC) indicates a resolution of 1ns.
>> But what's the implied meaning of resolution here? See below.
> 
> I have no ide what the returned value is supposed to promise.
> 
>> Or did you perhaps test with an older version, where the time
>> handling backports from master hadn't been there yet?
> 
> It was weeks ago, and I have not seen it since then. I think it is fixed
> in one way or another.
> 
>> > A workaround is booting the domU kernel with 'clocksource=tsc nohz=off 
>> > highres=off'.
>> What clocksource does the system use by default? HPET?
> 
> HPET would be really really slow. The default clocksource is "xen".

Oh, even for HVM. Doesn't that go back to the missing vDSO
support then again, which we had discussed just last week?

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel