From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Shared VNC sessions
Date: Thu, 1 Nov 2007 22:01:27 +0000 [thread overview]
Message-ID: <20071101220126.GF749@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0711011533450.15585@iserv.asic-linux.com.mx>
On Thu, Nov 01, 2007 at 03:49:42PM -0600, Felipe Sanchez wrote:
>
>
> Hi, in older versions of the RFB patch it was possible to connect multiple
> VNC clients to the VNC framebuffer. With the current VNC support if I have
> one connected client then any other trying to connect will block until the
> first one disconnects.
That is correct. I had a patch floating around somewhere to immediately
drop the second connection instead of making it block forever, so at least
client don't hang.
> After a quick look at vnc.c it seems that the incoming connections are
> handled via qemu's fd_handler function which I'm guessing is where the
> blocking takes place, but I'm not really familiar with qemu's code so any
> help would be greatly appreciated :-)
The blocking isn't really anything todo with the fd handlers - the event
loop can handle this kind of thing just fine. The problem is that the
VNC server state is only capable of tracking dirty region updates for
a single client at once. To support multiple clients will require some
significant refactoring of the server state. Not impossible, but not a
quick fix either. It just needs someone motivated enough to poke at it....
> Also: Does qemu's current VNC implementation support tight encoding?
No. Raw or hextile.
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 -=|
prev parent reply other threads:[~2007-11-01 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 21:49 [Qemu-devel] Shared VNC sessions Felipe Sanchez
2007-11-01 22:01 ` 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=20071101220126.GF749@redhat.com \
--to=berrange@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 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).