From: Sadi <sadijrp@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Wen Congyang <wency@cn.fujitsu.com>, xen-devel@lists.xen.org
Subject: Re: Error migrating VM to secondary host using COLO replication
Date: Tue, 8 Nov 2016 18:53:03 -0200 [thread overview]
Message-ID: <CAMHADrH6xXkAV8mpACBVmCuC-_p06f9mKfAXzEM0pPcMmJG39w@mail.gmail.com> (raw)
In-Reply-To: <20161108195721.GB20807@char.us.oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1933 bytes --]
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]: <info> (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.
[-- Attachment #1.2: Type: text/html, Size: 2962 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-08 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 22:56 Error migrating VM to secondary host using COLO replication Sadi
2016-10-28 16:56 ` Konrad Rzeszutek Wilk
2016-11-03 6:23 ` Zhang Chen
2016-11-03 6:33 ` Wen Congyang
[not found] ` <CAMHADrE4rXxM9K0UrSq38MZrz=dwKYyDSq0MQRiEZQyC+Qeviw@mail.gmail.com>
2016-11-04 17:50 ` Fwd: " Sadi
2016-11-07 20:37 ` Sadi
2016-11-08 19:57 ` Konrad Rzeszutek Wilk
2016-11-08 20:53 ` Sadi [this message]
2016-11-09 17:31 ` Sadi
2016-11-10 1:03 ` Wen Congyang
2016-11-10 21:53 ` Sadi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMHADrH6xXkAV8mpACBVmCuC-_p06f9mKfAXzEM0pPcMmJG39w@mail.gmail.com \
--to=sadijrp@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).