Re: [libvirt] qemu_driver migrateuri handling broken?

Gregor Schaffrath wrote: > On Mon, Sep 21, 2009 at 12:46:46PM +0100, Daniel P. Berrange wrote: >> On Wed, Sep 16, 2009 at 05:42:50PM +0200, Gregor Schaffrath wrote: >>> Hi all. >>> >>> Short summary on DV's request ;) >>> >>> I ran into a problem migrating kvm machines with libvirt-0.6.5: >>> >>> 1) At first, using the same syntax for the migrateuri as with xen (just the >>> IP) did not work... looking into the source code (! ;) ), I found a >>> different syntax for qemu. >> The URI schemes should be listed in the driver capabilities XML. >> The reason they are different is that they are two different ways >> of doing migration. >> >> We are working on a new tunnelled migration scheme that will be >> uniform across drivers. > ic - To be honest, I was confused by the migrateuri anyhow, since I > considered the situation where libvirt traffic is tunneled via SSH, but > Xen-/KVM-/foo communication may be direct a rather rare exception (or am > I mistaken?) (I understood that this was the rationale behind the > hostname-Query in the first place) Well, the rationale is that you may have two paths to get to a machine, and you may only want to allow migration traffic on one of them (say, a direct cross-over) since the data goes across unencrypted. So you might have a machine with eth0 and eth1, where eth0 is exposed to the world, and you have libvirtd listening on eth0. But then when you actually do the migration, you want it to send the data across on eth1.