On Wed, Oct 12, 2011 at 12:38:50PM +0200, Yonit Halperin wrote:
> Hi,
> in the following patch series the same logic of semi-seamless for the 0.8
> branch was
> adjusted to multiple clients (and to the refactoring of
> red_channel/reds/main_channel).
> The code differs from the 0.8 branch only fo
On Wed, Oct 12, 2011 at 12:39:00PM +0200, Yonit Halperin wrote:
> We will add a qemu call to spice_server_migrate_start when migration starts.
> For now, it does nothing, but we may need this notification in the future.
> (cherry picked from commit b8213167717979e6f2fb52646e43eb458634e6a1 branch
>
On Wed, Oct 12, 2011 at 12:38:59PM +0200, Yonit Halperin wrote:
> (1) not sending anything to a migrated client till we recieve
> SPICE_MSGC_MIGRATE_END
> (2) start a new client migration (handle client_migrate_info) only after
> SPICE_MSGC_MIGRATE_END
> from the previous migration was receiv
On Wed, Oct 12, 2011 at 12:38:58PM +0200, Yonit Halperin wrote:
>
ACK
> Signed-off-by: Yonit Halperin
> ---
> server/reds.c | 45 -
> 1 files changed, 28 insertions(+), 17 deletions(-)
>
> diff --git a/server/reds.c b/server/reds.c
> index 20032a9
On Wed, Oct 12, 2011 at 12:38:57PM +0200, Yonit Halperin wrote:
> If the migration has completed successfully:
> (1) send MSG_MAIN_MIGRATE_END to the clients that are connected to the target
> (2) send MSG_MAIN_SWITCH_HOST to all the other clients
>
ACK.
> If the migration failed, send MSG_MAIN_
On Wed, Oct 12, 2011 at 12:38:56PM +0200, Yonit Halperin wrote:
>
> Signed-off-by: Yonit Halperin
> ---
> spice.proto |4
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
Cherry pick.
ACK.
> diff --git a/spice.proto b/spice.proto
> index 78c1fad..266e03a 100644
> --- a/spice.pro
On Wed, Oct 12, 2011 at 12:38:55PM +0200, Yonit Halperin wrote:
> (1) send SPICE_MSG_MAIN_MIGRATE_BEGIN upon spice_server_migrate_connect
> (to all the clients that support it)
> (2) wait for SPICE_MSGC_MAIN_MIGRATE_(CONNECTED|CONNECT_ERROR) from all the
> relevant clients,
> or a timeout,
Little patch to make spice-gtk accept RFC-conform URLs of the form
"spice://host/?port=5901".
I didn't add '/' to the list of the other characters to ignore (?;&) by
intention since
an URL like spice://host/?port=5901/somotherstuff should not be valid, resp.
the password
may contain '/' because
On Wed, Oct 12, 2011 at 12:38:54PM +0200, Yonit Halperin wrote:
ACK
> Conflicts:
>
> configure.ac
>
> Signed-off-by: Yonit Halperin
> ---
> configure.ac |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 2afc559..203e82f 1
On Wed, Oct 12, 2011 at 12:38:53PM +0200, Yonit Halperin wrote:
> Conflicts:
>
ACK.
Please move the "cherry-picked from" messages from the status to the
commit body if possible (not critical).
> server/reds.h
>
> Signed-off-by: Yonit Halperin
> ---
> server/reds.c | 29 ++
On Wed, Oct 12, 2011 at 12:38:52PM +0200, Yonit Halperin wrote:
> semi-seamless migration details:
>
ACK
> 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
These patches add a Dispatcher (dispatcher.[ch]) struct that is used to
reimplement main_dispatcher.[ch] and red_dispatcher.[ch] + red_worker.c
The first two patches I consider non RFC, the RFC is for the last patch:
it adds 500 lines of code.
it doesn't hide the underlying socket completely sin
used for main_dispatcher only in this patch.
Dispatcher is meant to be used for Main<->any low frequency messages.
It's interface is meant to include the red_dispatcher usage:
fixed size messages per message type
some messages require an ack
Some methods are added to be used by RedDispatcher l
This is part of the dispatcher update, extracting the dispatcher routine
from red_dispatcher and main_dispatcher into dispatcher.
Supporting multiple async operations will make it natural to support
async monitor commands and async guest io requests that could overlap in
time.
Related bug: https:
14 matches
Mail list logo
