diff options
author | Yonit Halperin <yhalperi@redhat.com> | 2011-10-03 11:21:38 +0200 |
---|---|---|
committer | Yonit Halperin <yhalperi@redhat.com> | 2011-11-02 11:20:08 +0200 |
commit | cd402151def11c5748065de28d124747df09447b (patch) | |
tree | 7316f5a1bdf870bcd1af1e0765ab869211eeef4e /spice_codegen.py | |
parent | 0bf518cd3daad526a16468e82c1d6c715535e9ba (diff) | |
download | spice-cd402151def11c5748065de28d124747df09447b.tar.gz spice-cd402151def11c5748065de28d124747df09447b.tar.xz spice-cd402151def11c5748065de28d124747df09447b.zip |
server/spice.h: semi-seamless migration interface, RHBZ #738266
semi-seamless migration details:
migration source side
---------------------
(1) spice_server_migrate_connect (*): tell client to link
to the target side - send SPICE_MSG_MAIN_MIGRATE_BEGIN.
This should be called upon client_migrate_info cmd.
client_migrate_info is asynchronous.
(2) Complete spice_server_migrate_connect only when the client has been connected
to the target - wait for SPICE_MSGC_MAIN_MIGRATE_(CONNECTED|CONNECT_ERROR) or a timeout.
(3) spice_server_migrate_end: tell client migration it can switch to the target - send
SPICE_MSG_MAIN_MIGRATE_END.
(4) client cleans up all data related to the connection to the source and switches to the target.
It sends SPICE_MSGC_MAIN_MIGRATE_END.
migration target side
---------------------
(1) the server identifies itself as a migraiton target since the client is linked with (connection_id != 0)
(2) server doesn't start the channels' logic (channel->link) till it receives SPICE_MSGC_MAIN_MIGRATE_END
from the client.
* After migration starts, the target qemu is blocked and cannot accept new spice client
connections. Thus, we trigger the connection to the target upon client_migrate_info
command.
(cherry picked from commit 6e56bea67c5648b0c81990171d4bc0cf1a402043 branch 0.8)
Conflicts:
server/spice.h
Diffstat (limited to 'spice_codegen.py')
0 files changed, 0 insertions, 0 deletions