Back to bug 1019237

Who When What Removed Added
Jiri Denemark 2013-10-15 13:28:16 UTC Status NEW ASSIGNED
Assignee libvirt-maint jdenemar
Jiri Denemark 2013-10-22 15:27:55 UTC Status ASSIGNED POST
Jiri Denemark 2013-10-23 13:42:11 UTC Status POST MODIFIED
Fixed In Version libvirt-1.1.1-10.el7
errata-xmlrpc 2013-10-23 13:51:33 UTC Status MODIFIED ON_QA
zhe peng 2013-10-25 10:55:58 UTC Status ON_QA VERIFIED
Jiri Denemark 2013-11-06 14:16:13 UTC Status VERIFIED ASSIGNED
Jiri Denemark 2013-11-06 14:23:14 UTC Status ASSIGNED POST
Jiri Denemark 2013-11-08 15:33:39 UTC Status POST MODIFIED
Fixed In Version libvirt-1.1.1-10.el7 libvirt-1.1.1-12.el7
errata-xmlrpc 2013-11-08 15:42:56 UTC Status MODIFIED ON_QA
zhe peng 2013-11-13 07:23:06 UTC Status ON_QA VERIFIED
John Skeoch 2014-03-27 01:05:21 UTC CC jyang dallan
Ludek Smid 2014-06-13 09:51:13 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-06-13 05:51:13 UTC
Jiri Herrmann 2016-06-20 17:18:52 UTC CC jherrman
Doc Text Prior to this update, migrating a virtual machine failed when the libvirtd service used a transmission control protocol (TCP) port that was already in use. Now, it is possible to predefine a custom migration TCP port range in case the default port is in use. In addition, libvirtd now ensures that the port it chooses from the custom range is not used by another process.

Back to bug 1019237