diff options
author | Yonit Halperin <yhalperi@redhat.com> | 2013-04-08 16:16:05 -0400 |
---|---|---|
committer | Yonit Halperin <yhalperi@redhat.com> | 2013-04-08 16:16:05 -0400 |
commit | c7e81980917ac0172f943f2252b0458dbc1a8cfa (patch) | |
tree | 9b4fe1031e42853cca0104903fc5057e1a8e80fc /spice-common | |
parent | 21123f34e7f3601f072efa5b5ad8bf7024e5b555 (diff) | |
download | spice-c7e81980917ac0172f943f2252b0458dbc1a8cfa.tar.gz spice-c7e81980917ac0172f943f2252b0458dbc1a8cfa.tar.xz spice-c7e81980917ac0172f943f2252b0458dbc1a8cfa.zip |
red_worker.c: fix not destroying streams before sending MSG_MIGRATE
When qemu migration completes, we need to stop the streams, and to send
the corresponding upgrade_items to the client.
Otherwise, (1) the client might display lossy regions that we don't track
(streams are not part of the migration data).
(2) streams_timeout may occur after MSG_MIGRATE has been sent, leading
to messages being sent to the client after MSG_MIGRATE and before
MSG_MIGRATE_DATA (e.g., STREAM_CLIP, STREAM_DESTROY, DRAW_COPY).
No message besides MSG_MIGRATE_DATA should be sent after
MSG_MIGRATE.
When a msg other than MIGRATE_DATA reached spice-gtk after MSG_MIGRATE,
spice-gtk sent it to dest server as the migration data, and the dest
server crashed with a "bad message size" assert.
Diffstat (limited to 'spice-common')
0 files changed, 0 insertions, 0 deletions