virtualbox.org

I have a guest running, then I hibernate the host. Now when I wake up my host, it uses 100 % CPU resp. 50 % on a DualCore CPU. However that program seems not stucked in a endless loop. I can normal work with the guest and when I power it down and close the VMM VBoxSVC.exe closes.
How can I avoid this CPU stealing? What exactly does VBoxSVC.exe?

Thanks for help.

Known problem, see bugtracker ticket:
http://www.virtualbox.org/ticket/2978

Thank you. I'm glad to know that this CPU usage will go down after some minutes, so I don't have to powerdown the guest.

However in that bugreport is written it already happens when only the VMM without a guest running is open. I can have the VMM open, hibernate as I like. The problem only occurs when a guest was running while hibernating.

A bug is a bug, but on the other hand I find it normal behaviour as hybernation is a very specific OS technique that is not suited for emulated cpu's that have no notion whats going on when waking up.

But as far as I noticed the CPU is emulated by "VirtualBox.exe" and not VBoxSVC.exe. When I produce CPU usage in the guest it's virtualbox.exe that creates CPU usage on the host.

No VBoxSVC is running the VM, virtualbox is the GUI which can be closed when not needed.

Then how comes, that virtualbox.exe produces the CPU usage when using the CPU inside the guest?

No idea, could be part of the bug, close vb.exe when this happens and see what happens to the cpu. I hardly use vb.exe(GUI) unless to change VM parameters.

You don't need the GUI to see the process. You have virtualbox.exe for the GUI/the VMM and then you have for each VM running additional virtualbox.exe processes.
When everything works normal VBoxSVC.exe only needs CPU when starting a VM. I just found out, that I can even kill VBoxSVC while running a VM and the VM still works fine.
But with killing the problem is not solved, because when killed, I get this error, while trying to start another VM:


To get around by that, I have to open a new VMM window. Than vboxsvc.exe runs again, I can start new VMs.

Yes your right, VBoxSVC runs the vb.exe per VM process and the GUI so the cpu use in vb.exe is directly related to the VM.

i've got the same problem?
it this solved?

Same problem on my systems with VirtualBox 2.2.2 and 2.2.4 on Windows XP Prof SP3.

Problem seems to be solved with 3.0.2