Re: [Spice-devel] rfc seamless migration

2012-06-11 Thread Gerd Hoffmann
Hi, I'm still not a big fan of the concept of server data going through the client, this means the server will need to seriously sanity check what it receives to avoid potentially new attacks on it. I'm wondering why not do the following: 1) spicevmc device gets a savevm call, tell

Re: [Spice-devel] rfc seamless migration

2012-06-11 Thread Alon Levy
On Mon, Jun 11, 2012 at 09:25:46AM +0200, Gerd Hoffmann wrote: Hi, I'm still not a big fan of the concept of server data going through the client, this means the server will need to seriously sanity check what it receives to avoid potentially new attacks on it. I'm wondering why

Re: [Spice-devel] rfc seamless migration

2012-06-11 Thread Yonit Halperin
Hi, On 06/11/2012 10:25 AM, Gerd Hoffmann wrote: Hi, I'm still not a big fan of the concept of server data going through the client, this means the server will need to seriously sanity check what it receives to avoid potentially new attacks on it. I'm wondering why not do the following:

Re: [Spice-devel] rfc seamless migration

2012-06-11 Thread David Jaša
Hi, Alon Levy píše v Ne 10. 06. 2012 v 17:44 +0300: On Sun, Jun 10, 2012 at 04:32:54PM +0200, Hans de Goede wrote: Hi, On 06/10/2012 11:05 AM, Yonit Halperin wrote: Hi, As the qemu team rejected integrating spice connection migration in qemu migration process, we remain with a

[Spice-devel] rfc seamless migration

2012-06-10 Thread Yonit Halperin
Hi, As the qemu team rejected integrating spice connection migration in qemu migration process, we remain with a solution that will involve libvirt, and passing data from the src to the target via the client. Before I continue with the implementation I'd like to hear your comments on the

Re: [Spice-devel] rfc seamless migration

2012-06-10 Thread Alon Levy
On Sun, Jun 10, 2012 at 04:32:54PM +0200, Hans de Goede wrote: Hi, On 06/10/2012 11:05 AM, Yonit Halperin wrote: Hi, As the qemu team rejected integrating spice connection migration in qemu migration process, we remain with a solution that will involve libvirt, and passing data from

Re: [Spice-devel] rfc seamless migration

2012-06-10 Thread Hans de Goede
Hi, On 06/10/2012 04:44 PM, Alon Levy wrote: snip Obligatory migration data: - (1) agent/spicevmc/smartcard write buffer. i.e., data that reached the server after savevm, and thus was not written to the device. Currently, spicevmc and smartcard do not have write

Re: [Spice-devel] rfc seamless migration

2012-06-10 Thread Alon Levy
On Sun, Jun 10, 2012 at 05:11:06PM +0200, Hans de Goede wrote: Hi, On 06/10/2012 04:44 PM, Alon Levy wrote: snip Obligatory migration data: - (1) agent/spicevmc/smartcard write buffer. i.e., data that reached the server after savevm, and thus was not written

Re: [Spice-devel] rfc seamless migration

2012-06-10 Thread Yonit Halperin
Hi, On 06/10/2012 05:32 PM, Hans de Goede wrote: Hi, On 06/10/2012 11:05 AM, Yonit Halperin wrote: Hi, As the qemu team rejected integrating spice connection migration in qemu migration process, we remain with a solution that will involve libvirt, and passing data from the src to the target