diff options
| author |   Doug Goldstein <cardoe@gentoo.org> | 2011-08-04 23:32:52 +0000 |
|---|---|---|
| committer | Doug Goldstein <cardoe@gentoo.org> | 2011-08-04 23:32:52 +0000 |
| commit | 96262ea127031fddc02c7cf1d15ef6e0c2355d71 (patch) | |
| tree | e5e56b3ee24f654751d0126ff476be99240207ac /app-emulation/libvirt/metadata.xml | |
| parent | Version bump. (diff) | |
| download | gentoo-2-96262ea127031fddc02c7cf1d15ef6e0c2355d71.tar.gz gentoo-2-96262ea127031fddc02c7cf1d15ef6e0c2355d71.tar.bz2 gentoo-2-96262ea127031fddc02c7cf1d15ef6e0c2355d71.zip | |
Ignore this last change. The types of bridges it removes are 'virtual' bridges, which are the same as normal bridges but they're managed by libvirt so this can actually stay disabled. USE=virt-network will now always been in libvirt can manage any part of your network or if you must pre-configure your network prior to using libvirt.
(Portage version: 2.1.10.10/cvs/Linux x86_64)
Diffstat (limited to 'app-emulation/libvirt/metadata.xml')
| -rw-r--r-- | app-emulation/libvirt/metadata.xml | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/app-emulation/libvirt/metadata.xml b/app-emulation/libvirt/metadata.xml index 58c046c0ca2f..698e41726bf5 100644 --- a/app-emulation/libvirt/metadata.xml +++ b/app-emulation/libvirt/metadata.xml @@ -63,9 +63,10 @@ Support auto learning IP addreses for routing </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 + 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. </flag> <flag name='json'> Support QEmu 0.13 JSON-based interface, using <pkg>dev-libs/yajl</pkg>. @@ -74,8 +75,10 @@ Enable virtual networking (NAT) support for guests. Includes all the dependencies for NATed network mode. Effectively any network setup that relies on libvirt to setup and configure network - interfaces on your host. This does not include bridged or - routed networks. + interfaces on your host. This can include bridged and routed + networks ONLY if you are allowing libvirt to create and manage + the underlying devices for you. In some cases this requires + enabling the 'netcf' USE flag (currently unavailable). </flag> </use> </pkgmetadata> |