[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] bridge name not passed to network backend

  • To: xen-users@xxxxxxxxxxxxx
  • From: Niels Dettenbach <nd@xxxxxxxxxxxx>
  • Date: Mon, 16 Mar 2015 10:00:11 +0100
  • Delivery-date: Mon, 16 Mar 2015 09:00:40 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

Hi Henrik,

Am Samstag, 14. MÃrz 2015, 21:15:07 schrieb Henrik Riomar:
> Hi,
> I have a problem getting backend driver domains to work with xl and
> with multiple bridges
> in the driver domain. (e.g. in a one brigde per domU setup).
> vif         = [
> 'ip=,mac=00:16:3E:ab:cd:ef,bridge=br_b,backend=net-back' ]

I'm not shure if i understand you correctly here, but i.e. in order to 
generate a network device myDomUport0 and connect it to a xenbr0 and a second 
network interface myDomUport1 to another (independent from the first) bridge 
called xenbr1 - both automatically by the bride script you may use:

vif = [ 'mac=xx:yy:zz, bridge=xenbr0, vifname=myDomUport0',
        'mac=xx:yy:zz, bridge=xenbr1, vifname=myDomUport1' ]

means: There is no need for a "backend" option from my view, but i didn't 
worked with multiple backend domains on a single machine yet. If you have 
further intentions / requirement why you really need different backend domains 
(not needed only to build different / independent switches) it might be a 
solution to use another bridge name in the second backend domain (and i.e. 
make it default in that domain too) to avoid any "misunderstandings".

Newer xen implementations (which include the xl stack) have a strongly 
reorganized networking framework.

In your /etc/xl.conf you should set up bridged networking before:

        vif.default.script="vif-bridge" # standard linux bridge
        vif.default.script="vif-openvswitch"    # openvswitch bridge

and you may add a default like:


which is used if no bridge option is explicitely added to the vif statement in 
your DomU configs. If your main target is to differentiate the two independent 
bridges / switches more than possible with standard linux bridge and/or 
ebtables you may take a look at openvswitch as an alternative to the standard 
linux bridge / switch stack too.

hth a bit - if not, sorry for the noise...


 Niels Dettenbach
 Syndicat IT & Internet
 PGP: https://syndicat.com/pub_key.asc

Attachment: signature.asc
Description: This is a digitally signed message part.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.