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

Thomas Treutner thomas at scripty.at
Wed Nov 18 10:14:41 UTC 2009

On Monday 16 November 2009 14:42:16 Cole Robinson wrote:
> For virDomainMigrate, the least you need is a VM pointer and an open
> connection ptr, which will be the destination connection. URI should
> only be specified if you want to migrate over a specific interface on
> the remote host, and the uri should be of the form


> tcp://hostname[:port]

and omitting the URI parameter seem to work. 

Regarding javadoc - of course one should read it, which I didn't, but I think 
it wouldn't have helped me, because 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. Refer to driver documentation for the particular URIs 

the pointer to http://libvirt.org/drvqemu.html isn't helpful as "tcp://host" 
isn't there either. 

So I think it would be helpful to add your suggestions to either javadoc or 
the drivers doc?


More information about the libvir-list mailing list