Hi, > This allows the Spice client to have a special port for the qemu > monitor: > > ... -chardev spiceport,name=org.qemu.monitor,id=monitorport > -mon chardev=monitorport Nice. I think we should have a registry of names, at least for the org.qemu.* namespace. A simple text file in docs/ should do. Monitor needs to specify the protocol (hmp vs qmp). Also adding a number doesn't hurt. So ... org.qemu.monitor.hmp.0 org.qemu.monitor.qmp.0 Also nice to have: org.qemu.console.serial.0 ... and spice client redirecting that to a vte. You might have to add some termios control messages to spiceport, so one can turn on/off echo, send breaks, xon/xoff flow control, etc to make it work really nicely. > Or to allow arbitrary communication outside of qemu: > > ... -chardev spiceport,name=org.ovirt.controller,id=...,chardev=ovcsocket > -chardev socket,server,host=0.0.0.0,port=4242,id=ovcsocket,nowait Hmm, so that will make qemu just hook those chardevs back-to-back and forward data without looking at it? I'm not sure we want that ... What is the use case? Any reason why the spice client can not (or should not) speak to ovirt directly? cheers, Gerd _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel