From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Tunnel character device data over VNC (v1)
Date: Wed, 01 Jul 2009 13:47:12 -0500 [thread overview]
Message-ID: <4A4BAF30.8020609@codemonkey.ws> (raw)
In-Reply-To: <20090701184444.GB24144@redhat.com>
Daniel P. Berrange wrote:
> On Wed, Jul 01, 2009 at 01:36:23PM -0500, Anthony Liguori wrote:
>
>> Daniel P. Berrange wrote:
>>
>>> The following two patches make it possible to tunnel character devices
>>> over VNC, using a new VNC extension. This is motivated by the existing
>>> QEMU support for tunnelling audio streams over VNC, and the code follows
>>> a very similar design. The key requirement here is that it should not
>>> be neccessary to specifically configure each character device to make
>>> it available via VNC. The admin should be able to configure the char
>>> devices with all current available backends (file, pty, null, tcp, udp,
>>> unix, etc), and regardless of this config be able to snoop on data from
>>> any active VNC client on demand.
>>>
>>>
>> Shouldn't it just be the character devices put on vc's?
>>
>
> The 'vc' concept is a stateful one, requiring the user to switch betweeen
> channels statically and is opaque to VNC clients - all they see is a
> framebuffer with no idea that QEMU has this magic sequence to change
> what the framebuffer displays, nor what vc's are available.
I understand what you're suggesting, but I think the right way to handle
this use-case is to allow character devices to be redirected after
initial open making them truly dynamic.
This would be useful outside of VNC too.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-01 18:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 16:21 [Qemu-devel] [PATCH 0/2] Tunnel character device data over VNC (v1) Daniel P. Berrange
2009-07-01 16:26 ` [Qemu-devel] [PATCH 1/2] APIs to capture character device data Daniel P. Berrange
2009-07-01 16:27 ` [Qemu-devel] [PATCH 2/2] VNC char device data stream tunnelling Daniel P. Berrange
2009-07-01 18:44 ` Anthony Liguori
2009-07-01 16:32 ` [Qemu-devel] [PATCH 0/2] Tunnel character device data over VNC (v1) Daniel P. Berrange
2009-07-01 16:42 ` Gerd Hoffmann
2009-07-01 16:50 ` Daniel P. Berrange
2009-07-01 17:30 ` Gerd Hoffmann
2009-07-01 18:50 ` Daniel P. Berrange
2009-07-01 19:27 ` Gerd Hoffmann
2009-07-01 18:51 ` Anthony Liguori
2009-07-01 19:41 ` Gerd Hoffmann
2009-07-01 19:59 ` Anthony Liguori
2009-07-01 20:56 ` Gerd Hoffmann
2009-07-01 21:32 ` Anthony Liguori
2009-07-01 22:46 ` Gerd Hoffmann
2009-07-02 2:30 ` Jamie Lokier
2009-07-01 21:07 ` Daniel P. Berrange
2009-07-01 18:36 ` Anthony Liguori
2009-07-01 18:44 ` Daniel P. Berrange
2009-07-01 18:47 ` Anthony Liguori [this message]
2009-07-01 18:52 ` Daniel P. Berrange
2009-07-01 19:11 ` Anthony Liguori
2009-07-01 19:27 ` Daniel P. Berrange
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=4A4BAF30.8020609@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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).