I have recently posted another thread for a separate issue on VMware-server-1.0.6-91891 running on CentOS 5.3, this issue is different but stems from the same day.
I posted there that I had downgraded from 2.0.2 to 1.0.6 and found that unless I edited both the .vmx and .vmdk file that I couldn't get the 2.0 VM's to open in 1.0.6. Out of the 4 VM's I have, 2 are up via this method, 2 more are causing problems.
This particular discussion pertains to another Windows 2003 Server VM, 70Gb in size, that unfortunately was created as monolithicSparse. I did manage to edit the vmdk file with a hex editor, and now I'm seeing 'Continum's reference to the sanbarrow.com site state that doing this a NO-NO. /sigh.
Here is where I'm at:
I can load the VM into the inventory, but when I go to start the VM:
Can't open the disk "../path/to/VM/Win2k3.vmdk" or 1 or more of the snapshots it depends on. Reason: File specified is not a virtual disk
I tried moving the .vmdk file to another folder and opening it to no avail. I tried re-opening the file in nano, let it sit overnight, but it never did open.
Attached is the current date's vmware.log
I tried making a clone of this file with vmware-vdiskmanager, which also failed:
/usr/bin/vmware-vdiskmanager -r "/var/lib/vmware/Virtual\ Machines/Windows\ 2003\ Server/Windows\ 2003\ Server.vmdk" -t 1 "Windows2003Srv.vmdk"
Using log file /tmp/vmware-root/vdiskmanager.log
Failed to open the disk '/var/lib/vmware/Virtual\ Machines/Windows\ 2003\ Server/Windows\ 2003\ Server.vmdk' : The system cannot find the file specified (25).
thoughts?