From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: XenParavirtOps wiki page updates Date: Fri, 19 Dec 2008 17:32:16 -0800 Message-ID: <494C4B20.3080708@goop.org> References: <1e16a9ed0812131133p522eed2fhb54e6e8c5192b360@mail.gmail.com> <87fxkpveit.fsf@tac.ki.iif.hu> <494C09C1.5070009@goop.org> <87k59vk940.fsf@szonett.ki.iif.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87k59vk940.fsf@szonett.ki.iif.hu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ferenc Wagner Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Ferenc Wagner wrote: > Hmm, my last data points are from the summer, but since people keep > constantly asking on the users' list how to do this, I assumed things > didn't change. Back then ntpd was unable to change the domU clock, it > was constantly drifting away from the current time. Ah. I've never tested it, but I've never got a bug report about it either. The Xen clocksource's rate should be tuneable down to ~1ppm, which should be fine for ntp. > Also, when the > procfs settings (like independent_wallclock) disappeared I got the > impression that the system times are now unconditionally synced. > No, the opposite - its never synced, except at domain boot. > Probably I'm just confused and all is well now... I'll set up and > test this again. Thanks for the hint! > Please keep me informed. RH has been shipping pvops kernels for a while now, and their stock install starts ntp. I would have assumed that I'd have heard about any time sync problems by now... J