from:"Sadi"

Re: [Xen-devel] Error migrating VM to secondary host using COLO replication

2016-11-10 Thread Sadi

Hi,

Thanks for helping me.

I'm trying lots of different things so maybe there are traces of older
tries i've done conflicting right now.

I'm planning on starting over again from the very beginning. I just wanna
know what tutorial follow. The one from the Wiki,  from the mail thread or
another one.

Link to tutorials:

Wiki: http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
Mail Thread: http://xen.markmail.org/search/?q=COLO#query:COLO+page:1+
mid:fb7wrn62vbks4unn+state:results

I had a little fight against ubuntu, so if you could suggest me an
operating system to, would be of great help.

Thanks,

Sadi.

On Wed, Nov 9, 2016 at 11:03 PM, Wen Congyang <we...@cn.fujitsu.com> 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 failed.
> >
> > Here's the log:
> >
> > Nov  9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup: setup
> XENBUS_PATH=
> > Nov  9 14:43:39 colop kernel: [  302.825788] u32 classifier
> > Nov  9 14:43:39 colop kernel: [  302.825791] Actions configured
> > Nov  9 14:43:39 colop kernel: [  302.835407] Mirror/redirect action on
> > Nov  9 14:43:39 colop kernel: [  302.919605] ip6_tables: (C) 2000-2006
> Netfilter Core Team
> > Nov  9 14:43:39 colop kernel: [  302.941511] arp_tables: (C) 2002 David
> S. Miller
> > Nov  9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup:
> arptables -I INPUT -i eth1 -j MARK --set-mark 1 failed
> > Nov  9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup: Writing
> /hotplug-status connected to xenstore.
> > Nov  9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup:
> Successful colo-proxy-setup setup for vif2.0-emu. mode = primary  vifname:
> vif2.0-emu, index: 1, forwarddev: eth1.
> >
> > It's ok for the --set-mark argument to have value equal '1' , not a hex?
>
> This log is very useful, we will investigate it.
>
> Thanks
> Wen Congyang
>
> >
> > The i got running the command is:
> > root@colop:~# arptables -I INPUT -i eth1 -j MARK --set-mark 1
> > Bad argument `1'
> >
> > Thanks, Sadi.
> >
> >
> >
> > On Tue, Nov 8, 2016 at 6:53 PM, Sadi <sadi...@gmail.com  sadi...@gmail.com>> 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
> > 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.   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.w...@oracle.com <mailto:konrad.w...@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.
> >
> >
> >
> >
> > --
> > Sadi.
>
>
>
>


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

Re: [Xen-devel] Error migrating VM to secondary host using COLO replication

2016-11-09 Thread Sadi

Hello again,

Looking at the primary host's syslog, the arptables command from
xen/etc/scripts/colo-proxy-setup has failed.

Here's the log:

Nov  9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup: setup
XENBUS_PATH=
Nov  9 14:43:39 colop kernel: [  302.825788] u32 classifier
Nov  9 14:43:39 colop kernel: [  302.825791] Actions configured
Nov  9 14:43:39 colop kernel: [  302.835407] Mirror/redirect action on
Nov  9 14:43:39 colop kernel: [  302.919605] ip6_tables: (C) 2000-2006
Netfilter Core Team
Nov  9 14:43:39 colop kernel: [  302.941511] arp_tables: (C) 2002 David S.
Miller
Nov  9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup: arptables
-I INPUT -i eth1 -j MARK --set-mark 1 failed
Nov  9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup: Writing
/hotplug-status connected to xenstore.
Nov  9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup: Successful
colo-proxy-setup setup for vif2.0-emu. mode = primary  vifname: vif2.0-emu,
index: 1, forwarddev: eth1.

It's ok for the --set-mark argument to have value equal '1' , not a hex?

The i got running the command is:
root@colop:~# arptables -I INPUT -i eth1 -j MARK --set-mark 1
Bad argument `1'

Thanks, Sadi.



On Tue, Nov 8, 2016 at 6:53 PM, Sadi <sadi...@gmail.com> 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
> 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.   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.w...@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.
>



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

Re: [Xen-devel] Error migrating VM to secondary host using COLO replication

2016-11-08 Thread Sadi

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.   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.w...@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.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: [Xen-devel] Error migrating VM to secondary host using COLO replication

2016-11-07 Thread Sadi

--physdev-in vif2.0-emu -j SECCOLO --index
1 failed
Nov  7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: rmmod
xt_SECCOLO failed
Nov  7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: Successful
colo-proxy-setup teardown for vif2.0-emu.  vifname: vif2.0-emu, index: 1,
forwarddev: eth1,  forwardbr: br1.
Nov  7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: ip6tables -t
mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j SECCOLO --index
1 failed
Nov  7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: rmmod
xt_SECCOLO failed
Nov  7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: Successful
colo-proxy-setup teardown for vif2.0-emu.  vifname: vif2.0-emu, index: 1,
forwarddev: eth1,  forwardbr: br1.
Nov  7 18:10:45 colob kernel: [  625.475165] br0: port 3(vif2.0-emu)
entered forwarding state

When 'xl remus' hang on the error, the state of the vm in both hosts is:

Primary:
NameID   Mem VCPUsState
Time(s)
Domain-0 0  2502 4
r-  65.5
suse-hvm 2  1023 2
--pss-  42.0


Secondary:
NameID   Mem VCPUsState
Time(s)
Domain-0 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 the bound between eth1 and br1 , but apparently nothing
has changed.

Thanks for your help.

Sadi.


On Fri, Nov 4, 2016 at 3:50 PM, Sadi <sadi...@gmail.com> wrote:

> -- Forwarded message ------
> From: "Sadi" <sadi...@gmail.com>
> Date: Nov 3, 2016 20:34
> Subject: Re: [Xen-devel] Error migrating VM to secondary host using COLO
> replication
> To: "Wen Congyang" <we...@cn.fujitsu.com>
> Cc:
>
> > Hi,
>
> >
> > Thanks for replying. Here is what i got from /var/log/syslog:
> >
> > Nov  3 20:04:07 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: Started LSB:
> Start/stop xenstored and xenconsoled.
> > Nov  3 20:04:10 colob-HP-Compaq-6005-Pro-MT-PC systemd-timesyncd[631]:
> Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
> > Nov  3 20:04:20 colob-HP-Compaq-6005-Pro-MT-PC systemd-timesyncd[631]:
> Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
> > Nov  3 20:04:49 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]:
> session-3.scope: Cannot determine UID from slice user-0.slice
> > Nov  3 20:04:49 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: Started
> Session 3 of user root.
> > Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   (vif2.0-emu): new Tun device (carrier: OFF, driver: 'tun', ifindex:
> 7)
> > Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC systemd-udevd[2063]:
> Could not generate persistent MAC address for vif2.0-emu: No such file or
> directory
> > Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   devices added (path: /sys/devices/virtual/net/vif2.0-emu, iface:
> vif2.0-emu)
> > Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   device added (path: /sys/devices/virtual/net/vif2.0-emu, iface:
> vif2.0-emu): no ifupdown configuration found.
> > Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   (vif2.0): failed to find device 8 'vif2.0' with udev
> > Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   (vif2.0): new Ethernet device (carrier: OFF, driver: 'vif',
> ifindex: 8)
> > Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   devices added (path: /sys/devices/vif-2-0/net/vif2.0, iface:
> vif2.0)
> > Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   device added (path: /sys/devices/vif-2-0/net/vif2.0, iface:
> vif2.0): no ifupdown configuration found.
> > Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   (vif2.0): device state change: unmanaged -> unavailable (reason
> 'managed') [10 20 2]
> > Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.363596]
> IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> > Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.363696]
> IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> > Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root:
> /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/2/0
> > Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
>   (br0): bridge port vif2.0 was attached
> > Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.463896]
> device vif2.0 entered

[Xen-devel] Fwd: Re: Error migrating VM to secondary host using COLO replication

2016-11-04 Thread Sadi

-- Forwarded message --
From: "Sadi" <sadi...@gmail.com>
Date: Nov 3, 2016 20:34
Subject: Re: [Xen-devel] Error migrating VM to secondary host using COLO
replication
To: "Wen Congyang" <we...@cn.fujitsu.com>
Cc:

> Hi,

>
> Thanks for replying. Here is what i got from /var/log/syslog:
>
> Nov  3 20:04:07 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: Started LSB:
Start/stop xenstored and xenconsoled.
> Nov  3 20:04:10 colob-HP-Compaq-6005-Pro-MT-PC systemd-timesyncd[631]:
Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com).
> Nov  3 20:04:20 colob-HP-Compaq-6005-Pro-MT-PC systemd-timesyncd[631]:
Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
> Nov  3 20:04:49 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]:
session-3.scope: Cannot determine UID from slice user-0.slice
> Nov  3 20:04:49 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: Started
Session 3 of user root.
> Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (vif2.0-emu): new Tun device (carrier: OFF, driver: 'tun', ifindex:
7)
> Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC systemd-udevd[2063]: Could
not generate persistent MAC address for vif2.0-emu: No such file or
directory
> Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  devices added (path: /sys/devices/virtual/net/vif2.0-emu, iface:
vif2.0-emu)
> Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  device added (path: /sys/devices/virtual/net/vif2.0-emu, iface:
vif2.0-emu): no ifupdown configuration found.
> Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (vif2.0): failed to find device 8 'vif2.0' with udev
> Nov  3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (vif2.0): new Ethernet device (carrier: OFF, driver: 'vif',
ifindex: 8)
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  devices added (path: /sys/devices/vif-2-0/net/vif2.0, iface: vif2.0)
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  device added (path: /sys/devices/vif-2-0/net/vif2.0, iface:
vif2.0): no ifupdown configuration found.
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (vif2.0): device state change: unmanaged -> unavailable (reason
'managed') [10 20 2]
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.363596]
IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.363696]
IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root:
/etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/2/0
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (br0): bridge port vif2.0 was attached
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.463896]
device vif2.0 entered promiscuous mode
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (vif2.0): enslaved to br0
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.466360]
IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.529006]
ip_tables: (C) 2000-2006 Netfilter Core Team
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.585769]
Bridge firewalling registered
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root:
/etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif2.0,
bridge br0.
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root:
/etc/xen/scripts/vif-bridge: Writing backend/vif/2/0/hotplug-status
connected to xenstore.
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root:
/etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/2/0
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (br0): bridge port vif2.0-emu was attached
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (vif2.0-emu): enslaved to br0
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (vif2.0-emu): link connected
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.693288]
device vif2.0-emu entered promiscuous mode
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.695493]
br0: port 3(vif2.0-emu) entered forwarding state
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [  464.695500]
br0: port 3(vif2.0-emu) entered forwarding state
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root:
/etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif2.0-emu,
bridge br0.
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root:
/etc/xen/scripts/colo-proxy-setup: setup XENBUS_PATH=
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]:
  (br0): bridge port vif2.0-emu was detached
> Nov  3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924

[Xen-devel] Error migrating VM to secondary host using COLO replication

2016-10-27 Thread Sadi

Hello,

I've been trying to set COLO replication to work but i'm stuck on a problem
when migrating de primary VM to secondary host.

I have been following the instructions from this wiki

- http://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping

and this mail thread

 -
http://xen.markmail.org/search/?q=COLO#query:COLO+page:1+mid:fb7wrn62vbks4unn+state:results

I'm anexing the steps i took setting the environment before facing this
problem when executing 'xl remus' command:

>migration target: Ready to receive domain.
>Saving to migration stream new xl format (info 0x3/0x0/2840)
>Loading new save file  (new xl fmt info
0x3/0x0/2840)
>Savefile contains xl domain config in JSON format
>Parsing config from 
>xc: info: Saving domain 2, type x86 HVM
>xc: info: Found x86 HVM domain from Xen 4.7
>xc: info: Restoring domain
>xc: Frames iteration 0 of 5: 1045504/1045504  100%
>xc: Domain now suspended: 0/00%
>libxl: error: libxl_qmp.c:702:libxl__qmp_initialize: Connection error: No
such file or directory
>libxl: error: libxl_colo_restore.c:817:colo_restore_setup_cds_done: COLO:
failed to setup device >for guest with domid 1
>xc: error: Restore failed (38 = Function not implemented): Internal error
>libxl: info: libxl_colo_restore.c:320:libxl__colo_restore_teardown: colo
fails
>libxl: error: libxl_stream_read.c:852:libxl__xc_domain_restore_done:
restoring domain: Function >not implemented
>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: 192.168.2.30

slave:
br0 eth0: 10.20.107.33 binded with eth0
br1: no ip address binded with eth1
eth1: 192.168.1.33
eth2: 192.168.2.33

Eth1 both sides directly connected by cable
Eth2 both sides directly connected by cable

Repositories used:

https://github.com/Pating/colo-proxy/tree/changlox
https://github.com/macrosheep/iptables.git 
https://github.com/torvalds/linux 

https://github.com/wencongyang/xen 

Kernel build instructions followed:

2. Prepare host kernel for Dom0
colo-proxy kernel module need cooperate with linux kernel. You should patch 
kernel with ~/colo-proxy/colo-patch-for-kernel.patch 
-cd ~/colo-proxy/; git checkout 405527cbfa9f
-cd ~/linux/; git checkout v4.0; git am 
~/colo-proxy/colo-patch-for-kernel.patch 
-cp /boot/config-3.0.76-0.11-xen .config; make menuconfig to config your kernel 
support Dom0. Ref: 
http://wiki.xenproject.org/wiki/Mainline_Linux_Kernel_Configs 
-make -j8; make modules_install; make install 
-reboot


COLO-Proxy:

-cd ~/colo-proxy/; git checkout 405527cbfa9f; make; make install

IPTables:

-cd iptables; ./autogen.sh; ./configure --prefix=/usr/ --libdir=/usr/lib64; 
make; make install

XEN:

-./autogen.sh
-./configure --enable-debug 
-touch tools/libxl/libxlu_disk_l.l 
-touch tools/libxl/libxlu_cfg_l.l 
-make dist-xen 
-make dist-tools 
-make install-xen 
-make install-tools 

*i've tried with https://github.com/wencongyang/qemu-xen but got an error with 
qemu when xl creating the VM as follows:

>libxl: error: libxl_qmp.c:287:qmp_handle_error_response: received an error 
>message from QMP server: Could not set password

Qemu

-cd ~/qemu-xen/; git checkout colo-xen-v2

Configured QEMU with script provided at:
http://xen.markmail.org/message/y4jcdqxw2s2labdo?q=COLO#query:COLO+page:1+mid:3lzcuzeokqsqpu4i+state:results

*path_to_xen_source updated according my directory tree.
then..

-make
-make install

Running COLO

*HVM SUSE 64bits

primary:
rm -f /var/log/xen/* 
rm -f /var/lib/xen/userdata-d.* 
service xencommons start 
modprobe nf_conntrack_ipv4 
modprobe xt_PMYCOLO sec_dev=eth1

secondary:
rm -f /var/log/xen/*
rm -f /var/lib/xen/userdata-d.*
service xencommons start
modprobe xt_SECCOLO
active_disk=/mnt/ramfs/active_disk.img
hidden_disk=/mnt/ramfs/hidden_disk.img
local_img=/root/new/SUSE/xenguest.img
tmp_disk_size=`/root/new/pating/qemu-xen/qemu-img info $local_img |grep 
'virtual size' |awk  '{print $3}'`
rm -rf /mnt/ramfs/*
umount /mnt/ramfs/
rm -rf /mnt/ramfs/
mkdir /mnt/ramfs

function create_image()
{
 /root/new/pating/qemu-xen/qemu-img create -f qcow2 $1 $tmp_disk_size
}
function prepare_temp_images()
{
 grep -q "^none /mnt/ramfs ramfs" /proc/mounts
 if [[ $? -ne 0 ]]; then
 mount -t ramfs none /mnt/ramfs/ -o size=2G
 fi

 if [[ ! -e $active_disk ]]; then
 create_image $active_disk
 fi

 if [[ ! -e $hidden_disk ]]; then
 create_image $hidden_disk
 fi
}
prepare_temp_images

primary:

xl create new/SUSE/vm-suse.cfg
xl pause vm-suse
xl remus -c -u vm-suse 192.168.2.33


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

Re: [Xen-devel] Error migrating VM to secondary host using COLO replication

Re: [Xen-devel] Error migrating VM to secondary host using COLO replication

Re: [Xen-devel] Error migrating VM to secondary host using COLO replication

Re: [Xen-devel] Error migrating VM to secondary host using COLO replication

[Xen-devel] Fwd: Re: Error migrating VM to secondary host using COLO replication

[Xen-devel] Error migrating VM to secondary host using COLO replication

6 matches

Site Navigation

Mail list logo

Footer information