I've noticed a distinct increase in the amount of CPU that vb 3.2 uses when the guest is idle. On my 3.1.8 install, it used about 11% of my Athlon 3200+ processor. Now I'm seeing about 30% usage.
Doing a quick strace, it appears there's an idle loop in VB, which does a poll() and two reads() off a socket (possibly related to the display?). This used to happen 20 times a second and has now been upped to 44 / sec.
Anyone know what this is about and whether it can be configured down, to use up less of my little processor?