VBoxSvc goes to 100% CPU for idle Linux Guest on Windows 7 64-bit Host

[Captain Crunch]

1. Install new VirtualBox guest, 32-bit OpenSUSE 12.2, using the official DVD (openSUSE-12.2-DVD-i586.iso, md5: 0373980cd6f270e1172067b86c044633).

2. Take the defaults, except configure for 2048mb memory, 2 processors, and 32mb video memory. (Bug also reproduces with a single processor.) This means, among other things, Chipset is PIIX3, Enable IO APIC is checked, and 2D/3D acceleration are not checked.

3. Run guest, let it boot up, and then let it sit idle. (I open the system monitor to make sure nothing is running.) After a number of hours idle (can very between < 1 to 24 hours), the VBoxSvc in the host will jump to 100% of a core (so 25% CPU for a 4 core system), and remains there indefinitely.

Host: Windows 7 64-bit Pro, 8gb memory

CPU: Core i5 M450 (mobile)

VirtualBox 4.2.4r81684, plus associated version of VM VirtualBox Extension Pack

Also observed with OpenSUSE 11.4

Also observed with older version of VirtualBox (4.1.20 I believe)

Searched for other similar bugs. Most were old and marked fixed. Most recent was "leap second" issue for which I applied solution of setting the date with no effect.

[Captain Crunch]

Why has this critical bug sat idle with not a single comment for 3 months? I provided clear instructions on how to repfoduce it and it happens 100% of the time I launch VB for linux. After killing VBoxSvc, I have problems shutting down the virtual machine and I'm assuming there are other side effects as well.

This should be a showstopper but apparent no one cares.

[vak]

any updates? (Host OS: Ubuntu 13.10, guest OS: Ubuntu 12.04.3)

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.