VirtualBox

Opened 16 years ago

Closed 15 years ago

Last modified 14 years ago

#1946 closed defect (duplicate)

Ubuntu 8.04 host, Windows XP guest, AMD x86_64 SMP host, CPU = 100%

Reported by: Doug Roberts Owned by:
Component: other Version: VirtualBox 1.6.4
Keywords: Cc:
Guest type: Windows Host type: Linux

Description

CPU utilization is 100 percent in this configuration. Have found no tweaking combination of USB 2.0 / clipboard settings that present a work-around.

Ubuntu 8.04 host, Windows XP SP2 guest.

Attachments (1)

VBox.log (42.2 KB ) - added by gbell12 15 years ago.

Download all attachments as: .zip

Change History (20)

comment:1 by Doug Roberts, 16 years ago

Sorry, make that an "AMD" processor, not an "AMC".

--Doug

comment:2 by Sander van Leeuwen, 16 years ago

Component: host supportother
Summary: Ubuntu 8.04 host, Windows XP guest, AMC x86_64 SMP host, CPU = 100%Ubuntu 8.04 host, Windows XP guest, AMD x86_64 SMP host, CPU = 100%

Attach the sessions's VBox.log please.

comment:3 by Frank Mehnert, 15 years ago

Resolution: fixed
Status: newclosed

No response, closing. The problem might have been fixed anyway, try out the latest release 2.2.0.

by gbell12, 15 years ago

Attachment: VBox.log added

comment:4 by gbell12, 15 years ago

Resolution: fixed
Status: closedreopened

I'd like to reopen this ticket. Its a dupe of http://www.virtualbox.org/ticket/1233

I've attached my Vbox.log file. The only thing different from the original poster is that I'm on FC10.

As you can see from the attached log, I'm running 2.2.0, with XP as a guest. One CPU is pegged at 100% no matter what the guest is doing. For this testcase, I didn't even login, just booted XP, left it sitting there at the login screen for 20 minutes, then shutdown.

I was running with taskset -c 1. I've disabled the clipboard, increased video memory size to > 32MB, turned off USB, etc. etc. and it always runs at 100% CPU.

Archlinux as guest does not.

comment:5 by Sander van Leeuwen, 15 years ago

Don't use the IO-APIC for 32 bits Windows guests. That will kill performance. Turning it off will make Windows blue screen, so you either have to reinstall Windows or change the HAL. (see http://www.virtualbox.org/wiki/Migrate_Windows)

comment:6 by Sander van Leeuwen, 15 years ago

Resolution: duplicate
Status: reopenedclosed

Duplicate of #638.

comment:7 by gbell12, 15 years ago

Not a good solution as IO-APIC seems to be required for Windows XP install disk to boot. Also detailed in this bug, that appears to be yet another duplicate (638, 1233, 1407, 1946)

http://www.virtualbox.org/ticket/638

Changing the HAL as suggested doesn't seem to be an option without a Recovery floppy created.

comment:8 by Sander van Leeuwen, 15 years ago

Well, there is currently unfortunately no other option. IO-APIC is only required if you installed Windows with it enabled. Which probably implies that you migrated a VMWare image as we don't enable it by default for 32 bits guests.

comment:9 by gbell12, 15 years ago

Not a VMWare image, but it is an nLite generated image from a running system...

comment:10 by Sander van Leeuwen, 15 years ago

Same applies for images from physical systems. See defect #638 for a video link.

comment:12 by gbell12, 15 years ago

Everybody googling this issue:

Its extremely easy to fix. From the video,

Start->Control Panel->System->Hardware->Device Manager

Expand "Computer" Right-Click on "ACPI Multiprocessor PC" or "Advanced Configuration and Power Interface (ACPI)"

Select "Update Driver"

Select "No, not this time" and Next

Select "Install from a list or specific location" and Next

Select "Don't Search, I will cho-cho-choose the driver to install" and Next

Select "Standard PC" and next

Follow instructions to reboot, etc.

That's *it*. 5 minutes of interruption and your fans will be quiet again, and your power consumption will drop, providing the world with fewer black baloons for your outputted wonders from your VirutalBox? PC.

in reply to:  12 ; comment:13 by gbell12, 15 years ago

Everybody googling this issue:

Its extremely easy to fix. From the video,

Start->Control Panel->System->Hardware->Device Manager

Expand "Computer" Right-Click on "ACPI Multiprocessor PC" or "Advanced Configuration and Power Interface (ACPI)"

Select "Update Driver"

Select "No, not this time" and Next

Select "Install from a list or specific location" and Next

Select "Don't Search, I will cho-cho-choose the driver to install" and Next

Select "Standard PC" and next

Follow instructions to reboot, etc.

That's *it*. 5 minutes of interruption and your fans will be quiet again, and your power consumption will drop, providing the world with fewer black baloons for your outputted wonders from your VirtualBox PC.

in reply to:  13 comment:14 by vondralbra, 15 years ago

Replying to gbell12:

Everybody googling this issue:

Its extremely easy to fix. From the video,

I can confirm this workaround on an Ubuntu 9.0.4 Host and a Debian Lenny Host both having Windows XP Guests which showed up with high cpu loads on the host while the guests were idling along.

The Virtualbox version used here is vbox 3.0.2

in reply to:  12 comment:15 by nemo34, 15 years ago

Resolution: duplicate
Status: closedreopened

Replying to gbell12:

Everybody googling this issue:

Its extremely easy to fix. From the video,

Start->Control Panel->System->Hardware->Device Manager

Expand "Computer" Right-Click on "ACPI Multiprocessor PC" or "Advanced Configuration and Power Interface (ACPI)"

Select "Update Driver"

Select "No, not this time" and Next

Select "Install from a list or specific location" and Next

Select "Don't Search, I will cho-cho-choose the driver to install" and Next

Select "Standard PC" and next

Follow instructions to reboot, etc.

That's *it*. 5 minutes of interruption and your fans will be quiet again, and your power consumption will drop, providing the world with fewer black baloons for your outputted wonders from your VirutalBox? PC.

Warning, this fix did nto work for me. System would not restart. Had to switch to safe-mode windows to select back "multiple microprocessor with ACPI". So proceed with caution if trying this.

BTW, I still have 100% CPU load with XP-SP3 running on VB3.0.2 on Ubuntu 9.04 and no idea on how to fix that. Processes sucking CPU are services.exe, vm_sti.exe, explorer.exe, antivirus (rtvscan.exe) and wmiadap.exe

Any idea?

comment:16 by Sander van Leeuwen, 15 years ago

Resolution: fixed
Status: reopenedclosed

Nemo34: do not reopen tickets without providing any information (VBox.log). The original problem has been solved.

comment:17 by simoncpu, 15 years ago

Hi,

I am still experiencing this problem with version 2.2.4 r47978. My uname -a for my host is:

Linux soulfury 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 01:19:55 UTC 2009 x86_64 GNU/Linux

My guest is FreeBSD 7.1.

Sorry, I have no logs atm.

[ simon.cpu ]

comment:18 by Michael Thayer, 15 years ago

simoncpu: you might want to check whether the problem persists with version 3.0.4. If so, you could also try the test builds linked to on http://www.virtualbox.org/ticket/3755#comment:29 (see the information and the warnings there as well of course).

comment:19 by Michael Thayer, 15 years ago

Resolution: fixed
Status: closedreopened

[Pasted from ticket 894]

Good day!

I'm currently using version 2.2.4 r47978. The uname for my host is:

Linux soulfury 2.6.28-14-generic #47-Ubuntu SMP Sat Jul 25 01:19:55 UTC 2009 x86_64 GNU/Linux

The uname for my guest is:

FreeBSD inara.simoncpu.com 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #0: Thu May 7 12:19:03 PHT 2009 admin@inara:/usr/obj/usr/src/sys/SOLIDWALL i386

top gives the following output even though both host and guest OSes are idle:

7053 simoncpu 20 0 575m 261m 27m R 32.2 13.1 6024:17 VirtualBox

VirtualBox is consuming ~30-35% CPU. I'm reopening this because this problem still exist.

Thanks!

[ simon.cpu ]

comment:20 by Sander van Leeuwen, 15 years ago

Resolution: duplicate
Status: reopenedclosed

Just another case of IO-APIC overhead. Do not reopen duplicates.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use