similar to: Bug#388486: xen-utils-common: upgrade new 2.6.17-2-xen breaks create domU until modprobe netloop nloopbacks=n

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

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

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

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

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 put this page together just so I won't spam the board anymore begging for help..lol http://bobhoffman.com/vmissue.html This shows a working effort of bonded eths, bridged into a vm, and a few other things. The only missing thing is something on the host that ends up putting the VM internet connection into some kind of limbo. Whether it is hardware related, bug related, libvirt nat

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

Hi to the ML. I''m new to VLAN configuration, and combining it to XEN is a bit difficult. I want to use VLAN because it''s possible to "arping" from a domU to an other, and VLAN looks like; the only solution to prevent that. May be I''m wrong if someone got a solution, I may be interrested. I''ve also tryed ebtables, but nothing to prevent arp

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

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

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

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

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

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

Still trying to make my VMs appear on a subnet of their very own and route traffic to/from them from the Dom0. This network-multinet script sounds ideal for what I want: http://thepenguinpriest.com/linux/scripts/network-multinet.html However, the description of building a routed network says I need to call the script and give it the "virtual ethernet device (vethX)" that lives in

Hi, I'm wondering about the impact of using both dom0 and domU's on a server at the same time. I'm worried about the performance impact of running a Mysql server in a domU and now I'm thinking about moving the Mysql part of a LAMP setup into dom0 and running a few Apache guests as domUs. Since the Apaches will serve mostly from an NFS share they won't have much impact on

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!

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

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