virtualbox.org

The documentation is pretty generic when talking about teleportation. I tried to teleport a Windows XP VM on a Windows 2003 host without successes. I created an identical VM on the target machine, also Windows 2003. A question I have is about the shared storage. I have a disk dedicated to VBox Vms on the source host that I have shared via CIFS and mapped that drive on the target VM. I can see the .vdi on the target. Do I need to assign that disk to the target VM? I did.

I set up the target to listen for teleportation request on it's IP address using port 6000 without a password. When I commanded the source VM to teleport using this command: C:\Program Files\Sun\VirtualBox>VBoxManage.exe controlvm winxp teleport --host 192.168.0.143 --port 6000

I get this error:

Error: teleportation failed. Error message: Failed to connect to port 6000 on '192.168.0.143': VERR_NET_CONNECTION_REFUSED

I checked uisng VBoxManage.exe showvminfo winxp that the teleportation setting are right on the target host.

No firewall between the two host, completely open.

Any ideas?


Also, on a side note - A lot, if not all, of the articles I've read about this new feature mentions cross CPU compatibility. Moving VMs between Intel and AMD cpus. However, the manual states otherwise. Form the Teleporting section #3 "Teleporting between Intel
and AMD CPUs will probably fail with an error message." This doesn't' have anything to do with my issue, I'm using the same hardware, but I was wondering if the authors of the articles are making assumptions or if marketing is contradicting the manual.

Hi
did you start the v.m. on 192.168.0.143 the physical destination ?

physical-src:
VBoxManage startvm the_vm_host

physical-dst : (192.168.0.143)
VBoxManage modifyvm the_vm_host --teleporter on --teleporterport 6000
VBoxManage startvm the_vm_host

physical-src:
VBoxManage controlvm the_vm_host teleport --host physical-dst --port 6000

Thanks! That was it. I guess I was a little unclear on the order of operations.