On Wed, Jul 11, 2007 at 09:05:11AM -0700, 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? yes > If so, why should this be necessary? Because from an API point of view if you do a migration to some hypervisor, you're likely to need a connection to that hypervisor in the application anyway, so it's better to have the registration and the migration separate. Simplifies coding, error handling etc ... Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list