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

Re: [Xen-devel] [PATCH v2 6/6] Add a general description of the channel mechanism to docs/misc/

On Mon, 2014-06-16 at 10:49 +0100, David Scott wrote:
> +  type = (NONE | FILE | PTY | SOCKET | ... )

Are these the literal xenstore key values, shouty caps and all?

Is this stuff all forward compatible with the existing xenconsoled etc?
What stops it trying to manage these guys?

> +  path = <some path>
> +
> +In the default implementation where the backend is run in the toolstack
> +domain, the qemu "chardev" mechanism is used. This implementation
> +interprets the configuration as follows:
> +
> +  type = NONE: the backend will be connected to /dev/null
> +  type = FILE: the channel will be read the the output appended

"the the".

> +    to the file given by 'path'
> +  type = PTY: the backend will connect to a PTY like a regular console
> +  type = SOCKET: the backend will accept a connection on the Unix
> +    domain socket given by 'path' and proxy data to and from the device.
> +
> +If the implementation is in another domain (for example via a Mirage
> +console backend) then the behaviour will be defined by this other domain.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.