On 01/21/12 15:20, Martin Sugioarto wrote:
Am Sat, 21 Jan 2012 14:30:53 +0200
schrieb Alexander Motin<m...@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
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
