Host system hang

[LucaBabetto]

Hi guys!

I'm having a problem with the Host (and therefore the Guest as well) hanging/freezing for several minutes when I'm lucky, forcing me to reboot when it won't unlock.

I'm running Virtualbox 4.2.1 on an Intel Core 2 Duo MacBook Pro with OS X 10.6.8 and 8GB of RAM, the guest is a 32 bit Windows 7, pretty clean I have to say!

The Mac's System Monitor shows a 180-190% cpu usage by the VM, even though it is setted to use just 1 core and with a 40% execution cap, I guess it is the cpu overusage which causes the freeze!

Even with NO programs opened (neither the antivirus) it goes quite cool for some minutes, and then it freezes.

Please, someone help me!

=Luca=

Ps: I apologize for my (probably) bad English!

[Perryg]

Post the guests log file (as an attachment) after the next freeze.
See Online Users Manual for the location of the file.

[LucaBabetto]

It hasn't got the time to make a log file.

If it unlocks, it doesn't make a log file because it doesn't crash, but if I have to reboot it doesn't make a log file either because i turn the system off before it is able to write it down!

[Perryg]

The log file is created the very second that you start the guest so there has to be a log file. right click on the guest in the VirtualBox main manager and then click show log and save. Post that as an attachment.

[LucaBabetto]

Oh I apologize! I thought that the log file was created when the guest crashes!

Here you are!

[Perryg]

There have been some updates since 4.2.1 which could help your issue. Please consider updating to the 4.2.4 including the extension pack.

https://www.virtualbox.org/wiki/Downloads

[LucaBabetto]

Oh. Honestly I didn't notice the update.

I thought that Virtualbox would warn you if there was an update!

But when I click on "Check for updates" it says I'm using the latest version available.

I hope that the new version will fix the problem!

Thanks man for your help!!

=Luca=

Edit: I've updated it and everything seems to be working fine so far!

Re-Edit: nope, it just keeps freezing everything. The log file always shows the last strip to be "VM state changed from SUSPENDING to SUSPENDED".