From owner-freebsd-xen@FreeBSD.ORG Mon Feb 2 17:16:35 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B49951065670 for ; Mon, 2 Feb 2009 17:16:35 +0000 (UTC) (envelope-from gofx-freebsd-xen@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 6DBB68FC0A for ; Mon, 2 Feb 2009 17:16:35 +0000 (UTC) (envelope-from gofx-freebsd-xen@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LU2PN-0007ST-UW for freebsd-xen@freebsd.org; Mon, 02 Feb 2009 17:16:29 +0000 Received: from 77.64.176.217 ([77.64.176.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 02 Feb 2009 17:16:29 +0000 Received: from js by 77.64.176.217 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 02 Feb 2009 17:16:29 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-xen@freebsd.org From: Julian Stecklina Date: Mon, 02 Feb 2009 18:16:20 +0100 Lines: 41 Message-ID: <87ljsokbdn.fsf@tabernacle.localnet> References: <877i4d1p46.fsf@tabernacle.localnet> <1233285639.24925.12.camel@phoenix.blechhirn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 77.64.176.217 X-Archive: encrypt User-Agent: Gnus/5.1008 (Gnus v5.10.8) Cancel-Lock: sha1:IVDSAokuBrpl+dSQBWELC7iOZYw= Sender: news Subject: Re: Time goes backwards X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2009 17:16:36 -0000 Mister Olli writes: > Hi, > > I've had time problems too. The clock did not go backwards, but forwards > for some time sime, and then jumped back to a certain date. Like > Sun Jan 25 00:55:12 UTC 2009 > ... > Sun Jan 25 01:08:35 UTC 2009 > Sun Jan 25 00:55:12 UTC 2009 > Sun Jan 25 00:55:13 UTC 2009 > ... > > It took me quite some time to find a solution that helped for me: > - activate the independent_wallclock in domO by 'sysctl xen.independent_wallclock=1' I booted the DomU with machdep.independent_wallclock=1 as kernel parameter instead. But that didn't work. sysctl still reported it as 0. I've tried setting machdep.xen_disable_rtc_set and machdep.independent_wallclock after booting, but it does not help either. > - edit and configure '/etc/ntpd.conf' in domU > - edit '/etc/rc.conf' and add the following lines > # NTP stuff > ntpdate_enable="YES" > ntpdate_flags="-b " > ntpd_enable="YES" > - reboot domU > > If you try it on your problem, could you please give me some feedback if > it worked? Doesn't work. :-/ MfG, -- Julian Stecklina Well, take it from an old hand: the only reason it would be easier to program in C is that you can't easily express complex problems in C, so you don't. - Erik Naggum (in comp.lang.lisp)