similar to: Bug#678723: i got same and found the reson

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

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

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

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:

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

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

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

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

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

Hi, the networking just drives me crazy and it seems that i am missing something. So here is my situation: i have a server with 2 public IPs (85.214.1.230 and 81.169.1.81) the dom0 is on: ip 81.169.1.81 netmask 255.255.255.255 gw 81.169.1.1 i would like to have a domU with ip 85.214.1.230. I tried everything routing, bridging.. nothing seems to work. my dom0 config; . (network-script

Hi, the networking just drives me crazy and it seems that i am missing something. So here is my situation: i have a server with 2 public IPs (85.214.1.230 and 81.169.1.81) the dom0 is on: ip 81.169.1.81 netmask 255.255.255.255 gw 81.169.1.1 i would like to have a domU with ip 85.214.1.230. I tried everything routing, bridging.. nothing seems to work. my dom0 config; . (network-script

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

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

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

Good day. Few month ago I reported bug when vif was added as PIF to database. Now I found way to reproduce this: xe vif-create network-uuid=$NET_UUID vm-uuid=$DOM0_UUID device=1 mac=f4:03:02:01:00:01 xe vif-plug uuid=$NEWVIF_UUID xe pif-scan host-uuid=$HOST_UUID xe pif-list root at lab-xh4:~# xe pif-list uuid ( RO) : 62cdddc5-89ad-38e0-e9af-879df66e409d

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

Hello list. My server: Gentoo 2.6.21-xen dom0 xen-tools 3.2.1 lvm 2.02.28-r2 udev-115-r1 Symptoms: normally I run 4 domUs. About once a week I have a need to restart a domU. Sometimes it works just fine, but other times it does not and I''ll get a message back saying "Error: Device 0 (vif) could not be connected. Hotplug scripts not working". The domU config file has not

Hi, > Can you manually do on the xen interfaces what the scripts would? How about > doing it on some other interface configured in a similar way? Toying with the vif-route script, I might have found a workaround for this issue. If I disable the ifconfig and ip route commands from vif-route script, and bring up vif interface by hand later on, everything seems to work. In other works,

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-2 This is related to Bug#699237: Huawei E220 does not work under Debian Wheezy Mainboard Gigabyte Z77X-D3H, 32GB RAM Xen dom0: Debian Wheezy 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux - affected 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux - affected Bus 001 Device 004: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA