Thanks for the log. It is very helpful. Now we are investigating, and will keep you updated.
Your efforts and time are highly appreciated.

Could you try to uncheck "Allow your Mac to open applications in the virtual machine" in the VM's Sharing settings and see if it helps the VMwareUser CPU usage?

If it's checked, Fusion will re-publish proxy applications for all guest apps when Tools are started, which might contribute to the CPU load in the guest. It's also the reason for the "VMXVmdbGuestBinaryHandlersCB" errors, although they are harmless. Basically some applications don't have any file type or URL associations, so the call to get them fails, and the error is logged.


Looking at your log files, I'm more concerned about log messages such as "Command WRITE(10) took 1.183 seconds (ok)" and "Command READ(10) took 1.178 seconds (ok)". These mean that writing and reading from the virtual disk is delayed because of some OS X kernel file system locking issues. Basically the VM tries to read or write to the virtual disk, but OS X is blocking it from doing so, which will basically hang the VM for short periods of time, which would appear as slow performance. We are looking into these issues and working on a fix with Apple.

Just wanted to chime in. Running XP SP3 on MacBook Pro (10.5.5, 4GB RAM, 2.6GHz Core 2 Duo) with 1.5GB assigned to VM. I saw this problem continually. I have actually rolled back to a snapshot I took just before upgrading and reverted back to Fusion 1.1.3.

An interesting note though while I was still using 2.0... I tried the uninstall/reinstall of the tools. After uninstall, Windows of course rebooted. After this reboot, the VM window shows what appears to be only the top right corner of a much larger screen that the VM thinks I have. I am able to log in, but after that I have no visible/accessible Windows task bar. Installing the tools is quite problematic because the dialog boxes that appear (well, I assume they appear) for the install are in another area of the virtual screen that I cannot see or access. After trying this several times (revert to snapshot, upgrade VM to 2.0, uninstall tools, failed tools install), I gave up and went back to 1.1.3. Much more robust for me now, certainly not as snappy with moving large windows in Unity, but small price to pay for actual usability.

I see this without drag and drop. It made 2.0 unusable for me. The final beta usually works however.

This is triggered by the Cisco VPN for me. With 2.0, the VMWare tools goes to 100% cpu usage after the connection is made. Also, Norton Internet Security 2008 and PC Tools Spyware Doctor always peg to 100% cpu if I do not disable them before connecting the VPN. Something is very rotten here.

I have a dual quad MacPro with 8 GB memory.

I have that off all the time. I made a new VM with just the Cisco VPN and the McAfee software, and starting the VPN tunnel pins everything to 2 cpus 100%. Support is looking and stumped.

I also had vmwareuser.exe use more than 80 % of the CPU cycles all the time. This was after I loaded the VM after I had suspended it. I decided to close all the applications to see if it was caused by one of them, and the problem went away after I closed MS Word and Outlook. I could not tell which one was causing the problem.

JF

VMWare acknowledged that this (Cisco VPN + Security suite) is a bug with no known workaround. I was only able to get things to work with the last RC of 2.0. The released version will not work at all for me. I have been complaining about this since April with my free installation support ticket. They ignored the problem. This is not what I consider "good support." I had to buy a support incident to get any action.

So, if this affects you, try RC1 113392 build and turn off the security services before starting the VPN. That works with 2 cpus also.

Oddly, this second time, though the VM is slow as molasses, and the Mac side of the house is snappy, the vmwareuser process is not pegging the CPU at all. The System Idle Process is taking almost all the CPU, as normal. But, say, doing a build, devenv.exe is getting at most 2% CPU. Weird.