mkhalil, Sorry for the delay. The support request number is 271839.
I reviewed the SR records and located the vmx files.
One was your original file and the other one was Michael's commented version of your file.
What I could not locate is the vmx file that your recreated on ESX 2.x which allowed you to migrate the VM. This will give us some hints to which parameters may have caused this error.
I assume that you used VC 1.x to recreate the vmx file on the ESX 2.x server. If not, please provide more details.
If you still have the old ESX Server in-place, I would like to get vm-support dump from it as well as from the target ESX 3.0 server.
You can FTP the dumps to our ftp server.
Message was edited by:
to correct a typo
I have uploaded the requestion information to the ftp site.
I used the ESX 2.x server's web console, not the VC 1.x, to recreate the server.
Was ther any resolution to this issue? I am seeing it trying to migrate one of my LX VMs. . .
The only thing that I have seen to work so far is to remove the virtual from inventory and then recreate it. Usually after that I have to rename the virtual machine because if I already tried to migrate it once it comes back with another error message saying "The specified key, name or identifier already exists". Just rename the VM in VC and migrate then the name can be changed back.
We've been having this problem on several of our migrations. Sometimes it stems from the cdrom being defined to use a locally available iso image. But in the last instance, the easy way to recover was to remove the cdrom device from the configuration before migrating. This allowed the migration to complete successfully, at which time the cdrom can be added back.
I got the same error migrating from ESX 2.5.4 to 3.0.2 with a Windows 2000 vm guest. I removed the CD-rom drive and it migrated successfully.
After a few days of being bothered with this issue, I found that removing the machine from the Inventory and recreating it has resolved the issue.