similar to: Error: Device 0 (vif) could not be connected. ip addr add 10.0.0.329 dev vif28.0 failed

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

Hello, There is a xen setup in which "brctl show" gives the following output. bridge name bridge id STP enabled interfaces eth1 8000.003048c9d4df no peth1 vif1.0 vif2.0

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

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

Here is the situation. I have a xen system with 2 drives setup in a RAID1. I pulled one drive and put it into an identical server. Now, when I boot up the new server, peth1 is not created. [root@dom0 ~]# ifconfig | grep Link eth1 Link encap:Ethernet HWaddr 00:14:38:A7:55:C2 inet6 addr: fe80::214:38ff:fea7:55c2/64 Scope:Link lo Link encap:Local Loopback vif1.0 Link

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, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

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, 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''ve tried again Debian testing, with xen 3.1 binary. it works fine but i can''t have the networt working: i''ve have an ethernet card with static IP: 172.20.2.160 gateway: 172.20.2.1 uname -r :2.6.18-xen without xen, the network works fine. here''s my output: eth0 Lien encap:Ethernet HWaddr 00:0F:FE:6B:57:32 inet adr:172.20.2.160

Hello everyone. I just installed Xen 3.0.3 in a debian etch box. Linux server1.example.com 2.6.18-6-xen-686 #1 This server1 has two real nic (eth0 with real MAC 00:13:72:57:7B:AE and eth1 with real MAC00:13:72:57:7B:AF). I made a network-bridge custom like this: ----------------------------------------------------------------------- #!/bin/bash dir=$(dirname "$0")

Hi I installed xen by following this link: http://www.howtoforge.com/virtualization-with-xen-on-debian-lenny-amd64 Dom0(debian) has two IP :174.x.x.79 , 67.x.x.32 gateway is 174.x.x.65 DomU(win2003) IP is :67.x.x.38 The problem is : 1.weird network issue in win2003(can not access the internet in win2003): A:weird ping time for 127.0.0.1 B:weird ping time for its own ip 67.x.x.38 C:timeout

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 ''ve got a CentOS 5.2 server running xen 3.0 with 2 DomUs also running CentOS 5.2. All my boxes are up-to date. I''m experiencing trouble with networking. Dom0 can reach the outside world when no DomU are started. It can also reach the outside world when only one DomU is running. The troubles begin when I start the second DomU. At first, this new DomU, called DomU2,

CentOS 5.5 Xen "standard" Xen Installation. I have two nics. I just put the second one to DHCP and modified the ifcfg-et01 and so far I am holding, but I am not confident. Prior they were sequential IP Addrs on same subnet. arpwatch has indicated flip flips. I can find no rhyme or reason to predict them. I know I missed I must have missed a step somewhere. I want to keep the

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

Hello everyone, I have been able to get windows xp to run under a virtual machine, but i cannot get any network access. My desktop is connected to a university network, and we are only given 1 ip address. so i understand i have to use routing instead of bridging, right? i have commented the two lines for bridge and enabled routing in /etc/xen/xend-config.sxp next i inserted a line: vif

Hi, I have 3 xen box with 2-3 VM on each. Each server has 2 nic (1 for external and 1 for internal network). All VMs are webserver and they mount a nfs filesystem. I''ve noticed that on each dom0 there are many dropped packets. Server config is: 1- DELL (2xQuad Xeon E5320 @1.86Ghz - 8Gb Ram - Perc5 - Kernel 2.6.18-6 (debian etch)) 2- DELL (2xDual Xeon 5110 @1.60Ghz - 4Gb Ram - Perc5 -

I have a server running Centos 5.2 as a Xen host. A problem that's shown up recently is that at boot, the dom0 interface eth0 doesn't come up properly, with the result that the host is only accessible via remote console. If I execute 'service network restart', eth0 comes up normally, with an IP address and the correct routing. Three guests have been created via virt-manager

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