Back to bug 1019053
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Bala.FA | 2013-10-15 05:49:35 UTC | Blocks | 1019058 | |
| Daniel Berrangé | 2013-10-15 10:46:31 UTC | CC | berrange | |
| Blocks | 1018178, 1018383, 1018530, 1018695, 1019058 | |||
| Depends On | 987555 | |||
| Jiri Denemark | 2013-10-18 14:43:30 UTC | Status | NEW | CLOSED |
| CC | jdenemar | |||
| Resolution | --- | NEXTRELEASE | ||
| Last Closed | 2013-10-18 10:43:30 UTC | |||
| Leonardo Garcia | 2014-07-04 02:17:11 UTC | CC | lagarcia | |
| John Skeoch | 2015-11-23 02:58:09 UTC | CC | dpati | |
| Jiri Herrmann | 2016-06-20 17:21:13 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 1019053