virtualbox 4.2.4 tooooo slow

[Bernhard Fröhlich]

On Thu, Nov 22, 2012 at 12:21 AM, 진석오 <jsukoh at gmail.com> wrote:
> Dear All,
> thank you for your quick reply..
>
> Rusty, this is my kldstat as followings
>
> [mohicann at theBSD /mnt]$ kldstat
> Id Refs Address            Size     Name
>  1   34 0xffffffff80200000 1323388  kernel
>  2    1 0xffffffff81524000 2084d8   zfs.ko
>  3    2 0xffffffff8172d000 5c58     opensolaris.ko
>  4    1 0xffffffff81734000 ee5990   nvidia.ko
>  5    2 0xffffffff8261a000 484c0    linux.ko
>  6    3 0xffffffff82663000 59ce8    vboxdrv.ko
>  7    2 0xffffffff82812000 2951     vboxnetflt.ko
>  8    2 0xffffffff82815000 87b2     netgraph.ko
>  9    1 0xffffffff8281e000 1579     ng_ether.ko
> 10    1 0xffffffff82820000 3fea     vboxnetadp.ko
> 11    1 0xffffffff82824000 9de      pflog.ko
> 12    1 0xffffffff82825000 2a4a1    pf.ko
> 13    1 0xffffffff82850000 a9bb     fuse.ko
> [mohicann at theBSD /mnt]$
>
> Bernhard,
>
> It's very difficult for me to say "that" is slow because every thing is
> slow,
> form booting to running a program. after boot, just to log on windows 8 then
> I need to wait  at least 30 seconds after I type my ID and passwords.
> when I run a program such as MS word, cursor blinking period is too long,
> when I try to type any words I need to wait serveral seconds then after, I
> should wait more to type more words. if I type serveral words at the same
> time I must wait  5~7 seconds to see the display of my typing. It's like a
> 386 SX computer ;-\
>
> I think a BIOS would not a problem because I run a OpenSuse linux at the
> same computer, Virtualbox on Opensuse is quite fast to use. I can use MS
> office or any other programs without any speed problem with the same specs.
>
> any thing on virtualized OS should be slower, but in my case it's too slow
> to use it. for example booting time is 3 more times longer than OpenSuse
> linux on my the same PC. loading a software consumes much longer time.
>
> I will attach the log file.
> any clues are welcome to solve my virtualbox....
>
> thank you.

Thanks a lot for your cooperation. I've already talked to the vbox developers
and they say that your symptoms are known to them but they could not
reproduce nor narrow down the problem yet. So what they need to be able
to narrow it down is a ps and top listing on thread level (!) and if possible
a stacktrace from the most time consuming vbox threads.

--
Bernhard Froehlich
http://www.bluelife.at/