</dl>
- <h4><a name="elementsConsole">Consoles, serial & parallel devices</a></h4>
+ <h4><a name="elementsConsole">Consoles, serial, parallel & channel devices</a></h4>
<p>
A character device provides a way to interact with the virtual machine.
- Paravirtualized consoles, serial ports and parallel ports are all
- classed as character devices and so represented using the same syntax.
+ Paravirtualized consoles, serial ports, parallel ports and channels are
+ all classed as character devices and so represented using the same syntax.
</p>
<pre>
<source path='/dev/pts/4'/>
<target port='0'/>
</console>
+ <channel type='unix'>
+ <source mode='bind' path='/tmp/guestfwd'/>
+ <target type='guestfwd' address='10.0.2.1' port='4600'/>
+ </channel>
</devices>
</domain></pre>
only 1 console.
</p>
+ <h6><a name="elementCharChannel">Channel</a></h6>
+
+ <p>
+ This represents a private communication channel between the host and the
+ guest.
+ </p>
+
+ <pre>
+ ...
+ <channel type='unix'>
+ <source mode='bind' path='/tmp/guestfwd'/>
+ <target type='guestfwd' address='10.0.2.1' port='4600'/>
+ </channel>
+ ...</pre>
+
+ <p>
+ This can be implemented in a variety of ways. The specific type of
+ channel is given in the <code>type</code> attribute of the
+ <code>target</code> element. Different channel types have different
+ <code>target</code> attributes.
+ </p>
+
+ <dl>
+ <dt><code>guestfwd</code></dt>
+ <dd>TCP traffic sent by the guest to a given IP address and port is
+ forwarded to the channel device on the host. The <code>target</code>
+ element must have <code>address</code> and <code>port</code> attributes.
+ <span class="since">Since 0.7.3</span></dd>
+ </dl>
+
<h5><a name="elementsCharHostInterface">Host interface</a></h5>
<p>