similar to: order of network interfaces in domU messed up?

Hi, I''m using Xen 3.0.3 on two servers with Debian Etch (amd64). These servers have 10 nics (2 onboard and 8 in two 4-port cards) so that every vm can have its own interface. This worked so far with the Xen Version from Etch with a wrapper script wich started 10 bridges at boot time. But now I''ve updated Xen on one of these server to Xen 3.2.0 from backports.org and now the

I added a virtual interface eth0:1 on one of my machines and suddenly networking breaks on startup of the system (eth0 is gone) when xend starts and runs the network-bridge script. This is supposed to be fixed according to: https://bugzilla.redhat.com/show_bug.cgi I checked and the network-bridge script contains this fix. It works fine on one of my PCs when eth0:1 is added, but not on this

Dear I need create second bridge xenbr1 for separate traffic between my virtual machine , I following this step but show message that Link veth0 is missing, how I can create veth0 ? When I run script for create xenbr1 ./network-bridge netdev=eth1 bridge=xenbr1 start Shwo this message Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

Hello, I have been playing with the XCP for a while now, and must say I''m very exited about the technology. I had no prior experience with Xen so it has taken me a while to understand the concepts, but now I feel most important issues are solved and I''ve purchased some hardware to build my (tiny) cloud on. The box is a Supermicro 1026TT-IBXF, so I have 2 x Ethernet and 1 x

Hi, I''m trying to set up networking on a new machine. I''m not getting any networking from the domU''s I notice that I have two bridges being created: xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:3024 errors:0 dropped:0

Hey folks, I created a DomU, installed Linux, and then realized I''d only given it 1 NIC so brought it down to edit the cfg file to give it another NIC. Originally I just had : vif = [''''] And so I guess the defaults worked for the 1 NIC. So I changed it to : vif =

I installed 64-bit xen 3.1.0 (from xensource.com tarballs) on three new machines today, using a configuration setup that I''ve used successfully many times before. However, I encountered a new problem. These are Dell Poweredge 1950 servers, by the way. >From lspci 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 12) 08:00.0 Ethernet

When I add all interfaces, the internet does not work.... eth0 = interneteth1 = lan ------------------auto eth0 iface eth0 inet static address 192.168.1.254 netmask 255.255.255.0 broadcast 192.168.1.255 auto eth1 iface eth1 inet static address 192.168.0.100 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.254 auto xenbr0 iface xenbr0 inet static

Hi! I have a problem with my new Xen setup. I have installed Debian etch with netinstall and I''m using 2.6.18-6-xen-amd64 kernel in my dom0 and 3.0.3-0-4 version xen hypervisor. I''m using four network cards on my system and using three of them as xen bridges and dom0 is using the fourth one only for it''s own. So basicly both of my virtual servers use a network card

Hi, I've been using CentOS & Xen on a server that has 2 VM's configured. The default configuration includes one physical iface that is propagated (by a default bridge) to the VM's. Since I wanted to configure additional physical iface, define a new bridge and propagate it to the viface-s of the VM's, i configured the bridge/phys. iface and brought it up (here are

I want to add the following route command route add -net 192.168.2.0/27 gw 192.168.2.3 via the normal network setup. The result should be the following routing table (the first line): 192.168.2.0/27 via 192.168.2.3 dev xenbr1 scope link 192.168.2.0/27 dev eth2 proto kernel scope link src 192.168.2.4 192.168.2.0/27 dev xenbr1 proto kernel scope link src 192.168.2.3 192.168.1.0/24 dev xenbr0

Hi, We have configured several xen guest OSes on a server running SLES10. The physical server is a Sun 4200 with 3 NICs installed, configured, and working. Each of the xen guest OSes have three virtual nics, configured for RAC, Interconnect, and public IPs as follows; eth0 - public (routable and registered in DNS) eth1 - private (not routable, uses a seperate network subnet for

Hi. I have another question, hopefully easier than my last: Do all physical interfaces in dom0 need to have an IP addresse in order to be used as a bridge by guest domains? I thought that the interface would have to merely be "up" but not necessarily have an IP address configured since bridging is done at layer 2. But alas, if I don''t configure an IP address on dom0 the bridge

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

As I received no response on the general CentOS list, I'll repost it here as the question is about Xen virtual machine routing. This is my network setup: http://pastebin.com/kyWpTQYU Lets assume my dom0's eth2 public ip is 1.2.3.33 and my dmz network 11.22.33.96/255.255.255.224 . I have created NAT from my LAN with iptables. You can see my /etc/sysconfig/iptables here:

Hi, I have taken the long and winding road and indeed it lead me to your door. I need your help, please. My Xen includes 2 guests. Xen itself (10.2.0.52) gets free access to the outside world and to its guests. Both guests however (10.2.0.54/10.2.0.55) see each other but stay under house arrest! Not a single ping manages to go past the bridge (xenbr0) and get an answer from the default gateway

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

I have a beefy machine (Intel dual-quad core, 16GB memory 2 x GigE) I have loaded RHEL5.1-xen on the hardware and have created two logical systems: 4 cpus, 7.5 GB memory 1 x Gige Following RHEL guidelines, I have it set up so that eth0->xenbr0 and eth1->xenbr1 Each of the two RHEL5.1 guests uses one of the interfaces and this is verified at the switch by seeing the unique MAC addresses.

Hi *, having built Xen 4.1.0 and running my Dom0 on Slackware 13.1, I''m trying to assign different physical network interfaces to different DomU guests: vif = [ ''bridge=ethX'' ] in the DomU configuration files. My /etc/xen/scripts/network-bridge script, however, doesn''t create more than one bridge: root@cen:~# /etc/xen/scripts/network-bridge start