commit: 5cb0846e4099c74b40aeaae5c1c670321b8d6a55
Author: Michal Privoznik <mprivozn <AT> redhat <DOT> com>
AuthorDate: Thu Oct 31 11:13:05 2019 +0000
Commit: Doug Goldstein <cardoe <AT> gentoo <DOT> org>
CommitDate: Mon Dec 2 14:41:37 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5cb0846e
app-emulation/libvirt: Clean macvtap USE flag description
The description for the macvtap USE flag says, that the feature
is experimental and requires new kernel. While this might have
been true when this was being added (2015), it is definitely not
true today.
Signed-off-by: Michal Privoznik <mprivozn <AT> redhat.com>
Signed-off-by: Doug Goldstein <cardoe <AT> gentoo.org>
app-emulation/libvirt/metadata.xml | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/app-emulation/libvirt/metadata.xml
b/app-emulation/libvirt/metadata.xml
index 3b887d5ce0c..16c0b4752e5 100644
--- a/app-emulation/libvirt/metadata.xml
+++ b/app-emulation/libvirt/metadata.xml
@@ -76,9 +76,7 @@
</flag>
<flag name="macvtap">
Support for MAC-based TAP (macvlan/macvtap). For networking
instead
- of the normal TUN/TAP. It has its advantages and disadvantages.
- macvtap support requires very new kernels and is
- currently evolving. Support for this is experimental at best.
+ of the normal TUN/TAP.
</flag>
<flag name="vepa">Virtual Ethernet Port Aggregator (VEPA) / 802.1Qbg
support. Relies on macvtap support.</flag>
