similar to: Re: CentOS-virt Digest, Vol 7, Issue 22

Package: xen-utils-common Version: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was

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)

Hi all, Up until now, we''ve been using Xen 3.0 on CentOS 5.x. Under this setup, dom0 was given a virtual ''ethX'' with the original ''ethX'' (now ''pethX'') IP address. Under this older config, neither ''pethX'' or ''xenbrX'' had an IP address. The logic was to keep traffic from the domU''s, through

Hi, I''ve a working xen 3.0.2 booting a gentoo linux on Dom0. I have setup a Windows XP in a DomU OK with no problems except the network!! My problem is that I wanted to give a working network interface on the DomU and the best I could. making the windows detect an network adapter, was putting: vif = [''type=ioemu''] I also tryied: vif = [''type=ioemu,

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

Hi Everyone, In my HVM guest''s config file, I have given my guest 3 interface. I have called them fw1, fw2 and fw3. I have joined each interface to a bridge on the Dom0. This does appear when I do a "brctl show". However, there are 3 other interfaces also added called tapx.0,tapx.1 and tapx.2 (Where x is the domain ID for the guest). Furthermore, I am only able to run

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 have install the xen4+centos5 on my server following the post of the kernel version is 2.6.32.27 which is download from git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git But after I reboot the server ,and run the "ifconfig", whose output likes the following [root@localhost scripts]# ifconfig eth0 Link encap:Ethernet HWaddr 00:15:C5:EB:96:C3

Hello. After all, i found that distribution default setup works well, and the malfunction was my network-bridge wrapper's fault. Some changes to the way of work fo network bridge script was introduced. 1. The bridge is not named xenbrX any more, but ethX instead. 2. The Dom0's network interfaces are not virtual network interfaces bridged with the physical interface, but the network bridge

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 *, having built Xen 4.1.0 and running my Dom0 on Slackware 13.1, I''m trying to assign different physical network interfaces to different DomU guests: vif = [ ''bridge=ethX'' ] in the DomU configuration files. My /etc/xen/scripts/network-bridge script, however, doesn''t create more than one bridge: root@cen:~# /etc/xen/scripts/network-bridge start

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

what i am doing wrong? My vethX of xend-dom0 dont start. ---- dcgs0058:~# lspci |grep Ether 0000:06:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) 0000:07:08.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) dcgs0058:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:13:72:4E:7E:B3 inet addr:172.28.0.200

Yes, I saw that problem and removing the vif line or changing it to vif0 fixed it for me. Aravindh > -----Original Message----- > From: wei huang [mailto:huanwei@cse.ohio-state.edu] > Sent: Friday, November 04, 2005 12:14 PM > To: Puthiyaparambil, Aravindh > Cc: Mark Williamson; xen-users@lists.xensource.com; ewan@xensource.com > Subject: RE: [Xen-users] Error "Device 0

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

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!

I''ve been trying to track down an occasional system hang when doing /etc/xen/scripts/network-bridge stop. Would it be reasonable to do the fdown ${netdev} and then set ${vif0} down to provide ifdown with a behavior that is as close as possible to a real network card? Signed- off- by: Kirk Allan <kallan@novell.com> _______________________________________________ Xen-devel

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