qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <aliguori@cs.utexas.edu>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Support VNC PointerTypeChange psuedo-encoding
Date: Sun, 7 Jan 2007 17:20:37 +0000	[thread overview]
Message-ID: <20070107172037.GA27243@redhat.com> (raw)
In-Reply-To: <459F17D8.2090703@cs.utexas.edu>

On Fri, Jan 05, 2007 at 09:30:32PM -0600, Anthony Liguori wrote:
> The following patch adds support to the VNC server for the 
> PointerTypeChange.  This is a new encoding I've defined specifically for 
> virtualization.  It allows a VNC client to support a server that has a 
> relative mouse (such as a PS/2 mouse in QEMU).  If you're familiar with 
> the mouse being offset in a VNC session, this patch is the proper way to 
> address that.
> 
> This extension is documented at http://tocm.wikidot.com/pointertypechange
> 
> It uses a type that I've reserved in the latest RFB spec.
> 
> Currently, the only client that supports this encoding is my PoC client 
> available at http://hg.codemonkey.ws/vnc-gui.  I've also talked to Dan 
> Berrange, the virt-manager maintainer, and I believe he plans on 
> supporting this extension in virt-manager too.  Once QEMU supports the 
> encoding, I suspect some of the other more popular VNC clients will 
> considering also supporting it.

Yes, I will be implementing this extension in virt-manager, since its the
only approach to mouse pointer sanity which is portable across different
guest OS. Client-end code to make use of this extension is quite simple,
so I expect regular VNC clients could easily add support for it. For those
not familiar with VNC protocol, its worth noting that this extension is
'opt-in' - ie current default mouse pointer handling is unchanged, unless
the VNC client explicitly asks for it to be turned on.

That all said, if you've configured QEMU to use one of the pointer devices
which does absolute co-ordinates correctly (ie the graphics tables), then
you don't want to turn on this extension. ie. If you can get absolute coords
going through the whole stack Local Desktop -> VNC Client -> QEMU -> Guest OS
-> Guest Desktop, then that is the perfect approach because it doesn't
require you to do a local cursor-grab.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

      reply	other threads:[~2007-01-07 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-06  3:30 [Qemu-devel] [PATCH] Support VNC PointerTypeChange psuedo-encoding Anthony Liguori
2007-01-07 17:20 ` Daniel P. Berrange [this message]

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=20070107172037.GA27243@redhat.com \
    --to=berrange@redhat.com \
    --cc=aliguori@cs.utexas.edu \
    --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 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).