summaryrefslogtreecommitdiff
path: root/Documentation/howto
diff options
context:
space:
mode:
authorGreg Rose <gvrose8192@gmail.com>2022-08-08 13:36:02 -0700
committerIlya Maximets <i.maximets@ovn.org>2022-08-15 13:07:13 +0200
commit83c9518e7c67fb73ab17f6db50f398dc78403814 (patch)
tree7290abe2d043c4f30d55975f6f2d25608a9feadc /Documentation/howto
parentac1332216eb3a1857b942457e1b44a22512b092d (diff)
downloadopenvswitch-83c9518e7c67fb73ab17f6db50f398dc78403814.tar.gz
xenserver: Remove xenserver.
Remove the current xenserver implementation - it is obsolete and since 3.0 we do not support kernel module builds [1]. 1. https://mail.openvswitch.org/pipermail/ovs-dev/2022-July/395789.html [i.maximets] Can be added back if people willing to maintain it will be found. Signed-off-by: Greg Rose <gvrose8192@gmail.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
Diffstat (limited to 'Documentation/howto')
-rw-r--r--Documentation/howto/qos.rst3
-rw-r--r--Documentation/howto/sflow.rst3
-rw-r--r--Documentation/howto/tunneling.rst3
-rw-r--r--Documentation/howto/vlan.rst3
4 files changed, 4 insertions, 8 deletions
diff --git a/Documentation/howto/qos.rst b/Documentation/howto/qos.rst
index 4462856ba..376ec2514 100644
--- a/Documentation/howto/qos.rst
+++ b/Documentation/howto/qos.rst
@@ -72,8 +72,7 @@ Both VMs (`vm1` and `vm2`) run on `host1`.
Each VM has a single interface that appears as a Linux device (e.g., ``tap0``) on the physical host.
.. note::
- For Xen/XenServer, VM interfaces appears as Linux devices with names like
- ``vif1.0``. Other Linux systems may present these interfaces as ``vnet0``,
+ VM interfaces may appear as Linux devices with names like ``vnet0``,
``vnet1``, etc.
Configuration Steps
diff --git a/Documentation/howto/sflow.rst b/Documentation/howto/sflow.rst
index c6ab0764c..74d8b8e17 100644
--- a/Documentation/howto/sflow.rst
+++ b/Documentation/howto/sflow.rst
@@ -76,8 +76,7 @@ Two Virtual Machines
This guide uses two virtual machines - `vm1` and `vm2`- running on `host1`.
.. note::
- For Xen/XenServer, VM interfaces appears as Linux devices with names like
- ``vif1.0``. Other Linux systems may present these interfaces as ``vnet0``,
+ VM interfaces may appear as Linux devices with names like ``vnet0``,
``vnet1``, etc.
Configuration Steps
diff --git a/Documentation/howto/tunneling.rst b/Documentation/howto/tunneling.rst
index 2cbca977b..8b51267e0 100644
--- a/Documentation/howto/tunneling.rst
+++ b/Documentation/howto/tunneling.rst
@@ -83,8 +83,7 @@ Each VM has a single interface that appears as a Linux device (e.g., ``tap0``)
on the physical host.
.. note::
- For Xen/XenServer, VM interfaces appears as Linux devices with names like
- ``vif1.0``. Other Linux systems may present these interfaces as ``vnet0``,
+ VM interfaces may appear as Linux devices with names like ``vnet0``,
``vnet1``, etc.
Configuration Steps
diff --git a/Documentation/howto/vlan.rst b/Documentation/howto/vlan.rst
index 86fcf9508..8f2ffa26c 100644
--- a/Documentation/howto/vlan.rst
+++ b/Documentation/howto/vlan.rst
@@ -75,8 +75,7 @@ Each VM has a single interface that appears as a Linux device (e.g., ``tap0``)
on the physical host.
.. note::
- For Xen/XenServer, VM interfaces appears as Linux devices with names like
- ``vif1.0``. Other Linux systems may present these interfaces as ``vnet0``,
+ VM interfaces may appear as Linux devices with names like ``vnet0``,
``vnet1``, etc.
Configuration Steps