Luke S Crawford wrote : > Matthias Saou <[EMAIL PROTECTED]> writes: > > > ...slighty OT, but worth mentioning ;-) > > > > Now the other problem I'm having is to get Xen to use VLAN interfaces on > > top of the bonded interfaces... not working as expected either yet, and > > the Xen network scripts don't make that easy at all! ;-) > > I believe the correct foo (if you are using network-bridge) is in > /etc/xen/xend-config.sxp: > > (network-script 'network-bridge netdev=[device]') > > then in the xm config files, > > vif=["bridge=xenbr0"] > > (with, of course, your other vif options)
This works fine with ethX or even bondX interfaces, but not with vlanX or ethX.Y VLAN interfaces, as the Xen scripts break them pretty badly with their shuffling around. My current "solution" to keep things mostly reliable is to let the default script create xenbr0 from bond0, but then I run a custom script that creates xenbr1 with a vlanX interface inside it, which is a VLAN on top of bond0. But it's a somewhat ugly mix of untagged and tagged VLAN traffic... Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora release 8 (Werewolf) - Linux kernel 2.6.24.3-34.fc8 Load : 0.09 0.16 0.18 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
