itut_itut
Contributor
Contributor

Fusion Extremely slow on MacBook Pro

I have a MacBook Pro (Santa Rosa) with 4GB memory. I installed a beta version of fusion a couple of months ago and every things seemed to be working fine. Both OSX and WindowsXP were pretty responsive.

A few weeks ago I bought a license and updated Fusion. There was no discernible change in the performance of both OSX and XP after the upgrade. Last week I installed Office 2003 and also enabled auto update in XP. In the last couple of days, whenever I run the VM, the whole machine slows to a crawl. I almost seems to hang. It takes more than 10 minutes for any response to a mouse click.

The only way out is to shut down XP.

Any one has any ideas what might be the issue ?

Thanks

PS: the log file and vmx file is attached

0 Kudos
4 Replies
darkone3381
Contributor
Contributor

start task manager in your XP VM. Is there a process using lots of CPU time ?

There was an issue that affected some Xp installs a while back where Automatic updates would send an svchost.exe process into a spin at 99% and would slow everythign to a crawl.. There are some fixes out there for it if that is the case.. let us know..

0 Kudos
aetm
Hot Shot
Hot Shot

Hi Alex,

Sep 12 21:19:07.857: vmx| GuestRpcSendTimedOut: message to toolbox-dnd timed out.

Sep 12 21:19:07.857: vmx| TOOLS unity.get.binary.info failed: failure of the transport layer

Sep 12 21:19:07.857: vmx| VMXVmdbGuestBinaryInfoCB: failed: ret = VMDB failure

Sep 12 21:19:07.857: vmx| VMXVmdbGuestBinaryInfoCB: failed: ret = VMDB failure

Sep 12 21:19:07.857: vmx| GuestRpcSendTimedOut: message to toolbox-dnd timed out.

and

21:45:09.288: vmx| SCSI0:0: Command READ(10) took 6.238 seconds (ok)

Sep 12 21:45:09.290: vmx| SCSI0:0: Command READ(10) took 6.313 seconds (ok)

Sep 12 21:45:09.290: vmx| SCSI0:0: Command READ(10) took 6.283 seconds (ok)

Sep 12 21:45:09.290: vmx| SCSI0:0: Command READ(10) took 6.314 seconds (ok)

Sep 12 21:45:09.290: vmx| SCSI0:0: Command READ(10) took 6.253 seconds (ok)

Sep 12 21:45:09.290: vmx| SCSI0:0: Command READ(10) took 6.250 seconds (ok)

Sep 12 21:45:09.291: vmx| SCSI0:0: Command READ(10) took 6.245 seconds (ok)

Sep 12 21:45:09.291: vmx| SCSI0:0: Command READ(10) took 6.316 seconds (ok)

Sep 12 21:45:09.291: vmx| SCSI0:0: Command READ(10) took 6.316 seconds (ok)

Sep 12 21:45:09.291: vmx| SCSI0:0: Command READ(10) took 6.315 seconds (ok)

Sep 12 21:45:09.291: vmx| SCSI0:0: Command READ(10) took 6.315 seconds (ok)

Sep 12 21:45:09.291: vmx| SCSI0:0: Command READ(10) took 6.315 seconds (ok)

Sep 12 21:45:09.291: vmx| SCSI0:0: Command READ(10) took 6.266 seconds (ok)

Sep 12 21:45:09.292: vmx| SCSI0:0: Command READ(10) took 6.316 seconds (ok)

Sep 12 21:45:09.292: vmx| SCSI0:0: Command READ(10) took 6.264 seconds (ok)

Sep 12 21:45:09.293: vmx| SCSI0:0: Command READ(10) took 6.258 seconds (ok)

Sep 12 21:45:09.303: vmx| SCSI0:0: Command READ(10) took 6.327 seconds (ok)

Sep 12 21:45:09.303: vmx| SCSI0:0: Command READ(10) took 6.327 seconds (ok)

Sep 12 21:45:09.356: vmx| SCSI0:0: Command READ(10) took 6.306 seconds (ok)

Sep 12 21:45:09.360: vmx| SCSI0:0: Command READ(10) took 3.338 seconds (ok)

Sep 12 21:45:09.360: vmx| SCSI0:0: Command READ(10) took 3.338 seconds (ok)

Sep 12 21:45:09.363: vmx| SCSI0:0: Command READ(10) took 3.342 seconds (ok)

Sep 12 21:45:09.363: vmx| SCSI0:0: Command READ(10) took 3.342 seconds (ok)

Sep 12 21:45:09.388: vmx| SCSI0:0: Command READ(10) took 1.257 seconds (ok)

Sep 12 21:45:09.392: vmx| SCSI0:0: Command READ(10) took 3.370 seconds (ok)

Sep 12 21:45:09.413: vmx| SCSI0:0: Command READ(10) took 1.982 seconds (ok)

Sep 12 21:45:09.433: vmx| SCSI0:0: Command READ(10) took 1.277 seconds (ok)

Sep 12 21:45:09.433: vmx| SCSI0:0: Command READ(10) took 1.271 seconds (ok)

Sep 12 21:46:34.951: vmx| SCSI0:0: Command READ(10) took 1.124 seconds (ok)

Sep 12 21:46:45.340: vmx| SCSI0:0: Command READ(10) took 1.834 seconds (ok)

Sep 12 21:48:32.717: vmx| SCSI0:0: Command READ(10) took 99.499 seconds (ok)

Sep 12

look interesting. It is trying to read something on the drive but the times it take for it to do anything look way too high. 99.499 seconds..

Were the VMware Tools installed before these other installations? I would probably try to remove the tools and install them again to see if that speeds it up. Messages to toolbox are timing out ...

0 Kudos
itut_itut
Contributor
Contributor

I managed to get the task manager in XP by hitting CTRL-ALT-DEL, the CPU usage in XP was about 12% and the memory usage around 300MB (I have allocated over a gig to the VM). But the XP task manager would also freeze and only update in spurts.

I dont think its anything running in XP that is eating up the CPU, even if it did I would guess it only use the 1 CPU allocated to it. I have a feeling its the VM that is spinning.

0 Kudos
itut_itut
Contributor
Contributor

Yes, I also noticed the slow read times in the log. I did uninstall and re-install the tools in XP after upgrading the VM

0 Kudos