The only time most people will "need" to use a VMDK (a.k.a.: not split) is if they need the virtual machine to be compatible with a VMware ESX based host.
(Many tools have trouble opening very large files.) And if you ever need to recover data from a corrupt VMDK, it's easier working with 2GB files. Additionally, copying 2GB chunks is more reliable than a single 60GB file. (Try creating a new test VM in Fusion or Player and messing with the advanced settings.) Having the VMDK in 2GB chunk will allow you to use a FAT32 partitioned disk, which can then be used with Windows or OSX without any additional software. Normally you have to specify this when you create the virtual disk, but it can be converted later. VMware Player, Workstation and Fusion all support VMDK files split into multiple 2GB chunks. However I will explain an alternate method for you: 2GB split VMDKs. But Tuxera is not free so you may want to try 3G-NTFS first. I was getting suspicious errors when running large monolithic VMDK files (i.e.: 60GB VMDK) which caused me to switch from 3G-NTFS to Tuxera.
You can get the free 3G-NTFS to do the same. Me personally, I use Tuxera NTFS to mount NTFS partitions. It's up to the host OS (a.k.a.: OSX) to mount the exFAT partition, then Fusion will use that drive just like it would any other drive that your VM files are stored on. Fusion by itself doesn't deal with exFAT.
0 kommentar(er)
