A virtual disk is made up of one or more .vmdk files. If you have specified that the virtual disk should be split into 2GB chunks, the number of .vmdk files depends on the size of the virtual disk. As data is added to a virtual disk, the .vmdk files grow in size, to a maximum of 2GB each. (If you specify that all space should be allocated when you create the disk, these files start at the maximum size and do not grow.) Almost all of a .vmdk file's content is the virtual machine's data, with a small portion allotted to virtual machine overhead.
If the virtual machine is connected directly to a physical disk, rather than to a virtual disk, the .vmdk file stores information about the partitions the virtual machine is allowed to access.
Earlier VMware products used the extension .dsk for virtual disk files.
- It's probably a stupid thing to say, but make sure that the VM is not running; ideally, shut down Fusion / Workstation before proceeding
- Rename the subdirectory
- Remove the log files - they play no part in the actual operation of the VM, but may be worth moving/backing up for future reference
- Remove the appListCache directory - this MAY be a VMware Fusion feature which I don't use, so don't mind losing
- Rename all of the files
- Replace references to WPX615 in the .VMX, .VMXF and .VMDK files
PS Some very useful hints from here