From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Schroeder Subject: Re: [XEN-3.4] pv_ops dom0 time/clock handling Date: Mon, 25 May 2009 11:56:46 +0200 Message-ID: <4A1A6B5E.3010602@dschroeder.info> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > 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. > checked with OpenSUSE 2.6.29.X xenified dom0...pv domU has the right time...booted pvops .30-rc6, pv domU gets probably localtime as basetime, so domU is two hours in the future... daniel