On 05/20/2010 06:59 AM, [email protected] wrote: >> >> On 05/19/2010 11:29 AM, Mario Lobo wrote: >> >>> On Tuesday 18 May 2010 23:24:06 Mario Lobo wrote: >>> >>> >>>> Hi; >>>> >>>> First let me thank all the developers for their efforts with VBox. >>>> >>>> I've installed the recently announced 3.2.0 stable release but I see >>>> that, >>>> after installing its companion guest additions on a Win XP SP3 guest, >>>> VBoxService.exe hits 99% of CPU usage all the time!. I doesn't even go >>>> down >>>> to 97 or 98. It stays fixed at 99% on the performance monitor. After >>>> about >>>> 15 minutes of the VM on (without doing anything on it), VBox aborts >>>> the >>>> machine. >>>> >>>> The host also suffers with this. With the earlier GA (BETA1) and an >>>> idle >>>> VM, Host CPU hovers around 8% (11% peaks). With the new GA and idle >>>> VM, it >>>> sticks to 37% (40% peaks) CPU usage. >>>> >>>> The same thing happened with VBoxGuestAdditions_3.2.0_BETA2/3 but NOT >>>> with >>>> VBoxGuestAdditions_3.2.0_BETA1 or any earlier GA!, with BETA1, VBox >>>> works >>>> perfectly, so I reverted back to it until this issue is cleared. >>>> >>>> System: FBSD 8-STABLE (updated weekly) amd64 >>>> >>>> Any suggestions? >>>> >>>> Thanks, >>>> >>>> >>>> >>> Did anyone else on the list experience that? >>> >>> >>> >> I just ran winxp 32 bit guest on FC12 host >> using VB-3.2 release. >> CPU load of both VB threads did not exceed 25% >> (i.e. 50% total) >> On my uniproc Athlon64 3200+, this is the norm, >> for VB, and nothing new. >> >> >> > Well, I must say that either the VB load on FreeBSD hosts is A LOT lighter > (xp vm running and total host load=10%) or you do have a problem if you're > hitting 50% load with only 1 VM running, although I have something going > for me, which is a Phenom II 955 quad. > > But what I was referring to on my post was the load of VBoxService.exe > INSIDE the xp guest. > > Mario >
Well, I think things on FC12 are different perhaps. I dont know. I am NOT running two VM's What I meant by BOTH threads is that there is the VBox GUI thread which seems to be different from the emulation thread. I am running only ONE VM. Buth the two threads together consume 50% of CPU. The way the Fedora scheduler appears to work, is that if you have other threads that are also cpu hogs (as in my case, Firefox playing some Youtube vids, I was seeing VB1 25% VB2 25% FFox 35% Now after I killed Firefox, I checked again and lo and behold, the CPU load of the two VBox threads jumped to a total of 90-96% which DOES make sense if you realize that when no other thread wants to run, then the threads that DO want to run (i.e. they are on the runq), then they will be on the CPU. This remained the case even after I reniced the the two VBox threads to have lower priority than the rest of the threads running in the system (All had priority 20 and nice 0). So I reniced the VB threads to +2, and that lowered their priority to 22, but they still consumed 90-95% of CPU, which means that most of the time no other thread wanted to run (i.e no other thread was on the runq). Hope this helps a little. Cheers, JD ------------------------------------------------------------------------------ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
