According to Stefan Berger on 3/3/2010 5:09 AM: > This adds more information about the different macvtap device modes. > > + <dl> > + <dt><code>vepa</code></dt> > + <dd>All VMs' packets are sent to the external bridge. Packets > + whose destination is a VM on the same host as where the > + packet originates from are sent back to the host by the VEPA > + capable bridge (today's bridges are typically not VEPA capable).</dd> Given that VEPA is relatively new and not common yet, is it worth a link to some external page giving more details about VEPA, or even just spelling out the acronym once? > + <dt><code>bridge</code></dt> > + <dd>Packets whose destination is on the same host as where they > + originate from are directly delivered to the target macvtap device. > + Both origin and destination devices need to be in bridge mode > + for direct delivery. If either one of them is in <code>vepa</code> mode, > + a VEPA capable bridge is required. > + <dt><code>private</code></dt> > + <dd>All packets are sent to the external bridge and will only be > + delivered to a target VM on the same host if the are sent through an s/the are/they are/ > + external router or gateway and that device sends them back to the > + host. This procedure is followed if either the source or destination > + device is in <code>private</code> mode.</dd> > + </dl> > + -- Eric Blake eblake@xxxxxxxxxx +1-801-349-2682 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list