virtualbox.org

I'm testing out teleportation, but can't seem to get it to work. Teleporting from my AMD desktop to my Intel laptop fails. Settings are identical and virtualization acceleration is disabled. Initially I was getting an error that the source had exposed AMD features to the guest which were not available on the target (verr_ssm_load_cpuid_mismatch). I searched around and found the --synthcpu feature. If I issue the vboxmanage modifyvm command on the target machine with --synthcpu on and then try to teleport, I no longer get the error message; however, the source machine is stuck at 0% and never progresses while the destination machine says it is teleporting, but the expected completion time increases until I cancel it.

I've read the user manual and searched the forums and google but haven't found anything further. Everyone else that has had the cpuid_mismatch errors seem to get it to work with synthcpu. What am I doing wrong?

Copy the vdi file.

Copy it to/from where? It's sitting on an SMB share that's accessible to and mounted by both machines.

From old machine to new machine. Create a new guest on the new system, point to the copied vdi file.

But, then that's not a live teleportation. I know I can manually copy a VDI around, but I'm trying to get teleportation working.

It would appear that teleportation is only supported between CPUs of the same manufacturer. Going from AMD > Intel or vice versa isn't always that nice. I know, because Xen has the same flaw. At my school, we had a couple of Xen hosts and one was an AMD. Sending the VM from one Intel to another, no problem, sending it to or from the AMD caused issues.
So it would seem that the differences in the CPUs are too great for the --synthcpu option to handle. You can create a bug report in the Bugtracker (separate account needed) and ask for improvement. Be sure to check the manual first for known limitations with this teleportation feature.