I have used VMware converter 3.0.3 several times for moving and resizing vmware guestOSs and their disks however I have one machine that simply won't cooperate and I have no idea what to do or what I need to be looking for on my conversion logs. The operation always seems to fail on a particular volume. It's a 100 gig vmware disk. Originally the VMware host server was a 3.0.0 ESX standalone converting to a 3.0.2 ESX standalone. Thinking that it was an issue with the version, I upgraded the VMware host from 3.0.0 to 3.0.2 to match the destination. No luck with that. Right now I am attempting to convert the machine to the destination without the disk that is giving me problems. Does anyone have any other suggestions? Thanks.
Ok, so here's an update. I had to do 2 moves. I had to first move three of the four smaller disks on a seperate operation. Finally I moved the last large disk in a completely seperate move. This worked out well. I now have all the disks on the same machine. I now need to register the vmdk file (the large one) on the VMware server. How do I accomplish this. I basically created a seperate file folder where the large disk could exist, then moved it to the native file folder of the GuestOS.
I now need to add a disk to the GuestOS. When I go to add the vmdk file and I browse the directory, I do not see the file. Is there a register command? I have tried updating the VMX file with the appropriate lines however the GuestOS still doesnt see the vmdk file.
some details would be nice - like filelisting, vmx ...
No need to. I figured it out. The VMSD and the 64k vmdk file had to be updated with the new info. Once I updated these files with the correct information everything else worked out fine. Thanks for the help anyway.