Alexey, I know the system can do it. I see VBox running at 400% (thus fully consuming 4 cores) when the VM is booting, but when I run load on it subsequent to that, utilisation tops out at ~200%, even though the system believes it is scheduling load for 4 cores.
I appreciate the help, but mostly I was trying to do a sanity check before filing a bug report. It seems filing one might be a quicker way to get someone with access to an OS X system to try to reproduce the issue. Cheers, Bayard On 6 May 2011, at 10:55, Alexey Eromenko wrote: > Try to start 4 processes, like: > $ cat /dev/zero > /dev/null > (or Solaris equivalent command) > > ...and see if you can load all 4 cores. > (I know only Windows and Linux.) > -- > -Alexey Eromenko "Technologov" > > _______________________________________________ > vbox-dev mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-dev
smime.p7s
Description: S/MIME cryptographic signature
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ vbox-dev mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-dev
