updated to 2.2.2 from 2.1.4 100% CPU

[firebelly]

I think since the 2.1.* versions, I've been having CPU issues or networking issues.
cpu: coreduo on a laptop 1.9ghz
memory: 4gigs
VBox: latest as of today (64bit)
My Guest: Vista Ultimate (32bit)
My Host: Vista Ultimate (64bit)

I updated to 2.2.2 from 2.1.4. I had waited a while because networking was broken, but i heard this version fixed it (and it did) when i updated, CPU was through the roof on my host machine and the guest machine ran about as fast as my 486 did 1000 years ago. When ever i run a guest now, VB takes up all resources. I am going to reinstall 2.1.4 again and see if it works. Is anyone else having issues with VBox and Vista? Is there any help I can give that will assist debugging?

MOD Edit: I changed your subject to something that people could read and know what you wanted. Please read the forum guidelines http://forums.virtualbox.org/viewtopic.php?t=8208

[Perryg]

Put this in Google
Vista using 100% CPU in virtualbox site:forums.virtualbox.org
There are some helpful hints there.

[firebelly]

I've googled this over and over.
solutions from google?
1) Set Affinity to 1 CPU (did not work for me)
2) Resintall (did not work for me)
3) Change Guest to no SMP (Did not work, since this problem happens before OS even starts)
4) Install another guest (lul wut?, this didn't work either)
5) Disable USB (didn't work for me since it was never enabled)
6) http://support.microsoft.com/kb/949700 Memory leak in Windows (Wouldn't let me install, i'm assuming because it's part of SP1, but i will keep trying to install)

This 100% cpu occurs from the second the OS kicks on. Even before the OS boots, when it's thinking about safemode or not. If i pick safemode, it loads all the drivers, you can see if on the screen "Loading driver blah blah.dll". It goes SO SLOW, I can see the scree redraw the text.

This image worked great in older versions of VBox. Nothing has changed on the guest.

[vbox4me2]

2 things you can try, make a new VM and attach VDI, or fiddle with current VM settings, things change between versions where some VM setting does effect things.

[firebelly]

This was also failing on 2.2.0 and i did the steps in this thread
http://forums.virtualbox.org/viewtopic.php?f=6&t=17318
and reinstalled to 2.2.2 and it works now.