From f50827e5274cecbfca8cd5a4995215087d8368fc Mon Sep 17 00:00:00 2001 From: Yonit Halperin Date: Tue, 7 May 2013 11:04:59 -0400 Subject: red_worker: fix incorrect is_low_bandwidth after migrating a low bandwidth connection MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit rhbz#956345 After a spice session has been migrated, we don't retest the network (user experience considerations). Instead, we obtain the is_low_bandwidth flag from the src-server, via the migration data. Before this patch, if we migrated from server s1 to s2 and then to s3, and if the connection to s1 was a low bandwidth one, we erroneously passed is_low_bandwidth=FALSE from s2 to s3. Cc: Marc-André Lureau --- server/red_worker.c | 3 +++ 1 file changed, 3 insertions(+) (limited to 'server') diff --git a/server/red_worker.c b/server/red_worker.c index be53c1d2..247f1534 100644 --- a/server/red_worker.c +++ b/server/red_worker.c @@ -10199,6 +10199,9 @@ static int display_channel_handle_migrate_data(RedChannelClient *rcc, uint32_t s } else { spice_critical("restoring global lz dictionary failed"); } + + dcc->common.is_low_bandwidth = migrate_data->low_bandwidth_setting; + if (migrate_data->low_bandwidth_setting) { red_channel_client_ack_set_client_window(rcc, WIDE_CLIENT_ACK_WINDOW); if (dcc->common.worker->jpeg_state == SPICE_WAN_COMPRESSION_AUTO) { -- cgit