|
From: | Gerd Hoffmann |
Subject: | Re: [Qemu-devel] [PATCH 0/3] client_migrate_switch and auto_switch (RHBZ 725009) |
Date: | Fri, 26 Aug 2011 13:00:29 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110805 Red Hat/3.1.12-1.el6_1 Thunderbird/3.1.12 |
Hi,
Ok, so I think we should be able to fix the race outlined above without adding new monitor commands, just by letting libvirt set the spice ticket in stage 2.Is that different then what I suggested in my reply to Daniel's 5 stage outline?
I think we have to care to not mix up switch-host and seamless spice client migration, your reply seems to refer top some seamless spice migration implementation ideas.
Today we seem to have this workflow: (1) migration src->dst (stage 3) (2a) libvirt sets spice ticket at dst (not sure which stage) (2b) spice client switches connection to dst2a and 2b are racing here. I think we can fix the race by doing this instead:
(1) libvirt sets spice ticket at dst (stage 2) (2) migration src->dst (stage 3) (3) spice client switches connection to dst cheers, Gerd
[Prev in Thread] | Current Thread | [Next in Thread] |