I am getting the same errors on my hosts - but they are still 2.5.3 running under virtual center 2
I received the same error when trying to cold migrate a machine from ESX 2.5 to 3. The machine in question was running Linux with a Bus Logic SCSI driver. I don't believe the Linux part comes into play because I was able to do the migration on another VM running Linux, but with the LSI Logic driver. Just thought I would add another data point for comparison.
I was able to workaround the problem by using vmkfstools and exporting the dsk files from the ESX 2.5 machine and then importing it back on the ESX 3 machine. I then created a new VM with the same configuration as the old one and told it to use an existing disk when prompted.
I'm getting the same error cold migrating from 2.5.1 to 3. Has a suitable fix been identified?
I found my problem to be with the *.vmx file.
The VM would work fine in the 2.x environment. I would shut it down, proceed with a cold migration and get the error and the VM would fail back. I would then reboot the VM and it was running well. I would then down the VM, unregistered it, deleted the *.vmx, and recreate the VM again using the original *.vmdk. After the VM was recreated in a 2.x environment, I would start it to verify that it was working ok. Then I would shut it down, perform a cold migration again. This time the VM migration was successful.
I sent the *.vmx file to VMware support to be analyzed but the could not find any issue with file.
Strange but recreating the *.vmx file solved my issue.
I can carry out the same workaround..create a new vmx file for existing disks - however the prospect of doing it for 300 guests doesnt fill me with joy.
As this doesnt seem to be a unique problem someone at vmware must be able to give us a hint as to what is wrong with the vmx file migration????
I'm having the same problem migrating a VM from 2.5.2(21059) to 3.0. I've tried both a Windows 2000 VM and Windows 2003 and each fails with the same error. I'm going to give the recreate workaround a try.
See this w/ a couple NT4 vms trying to migrate to ESX 3 from 2.5.0
Workaround: Right click, remove from inventory.
Create new vm w/ same specs, hw, select use existing disk, browse to previous system disk.
Seems to be problems in the config. Both used buslogic controllers, but attempting to reselect the controller resulted in same error. After recreating I was able to migrate.
Would you please list the Support Request number through which you sent the vmx file?
I would like to look at it.
Sorry, anymore with things that are not critical I don't file SRs very frequently, especially with a new release warming up in the wings. I just glean as much as I can off the forums and keep pounding on it until it works. I know filing the SR is the only way to get it fixed, but if I can keep moving forward I do.
I have a clone of at least one of the NT4 systems. If you'd like I'll pull out the old and new vmx files and send them to you. You may open an SR with them, if you'd like. We do have more NT4 systems to migrate in the future, so it would be great to figure out a better way.
PM me w/ your email if you'd like to have these files.
I meant my last response to be for Jaygt not for Jae Eller.
Since Jaygt stated that the vmx files were sent to VMware Support I assumed that this was associated with a Support Request.
However, I will PM Jae if Jayot does not repond to this thread.
Message was edited by:
Corrected the spelling for Jaygt's alias
No problem. We'll hang onto the clones for a few days.
I opened request 307862 and the tech came back after a few hours and suggested using the tools to migrate manually from 2.5 to 3.0. 3 of my migrations worked. All the others on the same 2.5 host failed with the same device backing error. VM needs to figure this out or say that cloning is not supported from 2.5 to 3.0.
Do you mean vmkfstools or something else?
I'm having the same problem, except I'm trying to move a VM from one iSCSI volume to another. Successfully moved a series of other VMs, but these last two keep getting hung up on something.