Re: [libvirt] [PATCH] qemu: introduce spiceport serial backend

Hey, Not a full review yet as I have only been looking at the doc so far. On Mon, Feb 03, 2014 at 05:41:00PM +0100, Martin Kletzander wrote: This bit is wrong as the doc ends up as * UNIX domain socket client/server description spiceport sample XML * Spice channel description unix domain socket sample XML Regarding the way it's exposed, you have chosen to go with <devices> <serial type="spiceport"> <source channel="org.qemu.console.serial.0"/> <target port="1"/> </serial> </devices> This exposes the 'org.qemu.console.serial.0' spiceport as a serial port in the guest. This spiceport can then be used by client applications to interact with the guest. This is very similar to what is done for the spice agent channel (a virtio serial port is made available in the guest and is used for client<->guest communication). Wouldn't it be more consistent to use <channel type="spiceport"> <target type="virtio" name="org.qemu.console.serial.0"/> </channel> here? When I gave some thoughts about how to expose spiceport in libvirt, I got confused as in addition to this guest<->spice client channel, spiceport is much more generic and can also be used to create some host<->spice client channels (eg forward a local host socket/... over to the client through spice). If we use <channel>, maybe this can be added later with <channel type="spiceport"> <target type="host" name="org.qemu.console.serial.0"/> <source ... /> </channel> ? (thinking out loud, and something which can be added when there is need for it) Christophe