Date: Sat, 21 Jan 2012 15:30:10 +0200 From: Alexander Motin <mav@FreeBSD.org> To: Martin Sugioarto <martin@sugioarto.com> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Timekeeping in stable/9 Message-ID: <4F1ABDE2.5070904@FreeBSD.org> In-Reply-To: <20120121142040.1805e2ed@zelda.sugioarto.com> References: <20120118075049.289954e8@zelda.sugioarto.com> <mailpost.1327137575.1997238.49263.mailing.freebsd.stable@FreeBSD.cs.nctu.edu.tw> <4F1AAFFD.7070303@FreeBSD.org> <20120121142040.1805e2ed@zelda.sugioarto.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/21/12 15:20, Martin Sugioarto wrote: > Am Sat, 21 Jan 2012 14:30:53 +0200 > schrieb Alexander Motin<mav@FreeBSD.org>: >> I am not using VirtualBox right now, so I'll need to setup it to test >> this. Meanwhile you could try to experiment with switching to >> different timecounters and eventtimers. May be some change in 9.0 >> changed default timecounter for you, causing the problem. > > I think we have a misunderstanding here. The host (FreeBSD 9.0R) works > fine. The time is being updated under heavy load without problems. > > I already said that this seems to be an application problem and this > email(s) should be rather seen by the VBox maintainer. The problem is > that VBox seems to stop working properly when you put heavy CPU load on > the host. It even does not keep the clock up-to-date. > > I can desync the guest clock to -1 minute in a few seconds, just by > running "openssl speed -multi 20". Ah. I'm sorry. I was sure we are debugging FreeBSD inside VirtualBox. If we are speaking about FreeBSD outside, then neither timecounter nor eventtimer choice should not affect guest if host is working fine. It is more question to VirtualBox and may be host system scheduler. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F1ABDE2.5070904>