Blob Blame History Raw
From 9cc48e8b7fbec4f098a65577c4ef2fd37f473d1c Mon Sep 17 00:00:00 2001
Message-Id: <9cc48e8b7fbec4f098a65577c4ef2fd37f473d1c.1383922565.git.jdenemar@redhat.com>
From: =?UTF-8?q?J=C3=A1n=20Tomko?= <jtomko@redhat.com>
Date: Thu, 7 Nov 2013 18:57:02 +0100
Subject: [PATCH] Use a port from the migration range for NBD as well

Instead of using a port from the remote display range.

https://bugzilla.redhat.com/show_bug.cgi?id=1025699
(cherry picked from commit 3e1e16aa8d4238241a1806cb9bdb3b9ad60db777)

Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
---
 src/qemu/qemu_migration.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/qemu/qemu_migration.c b/src/qemu/qemu_migration.c
index fb5568e..32ffde7 100644
--- a/src/qemu/qemu_migration.c
+++ b/src/qemu/qemu_migration.c
@@ -1118,7 +1118,7 @@ qemuMigrationStartNBDServer(virQEMUDriverPtr driver,
             goto cleanup;
 
         if (!port &&
-            ((virPortAllocatorAcquire(driver->remotePorts, &port) < 0) ||
+            ((virPortAllocatorAcquire(driver->migrationPorts, &port) < 0) ||
              (qemuMonitorNBDServerStart(priv->mon, listenAddr, port) < 0))) {
             qemuDomainObjExitMonitor(driver, vm);
             goto cleanup;
-- 
1.8.4.2