similar to: Xen with 2 eth interface

Hi, I would like to ask concerning problems after installing xen 3.3 on Centos 5.2 I use 2.6.18.8-xen (xen3.3.1 testing - installing with mercurial). After done with make world and make install, I did mkinitrd and placing it in /boot changing the grub and reboot.. succeded I do not install libvirt and the domUs from the previous xen 3.0 (built-in Centos 5.2) are NOT able to start : [root@wing

Hi all, I have a strange problem with GPL PV 0.8.8 (0.6.4 did work). On my 2nd vif I cannot establish TCP connections. The 3rd IP packet (ACK from XEN-Image) is not forwarded by XEN/DOM0-Bridge. If I boot Windows without /GPLPV option, everything works fine. I did some investigation and found out that the packages arrive differently if GPLPV is enabled. "br_inet" is a bridge

Hi list! I''m trying to figure out a way to use network configuration scripts provided by the distribution to manage network/bridge configuration with xen.. This means I dont''t want use xen "network-bridge" (or any other) script at all, because they are a bit limited in functionality. I want to setup VLAN interfaces with the scripts/tools provided by the

Hi *.*, This is a continuation on the 2 NICs thread after some more testing. Just to remember my goal. --------------------------- I want to create a domU with 2 virtual NICS. One of them will contact the outside world, the other one will contact a VPN. No reason in concrete for choosing the bridging protocol, only because its the default one. I installed the dom0 with the 2 NICs active, with

Hi, I found this mail about network problems in the archive. I think I have the same network problems with a routing (with or without NAT) domU connected by two network bridges. The dom0 logs thousands of following messages: -- Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet -- and all outgoing TCP packets have wrong TCP checksums (traced on another machine on the

If you get a lot of those messages and you don''t want them: peth1: received packet with own address as source address or peth0: received packet with own address as source address This is the way I found to solve this problem on Debian maybe someone can post more information about other distribution like suse or redhat... This problem will occur if you have more than one dom0 on your

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! 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

Situation peth0 = internet peth1 = local private network Dom0 is only configured to use peth1 and works fine as such I have a DomU setup as a NAT box for the local network to the internet and it is functioning as well. DomU is also running a caching DNS and DHCP for the local network The problem I have is DomO''s gateway is set to the local network IP of the DomU, as is

I have seen those documents, I did not see anything that indicates how _automatic_ bridge configuration could be enabled with xl. For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> peth1). If I have to configure this manually with ifcfg scripts I will, but if an automatic method is provided or is possible with xl I'd prefer to use that. -Gene On Thu, Jan 29,

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 -

> That''s great, except when you need *two* bridges, for two > independent subnets, and there is no, as far as I can see, peth1. You can have multiple vethX interfaces on recent builds -- see netback/loopback.c. I think the current default is a rather miserly 1 (and should be increased), but can be set on the command line. Ian > Em Wednesday 14 September 2005 16:30, John

Hallo, I have running xen-4.2/linux-3.8 (compiled) on any hosts. - dell pe r720: drac, eth0-3:igb squeeze -> boot_xen:ok net:ok bridge:ok - dell pe R620: drac=eth0, eth1-3:tg3 wheezy -> boot_xen:ok net:ok bridge:fail So i running "xend start" (or "xenbridges start") on my patient (R620 with broadcom tg3) network will be lost: RTNETLINK answers: File exists

Hello Everyone, I have set up a xen server with 10 physical network devices using the bridge mode of XEN. This is because I want to split and separate the network traffic for security reasons. Maybe the best way is to use pci back hide. But I want to understand what is going on here. For all testings I have only activated eth[0-3]. My first tests were successful. I have created a VM using

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

I have a OpenSuse 10.3 with xen 3.1.0 running and it''s been running fine for a few months. This past weekend it suddenly started to act up and after some troubleshooting I can now say that it seems like the guests(domU) loose the outgoing network pipe, from the console I can see that the TX counter is stuck at the same value but it''s no errors. It behaves as if whatever I try to

We have been using Xen as our vm only recently (about a year now). We recently started to look at the tcp flow control that is coming in and out of the VM. Our configuration is that a physical interface on the host, peth1, is connect to vif1.1 by bridge br1, vif1.1 is instantiated as eth1 inside the vm. We have a data source attached to eth1 that over subscribe the data capacity of peth1.

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

think i posted in the wrong ml the first time, sorry, reposting here hi, i recently updated to xen 3.2 and now networking has stopped working. i have a configuration with 2 nics: eth1 (internet) and eth0 (lan) when i start xen i get peth0,peth1 with no ip, and bridge eth0,eth1 with the right addresses the server running xen is also the lan gw the routing table seems ok 192.168.0.0 *

Hello all, I would like to use two network interfaces. It is working but I notice that both bridges hace the same id. #brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif10.0 xenbr1