xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sadi <sadijrp@gmail.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 14:57:21 -0500	[thread overview]
Message-ID: <20161108195721.GB20807@char.us.oracle.com> (raw)
In-Reply-To: <CAMHADrHrEZ52ApFDTGxEvTpWcUPNW6chDQh-OD5sk7sTBkiFhQ@mail.gmail.com>

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

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-08 19:57 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 [this message]
2016-11-08 20:53           ` Sadi
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=20161108195721.GB20807@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=sadijrp@gmail.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).