search for: xenbrx

...any init script or so that might run it, so I assume >> it's xend doing that, but there's no error in any log. > >Kai, > >Snooping around I found this in /etc/xen/qemu-ifup: > ># ># Old style bridge setup with netloop, used to have a bridge name ># of xenbrX, enslaving pethX and vif0.X, and then configuring ># eth0. ># ># New style bridge setup does not use netloop, so the bridge name ># is ethX and the physical device is enslaved pethX ># ># So if... ># ># - User asks for xenbrX ># - AND xenbrX doesn't exist...

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

...uot;) if [ -z "$bridge" ] then bridge=$(brctl show | cut -d " " -f 2 | cut -f 1) if [ -z "$bridge" ] then fatal "Could not find bridge, and none was specified" fi else # # Old style bridge setup with netloop, used to have a bridge name # of xenbrX, enslaving pethX and vif0.X, and then configuring # eth0. # # New style bridge setup does not use netloop, so the bridge name # is ethX and the physical device is enslaved pethX # # So if... # # - User asks for xenbrX # - AND xenbrX doesn't exist # - AND there is a eth...

Hi, I just tested in the lab the new CentOS 5.1 Xen and find out it breaks network connectivity, at least in my setup. It seems it is somehow making use of the 3.1 Xen version (altought I am not sure about that) but whatever changes it introduce is not documented at the location one would expect, the obvious new thing (at least for me) is this thing I will call out of guessing a virtual

Hi Folks: I am a NOOB and need some help and/or advice about debugging a domU VM boot problem in XCP 1.0 beta. I am trying to get my first VM installed over the network using XCP 1.0 beta. I am able to get to the VNC boot window but the installation process fails after a few minutes with this error: Unable to retrieve http://10.45.2.1//tcc/os/CentOS-5.5-x86_64/images/stage2.img

Hi all: I installed xen-3.0.4 on Fedora 7, and installed Fedora 6 as DomainU, but, the network can not work normally. It only work for seconds, then I lose connect. If I ifdown the NIC and ifup it, the network can work for a few seconds, Can anybody help me figure what''s the problem ?? Thank you in advance _______________________________________________ Xen-devel mailing list

Hi, i want to install a WinXP as vm, but it won''t work. "xm list" tells me that the winxp-vm is running, but I am not able to connect via vnc. nmap tells me that there is no vnc-port listening and ps -A tells me that qemu-dm does not work. Maybe someone could help me because i have no idea what''s wrong.. System: Debian Lenny XEN: from lenny-repository ps -A says:

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 itself. Provably a notice should be added about this for those who is dist-upgrading? I assume this will pop-up in any setup that uses net...

I have a couple of Xen 3.1 servers running on Ubuntu 7.10 AMD64 Server machines. I decided to to upgrade these machines up to the latest release of Ubuntu (8.04 LTS) which upgrades Xen to version 3.2. I upgraded the first machine, installed the xen component. these machines all have two network interfaces one connected to the WAN and the other to the local LAN network. In a tutorial i read a

...by the distribution, and bridge each VLAN separately, so I can flexibly assign (and manage) specific VLAN''s to domU''s. This does not work with the default xen network-bridge script (the black magic it does seems to fail with VLAN interfaces). Example configuration: peth0.X == xenbrX peth0.Y == xenbrY peth1.Z == xenbrZ peth1.W == xenbrW Default Xen network-bridge script does the following (in addition to other things): 1. Changes the MAC-address of peth0 to FE:FF:FF:FF:FF:FF. If I have another physical interface, peth1, can it have the same MAC address, or does it have to b...

...i 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 the bridge and out ''pethX'' without dom0 seeing anything. This is particularly useful in our environment (2-node cluster using DRBD to allow hot-migration and disaster recovery between n...

Hi, I''m using Xen 3.0.3 on two servers with Debian Etch (amd64). These servers have 10 nics (2 onboard and 8 in two 4-port cards) so that every vm can have its own interface. This worked so far with the Xen Version from Etch with a wrapper script wich started 10 bridges at boot time. But now I''ve updated Xen on one of these server to Xen 3.2.0 from backports.org and now the

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

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