Back to bug 1018530
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Stefan Hajnoczi | 2013-10-14 08:11:09 UTC | Blocks | 1018695 | |
| Bala.FA | 2013-10-15 05:41:13 UTC | Depends On | 1019053 | |
| Bala.FA | 2013-10-15 05:49:35 UTC | Depends On | 1019058 | |
| Daniel Berrangé | 2013-10-15 10:46:31 UTC | Depends On | 1019053 | |
| Daniel Berrangé | 2013-10-15 10:49:43 UTC | Blocks | 1018178, 1018383, 1018695 | |
| Depends On | 987555, 1019058 | |||
| Ján Tomko | 2014-01-09 13:35:16 UTC | Status | NEW | POST |
| CC | jtomko | |||
| Eric Blake | 2014-01-09 16:33:47 UTC | CC | eblake | |
| Fedora Update System | 2014-01-17 14:02:00 UTC | Status | POST | MODIFIED |
| Fedora Update System | 2014-01-18 04:29:21 UTC | Status | MODIFIED | ON_QA |
| Cole Robinson | 2014-01-22 13:22:48 UTC | CC | crobinso | |
| Fedora Update System | 2014-01-26 11:54:11 UTC | Status | ON_QA | CLOSED |
| Fixed In Version | libvirt-1.0.5.9-1.fc19 | |||
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-01-26 06:54:11 UTC | |||
| Jiri Herrmann | 2016-06-20 17:19:25 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 1018530