Displaying 2 results from an estimated 2 matches for "bridge_name".
2013 Apr 18
10
[PATCH] hotplug: add openvswitch script
....conf or use
script=vif-openvswitch in the vif configuration.
Appears to do the right thing for PV and HVM guests (including tap devices)
and with stubdomains.
In order to support VLAN tagging and trunking the "bridge" specified in the
configuration can have a special syntax, that is:
BRIDGE_NAME[.VLAN][:TRUNK,TRUNK]
e.g.
- xenbr0.99
add the VIF to VLAN99 on xenbr0
- xenbr0:99,100,101
add the VIF to xenbr0 as a trunk port receiving VLANs 99, 100 & 101
Waldi, can you confirm if I have correctly reverse engineered the syntax from
the regexp please ;-)
Signed-off-by: Ian Campb...
2015 Mar 04
3
supermin on arm
...a BaseImage =============== Final Oz Config
> > > ================ [ paths ] output_dir
> > > = /var/lib/imagefactory/images data_dir = /var/lib/oz
> > > screenshot_dir = /var/lib/oz/screenshots [ libvirt ] uri =
> > > qemu:///system image_type = raw type = kvm
bridge_name = br0
cpus = 2
memory = 1024
[ cache ]
original_media = yes
modified_media = no
jeos = no
[ icicle ]
safe_generation = no
2015-03-03 17:02:52,791 DEBUG oz.Guest.FedoraGuest thread(d367f895)
Message: libvirt bridge name is br0 2015-03-03 17:02:52,793 DEBUG
oz.Guest.FedoraGuest thread(d36...