Here is another gotcha... If you did not expand the partition to its full size when moving the existing install to the head of the disk then the virtual hard disk will not shrink to is maximum capacity because a copy, although no longer accessible, of the original install exists at the tail of the disk in the virtual hard disk. In other words after performing a disk cleanup by pressing the Clean Up Virtual Machine button on the General sheet of the Virtual Machine's Settings you'll notice that the .vmdk extents at the end of the disk are still rather large and not ~320 KB as would be expected if the extents were empty. If this is the case then you'll have to, if only temporarily, extend the partition to its full size, zero out the free space, do the disk clean up again and then resize if wanted. Otherwise the previously existing install at the end of the disk will still exists and basically just wastes space on the Host's file system.
↧