On Sun, Apr 19, 2009 at 09:16:53AM +0200, Chris Lalancette wrote:
Zvi Dubitzky wrote:
What is the meaning of using virDomainMigrate () with NULL uri. Looking at the code of qemudDomainMigratePrepare2 ()/ qemu_driver.c, I understand that it tries to perform a migration to another VM on the same node . Is that correct ?
No, that's not right. The URI parameter is generally not needed when you are doing a live migrate; it's basically there to specify an "alternate" way to reach the remote qemu process, but I've haven't come across a case where it is useful yet. That is, you *should* set URI to NULL, and let libvirt handle the details.
The time it is useful is if your machine has multiple NICs, you are using one set of interfaces for management, and want migration to go over a different interface that's perhaps more suited for low-latency/high-bandwidth needs of migration. In this case you'd give a URI refering to the alternate interface's IP address Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|