I had problems running vmware images from a mounted ntfs filesystem in Ubuntu 10.04. The problem was that the process mount.ntfs used 100% CPU and froze my computer only a few moments after starting the image in wmware-player. I guess the mounting of ntfs filesystems aren’t that good in Ubuntu. At least not when you have an application that is very write-intensive.
The solution was to open the .vmx file and add this row:
workingDir = ”../../../var/vmware”
This is where vmware-player stores ”suspend files and snapshots. The path should be relative to the image-dir and be writable to the user running vmware-player. And of course, don’t change the path to another mounted ntfs-filesystem. You should also be able to edit the workingdir by using the vmware-player GUI as well. Look at screenshot below.