VB 4.2.6 a CPU hog on Win7/64bit host with no VM started

[nizze]

Just upgraded from v4.1.22-80657 (no CPU hogging problem for this one) to the latest VB. Installed VB with both Bridging and Host-Only networking selected. However now just starting up the new VB (with no guest VM started) my 4.2 GHz quad core 2500K pegs in at 20% for VirtualBox.exe and 28% for VBOXSVC.exe according to Task Manager.

When using Sysinternal's Process Explorer and its Thread tab for the VboxSVC.exe process we find four rather CPU consuming ntdll.dllRtlValidateHeap+0x170 threads. For process VirtualBox.exe we have two ditto named threads plus a thread called VirtualBox.exeTrustedMain+0x2bc92c.

Nothing have changed in my software setup before updating VB. And if I go back to v4.1.22-80657 there's no CPU hogging anymore...

[nizze]

Summary: VB 2.4.6 -> VB 4.2.6 Host type: Windows

Why can't we edit the above? Or can we?

And BTW: is it possible to delete one's own ticket?

[nizze]

Replying to Hachiman: Please also set the "Host type" to Windows if possible.

[qippur]

Same issue with me. Another effect was that log file VBoxSVC.log was getting filled with "inaccessible disk" entries. (sorry, don't have exact entry as I had to empty the file because it became VERY big). Problem with me was a missing entry in .vbox file (automatically converted from previous version) not listing VM virtual hard disk in <HardDisks> section.

After adding the line, everything went fine.

I believe this is a bug, as I had the same configuration issue also before upgrading and did not experience any cpu hog.

Disk attachment problem should be logged only once and not continuously, as it fills disk and CPU.

Here is a sample of the line I had to add to config .vbox file.

<HardDisks>

<HardDisk uuid="{01234567-89ab-cdef-0123-456789abcdef}" location="DiskName.vdi" format="VDI" type="Writethrough"/>

</HardDisks>

[nizze]

UPDATE: Just upgraded from v4.1.22 to 4.2.4 and that version is likewise working fine w/o hogging the processor whereas the 4.2.6 unfortunately has one or more coding oversights resulting in CPU overtaxing...

[nizze]

UPDATE 2: Just upgraded from 4.2.4 to 4.2.8 and I can happily report that this version of Vbox works w/o hogging any CPU cores. Thanks very much, Oracle!

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.