Hi, >> +- "id": the chardev's ID, must be unique (json-string) >> +- "backend": the chardev backend: "file", "socket", ... (json-string) >> +- "path": file / device / unix socket path (json-string, optional) >> +- "name": spice channel name (json-string, optional) >> +- "host": host name (json-string, optional) >> +- "port": port number (json-string, optional) >> +- "server": create socket in server mode (json-bool, optional) >> +- "wait": wait for connect (json-bool, optional) >> +- "ipv4": force ipv4-only (json-bool, optional) >> +- "ipv6": force ipv6-only (json-bool, optional) >> +- "telnet": telnet negotiation (json-bool, optional) >> + > > As mentioned in another thread, should it support the "mux" argument > for multiplexing mode?
I don't think so. Basically the only use case for the mux chardev is -nographic with serial line + monitor being multiplexed on stdio. cheers, Gerd
