qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: spice-devel <spice-devel@lists.freedesktop.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] spicevmv chardev, guest agents and paravirtual mouse
Date: Thu, 13 Jan 2011 09:52:00 +0100	[thread overview]
Message-ID: <4D2EBD30.4070601@redhat.com> (raw)
In-Reply-To: <4D2DE7AA.3010202@codemonkey.ws>

   Hi,

>> There isn't much spice-specific stuff in there. The clipboard bits
>> for example should work unmodified with vnc, one would just have to
>> hack up a vnc extention to tunnel the agent protocol over vnc (and vnc
>> client support of course).
>
> VNC already supports copy/paste as part of the protocol so can the agent
> protocol be terminated in QEMU such that the server can make use of the
> standard protocol extensions?

Should be doable too, didn't look at the vnc extension in detail though.

>> Also related: paravirtual mouse. I'd suggest to go for something new,
>> based on virtio-serial, doing just the mouse and nothing else.
>
> I'd agree. I think we want something that actually terminates in the
> kernel for Linux guests since then we can expose it as an evdev device.
> No special X driver would be needed.

Doesn't have to terminate in the kernel, you can feed the linux input 
subsystem via uinput (vdagent-linux actually does that btw.), X will get 
the events via evdev and everything works fine in the singlehead case. 
I think you need a X driver to handle multihead though.

> Is this something that makes sense for Spice in the future?

Yes.  Supporting multihead is a requirement for spice though.  Having 
the initial implementation not support it would be fine, but we need at 
least a plan how to handle this case.

> For instance, Spice makes use of a 1-off protocol whereas something like
> virt-agent uses an established RPC protocol (XML-RPC). I'm not tied to
> using any particular protocol, but I think it's very important to use a
> standardized, well specified protocol.

If that is a hard requirement it means we'll have to design something 
new for the agent, take care that it fulfills the spice requirements, 
then switch over for new deployments.  Of course we'll have to maintain 
current vdagent for backward compatibility.

Depending on the design we might be able to translate between the 
current vdagent and new agent protocol.  Being able to do that would be 
quite helpful for the transition of course.

cheers,
   Gerd

  parent reply	other threads:[~2011-01-13  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 16:12 [Qemu-devel] spicevmv chardev, guest agents and paravirtual mouse Gerd Hoffmann
2011-01-12 17:40 ` Anthony Liguori
2011-01-12 18:59   ` [Spice-devel] " Hans de Goede
2011-01-12 19:28     ` Alon Levy
2011-01-12 19:36       ` Anthony Liguori
2011-01-12 19:34     ` Anthony Liguori
2011-01-13  9:25       ` Gerd Hoffmann
2011-01-13  9:12     ` Gerd Hoffmann
2011-01-13  8:52   ` Gerd Hoffmann [this message]
2011-01-13 10:19 ` [Qemu-devel] Re: [Spice-devel] " Tiziano Müller
2011-01-13 10:54   ` 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=4D2EBD30.4070601@redhat.com \
    --to=kraxel@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=spice-devel@lists.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).