From mboxrd@z Thu Jan  1 00:00:00 1970
From: Saku Ytti <saku+xen-devel@ytti.fi>
Subject: domU clock over 23s off
Date: Sun, 26 Feb 2006 12:07:30 +0200
Message-ID: <20060226100730.GA24607@mx.ytti.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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

Hey,

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.

Any tip would be appricated.

Thanks,
-- 
  ++ytti