From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sadi Subject: Re: Error migrating VM to secondary host using COLO replication Date: Tue, 8 Nov 2016 18:53:03 -0200 Message-ID: References: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> <20161108195721.GB20807@char.us.oracle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3712676867859548058==" Return-path: In-Reply-To: <20161108195721.GB20807@char.us.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Konrad Rzeszutek Wilk Cc: Wen Congyang , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============3712676867859548058== Content-Type: multipart/alternative; boundary=001a11443abca84fe80540d05349 --001a11443abca84fe80540d05349 Content-Type: text/plain; charset=UTF-8 Hi, Apparently vif2.0-emu was already binded with br0 when "brctl addif br0 vif2.0-emu" failed. root@colob-HP-Compaq-6005-Pro-MT-PC:~# brctl addif br0 vif2.0-emu device vif2.0-emu is already a member of a bridge; can't enslave it to bridge br0. root@colob-HP-Compaq-6005-Pro-MT-PC:~# brctl show bridge name bridge id STP enabled interfaces br0 8000.001a3fc46255 no eth0 vif2.0 vif2.0-emu br1 8000.000000000000 no About the iptables, it seems like SECCOLO target can't be recognised. root@colob-HP-Compaq-6005-Pro-MT-PC:~# iptables -t mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j SECCOLO --index 1 iptables: No chain/target/match by that name. Here is my active modules matching colo: root@colob-HP-Compaq-6005-Pro-MT-PC:~# lsmod | grep -i colo xt_SECCOLO 16384 1 nf_conntrack_colo 16384 2 xt_SECCOLO x_tables 36864 8 xt_physdev,ip6table_mangle,ip_tables,xt_SECCOLO,xt_tcpudp,iptable_filter,iptable_mangle,ip6_tables nf_conntrack 106496 4 xt_SECCOLO,nf_nat,nf_conntrack_colo,nf_conntrack_ipv4 So i was looking in the iptables and this really looks like the source of the problem. Sadi. On Tue, Nov 8, 2016 at 5:57 PM, Konrad Rzeszutek Wilk < konrad.wilk@oracle.com> wrote: > > entered forwarding state > > Nov 7 18:10:30 colob NetworkManager[907]: (vif2.0-emu): enslaved > > to br0 > > Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl > addif > > br0 vif2.0-emu failed > > > How come this failed? > > > Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: iptables > -t > > mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j SECCOLO > --index > > 1 failed > > Ah b/c of this. Are there any errors of what exactly failed? > -- Sadi. --001a11443abca84fe80540d05349 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Apparently vif2.0-emu was already b= inded with br0 when "brctl addif br0 vif2.0-emu" failed.

root@colob-HP-Compaq-6005-Pro-MT-PC:~# brctl addif br= 0 vif2.0-emu
device vif2.0-emu is already a member of a bridge; c= an't enslave it to bridge br0.
root@colob-HP-Compaq-6005-Pro-= MT-PC:~# brctl show
bridge name =C2=A0 =C2=A0 bridge id =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 STP enabled =C2=A0 =C2=A0 interfa= ces
br0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8000.001a3fc462= 55 =C2=A0 =C2=A0 =C2=A0 no =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= eth0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 vif2.0
=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 vif2.0-emu
b= r1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8000.000000000000 =C2=A0 =C2= =A0 =C2=A0 no

About the iptables, it seems l= ike SECCOLO target can't be recognised.

r= oot@colob-HP-Compaq-6005-Pro-MT-PC:~# iptables -t mangle -D PREROUTING -m p= hysdev --physdev-in vif2.0-emu -j SECCOLO --index 1
iptables: No = chain/target/match by that name.

Here is my = active modules matching colo:

root@colob-HP-C= ompaq-6005-Pro-MT-PC:~# lsmod | grep -i colo
xt_SECCOLO =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 16384 =C2=A01
nf_conntrack_col= o =C2=A0 =C2=A0 =C2=A016384 =C2=A02 xt_SECCOLO
x_tables =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 36864 =C2=A08 xt_physdev,ip6table= _mangle,ip_tables,xt_SECCOLO,xt_tcpudp,iptable_filter,iptable_mangle,ip6_ta= bles
nf_conntrack =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0106496 =C2=A0= 4 xt_SECCOLO,nf_nat,nf_conntrack_colo,nf_conntrack_ipv4
So i was looking in the iptables and this really looks like the= source of the problem.=C2=A0

Sadi.

On Tue, Nov 8, 2016 = at 5:57 PM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> entered = forwarding state
> Nov=C2=A0 7 18:10:30 colob NetworkManager[907]: <info>=C2=A0 (vi= f2.0-emu): enslaved
> to br0
> Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setu= p: brctl addif
> br0 vif2.0-emu failed


How come this failed?

> Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setu= p: iptables -t
> mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j SECCOLO --i= ndex
> 1 failed

Ah b/c of this. Are there any errors of what exactly failed?



--
Sa= di.
--001a11443abca84fe80540d05349-- --===============3712676867859548058== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============3712676867859548058==--