[Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-11 Thread Gerd Hoffmann
Handle spice client migration, i.e. inform a spice client connected about the new host and connection parameters, so it can move over the connection automatically. Signed-off-by: Gerd Hoffmann --- hmp-commands.hx | 20 qmp-commands.hx | 35 +++

Re: [Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-11 Thread Gerd Hoffmann
Hi, This way the user doesn't have to say spice/vnc again after already having set it once at command line. Doesn't fly. You can activate *both* vnc and spice, and in that case management has to send two client_migrate_info commands, one for spice and one for vnc. Also this is consistent

Re: [Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-10 Thread Daniel P. Berrange
On Mon, Jan 10, 2011 at 09:26:12PM +0200, Alon Levy wrote: > On Mon, Jan 10, 2011 at 05:37:18PM +0100, Gerd Hoffmann wrote: > > Hi, > > > > >>I like client_migrate_info and it fits both spice+vnc naming too. > > >> > > >>Given that vnc just needs hostname and port (which are present > > >>alread

Re: [Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-10 Thread Alon Levy
On Mon, Jan 10, 2011 at 05:37:18PM +0100, Gerd Hoffmann wrote: > Hi, > > >>I like client_migrate_info and it fits both spice+vnc naming too. > >> > >>Given that vnc just needs hostname and port (which are present > >>already) and the arguments not used by vnc are optional all we need > >>to do i

Re: [Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-10 Thread Gerd Hoffmann
Hi, I like client_migrate_info and it fits both spice+vnc naming too. Given that vnc just needs hostname and port (which are present already) and the arguments not used by vnc are optional all we need to do is rename the command and add a "protocol" argument similar to "set_password", correct

Re: [Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-10 Thread Daniel P. Berrange
On Mon, Jan 10, 2011 at 05:08:40PM +0100, Gerd Hoffmann wrote: > On 01/10/11 16:57, Alon Levy wrote: > >>>+spice_migrate_info > >>>+-- > >>>+ > >>>+Set the spice connection info for the migration target. The spice > >>>+server will ask the spice client to automatically reconnect us

Re: [Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-10 Thread Gerd Hoffmann
On 01/10/11 16:57, Alon Levy wrote: +spice_migrate_info +-- + +Set the spice connection info for the migration target. The spice +server will ask the spice client to automatically reconnect using the +new parameters (if specified) once the vm migration finished +successfully. + +

Re: [Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-10 Thread Alon Levy
On Mon, Jan 10, 2011 at 03:49:34PM +, Daniel P. Berrange wrote: > On Mon, Jan 10, 2011 at 02:31:47PM +0100, Gerd Hoffmann wrote: > > Handle spice client migration, i.e. inform a spice client connected > > about the new host and connection parameters, so it can move over the > > connection autom

Re: [Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-10 Thread Daniel P. Berrange
On Mon, Jan 10, 2011 at 02:31:47PM +0100, Gerd Hoffmann wrote: > Handle spice client migration, i.e. inform a spice client connected > about the new host and connection parameters, so it can move over the > connection automatically. > > Signed-off-by: Gerd Hoffmann > --- > hmp-commands.hx | 20

[Qemu-devel] [PATCH 2/6] spice: client migration.

2011-01-10 Thread Gerd Hoffmann
Handle spice client migration, i.e. inform a spice client connected about the new host and connection parameters, so it can move over the connection automatically. Signed-off-by: Gerd Hoffmann --- hmp-commands.hx | 20 qmp-commands.hx | 35 +++