qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/2] Tunnel character device data over VNC (v1)


From: Gerd Hoffmann
Subject: Re: [Qemu-devel] [PATCH 0/2] Tunnel character device data over VNC (v1)
Date: Wed, 01 Jul 2009 21:41:26 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2

On 07/01/09 20:51, Anthony Liguori wrote:
Allowing multiple readers/writers for character devices is much more
complex to get right though. The current chardev API does not have good
semantics for just handling one client that connects and disconnects. It
certainly wouldn't gracefully handle multiple client states at once.

You could do something like a mirrored mode but things get really ugly
when dealing with multiple read-write clients.

I'm thinking about mirrored mode of course. Everything else doesn't make sense for guest devices. And you have that issue with Dan's current code already: -serial unix:, then connect via socket and via vnc. Voila, two read-write clients.

Think of how that would
behave with the monitor for instance.

I agree that for something like -monitor tcp::1025,server,nowait, you
want to be able to connect multiple times and get multiple monitor
sessions.

Monitor is a special case. Multiple connections to the same session are not very useful there. Multiple sessions are a different (albeit related) problem.

cheers,
  Gerd





reply via email to

[Prev in Thread] Current Thread [Next in Thread]