similar to: is_physical bug in xapi

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

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:

Hi I don''t quite understand the new xen networking. We use network-bridge! Everything works fine except that an iptables firewall on dom0 blocks all my domU. In my firewall settings i use eth0. I figured out that eth0 is the bridge but where is the interface for dom0? I want my firewall setting to only apply to dom0 interface! Since there is not anything like vif0.0 i don''t know

Hi ALL, Here is a weird problem comfusing me for a long time. i''v installed xen 4.0.1 with linux kernel 3.1.0-rc9+ Everything works fine except i cannot ping to the gateway in a PVM domU. i''v installed bridge-utils and brctl show like this bridge name bridge id STP enabled interfaces eth0 8000.00219b480d56 no

Hi, we''re running 4 xen servers on our network with multiple network cards. During HighLoad we experince degeneration of inbound network traffic through our loadbalancer. I might found a reason for it, in Dom0 dmesg output looks as follows: [1157421.975910] eth0: received packet with own address as source address [1157421.975957] eth0: received packet with own address as source

Hopefully I summed up the jist of the problem in the subject line. ;) I have a GFS cluster with ten Xen 3.0 dom0s sharing an iSCSI LUN. There are on average 8 domUs running on each Xen server. The dom0 on each server is hard-coded to 2 CPUs and 2GB of RAM with no ballooning, and has 2GB of partition-based swap. When creating a new domU on any of the Xen servers, just after the completion of

I''ve got 2.0.7 running on a machine with 1 physical interface and two bridges, like so -- bridge name bridge id STP enabled interfaces xen-br0 8000.0040f4ce392f no eth1 vif5.0 vif9.0 xenbr1 8000.feffffffffff no

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

I''m attempting to put together a Xen box, which has multiple VLANs running into it, on one bridged interface. I mostly copied the way it was done here: http://renial.net/weblog/2007/02/27/xen-vlan/ I basically have: bond0 is the bond device (composed of eth0 and eth1), vlan757 is the vlan device for vlan 757 on bond0, and "xen757" is a bridge created by the above scripts,

Hi all, I''m currently experiencing some problems with the network connection of a HVM domU. I''m using xen 3.0.3-1 on a debian etch box and have to use the routing configuration (but bridging does not work either) Booting the domU works fine, but I can not ping dom0 -> domU neither domU -> dom0. Although the transmit counter is incremented in the domU, no packets are

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

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: normal If quagga is running, and I start & stop a domain, the VIF interface doesn't go down properly (in addition to other problems). Here's what I do: 1. Boot the computer. By default, quagga is running (zebra + ospfd). 2. xm create test7.cfg, wait until the domU starts. 3. xm shutdown test7, wait until the domU

Package: xcp-xapi Version: 1.3.2-6 Severity: normal After some time of rebooting and toolstack restart found very funny output in 'xe pif-lis': xe pif-list params=currently-attached,device device ( RO) : vif2.0 currently-attached ( RO): false device ( RO) : vif211.0 currently-attached ( RO): false device ( RO) : eth1

Well where do I start...I have a domU (ubuntu) booting and appears well but I don''t have an eth0 listed at all, dom) looks good. DomU: eth0 Link encap:Ethernet HWaddr 00:06:5B:15:C5:0B inet addr:10.99.99.5 Bcast:10.99.99.7 Mask:255.255.255.248 inet6 addr: fe80::206:5bff:fe15:c50b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

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

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

Hi I'm very new with Xen (/Debian) I have 2 VMs running Windows: "Arch" and "Sql" -- static IPs VM Arch: is ok, accessible thru VNC, Remote Desktop, see the network, etc VM Sql : - just accessible thru VNC             - once I log in, I don't see the network             - pings don't reach peer             - appear 4 network ports on Windows the server has 4

Hello, I have the following Xen 3.0.2-2 related problem: A host system with Centos 4.4 in the dom0, guest systems are Fedora Core 5 (images from jailtime.org) mounted on LVM. Networking on the domUs is not working, Iptables in the guests are not working either. Each Guest system should have at least 1 dedicated public IP assigned to it, but should have the capability to have more than 1