Re: [libvirt] [Users] libvirt migration port configuration and virPortAllocator
On Thu, Jan 9, 2014 at 2:27 PM, Ján Tomko wrote:
On 01/08/2014 05:48 PM, Eric Blake wrote:
> On 01/08/2014 02:45 AM, Dan Kenigsberg wrote:
>> On Wed, Jan 08, 2014 at 01:26:23AM +0100, Gianluca Cecchi wrote:
>>> Hello,
>>> following the bugzilla here:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1019053
>
> This bug was tagged against upstream libvirt. If you need it backported
> to specific Fedora releases, it might be worth cloning the BZ and making
> sure the clone is against Fedora instead of Virtualization Tools.
>
>>>
>>> we have
>>> "
>>> This is now fixed by v1.1.3-188-g0196845 and v1.1.3-189-ge3ef20d
>>> "
>>>
>>> Does this mean that f19 that has
>>> libvirt-1.0.5.8-1.fc19.x86_64
>>> is out?
>
> We can backport the patch to v1.0.5-maint if there is a compelling
> reason (such as a BZ).
>
I found the BZ and backported the patches to v1.0.5-maint:
https://bugzilla.redhat.com/show_bug.cgi?id=1018530
I will do v1.1.3-maint as well.
Jan
As it was released to updates-testing, I tested and gave positive
feedback for your backport to v1.0.5-maint
https://bugzilla.redhat.com/show_bug.cgi?id=1018530
Successfully tested also the capability to automatically change tcp
port if busy without giving error messages in webadmin gui
Thanks!
BTW with gluster 3.4.2-1, already pushed in f19 stable we have now
also there the possibility to put port range (skip if busy capability
was already there before), putting for example inside
/etc/glusterfs/glusterd.vol
option base-port 50152
Gianluca