search for: peth

-------- Original Message -------- Subject: Re: [Xen-users] network-bridge does not create veth or peth devices Date: Wed, 28 Nov 2007 14:42:25 +0100 From: Ingard Mevåg <ingardm@startsiden.no> Organization: ABCStartsiden To: Luciano Rocha <strange@nsk.no-ip.org> References: <474D6492.5030807@startsiden.no> <20071128130205.GA1838@bit.office.eurotux.com> Luciano Rocha wrote: &...

Hi I reached the conclusion that my networking problem stems from the fact that I have no peth0 device. I''m trying to locate what creates the device, but until now no success. So I have a simple question: What creates the peth0 device in dom0? TIA Paolo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensourc...

...he default Xen boot option # xenhopt=dom0_mem=512M com1=9600,8n1 vcpus=1 ## Xen Linux kernel options to use with the default Xen boot option # xenkopt=console=tty0 maxcpus=1 console=ttyS0,9600n8 update-grub ----- after a reboot everything looks just fine, except: ifconfig shows only a xenbr0, no peth or veth.. The network works, creating a guest with xen-tools works, however the bridging is weird: ----- $brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.00188b82f742 no eth0...

>[root@localhost ~]# /etc/xen/scripts/network-bridge start > >Device "static" does not exist. > >usage: ifdown <device name> > >Device "static" does not exist. > >Cannot find device "static" > >SIOCGIFFLAGS: No such device requirements: - Interface (eth1) must be "up". (ifup eth1) (setting "ifconfig eth1

...i done brct show i have this : bridge name bridge id STP enabled interfaces bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 xenbr1 8000.feffffffffff no vif0.1 peth1 xenbr2 8000.feffffffffff no vif0.2 peth2 xenbr3 80...

...setup Shorewall under Ubuntu 7.04 and Xen configured to use network-dummy instead of network-bridge (network-bridge seems to be buggy at the moment under Debian/Ubuntu). Is there a shorewall config example I can use in combination with network-dummy? In particular, with network-dummy there is no peth interface and the bridge include the real eth interface. I tried to configure Shorewall by myself but i cannot match any situations so I have to open all to all :( -- Davide Corio davide.corio<at>redomino.com Redomino S.r.l. Largo Valgioie 14...

Hi Group ... havin'' read whatever I could "google" on this topic, I didn`t find any solution: openSuSE 10.2 (out of the box), xenkernel, running on HP Proliant DL360G5 (dual internal networking, plus additional 4-port adapter) gives me eth0 - eth5, but only peth0 - peth3 (as well as vif0 - vif3 and consequentely xenbr0 - xenbr3). I increased the number of loopback-devices to 64 ... no result Whenever I try to "/etc/xen/scripts/network-bridge start vifnum=4" I get a message regarding to a "nonexisting veth4" ... What am I missing T...

...--physdev-in vif1.0 ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif2.0 Chain OUTPUT (policy ACCEPT) target prot opt source destination foobar:~ # depending on of the domU''s are started or not. What I found strange, is that a peth isn''t displayed at all in my ip a output. Is this the result of renaming the eth devices while setting up vethX? I saw also in some posts that xenbr0 was assigned an ip address. Tried that as well and also set a routing entry for it but my domU''s don''t wanna talk to the o...

...;'Rourke wrote: > > The network device on our hardware uses a rather large MTU (~16k), but I > > noticed that when setting up bridging, the MTU for the bridge and veth > > device is set to 1500. Trying to set the MTU on the bridge, or eth > > device to match that of the peth is unsuccessful: > > > > [root@por-hv-proto3-p4 ~]# ip link set eth0 mtu 16896 > > SIOCSIFMTU: Invalid argument > > [root@por-hv-proto3-p4 ~]# ip link set xen-br0 mtu 16896 > > SIOCSIFMTU: Invalid argument > > > > We''re using xen-unstable, but a v...

...alling in Dom0. I have a question: Dom0 sees al the interfaces, not just those considered its "own" ones. So should I set up firewalling to use/protect only Dom0''s own interfaces, leaving individual firewalls to DomUs, or should I set up firewalling on the physical interfaces (peth*)? To make things a bit worse I'' using bonding, where I currently see a bond0, but no pbond0 ;-) I haven''t investigated yet whether the default scripts do what they are supposed to do. I''m using the description in http://www.novell.com/coolsolutions/feature/17605.html...

...;'s pinned to particular cores? as an example, i''ve got a dual quadcore xen system running with domU pinned to cores 1-3 (CPU#0) domU pinned to cores 4-5 (CPU#1) domU pinned to cores 6-7 (CPU#1) so dom0 should have 100% time on core 0 (CPU#0). When looking at /proc/interrupts, all peth and arcmsr (areca raid) interrupts - said: all IO - are handled by CPU0. Should i use irqbalanced to use other cores as well? Any suggestions are really welcome! Thanks in advance. Stephan -- Stephan Seitz Senior System Administrator *netz-haut* e.K. multimediale kommunikation zweierweg 22...

Hi, I am using the latest unstable and when I boot my xen, I do not see any veth devices. This happens even after I start xend. Xend gives this message on a "xend start" SIOCSIFNAME : Device or resource busy Presumably the creation of veth and peth is failing because of this. Any suggestions -Padma _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...om/archives/html/xen-users/2006-04/msg00186.html And I think I have found the reason, why the described problems happen: In a normal xen setup, network looks like this: domU (say ID=1) sees eth0 this eth0 is represented as vif1.0 in dom0 and connected to xenbr0, which goes "out" through peth0 brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 vif1.0 Neither xenbr0 nor vif1.0 no...

...promiscuous mode kernel: audit(1165827245.987:2): dev=vif0.0 prom=256 old_prom=0 auid=4294967295 kernel: xenbr0: port 1(vif0.0) entering learning state kernel: xenbr0: topology change detected, propagating kernel: xenbr0: port 1(vif0.0) entering forwarding state kernel: ADDRCONF(NETDEV_UP): peth0: link is not ready kernel: bnx2: peth0 NIC Link is Up, 1000 Mbps full duplex kernel: ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready kernel: device peth0 entered promiscuous mode kernel: audit(1165827249.211:3): dev=peth0 prom=256 old_prom=0 auid=4294967295 kernel: xenbr0: port 2(peth0)...

Hi I have an Asus M2N32 WS Pro, 4G Ram, AthlonX264 4600+. I Installed SuSE 10.3 (64bit) on Dom0, LVM on Raid 5. All domU''s boot off LVM, using same Suse 10.3. I have a firewall (fw) domU running shorewall and a domU name-dhcp-server (nds). Somewhere in between 10 and 16 hours the network stalls. In dns, I can see dhcp queries and offers, but these never make it to the clients in the

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

Hello, I use xen for a few months now and I upgraded to opensuse 10.3 with xen 3.1 (64bit versions) recently. Everything works fine, but there is a problem when I change xend-config.sxp to use my own network script (it''s slightly modified version of network-virtual scripts from http://en.opensuse.org/Xen3_yet_another_Virtual_Network_Concept ) instead of default network-bridge script.

...lowing packages: o Xen version 3.1.0-rc7-2950.fc8 (kojibuilder@(none)) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-32)) Tue Oct 23 12:21:08 EDT 2007 o xen-3.1.0-13.fc8 o kernel-xen-2.6.21-2950.fc8 The error message the kernel gives me is the following: Nov 16 14:38:31 xen2 kernel: NETDEV WATCHDOG: peth0: transmit timed out Nov 16 14:38:31 xen2 kernel: sky2 peth0: tx timeout Nov 16 14:38:31 xen2 kernel: sky2 peth0: disabling interface Nov 16 14:38:31 xen2 kernel: sky2 peth0: enabling interface Nov 16 14:38:31 xen2 kernel: sky2 peth0: ram buffer 48K Nov 16 14:38:31 xen2 kernel: eth0: port 1(peth0)...

...br0 ifup eth0.100 ifup eth0.200 ./network-bridge start vifnum=1 netdev=eth0.100 bridge=xenbr100 ./network-bridge start vifnum=2 netdev=eth0.200 bridge=xenbr200 One more note: to use it in startup scripts, I had to put a couple of "sleep" commands between each line - otherwise, some peth/pbond interfaces were missing sometimes. -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...br0 ifup eth0.100 ifup eth0.200 ./network-bridge start vifnum=1 netdev=eth0.100 bridge=xenbr100 ./network-bridge start vifnum=2 netdev=eth0.200 bridge=xenbr200 One more note: to use it in startup scripts, I had to put a couple of "sleep" commands between each line - otherwise, some peth/pbond interfaces were missing sometimes. -- Tomasz Chmielewski http://wpkg.org _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel