Ticket #10733 (closed defect: obsolete)

Opened 8 years ago

Last modified 4 years ago

VBoxSVC uses > 100% of CPU, even if no VM is running

Reported by: ElectricSnark Owned by:
Component: other Version: VirtualBox 4.1.18
Keywords: VBoxSVC Cc:
Guest type: all Host type: Linux


This is on a linux host (debian, 3.0.0 kernel), running version 4.1.18 of virtualbox.

Starting the "Oracle VM VirtualBox Manager" creates the VBoxSVC process which consumes > 100% of CPU, as reported by ps, before any VM is started.

See the forum posting at for some ps stats.


VBox.log Download (91.3 KB) - added by ElectricSnark 8 years ago.

Change History

Changed 8 years ago by ElectricSnark


comment:1 Changed 8 years ago by rfm

I'm seeing the same ~120% VBoxSVC cpu consumption behavior with Ubuntu 12.04 host, but only when the guest (also Ubuntu 12.04) is booted but essentially idle. VBoxHeadless is clocking about 60% usage at the same time, so total consumption is about 200% (quad core host.) Nothing interesting in VBox.log, host logs, or guest logs. Virtualbox 4.1.18, never saw this before on earlier Virtualbox releases.

comment:2 Changed 8 years ago by TuXator

I had similar issues. The kernels leap second bug turned out to be the reason in my case. Resetting the clock, e.g. using date -s "$(LC_ALL=C date)" fixed the problem for me. (Rebooting is another option.)

comment:3 Changed 8 years ago by frank

Yes, the comment by rfm really looks like the leap second bug TuXator reported. But the original report looks different as no guest was apparently running. ElektricSnark, can you reproduce this behavior? If so, could you try the following:

  1. Start the VBoxSVC service as a separate process with strace:
    strace -s128 -o ~/VBoxSVC.log -f /usr/lib/virtualbox/VBoxSVC
    Wait a bit (~30 seconds or so) until the service started successfully
  2. Start the GUI

Now wait a bit more (with strace everything takes a bit more time) and check if the host CPU load increases. Then terminate the VM, compress the resulting ~/VBoxSVC.log and attach it to this ticket.

comment:4 Changed 8 years ago by rfm

Rebooting the host does seem to have cleared my problem, so it probably was the leap second bug for me.

comment:5 Changed 8 years ago by blast

I'm have seen it on a Windows 7 host with Windows XP guests. My vdis are on a portable external hard drive if that makes a difference.


VirtualBox (XP)COM Server 4.1.18 r78361 win.amd64 (Jun 5 2012 15:58:59) release log
OS Product: Windows 7
OS Release: 6.1.7601

It goes away if I restart the process and unfortunately it isn't always reproducible.

comment:6 Changed 4 years ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use