---------- 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]: <info> (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]: <info> 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]: <info> 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]: <warn> (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]: <info> (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]: <info> 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]: <info> 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]: <info> (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]: <info> (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]: <info> (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]: <info> (br0): bridge port vif2.0-emu was attached > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (vif2.0-emu): enslaved to br0 > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (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]: <info> (br0): bridge port vif2.0-emu was detached > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (vif2.0-emu): released from master br0 > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 464.765881] device vif2.0-emu left promiscuous mode > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 464.765922] br0: port 3(vif2.0-emu) entered disabled state > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (colobr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 9) > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 464.771631] device vif2.0-emu entered promiscuous mode > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (colobr0): bridge port vif2.0-emu was attached > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (vif2.0-emu): enslaved to colobr0 > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC systemd-udevd[2251]: Could not generate persistent MAC address for colobr0: No such file or directory > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: brctl addif colobr0 eth1 failed > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 464.783326] colobr0: port 1(vif2.0-emu) entered forwarding state > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 464.783351] colobr0: port 1(vif2.0-emu) entered forwarding state > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (colobr0): link connected > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> devices added (path: /sys/devices/virtual/net/colobr0, iface: colobr0) > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> device added (path: /sys/devices/virtual/net/colobr0, iface: colobr0): no ifupdown configuration found. > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (colobr0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (colobr0): detached bridge port vif2.0-emu > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (vif2.0-emu): released from master colobr0 > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (colobr0): link disconnected > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 464.818240] device vif2.0-emu left promiscuous mode > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 464.818254] colobr0: port 1(vif2.0-emu) entered disabled state > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (colobr0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> Device 'colobr0' has no connection; scheduling activate_check in 0 seconds. > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 464.832977] ip6_tables: (C) 2000-2006 Netfilter Core Team > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: Writing /hotplug-status connected to xenstore. > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: Successful colo-proxy-setup setup for vif2.0-emu. vifname: vif2.0-emu, index: 1, forwarddev: eth1, forwardbr: colobr0. > Nov 3 20:04:56 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]: Joining mDNS multicast group on interface vif2.0-emu.IPv6 with address fe80::fcff:ffff:feff:ffff. > Nov 3 20:04:56 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]: New relevant interface vif2.0-emu.IPv6 for mDNS. > Nov 3 20:04:56 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]: Registering new address record for fe80::fcff:ffff:feff:ffff on vif2.0-emu.*. > Nov 3 20:04:59 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]: Received packet from invalid interface. > Nov 3 20:05:00 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]: message repeated 3 times: [ Received packet from invalid interface.] > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: teardown XENBUS_PATH= > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: teardown XENBUS_PATH= > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: brctl delif colobr0 eth1 failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: brctl delif colobr0 eth1 failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: brctl delif colobr0 vif2.0-emu failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: brctl delif colobr0 vif2.0-emu failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: brctl delbr colobr0 failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: brctl delbr colobr0 failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (br0): bridge port vif2.0-emu was attached > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: <info> (vif2.0-emu): enslaved to br0 > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 470.501624] device vif2.0-emu entered promiscuous mode > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 470.501656] br0: port 3(vif2.0-emu) entered forwarding state > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [ 470.501661] br0: port 3(vif2.0-emu) entered forwarding state > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: brctl addif br0 vif2.0-emu failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: rmmod xt_SECCOLO failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: iptables -t mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j SECCOLO --index 1 failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC 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: colobr0. > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC 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 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scripts/colo-proxy-setup: rmmod xt_SECCOLO failed > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC 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: colobr0. > Nov 3 20:05:02 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]: Received packet from invalid interface. > Nov 3 20:05:02 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]: Received packet from invalid interface. > > ... and dmesg: > > [ 464.363596] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready > [ 464.363696] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready > [ 464.463896] device vif2.0 entered promiscuous mode > [ 464.466360] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready > [ 464.529006] ip_tables: (C) 2000-2006 Netfilter Core Team > [ 464.585769] Bridge firewalling registered > [ 464.693288] device vif2.0-emu entered promiscuous mode > [ 464.695493] br0: port 3(vif2.0-emu) entered forwarding state > [ 464.695500] br0: port 3(vif2.0-emu) entered forwarding state > [ 464.765881] device vif2.0-emu left promiscuous mode > [ 464.765922] br0: port 3(vif2.0-emu) entered disabled state > [ 464.771631] device vif2.0-emu entered promiscuous mode > [ 464.783326] colobr0: port 1(vif2.0-emu) entered forwarding state > [ 464.783351] colobr0: port 1(vif2.0-emu) entered forwarding state > [ 464.818240] device vif2.0-emu left promiscuous mode > [ 464.818254] colobr0: port 1(vif2.0-emu) entered disabled state > [ 464.832977] ip6_tables: (C) 2000-2006 Netfilter Core Team > [ 470.501624] device vif2.0-emu entered promiscuous mode > [ 470.501656] br0: port 3(vif2.0-emu) entered forwarding state > [ 470.501661] br0: port 3(vif2.0-emu) entered forwarding state > [ 485.549302] br0: port 3(vif2.0-emu) entered forwarding state > > *These logs are from secondary host. I have not found the qemu logs. > > You have mentioned Qemu, so i reviewed my steps and realized that i've set it in a different way. These were the actually steps: > > qemu: > ./configure --target-list=x86_64-softmmu --enable-gcrypt --enable-kvm > make > make install > > xen > ./autogen.sh > ./configure --enable-debug --enable-githttp --with-system-qemu > make dist > make install > > I have tried many ways to set colo up and ended up a little confused. Sory for that. > > I see a lot of 'invalid interface' in the log. So i review my network topology to. > > In this mail http://xen.markmail.org/search/?q=COLO#query:COLO+page:1+mid:zgz7wrdys5hi6c5s+state:results, the eth1 in the secondary host is not explictly binded with br1. > > The topology in https://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping suggest it. I'm using the second way, binding the interfaces. Is this correct? > > Again, Thanks for yor time, > > Sadi. > > >
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
