Niall Fleming BSc. (Hons)
Systems Administrator
Webanywhere Limited
Phone: 0800 862 0131 Ext: 203
Web:
http://www.webanywhere.co.uk
Aire Valley Business Centre, Lawkholme Lane, Keighley, BD21 3BB
Registered in England with company number 4881346
On Mon, Nov 14, 2011 at 11:31:51AM -0800, Jeremy Fitzhardinge wrote:
On 11/14/2011 10:00 AM, Konrad Rzeszutek Wilk wrote:
Right. With those patches too (he used the xen-settime patch set which has it).
The hypercall is done (and the do_settime gets called) and the results are saved
in the RTC. And the wc_sec and wc_nsec are updated and propagated.
The problem is that wc_sec and wc_nsec are only propagated to the
existing guests.
If you launch a new guest after the 'hwclock', the new guests
retains the old wallclock time.
Existing (pvops) guests shouldn't see updated wallclock time, because
they never look at the hypervisor's wallclock after boot time.
It's surprising that new guests don't see the updated wallclock though.
That sounds like a Xen issue.
<nods> That is what I think is happening here.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
