similar to: eth0 not found in Suse Enterprice Server 10

Hello All, I'm trying to figure out why xen-utils-common 3.2 doesn't suport bridging on multiple interfaces. I've been digging around /etc/xen/scripts/network-bridges. And modified it so that during boot, when executed the script writes into /tmp/netbr file, but I commented out code that actually creates bridges. I discovered that this script is called three times during boot, I

Hi, This is my setting: I have a Logical Volume /dev/VG/suse with Suse installed. I have added it to the grub and I can boot it and works perfectly fine. Now I am running /dev/VG/root which is running Xen0. I have created a Xen config file to boot a VM with disk: /dev/VG/suse. In other words I want to boot /dev/VG/suse as a virtual machine. Below is what I am getting at boot time :

I have a domU configured with two virtual ethernet interfaces - one on a private bridge and one to the outside world. If I cat /proc/net/dev (or loop round the interfaces using SIOCGIFNAME) there are loads of them? Should they all be there ? I''m using the same kernel for dom0 & domU. Inter-| Receive | Transmit face |bytes

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

Dear Xen-Users, I use Xen 3.1.0_15042 on my OpenSuSE-10.3-computer. Without starting the xen-kernel I can connect my second computer via my native computer to the internet. After starting the xen-kernel the xen-bridge came automatically up. How can I configure the xen-bridge or the xen-devices? I get routing problems: Feb 20 18:31:36 intel6550 kernel: martian source 217.237.149.142 from

Hi! I''m not new to Xen but I''m new to this list. I''m having a truely bizarre problem with Xen bridged networking at the moment. This is a new install, on RHEL4. The symptom is that any domU set up simply fails to talk to anything else. It''s there, and running, and it has an ethernet device, but there''s never any response. After digging through the

I can''t find network device in domU. Debian domU shows Configuring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device and Fedora domU shows: eth0: unknown interface: No such device Dom0 is using Fedora with: kernel-xen-guest.i686 2.6.15-1.29_FC5 installed kernel-xen-hypervisor.i686

I installed Ubuntu Feisty successfully, then I configured the network (static IP) and things worked well. Then I installed Xen using "apt-get install ubuntu-xen-desktop". I could boot the xen kernel, and booted succesfully to dom0, however, there''s no network for dom0. According to network manager, I saw that Ubuntu recognizes now 4 unconfigured adapters (veth0, veth1, veth2,

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd

Has anyone ran into this issue before? 2 physical nics: eth0 hooked up to 10.175.8.0/21 eth1 hooked up to 10.150.8.0/24 Ifconfig -a looks like this: [root@mgixen1 ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:19:B9:F2:1B:C3 inet addr:10.175.8.158 Bcast:10.175.15.255 Mask:255.255.248.0 inet6 addr: fe80::219:b9ff:fef2:1bc3/64 Scope:Link UP

Hello, A bit of history ================ 1) I''ve got a normal 2.6.20 x64 Fedora 6 Linux server running several things 2) I''ve downloaded and installed the XenSource Administrator Console for Windows 3) I''ve added 2.6.20-1.2962.fc6xen kernel, xen and vnc packages on my Linux server 4) I rebooted the Linux server, and started xend as per user guide Configuration

Hi, I have a strange problem with my networking setup. I read all forums around the world where people had similar problems, but couldn''t find a solution. I have an Attansic L1 gigeth chip on my mainboard. This chip works OK in stock Ubuntu Gutsy (development) 2.6.22-9-generic kernel. When I boot into Xen, and after the bridge is created, the network stops working. Some info: - If I

I''ve setup Xen 3.0.2-2 (binary install) on Ubuntu 6.06, got my domUs up and running, got them connected to the Internet but I can''t even ping to any of these VMs. Now I''m not linux/xen genious but could the problem be that xen-br0 doesn''t have an IPv4 address? (it''s got an IPv6 address) Since I don''t use IPv6 on my network this seems a

Hi all, Has anyone seen this before? I''m running a CentOS 5.3 with xen 3.0 and the server has been running fine for a long time. In fact, it was up for 186 days before I had to reboot after the "network died", and I couldn''t fix it. The server has multiple domU''s on it, which all still works when the host node (dom0)''s network dies with these

I just did a fresh install of centos 5.0 from cd, followed by yum update which installed 399 packages. No failures or errors that I can see. I have three nics in the box, but am only setting up one at the moment. The box can ping others in my network, but if I try ssh, telnet, ftp, etc I get this: [root at cm network-scripts]# ftp watchdog ftp: connect: No route to host ftp> [root at cm

Hi, I got this error when starting a domU on Centos 5.1 i386, Device 0 (vif) could not be connected. Hotplug scripts not working. Why is this happening ? I should restart the machine to see if this still happends after a fresh network bridge. But it's somehow a production server, I would like not to restart it, if possible. No domU is currently running. I could start domUs a week ago.

Hello, Since my last update of xen, I am having problems with bridges and xen. When I want to start a bridge on the dom0 (to run a domU in a different vlan than the default) I run /etc/xen/scripts/network-bridge start netdev=eth0.302 bridge=xen-br302 antispoof=no where eth0.302 is an interface associated with my vlan 302 (it tags with this vlan identifier). The problem I have is that it

Hi, I''ve setup a box with xen. For the root machine, it''s ok, it see the network card: alian@yoda:~> /sbin/lspci ... 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 Gigabit Ethernet Controller (rev 19) alian@yoda:~> lsmod .... sk98lin 208748 1 alian@yoda:~> /sbin/ifconfig eth0 Lien encap:Ethernet HWaddr 00:15:F2:39:D4:DF

Ben Greear wrote: > Well, it seems we could and should fix veth to work, but it will have > to do equivalent work of copying an skb most likely, so either way > you'll probably get a big performance hit. Using the same pktgen script (i.e with clone=0) I see that a veth-->bridge-->veth configuration gives about 400K PPS forwarding performance where

Ben Greear wrote: > Well, it seems we could and should fix veth to work, but it will have > to do equivalent work of copying an skb most likely, so either way > you'll probably get a big performance hit. Using the same pktgen script (i.e with clone=0) I see that a veth-->bridge-->veth configuration gives about 400K PPS forwarding performance where