similar to: Arp problem with network bridging and VLANs

Hello, I''ve recently changed my xen network setup and now, almost expectedly, my configuration has broken access to the Domus from the network, and now I need a little help. Previously, I had four interfaces, only one of which was configured to be used by both dom0 and domu. I have since created a bond between eth2 and eth3, expecting that eth0 would be automatically assigned for use

Today I found I can not ping some of my domU''s. I logged in to dom0, did a "xm list", all domU are there. Then I did a "ifconfig" and surprised to find some of vif''s disappeared! Like for example. "xm list" show dom13 is alive, but "brctl show" shows no vif13.0. If I "xm console 13", there''s some message: WARNING:

I''m using Xen 4.1 and here''s what I did: 1.comment network-script and vif-script about bridge in /etc/xen/xend-config.sxp, uncomment the lines about nat 2.set vm config, add something like vif = [ ''mac=00:16:3e:00:00:11, ip=10.0.0.1'' ] 3.set /etc/network/interfaces in domU, add lines as follows: auto eth0 iface eth0 inet static address 10.0.0.1 gateway

I''m using Xen 4.1 and here''s what I did: 1.comment network-script and vif-script about bridge in /etc/xen/xend-config.sxp, uncomment the lines about nat 2.set vm config, add something like vif = [ ''mac=00:16:3e:00:00:11, ip=10.0.0.1'' ] 3.set /etc/network/interfaces in domU, add lines as follows: auto eth0 iface eth0 inet static address 10.0.0.1 gateway

hi all, i just found a bug from xapi code network_utils.ml: let is_physical name = try let link = Unix.readlink (getpath name "device") in (* filter out device symlinks which look like /../../../devices/xen-backend/vif- *) not(List.mem "xen-backend" (String.split ''/'' link)) with _ -> false i use xcp + ubuntu 12.04, in my /sys/class/net/ dir it

errors from /var/log/xcp-xapi.log: 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xapi] creating device emulator 652Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] Device.Dm.start domid=10 661Z|debug||1227 UNIX /var/lib/xcp/xapi|VM.start R:0b98978366e4|xenops] qemu-dm: should be running in the background (stdout redirected to syslog) 661Z|debug||1227 UNIX

i just found a bug from xapi code network_utils.ml: let is_physical name = try let link = Unix.readlink (getpath name "device") in (* filter out device symlinks which look like /../../../devices/xen-backend/vif- *) not(List.mem "xen-backend" (String.split '/' link)) with _ -> false i use xcp + ubuntu 12.04, in my /sys/class/net/ dir it looks like:

Package: xcp-xapi Version: 1.3.2-14 Severity: important I chose the Open vSwitch (ovs) networking mode when I installed XCP # cat /etc/xcp/network.conf openvswitch Whenever I boot a VM, I notice that the vif interface is created (e.g. vif1.0) on dom0, and the vif is added to the ovs bridge (I can see it in the output of ovs-vsctl show) However, there is no connectivity, I can't ping the

Hello I have two linux machines connected via 2 dsl lines (bonded) 192.168.0.1-eth0-dsl---2Mbit---dsl-eth0-192.168.0.2 ^-eth1-dsl---2Mbit---dsl-eth1-^ so the final figure is something like this: 192.168.0.1-bond0---4Mbit---bond0-192.168.0.2 I can only use arp monitoring for fail checking - if one dsl line fails - automatically use only the other one. I set up everything correctly (i

I don''t know if there was a problem in the archive or not, I just wanted to link to this post of mine, but I could not find it in the archive. So here''s a re-post. -------- Original-Nachricht -------- Betreff: [Xen-users] Xen, NIC bonding, ARP problem Datum: Fri, 30 Mar 2007 10:05:45 +0200 Von: Dominik Klein <dk@in-telegence.net> An: xen-users@lists.xensource.com Hi

Hi, I've been testing the Debian packages ahead of the Debian 7 release (which is very imminent) I believe this is a serious bug[1] in the package, as it appears that HVM networking is broken, or at the very least, requires some undocumented configuration step Specifically: - I can start the HVM domU without any vif - if I attach a vif, the domU will not start Looking at

My impression of this bug is that HVM networking is not possible with XCP, or at least it is not possible without some undocumented configuration setting or missing dependency package If there is a workaround from upstream, I would propose lowering the severity to important again. I am happy to test any proposed work around and provide quick feedback. The log output in my previous post suggests

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-3 Severity: important Hi, I have some domUs with two network interfaces, eth0 and eth1. eth0 is not configured in /etc/network/interfaces and so is not brought up at boot time. eth0 is on the host's external network bridge and eth1 is on the host's local network bridge. On dom0 I get messages like 'vif vif-10-0 vif10.0: draining TX

I am managing two Xen containers which are exhibiting a spooky behavior. There are intermittent network failures that affect only the VM''s, and not dom0. This exhibits itself as problems with nfs locks, snmp, and even icmp ping. The arp tables look normal on both the dom0 and the guest. However, it is definitely arp related. Causing arp traffic of any sort results the problem curing

Hello all, I would like to use two network interfaces. It is working but I notice that both bridges hace the same id. #brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif10.0 xenbr1

I''ve looked everywhere for the error message I''ve posted in the title, doesn''t seem like anyone else has it (lots of missing hotplugs scripts). We''re using network-nat. ifconfig -a outputs this: eth0 Link encap:Ethernet HWaddr 00:19:99:a8:f4:5c inet addr:X.X.X.X Bcast:X.X.X.X Mask:255.255.255.255 inet6 addr: X::X:X:X:X/64 Scope:Link

--- In english --- Hello! I am to implement a new architecture of the network in my company but I do not know right where to start ... need help! Currently 90% of my servers are virtual machines under Xen. I have many valid IP networks and all Hypervisors are configured in bridge mode, to simplify. We have 3 VMWare ESX Hypervisor also in bridge mode. Some networks are exclusive to certain

hi 2015-06-11 11:10 GMT+02:00 Timo Sch?ler <timo at riscworks.net>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi, > > some months ago I ran into a hassle with following, quite simple > config that works on CentOS 6 and CentOS 5 extremeley well, for years. > However, I have problems getting it running on CentOS 7. > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, some months ago I ran into a hassle with following, quite simple config that works on CentOS 6 and CentOS 5 extremeley well, for years. However, I have problems getting it running on CentOS 7. ,-- bond0.100 -- brbond0.100 -> (VMs) eth0 (eno1 on C7) --. | |--- bond0 ----|--

So, I have been running into network problems for a while on 4 boxes that I installed xen on so that some engineers have places to test code. This particular problem is happening on all 4 of these boxes. (although, it isn''t happening on an older box running xen from debian etch). What appears to be the problem is that traffic is getting dropped between the vif#.0 interface in dom0