On Thu, Feb 20, 2014 at 6:47 AM, Zoltan Kiss <zoltan.kiss@xxxxxxxxxx> wrote: > On 19/02/14 16:45, Luis R. Rodriguez wrote: > >> You seem to describe a case whereby it can make sense for xen-netback >> interfaces to end up becoming the root port of a bridge. Can you >> elaborate a little more on that as it was unclear the use case. > > Well, I might be wrong on that, but the scenario I was thinking: a guest > (let's say domain 1) can have multiple interfaces on different Dom0 (or > driver domain) bridges, let's say vif1.0 is plugged into xenbr0 and vif1.1 > is in xenbr1. If the guest wants to make a bridge of this two, then using > STP makes sense. The bridging would happen on the front end in that case no? > I wanted to bring up CloudStack's virtual router as an > example, but then I realized it's probably doesn't do such thing. However I > don't think we should hardcode that a netback interface can't be RP ever. My patch did allow for this but the root block flag that Stephen mentioned can always be lifted. Luis -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
