similar to: network-bridge does not create veth or peth devices

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

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 _______________________________________________

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

Ben Greear wrote: > Well, it seems we could and should fix veth to work, but it will have > to do equivalent work of copying an skb most likely, so either way > you'll probably get a big performance hit. Using the same pktgen script (i.e with clone=0) I see that a veth-->bridge-->veth configuration gives about 400K PPS forwarding performance where

Ben Greear wrote: > Well, it seems we could and should fix veth to work, but it will have > to do equivalent work of copying an skb most likely, so either way > you'll probably get a big performance hit. Using the same pktgen script (i.e with clone=0) I see that a veth-->bridge-->veth configuration gives about 400K PPS forwarding performance where

Hi. I am trying to make initrd for xen0 but I am not successful. I receive error: #yaird error: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.16.33-xen0 evdev (fatal). If I do that just for xen kernel (not xen0) it goes without any problem. I guest I have to use initrd for xen0 otherwise it does not want to boot. Similarly, xen kernel without initrd will not

Hello all, I''m getting stucked with debian and Xen 3.0.2 Problem is that during boot with xen kernel system said: mount: unknown filesystem ''devfs'' and then Unable to open initial console /dev/console And reboot... How can I solve? googled for some information but nothing usefull.. Thanks Stefano -- Ste Visit: http://www.stefanocislaghi.it/

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

Hello *, I''m trying to 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

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

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.

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

Hi all ! It seems, that new kernel 2.6.24 offers new feature, that enables me to create pair of virtual Ethernet devices and connect them to each other. This module is called "VETH". However, I have not found any userspace app to use this feature. Please help ! -- -Alexey Eremenko "Technologov"

> On Friday 02 September 2005 17:58, Patrick 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: > > > >

On 3/13/19 2:26 PM, Martin Kletzander wrote: > IIUC, you are using the tap0 device, but it is not plugged anywhere. > By that I > mean there is one end that you created and passed through into the VM, > but there > is no other end of that.  I can think of some complicated ways how to > do what > you are trying to, but hopefully the above explanation will move you > forward

flight 22184 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/22184/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-winxpsp3 7 windows-install fail REGR. vs. 22106 test-amd64-i386-xl-win7-amd64 9 guest-localmigrate fail REGR. vs. 22106 Regressions which are regarded as

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Hi, I am using Xen 4.1.1 with Linux 3.0.1 kernel. Previously (Xen 3.4.4 and linux kernel 2.6.18) Xen by default created veth0 <--> vif0.0 pair in dom0. With Xen 4.1.1 these pairs are missing in dom0. Using command ''ip link add type veth'' I can create veth0 and veth1 but vif0.0 is still missing in dom0. (When new domU created I can see vif1.x created) Could you please help

Hi folks, I read quite some posts about "Destination host unreachable" problems before, but none could help me to solve my issue. So here we go: This is what I am using: SUSE Linux Enterprise Desktop 10 SP1 - Current with all updates Network configuration of my dom0: foobar:~ # ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd

Hi Team I'm trying to launch LXC VM with libvirt 1.2.12 having commit *22cff52a2b8e06c913b1f97767e5d3**90fb17fc3b *with below XML configuration.. <domain type="lxc"> <uuid>64c48da2-e318-4085-8b88-c980aab4de34</uuid> <name>test</name> <memory>524288</memory> <vcpu>1</vcpu> <os> <type