winXP guest using 100% of one of CPU's

vbox.log

Having the same problem here, using Ubuntu Feisty as host. This problem came imminent after upgrading from 1.3.8 to 1.4.0. So before, using 1.3.8, this combination (Feisty host, XP guest) was working perfectly.

After rereading the problem text, I guess my problem is different: in my case, the host goes to 100% as the guest stays normal. Please ignore my comment.

Added note: allocated base memory for VM is 512MB. Host monitor reports memory used by VirtualBox process is over 580MiB. CPU load is reasonable until a user is logged on in guest Windows XP. Logging user out does not drop CPU load, only closing VM drops load. Host monitor reports process using all the cycles is VirtualBox (one of two instances running).

Problem resolved - sort of.

Using taskmanager to kill the incidence of svchost.exe which is using all the CPU cycles allows the frozen install process to continue. Had to do this each time to complete installation of guestadditions.iso, USB controller, and scanner software. CPU usage is now below 5% at idle.

Could someone explain to me what this is doing?

This looks like a duplicate of bug #824.

-Technologov

I've been suffering this virtualbox issue for long.

Always in ubuntu hosts (7.10 32bits, and now 8.04 64bits), in different host machines (laptops and desktops), with clean-install WinXP SP2, now all patched to SP3.

All virtuabox releases up to today's 1.5.6. A royal pain.

Right after the guest boots, the CPU ussage of both host and guest shots up and stays in 100%. WinXP task manager shows that the svchost process is eating all available cpu. After I kill it, all returns to normal. Sometimes after a while svchost shots up again.

Any hint on how to solve this would be greatly appreciated.

Typo: I meant: "Today's VB 1.6". Same problem shows up in virtual box 1.6 64bits. All the way up from 1.4 or so, 32bits.

ariel, please could you attach a VBox.log file you your WinXP session? And you observed this problem for all releases of VirtualBox you tested? Or was there an early 1.3.x release which did not show this behavior?

Attached vbox.log

The problem in 1.4 and beyond. I seem to remember that Ii didn't have this problem in 1.3.

Today as usual I had to manually kill svchost because it was eating the cpu. Uncommonly, I needed to use audio output from the virtual machine and found that it was not working. I realized that audio is lost for the virtual machine when I kill the ill-behaved svchost.

Then I opened up vbox.log and found a bunch of messages regarding audio. Not sure if they show the problem or not, but still.

Now I am using pulseaudio output with vbox 1.6. But before (with 1.4.x and 1.5.x) I used alsa, and had exactly the same problem.

The host is Winxp (orignally SP2, now SP3, no improvements in this issue after installing sp3).

If I am very patient (20 minutes or so) svchost seems to eventually calm down and go back to normal (close 0 cpu %).

Hopefully this can be reproduced by others and can be fixed.

Type: The GUEST is winxp (originally sp2, now sp3). The HOST is ubuntu 8.04/64bits. Previous hosts (7.04, 7.10, 32bits) had the same problem.

Unfortunately, vbox 1.6.2 didn't improve things at all in this end.

ariel, could you try if disabling the USB controller for the guest improves the CPU load? And as second step, try to disable VT-x as well. Does this make any difference?

I am experiencing 100% usage of one core as well. Here is my setup:

Version: 1.6.2
Host: Ubuntu Hardy 64-bit running on Intel Core 2 Duo
Guest: Windows XP SP2 + Guest Extensions

Not using VT-x/AMD-V. Only hard disk (rawdisk to one of my partitions) and network adapter enabled. I would like to eventually use USB host devices but have not yet enabled the feature.

Strange and interesting observation: In the session information dialog->runtime it says Guest Additions: Version 1.4 but below that it says Guest OS Type: Not Detected

Ultimately windows reports idle CPU usage of 4-8% and VirtualBox task on host is 100%-102% at all times. I wouldn't complain except that it makes for a very hot laptop that discharges the battery very quickly.

I'm happy to run tests or provide additional information.

Hi guys, I am experiencing 100% usage of one core as well. Here is my setup:

Version: 1.6.2 Host: Ubuntu Hardy 64-bit running on Intel Core 2 Duo Guest: Windows XP SP3 + Guest Extensions

VT-x/AMD-V:Disabled, Guest Additions: Version 1.4

As Steve, I'm getting "Guest OS Type:" Not Detected.

I do a lot of flash, and probably this might be related to #1350

I will be happy to provide testing as well.

I experience this at all times regardless of whether a browser is open. It is rare that I open a browser in this guest.

This seems to be a serious and fairly common problem.

VirtualBox 1.6.2 (Sun xVM VirtualBox) Host: Ubuntu Hardy 8.04 (2.6.24-19 amd64) Intel Dual Core

Guest: Windows XP SP2

After starting the Guest OS in the VM the CPU immediately goes to >100% and remains the entire time. Some brief periods (at startup mostly) of completely disk utilization as well.

Replying to ciriarte:

Hi guys, I am experiencing 100% usage of one core as well. Here is my setup: Version: 1.6.2 Host: Ubuntu Hardy 64-bit running on Intel Core 2 Duo Guest: Windows XP SP3 + Guest Extensions VT-x/AMD-V:Disabled, Guest Additions: Version 1.4 As Steve, I'm getting "Guest OS Type:" Not Detected. I do a lot of flash, and probably this might be related to #1350 I will be happy to provide testing as well.

I've been testing 1.6.4 for a while now. The problem is still there 100% CPU, the only improvement (related to this issue) I've seen is that now it does detect the guest OS type. I'll keep posting my findings.

Does the host utilization change when you change two VMs in parallel (both idle)?