21.09.2011 13:03, Dejan Muhamedagic wrote: > Hi, > > On Wed, Sep 21, 2011 at 11:28:07AM +0200, Michael Schwartzkopff wrote: >>> Hi, >>> >>> 19.09.2011 13:17, Michael Schwartzkopff wrote: >>>> Hi, >>>> >>>> I tested migration with a recent version of libvirt. Essentially it was >>>> from squeeze-backports. The transport qemu+ssh://<other_node>/system now >>>> needs the additional parameters >>>> >>>> --p2p --tunnelled >>>> >>>> in the migration command line. So it should be: >>>> >>>> virsh migrate <guest> --p2p --tunnelled qemu+ssh://<other_node>/system >>> >>> Do you have iptables enabled? >>> If yes, then do you allow incoming TCP traffic on ports 49152:49216 in >>> addition to 16514 >>> (http://wiki.libvirt.org/page/FAQ#What_are_the_different_migration_methods. >>> 3F)? >> >> No firewall involved. nothing listing on port 49152ff. >> >> If I use qemu+ssh for the transport I do not need libvirt to listen on >> tcp/ports.
Ah, missed +ssh. > > I think that the right way is to add a parameter with which > users can define extra options for virsh migrate. I suppose that > not everybody needs the very same options. With sane (different) defaults for each transport? Best, Vladislav _______________________________________________________ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
