From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Alexander Vallens" <avallens@archenergy.com>
Subject: Re: domU clock over 23s off
Date: Mon, 13 Nov 2006 15:49:23 -0700
Message-ID: <4558F673.7030501@archenergy.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

I'm encountering similar issues on the current release of SuSE 10.1 on a
dual duo-core Opteron system. He this issue ever been fixed?

Thanks!
Alexander


On Feb 26, Keir Fraser wrote:

> >I have rather new installation of xen, dom0 is running ntpd and is
> >perfectly in time. All domU's are ~23s in future. Running ntpd on
> >the domU's seem to have no effect, /proc/sys/xen/independent_wallclock
> >appears to have no effect. I'm running xen-unstable and 2.6.16-rc4
> >in AMD64 box.
>
> Booting the domU's with 'independent_wallclock' as a command-line
> parameter, and then running a standard vendor ntp init script (usually
> ntpdate followed by starting ntpd) certainly *should* have fixed the
> domU time problem.

-- 
Alexander Vallens
System Administrator
Architectural Energy Corporation
http://www.archenergy.com
Voice:	303-459-7463
Fax:	303-444-4304