After upgrading amd64 from 3.0.0 to 3.0.1 I can only start one bridge. When trying to manualy start another bridge with: # ./network-bridge start bridge=xenbr1 netdev=eth1 ..I get the following error: Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the loopback driver supports. If the loopback driver is a module, you may raise this limit by passing it as a parameter (nloopbacks=<N>); if the driver is compiled statically into the kernel, then you may set the parameter using loopback.nloopbacks=<N> on the domain 0 kernel command line. How do I get my other bridge up? Is it really a lack of loopbacks? Also, what should xend-config.sxp look like for two NICs bridged? The documentation is very vague. Regards, David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, try: # ./network-bridge start bridge=xenbr1 netdev=eth1 vifnum=1 which will cause xen to use veth1 rather than veth0 which is probably being used for xenbr0. Regards, Rowan David Koski wrote:> After upgrading amd64 from 3.0.0 to 3.0.1 I can only start one bridge. > When trying to manualy start another bridge with: > > # ./network-bridge start bridge=xenbr1 netdev=eth1 > > ..I get the following error: > > Link veth0 is missing. > This may be because you have reached the limit of the number of interfaces > that the loopback driver supports. If the loopback driver is a module, you > may raise this limit by passing it as a parameter (nloopbacks=<N>); if the > driver is compiled statically into the kernel, then you may set the parameter > using loopback.nloopbacks=<N> on the domain 0 kernel command line. > > How do I get my other bridge up? Is it really a lack of loopbacks? > > Also, what should xend-config.sxp look like for two NICs bridged? The > documentation is very vague. > > Regards, > David > > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday 02 February 2006 11:31 pm, Rowan Woodhouse wrote:> Hi, > > try: > > # ./network-bridge start bridge=xenbr1 netdev=eth1 vifnum=1 > > which will cause xen to use veth1 rather than veth0 which is probably > being used for xenbr0.That did it, thanks! But it used to work without a custom script. Is there a way to configure xend-config.sxp so a custom script is not needed? Regards, David _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
David Koski wrote:> But it used to work without a custom script. Is there a way to > configure xend-config.sxp so a custom script is not needed?I don''t think this is possible as xend-config.sxp says: "To do things like [having two outgoing interfaces] write yourself a wrapper script, and call network-bridge from it, as appropriate." Regards, Rowan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
That is what I thought but with 3.0.0 it just worked without any script. I had both eth0 and eth1 in my domUs. I had "nicd = 2" in their config. David On Friday 03 February 2006 05:44 am, Rowan Woodhouse wrote:> David Koski wrote: > > But it used to work without a custom script. Is there a way to > > configure xend-config.sxp so a custom script is not needed? > > I don''t think this is possible as xend-config.sxp says: > > "To do things like [having two outgoing interfaces] write yourself a > wrapper script, and call network-bridge from it, as appropriate." > > Regards, > Rowan > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 2/3/06, Rowan Woodhouse <rowan@decaelo.co.uk> wrote:> David Koski wrote: > > But it used to work without a custom script. Is there a way to > > configure xend-config.sxp so a custom script is not needed? > > I don''t think this is possible as xend-config.sxp says: > > "To do things like [having two outgoing interfaces] write yourself a > wrapper script, and call network-bridge from it, as appropriate." > > Regards, > RowanHi, This may be a wrapper script example for 4 nics on dom0, each one bridged: ----------------->8 #!/bin/bash /etc/xen/scripts/network-bridge start bridge=xenbr0 netdev=eth0 vifnum=0 /etc/xen/scripts/network-bridge start bridge=xenbr1 netdev=eth1 vifnum=1 /etc/xen/scripts/network-bridge start bridge=xenbr2 netdev=eth2 vifnum=2 /etc/xen/scripts/network-bridge start bridge=xenbr3 netdev=eth3 vifnum=3 ----------------->8 Make the script be executed before starting xend, AND disable processing of network-bridge in xend-config.sxp. -- Bye, Fernando Maior LPIC/1(31908) LinuxCounter(391325) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Friday 03 February 2006 11:39 am, Fernando Maior wrote: <snip>> Hi, > > This may be a wrapper script example for 4 nics on dom0, each one bridged: > > ----------------->8 > #!/bin/bash > > /etc/xen/scripts/network-bridge start bridge=xenbr0 netdev=eth0 vifnum=0 > /etc/xen/scripts/network-bridge start bridge=xenbr1 netdev=eth1 vifnum=1 > /etc/xen/scripts/network-bridge start bridge=xenbr2 netdev=eth2 vifnum=2 > /etc/xen/scripts/network-bridge start bridge=xenbr3 netdev=eth3 vifnum=3 > ----------------->8Thanks. That kind of worked. I created a startup script in /etc/init.d and set it to come up just before xend with the above for two bridges. Now on shutdown it hangs (there is nothing in the script to bring the bridges down, it only has start.) At shutdown it says something about xenbr0 entering disabled state. This seems like a lot of hoops to jump through just to get another interface to bridge, especially given that 3.0.0 did it without a problem---it just worked. There has to be a better way, no? Best Regards, David Koski david.nospham@kosmosisland.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Friday 03 February 2006 11:39 am, Fernando Maior wrote: <snip>> Hi, > > This may be a wrapper script example for 4 nics on dom0, each one bridged: > > ----------------->8 > #!/bin/bash > > /etc/xen/scripts/network-bridge start bridge=xenbr0 netdev=eth0 vifnum=0 > /etc/xen/scripts/network-bridge start bridge=xenbr1 netdev=eth1 vifnum=1 > /etc/xen/scripts/network-bridge start bridge=xenbr2 netdev=eth2 vifnum=2 > /etc/xen/scripts/network-bridge start bridge=xenbr3 netdev=eth3 vifnum=3 > ----------------->8 > > Make the script be executed before starting xend, AND disable processing > of network-bridge in xend-config.sxp.I made this script to start just before xend and stop after xend: #!/bin/bash case "$1" in start) /etc/xen/scripts/network-bridge start bridge=xenbr0 netdev=eth0 vifnum=0 /etc/xen/scripts/network-bridge start bridge=xenbr1 netdev=eth1 vifnum=1 echo ;; stop) /etc/xen/scripts/network-bridge stop bridge=xenbr0 netdev=eth0 vifnum=0 /etc/xen/scripts/network-bridge stop bridge=xenbr1 netdev=eth1 vifnum=1 echo ;; *) echo "Usage: $0 [start|stop]" ;; esac The bridge is there and both NICs work in domO but only eth0 works in domU. I also did put vif = [ '''', '''' ] in the config file for the domU: name ="cvs" kernel ="/boot/xen-linux-2.6.12.6-xen" root ="/dev/sda1 ro" memory = 64 disk = [ ''phy:/dev/mapper/main-guest.cvs,sda1,w'',''phy:/dev/mapper/main-guest.cvs.swap,sda2,w'' ] vif = [ '''', '''' ] extra="3" ..and commented out: #(network-script network-bridge bridge=xenbr0 netdev=eth0) ..in xend-config.sxp. What am I missing? Regards, David Koski david.nospham@kosmosisland.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday 09 February 2006 11:06 pm, David Koski wrote:> On Friday 03 February 2006 11:39 am, Fernando Maior wrote: > > <snip> > > > This may be a wrapper script example for 4 nics on dom0, each one bridged: > > ----------------->8 > > #!/bin/bash > > > > /etc/xen/scripts/network-bridge start bridge=xenbr0 netdev=eth0 vifnum=0 > > /etc/xen/scripts/network-bridge start bridge=xenbr1 netdev=eth1 vifnum=1 > > /etc/xen/scripts/network-bridge start bridge=xenbr2 netdev=eth2 vifnum=2 > > /etc/xen/scripts/network-bridge start bridge=xenbr3 netdev=eth3 vifnum=3 > > ----------------->8 > ><snip>> The bridge is there and both NICs work in domO but only eth0 works in domU. I also > did put vif = [ '''', '''' ] in the config file for the domU:I could only get eth0 working in a domU until I changed vif to: vif = [ ''bridge=xenbr0'', ''bridge=xenbr1'' ] It would be very cool if this was documented. Best Regards, David Koski david.nospham@kosmosisland.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users