@@ -147,18 +147,12 @@ The image hostname will be set to the same as the host on which you
147147are creating its image. It is a good idea to change that to avoid
148148"Oh, bummer, I rebooted the wrong machine".
149149
150- UML supports two classes of network devices - the older uml_net ones
151- which are scheduled for obsoletion. These are called ethX. It also
152- supports the newer vector IO devices which are significantly faster
153- and have support for some standard virtual network encapsulations like
154- Ethernet over GRE and Ethernet over L2TPv3. These are called vec0.
150+ UML supports vector I/O high performance network devices which have
151+ support for some standard virtual network encapsulations like
152+ Ethernet over GRE and Ethernet over L2TPv3. These are called vecX.
155153
156- Depending on which one is in use, ``/etc/network/interfaces `` will
157- need entries like::
158-
159- # legacy UML network devices
160- auto eth0
161- iface eth0 inet dhcp
154+ When vector network devices are in use, ``/etc/network/interfaces ``
155+ will need entries like::
162156
163157 # vector UML network devices
164158 auto vec0
@@ -219,44 +213,23 @@ remote UML and other VM instances.
219213+-----------+--------+------------------------------------+------------+
220214| vde | vector | dep. on VDE VPN: Virt.Net Locator | varies |
221215+-----------+--------+------------------------------------+------------+
222- | tuntap | legacy | none | ~ 500Mbit |
223- +-----------+--------+------------------------------------+------------+
224- | daemon | legacy | none | ~ 450Mbit |
225- +-----------+--------+------------------------------------+------------+
226- | socket | legacy | none | ~ 450Mbit |
227- +-----------+--------+------------------------------------+------------+
228- | ethertap | legacy | obsolete | ~ 500Mbit |
229- +-----------+--------+------------------------------------+------------+
230- | vde | legacy | obsolete | ~ 500Mbit |
231- +-----------+--------+------------------------------------+------------+
232216
233217* All transports which have tso and checksum offloads can deliver speeds
234218 approaching 10G on TCP streams.
235219
236220* All transports which have multi-packet rx and/or tx can deliver pps
237221 rates of up to 1Mps or more.
238222
239- * All legacy transports are generally limited to ~600-700MBit and 0.05Mps.
240-
241223* GRE and L2TPv3 allow connections to all of: local machine, remote
242224 machines, remote network devices and remote UML instances.
243225
244- * Socket allows connections only between UML instances.
245-
246- * Daemon and bess require running a local switch. This switch may be
247- connected to the host as well.
248-
249226
250227Network configuration privileges
251228================================
252229
253230The majority of the supported networking modes need ``root `` privileges.
254- For example, in the legacy tuntap networking mode, users were required
255- to be part of the group associated with the tunnel device.
256-
257- For newer network drivers like the vector transports, ``root `` privilege
258- is required to fire an ioctl to setup the tun interface and/or use
259- raw sockets where needed.
231+ For example, for vector transports, ``root `` privilege is required to fire
232+ an ioctl to setup the tun interface and/or use raw sockets where needed.
260233
261234This can be achieved by granting the user a particular capability instead
262235of running UML as root. In case of vector transport, a user can add the
@@ -610,12 +583,6 @@ connect to a local area cloud (all the UML nodes using the same
610583multicast address running on hosts in the same multicast domain (LAN)
611584will be automagically connected together to a virtual LAN.
612585
613- Configuring Legacy transports
614- =============================
615-
616- Legacy transports are now considered obsolete. Please use the vector
617- versions.
618-
619586***********
620587Running UML
621588***********
0 commit comments