similar to: network-bridge status something strange

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

Hello, I wants to make a self compiled kernel for my domUs on a debian etch server with Xen 3.1.4 and 2.6.18.8 dom0 kernel. So, I download sources for linux-2.6.26.8, and I enabled all the Xen features : Symbol: HVC_XEN [=y] Symbol: XEN_BALLOON [=y] Symbol: XEN_FBDEV_FRONTEND [=y] Symbol: XEN_SCRUB_PAGES [=y] Symbol: XEN_KBDDEV_FRONTEND [=y] Symbol: XEN_BLKDEV_FRONTEND [=y] Symbol:

Hello, I have to virtualize an old physical server who turn an a Debian Sarge with a 2.4.27-3-686-smp kernel with applications compiled with this kernel. My Xen Server is a Debian Etch Dom0 2.6.18.8 with Xen 3.1.4. So I wants to know how compile a 2.4.27 kernel for virtualize this machine. Thanks for your help -- ''''~``

Hello, I''ve got a big problem when I try to install Zimbra on a xen debian etch vm. Eeek! page_mapcount(page) went negative! (-1) page pfn = 7141 page->flags = 4000083c page->count = 2 page->mapping = cd946510 vma->vm_ops = 0x0 ------------[ cut here ]------------ kernel BUG at mm/rmap.c:669! invalid opcode: 0000 [#1] SMP Pid: 7717, comm: java Not tainted

Hello, I have a little problem with my Xen server. Friday, I done a xm destroy on a Windows XP vm. But now when I want to start this vm I have this error : Error: (28, ''No space left on device, while writing /vm/58c0159f-19c9-5e94-1ae7-eebd4205d520/image/cmdline : '') so I done this : xenstore-control check I use this script to dump the tdb :

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

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

Hello, Since my last update of xen, I am having problems with bridges and xen. When I want to start a bridge on the dom0 (to run a domU in a different vlan than the default) I run /etc/xen/scripts/network-bridge start netdev=eth0.302 bridge=xen-br302 antispoof=no where eth0.302 is an interface associated with my vlan 302 (it tags with this vlan identifier). The problem I have is that it

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

Dear I need create second bridge xenbr1 for separate traffic between my virtual machine , I following this step but show message that Link veth0 is missing, how I can create veth0 ? When I run script for create xenbr1 ./network-bridge netdev=eth1 bridge=xenbr1 start Shwo this message Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the

Hi, I''m using RHEL linux 5.1, I can''t add the another NIC to my virtual machine. # /etc/xen/scripts/network-bridge start Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the loopback driver supports. If the loopback driver is a module, you may raise this limit by passing it as a parameter (nloopbacks=<N>); if the

Package: xen-hypervisor-3.0-unstable-1-amd64 Version: 3.0-unstable+hg11292-2 Severity: important My server is a dell 2950 server. Before the dom0 rebooting bug ocurred, xen was well even for hvm domU. By now i have tried xen-hypervisor-3.0-amd64 (3.0.2+hg9697-2) and xen-hypervisor-3.0-unstable-1-amd64 (3.0-unstable+hg11292-2), but both of them are unusable for me. for

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

I try to bring up xend but get this error in the xend-debug.log /etc/xen/scripts/network-bridge: line 62: ip: command not found Link veth0 is missing. This may be because you have reached the limit of the number of interfaces that the loopback driver supports. If the loopback driver is a module, you may raise this limit by passing it as a parameter (nloopbacks=<N>); if the driver is

Hi All, I have a USB-HID compatible UPS which is connected to my dom0 (CentOS 5.1) which is being monitored.  I have a bunch of domU''s of various OS''es, and was wondering if anyone has a solution to send the "state" of the UPS to the domU''s (read-only).  I''d like that in the event of a power-outage and the UPS''s batteries are low that before

> I have installed xen-unstable change set 1150. I have 3 nics in my system. > > My ifconfig shows eth1, eth4 and eth5. > > And a brctl show shows xenbr1 only. > > When I try to create bridge 4 > > /etc/xen/scripts/network-bridge vifnum=4 start > > > > Link veth4 is missing. (...) > I tried increasing the loopback devices in the kernel boot

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 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 there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

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