search for: netloops

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

Package: xen-utils-common Version: 3.0+hg11292-2 Severity: normal After a recent etch upgrade (2.6.17, xen-3.0.2) I was unable to "xm create" until I "modprobe netloop nloopbacks=10" Error was network-bridge couln't create vif interface (backend not found). brctl addbr ... fails because of no free netloop device. passing more nloopbacks device to the module fixed the

Hi list, since release 5.3 all kernels ignore options netloop nloopbacks=<n> within /etc/modprobe.conf If <n> is smaller than four there are always four vifs created. If <n> is bigger than four the appropriate number of vifs are created. Is this expected/new/feature/bug? Henry

Hi, with reference to RH BZ#567540 [0], this patch makes the netloop module permanent (like netback is currently). It reverts parts of xen-unstable c/s 9019:271cb04a4f2b [1] [2] (though that has a typo: "__init clean_loopback", so it was probably changed later too). The patch fixes the problem of "rmmod netloop" hanging, resulting in blocked tasks and inability to shut down

Hi, I''m playing with xen from a couple of weeks, all standard configurations work fine within my suse box. But trying to become closer to the xen philosophy I can''t understand the issues which drown developers to use netloop module instead of the tap one. thank''s in advance _______________________________________________ Xen-users mailing list

Hi all, I recently change my Xen 3.1 for a 3.2 and I discover I have to set IP address on bridge rather than on virtual interfaces. I used to use bridge set on dummy interface to create virtual networks (not vlan) inside my Xen system. Without IP on it bridges can be consider as a hub. dom0 can be outside of these virtual networks. With IP on bridge, dom0 will exists on these networks, and I

It appears that this bug is caused by the netloop kernel module not being automatically loaded. xn

Package: xen-utils-common Version: 3.0+hg11624-2 Severity: normal I'm running etch with xen 3.0.3 with a hand-compiled 2.6.18.1 kernel. The /etc/xen/scripts/network-bridge fails to run, because it (effectively) does this: set -e modprobe netloop > /dev/null 2>&1 As I do not have a netloop module (where is it supposed to come from ? The 2.6.18.1 xen-patched kernel doesn't

I tried netperf / netserver with Dom0 / DomU, but I could''nt get a correct NW traffic with xentop. Is there anybody could help me? At Host1''s Dom0, run netperf -H VMIP At Host2''s DomU (with VMIP named TTVM), run netserver At Host1, run xentop this way ->"xentop -n -b -d 1" At Host2, run xentop this way->"xentop -n -b -d 1" In Host2''s

Package: xen-utils-3.0.2-1 Version: 3.0.2-3+hg9762-1 Hi, while trying to get xen work, I encountered two problems: 1. I don't know if its really an error, but I think something is messed up with the subdir-name /usr/lib/xen-3.0.2-1 because the version-number of the package suggests that it is an other version, than the subdir says. Every time when I call xm for example I get: WARING!

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

Hello, I have got something strange when I done a /etc/xen/scripts/network-bridge status : 201: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:15:17:8d:cb:1c brd ff:ff:ff:ff:ff:ff And when I done a /etc/xen/scripts/network-bridge I have got this : Link veth0 1 is missing. This may be because you have reached the limit of the number of

The FAQ says to use loopback.nloopbacks to limit the number of vif''s and veth''s that show up in dom0. This no longer appears to work. Has this been remove with no replacement or has this just changed and the FAQ hasn''t kept up? -- Jason The place where you made your stand never mattered, only that you were there... and still on your feet

Hi, I''m trying to install xen with this configuration: dom0 -> Centos 5.3 dom1 -> Fedora 10 dom2 -> Fedora 10 Centos kernel = (2.6.18-128.1.10.el5.centos.plusxen) XEN Version = 3.0.3 I''m having some problems trying to install xen on my mychine, but i''ve been able to solve all of them but one: i can''t reach my gateway from

Hi! I am trying to export a PCI device (an AVM Fritzcard PCI ISDN card...) to a domU but when starting my domU I am getting this error: "pciback pci-4-0: 22 Couldn''t locate PCI device (0000:00:06.0)! perhaps already in-use?" My system is running both debian etch in dom0 and domU... Below you can find (hopefully) all important information... Sincerely, Gaubatz Patrick

Already reported.... http://bugs.centos.org/view.php?id=2516 >Subject: RE: [CentOS-virt] xenbr0 isn't created anymore >To: <centos-virt at centos.org> >Message-ID: > <E2BB8074E5500C42984D980D4BD78EF9022A704E at MFG-NYC-EXCH2.mfg.prv> >Content-Type: text/plain; charset="us-ascii" > >Kai Schaetzl wrote: >> >> Somehow I managed

Hi, I try to get networking running with xen 3.2, but it seems I fail miserably. I am on sles10sp1, with xen 3.2.0, and kernel rpm''s installed from SP2. I configured in /etc/sysconfig/network the NETWORK_LIST: NETWORK_LIST="bridge,0,default,00:DE:AD:BE:EF,192.168.8.13/24,dhcp-off" but an ifconfig xenbr0 still shows the mac address of peth0 fe:ff:ff:ff:ff:ff. Initially, I

I have a new x3655 IBM and whenever the /etc/xen/scripts/network-bridge script starts, the ethernet would no longer work. This post isn''t about the cause, but the fix. I did a lot of tcpdumps and Googling, but I''ll spare you that. All they do is prove that yes, there is an issue. :) I tried Debian 4.0 i386/amd64 and Ubuntu 7.04 Server i386/amd64 and they all exhibit the

Somehow I managed to disable the creation of xenbr0 on boot-up of the host system. CentOS 5 with standard CentOS Xen. I changed all Xen VMs to use xenbr0 instead of virbr0 and disabled virtlibd. Works fine. But when I later restarted the machine I found that all networking for guests had gone. On inspection there's no xenbr0 created anymore. I can get it up by stopping network (or eth0)

I followed these steps to get 3.3 installed on a CentOS 5.2 machine: # wget http://bits.xensource.com/oss-xen/release/3.3.0/xen-3.3.0.tar.gz # tar xvcf xen-3.3.0.tar.gz # cd xen-3.3.0 # make tools # make xen # make install-tools # make install-xen Development deps were all meet, everything compiled w/o error. Used yum to install kernel-xen bridge-utils bridge-utils gtk-vnc (did I need that?)