From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sadi Subject: Error migrating VM to secondary host using COLO replication Date: Thu, 27 Oct 2016 20:56:34 -0200 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=001a11469ecc4986eb053fe0a729 Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --001a11469ecc4986eb053fe0a729 Content-Type: multipart/alternative; boundary=001a11469ecc4986e5053fe0a727 --001a11469ecc4986e5053fe0a727 Content-Type: text/plain; charset=UTF-8 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/0 0% >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. --001a11469ecc4986e5053fe0a727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I've been trying to set COL= O replication to work but i'm stuck on a problem when migrating de pri= mary VM to secondary host.

I have been following = the instructions from this wiki


<= /div>
and this mail thread


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

=
>migration target: Ready to receive domain.
>Sav= ing to migration stream new xl format (info 0x3/0x0/2840)
>Lo= ading new save file <incoming migration stream> (new xl fmt info 0x3= /0x0/2840)
>Savefile contains xl domain config in JSON format=
>Parsing config from <saved>
>xc: info: S= aving domain 2, type x86 HVM
>xc: info: Found x86 HVM domain = from Xen 4.7
>xc: info: Restoring domain
>xc: Fr= ames iteration 0 of 5: 1045504/1045504 =C2=A0100%
>xc: Domain= now suspended: 0/0 =C2=A0 =C2=A00%
>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
&= gt;xc: error: Restore failed (38 =3D Function not implemented): Internal e= rror
>libxl: info: libxl_colo_restore.c:320:libxl__colo_resto= re_teardown: colo fails
>libxl: error: libxl_stream_read.c:85= 2:libxl__xc_domain_restore_done: restoring domain: Function >not implem= ented
>libxl: info: libxl_colo_restore.c:320:libxl__colo_rest= ore_teardown: colo fails

I'm hoping tha= t someone could provide with directions.

Thanks f= or your time and sory for bad english (not native language).

Sadi.
--001a11469ecc4986e5053fe0a727-- --001a11469ecc4986eb053fe0a729 Content-Type: text/plain; charset=US-ASCII; name="steps.txt" Content-Disposition: attachment; filename="steps.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_iusy9v910 TmV0d29yaw0KDQptYXN0ZXI6DQpicjAgOiAxMC4yMC4xMDcuMzAgYmluZGVkIHdpdGggZXRoMA0K ZXRoMTogMTkyLjE2OC4xLjMwDQpldGgyOiAxOTIuMTY4LjIuMzANCg0Kc2xhdmU6DQpicjAgZXRo MDogMTAuMjAuMTA3LjMzIGJpbmRlZCB3aXRoIGV0aDANCmJyMTogbm8gaXAgYWRkcmVzcyBiaW5k ZWQgd2l0aCBldGgxDQpldGgxOiAxOTIuMTY4LjEuMzMNCmV0aDI6IDE5Mi4xNjguMi4zMw0KDQpF dGgxIGJvdGggc2lkZXMgZGlyZWN0bHkgY29ubmVjdGVkIGJ5IGNhYmxlDQpFdGgyIGJvdGggc2lk ZXMgZGlyZWN0bHkgY29ubmVjdGVkIGJ5IGNhYmxlDQoNClJlcG9zaXRvcmllcyB1c2VkOg0KDQpo dHRwczovL2dpdGh1Yi5jb20vUGF0aW5nL2NvbG8tcHJveHkvdHJlZS9jaGFuZ2xveA0KaHR0cHM6 Ly9naXRodWIuY29tL21hY3Jvc2hlZXAvaXB0YWJsZXMuZ2l0IA0KaHR0cHM6Ly9naXRodWIuY29t L3RvcnZhbGRzL2xpbnV4IA0KDQpodHRwczovL2dpdGh1Yi5jb20vd2VuY29uZ3lhbmcveGVuIA0K DQpLZXJuZWwgYnVpbGQgaW5zdHJ1Y3Rpb25zIGZvbGxvd2VkOg0KDQoyLiBQcmVwYXJlIGhvc3Qg a2VybmVsIGZvciBEb20wDQpjb2xvLXByb3h5IGtlcm5lbCBtb2R1bGUgbmVlZCBjb29wZXJhdGUg d2l0aCBsaW51eCBrZXJuZWwuIFlvdSBzaG91bGQgcGF0Y2gga2VybmVsIHdpdGggfi9jb2xvLXBy b3h5L2NvbG8tcGF0Y2gtZm9yLWtlcm5lbC5wYXRjaCANCi1jZCB+L2NvbG8tcHJveHkvOyBnaXQg Y2hlY2tvdXQgNDA1NTI3Y2JmYTlmDQotY2Qgfi9saW51eC87IGdpdCBjaGVja291dCB2NC4wOyBn aXQgYW0gfi9jb2xvLXByb3h5L2NvbG8tcGF0Y2gtZm9yLWtlcm5lbC5wYXRjaCANCi1jcCAvYm9v dC9jb25maWctMy4wLjc2LTAuMTEteGVuIC5jb25maWc7IG1ha2UgbWVudWNvbmZpZyB0byBjb25m aWcgeW91ciBrZXJuZWwgc3VwcG9ydCBEb20wLiBSZWY6IGh0dHA6Ly93aWtpLnhlbnByb2plY3Qu b3JnL3dpa2kvTWFpbmxpbmVfTGludXhfS2VybmVsX0NvbmZpZ3MgDQotbWFrZSAtajg7IG1ha2Ug bW9kdWxlc19pbnN0YWxsOyBtYWtlIGluc3RhbGwgDQotcmVib290DQoNCg0KQ09MTy1Qcm94eToN Cg0KLWNkIH4vY29sby1wcm94eS87IGdpdCBjaGVja291dCA0MDU1MjdjYmZhOWY7IG1ha2U7IG1h a2UgaW5zdGFsbA0KDQpJUFRhYmxlczoNCg0KLWNkIGlwdGFibGVzOyAuL2F1dG9nZW4uc2g7IC4v Y29uZmlndXJlIC0tcHJlZml4PS91c3IvIC0tbGliZGlyPS91c3IvbGliNjQ7IG1ha2U7IG1ha2Ug aW5zdGFsbA0KDQpYRU46DQoNCi0uL2F1dG9nZW4uc2gNCi0uL2NvbmZpZ3VyZSAtLWVuYWJsZS1k ZWJ1ZyANCi10b3VjaCB0b29scy9saWJ4bC9saWJ4bHVfZGlza19sLmwgDQotdG91Y2ggdG9vbHMv bGlieGwvbGlieGx1X2NmZ19sLmwgDQotbWFrZSBkaXN0LXhlbiANCi1tYWtlIGRpc3QtdG9vbHMg DQotbWFrZSBpbnN0YWxsLXhlbiANCi1tYWtlIGluc3RhbGwtdG9vbHMgDQoNCippJ3ZlIHRyaWVk IHdpdGggaHR0cHM6Ly9naXRodWIuY29tL3dlbmNvbmd5YW5nL3FlbXUteGVuIGJ1dCBnb3QgYW4g ZXJyb3Igd2l0aCBxZW11IHdoZW4geGwgY3JlYXRpbmcgdGhlIFZNIGFzIGZvbGxvd3M6DQoNCj5s aWJ4bDogZXJyb3I6IGxpYnhsX3FtcC5jOjI4NzpxbXBfaGFuZGxlX2Vycm9yX3Jlc3BvbnNlOiBy ZWNlaXZlZCBhbiBlcnJvciBtZXNzYWdlIGZyb20gUU1QIHNlcnZlcjogQ291bGQgbm90IHNldCBw YXNzd29yZA0KDQpRZW11DQoNCi1jZCB+L3FlbXUteGVuLzsgZ2l0IGNoZWNrb3V0IGNvbG8teGVu LXYyDQoNCkNvbmZpZ3VyZWQgUUVNVSB3aXRoIHNjcmlwdCBwcm92aWRlZCBhdDoNCmh0dHA6Ly94 ZW4ubWFya21haWwub3JnL21lc3NhZ2UveTRqY2RxeHcyczJsYWJkbz9xPUNPTE8jcXVlcnk6Q09M TytwYWdlOjErbWlkOjNsemN1emVva3FzcXB1NGkrc3RhdGU6cmVzdWx0cw0KDQoqcGF0aF90b194 ZW5fc291cmNlIHVwZGF0ZWQgYWNjb3JkaW5nIG15IGRpcmVjdG9yeSB0cmVlLg0KdGhlbi4uDQoN Ci1tYWtlDQotbWFrZSBpbnN0YWxsDQoNClJ1bm5pbmcgQ09MTw0KDQoqSFZNIFNVU0UgNjRiaXRz DQoNCnByaW1hcnk6DQpybSAtZiAvdmFyL2xvZy94ZW4vKiANCnJtIC1mIC92YXIvbGliL3hlbi91 c2VyZGF0YS1kLiogDQpzZXJ2aWNlIHhlbmNvbW1vbnMgc3RhcnQgDQptb2Rwcm9iZSBuZl9jb25u dHJhY2tfaXB2NCANCm1vZHByb2JlIHh0X1BNWUNPTE8gc2VjX2Rldj1ldGgxDQoNCnNlY29uZGFy eToNCnJtIC1mIC92YXIvbG9nL3hlbi8qDQpybSAtZiAvdmFyL2xpYi94ZW4vdXNlcmRhdGEtZC4q DQpzZXJ2aWNlIHhlbmNvbW1vbnMgc3RhcnQNCm1vZHByb2JlIHh0X1NFQ0NPTE8NCmFjdGl2ZV9k aXNrPS9tbnQvcmFtZnMvYWN0aXZlX2Rpc2suaW1nDQpoaWRkZW5fZGlzaz0vbW50L3JhbWZzL2hp ZGRlbl9kaXNrLmltZw0KbG9jYWxfaW1nPS9yb290L25ldy9TVVNFL3hlbmd1ZXN0LmltZw0KdG1w X2Rpc2tfc2l6ZT1gL3Jvb3QvbmV3L3BhdGluZy9xZW11LXhlbi9xZW11LWltZyBpbmZvICRsb2Nh bF9pbWcgfGdyZXAgJ3ZpcnR1YWwgc2l6ZScgfGF3ayAgJ3twcmludCAkM30nYA0Kcm0gLXJmIC9t bnQvcmFtZnMvKg0KdW1vdW50IC9tbnQvcmFtZnMvDQpybSAtcmYgL21udC9yYW1mcy8NCm1rZGly IC9tbnQvcmFtZnMNCg0KZnVuY3Rpb24gY3JlYXRlX2ltYWdlKCkNCnsNCiAgICAgL3Jvb3QvbmV3 L3BhdGluZy9xZW11LXhlbi9xZW11LWltZyBjcmVhdGUgLWYgcWNvdzIgJDEgJHRtcF9kaXNrX3Np emUNCn0NCmZ1bmN0aW9uIHByZXBhcmVfdGVtcF9pbWFnZXMoKQ0Kew0KICAgICBncmVwIC1xICJe bm9uZSAvbW50L3JhbWZzIHJhbWZzIiAvcHJvYy9tb3VudHMNCiAgICAgaWYgW1sgJD8gLW5lIDAg XV07IHRoZW4NCiAgICAgICAgIG1vdW50IC10IHJhbWZzIG5vbmUgL21udC9yYW1mcy8gLW8gc2l6 ZT0yRw0KICAgICBmaQ0KDQogICAgIGlmIFtbICEgLWUgJGFjdGl2ZV9kaXNrIF1dOyB0aGVuDQog ICAgICAgICBjcmVhdGVfaW1hZ2UgJGFjdGl2ZV9kaXNrDQogICAgIGZpDQoNCiAgICAgaWYgW1sg ISAtZSAkaGlkZGVuX2Rpc2sgXV07IHRoZW4NCiAgICAgICAgIGNyZWF0ZV9pbWFnZSAkaGlkZGVu X2Rpc2sNCiAgICAgZmkNCn0NCnByZXBhcmVfdGVtcF9pbWFnZXMNCg0KcHJpbWFyeToNCg0KeGwg Y3JlYXRlIG5ldy9TVVNFL3ZtLXN1c2UuY2ZnDQp4bCBwYXVzZSB2bS1zdXNlDQp4bCByZW11cyAt YyAtdSB2bS1zdXNlIDE5Mi4xNjguMi4zMw0KDQoNCg== --001a11469ecc4986eb053fe0a729 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --001a11469ecc4986eb053fe0a729-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Error migrating VM to secondary host using COLO replication Date: Fri, 28 Oct 2016 12:56:35 -0400 Message-ID: <20161028165635.GA5112@char.us.oracle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Sadi , zhangchen.fnst@cn.fujitsu.com Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org T24gVGh1LCBPY3QgMjcsIDIwMTYgYXQgMDg6NTY6MzRQTSAtMDIwMCwgU2FkaSB3cm90ZToKPiBI ZWxsbywKSGV5IQoKQ0MtaW5nIHJlbGV2YW50IHBlb3BsZS4KPiAKPiBJJ3ZlIGJlZW4gdHJ5aW5n IHRvIHNldCBDT0xPIHJlcGxpY2F0aW9uIHRvIHdvcmsgYnV0IGknbSBzdHVjayBvbiBhIHByb2Js ZW0KPiB3aGVuIG1pZ3JhdGluZyBkZSBwcmltYXJ5IFZNIHRvIHNlY29uZGFyeSBob3N0Lgo+IAo+ IEkgaGF2ZSBiZWVuIGZvbGxvd2luZyB0aGUgaW5zdHJ1Y3Rpb25zIGZyb20gdGhpcyB3aWtpCj4g Cj4gLSBodHRwOi8vd2lraS54ZW5wcm9qZWN0Lm9yZy93aWtpL0NPTE9fLV9Db2Fyc2VfR3JhaW5f TG9ja19TdGVwcGluZwo+IAo+IGFuZCB0aGlzIG1haWwgdGhyZWFkCj4gCj4gIC0KPiBodHRwOi8v eGVuLm1hcmttYWlsLm9yZy9zZWFyY2gvP3E9Q09MTyNxdWVyeTpDT0xPK3BhZ2U6MSttaWQ6ZmI3 d3JuNjJ2YmtzNHVubitzdGF0ZTpyZXN1bHRzCj4gCj4gSSdtIGFuZXhpbmcgdGhlIHN0ZXBzIGkg dG9vayBzZXR0aW5nIHRoZSBlbnZpcm9ubWVudCBiZWZvcmUgZmFjaW5nIHRoaXMKPiBwcm9ibGVt IHdoZW4gZXhlY3V0aW5nICd4bCByZW11cycgY29tbWFuZDoKPiAKPiA+bWlncmF0aW9uIHRhcmdl dDogUmVhZHkgdG8gcmVjZWl2ZSBkb21haW4uCj4gPlNhdmluZyB0byBtaWdyYXRpb24gc3RyZWFt IG5ldyB4bCBmb3JtYXQgKGluZm8gMHgzLzB4MC8yODQwKQo+ID5Mb2FkaW5nIG5ldyBzYXZlIGZp bGUgPGluY29taW5nIG1pZ3JhdGlvbiBzdHJlYW0+IChuZXcgeGwgZm10IGluZm8KPiAweDMvMHgw LzI4NDApCj4gPlNhdmVmaWxlIGNvbnRhaW5zIHhsIGRvbWFpbiBjb25maWcgaW4gSlNPTiBmb3Jt YXQKPiA+UGFyc2luZyBjb25maWcgZnJvbSA8c2F2ZWQ+Cj4gPnhjOiBpbmZvOiBTYXZpbmcgZG9t YWluIDIsIHR5cGUgeDg2IEhWTQo+ID54YzogaW5mbzogRm91bmQgeDg2IEhWTSBkb21haW4gZnJv bSBYZW4gNC43Cj4gPnhjOiBpbmZvOiBSZXN0b3JpbmcgZG9tYWluCj4gPnhjOiBGcmFtZXMgaXRl cmF0aW9uIDAgb2YgNTogMTA0NTUwNC8xMDQ1NTA0ICAxMDAlCj4gPnhjOiBEb21haW4gbm93IHN1 c3BlbmRlZDogMC8wICAgIDAlCj4gPmxpYnhsOiBlcnJvcjogbGlieGxfcW1wLmM6NzAyOmxpYnhs X19xbXBfaW5pdGlhbGl6ZTogQ29ubmVjdGlvbiBlcnJvcjogTm8KPiBzdWNoIGZpbGUgb3IgZGly ZWN0b3J5Cj4gPmxpYnhsOiBlcnJvcjogbGlieGxfY29sb19yZXN0b3JlLmM6ODE3OmNvbG9fcmVz dG9yZV9zZXR1cF9jZHNfZG9uZTogQ09MTzoKPiBmYWlsZWQgdG8gc2V0dXAgZGV2aWNlID5mb3Ig Z3Vlc3Qgd2l0aCBkb21pZCAxCj4gPnhjOiBlcnJvcjogUmVzdG9yZSBmYWlsZWQgKDM4ID0gRnVu Y3Rpb24gbm90IGltcGxlbWVudGVkKTogSW50ZXJuYWwgZXJyb3IKPiA+bGlieGw6IGluZm86IGxp YnhsX2NvbG9fcmVzdG9yZS5jOjMyMDpsaWJ4bF9fY29sb19yZXN0b3JlX3RlYXJkb3duOiBjb2xv Cj4gZmFpbHMKPiA+bGlieGw6IGVycm9yOiBsaWJ4bF9zdHJlYW1fcmVhZC5jOjg1MjpsaWJ4bF9f eGNfZG9tYWluX3Jlc3RvcmVfZG9uZToKPiByZXN0b3JpbmcgZG9tYWluOiBGdW5jdGlvbiA+bm90 IGltcGxlbWVudGVkCj4gPmxpYnhsOiBpbmZvOiBsaWJ4bF9jb2xvX3Jlc3RvcmUuYzozMjA6bGli eGxfX2NvbG9fcmVzdG9yZV90ZWFyZG93bjogY29sbwo+IGZhaWxzCj4gCj4gSSdtIGhvcGluZyB0 aGF0IHNvbWVvbmUgY291bGQgcHJvdmlkZSB3aXRoIGRpcmVjdGlvbnMuCj4gCj4gVGhhbmtzIGZv ciB5b3VyIHRpbWUgYW5kIHNvcnkgZm9yIGJhZCBlbmdsaXNoIChub3QgbmF0aXZlIGxhbmd1YWdl KS4KPiAKPiAKPiBTYWRpLgoKPiBOZXR3b3JrCj4gCj4gbWFzdGVyOgo+IGJyMCA6IDEwLjIwLjEw Ny4zMCBiaW5kZWQgd2l0aCBldGgwCj4gZXRoMTogMTkyLjE2OC4xLjMwCj4gZXRoMjogMTkyLjE2 OC4yLjMwCj4gCj4gc2xhdmU6Cj4gYnIwIGV0aDA6IDEwLjIwLjEwNy4zMyBiaW5kZWQgd2l0aCBl dGgwCj4gYnIxOiBubyBpcCBhZGRyZXNzIGJpbmRlZCB3aXRoIGV0aDEKPiBldGgxOiAxOTIuMTY4 LjEuMzMKPiBldGgyOiAxOTIuMTY4LjIuMzMKPiAKPiBFdGgxIGJvdGggc2lkZXMgZGlyZWN0bHkg Y29ubmVjdGVkIGJ5IGNhYmxlCj4gRXRoMiBib3RoIHNpZGVzIGRpcmVjdGx5IGNvbm5lY3RlZCBi eSBjYWJsZQo+IAo+IFJlcG9zaXRvcmllcyB1c2VkOgo+IAo+IGh0dHBzOi8vZ2l0aHViLmNvbS9Q YXRpbmcvY29sby1wcm94eS90cmVlL2NoYW5nbG94Cj4gaHR0cHM6Ly9naXRodWIuY29tL21hY3Jv c2hlZXAvaXB0YWJsZXMuZ2l0IAo+IGh0dHBzOi8vZ2l0aHViLmNvbS90b3J2YWxkcy9saW51eCAK PiAKPiBodHRwczovL2dpdGh1Yi5jb20vd2VuY29uZ3lhbmcveGVuIAo+IAo+IEtlcm5lbCBidWls ZCBpbnN0cnVjdGlvbnMgZm9sbG93ZWQ6Cj4gCj4gMi4gUHJlcGFyZSBob3N0IGtlcm5lbCBmb3Ig RG9tMAo+IGNvbG8tcHJveHkga2VybmVsIG1vZHVsZSBuZWVkIGNvb3BlcmF0ZSB3aXRoIGxpbnV4 IGtlcm5lbC4gWW91IHNob3VsZCBwYXRjaCBrZXJuZWwgd2l0aCB+L2NvbG8tcHJveHkvY29sby1w YXRjaC1mb3Ita2VybmVsLnBhdGNoIAo+IC1jZCB+L2NvbG8tcHJveHkvOyBnaXQgY2hlY2tvdXQg NDA1NTI3Y2JmYTlmCj4gLWNkIH4vbGludXgvOyBnaXQgY2hlY2tvdXQgdjQuMDsgZ2l0IGFtIH4v Y29sby1wcm94eS9jb2xvLXBhdGNoLWZvci1rZXJuZWwucGF0Y2ggCj4gLWNwIC9ib290L2NvbmZp Zy0zLjAuNzYtMC4xMS14ZW4gLmNvbmZpZzsgbWFrZSBtZW51Y29uZmlnIHRvIGNvbmZpZyB5b3Vy IGtlcm5lbCBzdXBwb3J0IERvbTAuIFJlZjogaHR0cDovL3dpa2kueGVucHJvamVjdC5vcmcvd2lr aS9NYWlubGluZV9MaW51eF9LZXJuZWxfQ29uZmlncyAKPiAtbWFrZSAtajg7IG1ha2UgbW9kdWxl c19pbnN0YWxsOyBtYWtlIGluc3RhbGwgCj4gLXJlYm9vdAo+IAo+IAo+IENPTE8tUHJveHk6Cj4g Cj4gLWNkIH4vY29sby1wcm94eS87IGdpdCBjaGVja291dCA0MDU1MjdjYmZhOWY7IG1ha2U7IG1h a2UgaW5zdGFsbAo+IAo+IElQVGFibGVzOgo+IAo+IC1jZCBpcHRhYmxlczsgLi9hdXRvZ2VuLnNo OyAuL2NvbmZpZ3VyZSAtLXByZWZpeD0vdXNyLyAtLWxpYmRpcj0vdXNyL2xpYjY0OyBtYWtlOyBt YWtlIGluc3RhbGwKPiAKPiBYRU46Cj4gCj4gLS4vYXV0b2dlbi5zaAo+IC0uL2NvbmZpZ3VyZSAt LWVuYWJsZS1kZWJ1ZyAKPiAtdG91Y2ggdG9vbHMvbGlieGwvbGlieGx1X2Rpc2tfbC5sIAo+IC10 b3VjaCB0b29scy9saWJ4bC9saWJ4bHVfY2ZnX2wubCAKPiAtbWFrZSBkaXN0LXhlbiAKPiAtbWFr ZSBkaXN0LXRvb2xzIAo+IC1tYWtlIGluc3RhbGwteGVuIAo+IC1tYWtlIGluc3RhbGwtdG9vbHMg Cj4gCj4gKmkndmUgdHJpZWQgd2l0aCBodHRwczovL2dpdGh1Yi5jb20vd2VuY29uZ3lhbmcvcWVt dS14ZW4gYnV0IGdvdCBhbiBlcnJvciB3aXRoIHFlbXUgd2hlbiB4bCBjcmVhdGluZyB0aGUgVk0g YXMgZm9sbG93czoKPiAKPiA+bGlieGw6IGVycm9yOiBsaWJ4bF9xbXAuYzoyODc6cW1wX2hhbmRs ZV9lcnJvcl9yZXNwb25zZTogcmVjZWl2ZWQgYW4gZXJyb3IgbWVzc2FnZSBmcm9tIFFNUCBzZXJ2 ZXI6IENvdWxkIG5vdCBzZXQgcGFzc3dvcmQKPiAKPiBRZW11Cj4gCj4gLWNkIH4vcWVtdS14ZW4v OyBnaXQgY2hlY2tvdXQgY29sby14ZW4tdjIKPiAKPiBDb25maWd1cmVkIFFFTVUgd2l0aCBzY3Jp cHQgcHJvdmlkZWQgYXQ6Cj4gaHR0cDovL3hlbi5tYXJrbWFpbC5vcmcvbWVzc2FnZS95NGpjZHF4 dzJzMmxhYmRvP3E9Q09MTyNxdWVyeTpDT0xPK3BhZ2U6MSttaWQ6M2x6Y3V6ZW9rcXNxcHU0aStz dGF0ZTpyZXN1bHRzCj4gCj4gKnBhdGhfdG9feGVuX3NvdXJjZSB1cGRhdGVkIGFjY29yZGluZyBt eSBkaXJlY3RvcnkgdHJlZS4KPiB0aGVuLi4KPiAKPiAtbWFrZQo+IC1tYWtlIGluc3RhbGwKPiAK PiBSdW5uaW5nIENPTE8KPiAKPiAqSFZNIFNVU0UgNjRiaXRzCj4gCj4gcHJpbWFyeToKPiBybSAt ZiAvdmFyL2xvZy94ZW4vKiAKPiBybSAtZiAvdmFyL2xpYi94ZW4vdXNlcmRhdGEtZC4qIAo+IHNl cnZpY2UgeGVuY29tbW9ucyBzdGFydCAKPiBtb2Rwcm9iZSBuZl9jb25udHJhY2tfaXB2NCAKPiBt b2Rwcm9iZSB4dF9QTVlDT0xPIHNlY19kZXY9ZXRoMQo+IAo+IHNlY29uZGFyeToKPiBybSAtZiAv dmFyL2xvZy94ZW4vKgo+IHJtIC1mIC92YXIvbGliL3hlbi91c2VyZGF0YS1kLioKPiBzZXJ2aWNl IHhlbmNvbW1vbnMgc3RhcnQKPiBtb2Rwcm9iZSB4dF9TRUNDT0xPCj4gYWN0aXZlX2Rpc2s9L21u dC9yYW1mcy9hY3RpdmVfZGlzay5pbWcKPiBoaWRkZW5fZGlzaz0vbW50L3JhbWZzL2hpZGRlbl9k aXNrLmltZwo+IGxvY2FsX2ltZz0vcm9vdC9uZXcvU1VTRS94ZW5ndWVzdC5pbWcKPiB0bXBfZGlz a19zaXplPWAvcm9vdC9uZXcvcGF0aW5nL3FlbXUteGVuL3FlbXUtaW1nIGluZm8gJGxvY2FsX2lt ZyB8Z3JlcCAndmlydHVhbCBzaXplJyB8YXdrICAne3ByaW50ICQzfSdgCj4gcm0gLXJmIC9tbnQv cmFtZnMvKgo+IHVtb3VudCAvbW50L3JhbWZzLwo+IHJtIC1yZiAvbW50L3JhbWZzLwo+IG1rZGly IC9tbnQvcmFtZnMKPiAKPiBmdW5jdGlvbiBjcmVhdGVfaW1hZ2UoKQo+IHsKPiAgICAgIC9yb290 L25ldy9wYXRpbmcvcWVtdS14ZW4vcWVtdS1pbWcgY3JlYXRlIC1mIHFjb3cyICQxICR0bXBfZGlz a19zaXplCj4gfQo+IGZ1bmN0aW9uIHByZXBhcmVfdGVtcF9pbWFnZXMoKQo+IHsKPiAgICAgIGdy ZXAgLXEgIl5ub25lIC9tbnQvcmFtZnMgcmFtZnMiIC9wcm9jL21vdW50cwo+ICAgICAgaWYgW1sg JD8gLW5lIDAgXV07IHRoZW4KPiAgICAgICAgICBtb3VudCAtdCByYW1mcyBub25lIC9tbnQvcmFt ZnMvIC1vIHNpemU9MkcKPiAgICAgIGZpCj4gCj4gICAgICBpZiBbWyAhIC1lICRhY3RpdmVfZGlz ayBdXTsgdGhlbgo+ICAgICAgICAgIGNyZWF0ZV9pbWFnZSAkYWN0aXZlX2Rpc2sKPiAgICAgIGZp Cj4gCj4gICAgICBpZiBbWyAhIC1lICRoaWRkZW5fZGlzayBdXTsgdGhlbgo+ICAgICAgICAgIGNy ZWF0ZV9pbWFnZSAkaGlkZGVuX2Rpc2sKPiAgICAgIGZpCj4gfQo+IHByZXBhcmVfdGVtcF9pbWFn ZXMKPiAKPiBwcmltYXJ5Ogo+IAo+IHhsIGNyZWF0ZSBuZXcvU1VTRS92bS1zdXNlLmNmZwo+IHhs IHBhdXNlIHZtLXN1c2UKPiB4bCByZW11cyAtYyAtdSB2bS1zdXNlIDE5Mi4xNjguMi4zMwo+IAo+ IAoKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhl bi1kZXZlbCBtYWlsaW5nIGxpc3QKPiBYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwo+IGh0dHBzOi8v bGlzdHMueGVuLm9yZy94ZW4tZGV2ZWwKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tZGV2ZWwgbWFpbGluZyBsaXN0Clhlbi1kZXZlbEBsaXN0cy54 ZW4ub3JnCmh0dHBzOi8vbGlzdHMueGVuLm9yZy94ZW4tZGV2ZWwK From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhang Chen Subject: Re: Error migrating VM to secondary host using COLO replication Date: Thu, 3 Nov 2016 14:23:18 +0800 Message-ID: <8e03e21d-7f1f-8c33-685d-6270304a3a56@cn.fujitsu.com> References: <20161028165635.GA5112@char.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; Format="flowed" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: <20161028165635.GA5112@char.us.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Konrad Rzeszutek Wilk , Sadi Cc: Changlong Xie , imhy.yang@gmail.com, Wen Congyang , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org CgpPbiAxMC8yOS8yMDE2IDEyOjU2IEFNLCBLb25yYWQgUnplc3p1dGVrIFdpbGsgd3JvdGU6Cj4g T24gVGh1LCBPY3QgMjcsIDIwMTYgYXQgMDg6NTY6MzRQTSAtMDIwMCwgU2FkaSB3cm90ZToKPj4g SGVsbG8sCj4gSGV5IQo+Cj4gQ0MtaW5nIHJlbGV2YW50IHBlb3BsZS4KCkNDClhpZSBDaGFuZ2xv bmcsIFdlbiBDb25neWFuZyBhbmQgWWFuZyBIb25neWFuZyBvbiB0aGUgQ09MTy1YZW4gd2lraSBm b3IgaGVscC4KClRoYW5rcwpaaGFuZyBDaGVuCgoKPj4gSSd2ZSBiZWVuIHRyeWluZyB0byBzZXQg Q09MTyByZXBsaWNhdGlvbiB0byB3b3JrIGJ1dCBpJ20gc3R1Y2sgb24gYSBwcm9ibGVtCj4+IHdo ZW4gbWlncmF0aW5nIGRlIHByaW1hcnkgVk0gdG8gc2Vjb25kYXJ5IGhvc3QuCj4+Cj4+IEkgaGF2 ZSBiZWVuIGZvbGxvd2luZyB0aGUgaW5zdHJ1Y3Rpb25zIGZyb20gdGhpcyB3aWtpCj4+Cj4+IC0g aHR0cDovL3dpa2kueGVucHJvamVjdC5vcmcvd2lraS9DT0xPXy1fQ29hcnNlX0dyYWluX0xvY2tf U3RlcHBpbmcKPj4KPj4gYW5kIHRoaXMgbWFpbCB0aHJlYWQKPj4KPj4gICAtCj4+IGh0dHA6Ly94 ZW4ubWFya21haWwub3JnL3NlYXJjaC8/cT1DT0xPI3F1ZXJ5OkNPTE8rcGFnZToxK21pZDpmYjd3 cm42MnZia3M0dW5uK3N0YXRlOnJlc3VsdHMKPj4KPj4gSSdtIGFuZXhpbmcgdGhlIHN0ZXBzIGkg dG9vayBzZXR0aW5nIHRoZSBlbnZpcm9ubWVudCBiZWZvcmUgZmFjaW5nIHRoaXMKPj4gcHJvYmxl bSB3aGVuIGV4ZWN1dGluZyAneGwgcmVtdXMnIGNvbW1hbmQ6Cj4+Cj4+PiBtaWdyYXRpb24gdGFy Z2V0OiBSZWFkeSB0byByZWNlaXZlIGRvbWFpbi4KPj4+IFNhdmluZyB0byBtaWdyYXRpb24gc3Ry ZWFtIG5ldyB4bCBmb3JtYXQgKGluZm8gMHgzLzB4MC8yODQwKQo+Pj4gTG9hZGluZyBuZXcgc2F2 ZSBmaWxlIDxpbmNvbWluZyBtaWdyYXRpb24gc3RyZWFtPiAobmV3IHhsIGZtdCBpbmZvCj4+IDB4 My8weDAvMjg0MCkKPj4+IFNhdmVmaWxlIGNvbnRhaW5zIHhsIGRvbWFpbiBjb25maWcgaW4gSlNP TiBmb3JtYXQKPj4+IFBhcnNpbmcgY29uZmlnIGZyb20gPHNhdmVkPgo+Pj4geGM6IGluZm86IFNh dmluZyBkb21haW4gMiwgdHlwZSB4ODYgSFZNCj4+PiB4YzogaW5mbzogRm91bmQgeDg2IEhWTSBk b21haW4gZnJvbSBYZW4gNC43Cj4+PiB4YzogaW5mbzogUmVzdG9yaW5nIGRvbWFpbgo+Pj4geGM6 IEZyYW1lcyBpdGVyYXRpb24gMCBvZiA1OiAxMDQ1NTA0LzEwNDU1MDQgIDEwMCUKPj4+IHhjOiBE b21haW4gbm93IHN1c3BlbmRlZDogMC8wICAgIDAlCj4+PiBsaWJ4bDogZXJyb3I6IGxpYnhsX3Ft cC5jOjcwMjpsaWJ4bF9fcW1wX2luaXRpYWxpemU6IENvbm5lY3Rpb24gZXJyb3I6IE5vCj4+IHN1 Y2ggZmlsZSBvciBkaXJlY3RvcnkKPj4+IGxpYnhsOiBlcnJvcjogbGlieGxfY29sb19yZXN0b3Jl LmM6ODE3OmNvbG9fcmVzdG9yZV9zZXR1cF9jZHNfZG9uZTogQ09MTzoKPj4gZmFpbGVkIHRvIHNl dHVwIGRldmljZSA+Zm9yIGd1ZXN0IHdpdGggZG9taWQgMQo+Pj4geGM6IGVycm9yOiBSZXN0b3Jl IGZhaWxlZCAoMzggPSBGdW5jdGlvbiBub3QgaW1wbGVtZW50ZWQpOiBJbnRlcm5hbCBlcnJvcgo+ Pj4gbGlieGw6IGluZm86IGxpYnhsX2NvbG9fcmVzdG9yZS5jOjMyMDpsaWJ4bF9fY29sb19yZXN0 b3JlX3RlYXJkb3duOiBjb2xvCj4+IGZhaWxzCj4+PiBsaWJ4bDogZXJyb3I6IGxpYnhsX3N0cmVh bV9yZWFkLmM6ODUyOmxpYnhsX194Y19kb21haW5fcmVzdG9yZV9kb25lOgo+PiByZXN0b3Jpbmcg ZG9tYWluOiBGdW5jdGlvbiA+bm90IGltcGxlbWVudGVkCj4+PiBsaWJ4bDogaW5mbzogbGlieGxf Y29sb19yZXN0b3JlLmM6MzIwOmxpYnhsX19jb2xvX3Jlc3RvcmVfdGVhcmRvd246IGNvbG8KPj4g ZmFpbHMKPj4KPj4gSSdtIGhvcGluZyB0aGF0IHNvbWVvbmUgY291bGQgcHJvdmlkZSB3aXRoIGRp cmVjdGlvbnMuCj4+Cj4+IFRoYW5rcyBmb3IgeW91ciB0aW1lIGFuZCBzb3J5IGZvciBiYWQgZW5n bGlzaCAobm90IG5hdGl2ZSBsYW5ndWFnZSkuCj4+Cj4+Cj4+IFNhZGkuCj4+IE5ldHdvcmsKPj4K Pj4gbWFzdGVyOgo+PiBicjAgOiAxMC4yMC4xMDcuMzAgYmluZGVkIHdpdGggZXRoMAo+PiBldGgx OiAxOTIuMTY4LjEuMzAKPj4gZXRoMjogMTkyLjE2OC4yLjMwCj4+Cj4+IHNsYXZlOgo+PiBicjAg ZXRoMDogMTAuMjAuMTA3LjMzIGJpbmRlZCB3aXRoIGV0aDAKPj4gYnIxOiBubyBpcCBhZGRyZXNz IGJpbmRlZCB3aXRoIGV0aDEKPj4gZXRoMTogMTkyLjE2OC4xLjMzCj4+IGV0aDI6IDE5Mi4xNjgu Mi4zMwo+Pgo+PiBFdGgxIGJvdGggc2lkZXMgZGlyZWN0bHkgY29ubmVjdGVkIGJ5IGNhYmxlCj4+ IEV0aDIgYm90aCBzaWRlcyBkaXJlY3RseSBjb25uZWN0ZWQgYnkgY2FibGUKPj4KPj4gUmVwb3Np dG9yaWVzIHVzZWQ6Cj4+Cj4+IGh0dHBzOi8vZ2l0aHViLmNvbS9QYXRpbmcvY29sby1wcm94eS90 cmVlL2NoYW5nbG94Cj4+IGh0dHBzOi8vZ2l0aHViLmNvbS9tYWNyb3NoZWVwL2lwdGFibGVzLmdp dAo+PiBodHRwczovL2dpdGh1Yi5jb20vdG9ydmFsZHMvbGludXgKPj4KPj4gaHR0cHM6Ly9naXRo dWIuY29tL3dlbmNvbmd5YW5nL3hlbgo+Pgo+PiBLZXJuZWwgYnVpbGQgaW5zdHJ1Y3Rpb25zIGZv bGxvd2VkOgo+Pgo+PiAyLiBQcmVwYXJlIGhvc3Qga2VybmVsIGZvciBEb20wCj4+IGNvbG8tcHJv eHkga2VybmVsIG1vZHVsZSBuZWVkIGNvb3BlcmF0ZSB3aXRoIGxpbnV4IGtlcm5lbC4gWW91IHNo b3VsZCBwYXRjaCBrZXJuZWwgd2l0aCB+L2NvbG8tcHJveHkvY29sby1wYXRjaC1mb3Ita2VybmVs LnBhdGNoCj4+IC1jZCB+L2NvbG8tcHJveHkvOyBnaXQgY2hlY2tvdXQgNDA1NTI3Y2JmYTlmCj4+ IC1jZCB+L2xpbnV4LzsgZ2l0IGNoZWNrb3V0IHY0LjA7IGdpdCBhbSB+L2NvbG8tcHJveHkvY29s by1wYXRjaC1mb3Ita2VybmVsLnBhdGNoCj4+IC1jcCAvYm9vdC9jb25maWctMy4wLjc2LTAuMTEt eGVuIC5jb25maWc7IG1ha2UgbWVudWNvbmZpZyB0byBjb25maWcgeW91ciBrZXJuZWwgc3VwcG9y dCBEb20wLiBSZWY6IGh0dHA6Ly93aWtpLnhlbnByb2plY3Qub3JnL3dpa2kvTWFpbmxpbmVfTGlu dXhfS2VybmVsX0NvbmZpZ3MKPj4gLW1ha2UgLWo4OyBtYWtlIG1vZHVsZXNfaW5zdGFsbDsgbWFr ZSBpbnN0YWxsCj4+IC1yZWJvb3QKPj4KPj4KPj4gQ09MTy1Qcm94eToKPj4KPj4gLWNkIH4vY29s by1wcm94eS87IGdpdCBjaGVja291dCA0MDU1MjdjYmZhOWY7IG1ha2U7IG1ha2UgaW5zdGFsbAo+ Pgo+PiBJUFRhYmxlczoKPj4KPj4gLWNkIGlwdGFibGVzOyAuL2F1dG9nZW4uc2g7IC4vY29uZmln dXJlIC0tcHJlZml4PS91c3IvIC0tbGliZGlyPS91c3IvbGliNjQ7IG1ha2U7IG1ha2UgaW5zdGFs bAo+Pgo+PiBYRU46Cj4+Cj4+IC0uL2F1dG9nZW4uc2gKPj4gLS4vY29uZmlndXJlIC0tZW5hYmxl LWRlYnVnCj4+IC10b3VjaCB0b29scy9saWJ4bC9saWJ4bHVfZGlza19sLmwKPj4gLXRvdWNoIHRv b2xzL2xpYnhsL2xpYnhsdV9jZmdfbC5sCj4+IC1tYWtlIGRpc3QteGVuCj4+IC1tYWtlIGRpc3Qt dG9vbHMKPj4gLW1ha2UgaW5zdGFsbC14ZW4KPj4gLW1ha2UgaW5zdGFsbC10b29scwo+Pgo+PiAq aSd2ZSB0cmllZCB3aXRoIGh0dHBzOi8vZ2l0aHViLmNvbS93ZW5jb25neWFuZy9xZW11LXhlbiBi dXQgZ290IGFuIGVycm9yIHdpdGggcWVtdSB3aGVuIHhsIGNyZWF0aW5nIHRoZSBWTSBhcyBmb2xs b3dzOgo+Pgo+Pj4gbGlieGw6IGVycm9yOiBsaWJ4bF9xbXAuYzoyODc6cW1wX2hhbmRsZV9lcnJv cl9yZXNwb25zZTogcmVjZWl2ZWQgYW4gZXJyb3IgbWVzc2FnZSBmcm9tIFFNUCBzZXJ2ZXI6IENv dWxkIG5vdCBzZXQgcGFzc3dvcmQKPj4gUWVtdQo+Pgo+PiAtY2Qgfi9xZW11LXhlbi87IGdpdCBj aGVja291dCBjb2xvLXhlbi12Mgo+Pgo+PiBDb25maWd1cmVkIFFFTVUgd2l0aCBzY3JpcHQgcHJv dmlkZWQgYXQ6Cj4+IGh0dHA6Ly94ZW4ubWFya21haWwub3JnL21lc3NhZ2UveTRqY2RxeHcyczJs YWJkbz9xPUNPTE8jcXVlcnk6Q09MTytwYWdlOjErbWlkOjNsemN1emVva3FzcXB1NGkrc3RhdGU6 cmVzdWx0cwo+Pgo+PiAqcGF0aF90b194ZW5fc291cmNlIHVwZGF0ZWQgYWNjb3JkaW5nIG15IGRp cmVjdG9yeSB0cmVlLgo+PiB0aGVuLi4KPj4KPj4gLW1ha2UKPj4gLW1ha2UgaW5zdGFsbAo+Pgo+ PiBSdW5uaW5nIENPTE8KPj4KPj4gKkhWTSBTVVNFIDY0Yml0cwo+Pgo+PiBwcmltYXJ5Ogo+PiBy bSAtZiAvdmFyL2xvZy94ZW4vKgo+PiBybSAtZiAvdmFyL2xpYi94ZW4vdXNlcmRhdGEtZC4qCj4+ IHNlcnZpY2UgeGVuY29tbW9ucyBzdGFydAo+PiBtb2Rwcm9iZSBuZl9jb25udHJhY2tfaXB2NAo+ PiBtb2Rwcm9iZSB4dF9QTVlDT0xPIHNlY19kZXY9ZXRoMQo+Pgo+PiBzZWNvbmRhcnk6Cj4+IHJt IC1mIC92YXIvbG9nL3hlbi8qCj4+IHJtIC1mIC92YXIvbGliL3hlbi91c2VyZGF0YS1kLioKPj4g c2VydmljZSB4ZW5jb21tb25zIHN0YXJ0Cj4+IG1vZHByb2JlIHh0X1NFQ0NPTE8KPj4gYWN0aXZl X2Rpc2s9L21udC9yYW1mcy9hY3RpdmVfZGlzay5pbWcKPj4gaGlkZGVuX2Rpc2s9L21udC9yYW1m cy9oaWRkZW5fZGlzay5pbWcKPj4gbG9jYWxfaW1nPS9yb290L25ldy9TVVNFL3hlbmd1ZXN0Lmlt Zwo+PiB0bXBfZGlza19zaXplPWAvcm9vdC9uZXcvcGF0aW5nL3FlbXUteGVuL3FlbXUtaW1nIGlu Zm8gJGxvY2FsX2ltZyB8Z3JlcCAndmlydHVhbCBzaXplJyB8YXdrICAne3ByaW50ICQzfSdgCj4+ IHJtIC1yZiAvbW50L3JhbWZzLyoKPj4gdW1vdW50IC9tbnQvcmFtZnMvCj4+IHJtIC1yZiAvbW50 L3JhbWZzLwo+PiBta2RpciAvbW50L3JhbWZzCj4+Cj4+IGZ1bmN0aW9uIGNyZWF0ZV9pbWFnZSgp Cj4+IHsKPj4gICAgICAgL3Jvb3QvbmV3L3BhdGluZy9xZW11LXhlbi9xZW11LWltZyBjcmVhdGUg LWYgcWNvdzIgJDEgJHRtcF9kaXNrX3NpemUKPj4gfQo+PiBmdW5jdGlvbiBwcmVwYXJlX3RlbXBf aW1hZ2VzKCkKPj4gewo+PiAgICAgICBncmVwIC1xICJebm9uZSAvbW50L3JhbWZzIHJhbWZzIiAv cHJvYy9tb3VudHMKPj4gICAgICAgaWYgW1sgJD8gLW5lIDAgXV07IHRoZW4KPj4gICAgICAgICAg IG1vdW50IC10IHJhbWZzIG5vbmUgL21udC9yYW1mcy8gLW8gc2l6ZT0yRwo+PiAgICAgICBmaQo+ Pgo+PiAgICAgICBpZiBbWyAhIC1lICRhY3RpdmVfZGlzayBdXTsgdGhlbgo+PiAgICAgICAgICAg Y3JlYXRlX2ltYWdlICRhY3RpdmVfZGlzawo+PiAgICAgICBmaQo+Pgo+PiAgICAgICBpZiBbWyAh IC1lICRoaWRkZW5fZGlzayBdXTsgdGhlbgo+PiAgICAgICAgICAgY3JlYXRlX2ltYWdlICRoaWRk ZW5fZGlzawo+PiAgICAgICBmaQo+PiB9Cj4+IHByZXBhcmVfdGVtcF9pbWFnZXMKPj4KPj4gcHJp bWFyeToKPj4KPj4geGwgY3JlYXRlIG5ldy9TVVNFL3ZtLXN1c2UuY2ZnCj4+IHhsIHBhdXNlIHZt LXN1c2UKPj4geGwgcmVtdXMgLWMgLXUgdm0tc3VzZSAxOTIuMTY4LjIuMzMKPj4KPj4KPj4gX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPj4gWGVuLWRldmVs IG1haWxpbmcgbGlzdAo+PiBYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwo+PiBodHRwczovL2xpc3Rz Lnhlbi5vcmcveGVuLWRldmVsCj4KPgo+IC4KPgoKLS0gClRoYW5rcwp6aGFuZ2NoZW4KCgoKCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhlbi1kZXZlbCBt YWlsaW5nIGxpc3QKWGVuLWRldmVsQGxpc3RzLnhlbi5vcmcKaHR0cHM6Ly9saXN0cy54ZW4ub3Jn L3hlbi1kZXZlbAo= From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: Error migrating VM to secondary host using COLO replication Date: Thu, 3 Nov 2016 14:33:15 +0800 Message-ID: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Sadi , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org T24gMTAvMjgvMjAxNiAwNjo1NiBBTSwgU2FkaSB3cm90ZToKPiBIZWxsbywKPiAKPiBJJ3ZlIGJl ZW4gdHJ5aW5nIHRvIHNldCBDT0xPIHJlcGxpY2F0aW9uIHRvIHdvcmsgYnV0IGknbSBzdHVjayBv biBhIHByb2JsZW0gd2hlbiBtaWdyYXRpbmcgZGUgcHJpbWFyeSBWTSB0byBzZWNvbmRhcnkgaG9z dC4KPiAKPiBJIGhhdmUgYmVlbiBmb2xsb3dpbmcgdGhlIGluc3RydWN0aW9ucyBmcm9tIHRoaXMg d2lraQo+IAo+IC0gaHR0cDovL3dpa2kueGVucHJvamVjdC5vcmcvd2lraS9DT0xPXy1fQ29hcnNl X0dyYWluX0xvY2tfU3RlcHBpbmcKPiAKPiBhbmQgdGhpcyBtYWlsIHRocmVhZAo+IAo+ICAtIGh0 dHA6Ly94ZW4ubWFya21haWwub3JnL3NlYXJjaC8/cT1DT0xPI3F1ZXJ5OkNPTE8rcGFnZToxK21p ZDpmYjd3cm42MnZia3M0dW5uK3N0YXRlOnJlc3VsdHMKPiAKPiBJJ20gYW5leGluZyB0aGUgc3Rl cHMgaSB0b29rIHNldHRpbmcgdGhlIGVudmlyb25tZW50IGJlZm9yZSBmYWNpbmcgdGhpcyBwcm9i bGVtIHdoZW4gZXhlY3V0aW5nICd4bCByZW11cycgY29tbWFuZDoKClNvcnJ5IGZvciB0aGUgbGF0 ZSByZXBseS4KCj4gCj4+bWlncmF0aW9uIHRhcmdldDogUmVhZHkgdG8gcmVjZWl2ZSBkb21haW4u Cj4+U2F2aW5nIHRvIG1pZ3JhdGlvbiBzdHJlYW0gbmV3IHhsIGZvcm1hdCAoaW5mbyAweDMvMHgw LzI4NDApCj4+TG9hZGluZyBuZXcgc2F2ZSBmaWxlIDxpbmNvbWluZyBtaWdyYXRpb24gc3RyZWFt PiAobmV3IHhsIGZtdCBpbmZvIDB4My8weDAvMjg0MCkKPj5TYXZlZmlsZSBjb250YWlucyB4bCBk b21haW4gY29uZmlnIGluIEpTT04gZm9ybWF0Cj4+UGFyc2luZyBjb25maWcgZnJvbSA8c2F2ZWQ+ Cj4+eGM6IGluZm86IFNhdmluZyBkb21haW4gMiwgdHlwZSB4ODYgSFZNCj4+eGM6IGluZm86IEZv dW5kIHg4NiBIVk0gZG9tYWluIGZyb20gWGVuIDQuNwo+PnhjOiBpbmZvOiBSZXN0b3JpbmcgZG9t YWluCj4+eGM6IEZyYW1lcyBpdGVyYXRpb24gMCBvZiA1OiAxMDQ1NTA0LzEwNDU1MDQgIDEwMCUK Pj54YzogRG9tYWluIG5vdyBzdXNwZW5kZWQ6IDAvMCAgICAwJQo+PmxpYnhsOiBlcnJvcjogbGli eGxfcW1wLmM6NzAyOmxpYnhsX19xbXBfaW5pdGlhbGl6ZTogQ29ubmVjdGlvbiBlcnJvcjogTm8g c3VjaCBmaWxlIG9yIGRpcmVjdG9yeQo+PmxpYnhsOiBlcnJvcjogbGlieGxfY29sb19yZXN0b3Jl LmM6ODE3OmNvbG9fcmVzdG9yZV9zZXR1cF9jZHNfZG9uZTogQ09MTzogZmFpbGVkIHRvIHNldHVw IGRldmljZSA+Zm9yIGd1ZXN0IHdpdGggZG9taWQgMQoKQWNjb3JkaW5nIHRvIHRoZSBsb2csIHdl IGNhbm5vdCBjb25uZWN0IHRvIHRoZSBzZWNvbmRhcnkgcWVtdS4gQ2FuIHlvdSBnaXZlIHRoZSBz ZWNvbmRyeSBxZW11IGxvZz8KClRoYW5rcwpXZW4gQ29uZ3lhbmcKCj4+eGM6IGVycm9yOiBSZXN0 b3JlIGZhaWxlZCAoMzggPSBGdW5jdGlvbiBub3QgaW1wbGVtZW50ZWQpOiBJbnRlcm5hbCBlcnJv cgo+PmxpYnhsOiBpbmZvOiBsaWJ4bF9jb2xvX3Jlc3RvcmUuYzozMjA6bGlieGxfX2NvbG9fcmVz dG9yZV90ZWFyZG93bjogY29sbyBmYWlscwo+PmxpYnhsOiBlcnJvcjogbGlieGxfc3RyZWFtX3Jl YWQuYzo4NTI6bGlieGxfX3hjX2RvbWFpbl9yZXN0b3JlX2RvbmU6IHJlc3RvcmluZyBkb21haW46 IEZ1bmN0aW9uID5ub3QgaW1wbGVtZW50ZWQKPj5saWJ4bDogaW5mbzogbGlieGxfY29sb19yZXN0 b3JlLmM6MzIwOmxpYnhsX19jb2xvX3Jlc3RvcmVfdGVhcmRvd246IGNvbG8gZmFpbHMKPiAKPiBJ J20gaG9waW5nIHRoYXQgc29tZW9uZSBjb3VsZCBwcm92aWRlIHdpdGggZGlyZWN0aW9ucy4KPiAK PiBUaGFua3MgZm9yIHlvdXIgdGltZSBhbmQgc29yeSBmb3IgYmFkIGVuZ2xpc2ggKG5vdCBuYXRp dmUgbGFuZ3VhZ2UpLgo+IAo+IAo+IFNhZGkuCj4gCj4gCj4gX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KPiBYZW4tZGV2ZWwgbWFpbGluZyBsaXN0Cj4gWGVu LWRldmVsQGxpc3RzLnhlbi5vcmcKPiBodHRwczovL2xpc3RzLnhlbi5vcmcveGVuLWRldmVsCj4g CgoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpYZW4t ZGV2ZWwgbWFpbGluZyBsaXN0Clhlbi1kZXZlbEBsaXN0cy54ZW4ub3JnCmh0dHBzOi8vbGlzdHMu eGVuLm9yZy94ZW4tZGV2ZWwK From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sadi Subject: Fwd: Re: Error migrating VM to secondary host using COLO replication Date: Fri, 4 Nov 2016 15:50:13 -0200 Message-ID: References: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8071966358666038931==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============8071966358666038931== Content-Type: multipart/alternative; boundary=089e010d829c75082805407d4e66 --089e010d829c75082805407d4e66 Content-Type: text/plain; charset=UTF-8 ---------- 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: > > 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]: (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]: (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]: (colobr0): 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 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]: (colobr0): link connected > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: devices added (path: /sys/devices/virtual/net/colobr0, iface: colobr0) > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: 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]: (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]: (colobr0): detached bridge port vif2.0-emu > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: (vif2.0-emu): released from master colobr0 > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: (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]: (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]: 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]: (br0): bridge port vif2.0-emu was attached > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: (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. > > > --089e010d829c75082805407d4e66 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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

> Hi,

>
> Thanks for replying. Here is what i got from /var/log/syslog:
>
> Nov=C2=A0 3 20:04:07 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: Starte= d LSB: Start/stop xenstored and xenconsoled.
> Nov=C2=A0 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=C2=A0 3 20:04:20 colob-HP-Compaq-6005-Pro-MT-PC systemd-timesyncd[= 631]: Timed out waiting for reply from 9= 1.189.94.4:123 (ntp.ubuntu.com).<= br> > Nov=C2=A0 3 20:04:49 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: sessio= n-3.scope: Cannot determine UID from slice user-0.slice
> Nov=C2=A0 3 20:04:49 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: Starte= d Session 3 of user root.
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): new Tun device (carrier: OFF, driver: &= #39;tun', ifindex: 7)
> Nov=C2=A0 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 o= r directory
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 devices added (path: /sys/devices/virtual/net/vif2.0-= emu, iface: vif2.0-emu)
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 device added (path: /sys/devices/virtual/net/vif2.0-e= mu, iface: vif2.0-emu): no ifupdown configuration found.
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <warn>=C2=A0 (vif2.0): failed to find device 8 'vif2.0' wi= th udev
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0): new Ethernet device (carrier: OFF, driver: = 'vif', ifindex: 8)
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 devices added (path: /sys/devices/vif-2-0/net/vif2.0,= iface: vif2.0)
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 device added (path: /sys/devices/vif-2-0/net/vif2.0, = iface: vif2.0): no ifupdown configuration found.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0): device state change: unmanaged -> unavai= lable (reason 'managed') [10 20 2]
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.363596] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.363696] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: online type_if=3Dvif XENBUS_PATH=3Dbackend/vif/2/0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (br0): bridge port vif2.0 was attached
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.463896] device vif2.0 entered promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0): enslaved to br0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.466360] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.529006] ip_tables: (C) 2000-2006 Netfilter Core Team
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.585769] Bridge firewalling registered
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: Successful vif-bridge online for vif2.0, bridge br0.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: Writing backend/vif/2/0/hotplug-status connected to xensto= re.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: add type_if=3Dtap XENBUS_PATH=3Dbackend/vif/2/0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (br0): bridge port vif2.0-emu was attached
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): enslaved to br0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): link connected
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.693288] device vif2.0-emu entered promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.695493] br0: port 3(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.695500] br0: port 3(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: Successful vif-bridge add for vif2.0-emu, bridge br0.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: setup XENBUS_PATH=3D
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (br0): bridge port vif2.0-emu was detached
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): released from master br0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.765881] device vif2.0-emu left promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.765922] br0: port 3(vif2.0-emu) entered disabled state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): new Bridge device (carrier: OFF, driver: &= #39;bridge', ifindex: 9)
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.771631] device vif2.0-emu entered promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): bridge port vif2.0-emu was attached
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): enslaved to colobr0
> Nov=C2=A0 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 d= irectory
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl addif colobr0 eth1 failed
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.783326] colobr0: port 1(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.783351] colobr0: port 1(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): link connected
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 devices added (path: /sys/devices/virtual/net/colobr0= , iface: colobr0)
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 device added (path: /sys/devices/virtual/net/colobr0,= iface: colobr0): no ifupdown configuration found.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): device state change: unmanaged -> unava= ilable (reason 'managed') [10 20 2]
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): detached bridge port vif2.0-emu
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): released from master colobr0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): link disconnected
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.818240] device vif2.0-emu left promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.818254] colobr0: port 1(vif2.0-emu) entered disabled state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): device state change: unavailable -> dis= connected (reason 'none') [20 30 0]
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 Device 'colobr0' has no connection; schedulin= g activate_check in 0 seconds.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.832977] ip6_tables: (C) 2000-2006 Netfilter Core Team
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: Writing /hotplug-status connected to xenstore.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: Successful colo-proxy-setup setup for vif2.0-emu.=C2= =A0 vifname: vif2.0-emu, index: 1, forwarddev: eth1,=C2=A0 forwardbr: colob= r0.
> Nov=C2=A0 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 fe= 80::fcff:ffff:feff:ffff.
> Nov=C2=A0 3 20:04:56 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : New relevant interface vif2.0-emu.IPv6 for mDNS.
> Nov=C2=A0 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-em= u.*.
> Nov=C2=A0 3 20:04:59 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : Received packet from invalid interface.
> Nov=C2=A0 3 20:05:00 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : message repeated 3 times: [ Received packet from invalid interface.]
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: teardown XENBUS_PATH=3D
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: teardown XENBUS_PATH=3D
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delif colobr0 eth1 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delif colobr0 eth1 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delif colobr0 vif2.0-emu failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delif colobr0 vif2.0-emu failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delbr colobr0 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delbr colobr0 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (br0): bridge port vif2.0-emu was attached
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): enslaved to br0
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 47= 0.501624] device vif2.0-emu entered promiscuous mode
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 47= 0.501656] br0: port 3(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 47= 0.501661] br0: port 3(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl addif br0 vif2.0-emu failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: rmmod xt_SECCOLO failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: iptables -t mangle -D PREROUTING -m physdev --physde= v-in vif2.0-emu -j SECCOLO --index 1 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: Successful colo-proxy-setup teardown for vif2.0-emu.= =C2=A0 vifname: vif2.0-emu, index: 1, forwarddev: eth1,=C2=A0 forwardbr: co= lobr0.
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: ip6tables -t mangle -D PREROUTING -m physdev --physd= ev-in vif2.0-emu -j SECCOLO --index 1 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: rmmod xt_SECCOLO failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: Successful colo-proxy-setup teardown for vif2.0-emu.= =C2=A0 vifname: vif2.0-emu, index: 1, forwarddev: eth1,=C2=A0 forwardbr: co= lobr0.
> Nov=C2=A0 3 20:05:02 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : Received packet from invalid interface.
> Nov=C2=A0 3 20:05:02 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : Received packet from invalid interface.
>
> ... and dmesg:
>
> [=C2=A0 464.363596] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not rea= dy
> [=C2=A0 464.363696] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not rea= dy
> [=C2=A0 464.463896] device vif2.0 entered promiscuous mode
> [=C2=A0 464.466360] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not rea= dy
> [=C2=A0 464.529006] ip_tables: (C) 2000-2006 Netfilter Core Team
> [=C2=A0 464.585769] Bridge firewalling registered
> [=C2=A0 464.693288] device vif2.0-emu entered promiscuous mode
> [=C2=A0 464.695493] br0: port 3(vif2.0-emu) entered forwarding state > [=C2=A0 464.695500] br0: port 3(vif2.0-emu) entered forwarding state > [=C2=A0 464.765881] device vif2.0-emu left promiscuous mode
> [=C2=A0 464.765922] br0: port 3(vif2.0-emu) entered disabled state
> [=C2=A0 464.771631] device vif2.0-emu entered promiscuous mode
> [=C2=A0 464.783326] colobr0: port 1(vif2.0-emu) entered forwarding sta= te
> [=C2=A0 464.783351] colobr0: port 1(vif2.0-emu) entered forwarding sta= te
> [=C2=A0 464.818240] device vif2.0-emu left promiscuous mode
> [=C2=A0 464.818254] colobr0: port 1(vif2.0-emu) entered disabled state=
> [=C2=A0 464.832977] ip6_tables: (C) 2000-2006 Netfilter Core Team
> [=C2=A0 470.501624] device vif2.0-emu entered promiscuous mode
> [=C2=A0 470.501656] br0: port 3(vif2.0-emu) entered forwarding state > [=C2=A0 470.501661] br0: port 3(vif2.0-emu) entered forwarding state > [=C2=A0 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= 9;ve set it in a different way. These were the actually steps:
>
> qemu:
> ./configure --target-list=3Dx86_64-softmmu=C2=A0 --enable-gcrypt=C2=A0= --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/se= arch/?q=3DCOLO#query:COLO+page:1+mid:zgz7wrdys5hi6c5s+state:results, th= e eth1 in the secondary host is not explictly binded with br1.
>
> The topology in https://wiki.xenproject.org/wiki/COLO_-_Coarse_Gra= in_Lock_Stepping suggest it. I'm using the second way, binding the = interfaces. Is this correct?
>
> Again, Thanks for yor time,
>
> Sadi.
>
>
>

--089e010d829c75082805407d4e66-- --===============8071966358666038931== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============8071966358666038931==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sadi Subject: Re: Error migrating VM to secondary host using COLO replication Date: Mon, 7 Nov 2016 18:37:30 -0200 Message-ID: References: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6784382393150124089==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: xen-devel@lists.xen.org, Wen Congyang List-Id: xen-devel@lists.xenproject.org --===============6784382393150124089== Content-Type: multipart/alternative; boundary=001a114a61782f346b0540bbfe9a --001a114a61782f346b0540bbfe9a Content-Type: text/plain; charset=UTF-8 Hi, I've noticed that in the /etc/xen/scripts/colo-proxy-setup the forward bridge was configured to colobr0. So, i've updated the script to use br1 and the situation seems to get a little bether. In Primary host, after executing 'xl remus' command the error is still the same: 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: Frames iteration 1 of 5: 1024/1024 100% xc: Domain now suspended: 0/0 0% 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 2 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 Looking in the secondary host's syslog, it seems that the secondary host has understood that the primary one has failed. So it assumes the handle of the machine entering the network topology "after failover" especified in https://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping. Secondary host's syslog: Nov 7 18:10:13 colob systemd[1]: session-3.scope: Cannot determine UID from slice user-0.slice Nov 7 18:10:13 colob systemd[1]: Started Session 3 of user root. Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0-emu): new Tun device (carrier: OFF, driver: 'tun', ifindex: 6) Nov 7 18:10:24 colob systemd-udevd[1917]: Could not generate persistent MAC address for vif2.0-emu: No such file or directory Nov 7 18:10:24 colob NetworkManager[907]: devices added (path: /sys/devices/virtual/net/vif2.0-emu, iface: vif2.0-emu) Nov 7 18:10:24 colob NetworkManager[907]: device added (path: /sys/devices/virtual/net/vif2.0-emu, iface: vif2.0-emu): no ifupdown configuration found. Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0): failed to find device 7 'vif2.0' with udev Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0): new Ethernet device (carrier: OFF, driver: 'vif', ifindex: 7) Nov 7 18:10:24 colob NetworkManager[907]: devices added (path: /sys/devices/vif-2-0/net/vif2.0, iface: vif2.0) Nov 7 18:10:24 colob NetworkManager[907]: device added (path: /sys/devices/vif-2-0/net/vif2.0, iface: vif2.0): no ifupdown configuration found. Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Nov 7 18:10:24 colob kernel: [ 604.313326] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready Nov 7 18:10:24 colob kernel: [ 604.313426] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready Nov 7 18:10:24 colob root: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/2/0 Nov 7 18:10:24 colob NetworkManager[907]: (br0): bridge port vif2.0 was attached Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0): enslaved to br0 Nov 7 18:10:24 colob kernel: [ 604.405016] device vif2.0 entered promiscuous mode Nov 7 18:10:24 colob kernel: [ 604.407207] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready Nov 7 18:10:24 colob kernel: [ 604.470129] ip_tables: (C) 2000-2006 Netfilter Core Team Nov 7 18:10:24 colob kernel: [ 604.526929] Bridge firewalling registered Nov 7 18:10:24 colob root: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif2.0, bridge br0. Nov 7 18:10:24 colob root: /etc/xen/scripts/vif-bridge: Writing backend/vif/2/0/hotplug-status connected to xenstore. Nov 7 18:10:24 colob root: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=backend/vif/2/0 Nov 7 18:10:24 colob NetworkManager[907]: (br0): bridge port vif2.0-emu was attached Nov 7 18:10:24 colob kernel: [ 604.634201] device vif2.0-emu entered promiscuous mode Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0-emu): enslaved to br0 Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0-emu): link connected Nov 7 18:10:24 colob kernel: [ 604.636443] br0: port 3(vif2.0-emu) entered forwarding state Nov 7 18:10:24 colob kernel: [ 604.636463] br0: port 3(vif2.0-emu) entered forwarding state Nov 7 18:10:24 colob root: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif2.0-emu, bridge br0. Nov 7 18:10:24 colob root: /etc/xen/scripts/colo-proxy-setup: setup XENBUS_PATH= Nov 7 18:10:24 colob NetworkManager[907]: (br0): bridge port vif2.0-emu was detached Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0-emu): released from master br0 Nov 7 18:10:24 colob kernel: [ 604.721085] device vif2.0-emu left promiscuous mode Nov 7 18:10:24 colob kernel: [ 604.721122] br0: port 3(vif2.0-emu) entered disabled state Nov 7 18:10:24 colob NetworkManager[907]: (br1): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 8) Nov 7 18:10:24 colob kernel: [ 604.726401] device vif2.0-emu entered promiscuous mode Nov 7 18:10:24 colob NetworkManager[907]: (br1): bridge port vif2.0-emu was attached Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0-emu): enslaved to br1 Nov 7 18:10:24 colob systemd-udevd[2102]: Could not generate persistent MAC address for br1: No such file or directory Nov 7 18:10:24 colob NetworkManager[907]: (br1): bridge port eth1 was attached Nov 7 18:10:24 colob kernel: [ 604.730047] device eth1 entered promiscuous mode Nov 7 18:10:24 colob NetworkManager[907]: (eth1): enslaved to br1 Nov 7 18:10:24 colob NetworkManager[907]: (br1): link connected Nov 7 18:10:24 colob kernel: [ 604.732580] br1: port 2(eth1) entered forwarding state Nov 7 18:10:24 colob kernel: [ 604.732605] br1: port 2(eth1) entered forwarding state Nov 7 18:10:24 colob kernel: [ 604.732610] br1: port 1(vif2.0-emu) entered forwarding state Nov 7 18:10:24 colob kernel: [ 604.732613] br1: port 1(vif2.0-emu) entered forwarding state Nov 7 18:10:24 colob kernel: [ 604.774105] ip6_tables: (C) 2000-2006 Netfilter Core Team Nov 7 18:10:24 colob systemd[1]: Started ifup for br1. Nov 7 18:10:24 colob root: /etc/xen/scripts/colo-proxy-setup: Writing /hotplug-status connected to xenstore. Nov 7 18:10:24 colob NetworkManager[907]: devices added (path: /sys/devices/virtual/net/br1, iface: br1) Nov 7 18:10:24 colob NetworkManager[907]: device added (path: /sys/devices/virtual/net/br1, iface: br1): no ifupdown configuration found. Nov 7 18:10:24 colob NetworkManager[907]: (br1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Nov 7 18:10:24 colob kernel: [ 604.785960] device vif2.0-emu left promiscuous mode Nov 7 18:10:24 colob kernel: [ 604.785973] br1: port 1(vif2.0-emu) entered disabled state Nov 7 18:10:24 colob systemd[1]: Found device /sys/subsystem/net/devices/br1. Nov 7 18:10:24 colob NetworkManager[907]: (br1): detached bridge port vif2.0-emu Nov 7 18:10:24 colob NetworkManager[907]: (vif2.0-emu): released from master br1 Nov 7 18:10:24 colob NetworkManager[907]: (br1): detached bridge port eth1 Nov 7 18:10:24 colob NetworkManager[907]: (eth1): released from master br1 Nov 7 18:10:24 colob NetworkManager[907]: (br1): link disconnected Nov 7 18:10:24 colob NetworkManager[907]: (br1): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Nov 7 18:10:24 colob kernel: [ 604.787454] device eth1 left promiscuous mode Nov 7 18:10:24 colob kernel: [ 604.787475] br1: port 2(eth1) entered disabled state Nov 7 18:10:24 colob NetworkManager[907]: Device 'br1' has no connection; scheduling activate_check in 0 seconds. Nov 7 18:10:24 colob 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: br1. Nov 7 18:10:25 colob systemd[1]: Reloading OpenBSD Secure Shell server. Nov 7 18:10:25 colob systemd[1]: Reloaded OpenBSD Secure Shell server. Nov 7 18:10:25 colob avahi-daemon[920]: Joining mDNS multicast group on interface vif2.0-emu.IPv6 with address fe80::fcff:ffff:feff:ffff. Nov 7 18:10:25 colob avahi-daemon[920]: New relevant interface vif2.0-emu.IPv6 for mDNS. Nov 7 18:10:25 colob avahi-daemon[920]: Registering new address record for fe80::fcff:ffff:feff:ffff on vif2.0-emu.*. Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: teardown XENBUS_PATH= Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: teardown XENBUS_PATH= Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl delif br1 eth1 failed Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl delif br1 eth1 failed Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl delif br1 vif2.0-emu failed Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl delif br1 vif2.0-emu failed Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl delbr br1 failed Nov 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl delbr br1 failed Nov 7 18:10:30 colob NetworkManager[907]: (br0): bridge port vif2.0-emu was attached Nov 7 18:10:30 colob kernel: [ 610.445938] device vif2.0-emu entered promiscuous mode Nov 7 18:10:30 colob kernel: [ 610.445972] br0: port 3(vif2.0-emu) entered forwarding state Nov 7 18:10:30 colob kernel: [ 610.445977] br0: port 3(vif2.0-emu) 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 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 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: Name ID Mem VCPUs State Time(s) Domain-0 0 2502 4 r----- 65.5 suse-hvm 2 1023 2 --pss- 42.0 Secondary: Name ID Mem VCPUs State 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 wrote: > ---------- 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: > > > > 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]: > (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]: > (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]: > (colobr0): 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 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]: > (colobr0): link connected > > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: > devices added (path: /sys/devices/virtual/net/colobr0, iface: > colobr0) > > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: > 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]: > (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]: > (colobr0): detached bridge port vif2.0-emu > > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: > (vif2.0-emu): released from master colobr0 > > Nov 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: > (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]: > (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]: > 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]: > (br0): bridge port vif2.0-emu was attached > > Nov 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924]: > (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. > > > > > > > -- Sadi. --001a114a61782f346b0540bbfe9a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I've noticed that in the /etc/xen/scripts/colo-proxy= -setup the forward bridge was configured to colobr0. So, i've updated t= he script to use br1 and the situation seems to get a little bether.
In Primary host, after executing 'xl remus' command the erro= r is still the same:

migration target: Ready to receive domain.
S= aving to migration stream new xl format (info 0x3/0x0/2840)
Loading new = save file <incoming migration stream> (new xl fmt info 0x3/0x0/2840)<= br>=C2=A0Savefile contains xl domain config in JSON format
Parsing confi= g from <saved>
xc: info: Saving domain 2, type x86 HVM
xc: info= : Found x86 HVM domain from Xen 4.7
xc: info: Restoring domain
xc: Fr= ames iteration 0 of 5: 1045504/1045504=C2=A0 100%
xc: Frames iteration 1= of 5: 1024/1024=C2=A0 100%=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
xc: Dom= ain now suspended: 0/0=C2=A0=C2=A0=C2=A0 0%
libxl: error: libxl_qmp.c:70= 2:libxl__qmp_initialize: Connection error: No such file or directory
lib= xl: error: libxl_colo_restore.c:817:colo_restore_setup_cds_done: COLO: fail= ed to setup device for guest with domid 2
xc: error: Restore failed (38 = =3D Function not implemented): Internal error
libxl: info: libxl_colo_re= store.c:320:libxl__colo_restore_teardown: colo fails
libxl: error: libxl= _stream_read.c:852:libxl__xc_domain_restore_done: restoring domain: Functio= n not implemented
libxl: info: libxl_colo_restore.c:320:libxl__colo_rest= ore_teardown: colo fails


Looking in the secondary host'= ;s syslog, it seems that the secondary host has understood that the primary= one has failed. So it assumes the handle of the machine entering the netwo= rk topology "after failover" especified in https://wiki.xen.org/wiki= /COLO_-_Coarse_Grain_Lock_Stepping.

Secondary host&#= 39;s syslog:

Nov=C2=A0 7 18:10:13 colob systemd[1]: session-3.scope:= Cannot determine UID from slice user-0.slice
Nov=C2=A0 7 18:10:13 colob= systemd[1]: Started Session 3 of user root.
Nov=C2=A0 7 18:10:24 colob = NetworkManager[907]: <info>=C2=A0 (vif2.0-emu): new Tun device (carri= er: OFF, driver: 'tun', ifindex: 6)
Nov=C2=A0 7 18:10:24 colob s= ystemd-udevd[1917]: Could not generate persistent MAC address for vif2.0-em= u: No such file or directory
Nov=C2=A0 7 18:10:24 colob NetworkManager[9= 07]: <info>=C2=A0 devices added (path: /sys/devices/virtual/net/vif2.= 0-emu, iface: vif2.0-emu)
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]= : <info>=C2=A0 device added (path: /sys/devices/virtual/net/vif2.0-em= u, iface: vif2.0-emu): no ifupdown configuration found.
Nov=C2=A0 7 18:1= 0:24 colob NetworkManager[907]: <warn>=C2=A0 (vif2.0): failed to find= device 7 'vif2.0' with udev
Nov=C2=A0 7 18:10:24 colob NetworkM= anager[907]: <info>=C2=A0 (vif2.0): new Ethernet device (carrier: OFF= , driver: 'vif', ifindex: 7)
Nov=C2=A0 7 18:10:24 colob NetworkM= anager[907]: <info>=C2=A0 devices added (path: /sys/devices/vif-2-0/n= et/vif2.0, iface: vif2.0)
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]= : <info>=C2=A0 device added (path: /sys/devices/vif-2-0/net/vif2.0, i= face: vif2.0): no ifupdown configuration found.
Nov=C2=A0 7 18:10:24 col= ob NetworkManager[907]: <info>=C2=A0 (vif2.0): device state change: u= nmanaged -> unavailable (reason 'managed') [10 20 2]
Nov=C2= =A0 7 18:10:24 colob kernel: [=C2=A0 604.313326] IPv6: ADDRCONF(NETDEV_UP):= vif2.0: link is not ready
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0 60= 4.313426] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
Nov=C2=A0= 7 18:10:24 colob root: /etc/xen/scripts/vif-bridge: online type_if=3Dvif X= ENBUS_PATH=3Dbackend/vif/2/0
Nov=C2=A0 7 18:10:24 colob NetworkManager[9= 07]: <info>=C2=A0 (br0): bridge port vif2.0 was attached
Nov=C2=A0= 7 18:10:24 colob NetworkManager[907]: <info>=C2=A0 (vif2.0): enslave= d to br0
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.405016] device v= if2.0 entered promiscuous mode
Nov=C2=A0 7 18:10:24 colob kernel: [=C2= =A0 604.407207] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
Nov= =C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.470129] ip_tables: (C) 2000-200= 6 Netfilter Core Team
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.526= 929] Bridge firewalling registered
Nov=C2=A0 7 18:10:24 colob root: /etc= /xen/scripts/vif-bridge: Successful vif-bridge online for vif2.0, bridge br= 0.
Nov=C2=A0 7 18:10:24 colob root: /etc/xen/scripts/vif-bridge: Writing= backend/vif/2/0/hotplug-status connected to xenstore.
Nov=C2=A0 7 18:10= :24 colob root: /etc/xen/scripts/vif-bridge: add type_if=3Dtap XENBUS_PATH= =3Dbackend/vif/2/0
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]: <i= nfo>=C2=A0 (br0): bridge port vif2.0-emu was attached
Nov=C2=A0 7 18:= 10:24 colob kernel: [=C2=A0 604.634201] device vif2.0-emu entered promiscuo= us mode
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]: <info>=C2= =A0 (vif2.0-emu): enslaved to br0
Nov=C2=A0 7 18:10:24 colob NetworkMana= ger[907]: <info>=C2=A0 (vif2.0-emu): link connected
Nov=C2=A0 7 18= :10:24 colob kernel: [=C2=A0 604.636443] br0: port 3(vif2.0-emu) entered fo= rwarding state
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.636463] br= 0: port 3(vif2.0-emu) entered forwarding state
Nov=C2=A0 7 18:10:24 colo= b root: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for vif2.0-e= mu, bridge br0.
Nov=C2=A0 7 18:10:24 colob root: /etc/xen/scripts/colo-p= roxy-setup: setup XENBUS_PATH=3D
Nov=C2=A0 7 18:10:24 colob NetworkManag= er[907]: <info>=C2=A0 (br0): bridge port vif2.0-emu was detached
N= ov=C2=A0 7 18:10:24 colob NetworkManager[907]: <info>=C2=A0 (vif2.0-e= mu): released from master br0
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0= 604.721085] device vif2.0-emu left promiscuous mode
Nov=C2=A0 7 18:10:2= 4 colob kernel: [=C2=A0 604.721122] br0: port 3(vif2.0-emu) entered disable= d state
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]: <info>=C2= =A0 (br1): new Bridge device (carrier: OFF, driver: 'bridge', ifind= ex: 8)
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.726401] device vif= 2.0-emu entered promiscuous mode
Nov=C2=A0 7 18:10:24 colob NetworkManag= er[907]: <info>=C2=A0 (br1): bridge port vif2.0-emu was attached
N= ov=C2=A0 7 18:10:24 colob NetworkManager[907]: <info>=C2=A0 (vif2.0-e= mu): enslaved to br1
Nov=C2=A0 7 18:10:24 colob systemd-udevd[2102]: Cou= ld not generate persistent MAC address for br1: No such file or directoryNov=C2=A0 7 18:10:24 colob NetworkManager[907]: <info>=C2=A0 (br1):= bridge port eth1 was attached
Nov=C2=A0 7 18:10:24 colob kernel: [=C2= =A0 604.730047] device eth1 entered promiscuous mode
Nov=C2=A0 7 18:10:2= 4 colob NetworkManager[907]: <info>=C2=A0 (eth1): enslaved to br1
= Nov=C2=A0 7 18:10:24 colob NetworkManager[907]: <info>=C2=A0 (br1): l= ink connected
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.732580] br1= : port 2(eth1) entered forwarding state
Nov=C2=A0 7 18:10:24 colob kerne= l: [=C2=A0 604.732605] br1: port 2(eth1) entered forwarding state
Nov=C2= =A0 7 18:10:24 colob kernel: [=C2=A0 604.732610] br1: port 1(vif2.0-emu) en= tered forwarding state
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.73= 2613] br1: port 1(vif2.0-emu) entered forwarding state
Nov=C2=A0 7 18:10= :24 colob kernel: [=C2=A0 604.774105] ip6_tables: (C) 2000-2006 Netfilter C= ore Team
Nov=C2=A0 7 18:10:24 colob systemd[1]: Started ifup for br1.Nov=C2=A0 7 18:10:24 colob root: /etc/xen/scripts/colo-proxy-setup: Writin= g /hotplug-status connected to xenstore.
Nov=C2=A0 7 18:10:24 colob Netw= orkManager[907]: <info>=C2=A0 devices added (path: /sys/devices/virtu= al/net/br1, iface: br1)
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]: = <info>=C2=A0 device added (path: /sys/devices/virtual/net/br1, iface:= br1): no ifupdown configuration found.
Nov=C2=A0 7 18:10:24 colob Netwo= rkManager[907]: <info>=C2=A0 (br1): device state change: unmanaged -&= gt; unavailable (reason 'managed') [10 20 2]
Nov=C2=A0 7 18:10:2= 4 colob kernel: [=C2=A0 604.785960] device vif2.0-emu left promiscuous mode=
Nov=C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.785973] br1: port 1(vif2= .0-emu) entered disabled state
Nov=C2=A0 7 18:10:24 colob systemd[1]: Fo= und device /sys/subsystem/net/devices/br1.
Nov=C2=A0 7 18:10:24 colob Ne= tworkManager[907]: <info>=C2=A0 (br1): detached bridge port vif2.0-em= u
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]: <info>=C2=A0 (vi= f2.0-emu): released from master br1
Nov=C2=A0 7 18:10:24 colob NetworkMa= nager[907]: <info>=C2=A0 (br1): detached bridge port eth1
Nov=C2= =A0 7 18:10:24 colob NetworkManager[907]: <info>=C2=A0 (eth1): releas= ed from master br1
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]: <i= nfo>=C2=A0 (br1): link disconnected
Nov=C2=A0 7 18:10:24 colob Networ= kManager[907]: <info>=C2=A0 (br1): device state change: unavailable -= > disconnected (reason 'none') [20 30 0]
Nov=C2=A0 7 18:10:24= colob kernel: [=C2=A0 604.787454] device eth1 left promiscuous mode
Nov= =C2=A0 7 18:10:24 colob kernel: [=C2=A0 604.787475] br1: port 2(eth1) enter= ed disabled state
Nov=C2=A0 7 18:10:24 colob NetworkManager[907]: <in= fo>=C2=A0 Device 'br1' has no connection; scheduling activate_ch= eck in 0 seconds.
Nov=C2=A0 7 18:10:24 colob root: /etc/xen/scripts/colo= -proxy-setup: Successful colo-proxy-setup setup for vif2.0-emu.=C2=A0 vifna= me: vif2.0-emu, index: 1, forwarddev: eth1,=C2=A0 forwardbr: br1.
Nov=C2= =A0 7 18:10:25 colob systemd[1]: Reloading OpenBSD Secure Shell server.
= Nov=C2=A0 7 18:10:25 colob systemd[1]: Reloaded OpenBSD Secure Shell server= .
Nov=C2=A0 7 18:10:25 colob avahi-daemon[920]: Joining mDNS multicast g= roup on interface vif2.0-emu.IPv6 with address fe80::fcff:ffff:feff:ffff.Nov=C2=A0 7 18:10:25 colob avahi-daemon[920]: New relevant interface vif2= .0-emu.IPv6 for mDNS.
Nov=C2=A0 7 18:10:25 colob avahi-daemon[920]: Regi= stering new address record for fe80::fcff:ffff:feff:ffff on vif2.0-emu.*.Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: teard= own XENBUS_PATH=3D
Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/col= o-proxy-setup: teardown XENBUS_PATH=3D
Nov=C2=A0 7 18:10:30 colob root: = /etc/xen/scripts/colo-proxy-setup: brctl delif br1 eth1 failed
Nov=C2=A0= 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl delif br1 = eth1 failed
Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy= -setup: brctl delif br1 vif2.0-emu failed
Nov=C2=A0 7 18:10:30 colob roo= t: /etc/xen/scripts/colo-proxy-setup: brctl delif br1 vif2.0-emu failed
= Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setup: brctl d= elbr br1 failed
Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-p= roxy-setup: brctl delbr br1 failed
Nov=C2=A0 7 18:10:30 colob NetworkMan= ager[907]: <info>=C2=A0 (br0): bridge port vif2.0-emu was attachedNov=C2=A0 7 18:10:30 colob kernel: [=C2=A0 610.445938] device vif2.0-emu e= ntered promiscuous mode
Nov=C2=A0 7 18:10:30 colob kernel: [=C2=A0 610.4= 45972] br0: port 3(vif2.0-emu) entered forwarding state
Nov=C2=A0 7 18:1= 0:30 colob kernel: [=C2=A0 610.445977] br0: port 3(vif2.0-emu) entered forw= arding state
Nov=C2=A0 7 18:10:30 colob NetworkManager[907]: <info>= ;=C2=A0 (vif2.0-emu): enslaved to br0
Nov=C2=A0 7 18:10:30 colob root: /= etc/xen/scripts/colo-proxy-setup: brctl addif br0 vif2.0-emu failed
Nov= =C2=A0 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 --inde= x 1 failed
Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-= setup: rmmod xt_SECCOLO failed
Nov=C2=A0 7 18:10:30 colob root: /etc/xen= /scripts/colo-proxy-setup: Successful colo-proxy-setup teardown for vif2.0-= emu.=C2=A0 vifname: vif2.0-emu, index: 1, forwarddev: eth1,=C2=A0 forwardbr= : br1.
Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setu= p: ip6tables -t mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j = SECCOLO --index 1 failed
Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scrip= ts/colo-proxy-setup: rmmod xt_SECCOLO failed
Nov=C2=A0 7 18:10:30 colob = root: /etc/xen/scripts/colo-proxy-setup: Successful colo-proxy-setup teardo= wn for vif2.0-emu.=C2=A0 vifname: vif2.0-emu, index: 1, forwarddev: eth1,= =C2=A0 forwardbr: br1.
Nov=C2=A0 7 18:10:45 colob kernel: [=C2=A0 625.47= 5165] br0: port 3(vif2.0-emu) entered forwarding state

When &#= 39;xl remus' hang on the error, the state of the vm in both hosts is:
Primary:
Name=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ID=C2=A0=C2=A0 Mem VCPUs=C2=A0=C2= =A0=C2=A0 State=C2=A0=C2=A0=C2=A0 Time(s)
Domain-0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0 2502=C2=A0=C2=A0=C2= =A0=C2=A0 4=C2=A0=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 r-----=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 65.5
suse-hvm=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 2=C2=A0 1023=C2=A0=C2=A0=C2=A0=C2=A0 2=C2=A0=C2= =A0=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 --pss-=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 4= 2.0


Secondary:
Name=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ID=C2=A0=C2=A0 Mem VCPUs= =C2=A0=C2=A0=C2=A0 State=C2=A0=C2=A0=C2=A0 Time(s)
Domain-0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0=C2=A0 2502=C2=A0= =C2=A0=C2=A0=C2=A0 4=C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 r-----=C2=A0= =C2=A0=C2=A0=C2=A0 453.2
suse-hvm--incoming=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 2=C2=A0 1023=C2=A0=C2=A0=C2=A0=C2=A0 2=C2=A0=C2=A0=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 --p---=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 0.0
=
At this moment, if i unpause the VM in the secondary host it keep= s running from the point where the process was paused before the xl remus c= ommand.

I've tried removing the bound between eth1 and br1= , but apparently nothing has changed.

Thanks for your help.
Sadi.

=

On Fri, Nov 4, 20= 16 at 3:50 PM, Sadi <sadijrp@gmail.com> wrote:

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

> Hi,

>
> Thanks for replying. Here is what i got from /var/log/syslog:
>
> Nov=C2=A0 3 20:04:07 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: Starte= d LSB: Start/stop xenstored and xenconsoled.
> Nov=C2=A0 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=C2=A0 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=C2=A0 3 20:04:49 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: sessio= n-3.scope: Cannot determine UID from slice user-0.slice
> Nov=C2=A0 3 20:04:49 colob-HP-Compaq-6005-Pro-MT-PC systemd[1]: Starte= d Session 3 of user root.
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): new Tun device (carrier: OFF, driver: &= #39;tun', ifindex: 7)
> Nov=C2=A0 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 o= r directory
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 devices added (path: /sys/devices/virtual/net/vif2.0-emu, iface: vif2.0-emu)
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 device added (path: /sys/devices/virtual/net/vif2.0-emu, iface: vif2.0-emu): no ifupdown configuration found.
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <warn>=C2=A0 (vif2.0): failed to find device 8 'vif2.0' wi= th udev
> Nov=C2=A0 3 20:04:54 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0): new Ethernet device (carrier: OFF, driver: = 'vif', ifindex: 8)
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 devices added (path: /sys/devices/vif-2-0/net/vif2.0, iface: vif2.0)
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 device added (path: /sys/devices/vif-2-0/net/vif2.0, iface: vif2.0): no ifupdown configuration found.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0): device state change: unmanaged -> unavai= lable (reason 'managed') [10 20 2]
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.363596] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.363696] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: online type_if=3Dvif XENBUS_PATH=3Dbackend/vif/2/0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (br0): bridge port vif2.0 was attached
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.463896] device vif2.0 entered promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0): enslaved to br0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.466360] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.529006] ip_tables: (C) 2000-2006 Netfilter Core Team
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.585769] Bridge firewalling registered
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: Successful vif-bridge online for vif2.0, bridge br0.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: Writing backend/vif/2/0/hotplug-status connected to xensto= re.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: add type_if=3Dtap XENBUS_PATH=3Dbackend/vif/2/0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (br0): bridge port vif2.0-emu was attached
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): enslaved to br0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): link connected
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.693288] device vif2.0-emu entered promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.695493] br0: port 3(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.695500] br0: port 3(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/vif-bridge: Successful vif-bridge add for vif2.0-emu, bridge br0.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: setup XENBUS_PATH=3D
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (br0): bridge port vif2.0-emu was detached
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): released from master br0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.765881] device vif2.0-emu left promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.765922] br0: port 3(vif2.0-emu) entered disabled state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): new Bridge device (carrier: OFF, driver: &= #39;bridge', ifindex: 9)
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.771631] device vif2.0-emu entered promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): bridge port vif2.0-emu was attached
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): enslaved to colobr0
> Nov=C2=A0 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 d= irectory
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl addif colobr0 eth1 failed
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.783326] colobr0: port 1(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.783351] colobr0: port 1(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): link connected
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 devices added (path: /sys/devices/virtual/net/co= lobr0, iface: colobr0)
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 device added (path: /sys/devices/virtual/net/col= obr0, iface: colobr0): no ifupdown configuration found.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): device state change: unmanaged -> unava= ilable (reason 'managed') [10 20 2]
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): detached bridge port vif2.0-emu
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): released from master colobr0
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): link disconnected
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.818240] device vif2.0-emu left promiscuous mode
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.818254] colobr0: port 1(vif2.0-emu) entered disabled state
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (colobr0): device state change: unavailable -> dis= connected (reason 'none') [20 30 0]
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 Device 'colobr0' has no connection; schedulin= g activate_check in 0 seconds.
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 46= 4.832977] ip6_tables: (C) 2000-2006 Netfilter Core Team
> Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: Writing /hotplug-status connected to xenstore.<= br> > Nov=C2=A0 3 20:04:55 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: Successful colo-proxy-setup setup for vif2.0-em= u.=C2=A0 vifname: vif2.0-emu, index: 1, forwarddev: eth1,=C2=A0 forwardbr: = colobr0.
> Nov=C2=A0 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 fe= 80::fcff:ffff:feff:ffff.
> Nov=C2=A0 3 20:04:56 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : New relevant interface vif2.0-emu.IPv6 for mDNS.
> Nov=C2=A0 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-em= u.*.
> Nov=C2=A0 3 20:04:59 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : Received packet from invalid interface.
> Nov=C2=A0 3 20:05:00 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : message repeated 3 times: [ Received packet from invalid interface.]
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: teardown XENBUS_PATH=3D
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: teardown XENBUS_PATH=3D
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delif colobr0 eth1 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delif colobr0 eth1 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delif colobr0 vif2.0-emu failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delif colobr0 vif2.0-emu failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delbr colobr0 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl delbr colobr0 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (br0): bridge port vif2.0-emu was attached
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC NetworkManager[924= ]: <info>=C2=A0 (vif2.0-emu): enslaved to br0
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 47= 0.501624] device vif2.0-emu entered promiscuous mode
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 47= 0.501656] br0: port 3(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC kernel: [=C2=A0 47= 0.501661] br0: port 3(vif2.0-emu) entered forwarding state
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: brctl addif br0 vif2.0-emu failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: rmmod xt_SECCOLO failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: iptables -t mangle -D PREROUTING -m physdev --p= hysdev-in vif2.0-emu -j SECCOLO --index 1 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: Successful colo-proxy-setup teardown for vif2.0= -emu.=C2=A0 vifname: vif2.0-emu, index: 1, forwarddev: eth1,=C2=A0 forwardb= r: colobr0.
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: ip6tables -t mangle -D PREROUTING -m physdev --= physdev-in vif2.0-emu -j SECCOLO --index 1 failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: rmmod xt_SECCOLO failed
> Nov=C2=A0 3 20:05:01 colob-HP-Compaq-6005-Pro-MT-PC root: /etc/xen/scr= ipts/colo-proxy-setup: Successful colo-proxy-setup teardown for vif2.0= -emu.=C2=A0 vifname: vif2.0-emu, index: 1, forwarddev: eth1,=C2=A0 forwardb= r: colobr0.
> Nov=C2=A0 3 20:05:02 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : Received packet from invalid interface.
> Nov=C2=A0 3 20:05:02 colob-HP-Compaq-6005-Pro-MT-PC avahi-daemon[1117]= : Received packet from invalid interface.
>
> ... and dmesg:
>
> [=C2=A0 464.363596] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not rea= dy
> [=C2=A0 464.363696] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not rea= dy
> [=C2=A0 464.463896] device vif2.0 entered promiscuous mode
> [=C2=A0 464.466360] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not rea= dy
> [=C2=A0 464.529006] ip_tables: (C) 2000-2006 Netfilter Core Team
> [=C2=A0 464.585769] Bridge firewalling registered
> [=C2=A0 464.693288] device vif2.0-emu entered promiscuous mode
> [=C2=A0 464.695493] br0: port 3(vif2.0-emu) entered forwarding state > [=C2=A0 464.695500] br0: port 3(vif2.0-emu) entered forwarding state > [=C2=A0 464.765881] device vif2.0-emu left promiscuous mode
> [=C2=A0 464.765922] br0: port 3(vif2.0-emu) entered disabled state
> [=C2=A0 464.771631] device vif2.0-emu entered promiscuous mode
> [=C2=A0 464.783326] colobr0: port 1(vif2.0-emu) entered forwarding sta= te
> [=C2=A0 464.783351] colobr0: port 1(vif2.0-emu) entered forwarding sta= te
> [=C2=A0 464.818240] device vif2.0-emu left promiscuous mode
> [=C2=A0 464.818254] colobr0: port 1(vif2.0-emu) entered disabled state=
> [=C2=A0 464.832977] ip6_tables: (C) 2000-2006 Netfilter Core Team
> [=C2=A0 470.501624] device vif2.0-emu entered promiscuous mode
> [=C2=A0 470.501656] br0: port 3(vif2.0-emu) entered forwarding state > [=C2=A0 470.501661] br0: port 3(vif2.0-emu) entered forwarding state > [=C2=A0 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= 9;ve set it in a different way. These were the actually steps:
>
> qemu:
> ./configure --target-list=3Dx86_64-softmmu=C2=A0 --enable-gcrypt=C2=A0= --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://x= en.markmail.org/search/?q=3DCOLO#query:COLO+page:1+mid:zgz7wrdys5= hi6c5s+state:results, the eth1 in the secondary host is not explic= tly 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.
>
>
>




--
Sa= di.
--001a114a61782f346b0540bbfe9a-- --===============6784382393150124089== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============6784382393150124089==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Error migrating VM to secondary host using COLO replication Date: Tue, 8 Nov 2016 14:57:21 -0500 Message-ID: <20161108195721.GB20807@char.us.oracle.com> References: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Sadi Cc: Wen Congyang , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org PiBlbnRlcmVkIGZvcndhcmRpbmcgc3RhdGUKPiBOb3YgIDcgMTg6MTA6MzAgY29sb2IgTmV0d29y a01hbmFnZXJbOTA3XTogPGluZm8+ICAodmlmMi4wLWVtdSk6IGVuc2xhdmVkCj4gdG8gYnIwCj4g Tm92ICA3IDE4OjEwOjMwIGNvbG9iIHJvb3Q6IC9ldGMveGVuL3NjcmlwdHMvY29sby1wcm94eS1z ZXR1cDogYnJjdGwgYWRkaWYKPiBicjAgdmlmMi4wLWVtdSBmYWlsZWQKCgpIb3cgY29tZSB0aGlz IGZhaWxlZD8KCj4gTm92ICA3IDE4OjEwOjMwIGNvbG9iIHJvb3Q6IC9ldGMveGVuL3NjcmlwdHMv Y29sby1wcm94eS1zZXR1cDogaXB0YWJsZXMgLXQKPiBtYW5nbGUgLUQgUFJFUk9VVElORyAtbSBw aHlzZGV2IC0tcGh5c2Rldi1pbiB2aWYyLjAtZW11IC1qIFNFQ0NPTE8gLS1pbmRleAo+IDEgZmFp bGVkCgpBaCBiL2Mgb2YgdGhpcy4gQXJlIHRoZXJlIGFueSBlcnJvcnMgb2Ygd2hhdCBleGFjdGx5 IGZhaWxlZD8KCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Clhlbi1kZXZlbCBtYWlsaW5nIGxpc3QKWGVuLWRldmVsQGxpc3RzLnhlbi5vcmcKaHR0cHM6Ly9s aXN0cy54ZW4ub3JnL3hlbi1kZXZlbAo= From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sadi Subject: Re: Error migrating VM to secondary host using COLO replication Date: Tue, 8 Nov 2016 18:53:03 -0200 Message-ID: References: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> <20161108195721.GB20807@char.us.oracle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3712676867859548058==" Return-path: In-Reply-To: <20161108195721.GB20807@char.us.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Konrad Rzeszutek Wilk Cc: Wen Congyang , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============3712676867859548058== Content-Type: multipart/alternative; boundary=001a11443abca84fe80540d05349 --001a11443abca84fe80540d05349 Content-Type: text/plain; charset=UTF-8 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]: (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. --001a11443abca84fe80540d05349 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Apparently vif2.0-emu was already b= inded with br0 when "brctl addif br0 vif2.0-emu" failed.

root@colob-HP-Compaq-6005-Pro-MT-PC:~# brctl addif br= 0 vif2.0-emu
device vif2.0-emu is already a member of a bridge; c= an't enslave it to bridge br0.
root@colob-HP-Compaq-6005-Pro-= MT-PC:~# brctl show
bridge name =C2=A0 =C2=A0 bridge id =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 STP enabled =C2=A0 =C2=A0 interfa= ces
br0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8000.001a3fc462= 55 =C2=A0 =C2=A0 =C2=A0 no =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= eth0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 vif2.0
=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 vif2.0-emu
b= r1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 8000.000000000000 =C2=A0 =C2= =A0 =C2=A0 no

About the iptables, it seems l= ike SECCOLO target can't be recognised.

r= oot@colob-HP-Compaq-6005-Pro-MT-PC:~# iptables -t mangle -D PREROUTING -m p= hysdev --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-C= ompaq-6005-Pro-MT-PC:~# lsmod | grep -i colo
xt_SECCOLO =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 16384 =C2=A01
nf_conntrack_col= o =C2=A0 =C2=A0 =C2=A016384 =C2=A02 xt_SECCOLO
x_tables =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 36864 =C2=A08 xt_physdev,ip6table= _mangle,ip_tables,xt_SECCOLO,xt_tcpudp,iptable_filter,iptable_mangle,ip6_ta= bles
nf_conntrack =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0106496 =C2=A0= 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.=C2=A0

Sadi.

On Tue, Nov 8, 2016 = at 5:57 PM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> entered = forwarding state
> Nov=C2=A0 7 18:10:30 colob NetworkManager[907]: <info>=C2=A0 (vi= f2.0-emu): enslaved
> to br0
> Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setu= p: brctl addif
> br0 vif2.0-emu failed


How come this failed?

> Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setu= p: iptables -t
> mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j SECCOLO --i= ndex
> 1 failed

Ah b/c of this. Are there any errors of what exactly failed?



--
Sa= di.
--001a11443abca84fe80540d05349-- --===============3712676867859548058== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============3712676867859548058==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sadi Subject: Re: Error migrating VM to secondary host using COLO replication Date: Wed, 9 Nov 2016 15:31:20 -0200 Message-ID: References: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> <20161108195721.GB20807@char.us.oracle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0795096264588326742==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Konrad Rzeszutek Wilk Cc: Wen Congyang , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============0795096264588326742== Content-Type: multipart/alternative; boundary=047d7b66f18f1d035f0540e1a04f --047d7b66f18f1d035f0540e1a04f Content-Type: text/plain; charset=UTF-8 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 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.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]: (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. --047d7b66f18f1d035f0540e1a04f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello again,

Lookin= g at the primary host's syslog, the arptables command from xen/etc/scri= pts/colo-proxy-setup has failed.

Here's the log:

No= v=C2=A0 9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup: setup XE= NBUS_PATH=3D
Nov=C2=A0 9 14:43:39 colop kernel: [=C2=A0 302.825788] u32 = classifier
Nov=C2=A0 9 14:43:39 colop kernel: [=C2=A0 302.825791]=C2=A0= =C2=A0=C2=A0=C2=A0 Actions configured
Nov=C2=A0 9 14:43:39 colop kernel:= [=C2=A0 302.835407] Mirror/redirect action on
Nov=C2=A0 9 14:43:39 colo= p kernel: [=C2=A0 302.919605] ip6_tables: (C) 2000-2006 Netfilter Core Team=
Nov=C2=A0 9 14:43:39 colop kernel: [=C2=A0 302.941511] arp_tables: (C) = 2002 David S. Miller
Nov=C2=A0 9 14:43:39 colop colop: /etc/xen/scripts/= colo-proxy-setup: arptables -I INPUT -i eth1 -j MARK --set-mark 1 failedNov=C2=A0 9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-setup: Writi= ng /hotplug-status connected to xenstore.
Nov=C2=A0 9 14:43:39 colop col= op: /etc/xen/scripts/colo-proxy-setup: Successful colo-proxy-setup setup fo= r vif2.0-emu. mode =3D primary=C2=A0 vifname: vif2.0-emu, index: 1, forward= dev: eth1.

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

The i got running the comman= d is:
root@colop:~# arptables -I INPUT -i eth1 -j MARK --set-mark 1
B= ad argument `1'

Thanks, Sadi.


=

On Tue, Nov 8, 20= 16 at 6:53 PM, Sadi <sadijrp@gmail.com> wrote:
Hi,

Apparently vif= 2.0-emu was already binded with br0 when "brctl addif br0 vif2.0-emu&q= uot; failed.

root@colob-HP-Compaq-6005-Pro-MT-PC:~# brctl addif br0 vif2.0-emu
device vif2.0-emu is alrea= dy a member of a bridge; can't enslave it to bridge br0.
root= @colob-HP-Compaq-6005-Pro-MT-PC:~# brctl show
bridge name = =C2=A0 =C2=A0 bridge id =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ST= P enabled =C2=A0 =C2=A0 interfaces
br0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 8000.001a3fc46255 =C2=A0 =C2=A0 =C2=A0 no =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0eth0
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 vif2.0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 vif2.0-emu
br1 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 8000.000000000000 =C2=A0 =C2=A0 =C2=A0 no

About the iptables, it seems like SECCOLO target can't be reco= gnised.

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:~# ls= mod | grep -i colo
xt_SECCOLO =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 16384 =C2=A01
nf_conntrack_colo =C2=A0 =C2=A0 =C2=A016384 = =C2=A02 xt_SECCOLO
x_tables =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 36864 =C2=A08 xt_physdev,ip6table_mangle,ip_tables,xt_SE= CCOLO,xt_tcpudp,iptable_filter,iptable_mangle,ip6_tables
nf_conntrack =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0106496 =C2=A04 xt_SECCOLO,= nf_nat,nf_conntrack_colo,nf_conntrack_ipv4

So i was looking in the iptables and this really looks like the so= urce of the problem.=C2=A0

Sadi.

= On Tue, Nov 8, 2016 at 5:57 PM, Konrad Rzeszutek Wilk <= ;konrad.wilk@or= acle.com> wrote:
&g= t; entered forwarding state
> Nov=C2=A0 7 18:10:30 colob NetworkManager[907]: <info>=C2=A0 (vi= f2.0-emu): enslaved
> to br0
> Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setu= p: brctl addif
> br0 vif2.0-emu failed


How come this failed?

> Nov=C2=A0 7 18:10:30 colob root: /etc/xen/scripts/colo-proxy-setu= p: iptables -t
> mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j SECCOLO --i= ndex
> 1 failed

Ah b/c of this. Are there any errors of what exactly failed?



--
Sadi.



--
Sadi.
=
--047d7b66f18f1d035f0540e1a04f-- --===============0795096264588326742== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============0795096264588326742==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: Error migrating VM to secondary host using COLO replication Date: Thu, 10 Nov 2016 09:03:52 +0800 Message-ID: References: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> <20161108195721.GB20807@char.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Sadi , Konrad Rzeszutek Wilk Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org T24gMTEvMTAvMjAxNiAwMTozMSBBTSwgU2FkaSB3cm90ZToKPiBIZWxsbyBhZ2FpbiwKPiAKPiBM b29raW5nIGF0IHRoZSBwcmltYXJ5IGhvc3QncyBzeXNsb2csIHRoZSBhcnB0YWJsZXMgY29tbWFu ZCBmcm9tIHhlbi9ldGMvc2NyaXB0cy9jb2xvLXByb3h5LXNldHVwIGhhcyBmYWlsZWQuCj4gCj4g SGVyZSdzIHRoZSBsb2c6Cj4gCj4gTm92ICA5IDE0OjQzOjM5IGNvbG9wIGNvbG9wOiAvZXRjL3hl bi9zY3JpcHRzL2NvbG8tcHJveHktc2V0dXA6IHNldHVwIFhFTkJVU19QQVRIPQo+IE5vdiAgOSAx NDo0MzozOSBjb2xvcCBrZXJuZWw6IFsgIDMwMi44MjU3ODhdIHUzMiBjbGFzc2lmaWVyCj4gTm92 ICA5IDE0OjQzOjM5IGNvbG9wIGtlcm5lbDogWyAgMzAyLjgyNTc5MV0gICAgIEFjdGlvbnMgY29u ZmlndXJlZAo+IE5vdiAgOSAxNDo0MzozOSBjb2xvcCBrZXJuZWw6IFsgIDMwMi44MzU0MDddIE1p cnJvci9yZWRpcmVjdCBhY3Rpb24gb24KPiBOb3YgIDkgMTQ6NDM6MzkgY29sb3Aga2VybmVsOiBb ICAzMDIuOTE5NjA1XSBpcDZfdGFibGVzOiAoQykgMjAwMC0yMDA2IE5ldGZpbHRlciBDb3JlIFRl YW0KPiBOb3YgIDkgMTQ6NDM6MzkgY29sb3Aga2VybmVsOiBbICAzMDIuOTQxNTExXSBhcnBfdGFi bGVzOiAoQykgMjAwMiBEYXZpZCBTLiBNaWxsZXIKPiBOb3YgIDkgMTQ6NDM6MzkgY29sb3AgY29s b3A6IC9ldGMveGVuL3NjcmlwdHMvY29sby1wcm94eS1zZXR1cDogYXJwdGFibGVzIC1JIElOUFVU IC1pIGV0aDEgLWogTUFSSyAtLXNldC1tYXJrIDEgZmFpbGVkCj4gTm92ICA5IDE0OjQzOjM5IGNv bG9wIGNvbG9wOiAvZXRjL3hlbi9zY3JpcHRzL2NvbG8tcHJveHktc2V0dXA6IFdyaXRpbmcgL2hv dHBsdWctc3RhdHVzIGNvbm5lY3RlZCB0byB4ZW5zdG9yZS4KPiBOb3YgIDkgMTQ6NDM6MzkgY29s b3AgY29sb3A6IC9ldGMveGVuL3NjcmlwdHMvY29sby1wcm94eS1zZXR1cDogU3VjY2Vzc2Z1bCBj b2xvLXByb3h5LXNldHVwIHNldHVwIGZvciB2aWYyLjAtZW11LiBtb2RlID0gcHJpbWFyeSAgdmlm bmFtZTogdmlmMi4wLWVtdSwgaW5kZXg6IDEsIGZvcndhcmRkZXY6IGV0aDEuCj4gCj4gSXQncyBv ayBmb3IgdGhlIC0tc2V0LW1hcmsgYXJndW1lbnQgdG8gaGF2ZSB2YWx1ZSBlcXVhbCAnMScgLCBu b3QgYSBoZXg/CgpUaGlzIGxvZyBpcyB2ZXJ5IHVzZWZ1bCwgd2Ugd2lsbCBpbnZlc3RpZ2F0ZSBp dC4KClRoYW5rcwpXZW4gQ29uZ3lhbmcKCj4gCj4gVGhlIGkgZ290IHJ1bm5pbmcgdGhlIGNvbW1h bmQgaXM6Cj4gcm9vdEBjb2xvcDp+IyBhcnB0YWJsZXMgLUkgSU5QVVQgLWkgZXRoMSAtaiBNQVJL IC0tc2V0LW1hcmsgMQo+IEJhZCBhcmd1bWVudCBgMScKPiAKPiBUaGFua3MsIFNhZGkuCj4gCj4g Cj4gCj4gT24gVHVlLCBOb3YgOCwgMjAxNiBhdCA2OjUzIFBNLCBTYWRpIDxzYWRpanJwQGdtYWls LmNvbSA8bWFpbHRvOnNhZGlqcnBAZ21haWwuY29tPj4gd3JvdGU6Cj4gCj4gICAgIEhpLAo+IAo+ ICAgICBBcHBhcmVudGx5IHZpZjIuMC1lbXUgd2FzIGFscmVhZHkgYmluZGVkIHdpdGggYnIwIHdo ZW4gImJyY3RsIGFkZGlmIGJyMCB2aWYyLjAtZW11IiBmYWlsZWQuCj4gCj4gICAgIHJvb3RAY29s b2ItSFAtQ29tcGFxLTYwMDUtUHJvLU1ULVBDOn4jIGJyY3RsIGFkZGlmIGJyMCB2aWYyLjAtZW11 Cj4gICAgIGRldmljZSB2aWYyLjAtZW11IGlzIGFscmVhZHkgYSBtZW1iZXIgb2YgYSBicmlkZ2U7 IGNhbid0IGVuc2xhdmUgaXQgdG8gYnJpZGdlIGJyMC4KPiAgICAgcm9vdEBjb2xvYi1IUC1Db21w YXEtNjAwNS1Qcm8tTVQtUEM6fiMgYnJjdGwgc2hvdwo+ICAgICBicmlkZ2UgbmFtZSAgICAgYnJp ZGdlIGlkICAgICAgICAgICAgICAgU1RQIGVuYWJsZWQgICAgIGludGVyZmFjZXMKPiAgICAgYnIw ICAgICAgICAgICAgIDgwMDAuMDAxYTNmYzQ2MjU1ICAgICAgIG5vICAgICAgICAgICAgICBldGgw Cj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgdmlmMi4wCj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgdmlmMi4wLWVtdQo+ICAgICBicjEgICAgICAgICAgICAgODAwMC4w MDAwMDAwMDAwMDAgICAgICAgbm8KPiAKPiAgICAgQWJvdXQgdGhlIGlwdGFibGVzLCBpdCBzZWVt cyBsaWtlIFNFQ0NPTE8gdGFyZ2V0IGNhbid0IGJlIHJlY29nbmlzZWQuCj4gCj4gICAgIHJvb3RA Y29sb2ItSFAtQ29tcGFxLTYwMDUtUHJvLU1ULVBDOn4jIGlwdGFibGVzIC10IG1hbmdsZSAtRCBQ UkVST1VUSU5HIC1tIHBoeXNkZXYgLS1waHlzZGV2LWluIHZpZjIuMC1lbXUgLWogU0VDQ09MTyAt LWluZGV4IDEKPiAgICAgaXB0YWJsZXM6IE5vIGNoYWluL3RhcmdldC9tYXRjaCBieSB0aGF0IG5h bWUuCj4gCj4gICAgIEhlcmUgaXMgbXkgYWN0aXZlIG1vZHVsZXMgbWF0Y2hpbmcgY29sbzoKPiAK PiAgICAgcm9vdEBjb2xvYi1IUC1Db21wYXEtNjAwNS1Qcm8tTVQtUEM6fiMgbHNtb2QgfCBncmVw IC1pIGNvbG8KPiAgICAgeHRfU0VDQ09MTyAgICAgICAgICAgICAxNjM4NCAgMQo+ICAgICBuZl9j b25udHJhY2tfY29sbyAgICAgIDE2Mzg0ICAyIHh0X1NFQ0NPTE8KPiAgICAgeF90YWJsZXMgICAg ICAgICAgICAgICAzNjg2NCAgOCB4dF9waHlzZGV2LGlwNnRhYmxlX21hbmdsZSxpcF90YWJsZXMs eHRfU0VDQ09MTyx4dF90Y3B1ZHAsaXB0YWJsZV9maWx0ZXIsaXB0YWJsZV9tYW5nbGUsaXA2X3Rh Ymxlcwo+ICAgICBuZl9jb25udHJhY2sgICAgICAgICAgMTA2NDk2ICA0IHh0X1NFQ0NPTE8sbmZf bmF0LG5mX2Nvbm50cmFja19jb2xvLG5mX2Nvbm50cmFja19pcHY0Cj4gCj4gICAgIFNvIGkgd2Fz IGxvb2tpbmcgaW4gdGhlIGlwdGFibGVzIGFuZCB0aGlzIHJlYWxseSBsb29rcyBsaWtlIHRoZSBz b3VyY2Ugb2YgdGhlIHByb2JsZW0uIAo+IAo+ICAgICBTYWRpLgo+IAo+ICAgICBPbiBUdWUsIE5v diA4LCAyMDE2IGF0IDU6NTcgUE0sIEtvbnJhZCBSemVzenV0ZWsgV2lsayA8a29ucmFkLndpbGtA b3JhY2xlLmNvbSA8bWFpbHRvOmtvbnJhZC53aWxrQG9yYWNsZS5jb20+PiB3cm90ZToKPiAKPiAg ICAgICAgID4gZW50ZXJlZCBmb3J3YXJkaW5nIHN0YXRlCj4gICAgICAgICA+IE5vdiAgNyAxODox MDozMCBjb2xvYiBOZXR3b3JrTWFuYWdlcls5MDddOiA8aW5mbz4gICh2aWYyLjAtZW11KTogZW5z bGF2ZWQKPiAgICAgICAgID4gdG8gYnIwCj4gICAgICAgICA+IE5vdiAgNyAxODoxMDozMCBjb2xv YiByb290OiAvZXRjL3hlbi9zY3JpcHRzL2NvbG8tcHJveHktc2V0dXA6IGJyY3RsIGFkZGlmCj4g ICAgICAgICA+IGJyMCB2aWYyLjAtZW11IGZhaWxlZAo+IAo+IAo+ICAgICAgICAgSG93IGNvbWUg dGhpcyBmYWlsZWQ/Cj4gCj4gICAgICAgICA+IE5vdiAgNyAxODoxMDozMCBjb2xvYiByb290OiAv ZXRjL3hlbi9zY3JpcHRzL2NvbG8tcHJveHktc2V0dXA6IGlwdGFibGVzIC10Cj4gICAgICAgICA+ IG1hbmdsZSAtRCBQUkVST1VUSU5HIC1tIHBoeXNkZXYgLS1waHlzZGV2LWluIHZpZjIuMC1lbXUg LWogU0VDQ09MTyAtLWluZGV4Cj4gICAgICAgICA+IDEgZmFpbGVkCj4gCj4gICAgICAgICBBaCBi L2Mgb2YgdGhpcy4gQXJlIHRoZXJlIGFueSBlcnJvcnMgb2Ygd2hhdCBleGFjdGx5IGZhaWxlZD8K PiAKPiAKPiAKPiAKPiAgICAgLS0gCj4gICAgIFNhZGkuCj4gCj4gCj4gCj4gCj4gLS0gCj4gU2Fk aS4KCgoKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClhl bi1kZXZlbCBtYWlsaW5nIGxpc3QKWGVuLWRldmVsQGxpc3RzLnhlbi5vcmcKaHR0cHM6Ly9saXN0 cy54ZW4ub3JnL3hlbi1kZXZlbAo= From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sadi Subject: Re: Error migrating VM to secondary host using COLO replication Date: Thu, 10 Nov 2016 19:53:08 -0200 Message-ID: References: <817ca129-78c6-2c90-bfe2-2f3dce59208d@cn.fujitsu.com> <20161108195721.GB20807@char.us.oracle.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6007121922926968501==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Wen Congyang Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============6007121922926968501== Content-Type: multipart/alternative; boundary=001a114a61783c22940540f96697 --001a114a61783c22940540f96697 Content-Type: text/plain; charset=UTF-8 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 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 sadijrp@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.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]: > (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. --001a114a61783c22940540f96697 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Thanks for helping me.

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

I= 9;m planning on starting over again from the very beginning. I just wanna=20 know what tutorial follow. The one from the Wiki,=C2=A0 from the mail threa= d=20 or another one.

Link to tutorials:

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

Th= anks,

Sadi.

On Wed, Nov 9, 2016 at 11:03 PM, Wen Congyang <wency@cn.f= ujitsu.com> wrote:
On 11/10/2016 01:31 AM, Sadi wrote:
> Hello again,
>
> Looking at the primary host's syslog, the arptables command from x= en/etc/scripts/colo-proxy-setup has failed.
>
> Here's the log:
>
> Nov=C2=A0 9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-set= up: setup XENBUS_PATH=3D
> Nov=C2=A0 9 14:43:39 colop kernel: [=C2=A0 302.825788] u32 classifier<= br> > Nov=C2=A0 9 14:43:39 colop kernel: [=C2=A0 302.825791]=C2=A0 =C2=A0 = =C2=A0Actions configured
> Nov=C2=A0 9 14:43:39 colop kernel: [=C2=A0 302.835407] Mirror/redirect= action on
> Nov=C2=A0 9 14:43:39 colop kernel: [=C2=A0 302.919605] ip6_tables: (C)= 2000-2006 Netfilter Core Team
> Nov=C2=A0 9 14:43:39 colop kernel: [=C2=A0 302.941511] arp_tables: (C)= 2002 David S. Miller
> Nov=C2=A0 9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-set= up: arptables -I INPUT -i eth1 -j MARK --set-mark 1 failed
> Nov=C2=A0 9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-set= up: Writing /hotplug-status connected to xenstore.
> Nov=C2=A0 9 14:43:39 colop colop: /etc/xen/scripts/colo-proxy-set= up: Successful colo-proxy-setup setup for vif2.0-emu. mode =3D primary=C2= =A0 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 = <sadijrp@gmail.com <mailto:<= a href=3D"mailto:sadijrp@gmail.com">sadijrp@gmail.com>> wrote: >
>=C2=A0 =C2=A0 =C2=A0Hi,
>
>=C2=A0 =C2=A0 =C2=A0Apparently vif2.0-emu was already binded with br0 w= hen "brctl addif br0 vif2.0-emu" failed.
>
>=C2=A0 =C2=A0 =C2=A0root@colob-HP-Compaq-6005-Pro-MT-PC:~# brctl a= ddif br0 vif2.0-emu
>=C2=A0 =C2=A0 =C2=A0device vif2.0-emu is already a member of a bridge; = can't enslave it to bridge br0.
>=C2=A0 =C2=A0 =C2=A0root@colob-HP-Compaq-6005-Pro-MT-PC:~# brctl s= how
>=C2=A0 =C2=A0 =C2=A0bridge name=C2=A0 =C2=A0 =C2=A0bridge id=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0STP enabled=C2=A0 =C2=A0 =C2= =A0interfaces
>=C2=A0 =C2=A0 =C2=A0br0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= 8000.001a3fc46255=C2=A0 =C2=A0 =C2=A0 =C2=A0no=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 eth0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0vi= f2.0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0vi= f2.0-emu
>=C2=A0 =C2=A0 =C2=A0br1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= 8000.000000000000=C2=A0 =C2=A0 =C2=A0 =C2=A0no
>
>=C2=A0 =C2=A0 =C2=A0About the iptables, it seems like SECCOLO target ca= n't be recognised.
>
>=C2=A0 =C2=A0 =C2=A0root@colob-HP-Compaq-6005-Pro-MT-PC:~# iptable= s -t mangle -D PREROUTING -m physdev --physdev-in vif2.0-emu -j SECCOLO --i= ndex 1
>=C2=A0 =C2=A0 =C2=A0iptables: No chain/target/match by that name.
>
>=C2=A0 =C2=A0 =C2=A0Here is my active modules matching colo:
>
>=C2=A0 =C2=A0 =C2=A0root@colob-HP-Compaq-6005-Pro-MT-PC:~# lsmod |= grep -i colo
>=C2=A0 =C2=A0 =C2=A0xt_SECCOLO=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A016384=C2=A0 1
>=C2=A0 =C2=A0 =C2=A0nf_conntrack_colo=C2=A0 =C2=A0 =C2=A0 16384=C2=A0 2= xt_SECCOLO
>=C2=A0 =C2=A0 =C2=A0x_tables=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A036864=C2=A0 8 xt_physdev,ip6table_mangle,ip_tables,xt_SEC= COLO,xt_tcpudp,iptable_filter,iptable_mangle,ip6_tables
>=C2=A0 =C2=A0 =C2=A0nf_conntrack=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 1064= 96=C2=A0 4 xt_SECCOLO,nf_nat,nf_conntrack_colo,nf_conntrack_ipv4<= br> >
>=C2=A0 =C2=A0 =C2=A0So i was looking in the iptables and this really lo= oks like the source of the problem.
>
>=C2=A0 =C2=A0 =C2=A0Sadi.
>
>=C2=A0 =C2=A0 =C2=A0On T= ue, Nov 8, 2016 at 5:57 PM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com <mailto:konrad.wilk@oracle.com>> wrote: >
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> entered forwarding state
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> Nov=C2=A0 7 18:10:30 colob Netwo= rkManager[907]: <info>=C2=A0 (vif2.0-emu): enslaved
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> to br0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> Nov=C2=A0 7 18:10:30 colob root:= /etc/xen/scripts/colo-proxy-setup: brctl addif
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> br0 vif2.0-emu failed
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0How come this failed?
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> Nov=C2=A0 7 18:10:30 colob root:= /etc/xen/scripts/colo-proxy-setup: iptables -t
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> mangle -D PREROUTING -m physdev = --physdev-in vif2.0-emu -j SECCOLO --index
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0> 1 failed
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ah b/c of this. Are there any errors = of what exactly failed?
>
>
>
>
>=C2=A0 =C2=A0 =C2=A0--
>=C2=A0 =C2=A0 =C2=A0Sadi.
>
>
>
>
> --
> Sadi.






--
Sa= di.
--001a114a61783c22940540f96697-- --===============6007121922926968501== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============6007121922926968501==--