Date: Sun, 19 Aug 2012 14:00:51 +0200 From: Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= <decke@bluelife.at> To: Stephen McKay <smckay@internode.on.net>, freebsd-emulation@freebsd.org Subject: Re: VirtualBox limitations with FreeBSD clients? Message-ID: <1345377651.18956.2.camel@Nokia-N900-42-11> In-Reply-To: <201208191133.q7JBXvpX005732@dungeon.home> References: <201208191133.q7JBXvpX005732@dungeon.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On So., 19. Aug. 2012 13:33:57 CEST, Stephen McKay <smckay@internode.on.net> wrote: > Hi! > > I'm trying to get the following setup stable: > > FreeBSD 9.1-beta1 host (Intel Q6600 cpu with 4 cores) > VirtualBox 4.1.18 > FreeBSD 10-current client (4 virtual cpus) > > No matter what I fiddle in kern.timecounter, I get many calcru errors > on the client, for example: > > calcru: runtime went backwards from 6968924848397985 usec to 38 used for > pid 16 (vnlru) > > In fact, that one is more preposterous than most. I think that many usec > is about 220 years. Something is completely out of whack here. > > So, my questions are: > - do multi-cpu FreeBSD clients work for you in VirtualBox? > - does FreeBSD-current as a client in VirtualBox work for you? > - what's the oldest hardware you've successfully used as a VirtualBox > host? > > If this has never worked I may as well give up. But if it works for > most people, maybe it can be traced, and I'll do a much better bug > report. ;-) What do you currently use to keep the time in sync? There are vbox guest additions that can keep the time in sync with the host clock or you could use an ntp client in the guest. Both did work fine for me in the past but results may vary. -- http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1345377651.18956.2.camel>