VirtualBox

Ticket #5131 (closed defect: fixed)

Opened 5 years ago

Last modified 3 years ago

100% CPU usage with x64 Win7 host, x32 WinXP guest and >1 CPUs

Reported by: ServerAlex Owned by:
Priority: critical Component: VMM
Version: VirtualBox 3.0.8 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description

I'm running Windows 7 x64 as host with VBox 3.0.8 PUEL. PC is a notebook with AMD Turion X2 TL-60 and 4GB RAM.

Guest is Windows XP 32-bit. When I enable 2 virtual CPUs, the VBox produces 100% CPU usage on the host, even if the guest is idle. The usage is kernel-mode, so even the mouse is lagging very heavily.

1 virtual CPU doesn't have that problem.

Attachments

Windows XP-2009-10-06-15-22-05.log Download (51.4 KB) - added by ServerAlex 5 years ago.
VBox.log

Change History

Changed 5 years ago by ServerAlex

VBox.log

comment:1 Changed 5 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to worksforme

Make sure you update your additions to 3.0.8.

comment:2 Changed 5 years ago by ServerAlex

  • Status changed from closed to reopened
  • Resolution worksforme deleted

Updated the additions to 3.0.8, but problem isn't solved.

comment:3 Changed 5 years ago by webJose

I am experiencing what it could be a related problem.

Host: Windows 7 64-bit. Guest: Windows Server 2008 R2 Enterprise, full installation.

VM: 2 CPU's, 1GB RAM, ICH6 + SATA.

VM and some 12 other programs running. Wife comes in and wants to harvest in Farmville! Had to budge. She logs in via Fast User Switching and plays for a bit over 2 hours. She logs off. I unlock my running session only to find out Virtualbox is driving my Q6600 mad (8 GB RAM) and the VM showing garbage on the virtual screen. I too saw a sluggish mouse. Took me several minutes to bring Task Manager to investigate.

This is an upgrade from VBox 3.0.6 (I think), and the VM was installed after I upgraded to 3.0.8.

I cannot comment for other versions as this is the first time I use more than one virtual CPU.

comment:4 Changed 4 years ago by frank

  • Component changed from other to VMM

comment:5 Changed 3 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

Please reopen if still relevant with VBox 4.1.4.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use