similar to: network bridge empty

I''m using xen-3.0.3-64.el5_2.1 on centos 5.2. When I installed centos 5.2 at first time, I could see shared physical device (xenbr0). but after updating virtualization package by yum, it disappeared... connection.py is patched at centos 5.2 release time. so I can''t find out what''s wrong.... bridge configuration is below and it''s normal state.

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, I am trying to run Xen 3 on FC5, but I cannot have the eth0 interface appear in domU. I have 3 servers running FC3 and Xen 2 with various domUs since a year. Everything is fine on that front. I took one of the server, upgraded it to FC5 and did the following: - yum install xen kernel-xen0 kernel-xenU - grub.conf contains title Fedora Core (2.6.15-1.2054_FC5xen0 root (hd0,0) kernel

Hello ! I yesterday updated one server to XEN 3.2 which was running 3.1.2 before. The default bridge setup stopped working (Guests network packets were not forwarded to physical ethernet connection on eth0) My bridge setup looked like this: root@quadxeon2:~# brctl show bridge name bridge id STP enabled interfaces eth0 8000.003048359fc0 no

Hi, I tried already a long time to enable network in my domU but I always fail with: # ifconfig eth0 192.168.0.1 up SIOCSIFADDR: No such device SIOCGIFFLAGS: No such device Do I need to load a kernel module? I use OpenSuse 10.2 with kernel 2.6.18.8-0.5-xen (for both domU and dom0). My config: kernel = "/boot/vmlinuz-xen" ramdisk = "/home/jens/initrd.gz" memory = 1024 name

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

Hi I''m testing around with xen 3.0 snapshot from last week. And i''m now having a problem with a xenbr which is based on a vlan if (dot1q). this is all in dom0 os: debian testing network: tg3 I can start the bridge based on my normal physical eth0 which is working without any problems. My clan without bridge is also working. I can start the bridge based on a vlan if with help

Hi there! I am currently setting up a Xen box on 3 VLans, each VLan interface is in a bridge and currently, dom0 is reachable from on of these and is performing great. My only problem is with domU : it can ping anything but it won''t work for TCP and UDP protocol UNLESS I do a manual tcpdump on my vlan interface. Bridges on dom0: xen-vl97 8000.001372529fbf no

Hey All I''m Using Xen 3.0.3-105 on CentOS 5.5. It Has to Nics: eth0 - Internet eth1 - Internal Lan ( where Dhcp , DNs , Cobbler - Kick Start Server Resides ) I''ve Set xend-config.xsp to create xenbr1 on eth1 and it looks well So Guest May Get Access TO ALl Resources via the Bridge. brctl show bridge name bridge id STP enabled interfaces xenbr1

Hi, I have Xen 3.0.3 installed on CentOS 5.5 with 2 paravirtualized domU''s configured to use the default bridge networking and am having networking issues. If I boot the computer fresh I am able to ping dom0 and can SSH into it and start the domU''s. The following ping snippet demonstrates the problem. The first group of "Destination Host Unreachable" is while the

So Working on CEntOS 5 I am trying to sett up Xen with 2 bridges, one that connects dom0 and most of the domU to the physical card and the out to the network. Got that figured out no problem, now i want to have a second bridge that runs a local network for all the doms that doesn''t connect to the network. With code I have found used in multiple places I can easily get 2 bridges, and

Hi, I''ve installed xen 3.0.3 from packages (xen-linux-system) on a debian etch, and i''ve configured it with network-bridge script in the default way (netdev=eth0, bridge=xenbr0, etc...) which is ok for me. the problem I have: I cannot ping any outer machine from dom0 (nor any outer machine can ping me). It gives me a "Destination Host Unreachable" message that

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

Hello again, folks! I''m getting one strange problem with FC5 running on XEN 3.0.3 x64... The MRTG point to my machine with XEN running one absurd volume of output data sent (normal is around 6 MB/s) and when XEN is working we get 80 MB/s until my DRAC is alive... after this, the machine crash, DRAC stop do reply, swith stop do work together... Anyone knows whats happening now? ;)

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

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

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

Hi, [1] Are there guides for setting up a virtual switch for use in between guest domains in Xen ? [2] In Xen, is it possible for a guest domain to perform a initial dhcp IP lookup from another guest domain ? How are the configurations like ? Are there references or step procedures ? Kindly advice. Thanks. _______________________________________________ Xen-users mailing list

I am installed Xen 3.0 on a Fedora Core 4(2.6.12-1.1454_FC4xen0) machine. This machine is currently running one host domain: [root@]# xm list Name Id Mem(MB) CPU VCPU(s) State Time(s) Domain-0 0 128 0 1 r---- 49.1 fc4-vm1 1 63 0 1 -b--- 18.5 Following is the network configuration for Domain-0: eth0 Link

Hi all, my dom0 is centos5.2 and domU paravirtualized is centos5.1 I can play sound on dom0 but not in domU (name: gasphar), moreover I use wifi as my inet connection and on installing domU cento5.1, I used virt-manager. I know that libvirtd made virbr0 and when changing to xenbr0, I cannot connect to internet but ssh to dom0 is fine! so how do I enable sound device on domU and changing to