search for: peth2

...external eth1 internal create bridge br0 for eth0 create bridge br1 for eth1 Strip IP addresses for eth0 and eth1 and assign to br0 and br1 respectively. Worked great in a non-xen kernel under Fedora 8 in KVM/Qemu. Booting into Xen, my eth1 becomes eth2, I also get an eth0.bak and an eth2.bak! peth2 is sort of explainable I would imagine. So I create a br0 bridge, give eth0 ip address 0.0.0.0 and give the original IP address to br0. Despite my ifcfg-eth2 having DEVICE=eth2 ONBOOT=yes BOOTPROTO=none HWADDR=5c:6c:c0:7d:1d:00 NETMASK=255.255.255.0 IPADDR=10.0.0.30 GATEWAY=10.0.0.35 TYPE=Ethern...

...peth0 xenbr1 8000.feffffffffff no vif0.1 peth1 xenbr2 8000.feffffffffff no vif0.2 peth2 xenbr3 8000.feffffffffff no vif0.3 peth3 xenbr4 8000.000d88cd4e6f no eth4 xenbr5 8000.000d88cd4e6e no eth5 It doesn''t create peth4 / p...

...peth1 vif2.1 vif3.0 xenbr2 8000.fefffffff002 no vif0.2 peth2 vif1.0 vif2.2 xenbr3 8000.fefffffff003 no vif0.3 peth3...

...g state xenbr1: topology change detected, propagating xenbr1: port 2(peth1) entering forwarding state root@bs-xen-p-01:~[0]# dmesg|grep xenbr2 xenbr2: port 1(vif0.2) entering learning state xenbr2: topology change detected, propagating xenbr2: port 1(vif0.2) entering forwarding state xenbr2: port 2(peth2) entering learning state xenbr2: topology change detected, propagating xenbr2: port 2(peth2) entering forwarding state root@bs-xen-p-01:~[0]# ifconfig shows eth[0-3], lo, peth[1-2], vif0.[1-2] and xenbr[1-2]. All interfaces up and running and have a link status. I fired up the VM, the VM start...

Hi, I was hoping someone on this forums could help me out with a problem I was facing with Xen. When I compiled the kernel for Xen-3.1.3 using "make world"(I know this is an old version but I need to use it for some compatibility issues), the kernel was missing the Xen netloop module. There was no /kernel/drivers/xen/netback/netloop.ko in the newly compiled kernel. I think we would

...web" (ID 3) to Domain-0 unless it does so via the physical ethernet interface. I have ensured that interweb(3) is on its own bridge along with the physical interface, eth2: xenbr2 8000.dab561626236 no vif0.2 peth2 tap2 vif3.0 Q4: If ebtables and iptables were both left open and un-configured, would the above configuration by itself be sufficient to isolate interweb(3) in the way I want? I am assu...

...t start vifnum=3 bridge=xenbr3 netdev=eth3 … These are the only things i configured. [root@sv-173 ~]# brctl show bridge name bridge id STP enabled interfaces xenbr1 8000.001a64358c26 no peth1 xenbr2 8000.001a643589d0 no peth2 xenbr3 8000.001a643589d2 no peth3 If i startup a machine like this: virt-install -f /data/machines/tmpl-centos.img -p -l http://url_to_image/centos/5/64/ --vcpus=1 -r 512 -b xenbr1 I got the following error after retrieving the initrd: virDomainCreateLinux() failed...

...it keeps going. If I startup any other guests, there is intermittent network problems and strange ssh connection failures. For example, one ssh client won''t connect while another one can. If I create another bridge from a single NIC via the same network-bridge script, like: eth2 -> peth2 -> xenbr2 Multiple guests can connect fine using xenbr2. I tried using the network-bridge-bonding script with bond0, but while it created pbond0, it never created the xenbr0 bridge for the guests to connect. Either I need to use the bonding script with additional parameters or steps to get th...

...6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1281 (1.2 KiB) TX bytes:1281 (1.2 KiB) peth2 Link encap:Ethernet HWaddr 00:26:b9:82:42:38 inet6 addr: fe80::226:b9ff:fe82:4238/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:178069 errors:0 dropped:0 overruns:0 frame:0 TX packets:421 errors:0 dropped:0 overruns:...

...inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) peth2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP MULTICAST 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....

Hello everybody, I''ve finished with pci export from DomU to Dom0 (Debian Etch) but now i have a new problem, and a big one. My ethernet card is dropping packets but after some time (i can''t tell how) It can work for a day (not in production so not hard tested) and then all packets are dropped. Look at the ifconfig output : eth0      Link encap:Ethernet  HWaddr

...6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:42 errors:0 dropped:0 overruns:0 frame:0 TX packets:42 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3480 (3.3 KiB) TX bytes:3480 (3.3 KiB) peth2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:556 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0...

I''ve just uploaded 0.9.11-pre12 of the GPL PV drivers for Windows. Since -pre10 (and -pre11) I''ve fixed a heap of crashes that were plaguing xennet under load, and also rewritten the interrupt/event distribution logic to improve performance. Under windows 2003 I can now get network speeds of 1-2Gbit/second TX and 600Gbit/second RX, which is considerably better than I was

I''ve just uploaded 0.9.11-pre12 of the GPL PV drivers for Windows. Since -pre10 (and -pre11) I''ve fixed a heap of crashes that were plaguing xennet under load, and also rewritten the interrupt/event distribution logic to improve performance. Under windows 2003 I can now get network speeds of 1-2Gbit/second TX and 600Gbit/second RX, which is considerably better than I was

Hi, I''m using Xen 3.0.3 on two servers with Debian Etch (amd64). These servers have 10 nics (2 onboard and 8 in two 4-port cards) so that every vm can have its own interface. This worked so far with the Xen Version from Etch with a wrapper script wich started 10 bridges at boot time. But now I''ve updated Xen on one of these server to Xen 3.2.0 from backports.org and now the