Hi, Larry. Tom is right: there's a document elsewhere in these forums that describes how to resize a virtual disk. I'll append a direct link below.
I should mention, though, that it's a multi-step process. You may wish, instead, to redo the VMware Converter operation, because Converter can proactively resize. You can delete the unnecessary files on the original source PC (or copy them temporarily to backup media, if you plan to keep that PC around) and then re-run the conversion, specifying the desired size for the virtual disks Converter builds.
Notice that you can change the disk size with the "New Disk Space" pulldown on the right.
Also, the files that were created by Converter were three: XP-flat.vmdk, XP.vmdk, and XP.vmx .
Your virtual disk consists of two files: XP.vmdk and XP-flat.vmdk. I wonder... when you told Converter how to make your new virtual machine's virtual disk, did you specify that the disk should be allowed to grow?
This is a great space-saving measure. Growable virtual disks take up, on your Mac OS disk drive, about as much space as their contents. Whenever Fusion needs to, it allocates more space for the virtual disk, up to the virtual disk's official stated "size" (that is, the size that Windows believes the disk really is). The tradeoff for this convenience is a small degradation in disk-write performance whenever the virtual disk needs to be grown. For most applications, this is a negligible cost.
Anyway, if you did not originally make the virtual disk growable, this might be one more reason to repeat the conversion.
You also asked about XP.vmx. This file is the definition of the virtual machine. Every virtual machine must have a .vmx file. However, Converter generates .vmx files that are slightly older than Fusion's. What a lot of people do is to use Converter to create a new virtual disk from their old physical PC, and then discard the .vmx file Converter creates. To make a new .vmx file, they'll use Fusion's New Virtual Machine Assistant, telling it to use an existing virtual disk -- the one created by Converter -- instead of creating a new blank one. Using an existing virtual disk is an option in the New Virtual Machine Assistant's
Virtual Hard Disk screen, under the
Advanced disk options.
Don't forget to install VMware Tools from Fusion in the new VM. The version of Tools that Converter offers to insert is not specific to Fusion.
Anyway, if you should decide to resize your already-created virtual disk instead of making a new one, here's a direct link to the document that Tom has in mind:
Resizing a Virtual Disk for Windows Guests with Step by Step Instructions
Message was edited by: brianriceca to correct a couple of places where I said "virtual machine" and meant "virtual disk"