From owner-freebsd-ports@FreeBSD.ORG  Fri Dec 16 15:42:56 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 4DD38106566B
	for <freebsd-ports@freebsd.org>; Fri, 16 Dec 2011 15:42:56 +0000 (UTC)
	(envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
	by mx1.freebsd.org (Postfix) with ESMTP id 0FBFA8FC15
	for <freebsd-ports@freebsd.org>; Fri, 16 Dec 2011 15:42:56 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.72 (FreeBSD))
	(envelope-from <lists@opsec.eu>)
	id 1RbZvz-000Pi6-QB; Fri, 16 Dec 2011 16:42:55 +0100
Date: Fri, 16 Dec 2011 16:42:55 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Larry Rosenman <ler@lerctr.org>
Message-ID: <20111216154255.GA14039@home.opsec.eu>
References: <4EE9014F.7010300@lerctr.org>
 <4EEA5461.4080107@lerctr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4EEA5461.4080107@lerctr.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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 15:42:56 -0000

Hi!

> 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?

I have seen similar behaviour on other systems (Linux+Qemu)
and other versions of vbox+fbsd, so: I'm not surprised.

>From what I've heard, its a common virtualization issue.

> 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'd be willing to provide access to test hosts as well.

-- 
pi@opsec.eu            +49 171 3101372                         9 years to go !