On 21.08.2012 10:51, Yonit Halperin wrote:
> v3:
> patch 2: hold a global variable for the state of spice display, instead of 
> one per
>          device.
> 
> v2:
> Notify spice about vm state changes only via spice_server_vm_start/stop
> spice repo:  
> http://cgit.freedesktop.org/~yhalperi/spice/log/?h=seamless-migration.v2
> -----------
> Hi,
> 
> The following series introduces support for keeping the spice session active 
> after migration.
> For more details about spice seamless migration, see
> http://lists.freedesktop.org/archives/spice-devel/2012-August/010412.html
> 
> Spice branches with seamless migration support can be found at:
> spice-protocol: 
> http://cgit.freedesktop.org/~yhalperi/spice-protocol/log/?h=seamless-migration.v1
> spice-common: http://cgit.freedesktop.org/~yhalperi/spice-common/log/
> spice: 
> http://cgit.freedesktop.org/~yhalperi/spice/log/?h=seamless-migration.v1
> spicei-gtk: http://cgit.freedesktop.org/~yhalperi/spice-gtk/log/
> 
> Regards,
> Yonit.
> 
> Yonit Halperin (5):
>   spice: notify spice server on vm start/stop
>   spice: notify on vm state change only via spice_server_vm_start/stop
>   spice migration: add QEVENT_SPICE_MIGRATE_COMPLETED
>   spice: add 'migrated' flag to spice info
>   spice: adding seamless-migration option to the command line
> 
>  hmp.c              |    2 ++
>  hw/qxl.c           |    7 ++++---
>  monitor.c          |    1 +
>  monitor.h          |    1 +
>  qapi-schema.json   |    5 ++++-
>  qemu-config.c      |    3 +++
>  qemu-options.hx    |    3 +++
>  ui/spice-core.c    |   38 +++++++++++++++++++++++++++++++++++++-
>  ui/spice-display.c |   32 ++++++++++++++++++++++++++++++--
>  ui/spice-display.h |    9 +++++++--
>  10 files changed, 92 insertions(+), 9 deletions(-)
> 

Okay, from libvirt POV this is easily doable.
One one hand, libvirt doesn't query for 'query-spice' yet. But on the
other hand, we can start to if libvirt would know qemu supports it.
And it will indeed - assuming qemu will report 'seamless-migration'
option in -help output.

Michal

Reply via email to