On Tue, May 28, 2013 at 12:09:14PM -0700, John Stultz wrote:On 05/28/2013 11:31 AM, Konrad Rzeszutek Wilk wrote:The #1 patch - b/c you try to set the RTC time and it actually never takes. MeaningOn Tue, May 28, 2013 at 07:26:14PM +0100, David Vrabel wrote:I'm really not sure I'd call this a bug. That seems like anOn 15/05/13 19:10, John Stultz wrote:Looks good.Ok, so really, as soon as the Dom0 time is set by NTP, all guests willIt's a small window but it's occurring in our automated test system.
see the right time? That makes more sense, and means the window for
these sorts of issues is reasonably quite small.
David: So I'm less inclined to merge this individual change, but if youThis patch was the actual bug fix but I've reworked it to use the
still feel strongly about it, let me know and we can circle around on it
after you've addressed the specific issues I pointed out earlier.
pvclock_gtod notifier chain as this seemed to be what KVM hosts were
using to maintain a clock for guests. Please review the new series, thanks.
John if you are OK I am thinking to push this to Linus shortly as it is
fixing a bug.
over-reaction to a misconfigured system.
Or if there is a bug, I'm not sure its been clearly explained.
on the next time the machine is booted the time is again off.