em to, would be of great help.
Thanks,
Sadi.
On Wed, Nov 9, 2016 at 11:03 PM, Wen Congyang wrote:
> On 11/10/2016 01:31 AM, Sadi wrote:
> > Hello again,
> >
> > Looking at the primary host's syslog, the arptables command from
> xen/etc/scripts/colo-proxy-setup has
et-mark 1
Bad argument `1'
Thanks, Sadi.
On Tue, Nov 8, 2016 at 6:53 PM, Sadi wrote:
> 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
> dev
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.w...@oracle.com> wrote:
> > entered forwarding state
> > No
0 2502 4
r- 453.2
suse-hvm--incoming 2 1023 2
--p--- 0.0
At this moment, if i unpause the VM in the secondary host it keeps running
from the point where the process was paused before the xl remus command.
I've tried removing
-- Forwarded message --
From: "Sadi"
Date: Nov 3, 2016 20:34
Subject: Re: [Xen-devel] Error migrating VM to secondary host using COLO
replication
To: "Wen Congyang"
Cc:
> Hi,
>
> Thanks for replying. Here is what i got from /var/log/syslog:
>
&
;libxl: info: libxl_colo_restore.c:320:libxl__colo_restore_teardown: colo
fails
I'm hoping that someone could provide with directions.
Thanks for your time and sory for bad english (not native language).
Sadi.
Network
master:
br0 : 10.20.107.30 binded with eth0
eth1: 192.168.1.30
eth2: 19
