similar to: Bug#396477: network-bridge script exits prematurely

Package: xen-utils-common Version: 3.0+hg11292-2 Severity: normal After a recent etch upgrade (2.6.17, xen-3.0.2) I was unable to "xm create" until I "modprobe netloop nloopbacks=10" Error was network-bridge couln't create vif interface (backend not found). brctl addbr ... fails because of no free netloop device. passing more nloopbacks device to the module fixed the

> I have installed xen-unstable change set 1150. I have 3 nics in my system. > > My ifconfig shows eth1, eth4 and eth5. > > And a brctl show shows xenbr1 only. > > When I try to create bridge 4 > > /etc/xen/scripts/network-bridge vifnum=4 start > > > > Link veth4 is missing. (...) > I tried increasing the loopback devices in the kernel boot

Hello all, I have a Xen server with 6 network interfaces, I want a bridge on all of them. I use a personal network script like this : #!/bin/bash dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=xenbr1 "$dir/network-bridge" "$@"

Hello all, I''m using Red Hat Enterprise Linux 5 (with RH Virtualization) and a Dell Poweredge 2950 with 10 NICs. My virtual operating systems are all RHEL4, and I''ve installed 4 instances. I''m trying to set up the virtual operating systems so that the physical NICs are allocated to certain operating systems. Using the following tutorial:

Hi Folks: I have a strange problem with multiple (2) NICs on a CentOS 5.5 dom0 setup running xen 3.4.3 and have been struggling to fix it for some time. I could not find anything by googling or searching through this list but that is probably because I couldn''t figure out the correct search terms. After I configure my bridges the command "system network restart" fails for eth1

I'm seeing an issue with xend not running a custom network script automatically, but works when I run it manually. In /etc/xen/xend-config.sxp I've changed: (network-script network-bridge) TO: (network-script network-custom) Here is /etc/xen/scripts/network-custom: # !/bin/bash # network-custom script=/etc/xen/scripts/network-bridge case $1 in start) $script start vifnum=0

Hello all, I have been running xen for a while now with two interfaces: dummy0 for host only communication, and eth0 for the outside network. my script looks like this: (/etc/xen/scripts/network-bridge-more) ------------------------------------------------------------------ #! /bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

As the issue concerns both the -user (configuration) and -devel (OOPS), I''m sending this message to both lists. Some time ago I complained about two problems: - VLANs are not working on machines with 100 Mbit cards - I get a kernel Oops (sometimes panic) when I try to use bonding and VLANs with Xen The root of the issue is the same in both cases: VLAN interfaces must *not* be

Hi, with reference to RH BZ#567540 [0], this patch makes the netloop module permanent (like netback is currently). It reverts parts of xen-unstable c/s 9019:271cb04a4f2b [1] [2] (though that has a typo: "__init clean_loopback", so it was probably changed later too). The patch fixes the problem of "rmmod netloop" hanging, resulting in blocked tasks and inability to shut down

Hello, I''m new to Xen (and this mailing-list) and facing some problems with the network. I''m stuck and don''t know how to continue. And Google isn''t very helpful either... My setup: - Ubuntu 7.10 for dom0 and Debian 4.0 for all domU - 4 physical NIC (DHCP from my ISP, internal LAN, DMZ & WLAN) - 1 Dom as firewall/router - 1 domU with internal services

Hello all, I would like to use two network interfaces. It is working but I notice that both bridges hace the same id. #brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif10.0 xenbr1

Hi, In one of our xen server, I am using two bonding. bond0 : Is for trunk, where the vlans are attached , port eth0 & eth1 is attached to bond0 bond1 : eth2 & eth3 are attached to bond1, where physical ip has been set . In the /etc/xen/xend-config.sxp, I am using (network-script *multi-network-bridge*) , the

Hello. The network-bridge script tries to automatically find the default network interface number with the following ligne: vifnum=${vifnum:-$(ip route list | awk ''/^default / { print $NF }'' | sed ''s/^[^0-9]*//'')} However, this fails on mandriva, because the parsed line is: default via 193.55.250.126 dev eth0 metric 10 This causes many troubles, such as:

Hello all, I have been running xen for a while now with two interfaces: dummy0 for host only communication, and eth0 for the outside network. my script looks like this: (/etc/xen/scripts/network-bridge-more) ------------------------------------------------------------------ #! /bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0

On 11/01/2017 07:55 AM, Scott Gennari wrote: > /etc/xen/scripts/network-bridge-pcl > > #/bin/sh > > dir=$(dirname "$0") > "$dir/network-bridge" "$@" vifnum=1 netdev=eth2 bridge=xen-dmz2 > "$dir/network-bridge" "$@" vifnum=3 netdev=eth0 bridge=xen-dmz1 Do you get any error output when you run: /etc/xen/scripts/network-bridge

Hi, I am facing issues after upgrading one of the server from rhel5.5. (86_64) to latest rhel5.7 (86_64). The server is under trunk configuraion. I have set the network bridge as follows: #!/bin/bash vconfig set_name_type DEV_PLUS_VID_NO_PAD dir=$(dirname " $0" /etc/xen/scripts/network-bridge $@ vifnum=1 bridge=xenbr2 netdev=bond0.10 /etc/xen/scripts/network-bridge $@

Package: xen-utils-common Version: 4.0.0-1 Hello guys, Ik running Debian stable (squeeze). I run a virtual pfsense firwall in a DomU. I created multiple bridges. The interfaces itself (except eth2 (connected to br_lan)) itself don't have a IP assigned. I use them to connect to other devices. grep my-network /etc/xen/xend-config.sxp (network-script my-network-script) root at

Package: xen-utils-common Version: 4.0.0-1 Hello guys, Ik running Debian stable (squeeze). This appeared in the messages when i started and stopped a DomU: root at dom0:~# cat messages Aug 31 22:04:52 dom0 kernel: [ 775.569937] device vif6.0 entered promiscuous mode Aug 31 22:04:52 dom0 kernel: [ 775.575993] br_lan: port 2(vif6.0) entering forwarding state Aug 31 22:04:52 dom0 kernel: [

Package: xen-utils-3.0.2-1 Version: 3.0.2-3+hg9762-1 Hi, while trying to get xen work, I encountered two problems: 1. I don't know if its really an error, but I think something is messed up with the subdir-name /usr/lib/xen-3.0.2-1 because the version-number of the package suggests that it is an other version, than the subdir says. Every time when I call xm for example I get: WARING!