From owner-freebsd-ports@FreeBSD.ORG Tue Dec 20 01:41:49 2011 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71A6D106566C for ; Tue, 20 Dec 2011 01:41:49 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f07:14d3:2::11]) by mx1.freebsd.org (Postfix) with ESMTP id 27C778FC14 for ; Tue, 20 Dec 2011 01:41:49 +0000 (UTC) Received: from thor.farley.org (HPooka@thor.farley.org [IPv6:2001:470:1f07:14d3:1::5]) by mail.farley.org (8.14.5/8.14.5) with ESMTP id pBK1flJ4019970; Mon, 19 Dec 2011 20:41:47 -0500 (EST) (envelope-from scf@FreeBSD.org) Date: Mon, 19 Dec 2011 20:41:47 -0500 (EST) From: "Sean C. Farley" To: Larry Rosenman In-Reply-To: <4EEA5461.4080107@lerctr.org> Message-ID: References: <4EE9014F.7010300@lerctr.org> <4EEA5461.4080107@lerctr.org> User-Agent: Alpine 2.02 (BSF 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-1.5 required=4.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.farley.org Cc: freebsd-ports@FreeBSD.org Subject: Re: Fwd: Lousy timekeeping in VirtualBox 4.0.14 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2011 01:41:49 -0000 On Thu, 15 Dec 2011, Larry Rosenman wrote: > I've set up VirtualBox 4.0.14 on my FreeBSD 10.0-CURRENT (r228498) > box, and have a FreeBSD 10.0-CURRENT VM running underneath it. > > While the VM is running, it doesn't keep time worth a flip. > > This is even with the VirtualBox-Additions in it. > > 1) is this expected/known? > 2) What can we do to fix it? > > What diagnostics do you need? > > I *CAN* provide ssh access to both the host and the guest. I recall two things that caused problems for me in the past. One was running a VM in a Linux host that caused havoc on the time under load. My only "solution" was to disable PowerNow! in the BIOS. The second was on a WinXP host which was fixed, if I recall correctly, by changing the timecounter (kern.timecounter.hardware). I think I set it to HPET or ACPI-*. I hope one of those helps. Sean -- scf@FreeBSD.org