Fusion 3 hangs when accessing shared Mac file system

[svedel]

I have very consistent application hangs when those applications access the mac filesystem through the shared folders feature in Fusion. This worked finr in 2.x (and I have reverted back from 3.0.0 to get this to work before). I just tried 3.0.1 hoping this might fix the issue, but it is still happening, so I am gonna uninstall 3.0.1 again.

This happens with my orginal XP machine, and also with a new Windows 7 macine that was freshly created under Fusion 3.0.0.

I uninstalled and reinstalled VMWare Tools in both guest machines. I am aware that there was some discussion about how to handle this properly when migrating a 2.x VM to 3.0, but as I mentioned above, the same happens in my freshly created 3.0 Windows 7 VM.

If there is anything that is required to diagnose this furhter, please let me know. As it stands, 3.0 seems to be fundamentally broken, which is sad given all the other good stuff that it does.

Thanks.

Sven

[derekn]

When you migrated, were the shares in the VM when you moved?

Or did you add the shares afterwards?

[svedel]

For the XP VM they where in place when I upgraded. The Windows 7 was newly created, so no migration. This issue manifested in 3.0.0 as well as 3.0.1 for the Windows 7 VM.

Thanks,

Sven

[derekn]

When accessing these shared files...what types are they? I am trying to determine if you have applications or tasks hitting your drive at the same time from both OSX and your VM's. Could this be a drive issue?

[svedel]

These are source files... and the generated output files (object files, .dll's and .exe's). It is certainly possible that there are other processes accessing them from MacOS. I am running time machine (although that was not actively doing a backup at the time), and ClamXAv (the folder and subfolders in question is not part of the scan list though).

Thanks,

Sven

[m40]

I had the same problem. Solved it by using a suggestion someone else here made to map the drive via regular Windows Sharing instead of the built-in VMware Shared Folders. That means you won't be mapping to
vmware-host\Shared Folders, but instead, you'll have to enable Windows Sharing on your Mac (System Preferences -> Sharing -> File Sharing) and then map the drive via Explorer in Windows/VMware through the NAT'd IP address (
192.168.235.2\folder).

[svedel]

That's interesting. I will try that over the weekend. Have you noticed a performance impact from doing this?

Thanks,

Sven