In the past, moving VMs between Data stores or Hosts with snapshots was deadly.
Does this still happen in ESX4?
ESX4 does not throw the warning like ESX3.5 did.
you can migrate a VM with snapshots, you just may be seeing a different issue. You are trying to do a vMotion in vCenter?
Is this the symptoms you are seeing?
I think the same principles apply, the warning may just have been suppressed in vSphere4
see this KB
Well, best way to answer your own question is to just test it.
You cannot migrate a VM with a snapshot. You will get the "the parent virtual disk has been modified since the child was created"
Guess snapshot migrations are still a thing of the future!
Has anyone found a way to fix this or a way around it?
you can migrate a VM with snapshots, you just may be seeing a different issue. You are trying to do a vMotion in vCenter?
Is this the symptoms you are seeing?
You sir are a genius.
So you CAN migrate servers from an ESX 3.5 host on Local storage to ESX 4 host with SAN storage with snapshots.
The VM had three different vmdks with two snapshots making 9 wonderful files to play with but after fixing all of the CIDs, we had magic land!
Very work heavy to migrate vms with snaps but its a solution for those "oooh. crap" moments!
Thank you!