Hi,
>> What about the second part? it's independant of the async issue.
>
> Isn't this a client problem? The client has this state, no?
It is state of the client <-> server session. Today spice client
creates a new session on migration, so there is simply no need to
maintain any state. Draw
Hi.
On 03/11/2012 05:36 PM, Anthony Liguori wrote:
On 03/11/2012 10:25 AM, Alon Levy wrote:
On Sun, Mar 11, 2012 at 09:18:17AM -0500, Anthony Liguori wrote:
On 03/11/2012 08:16 AM, Yonit Halperin wrote:
Hi,
We would like to implement seamless migration for Spice, i.e.,
keeping the
currently o
Hi,
We would like to implement seamless migration for Spice, i.e., keeping
the currently opened spice client session valid after migration.
Today, the spice client establishes the connection to the destination
before migration starts, and when migration completes, the client's
session is moved
On 03/11/2012 10:25 AM, Alon Levy wrote:
On Sun, Mar 11, 2012 at 09:18:17AM -0500, Anthony Liguori wrote:
On 03/11/2012 08:16 AM, Yonit Halperin wrote:
Hi,
We would like to implement seamless migration for Spice, i.e., keeping the
currently opened spice client session valid after migration.
To
On Sun, Mar 11, 2012 at 09:18:17AM -0500, Anthony Liguori wrote:
> On 03/11/2012 08:16 AM, Yonit Halperin wrote:
> >Hi,
> >
> >We would like to implement seamless migration for Spice, i.e., keeping the
> >currently opened spice client session valid after migration.
> >Today, the spice client establ
On 03/11/2012 08:16 AM, Yonit Halperin wrote:
Hi,
We would like to implement seamless migration for Spice, i.e., keeping the
currently opened spice client session valid after migration.
Today, the spice client establishes the connection to the destination before
migration starts, and when migrat
