Lines Matching +full:host +full:- +full:command
1 # SPDX-License-Identifier: GPL-2.0
14 The User-Mode Linux environment allows you to create virtual serial
15 lines on the UML that are usually made to show up on the host as
18 See <http://user-mode-linux.sourceforge.net/old/input.html> for more
19 information and command line examples of how to use this facility.
34 lines to host portals. They may be accessed with 'telnet <host>
44 lines to host pseudo-terminals. Access to both traditional
45 pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
46 with this option. The assignment of UML devices to host devices
54 lines to host terminals. Access to both virtual consoles
55 (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
77 command line. The default value is "fd:0,fd:1", which attaches the
87 be overridden from the command line. The default value is "xterm",
99 command line. The default value is "pty", which attaches them to
100 traditional pseudo-terminals.
112 between the host's dsp and mixer devices and the UML sound system.
124 While the User-Mode port cannot directly talk to any physical
127 kernels can talk to each other, the host, and with the host's help,
132 <http://user-mode-linux.sourceforge.net/old/networking.html>.
134 If you'd like to be able to enable networking in the User-Mode
143 The Ethertap User-Mode Linux network transport allows a single
144 running UML to exchange packets with its host over one of the
145 host's Ethertap devices, such as /dev/tap0. Additional running
147 While the UML believes it's on a (multi-device, broadcast) virtual
148 Ethernet network, it's in fact communicating over a point-to-point
149 link with the host.
151 To use this, your host kernel must have support for Ethertap
152 devices. Also, if your host kernel is 2.4.x, it must have
156 <http://user-mode-linux.sourceforge.net/old/networking.html> That site
157 has examples of the UML command line to use to enable Ethertap
170 packets with the host over a TUN/TAP device. This option will only
171 work with a 2.4 host, unless you've applied the TUN/TAP patch to
172 your 2.2 host kernel.
174 To use this transport, your host kernel must have support for TUN/TAP
175 devices, either built-in or as a module.
186 The slip User-Mode Linux network transport allows a running UML to
187 network with its host over a point-to-point link. Unlike Ethertap,
188 which can carry any Ethernet frame (and hence even non-IP packets),
191 To use this, your host must support slip devices.
194 <http://user-mode-linux.sourceforge.net/old/networking.html>.
195 has examples of the UML command line to use to enable slip
207 This User-Mode Linux network transport allows one or more running
208 UMLs on a single host to communicate with each other, but not to
209 the host.
212 networking daemon on the host.
215 <http://user-mode-linux.sourceforge.net/old/networking.html> That site
216 has examples of the UML command line to use to enable Daemon
229 This User-Mode Linux network driver uses multi-message send
230 and receive functions. The host running the UML guest must have
241 This User-Mode Linux network transport allows one or more running
242 UMLs on a single host to communicate with each other and also
250 on the host.
254 of the UML command line to use to enable VDE networking.
265 This Multicast User-Mode Linux network transport allows multiple
266 UMLs (even ones running on different host machines!) to talk to
272 To use this, your host kernel(s) must support IP Multicasting.
275 <http://user-mode-linux.sourceforge.net/old/networking.html> That site
276 has examples of the UML command line to use to enable Multicast
289 The pcap transport makes a pcap packet stream on the host look
291 UML act as a network monitor for the host. You must have libcap
295 <http://user-mode-linux.sourceforge.net/old/networking.html> That site
296 has examples of the UML command line to use to enable this option.
307 The SLiRP User-Mode Linux network transport allows a running UML
310 known as SLiRP, a program that can re-socket IP packets back onto
311 he host on which it is run. Only IP packets are supported,
314 to the outside world that the host user is permitted, and unlike
316 privleges, setuid binaries, or SLIP devices on the host. This
321 that of a host behind a firewall that masquerades all network
338 drivers over vhost-user sockets.