similar to: Patch for domU packet loss

Hi all, I have the following problem. A Linux box configured as a bridge. One interface connects to the router via a crossover cable, the other connects to a switch via the cable that used to go to the router. Now I get the following: [root@localhost net]# ifconfig eth3 eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D UP BROADCAST MULTICAST MTU:1500 Metric:1 RX

Hi, we''re running 4 xen servers on our network with multiple network cards. During HighLoad we experince degeneration of inbound network traffic through our loadbalancer. I might found a reason for it, in Dom0 dmesg output looks as follows: [1157421.975910] eth0: received packet with own address as source address [1157421.975957] eth0: received packet with own address as source

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''m running Xen 4.1.4 on Fedora 17. I have some CentOS 6 DomUs - an haproxy machine and some tomcat VMs. When clients send requests with: POST /ProposalInterface HTTP/1.1 Content-Type: text/xml Host: www.myhost.co.uk Content-Length: 2099 Expect: 100-continue Connection: Keep-Alive The "continuation" doesn''t happen. The POST is truncated at 1449 bytes, and the

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 -

Hi, I?m fighting with a silly problem: my syslog tells me tinc cannot route a packet. I can use a telnet or the good ol ping, it is the same effect. When I?m pinging from the laptop (172.16.11.2) the network address (172.16.11.0) or any address numerically lower than the laptops address, the packet gets routed, otherwise not. And when I ping the network address, I get the reply twice, as to be

Last problem I had involved changing one character in my configuration scripts. Really easy once someone showed me what was wrong. Well I think this issue is just the same. The moment I used apt to install the Xen kernal and tools I lost internet connectivity. I have been managing because I can restore connectivity be deleting the bridge mpower@dodtsair:~$ sudo ifdown eth0

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 All, We have a single Centos 5.11 server running a xen hypervisor that went down hard after an extended power outage this weekend. I'm mostly familiar for KVM as that is the majority of what our guests run under and have tried getting up to speed on xen bridging to no avail. The problem is that after the xen server spun back up, the previously defined xen bridges were lost. I've

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

greetings, following are command line problems as user using virtual terminals. ]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1419 errors:0 dropped: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

Guys, good afternoon I'm using in my bond interfaces as active backup, in theory, should assume an interface (or work) only when another interface is down. But I'm just lost packets on the interface that is not being used and is generating packet loss on bond. What can that be? Follow my settings bond [root at xxxxx ~]# ifconfig bond0 ; ifconfig eth0 ; ifconfig eth1 bond0

Hi all, we are testing CentOS 7 in order to migrate from Scientific Linux 6 / CentOS 6 and we are facing an issue with the network. Trying to configure network with teaming in activebackup mode or also with bonding in mode=1 (active backup as well) we see many RX dropped packets in the bond0 interface (around 10% of the total), 100% RX drops in the backup interface and 0% in the active interface.

I am currently running a Redhat Rel5 Dom0 with a solaris 11-66 xen domU as well as a Redhat REL4 domU. I am experiancing problems similary to those described the the Aug 2006 Release notes regarding ... Solaris domUs on non-Solaris dom0s 32-bit Solaris domUs should run on any 3.0.2-3 or later dom0. The majority of our testing has been on CentOS dom0s. 64-bit solaris dom0 and domU require updates

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

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

XenServer build date: 2010-11-30 XenServer build number: 39265p XenServer version: 5.6 Feature Pack 1 Guest OS: CentOS 5.6 Guest Kernel: 2.6.18-238.9.1.el5xen Hi everyone, we have set up several Xen servers with the version mentioned above. The version is the same on all servers, the kernel is the default one, not patches or self compiled versions. Each Xen server has 6 network interfaces (eth0

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'm very new with Xen (/Debian) I have 2 VMs running Windows: "Arch" and "Sql" -- static IPs VM Arch: is ok, accessible thru VNC, Remote Desktop, see the network, etc VM Sql : - just accessible thru VNC             - once I log in, I don't see the network             - pings don't reach peer             - appear 4 network ports on Windows the server has 4