[libvirt] migration: qemu vs. qemu+tcp at virsh vs. libvirt-java

Thomas Treutner thomas at scripty.at
Wed Nov 18 14:28:12 UTC 2009

On Wednesday 18 November 2009 14:05:03 Bryan Kearney wrote:
> thanks.. I am in the code right now.. what would have been better in the
> javadoc for you? I will put it in.

"If uri is NULL, then libvirt will try to find the best method. Uri may
specify the hostname or IP address of the destination host as seen from
the source, or uri may be a URI giving transport, hostname, user, port,
etc. in the usual form. Uri should only be specified if you want to migrate 
over a specific interface on the remote host. For Qemu/KVM, the uri should be 
of the form "tcp://hostname[:port]". This does not require TCP auth to be 
setup between the connections, since migrate uses a straight TCP connection 
(unless using the PEER2PEER flag, in which case URI should be a full fledged 
libvirt URI). Refer also to driver documentation for the particular
URIs supported."

@Cole: I've merged your comment - could you please (N)ACK that? I assume 
the "tcp://.." form is a special case for Qemu/KVM, as with Xen, an IP was 


More information about the libvir-list mailing list