From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [XEN-3.4] pv_ops dom0 time/clock handling Date: Mon, 25 May 2009 10:16:57 +0100 Message-ID: References: <4A1A60C6.7050100@dschroeder.info> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4A1A60C6.7050100@dschroeder.info> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Daniel Schroeder , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 25/05/2009 10:11, "Daniel Schroeder" wrote: >> I have added "localtime = 0" and it seems to be fine...so, probably solved.. >> > this works for OpenSUSE 2.6.29.X XEN dom0 Kernel... > ...i have tested latest git-next repo .30-rc6 and the pv domU is two > hours ahead. > I have checked the following: > > dom0 ntpd working, correct time and /etc/localtime is correct > (Europe/Berlin) > > domU no ntpd and correct timezone and /etc/localtime (Europe/Berlin) > "localtime = 0" in pv domU config file... > > it seems to me, that the domU gets not UTC as basetime... This could plausibly be a pv_ops bug. I fthe only thing you change is the kernel -- keeping all configuration the same -- then dom0 will be providing exactly the same time info to both kernels. -- Keir