Hi,
On 08/26/2011 10:07 AM, Alon Levy wrote:
On Thu, Aug 25, 2011 at 01:57:21PM +0200, Hans de Goede wrote:
Hi,
On 08/25/2011 01:35 PM, Gerd Hoffmann wrote:
Hi,
Some examples of why having a generic spicevmc pass through is good:
(5) Redirect the serial or virtio console over spice. Especially with
spice-gtk it should be easy to wind up the spice client side to a
vte widget.
Right, so this would be very similar to doing the qemu
monitor over a spice channel. So what we need is some spice-gtk
code to plug a spicevmc channel into a vte widget, and then
we can add both a monitor and a serial-console channel :)
With the current code you would have to let both sides know what the new
channels are:
qemu -chardev spicevmc,name=generic,channelid=128,id=mon -mon chardev=mon
# and same for virtio
spicy --spicevmc channelid=128,handler=vte
# just an example
Right, although I propose that as soon as we've a vte channel handler, we
reserve channel-ids for monitor and serial-console channels, so that the
client will know how to handle these without needing special cmdline
options, and can even represent them in its menu with sensible entries
like: "show qemu monitor" "show serial console X" (we can have
multiple serial consoles)
Regards,
Hans
_______________________________________________
Spice-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/spice-devel
