Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hey Felix, Unfortunately, basically no it seems... XenServer manages interfaces as bridges by default, and this setup is the one recommended by Linbit. That said, right certainly the alternative would be to just setup the interface manually on the dom0 which would avoid the whole issue to begin with, and admit, might be a better solution over-all. Just till now I've been sticking with the official instructions as much as I could and trying to avoid under the covers changes to XS when possible. Something like what this guy did to setup the interface: http://www.reidmartin.ca/tech-corner/xenserver-dedicated-interfaces/ Definitely a better solution if someone wants to keep OVS as well. Cheers, Andrew On Sun, Oct 7, 2012 at 1:08 PM, Felix Frank <ff at mpexnet.de> wrote: > Hi, > > > On 10/07/2012 05:46 PM, Andrew Eross wrote: > >> I can change from open vswitch to normal linux bridging with >> "xe-switch-network-backend bridge" on XenServer, so what the heck let's >> see if that does some magic here. >> > > meh, that seems a little exaggerated to me. > > Doesn't Xenserver allow you to un-bridge eth1 for good? I assume it's a > dedicated DRBD NIC, so there is no point in adding it to *any* bridge, > vanilla or ovs. (I went on a limb here of course - I just assume that eth1 > is the one device in xenbr1.) > > Glad that worked for you, though. > > Cheers, > Felix > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20121007/cb940a6a/attachment.htm>