On 01/27/2012 02:45 PM, Roopa Prabhu wrote:
The existing forward mode bridge could also work perhaps. If there are no
special cases for ovs.
<network>
<name>ovs-network</name>
<forward mode='bridge' dev='ovs-bridge'>
<script path='/etc/qemu-ifup-ovs'/>
</forward>
</network>
This one would be confused with macvtap in bridge mode (which is
recognized by mode='bridge' and the presence of a dev attribute (or
rather, an array of <interface> elements being present, of which by
definition the first is copied into the dev attribute for historical
reasons).
Or maybe the real syntax is,
<network>
<name>ovs-network</name>
<forward mode='bridge'>
<bridge name='ovs-bridge'/>
<script path='/etc/qemu-ifup-ovs'/>
</forward>
</network>
A human might confuse that one with a host bridge network (which is the
same, except the <bridge> element isn't inside the <forward> element).
I'm leaning towards:
<network>
<name>ovs-network</name>
<forward mode='bridge'/>
<bridge name='ovs-bridge' type='openvswitch'/>
</network>
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list