From: Alon Levy <alevy@redhat.com>
To: "Marc-André Lureau" <mlureau@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] spice: set spice uuid and name
Date: Fri, 2 Mar 2012 18:27:25 +0200 [thread overview]
Message-ID: <20120302162725.GF22523@garlic> (raw)
In-Reply-To: <c730889e-ff9e-4a33-a177-5380aea14aa0@zmail17.collab.prod.int.phx2.redhat.com>
On Fri, Mar 02, 2012 at 11:15:48AM -0500, Marc-André Lureau wrote:
>
>
> ----- Mensaje original -----
> > On Fri, Mar 02, 2012 at 01:49:22PM +0100, Marc-André Lureau wrote:
> > > This allows a Spice client to identify a VM
> >
> > My only problem with this is that if we have a monitor vmcchannel you
> > could issue the command to query that, and much more, without having
> > to
> > add any messages. And adding a monitor channel is really easy - the
> > only
> > requirement being that qemu can handle two monitor users, libvirt and
> > spice.
>
> Interesting idea, then we would have a Spice "qemu monitor" channel,
> and we would need to do the same job as libvirt-qemu to have a stable
> layer on top. Arguably, we could share their code, but that doesn't seem
> trivial either.
True. It would be simpler if there was a libqemumonitor inside qemu that
libvirt and us used.
>
> Both approach do not seem incompatible to me.Having a uuid/name Spice API
> can be useful for XSpice or other servers too.
True. Then it makes sense to add this.
next prev parent reply other threads:[~2012-03-02 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:49 [Qemu-devel] [PATCH] spice: set spice uuid and name Marc-André Lureau
2012-03-02 13:25 ` Gerd Hoffmann
2012-03-02 13:59 ` Marc-André Lureau
2012-03-02 14:10 ` Gerd Hoffmann
2012-03-05 17:22 ` Marc-André Lureau
2012-03-05 18:00 ` Alon Levy
2012-03-06 8:20 ` Gerd Hoffmann
2012-03-02 16:04 ` Alon Levy
2012-03-02 16:15 ` Marc-André Lureau
2012-03-02 16:27 ` Alon Levy [this message]
2012-03-12 16:13 ` Stefano Stabellini
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=20120302162725.GF22523@garlic \
--to=alevy@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=mlureau@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.