![]() ![]() I un-installed and then re-installed VMware tools. Sorry to keep replying to my post, but I am discovering some more weirdness. Maybe this can be improved in the next Fusion release. Mapping the share to a drive doesn't help. Is this common experience - really slow shared folders?Īny advice to speed things up? I tried to use Windows file sharing from my Mac rather than Fusion shared folders and it was no better - might have even been worse. If I copy the file to my virtual disk, and double click the copy, things are very speedy but I want to keep my files where my Mac subversion client can access them. But Parallels could handle files of this size. ![]() The file is a 15 meg file so that is a factor. With Fusion I seem to have to wait 3 or 4 times as long for a double click to have the app open the file. With Parallels, it was slow but usable to double click a file in a shared folder and have the Windows app open it. I keep my subversion check-out for a company project on my Mac file system and some of the files are Windows-only binaries - discrete event simulation files for the product Extend. One thing I was disappointed with in Parallels was the speed at which file reads and writes from a shared folder happened. This setting is defined at the time of creating the virtual disk with VMware Workstation.I was a mostly satisfied user of Parallels (version 2.5) but I bought the early bird special license for Fusion and have been trying it out the past few days. If you are going to be moving VMs between PCs that have this 2GB file limitation then you should consider configuring any future virtual disks to use a set of files limited to 2GB per file. Note: The VMX file is generally found in the same directory as your VMs VMDK file. Though not to worry all is not lost as you can tell VMware Workstation to skip checking any underlying disk file size limitations (ie: 2GB) by adding the following line to your VMs VMX file. For example a hard disk formatted with FAT32 will throw up this error. Your VMs VMDK disk will, in the majority of cases be bigger than this. "The most common cause is that, as the error message outlines, the underlying file system on which the VM is being run from doesn’t support larger files than 2GB. vmware-workstation-cannot-open-one-of-the-virtual-disks-needed-by-this-vm-because-it-is-larger-that-the-maximum-size-supported-by-the-host-file-system/ Some remote file systems do not support files larger than 2 GB, even though the file system on the server might.Ĭannot open the disk 'D:\Virtual Machines\Mac OS X Yosemite\OS X 10.10 Yosemite.vmdk' or one of the snapshot disks it depends on. VMware Player cannot open one of the virtual disks needed by this VM because it is larger than the maximum file size supported by the host file system. ![]() Again, I made an exact copy of the working VM. Both drives are of course NTFS and obviously supports the 15GB file. When I try to start the VM I just get the error below. And when I opened it, I got the usual dialog that says it noticed the new location, and I chose that I copied it. I copied the entire VM image and files to my SSD. Now I bought a new SSD and wanted to move the image to it to take advantage of the speed increase. Because I was lacking space on my SSD I placed the VMware image on a different drive. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |