On 09/23/2014 09:48 AM, Laine Stump wrote:
Instead of this, create a libvirt network that points to the ovs
bridge,
something like this:
<network>
<name>ovs-net</name>
<forward mode='bridge'/>
<bridge name='ovs0'/>
<virtualport type='openvswitch'/>
</network>
net-start and net-autostart that network, then whenever you create new
guests, point their network device at this network.
That's what I was hoping for. Thank you, thank you, thank you!
The one caveat of this is that no permanent interfaceid will be
generated for each interface, so each time a guest is started, it will
get a new OVS interfaceid. To solve this, just add:
<virtualport type='openvswitch'/>
to the guest's <interface> at some later time (this can be after the
installation is already finished) using virsh edit - a permanent
interfaceid will be automatically generated and used from then on.
What are the implications (if any) of not having a permanent interface
ID?
--
========================================================================
Ian Pilcher arequipeno(a)gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================