Hi, On Fri, 25 May 2012, Niclas Zeising wrote:
NZ>Sometime quite recent a change to FreeBSD CURRENT makes it almost impossible NZ>to run it as a virtualbox guest, at least under Windows. If I roll back the NZ>vbox machine to a (unfortunately quite old, from January) CURRENT everything NZ>seems to be working. NZ>The issue is that the virtual machine runs very very slow, and makes the host NZ>almost impossible to work with, especially during compiles and other NZ>activities involving the CPU and the disk. I have also experienced that the NZ>host machine crashes, but that might be unrelated. NZ>Is anyone else experiencing this, or am I doing something very wrong? I'm running current compiled with CLANG on the latest stable virtualbox under Win7. It works good, the only issue I had a couple of days ago when compiling world with -j4 (I've a 2-core with HTT) was that the CPUs were not raising their speed. They were just running on 780MHz and the compilation took half a day. A reboot of windows 'fixed' this. Normally if I do such a compile then both CPUs go up stable to 3.3GHz. I suspect that this is a bug in the BIOS or Windows where the frequency control gets stuck. NZ>Let me know if I need to provide more information or if I can help in some NZ>other way. Maybe first try to check with hwinfo what your CPUs are doing. harti _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"