I was hoping that I could delegate creation of bridge devices to libvirt for address-less bridges, in order to not have to deal with the various ways distributions handle persistent network configuration, but while this creates a libvirt network...
<network>
<name>provision</name>
<forward mode='bridge'/>
<bridge name='brprov'/>
</network>
...it doesn't actually create the bridge. Configuring the bridge
using either <forward mode="route"/> or <forward mode="nat"/> *will*
create the bridge device, but both of these require assigning an
address to the bridge which means I have to suddenly worry about
IPAM and conflicts with local networks.
I look at the various interface-related commands, and there is an
"iface-bridge" command but this requires a physical interface.
Is there any way to convince libvirt to create the bridge device for a
<forward mode='bridge'/> network?
--
Lars Kellogg-Stedman <l...@redhat.com> | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack | http://blog.oddbit.com/
signature.asc
Description: PGP signature
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
