similar to: XCP domUs not added to bridges (possible bug)

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

Package: xcp-xapi Version: 1.3.2-6 Severity: important Looks like on Wheezy, /etc/default/xen is not created by xen-utils-common. Since xcp-xapi depends on its existence and further declaration of the toolstack in it, it should take extra care to ensure that it is present. root at debian:~# aptitude install xcp-xapi The following NEW packages will be installed: blktap-dkms{a} blktap-utils{a}

hi all , i use ubuntu 12.04 with xcp , all config run very well except vlan i use xe network-create and xe vlan-create to build vlan 3000 then startup a vm in this network, xapi0 fakebridge and vif1.0 all looks well, use ovs-vsctl list port i can see xapi0 and vif1.0 have beed taged with 3000 but i can not access the internent~~~ somebody can help me with this? thanks.

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-api Severity: wishlist Tags: patch l10n Hello, Attached is the Dutch translation of the xen-api debconf templates. Please include it in your next upload. Regards, -- Jeroen Schot -------------- next part -------------- # Dutch translation of xen-api debconf templates. # Copyright (C) 2012 THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the

Package: xen-api Version: 1.3.2-3 Severity: wishlist Tags: l10n patch Greetings, -- Camale?n -------------- next part -------------- # xen-api po-debconf translation to Spanish # Copyright (C) 2010 Software in the Public Interest # This file is distributed under the same license as the xen-api package. # # Changes: # - Initial translation # Camale?n <noelamac at gmail.com>, 2012 # # -

Hello Everyone, I am new with XCP. I''ve setup several hosts with* XCP 1.0* and manage it through XenCenter and command console. Each host has two NICs, one (xenbr0) connected to a physical switch for Internet (said sw1), the other (xenbr3) connected to a physical switch for internal network (said sw2). I am trying to setup VMs and VLANs on xenbr3. I created a virtual bridge by

Got following message in /var/log/daemon.log: Jul 30 19:45:11 cvt-xh4 xapi: [error|cvt-xh4|5|Starting periodic scheduler D:7c5d1d776763|backgroundscheduler] Logrotate executed with error code: stdout='''' stderr=''error: error renaming

Hi, I would like to know if somebody can point me out how to configure several DomUs in a private LAN (for example 192.168.100.0/24) and one DomU with two interfaces (one - 192.168.100.0/24 and two - internet). So far I have enabled in xend-config.sxp: (network-script network-route) (vif-script vif-route) My config files have: /mnt/VM/1.cfg:vif = [''ip=192.168.1.3'']

This patch adds an ACM hook into the network scripts (/etc/xen/scripts). It adds iptables rules that enforce mandatory access control on network packets exchanged between virtual interfaces. If ACM is active, this patch sets the default FORWARD policy in Dom0 to DROP and adds iptables ACCEPT rules between vifs that belong to domains that are permitted to share (determined by using the

Hello, I have been playing with the XCP for a while now, and must say I''m very exited about the technology. I had no prior experience with Xen so it has taken me a while to understand the concepts, but now I feel most important issues are solved and I''ve purchased some hardware to build my (tiny) cloud on. The box is a Supermicro 1026TT-IBXF, so I have 2 x Ethernet and 1 x

Here is the situation. I have a xen system with 2 drives setup in a RAID1. I pulled one drive and put it into an identical server. Now, when I boot up the new server, peth1 is not created. [root@dom0 ~]# ifconfig | grep Link eth1 Link encap:Ethernet HWaddr 00:14:38:A7:55:C2 inet6 addr: fe80::214:38ff:fea7:55c2/64 Scope:Link lo Link encap:Local Loopback vif1.0 Link

*Hello,* I have installed Xen as Hypervisor with OpenSUSE running in Dom0. I want to use ovswitch (ovs) instead of the bridges that Xen created. In order to do so, I installed ovs in dom0 just like for the plain Linux. Xen has replaced eth0 with peth0, and has created a bridge named eth0. And eth0 is connected peth0 interface , vif2.0 interface (VM), and everything is working fine. Now I delete

Hi, this is propably bridge related and not really a xen problem, but it might help someone: Some of our domUs are not able to arp. Arp -n show (incomplete), and doing a tcpdump shows, that on the dom0''s eth0 the arp request goes out, the response comes in, but on the vifX.0 interface the arp response is gone. dom0# tcpdump -ni eth0 arp who-has 10.32.2.51 tell 10.32.7.70 arp reply

On Wed, Mar 15, 2017 at 10:10:36AM +0000, Daniel Pocock wrote: > > I've been using XenServer / XCP (with the "xe" toolset) for a number of > years for hosting servers used for development and free software > projects and I'm now looking at migrating all those environments to > libvirt / KVM. > > I had a look at the wiki[1] already and didn't see

Hi all, Is it possible to have native VLAN (802.1q) and a VLAN x at the same time in DOMU''s? This is what I have configured on my DOM0 (xen2): Eth0 (connected by a 801.1q trunk to Cisco 2950 switch) Created vlan100 : vconfig eth0 100 Created bridge : brctl addbr br100 Attach switchport: brctl addif br100 eth0.100 Attach a DOMU : brctl addif br100 vif2.0 I now have bridge br100

Hi, I''ve bit the bullet and gone with Xen, but I get some odd networking. Basically, this was the original idea. eth0 external eth1 internal create bridge br0 for eth0 create bridge br1 for eth1 Strip IP addresses for eth0 and eth1 and assign to br0 and br1 respectively. Worked great in a non-xen kernel under Fedora 8 in KVM/Qemu. Booting into Xen, my eth1 becomes eth2, I also get

A huge thank you to mario from the ''openvswitch on Xen 4.1'' post. I was having some trouble with using openvswitch with Xen 4.1 (I''m currently migrating from 4.0.1) until I saw his post and noticed that the xl.conf needed the full path to the networking script. Made this change and all is good now. Thank you. I would like to contribute what I have for using

P{font-size:10pt; line-height:16; margin-left:0; margin-top:0; margin-right:0; margin-bottom:0; font-family:gulim;} (English is not my first language Sorry for my poor English ) &nbsp; OS :&nbsp; Linux nc233 2632-220171el6x86_64 #1 SMP Tue May 15 17:16:46 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux CentOS release 63 (Final) open vswitch : 11190 virsh : 100 ibvirtd (libvirt) :

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for