VirtualBox limitations with FreeBSD clients?
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. ;-) Cheers, Stephen. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox limitations with FreeBSD clients?
On So., 19. Aug. 2012 13:33:57 CEST, Stephen McKay 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/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: VirtualBox limitations with FreeBSD clients?
On Sunday, 19th August 2012, Bernhard =?ISO-8859-1?Q?Fr=F6hlich?= wrote: >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. I've tried with and without the virtualbox-ose-additions port but my problem is more fundamental than drifting time. Those "calcru" warnings should not occur, no matter whether you have the additions running or not. At a very low level, my 10-current client is getting such bad time information it cannot track time even approximately, and none of the settings I've tried make it stable. Do you have any well behaved FreeBSD virtual box clients? Are any of them running 10-current? My experience with virtual FreeBSD clients so far has been FreeBSD 8 on ESXi 4, and that has worked fine. Stephen. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
