From owner-freebsd-xen@FreeBSD.ORG Mon Aug 22 10:13:10 2011 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 8F0A1106564A for ; Mon, 22 Aug 2011 10:13:10 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id 63AA68FC0C for ; Mon, 22 Aug 2011 10:13:10 +0000 (UTC) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id 674F38BD for ; Mon, 22 Aug 2011 10:13:09 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id z-DdCstaMEYN for ; Mon, 22 Aug 2011 10:12:32 +0000 (UTC) Received: from [192.168.1.1] (a89-152-172-232.cpe.netcabo.pt [89.152.172.232]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id C79A58B0 for ; Mon, 22 Aug 2011 10:12:31 +0000 (UTC) Message-ID: <4E522B8D.2050202@barafranca.com> Date: Mon, 22 Aug 2011 11:12:29 +0100 From: Hugo Silva User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: amd64 HVM(+PV) domUs: losing 10+ minutes a day 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, 22 Aug 2011 10:13:10 -0000 Hello, During my tests with 9.0, I have found another issue that I would like to bring your attention to. On all three 9.0-BETA1 virtual machines installed (on a NetBSD dom0, should it matter) I'm encountering the infamous 'runtime went backwards' messages (the VM's been up for days, it seems to do it only when there's heavy activity in the system (not necessarily on the same VM, it seems)- no such messages for 3 days now, even though the system is up and services are running; still, clock time is being lost every day). On that same machine, there are NetBSD (pv), OpenIndiana (pv) and OpenBSD (hvm) vms - none of which has issues keeping track of time (therefore I don't think it's a hvm problem (openbsd works) nor a hardware/dom0 problem (dom0 + !freebsd_domU works) I'm talking about 10-15 minutes a day lost, enough to confuse the applications running inside the FreeBSD systems. Eventually ntpd will refuse to adjust the time, saying: ntpd[20176]: frequency error 2273 PPM exceeds tolerance 500 PPM I haven't found how to counter this yet (other than stopping ntpd, running ntpdate, and restarting ntpd), but in any case that seems to me like sidestepping the real problem. Haven't tested with HVM FreeBSD, but if it helps troubleshooting I'll set something up.. Regards, Hugo