From: Michal Privoznik <mprivozn@redhat.com>
To: Yonit Halperin <yhalperi@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/5] add support for spice migration v3
Date: Tue, 21 Aug 2012 11:20:36 +0200 [thread overview]
Message-ID: <503352E4.5090906@redhat.com> (raw)
In-Reply-To: <1345539119-26196-1-git-send-email-yhalperi@redhat.com>
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
next prev parent reply other threads:[~2012-08-21 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 8:51 [Qemu-devel] [PATCH v3 0/5] add support for spice migration v3 Yonit Halperin
2012-08-21 8:51 ` [Qemu-devel] [PATCH v3 1/5] spice: notify spice server on vm start/stop Yonit Halperin
2012-08-21 8:51 ` [Qemu-devel] [PATCH v3 2/5] spice: notify on vm state change only via spice_server_vm_start/stop Yonit Halperin
2012-08-21 8:51 ` [Qemu-devel] [PATCH v3 3/5] spice migration: add QEVENT_SPICE_MIGRATE_COMPLETED Yonit Halperin
2012-08-21 14:09 ` Luiz Capitulino
2012-08-21 8:51 ` [Qemu-devel] [PATCH v3 4/5] spice: add 'migrated' flag to spice info Yonit Halperin
2012-08-21 14:10 ` Luiz Capitulino
2012-08-21 8:51 ` [Qemu-devel] [PATCH v3 5/5] spice: adding seamless-migration option to the command line Yonit Halperin
2012-08-21 9:20 ` Michal Privoznik [this message]
2012-08-21 10:35 ` [Qemu-devel] [PATCH v3 0/5] add support for spice migration v3 Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=503352E4.5090906@redhat.com \
--to=mprivozn@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yhalperi@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).