VBoxSVC.exe 100% CPU after WinXP SP3 Hibernate -> fixed in SVN/3.0.2

The title says almost all, VBoxSVC.exe takes all CPU for several minutes (~5-10mins) (on a P4 2.8GHz, 2GB RAM) so that Windows is almost completely frozen.. after a while the CPU hog stops and Windows is responding normally. No guest VMs loaded when hibernated! Only the VirtualBox main application window was open.

I'm not using a Win page file.. just mentioning if that counts, I've no problems with this other than that some games doesn't work perfectly.. but I suspect that it's not the problem here.

Sorry if this a duplicate ticket, tried to search and found only something vaguely similar related to this.

I'm sorry but how's that going to help? I mean, isn't VBox.log files only generated when running guest OS's? Look at my steps to reproduce this problem, there's no step to run guest OS's = no VBox.log files! Or am I missing something here?

I think I got new data to this problem; it seems that the hang and the length of it is connected to the standby/hibernate length.

At first I tried the standby really quickly, standby and resume after about 10 seconds, no hang at all. I decided to test again, I put my PC to standby and went to make some food and watched a movie + tv for about 2½-3 hours, resume brought the desktop to the screen very slowly and the VBoxSVC.exe was again hogging the CPU.. this lasted about 2-3 minutes.

Last time I tried the hibernate, the system was in that state for about 3-4 hours and the hang lasted about 4 minutes after resume.

And my hibernate test before that lasted overnight and the hang lasted about 9 minutes after resume.

(yes, I do keep rough notes when I test bugs/problems.. I'm not a newbie with testing)

I think that this is an important observation and could lead to the culprit more easily.

Just installed 2.2.2r46594, Same issue after I hibernate my laptop (DELL Inspiron 1545,Vista Home Premium SP1; Intel Dual-Core T4200)for a night and
the VBoxSVC.exe forces the *second* CPU core running at almost 100% usage for several minutes. No VM or VBox GUI is running at all.

Same problem here with VB 2.2.4r47978 on Windows Vista Business 64-bit w/ SP2 running Windows Vista Business 32-bit VM. I usually don't hibernate the machine, only do standby, and as soon as it comes out of standby, it ties up the CPU 100% for several minutes. I have a Core 2 Duo 2.53 GHz processor w/ 4 GB RAM.

I'm afraid I've said that too soon - the problem is still here :-(
Sorry for my mistake.

I guess the laptop didn't sleep long enough last time (just about 15-20 minutes or so)
and that's why I didn't notice a high cpu usage.
This time, after waking up after
about 10 hours, it's been thinking hard for sth like 10 minutes!?
It's the VBoxSvc.exe process showing 50% CPU usage on a Core2 Duo CPU.

Yep, problem still remains here too with 3.0.0. VBoxSVC.exe still churns away and hogs CPU completely. Just hibernated for about 3 hours and the "freeze" took about 3 minutes. Is there any progress on nailing this issue? Have any of the testers/coders been able to reproduce this?

Unfortunately we are unable to reproduce the problem. I even have the exact same machine (Thinkpad T60p) as one of the reporters with XP and don't see it. Are all of you able to reproduce this even when no VM is running? (just the VirtualBox GUI)

I'm running Ubuntu Server 9.04 as a guest. I pause the guest and hibernate, but when I resume one of my CPU cores maxes out for an extended period (I've not yet waited to see how long for, but it's in excess of 10 mins). The offending process is VBoxSVC.exe.

Shutting down the guest does not stop this, however closing the VirtualBox GUI does.

Volunteers that wish to try out test builds should say so here. I'll wait a few days and will then send out links to test binaries next week. We are still unable to reproduce this problem, so the only solution is to try out a few things. Thanks in advance.

@sandervl73: I am able to reproduce this with just the GUI (even when no VM is running) on a Vaio 1GB Pentium M 1.2 GHz with Win XP SP3 host.
I am still using Vbox 2.2.0, because setup ends prematurely for 2.2.4 and 3.0.0 (but I don't need any update before #2978 is fixed ;-) ).

This is still a problem in VirtualBox 3.0.0 r49315.
I am running a Vista 64-bit host.
I notice the problem when I have a VM running or paused and I put the host to sleep. I haven't tried other scenarios.
After I kill VBoxSvc and unpause the VM and try to enter seamless mode, it errors saying that there isn't enough video memory allocated and I should allocate more than 1mb of video memory... when it has already been allocated 64mb.

I've only noticed this issue today for the first time. I've been using different versions from 1.6.x up to 3.0.0 (current). Could it have anything to do with hardware virtualization? Until yesterday, my system bBIOS was locked not to use it, and I've just unlocked it.

After sleeping tonight (not hibernating), I woke up my PC this morning to see that VBoxSvc.exe was hogging one of the two cores of my Core2Duo CPU. The VirtualBox.exe process that ran the machine (Ubuntu Server Jaunty) was very low on CPU, as usual, and both inside the machine and the VirtualBox GUI there were no signs of slowness whatsoever. I noticed however that the Session Information Dialogue, which I still had open, did not respond and I had to close it (which went smooth).

I haven't tested any further for now, but these observations were new to me.