On Fri, Oct 11, 2013 at 11:41 PM, Dan Kenigsberg wrote: >> > > >> > > yeah ! >> > > It seems gluster uses it on both sides >> > >> > Since libvirt has been using this port range first, would you open a >> > bug on gluster to avoid it? >> > >> > Dan. (prays that Vdsm is not expected to edit libvirt's migration port >> > range on installation) >> >> If it makes you feel better, you can't even do that :-) Unfortunately, >> the port range used for migration is hard-coded in libvirt. And since we >> don't use port allocator yet (patches are in progress), we don't >> automatically avoid ports that are already taken. All this is going to >> change, though. > > Are these patches posted? Is there a libvirt BZ that tracks this issue? > > Dan. In the mean time I got 3.4.1 source rpm for fedora 19 and rebuilt with patches review as in comment#2 of https://bugzilla.redhat.com/show_bug.cgi?id=1018178 Now range is 50152+ and I'm able to successfully migrate in oVirt my CentOS 6.4 VM Gianluca -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list