From: Gerd Hoffmann <kraxel@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>,
"spice-devel@freedesktop.org" <spice-devel@freedesktop.org>,
qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [Spice-devel] seamless migration with spice
Date: Mon, 12 Mar 2012 11:26:50 +0100 [thread overview]
Message-ID: <4F5DCF6A.60008@redhat.com> (raw)
In-Reply-To: <20120312100307.GD6256@garlic>
Hi,
>>> As for certain other
>>> data, such
>>> as (but not limited to) partially parsed agent messages, these should be
>>> send through the regular vmstate methods IMHO.
>>
>> That isn't easy to handle via vmstate, at least as soon as this goes
>> beyond a fixed number of fields aka 'migrate over this struct for me'.
>> Think multiple spice clients connected at the same time.
>
> Migrate this struct n times for me.
I think for the agent case this isn't needed. Or is every client
allowed to speak to the agent in case of multiple clients connected? I
somehow doubt this can work as the agent protocol can't multicast ...
cheers,
Gerd
next prev parent reply other threads:[~2012-03-12 10:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 13:16 [Qemu-devel] seamless migration with spice Yonit Halperin
2012-03-11 14:18 ` Anthony Liguori
2012-03-11 15:25 ` Alon Levy
2012-03-11 15:36 ` Anthony Liguori
2012-03-11 19:11 ` Yonit Halperin
2012-03-12 7:57 ` Gerd Hoffmann
2012-03-12 8:51 ` [Qemu-devel] [Spice-devel] " Hans de Goede
2012-03-12 9:46 ` Gerd Hoffmann
2012-03-12 10:03 ` Alon Levy
2012-03-12 10:26 ` Gerd Hoffmann [this message]
2012-03-12 11:29 ` Alon Levy
2012-03-12 11:34 ` Gerd Hoffmann
2012-03-12 11:45 ` Alon Levy
2012-03-12 12:44 ` Gerd Hoffmann
2012-03-12 14:24 ` Alon Levy
2012-03-12 14:35 ` Alon Levy
2012-03-12 11:23 ` Hans de Goede
2012-03-12 12:21 ` Gerd Hoffmann
2012-03-12 12:47 ` Yonit Halperin
2012-03-12 13:50 ` Gerd Hoffmann
2012-03-12 18:45 ` Yonit Halperin
2012-03-13 6:40 ` Gerd Hoffmann
2012-03-13 6:52 ` Yonit Halperin
2012-03-13 7:40 ` Gerd Hoffmann
2012-03-12 11:39 ` David Jaša
2012-03-12 8:42 ` Hans de Goede
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=4F5DCF6A.60008@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=hdegoede@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@freedesktop.org \
/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).