- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's actually the replacement/renaming which wasn't correct.
Depending on the virtual disk format, a virtual disk can consist of:
- a single <vmname>.vmdk file which contains metadata as well as user data
- two files where <vmname>.vmdk contains the metadata and <vmname>-flat.vmdk contains the user data
- multiple .vmdk files where <vmname>.vmdk contains the metadata, and the other .vmdk file (...f00x.vmdk or ...s00x.vmdk) contain used data
Note: There are also a few other file types, but these are the main ones.
With the conversion you ran (-t 0), you created a "single growable virtual disk" which contains metadata as well as user data.
To ensure I don't give you wrong directions, please let me know which .vmdk files you currently have?
From the steps you provided, I assume you still have the renamed new.vmdk on the F: drive which you used to overwrite the Windows XP Professional-flat.vmdk. If this is the case - and with the low disk space you have on the C: drive - I'd recommend you use the "growable virtual disk split in 2GB files" (-t 1) for the virtual disk. This will allow you to increase and/or compact the virtual disk in the future without the need of a huge amount of additional disk space.
So again, assuming the virtual disk file on the F: drive is the one which you still have, you could delete the current "Windows XP Professional.vmdk" and "Windows XP Professional-flat.vmdk" files in the VM's folder on the C: drive (please consider to backup the files before deleting them), then rename "Windows XP Professional.vmdk" on the F: drive back to "new.vmdk" and run:
vmware-vdiskmanager -r F:\new.vmdk -t 1 "C:\Virtual Machines\Windows XP Professional\Windows XP Professional.vmdk"
This will create the "Windows XP Professional.vmdk" descriptor file as well as a number of "Windows XP Professional-s00x.vmdk" files depending on the provisioned virtual disk file. With the 15GB virtual disk you should end up with ...-s001.vmdk through ...-s008.vmdk.
André