similar to: VM nic not taking IP address

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

Greetings! I finally got the install done for a couple of gust OSs (Win 2003 server & Suse Enterprise 10) Bothe gusts are up and running, but - no networking. My setup: Hardware - AMD Athlon 4200+, ABIT Motherboard, 4 GB of DDR2 RAM, 2 onboard GB NICs Host OS- Suse Linux Enterprise server 10 Xen - 3.0.2_09749-0.4 Config file for Win 2003 server guest: # -*- mode: python; -*-

I'm recording TCP network throughput performance between Dom0 IP stack and all my guest domains (currently 6 running simultaneously). All guests are running simultaneously, but I only ever transmit between Dom0 and one of the DomUs while the other five are idle. When running a netperf TCP_STREAM test (netperf on Dom0, netserver on DomU) I record the following performance numbers, CPU % as

Hi all, I just noticed that my two nics that are bonded via mode 0 are showing the same mac addy in ifconfig. Is this normal? In syslog I keep getting; kernel: pbond0: received packet with own address as source address Some guidance is appreciated before I dive in and troubleshoot. If I don't list the mac addy in my ifcfg-th# files, only one of the 2 nic comes up during boot.

Dear, I''ve attempted to upgrade a Xen box from 3.1.2 to 3.2.1. Unfortunately it has been a partial success only. At this point I''m really stuck with a network problem that affects my HVM machines (Linux PV run fine). The really odd thing is that everything seems to work properly, except that the "vif" network interfaces in dom0 seem to have only dropped TX packets for

Hi Folk, My BOX is running Debian Sarge. i recently setup a bridge with two NIC's for transparent proxy. However something weird i found as listed below when i run ifconfig. So just curious to ask why the hardware address of "br0" is the same as "eth1", it's supposed to be the same as "eth0"...normally. Should this cause a probelm with the bridge?? If so how

Hi all, I have a very strange situation, which I can''t explain. On a Core 2Quad server with 8GB RAM, we have 10 xen domU''s, as follows: vps.animalsaregreat.info login: root@zaxen01:[~]$ xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 512 4 r----- 232.2 actionco.vm

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

Greetings, I have two vms, one is a router and the other one is a client, for some reason, the client vm is unable get ip via dhcp from the router vm. here are outputs: vm1.xml: <interface type='bridge'> <mac address='52:54:00:54:78:be'/> <source bridge='virbr0'/> <model type='virtio'/> <address

I am running Fedora 16 64bit and installed libvirt. I have the VM running with arm emulation with this one issue I can't figure out. I used Virtual Machine Manager to manage the VM and can access its console there. The Ethernet appears to be eth1 and the guest can set an IP on it etc. However, I cannot see any traffic from the Host when dumping any of the interfaces. I've tried

Hi, I tried this post on the Xen list first with no answer. I have 4 machines and 3 of which (all different) have no network access when booted into Xen. I tried using Fedora Core 8 and it produced the same results. Is it normal for the virbr0 interface to take an arbitrary IP? How does it decide what to use? An ifconfig when booted into Xen shows the following: eth0 Link encap:Ethernet

TEQL and Subnet problem I have a network topology shown below, and I am trying to use TEQL. My problem is: When I ping to P3.teql0 from P2 ("[P2]# ping 16.119.144.66"), the traffic can never go from P2.eth1, and all traffic only goes to P1.eth0. What P2.eth1 (16.119.144.33) did is broadcasting an ARP asking for the MAC address of 16.119.144.66, although I have specified the route to

Hi, I hope someone could help me out. Pls find the details below. dom0: ifconfig before "xend start" eth0 Link encap:Ethernet HWaddr 00:0C:76:53:44:FB inet addr:10.0.0.3 <http://10.0.0.3> Bcast:10.0.0.255 <http://10.0.0.255>Mask: 255.255.255.0 <http://255.255.255.0> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX

dummy0 Link encap:Ethernet HWaddr C6:C8:2A:04:FD:23 BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX

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

Hello. I need your help, DomU xen network diconnects randomly, how do you monitoring this? When I connect to vnc server in the hosts, DomU is running, then I open the DomU, after that guest network responds. DomU Debian 6.03 over Centos 5.7 and Xen 3.03. My network configuration: eth0 Link encap:Ethernet HWaddr 68:B5:99:78:AA:6D inet addr:192.168.5.230 Bcast:192.168.5.255

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

Well where do I start...I have a domU (ubuntu) booting and appears well but I don''t have an eth0 listed at all, dom) looks good. DomU: eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B inet addr:10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248 inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Hello, I have problems with installation of my second DomU. I cannot ping it from the outside world and I cannot access outside world from this domain. I see it from Dom0 and my first DomU, same as my second DomU can ping Dom0 and my first DomU. I use xen 3.0.3 on ubuntu 6 LTS. DomU is running on debian. I also network-bridge script in the xend config.

I am posting the message below again because it did not go through last night. Help! Steve Timm -- ------------------------------------------------------------------ Steven C. Timm, Ph.D (630) 840-8525 timm@fnal.gov http://home.fnal.gov/~timm/ Fermilab Computing Division, Scientific Computing Facilities, Grid Facilities Department, FermiGrid Services Group, Assistant Group Leader.