Dan Smith wrote:
DV> you really want a pointer to an existing connection, not an URI
DV> and hostname. Sure you could get the virConnectPtr based on the
DV> URI, but it's better to rely on the user to do that step
DV> independantly.
So that implies that in order to perform a migration with libvirt, the
user will need the libvirt daemon running and accessible on the remote
machine, is that right? If so, why should this be necessary?
1) It's required for tcp:// migration in QEMU/KVM
2) Xen is insane for allowing arbitrary incoming migrations from
anywhere. When the Xen migration model is made more sane, you'll
probably be forced to tell a destination node that it should accept an
incoming migration for a particular domain.
Regards,
Anthony Liguori
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
