similar to: No shared physical device in virt-manger on centos 5.2

My very first xen DomU can not ping anything on my network. Well that is not entirely true, it can ping itself. I did not touch any of the scripts in /etc/xen so xen should be using bridging. My pc is running xen-unstable and uses a 3Com PCI 3c905B Just after the ''xen start'' on Dom0 brctl shows: bash-3.00# brctl show xenbr0 bridge name bridge id STP

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

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

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

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

Hi, We are planning to upgrade our dom0s from CentOS5.0 to CentOS 5.2, using the xen version shipped with the OS : the RPM versions are respectively 3.0.3-25.el5 and 3.0.3-64.el5_2.1, I don''t know exactly to which version of Xen it corresponds (but it should be further than 3.0.3, right ?). Kernel versions are resp. 2.6.18-8.el5xen and 2.6.18-92.el5xen. As we want to avoid any

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" "$@"

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

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? ;)

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

Before starting xend (xen 3.0) these are my correct network interfaces: eth0 Link encap:Ethernet HWaddr 00:14:5E:0A:53:04 inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 eth1 Link encap:Ethernet HWaddr 00:14:5E:0A:53:05 inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0 lo Link encap:Local Loopback inet

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

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, [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 tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

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

Hello. I have installed the SuSE Linux 10 XEN kernel but no domU yet. Now I cannot ping to and from dom0. I get lots of ARP broadcasts from dom0 but dom0 seems to ignore ARP answers. When pinging to dom0 it ignores arp requests. This happens regardless xend is running or not. This happens in the xen kernel only, when booting stock kernel all works as expected. What can I do? Robert

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''m using Fedora 7 with xen''s virt-manager. I''d manage to install a full virtualized WinXp domU after changing the settings in .xml files. Now I would like to try to install the paravirtualize fedora 7 using virt-manager I''m using this install media address > http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/ And the virt-manager console