From xen-api-bounces@lists.xen.org Mon Mar 03 05:45:56 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Mar 2014 05:45:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKLgv-0001CV-ME; Mon, 03 Mar 2014 05:45:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKLgt-0001CQ-N6 for xen-api@lists.xen.org; Mon, 03 Mar 2014 05:45:28 +0000 Received: from [193.109.254.147:10437] by server-2.bemta-14.messagelabs.com id 40/B7-01236-7F614135; Mon, 03 Mar 2014 05:45:27 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-16.tower-27.messagelabs.com!1393825524!7859520!1 X-Originating-IP: [65.55.88.11] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12856 invoked from network); 3 Mar 2014 05:45:26 -0000 Received: from tx2ehsobe001.messaging.microsoft.com (HELO tx2outboundpool.messaging.microsoft.com) (65.55.88.11) by server-16.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 3 Mar 2014 05:45:26 -0000 Received: from mail79-tx2-R.bigfish.com (10.9.14.230) by TX2EHSOBE006.bigfish.com (10.9.40.26) with Microsoft SMTP Server id 14.1.225.22; Mon, 3 Mar 2014 05:45:24 +0000 Received: from mail79-tx2 (localhost [127.0.0.1]) by mail79-tx2-R.bigfish.com (Postfix) with ESMTP id 249E73A01E6 for ; Mon, 3 Mar 2014 05:45:24 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: 5 X-BigFish: VPS5(z36e9nz14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de098h8275bh1de097hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch1155h) Received-SPF: pass (mail79-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(199002)(189002)(53754006)(83072002)(74366001)(90146001)(4396001)(56816005)(76176001)(36756003)(77096001)(85852003)(33656001)(92566001)(93516002)(47976001)(47446002)(74502001)(47736001)(50986001)(49866001)(74662001)(81542001)(76786001)(31966008)(79102001)(63696002)(65816001)(80022001)(66066001)(94316002)(92726001)(93136001)(94946001)(83322001)(19580405001)(86362001)(56776001)(19580395003)(80976001)(69226001)(95416001)(81816001)(81686001)(82746002)(95666003)(87266001)(76482001)(59766001)(77982001)(74706001)(81342001)(83716003)(76796001)(2656002)(74876001)(51856001)(87936001)(54356001)(53806001)(46102001)(54316002)(85306002)(140573001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB778; H:BL2PR05MB193.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:B616D0F5.823327C2.8CD39DAB.4EA49262.203AB; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail79-tx2 (localhost.localdomain [127.0.0.1]) by mail79-tx2 (MessageSwitch) id 1393825522182949_14849; Mon, 3 Mar 2014 05:45:22 +0000 (UTC) Received: from TX2EHSMHS017.bigfish.com (unknown [10.9.14.227]) by mail79-tx2.bigfish.com (Postfix) with ESMTP id 105DC1C0078 for ; Mon, 3 Mar 2014 05:45:22 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS017.bigfish.com (10.9.99.117) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 3 Mar 2014 05:45:19 +0000 Received: from CO2PR05MB778.namprd05.prod.outlook.com (10.141.226.151) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Mon, 3 Mar 2014 05:45:17 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com (10.242.198.143) by CO2PR05MB778.namprd05.prod.outlook.com (10.141.226.151) with Microsoft SMTP Server (TLS) id 15.0.888.9; Mon, 3 Mar 2014 05:45:16 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) by BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) with mapi id 15.00.0888.003; Mon, 3 Mar 2014 05:45:15 +0000 From: Anirban Chakraborty To: "xen-api@lists.xen.org" Thread-Topic: build issue with xapi Thread-Index: AQHPNqO/DQJ26lju90S7esAZ24U2dA== Date: Mon, 3 Mar 2014 05:45:14 +0000 Message-ID: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 0139052FDB Content-ID: MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Subject: [Xen-API] build issue with xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi All, I am trying to build xapi via opam install xapi, and getting following erro= r: ---=3D-=3D-=3D Installing xapi.1.0.0 =3D-=3D-=3D Building xapi.1.0.0: ./configure --varpatchdir /contrail/opam/system/var/patch --optdir /contr= ail/opam/system/lib/xcp --plugindir /contrail/opam/system/lib/xcp/plugins -= -hooksdir /contrail/opam/system/etc/hook-scripts --xapiconf /contrail/opam/= system/etc/xapi.conf --libexecdir /contrail/opam/system/lib/xcp/bin --scrip= tsdir /contrail/opam/system/lib/xcp/scripts --sharedir /contrail/opam/syste= m/share/xcp --webdir /contrail/opam/system/share/xcp/web --xhadir /contrail= /opam/system/bin/xha --bindir /contrail/opam/system/bin --sbindir /contrail= /opam/system/bin --etcdir /contrail/opam/system/etc --vardir /var/lib/xcp make version omake phase1 omake phase2 omake ocaml/xapi/xapi install -m 0755 ocaml/xapi/xapi.opt /contrail/opam/system/bin/xapi [ERROR] The compilation of xapi.1.0.0 failed. Removing xapi.1.0.0. rm /contrail/opam/system/bin/xapi [ERROR] Failure while processing xapi.1.0.0 =3D=3D=3D=3D=3D ERROR while installing xapi.1.0.0 =3D=3D=3D=3D=3D # opam-version 1.1.1 (d2d459e390e869bf20f1889a5d2cf7933f2851ae) # os linux # command ./configure --varpatchdir /contrail/opam/system/var/patch --= optdir /contrail/opam/system/lib/xcp --plugindir /contrail/opam/system/lib/= xcp/plugins --hooksdir /contrail/opam/system/etc/hook-scripts --xapiconf /c= ontrail/opam/system/etc/xapi.conf --libexecdir /contrail/opam/system/lib/xc= p/bin --scriptsdir /contrail/opam/system/lib/xcp/scripts --sharedir /contra= il/opam/system/share/xcp --webdir /contrail/opam/system/share/xcp/web --xha= dir /contrail/opam/system/bin/xha --bindir /contrail/opam/system/bin --sbin= dir /contrail/opam/system/bin --etcdir /contrail/opam/system/etc --vardir /= var/lib/xcp # path /contrail/opam/system/build/xapi.1.0.0 # compiler system (4.01.0) # exit-code 2 # env-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.env # stdout-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.out # stderr-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.err ### stdout ### # Cannot find file topfind. ### stderr ### # Unknown directive `require'. =97=97 The configure script is not able to find topfind, as it looks from the mess= ages. However, I do have following set: OCAML_TOPLEVEL_PATH=3D/contrail/opam/system/lib/toplevel As a check, when I run utop and then in the cmd prompt issue, use =93topfin= d=94, it doesn=92t complain. So, as it appears that the configure script do= esn=92t find =93topfind" whereas utop can find it. Does it mean that findli= b could not be resolved properly? I am pretty new to OCaml. Can some one shed some light on it? My xapi code is at following change set: commit ffd3561cb05e828ffa8646fb9cc91e3c3e721b2f Merge: 1b6ff5f 8fa2e83 Author: Dave Scott Date: Mon Nov 25 03:27:02 2013 -0800 Merge pull request #6 from jonludlam/fusion-vbdfix = Relax the rules about ISO vbds coming from ISO SRs =97=97=97 and ocaml version is: [root@localhost xapi.1.0.0]# ocaml = OCaml version 4.01.0 Findlib has been successfully loaded. Additional directives: #require "package";; to load a package #list;; to list the available packages #camlp4o;; to load camlp4 (standard syntax) #camlp4r;; to load camlp4 (revised syntax) #predicates "p,q,...";; to set these predicates Topfind.reset();; to force that packages will be reloaded #thread;; to enable threads ----- thanks much, Anirban _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 03 05:45:56 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Mar 2014 05:45:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKLgv-0001CV-ME; Mon, 03 Mar 2014 05:45:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKLgt-0001CQ-N6 for xen-api@lists.xen.org; Mon, 03 Mar 2014 05:45:28 +0000 Received: from [193.109.254.147:10437] by server-2.bemta-14.messagelabs.com id 40/B7-01236-7F614135; Mon, 03 Mar 2014 05:45:27 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-16.tower-27.messagelabs.com!1393825524!7859520!1 X-Originating-IP: [65.55.88.11] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12856 invoked from network); 3 Mar 2014 05:45:26 -0000 Received: from tx2ehsobe001.messaging.microsoft.com (HELO tx2outboundpool.messaging.microsoft.com) (65.55.88.11) by server-16.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 3 Mar 2014 05:45:26 -0000 Received: from mail79-tx2-R.bigfish.com (10.9.14.230) by TX2EHSOBE006.bigfish.com (10.9.40.26) with Microsoft SMTP Server id 14.1.225.22; Mon, 3 Mar 2014 05:45:24 +0000 Received: from mail79-tx2 (localhost [127.0.0.1]) by mail79-tx2-R.bigfish.com (Postfix) with ESMTP id 249E73A01E6 for ; Mon, 3 Mar 2014 05:45:24 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: 5 X-BigFish: VPS5(z36e9nz14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de098h8275bh1de097hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch1155h) Received-SPF: pass (mail79-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(199002)(189002)(53754006)(83072002)(74366001)(90146001)(4396001)(56816005)(76176001)(36756003)(77096001)(85852003)(33656001)(92566001)(93516002)(47976001)(47446002)(74502001)(47736001)(50986001)(49866001)(74662001)(81542001)(76786001)(31966008)(79102001)(63696002)(65816001)(80022001)(66066001)(94316002)(92726001)(93136001)(94946001)(83322001)(19580405001)(86362001)(56776001)(19580395003)(80976001)(69226001)(95416001)(81816001)(81686001)(82746002)(95666003)(87266001)(76482001)(59766001)(77982001)(74706001)(81342001)(83716003)(76796001)(2656002)(74876001)(51856001)(87936001)(54356001)(53806001)(46102001)(54316002)(85306002)(140573001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB778; H:BL2PR05MB193.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:B616D0F5.823327C2.8CD39DAB.4EA49262.203AB; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail79-tx2 (localhost.localdomain [127.0.0.1]) by mail79-tx2 (MessageSwitch) id 1393825522182949_14849; Mon, 3 Mar 2014 05:45:22 +0000 (UTC) Received: from TX2EHSMHS017.bigfish.com (unknown [10.9.14.227]) by mail79-tx2.bigfish.com (Postfix) with ESMTP id 105DC1C0078 for ; Mon, 3 Mar 2014 05:45:22 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS017.bigfish.com (10.9.99.117) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 3 Mar 2014 05:45:19 +0000 Received: from CO2PR05MB778.namprd05.prod.outlook.com (10.141.226.151) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Mon, 3 Mar 2014 05:45:17 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com (10.242.198.143) by CO2PR05MB778.namprd05.prod.outlook.com (10.141.226.151) with Microsoft SMTP Server (TLS) id 15.0.888.9; Mon, 3 Mar 2014 05:45:16 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) by BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) with mapi id 15.00.0888.003; Mon, 3 Mar 2014 05:45:15 +0000 From: Anirban Chakraborty To: "xen-api@lists.xen.org" Thread-Topic: build issue with xapi Thread-Index: AQHPNqO/DQJ26lju90S7esAZ24U2dA== Date: Mon, 3 Mar 2014 05:45:14 +0000 Message-ID: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 0139052FDB Content-ID: MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Subject: [Xen-API] build issue with xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi All, I am trying to build xapi via opam install xapi, and getting following erro= r: ---=3D-=3D-=3D Installing xapi.1.0.0 =3D-=3D-=3D Building xapi.1.0.0: ./configure --varpatchdir /contrail/opam/system/var/patch --optdir /contr= ail/opam/system/lib/xcp --plugindir /contrail/opam/system/lib/xcp/plugins -= -hooksdir /contrail/opam/system/etc/hook-scripts --xapiconf /contrail/opam/= system/etc/xapi.conf --libexecdir /contrail/opam/system/lib/xcp/bin --scrip= tsdir /contrail/opam/system/lib/xcp/scripts --sharedir /contrail/opam/syste= m/share/xcp --webdir /contrail/opam/system/share/xcp/web --xhadir /contrail= /opam/system/bin/xha --bindir /contrail/opam/system/bin --sbindir /contrail= /opam/system/bin --etcdir /contrail/opam/system/etc --vardir /var/lib/xcp make version omake phase1 omake phase2 omake ocaml/xapi/xapi install -m 0755 ocaml/xapi/xapi.opt /contrail/opam/system/bin/xapi [ERROR] The compilation of xapi.1.0.0 failed. Removing xapi.1.0.0. rm /contrail/opam/system/bin/xapi [ERROR] Failure while processing xapi.1.0.0 =3D=3D=3D=3D=3D ERROR while installing xapi.1.0.0 =3D=3D=3D=3D=3D # opam-version 1.1.1 (d2d459e390e869bf20f1889a5d2cf7933f2851ae) # os linux # command ./configure --varpatchdir /contrail/opam/system/var/patch --= optdir /contrail/opam/system/lib/xcp --plugindir /contrail/opam/system/lib/= xcp/plugins --hooksdir /contrail/opam/system/etc/hook-scripts --xapiconf /c= ontrail/opam/system/etc/xapi.conf --libexecdir /contrail/opam/system/lib/xc= p/bin --scriptsdir /contrail/opam/system/lib/xcp/scripts --sharedir /contra= il/opam/system/share/xcp --webdir /contrail/opam/system/share/xcp/web --xha= dir /contrail/opam/system/bin/xha --bindir /contrail/opam/system/bin --sbin= dir /contrail/opam/system/bin --etcdir /contrail/opam/system/etc --vardir /= var/lib/xcp # path /contrail/opam/system/build/xapi.1.0.0 # compiler system (4.01.0) # exit-code 2 # env-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.env # stdout-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.out # stderr-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.err ### stdout ### # Cannot find file topfind. ### stderr ### # Unknown directive `require'. =97=97 The configure script is not able to find topfind, as it looks from the mess= ages. However, I do have following set: OCAML_TOPLEVEL_PATH=3D/contrail/opam/system/lib/toplevel As a check, when I run utop and then in the cmd prompt issue, use =93topfin= d=94, it doesn=92t complain. So, as it appears that the configure script do= esn=92t find =93topfind" whereas utop can find it. Does it mean that findli= b could not be resolved properly? I am pretty new to OCaml. Can some one shed some light on it? My xapi code is at following change set: commit ffd3561cb05e828ffa8646fb9cc91e3c3e721b2f Merge: 1b6ff5f 8fa2e83 Author: Dave Scott Date: Mon Nov 25 03:27:02 2013 -0800 Merge pull request #6 from jonludlam/fusion-vbdfix = Relax the rules about ISO vbds coming from ISO SRs =97=97=97 and ocaml version is: [root@localhost xapi.1.0.0]# ocaml = OCaml version 4.01.0 Findlib has been successfully loaded. Additional directives: #require "package";; to load a package #list;; to list the available packages #camlp4o;; to load camlp4 (standard syntax) #camlp4r;; to load camlp4 (revised syntax) #predicates "p,q,...";; to set these predicates Topfind.reset();; to force that packages will be reloaded #thread;; to enable threads ----- thanks much, Anirban _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 03 13:42:08 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Mar 2014 13:42:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKT7r-0001Ig-Id; Mon, 03 Mar 2014 13:41:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKT7q-0001Ib-El for xen-api@lists.xen.org; Mon, 03 Mar 2014 13:41:46 +0000 Received: from [85.158.143.35:43397] by server-3.bemta-4.messagelabs.com id 35/D2-11539-99684135; Mon, 03 Mar 2014 13:41:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1393854104!9582396!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3426 invoked from network); 3 Mar 2014 13:41:44 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-21.messagelabs.com with SMTP; 3 Mar 2014 13:41:44 -0000 Received: (qmail 11935 invoked by uid 634); 3 Mar 2014 13:41:44 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 03 Mar 2014 13:41:44 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> Date: Mon, 3 Mar 2014 13:41:43 +0000 Message-Id: <8BA944B8-0B6B-46E6-B290-FD4541FB77DD@recoil.org> References: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> To: Anirban Chakraborty X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] build issue with xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org As a workaround, you could try: $ opam switch 4.00.1 # or 4.01.0 $ opam install xapi This topfind problem tends to only happen with the system compiler. -anil On 3 Mar 2014, at 05:45, Anirban Chakraborty wrote: > Hi All, > = > I am trying to build xapi via opam install xapi, and getting following er= ror: > = > ---=3D-=3D-=3D Installing xapi.1.0.0 =3D-=3D-=3D > Building xapi.1.0.0: > ./configure --varpatchdir /contrail/opam/system/var/patch --optdir /cont= rail/opam/system/lib/xcp --plugindir /contrail/opam/system/lib/xcp/plugins = --hooksdir /contrail/opam/system/etc/hook-scripts --xapiconf /contrail/opam= /system/etc/xapi.conf --libexecdir /contrail/opam/system/lib/xcp/bin --scri= ptsdir /contrail/opam/system/lib/xcp/scripts --sharedir /contrail/opam/syst= em/share/xcp --webdir /contrail/opam/system/share/xcp/web --xhadir /contrai= l/opam/system/bin/xha --bindir /contrail/opam/system/bin --sbindir /contrai= l/opam/system/bin --etcdir /contrail/opam/system/etc --vardir /var/lib/xcp > make version > omake phase1 > omake phase2 > omake ocaml/xapi/xapi > install -m 0755 ocaml/xapi/xapi.opt /contrail/opam/system/bin/xapi > [ERROR] The compilation of xapi.1.0.0 failed. > Removing xapi.1.0.0. > rm /contrail/opam/system/bin/xapi > = > [ERROR] Failure while processing xapi.1.0.0 > = > = > =3D=3D=3D=3D=3D ERROR while installing xapi.1.0.0 =3D=3D=3D=3D=3D > # opam-version 1.1.1 (d2d459e390e869bf20f1889a5d2cf7933f2851ae) > # os linux > # command ./configure --varpatchdir /contrail/opam/system/var/patch = --optdir /contrail/opam/system/lib/xcp --plugindir /contrail/opam/system/li= b/xcp/plugins --hooksdir /contrail/opam/system/etc/hook-scripts --xapiconf = /contrail/opam/system/etc/xapi.conf --libexecdir /contrail/opam/system/lib/= xcp/bin --scriptsdir /contrail/opam/system/lib/xcp/scripts --sharedir /cont= rail/opam/system/share/xcp --webdir /contrail/opam/system/share/xcp/web --x= hadir /contrail/opam/system/bin/xha --bindir /contrail/opam/system/bin --sb= indir /contrail/opam/system/bin --etcdir /contrail/opam/system/etc --vardir= /var/lib/xcp > # path /contrail/opam/system/build/xapi.1.0.0 > # compiler system (4.01.0) > # exit-code 2 > # env-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.e= nv > # stdout-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.o= ut > # stderr-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.e= rr > ### stdout ### > # Cannot find file topfind. > ### stderr ### > # Unknown directive `require'. > = > =97=97 > = > The configure script is not able to find topfind, as it looks from the me= ssages. However, I do have following set: > = > OCAML_TOPLEVEL_PATH=3D/contrail/opam/system/lib/toplevel > = > As a check, when I run utop and then in the cmd prompt issue, use =93topf= ind=94, it doesn=92t complain. So, as it appears that the configure script = doesn=92t find =93topfind" whereas utop can find it. Does it mean that find= lib could not be resolved properly? > = > I am pretty new to OCaml. Can some one shed some light on it? > = > My xapi code is at following change set: > commit ffd3561cb05e828ffa8646fb9cc91e3c3e721b2f > Merge: 1b6ff5f 8fa2e83 > Author: Dave Scott > Date: Mon Nov 25 03:27:02 2013 -0800 > = > Merge pull request #6 from jonludlam/fusion-vbdfix > = > Relax the rules about ISO vbds coming from ISO SRs > =97=97=97 > and ocaml version is: > = > [root@localhost xapi.1.0.0]# ocaml = > OCaml version 4.01.0 > = > Findlib has been successfully loaded. Additional directives: > #require "package";; to load a package > #list;; to list the available packages > #camlp4o;; to load camlp4 (standard syntax) > #camlp4r;; to load camlp4 (revised syntax) > #predicates "p,q,...";; to set these predicates > Topfind.reset();; to force that packages will be reloaded > #thread;; to enable threads > = > ----- > = > thanks much, > Anirban > = > = > = > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > = _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 03 13:42:08 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Mar 2014 13:42:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKT7r-0001Ig-Id; Mon, 03 Mar 2014 13:41:47 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKT7q-0001Ib-El for xen-api@lists.xen.org; Mon, 03 Mar 2014 13:41:46 +0000 Received: from [85.158.143.35:43397] by server-3.bemta-4.messagelabs.com id 35/D2-11539-99684135; Mon, 03 Mar 2014 13:41:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1393854104!9582396!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3426 invoked from network); 3 Mar 2014 13:41:44 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-21.messagelabs.com with SMTP; 3 Mar 2014 13:41:44 -0000 Received: (qmail 11935 invoked by uid 634); 3 Mar 2014 13:41:44 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 03 Mar 2014 13:41:44 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> Date: Mon, 3 Mar 2014 13:41:43 +0000 Message-Id: <8BA944B8-0B6B-46E6-B290-FD4541FB77DD@recoil.org> References: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> To: Anirban Chakraborty X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] build issue with xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org As a workaround, you could try: $ opam switch 4.00.1 # or 4.01.0 $ opam install xapi This topfind problem tends to only happen with the system compiler. -anil On 3 Mar 2014, at 05:45, Anirban Chakraborty wrote: > Hi All, > = > I am trying to build xapi via opam install xapi, and getting following er= ror: > = > ---=3D-=3D-=3D Installing xapi.1.0.0 =3D-=3D-=3D > Building xapi.1.0.0: > ./configure --varpatchdir /contrail/opam/system/var/patch --optdir /cont= rail/opam/system/lib/xcp --plugindir /contrail/opam/system/lib/xcp/plugins = --hooksdir /contrail/opam/system/etc/hook-scripts --xapiconf /contrail/opam= /system/etc/xapi.conf --libexecdir /contrail/opam/system/lib/xcp/bin --scri= ptsdir /contrail/opam/system/lib/xcp/scripts --sharedir /contrail/opam/syst= em/share/xcp --webdir /contrail/opam/system/share/xcp/web --xhadir /contrai= l/opam/system/bin/xha --bindir /contrail/opam/system/bin --sbindir /contrai= l/opam/system/bin --etcdir /contrail/opam/system/etc --vardir /var/lib/xcp > make version > omake phase1 > omake phase2 > omake ocaml/xapi/xapi > install -m 0755 ocaml/xapi/xapi.opt /contrail/opam/system/bin/xapi > [ERROR] The compilation of xapi.1.0.0 failed. > Removing xapi.1.0.0. > rm /contrail/opam/system/bin/xapi > = > [ERROR] Failure while processing xapi.1.0.0 > = > = > =3D=3D=3D=3D=3D ERROR while installing xapi.1.0.0 =3D=3D=3D=3D=3D > # opam-version 1.1.1 (d2d459e390e869bf20f1889a5d2cf7933f2851ae) > # os linux > # command ./configure --varpatchdir /contrail/opam/system/var/patch = --optdir /contrail/opam/system/lib/xcp --plugindir /contrail/opam/system/li= b/xcp/plugins --hooksdir /contrail/opam/system/etc/hook-scripts --xapiconf = /contrail/opam/system/etc/xapi.conf --libexecdir /contrail/opam/system/lib/= xcp/bin --scriptsdir /contrail/opam/system/lib/xcp/scripts --sharedir /cont= rail/opam/system/share/xcp --webdir /contrail/opam/system/share/xcp/web --x= hadir /contrail/opam/system/bin/xha --bindir /contrail/opam/system/bin --sb= indir /contrail/opam/system/bin --etcdir /contrail/opam/system/etc --vardir= /var/lib/xcp > # path /contrail/opam/system/build/xapi.1.0.0 > # compiler system (4.01.0) > # exit-code 2 > # env-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.e= nv > # stdout-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.o= ut > # stderr-file /contrail/opam/system/build/xapi.1.0.0/xapi-22122-7afd23.e= rr > ### stdout ### > # Cannot find file topfind. > ### stderr ### > # Unknown directive `require'. > = > =97=97 > = > The configure script is not able to find topfind, as it looks from the me= ssages. However, I do have following set: > = > OCAML_TOPLEVEL_PATH=3D/contrail/opam/system/lib/toplevel > = > As a check, when I run utop and then in the cmd prompt issue, use =93topf= ind=94, it doesn=92t complain. So, as it appears that the configure script = doesn=92t find =93topfind" whereas utop can find it. Does it mean that find= lib could not be resolved properly? > = > I am pretty new to OCaml. Can some one shed some light on it? > = > My xapi code is at following change set: > commit ffd3561cb05e828ffa8646fb9cc91e3c3e721b2f > Merge: 1b6ff5f 8fa2e83 > Author: Dave Scott > Date: Mon Nov 25 03:27:02 2013 -0800 > = > Merge pull request #6 from jonludlam/fusion-vbdfix > = > Relax the rules about ISO vbds coming from ISO SRs > =97=97=97 > and ocaml version is: > = > [root@localhost xapi.1.0.0]# ocaml = > OCaml version 4.01.0 > = > Findlib has been successfully loaded. Additional directives: > #require "package";; to load a package > #list;; to list the available packages > #camlp4o;; to load camlp4 (standard syntax) > #camlp4r;; to load camlp4 (revised syntax) > #predicates "p,q,...";; to set these predicates > Topfind.reset();; to force that packages will be reloaded > #thread;; to enable threads > = > ----- > = > thanks much, > Anirban > = > = > = > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > = _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 03 22:45:25 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Mar 2014 22:45:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKbbe-0000Gn-Ii; Mon, 03 Mar 2014 22:45:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKbbd-0000Gf-9q for xen-api@lists.xen.org; Mon, 03 Mar 2014 22:45:05 +0000 Received: from [85.158.143.35:22929] by server-2.bemta-4.messagelabs.com id 1A/A9-06539-0F505135; Mon, 03 Mar 2014 22:45:04 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-2.tower-21.messagelabs.com!1393886702!9692112!1 X-Originating-IP: [216.32.180.16] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24202 invoked from network); 3 Mar 2014 22:45:03 -0000 Received: from va3ehsobe006.messaging.microsoft.com (HELO va3outboundpool.messaging.microsoft.com) (216.32.180.16) by server-2.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 3 Mar 2014 22:45:03 -0000 Received: from mail163-va3-R.bigfish.com (10.7.14.233) by VA3EHSOBE014.bigfish.com (10.7.40.64) with Microsoft SMTP Server id 14.1.225.22; Mon, 3 Mar 2014 22:45:02 +0000 Received: from mail163-va3 (localhost [127.0.0.1]) by mail163-va3-R.bigfish.com (Postfix) with ESMTP id 8364D1C0071; Mon, 3 Mar 2014 22:45:02 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -3 X-BigFish: VPS-3(zz98dI9371I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de098h8275bh8275dh1de097hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch1155h) Received-SPF: pass (mail163-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(24454002)(51704005)(377454003)(199002)(189002)(4396001)(79102001)(47976001)(50986001)(82746002)(74876001)(74662001)(47446002)(74502001)(56816005)(85852003)(49866001)(47736001)(93136001)(80976001)(85306002)(80022001)(65816001)(83322001)(19580405001)(66066001)(90146001)(2656002)(19580395003)(81542001)(95666003)(77096001)(87936001)(76796001)(87266001)(36756003)(46102001)(51856001)(95416001)(76482001)(54316002)(81686001)(31966008)(83072002)(81816001)(93516002)(92566001)(59766001)(69226001)(76786001)(92726001)(63696002)(94946001)(94316002)(81342001)(53806001)(74366001)(74706001)(56776001)(33656001)(86362001)(83716003)(77982001)(54356001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB776; H:BL2PR05MB193.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:B829DDB7.E137FDA.39D37F97.C24EB631.20314; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail163-va3 (localhost.localdomain [127.0.0.1]) by mail163-va3 (MessageSwitch) id 1393886700978272_32519; Mon, 3 Mar 2014 22:45:00 +0000 (UTC) Received: from VA3EHSMHS004.bigfish.com (unknown [10.7.14.226]) by mail163-va3.bigfish.com (Postfix) with ESMTP id DF665320048; Mon, 3 Mar 2014 22:45:00 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS004.bigfish.com (10.7.99.14) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 3 Mar 2014 22:44:57 +0000 Received: from BY2PR05MB776.namprd05.prod.outlook.com (10.141.224.154) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Mon, 3 Mar 2014 22:44:57 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com (10.242.198.143) by BY2PR05MB776.namprd05.prod.outlook.com (10.141.224.154) with Microsoft SMTP Server (TLS) id 15.0.888.9; Mon, 3 Mar 2014 22:44:55 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) by BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) with mapi id 15.00.0888.003; Mon, 3 Mar 2014 22:44:53 +0000 From: Anirban Chakraborty To: Anil Madhavapeddy Thread-Topic: [Xen-API] build issue with xapi Thread-Index: AQHPNqO/DQJ26lju90S7esAZ24U2dJrPX1iAgACXxAA= Date: Mon, 3 Mar 2014 22:44:53 +0000 Message-ID: References: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> <8BA944B8-0B6B-46E6-B290-FD4541FB77DD@recoil.org> In-Reply-To: <8BA944B8-0B6B-46E6-B290-FD4541FB77DD@recoil.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 0139052FDB Content-ID: <627F6C07359258419A53BE9C8C3BA956@namprd05.prod.outlook.com> MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] build issue with xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mar 3, 2014, at 5:41 AM, Anil Madhavapeddy wrote: > As a workaround, you could try: > = > $ opam switch 4.00.1 # or 4.01.0 > $ opam install xapi > = > This topfind problem tends to only happen with the system compiler. Thanks a lot. switching to 4.00.1 solved the topfind issue. However, now I = see a different issue (given below): =97 - build ocaml/xenops domain.o = = + ocamlfind ocamlopt -syntax camlp4o -package oclock,xml-light2,sexpr,stunn= el,http-svr,netdev,rpclib,threads,xenctrl,xenstore-compat,xenctrlext,stdext= ,cdrom,netdev,oUnit,uuid,xcp-inventory,xcp,xcp.xen,rpclib.syntax -g -dtypes= -thread -warn-error +a-4-6-9-27-28-29 -thread -ccopt -fPIC -I ../xapi -I .= ./util -I .. -c domain.ml File "domain.ml", line 307, characters 6-38: Error: Unbound module Xenctrl.Domain_info =97 My xapi code is at following change set: commit 0320fb13cc176d0864865851672131acaad7be86 Author: David Scott Date: Wed Oct 30 13:58:04 2013 +0000 import_raw_vdi: look for vhd-tool in %{_bindir} and xenstore is at: commit 03df4be36f6cb2236f813dad7b13db8b060060e8 Author: David Scott Date: Wed Sep 11 11:15:14 2013 +0100 Regenerate OASIS =97=97 xenstore build and install went fine. ocamlfind list shows following: xenstore (version: 1.2.4) xenstore-compat (version: 0.9.3) xenstore.client (version: 1.2.4) xenstore.server (version: 1.2.4) xenstore.unix (version: 1.2.4) xenstore_transport (version: 0.9.2) xenstore_transport.lwt (version: 0.9.2) xenstore_transport.unix (version: 0.9.2) Am I missing something in building xapi? My build OS is 2.6.32.43-0.4.1.xs= 1.8.0.847.170785xen. Any pointer will be highly appreciated. Thanks much. Anirban _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 03 22:45:25 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 03 Mar 2014 22:45:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKbbe-0000Gn-Ii; Mon, 03 Mar 2014 22:45:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKbbd-0000Gf-9q for xen-api@lists.xen.org; Mon, 03 Mar 2014 22:45:05 +0000 Received: from [85.158.143.35:22929] by server-2.bemta-4.messagelabs.com id 1A/A9-06539-0F505135; Mon, 03 Mar 2014 22:45:04 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-2.tower-21.messagelabs.com!1393886702!9692112!1 X-Originating-IP: [216.32.180.16] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24202 invoked from network); 3 Mar 2014 22:45:03 -0000 Received: from va3ehsobe006.messaging.microsoft.com (HELO va3outboundpool.messaging.microsoft.com) (216.32.180.16) by server-2.tower-21.messagelabs.com with AES128-SHA encrypted SMTP; 3 Mar 2014 22:45:03 -0000 Received: from mail163-va3-R.bigfish.com (10.7.14.233) by VA3EHSOBE014.bigfish.com (10.7.40.64) with Microsoft SMTP Server id 14.1.225.22; Mon, 3 Mar 2014 22:45:02 +0000 Received: from mail163-va3 (localhost [127.0.0.1]) by mail163-va3-R.bigfish.com (Postfix) with ESMTP id 8364D1C0071; Mon, 3 Mar 2014 22:45:02 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -3 X-BigFish: VPS-3(zz98dI9371I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de098h8275bh8275dh1de097hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch1155h) Received-SPF: pass (mail163-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(24454002)(51704005)(377454003)(199002)(189002)(4396001)(79102001)(47976001)(50986001)(82746002)(74876001)(74662001)(47446002)(74502001)(56816005)(85852003)(49866001)(47736001)(93136001)(80976001)(85306002)(80022001)(65816001)(83322001)(19580405001)(66066001)(90146001)(2656002)(19580395003)(81542001)(95666003)(77096001)(87936001)(76796001)(87266001)(36756003)(46102001)(51856001)(95416001)(76482001)(54316002)(81686001)(31966008)(83072002)(81816001)(93516002)(92566001)(59766001)(69226001)(76786001)(92726001)(63696002)(94946001)(94316002)(81342001)(53806001)(74366001)(74706001)(56776001)(33656001)(86362001)(83716003)(77982001)(54356001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB776; H:BL2PR05MB193.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:B829DDB7.E137FDA.39D37F97.C24EB631.20314; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail163-va3 (localhost.localdomain [127.0.0.1]) by mail163-va3 (MessageSwitch) id 1393886700978272_32519; Mon, 3 Mar 2014 22:45:00 +0000 (UTC) Received: from VA3EHSMHS004.bigfish.com (unknown [10.7.14.226]) by mail163-va3.bigfish.com (Postfix) with ESMTP id DF665320048; Mon, 3 Mar 2014 22:45:00 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS004.bigfish.com (10.7.99.14) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 3 Mar 2014 22:44:57 +0000 Received: from BY2PR05MB776.namprd05.prod.outlook.com (10.141.224.154) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Mon, 3 Mar 2014 22:44:57 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com (10.242.198.143) by BY2PR05MB776.namprd05.prod.outlook.com (10.141.224.154) with Microsoft SMTP Server (TLS) id 15.0.888.9; Mon, 3 Mar 2014 22:44:55 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) by BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) with mapi id 15.00.0888.003; Mon, 3 Mar 2014 22:44:53 +0000 From: Anirban Chakraborty To: Anil Madhavapeddy Thread-Topic: [Xen-API] build issue with xapi Thread-Index: AQHPNqO/DQJ26lju90S7esAZ24U2dJrPX1iAgACXxAA= Date: Mon, 3 Mar 2014 22:44:53 +0000 Message-ID: References: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> <8BA944B8-0B6B-46E6-B290-FD4541FB77DD@recoil.org> In-Reply-To: <8BA944B8-0B6B-46E6-B290-FD4541FB77DD@recoil.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 0139052FDB Content-ID: <627F6C07359258419A53BE9C8C3BA956@namprd05.prod.outlook.com> MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] build issue with xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mar 3, 2014, at 5:41 AM, Anil Madhavapeddy wrote: > As a workaround, you could try: > = > $ opam switch 4.00.1 # or 4.01.0 > $ opam install xapi > = > This topfind problem tends to only happen with the system compiler. Thanks a lot. switching to 4.00.1 solved the topfind issue. However, now I = see a different issue (given below): =97 - build ocaml/xenops domain.o = = + ocamlfind ocamlopt -syntax camlp4o -package oclock,xml-light2,sexpr,stunn= el,http-svr,netdev,rpclib,threads,xenctrl,xenstore-compat,xenctrlext,stdext= ,cdrom,netdev,oUnit,uuid,xcp-inventory,xcp,xcp.xen,rpclib.syntax -g -dtypes= -thread -warn-error +a-4-6-9-27-28-29 -thread -ccopt -fPIC -I ../xapi -I .= ./util -I .. -c domain.ml File "domain.ml", line 307, characters 6-38: Error: Unbound module Xenctrl.Domain_info =97 My xapi code is at following change set: commit 0320fb13cc176d0864865851672131acaad7be86 Author: David Scott Date: Wed Oct 30 13:58:04 2013 +0000 import_raw_vdi: look for vhd-tool in %{_bindir} and xenstore is at: commit 03df4be36f6cb2236f813dad7b13db8b060060e8 Author: David Scott Date: Wed Sep 11 11:15:14 2013 +0100 Regenerate OASIS =97=97 xenstore build and install went fine. ocamlfind list shows following: xenstore (version: 1.2.4) xenstore-compat (version: 0.9.3) xenstore.client (version: 1.2.4) xenstore.server (version: 1.2.4) xenstore.unix (version: 1.2.4) xenstore_transport (version: 0.9.2) xenstore_transport.lwt (version: 0.9.2) xenstore_transport.unix (version: 0.9.2) Am I missing something in building xapi? My build OS is 2.6.32.43-0.4.1.xs= 1.8.0.847.170785xen. Any pointer will be highly appreciated. Thanks much. Anirban _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Mar 04 06:57:36 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 06:57:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjHQ-0005sH-QC; Tue, 04 Mar 2014 06:56:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjHM-0005sA-Ui for xen-api@lists.xen.org; Tue, 04 Mar 2014 06:56:41 +0000 Received: from [85.158.139.211:2325] by server-3.bemta-5.messagelabs.com id 2B/39-13671-82975135; Tue, 04 Mar 2014 06:56:40 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1393916198!7101926!1 X-Originating-IP: [209.85.216.41] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15073 invoked from network); 4 Mar 2014 06:56:39 -0000 Received: from mail-qa0-f41.google.com (HELO mail-qa0-f41.google.com) (209.85.216.41) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Mar 2014 06:56:39 -0000 Received: by mail-qa0-f41.google.com with SMTP id j5so4554312qaq.14 for ; Mon, 03 Mar 2014 22:56:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=vXqMu4oLmWsO00DypVLqs/4wa5vk7e4xacg2twiDUJ0=; b=p13bKmylV5b3LfpCNAfLVVKd9rDgUS2HE50BknXPb/cEOZgFehJmYAPizvU8qii7+q /+pxgLhh6Rj8QlYU5gmCVvcfTS1EB4O+uugurNOs1SFmscQdrp9FGUtdzRyV83eQ6fwu dtW8gA/h/NBl1AUd4YC68dpp1JGai1rZZY397iqU8my3V6aZn2F8NYNB8XNxZP9rKOwV 9yiSuB9h/KVzzxbItIF6vfjyJ25U3QyK0EpRCiavqjurSmImIS+M85PbcKZnXXVRxAnG D7NtxkdorakWGIfaMs03pcu4+u1IRKFSoLbhUQfRAJNfecJG5onGwoW2WqsfoszE4wwZ r+hw== MIME-Version: 1.0 X-Received: by 10.140.91.228 with SMTP id z91mr27624073qgd.32.1393916198172; Mon, 03 Mar 2014 22:56:38 -0800 (PST) Received: by 10.140.83.180 with HTTP; Mon, 3 Mar 2014 22:56:38 -0800 (PST) Date: Mon, 3 Mar 2014 23:56:38 -0700 Message-ID: From: jacek burghardt To: "xen-api@lists.xen.org" Subject: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6129334031833305626==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6129334031833305626== Content-Type: multipart/alternative; boundary=001a113a7b1ed6bc2304f3c2678b --001a113a7b1ed6bc2304f3c2678b Content-Type: text/plain; charset=ISO-8859-1 I am trying to install xapi on arch linux but - install message_switch.0.9.2 - install xenctrl.5.0.0 - install xenstore_transport.1.0.0 failed xenstore_transport.1.0.0 gives this error Error: Unbound module Xs_client_lwt how I can fix it ? --001a113a7b1ed6bc2304f3c2678b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I am trying to install xapi on arch linux but =A0
- in= stall =A0 message_switch.0.9.2
=A0- install =A0 xenctrl.5.0.0
=A0- install =A0 xenstore_transport.1.0.0
failed
xenst= ore_transport.1.0.0 gives this error
=A0Error: Unbound module Xs_client_lwt how I can fix it ?


--001a113a7b1ed6bc2304f3c2678b-- --===============6129334031833305626== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6129334031833305626==-- From xen-api-bounces@lists.xen.org Tue Mar 04 06:57:36 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 06:57:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjHQ-0005sH-QC; Tue, 04 Mar 2014 06:56:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjHM-0005sA-Ui for xen-api@lists.xen.org; Tue, 04 Mar 2014 06:56:41 +0000 Received: from [85.158.139.211:2325] by server-3.bemta-5.messagelabs.com id 2B/39-13671-82975135; Tue, 04 Mar 2014 06:56:40 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1393916198!7101926!1 X-Originating-IP: [209.85.216.41] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15073 invoked from network); 4 Mar 2014 06:56:39 -0000 Received: from mail-qa0-f41.google.com (HELO mail-qa0-f41.google.com) (209.85.216.41) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Mar 2014 06:56:39 -0000 Received: by mail-qa0-f41.google.com with SMTP id j5so4554312qaq.14 for ; Mon, 03 Mar 2014 22:56:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=vXqMu4oLmWsO00DypVLqs/4wa5vk7e4xacg2twiDUJ0=; b=p13bKmylV5b3LfpCNAfLVVKd9rDgUS2HE50BknXPb/cEOZgFehJmYAPizvU8qii7+q /+pxgLhh6Rj8QlYU5gmCVvcfTS1EB4O+uugurNOs1SFmscQdrp9FGUtdzRyV83eQ6fwu dtW8gA/h/NBl1AUd4YC68dpp1JGai1rZZY397iqU8my3V6aZn2F8NYNB8XNxZP9rKOwV 9yiSuB9h/KVzzxbItIF6vfjyJ25U3QyK0EpRCiavqjurSmImIS+M85PbcKZnXXVRxAnG D7NtxkdorakWGIfaMs03pcu4+u1IRKFSoLbhUQfRAJNfecJG5onGwoW2WqsfoszE4wwZ r+hw== MIME-Version: 1.0 X-Received: by 10.140.91.228 with SMTP id z91mr27624073qgd.32.1393916198172; Mon, 03 Mar 2014 22:56:38 -0800 (PST) Received: by 10.140.83.180 with HTTP; Mon, 3 Mar 2014 22:56:38 -0800 (PST) Date: Mon, 3 Mar 2014 23:56:38 -0700 Message-ID: From: jacek burghardt To: "xen-api@lists.xen.org" Subject: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6129334031833305626==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6129334031833305626== Content-Type: multipart/alternative; boundary=001a113a7b1ed6bc2304f3c2678b --001a113a7b1ed6bc2304f3c2678b Content-Type: text/plain; charset=ISO-8859-1 I am trying to install xapi on arch linux but - install message_switch.0.9.2 - install xenctrl.5.0.0 - install xenstore_transport.1.0.0 failed xenstore_transport.1.0.0 gives this error Error: Unbound module Xs_client_lwt how I can fix it ? --001a113a7b1ed6bc2304f3c2678b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I am trying to install xapi on arch linux but =A0
- in= stall =A0 message_switch.0.9.2
=A0- install =A0 xenctrl.5.0.0
=A0- install =A0 xenstore_transport.1.0.0
failed
xenst= ore_transport.1.0.0 gives this error
=A0Error: Unbound module Xs_client_lwt how I can fix it ?


--001a113a7b1ed6bc2304f3c2678b-- --===============6129334031833305626== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6129334031833305626==-- From xen-api-bounces@lists.xen.org Tue Mar 04 07:07:47 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 07:07:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjRZ-0006O0-42; Tue, 04 Mar 2014 07:07:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjRX-0006Ns-EF for xen-api@lists.xen.org; Tue, 04 Mar 2014 07:07:11 +0000 Received: from [85.158.139.211:63439] by server-7.bemta-5.messagelabs.com id D1/00-14867-E9B75135; Tue, 04 Mar 2014 07:07:10 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-11.tower-206.messagelabs.com!1393916828!2971154!1 X-Originating-IP: [207.46.163.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7704 invoked from network); 4 Mar 2014 07:07:09 -0000 Received: from co9ehsobe004.messaging.microsoft.com (HELO co9outboundpool.messaging.microsoft.com) (207.46.163.27) by server-11.tower-206.messagelabs.com with AES128-SHA encrypted SMTP; 4 Mar 2014 07:07:09 -0000 Received: from mail71-co9-R.bigfish.com (10.236.132.231) by CO9EHSOBE034.bigfish.com (10.236.130.97) with Microsoft SMTP Server id 14.1.225.22; Tue, 4 Mar 2014 07:07:07 +0000 Received: from mail71-co9 (localhost [127.0.0.1]) by mail71-co9-R.bigfish.com (Postfix) with ESMTP id B719C420046; Tue, 4 Mar 2014 07:07:07 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -2 X-BigFish: VPS-2(zz98dI9371Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hz8dhz1de098h8275bh1de097hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch1155h) Received-SPF: pass (mail71-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(189002)(199002)(24454002)(377454003)(36756003)(19580405001)(76786001)(81686001)(47736001)(83072002)(49866001)(76796001)(4396001)(95666003)(19580395003)(81816001)(69226001)(47976001)(50986001)(82746002)(83322001)(80976001)(85852003)(2656002)(81542001)(86362001)(54316002)(33656001)(93516002)(77096001)(74706001)(74366001)(79102001)(63696002)(66066001)(90146001)(56816005)(76482001)(46102001)(80022001)(95416001)(59766001)(87936001)(92566001)(85306002)(83716003)(87266001)(81342001)(74662001)(65816001)(53806001)(94946001)(51856001)(93136001)(74502001)(94316002)(31966008)(47446002)(1411001)(77982001)(54356001)(74876001)(56776001)(92726001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB777; H:BL2PR05MB193.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:AAF662BE.1C3CAD18.D1CABC5B.805D5888.20187; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail71-co9 (localhost.localdomain [127.0.0.1]) by mail71-co9 (MessageSwitch) id 1393916826196158_10886; Tue, 4 Mar 2014 07:07:06 +0000 (UTC) Received: from CO9EHSMHS023.bigfish.com (unknown [10.236.132.232]) by mail71-co9.bigfish.com (Postfix) with ESMTP id 21765600B5; Tue, 4 Mar 2014 07:07:06 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS023.bigfish.com (10.236.130.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 4 Mar 2014 07:07:05 +0000 Received: from CO2PR05MB777.namprd05.prod.outlook.com (10.141.226.139) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Tue, 4 Mar 2014 07:07:04 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com (10.242.198.143) by CO2PR05MB777.namprd05.prod.outlook.com (10.141.226.139) with Microsoft SMTP Server (TLS) id 15.0.888.9; Tue, 4 Mar 2014 07:07:02 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) by BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) with mapi id 15.00.0888.003; Tue, 4 Mar 2014 07:07:01 +0000 From: Anirban Chakraborty To: jacek burghardt Thread-Topic: [Xen-API] archlinux and xcp Thread-Index: AQHPN3cwYhxrb5zhkUi2FZVPJciinZrQgb4A Date: Tue, 4 Mar 2014 07:07:00 +0000 Message-ID: <93C78E4A-5A8B-448F-B3F8-82F4212D8EF6@juniper.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 01401330D1 Content-ID: <49FED3B40282F04FB7C555DC49A38BE2@namprd05.prod.outlook.com> MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mar 3, 2014, at 10:56 PM, jacek burghardt wr= ote: > I am trying to install xapi on arch linux but = > - install message_switch.0.9.2 > - install xenctrl.5.0.0 > - install xenstore_transport.1.0.0 > failed > xenstore_transport.1.0.0 gives this error > Error: Unbound module Xs_client_lwt how I can fix it ? > = The way I solved it was: cd to xenstore.2.0.0 under ~/.opam/packages.dev git reset =97hard 1.2.4 make and make install This will not add the entry to installed file, so edit ~/.opam/system/insta= lled and add an entry for xenstore 2.0.0 Once this is done, cd to packages.dev/xenstore_transport and git reset =97h= ard 0.9.2 followed by make and make install. ocamlfind list shows following in my system: xenstore (version: 1.2.4) xenstore-compat (version: 0.9.3) xenstore.client (version: 1.2.4) xenstore.server (version: 1.2.4) xenstore.unix (version: 1.2.4) xenstore_transport (version: 0.9.2) xenstore_transport.lwt (version: 0.9.2) xenstore_transport.unix (version: 0.9.2) -Anirban = _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Mar 04 07:07:47 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 07:07:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjRZ-0006O0-42; Tue, 04 Mar 2014 07:07:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjRX-0006Ns-EF for xen-api@lists.xen.org; Tue, 04 Mar 2014 07:07:11 +0000 Received: from [85.158.139.211:63439] by server-7.bemta-5.messagelabs.com id D1/00-14867-E9B75135; Tue, 04 Mar 2014 07:07:10 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-11.tower-206.messagelabs.com!1393916828!2971154!1 X-Originating-IP: [207.46.163.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7704 invoked from network); 4 Mar 2014 07:07:09 -0000 Received: from co9ehsobe004.messaging.microsoft.com (HELO co9outboundpool.messaging.microsoft.com) (207.46.163.27) by server-11.tower-206.messagelabs.com with AES128-SHA encrypted SMTP; 4 Mar 2014 07:07:09 -0000 Received: from mail71-co9-R.bigfish.com (10.236.132.231) by CO9EHSOBE034.bigfish.com (10.236.130.97) with Microsoft SMTP Server id 14.1.225.22; Tue, 4 Mar 2014 07:07:07 +0000 Received: from mail71-co9 (localhost [127.0.0.1]) by mail71-co9-R.bigfish.com (Postfix) with ESMTP id B719C420046; Tue, 4 Mar 2014 07:07:07 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -2 X-BigFish: VPS-2(zz98dI9371Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hz8dhz1de098h8275bh1de097hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch1155h) Received-SPF: pass (mail71-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(189002)(199002)(24454002)(377454003)(36756003)(19580405001)(76786001)(81686001)(47736001)(83072002)(49866001)(76796001)(4396001)(95666003)(19580395003)(81816001)(69226001)(47976001)(50986001)(82746002)(83322001)(80976001)(85852003)(2656002)(81542001)(86362001)(54316002)(33656001)(93516002)(77096001)(74706001)(74366001)(79102001)(63696002)(66066001)(90146001)(56816005)(76482001)(46102001)(80022001)(95416001)(59766001)(87936001)(92566001)(85306002)(83716003)(87266001)(81342001)(74662001)(65816001)(53806001)(94946001)(51856001)(93136001)(74502001)(94316002)(31966008)(47446002)(1411001)(77982001)(54356001)(74876001)(56776001)(92726001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB777; H:BL2PR05MB193.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:AAF662BE.1C3CAD18.D1CABC5B.805D5888.20187; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail71-co9 (localhost.localdomain [127.0.0.1]) by mail71-co9 (MessageSwitch) id 1393916826196158_10886; Tue, 4 Mar 2014 07:07:06 +0000 (UTC) Received: from CO9EHSMHS023.bigfish.com (unknown [10.236.132.232]) by mail71-co9.bigfish.com (Postfix) with ESMTP id 21765600B5; Tue, 4 Mar 2014 07:07:06 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS023.bigfish.com (10.236.130.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 4 Mar 2014 07:07:05 +0000 Received: from CO2PR05MB777.namprd05.prod.outlook.com (10.141.226.139) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Tue, 4 Mar 2014 07:07:04 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com (10.242.198.143) by CO2PR05MB777.namprd05.prod.outlook.com (10.141.226.139) with Microsoft SMTP Server (TLS) id 15.0.888.9; Tue, 4 Mar 2014 07:07:02 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) by BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) with mapi id 15.00.0888.003; Tue, 4 Mar 2014 07:07:01 +0000 From: Anirban Chakraborty To: jacek burghardt Thread-Topic: [Xen-API] archlinux and xcp Thread-Index: AQHPN3cwYhxrb5zhkUi2FZVPJciinZrQgb4A Date: Tue, 4 Mar 2014 07:07:00 +0000 Message-ID: <93C78E4A-5A8B-448F-B3F8-82F4212D8EF6@juniper.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 01401330D1 Content-ID: <49FED3B40282F04FB7C555DC49A38BE2@namprd05.prod.outlook.com> MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mar 3, 2014, at 10:56 PM, jacek burghardt wr= ote: > I am trying to install xapi on arch linux but = > - install message_switch.0.9.2 > - install xenctrl.5.0.0 > - install xenstore_transport.1.0.0 > failed > xenstore_transport.1.0.0 gives this error > Error: Unbound module Xs_client_lwt how I can fix it ? > = The way I solved it was: cd to xenstore.2.0.0 under ~/.opam/packages.dev git reset =97hard 1.2.4 make and make install This will not add the entry to installed file, so edit ~/.opam/system/insta= lled and add an entry for xenstore 2.0.0 Once this is done, cd to packages.dev/xenstore_transport and git reset =97h= ard 0.9.2 followed by make and make install. ocamlfind list shows following in my system: xenstore (version: 1.2.4) xenstore-compat (version: 0.9.3) xenstore.client (version: 1.2.4) xenstore.server (version: 1.2.4) xenstore.unix (version: 1.2.4) xenstore_transport (version: 0.9.2) xenstore_transport.lwt (version: 0.9.2) xenstore_transport.unix (version: 0.9.2) -Anirban = _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Mar 04 07:22:18 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 07:22:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjfy-0006yV-KN; Tue, 04 Mar 2014 07:22:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjfx-0006yA-Ok for xen-api@lists.xen.org; Tue, 04 Mar 2014 07:22:06 +0000 Received: from [85.158.139.211:54507] by server-14.bemta-5.messagelabs.com id 8C/16-27598-C1F75135; Tue, 04 Mar 2014 07:22:04 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1393917722!2974899!1 X-Originating-IP: [209.85.216.50] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31018 invoked from network); 4 Mar 2014 07:22:03 -0000 Received: from mail-qa0-f50.google.com (HELO mail-qa0-f50.google.com) (209.85.216.50) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Mar 2014 07:22:03 -0000 Received: by mail-qa0-f50.google.com with SMTP id o15so3060756qap.23 for ; Mon, 03 Mar 2014 23:22:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CJT25wVGy45LhKJHBBclPVLaWeUlCviuc75Q52efdHQ=; b=jmadDMqO3zO0+iYvKL+px1gHpn/xD6/m9b6wPjgBFQhymvPDHGrPX/A9ZpfxNznJeh B2eX/etttN+OM7btztu/ITvsLD8V0t20gExMIRPk+k++hztV9gSH9DkV0dWwqeLYZI4B l8+zOPyGYa1xigNhHpTES7Iznd4LZlIoGlFhr9YcMiKmG1L7nXEugIwlidyuIfpGQsHT qcw3/Qt/5aClxzce27oyOsa9PdFR8jQMhmLwAH6OQHA45m3t4dpj+9BPclAsfiGQdOIg 3tlh6IaoslRRoNsbw1HdvJPNGKHsMk8lp87vyru3cfd78lPWy77qtfn+6UuAOlXAO+qa jTGw== MIME-Version: 1.0 X-Received: by 10.224.87.193 with SMTP id x1mr28963152qal.70.1393917722398; Mon, 03 Mar 2014 23:22:02 -0800 (PST) Received: by 10.140.83.180 with HTTP; Mon, 3 Mar 2014 23:22:02 -0800 (PST) In-Reply-To: <93C78E4A-5A8B-448F-B3F8-82F4212D8EF6@juniper.net> References: <93C78E4A-5A8B-448F-B3F8-82F4212D8EF6@juniper.net> Date: Tue, 4 Mar 2014 00:22:02 -0700 Message-ID: From: jacek burghardt To: Anirban Chakraborty Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0470118217203018161==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0470118217203018161== Content-Type: multipart/alternative; boundary=001a11c3e246b094e004f3c2c2a9 --001a11c3e246b094e004f3c2c2a9 Content-Type: text/plain; charset=ISO-8859-1 Thank you for the info did you get xapi compiled ? On Tue, Mar 4, 2014 at 12:07 AM, Anirban Chakraborty wrote: > > On Mar 3, 2014, at 10:56 PM, jacek burghardt > wrote: > > > I am trying to install xapi on arch linux but > > - install message_switch.0.9.2 > > - install xenctrl.5.0.0 > > - install xenstore_transport.1.0.0 > > failed > > xenstore_transport.1.0.0 gives this error > > Error: Unbound module Xs_client_lwt how I can fix it ? > > > > The way I solved it was: > cd to xenstore.2.0.0 under ~/.opam/packages.dev > git reset --hard 1.2.4 > make and make install > This will not add the entry to installed file, so edit > ~/.opam/system/installed and add an entry for xenstore 2.0.0 > Once this is done, cd to packages.dev/xenstore_transport and git reset > --hard 0.9.2 followed by make and make install. > > ocamlfind list shows following in my system: > > xenstore (version: 1.2.4) > xenstore-compat (version: 0.9.3) > xenstore.client (version: 1.2.4) > xenstore.server (version: 1.2.4) > xenstore.unix (version: 1.2.4) > xenstore_transport (version: 0.9.2) > xenstore_transport.lwt (version: 0.9.2) > xenstore_transport.unix (version: 0.9.2) > > -Anirban > > --001a11c3e246b094e004f3c2c2a9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thank you for the info did you get xapi compiled ?


On Tue, Mar 4, = 2014 at 12:07 AM, Anirban Chakraborty <abchak@juniper.net> = wrote:

On Mar 3, 2014, at 10:56 PM, jacek burghardt <jaceksburghardt@gmail.com> wrote:

> I am trying to install xapi on arch linux but
> - install   message_switch.0.9.2
>  - install   xenctrl.5.0.0
>  - install   xenstore_transport.1.0.0
> failed
> xenstore_transport.1.0.0 gives this error
>  Error: Unbound module Xs_client_lwt how I can fix it ?
>

The way I solved it was:
cd to xenstore.2.0.0 under ~/.opam/packages.dev
git reset —hard 1.2.4
make and make install
This will not add the entry to installed file, so edit ~/.opam/system/insta= lled and add an entry for xenstore 2.0.0
Once this is done, cd to packages.dev/xenstore_transport and git reset &mda= sh;hard 0.9.2 followed by make and make install.

ocamlfind list shows following in my system:

xenstore            (version: 1.2.4)
xenstore-compat     (version: 0.9.3)
xenstore.client     (version: 1.2.4)
xenstore.server     (version: 1.2.4)
xenstore.unix       (version: 1.2.4)
xenstore_transport  (version: 0.9.2)
xenstore_transport.lwt (version: 0.9.2)
xenstore_transport.unix (version: 0.9.2)

-Anirban


--001a11c3e246b094e004f3c2c2a9-- --===============0470118217203018161== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0470118217203018161==-- From xen-api-bounces@lists.xen.org Tue Mar 04 07:22:18 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 07:22:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjfy-0006yV-KN; Tue, 04 Mar 2014 07:22:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKjfx-0006yA-Ok for xen-api@lists.xen.org; Tue, 04 Mar 2014 07:22:06 +0000 Received: from [85.158.139.211:54507] by server-14.bemta-5.messagelabs.com id 8C/16-27598-C1F75135; Tue, 04 Mar 2014 07:22:04 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1393917722!2974899!1 X-Originating-IP: [209.85.216.50] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31018 invoked from network); 4 Mar 2014 07:22:03 -0000 Received: from mail-qa0-f50.google.com (HELO mail-qa0-f50.google.com) (209.85.216.50) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Mar 2014 07:22:03 -0000 Received: by mail-qa0-f50.google.com with SMTP id o15so3060756qap.23 for ; Mon, 03 Mar 2014 23:22:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CJT25wVGy45LhKJHBBclPVLaWeUlCviuc75Q52efdHQ=; b=jmadDMqO3zO0+iYvKL+px1gHpn/xD6/m9b6wPjgBFQhymvPDHGrPX/A9ZpfxNznJeh B2eX/etttN+OM7btztu/ITvsLD8V0t20gExMIRPk+k++hztV9gSH9DkV0dWwqeLYZI4B l8+zOPyGYa1xigNhHpTES7Iznd4LZlIoGlFhr9YcMiKmG1L7nXEugIwlidyuIfpGQsHT qcw3/Qt/5aClxzce27oyOsa9PdFR8jQMhmLwAH6OQHA45m3t4dpj+9BPclAsfiGQdOIg 3tlh6IaoslRRoNsbw1HdvJPNGKHsMk8lp87vyru3cfd78lPWy77qtfn+6UuAOlXAO+qa jTGw== MIME-Version: 1.0 X-Received: by 10.224.87.193 with SMTP id x1mr28963152qal.70.1393917722398; Mon, 03 Mar 2014 23:22:02 -0800 (PST) Received: by 10.140.83.180 with HTTP; Mon, 3 Mar 2014 23:22:02 -0800 (PST) In-Reply-To: <93C78E4A-5A8B-448F-B3F8-82F4212D8EF6@juniper.net> References: <93C78E4A-5A8B-448F-B3F8-82F4212D8EF6@juniper.net> Date: Tue, 4 Mar 2014 00:22:02 -0700 Message-ID: From: jacek burghardt To: Anirban Chakraborty Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0470118217203018161==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0470118217203018161== Content-Type: multipart/alternative; boundary=001a11c3e246b094e004f3c2c2a9 --001a11c3e246b094e004f3c2c2a9 Content-Type: text/plain; charset=ISO-8859-1 Thank you for the info did you get xapi compiled ? On Tue, Mar 4, 2014 at 12:07 AM, Anirban Chakraborty wrote: > > On Mar 3, 2014, at 10:56 PM, jacek burghardt > wrote: > > > I am trying to install xapi on arch linux but > > - install message_switch.0.9.2 > > - install xenctrl.5.0.0 > > - install xenstore_transport.1.0.0 > > failed > > xenstore_transport.1.0.0 gives this error > > Error: Unbound module Xs_client_lwt how I can fix it ? > > > > The way I solved it was: > cd to xenstore.2.0.0 under ~/.opam/packages.dev > git reset --hard 1.2.4 > make and make install > This will not add the entry to installed file, so edit > ~/.opam/system/installed and add an entry for xenstore 2.0.0 > Once this is done, cd to packages.dev/xenstore_transport and git reset > --hard 0.9.2 followed by make and make install. > > ocamlfind list shows following in my system: > > xenstore (version: 1.2.4) > xenstore-compat (version: 0.9.3) > xenstore.client (version: 1.2.4) > xenstore.server (version: 1.2.4) > xenstore.unix (version: 1.2.4) > xenstore_transport (version: 0.9.2) > xenstore_transport.lwt (version: 0.9.2) > xenstore_transport.unix (version: 0.9.2) > > -Anirban > > --001a11c3e246b094e004f3c2c2a9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thank you for the info did you get xapi compiled ?


On Tue, Mar 4, = 2014 at 12:07 AM, Anirban Chakraborty <abchak@juniper.net> = wrote:

On Mar 3, 2014, at 10:56 PM, jacek burghardt <jaceksburghardt@gmail.com> wrote:

> I am trying to install xapi on arch linux but
> - install   message_switch.0.9.2
>  - install   xenctrl.5.0.0
>  - install   xenstore_transport.1.0.0
> failed
> xenstore_transport.1.0.0 gives this error
>  Error: Unbound module Xs_client_lwt how I can fix it ?
>

The way I solved it was:
cd to xenstore.2.0.0 under ~/.opam/packages.dev
git reset —hard 1.2.4
make and make install
This will not add the entry to installed file, so edit ~/.opam/system/insta= lled and add an entry for xenstore 2.0.0
Once this is done, cd to packages.dev/xenstore_transport and git reset &mda= sh;hard 0.9.2 followed by make and make install.

ocamlfind list shows following in my system:

xenstore            (version: 1.2.4)
xenstore-compat     (version: 0.9.3)
xenstore.client     (version: 1.2.4)
xenstore.server     (version: 1.2.4)
xenstore.unix       (version: 1.2.4)
xenstore_transport  (version: 0.9.2)
xenstore_transport.lwt (version: 0.9.2)
xenstore_transport.unix (version: 0.9.2)

-Anirban


--001a11c3e246b094e004f3c2c2a9-- --===============0470118217203018161== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0470118217203018161==-- From xen-api-bounces@lists.xen.org Tue Mar 04 17:42:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 17:42:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKtM3-0008QX-M9; Tue, 04 Mar 2014 17:42:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKtM1-0008QK-HI for xen-api@lists.xen.org; Tue, 04 Mar 2014 17:42:09 +0000 Received: from [85.158.139.211:58133] by server-8.bemta-5.messagelabs.com id DB/CA-05298-07016135; Tue, 04 Mar 2014 17:42:08 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1393954926!7713020!1 X-Originating-IP: [209.85.192.41] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23084 invoked from network); 4 Mar 2014 17:42:07 -0000 Received: from mail-qg0-f41.google.com (HELO mail-qg0-f41.google.com) (209.85.192.41) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Mar 2014 17:42:07 -0000 Received: by mail-qg0-f41.google.com with SMTP id i50so16270158qgf.0 for ; Tue, 04 Mar 2014 09:42:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=82z8wGfcF+SqGb0zh9CmzB9uNTfdgjDrLwllwmX6t0g=; b=W/uWqnDhr1DfmVRRStzs1w4CJ4SAvOZeyPjwh0pNJu8PNO/yp1oJrgrr34tbpvDr8F EzQikBAlR6dmeg22d2ldZl9zdI+Z8WJ1KwNvoXrZm8ZzkT5PI+6OAWnaA0JsfsmFOEjV KNRQlJ7o9vwaCeJtDakEDFVglsoxJDMjhvQYi/aweivMmi0cyPNb+lB8pRjdKQThbiNJ NZubkcycvjLa7ml12nt1Ckn0Z/GIwix17uL4PQN76r1xK8Dfw6hH9N8g6taZoKjQjPmO Ufs/62Y6EIJ9p1md/+i7WcEBFUU01gIHMoytS/Nx6H78dRuAyZJ8rkMb5J5vQrxuuGc+ Fznw== MIME-Version: 1.0 X-Received: by 10.140.94.113 with SMTP id f104mr1154549qge.64.1393954926316; Tue, 04 Mar 2014 09:42:06 -0800 (PST) Received: by 10.140.83.180 with HTTP; Tue, 4 Mar 2014 09:42:06 -0800 (PST) In-Reply-To: References: Date: Tue, 4 Mar 2014 10:42:06 -0700 Message-ID: From: jacek burghardt To: "xen-api@lists.xen.org" Subject: Re: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0219745688932712394==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0219745688932712394== Content-Type: multipart/alternative; boundary=001a113aabac37512404f3cb6c9c --001a113aabac37512404f3cb6c9c Content-Type: text/plain; charset=ISO-8859-1 Did anyone compiled xen-api on archlinux ? What is the source of Xs_client_lwt xenstore ? File "lib/xs.ml", line 1, characters 8-28: # Error: Unbound module Xs_client_lwt # Command exited with code 2. I am couple packages away from xen-api I had tried arch linux git version but it seems buggy as claims to be missing packages that had been installed with omap. I hope I can get some help. On Mon, Mar 3, 2014 at 11:56 PM, jacek burghardt wrote: > I am trying to install xapi on arch linux but > - install message_switch.0.9.2 > - install xenctrl.5.0.0 > - install xenstore_transport.1.0.0 > failed > xenstore_transport.1.0.0 gives this error > Error: Unbound module Xs_client_lwt how I can fix it ? > > > --001a113aabac37512404f3cb6c9c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Did anyone compiled xen-api on =A0archlinux ? What is the = source of=A0Xs_client_lwt xenstore ?
=A0File "lib/xs.ml", line 1, characters 8-28:
# Error: Unbound mod= ule Xs_client_lwt
# Command exited with code 2.
I am couple packages away from= xen-api
I had tried arch linux git version but it seems bu= ggy as claims to be missing packages that had been installed with omap.
I hope I can get some help.

=
On Mon, Mar 3, 2014 at 11:56 PM, jacek burgh= ardt <jaceksburghardt@gmail.com> wrote:
I am trying to install xapi= on arch linux but =A0
- install =A0 message_switch.0.9.2
=A0- inst= all =A0 xenctrl.5.0.0
=A0- install =A0 xenstore_transport.1.0.0
failed
x= enstore_transport.1.0.0 gives this error
=A0Error: Unbound module Xs_client_lwt how I can fix it ?



--001a113aabac37512404f3cb6c9c-- --===============0219745688932712394== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0219745688932712394==-- From xen-api-bounces@lists.xen.org Tue Mar 04 17:42:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 17:42:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKtM3-0008QX-M9; Tue, 04 Mar 2014 17:42:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKtM1-0008QK-HI for xen-api@lists.xen.org; Tue, 04 Mar 2014 17:42:09 +0000 Received: from [85.158.139.211:58133] by server-8.bemta-5.messagelabs.com id DB/CA-05298-07016135; Tue, 04 Mar 2014 17:42:08 +0000 X-Env-Sender: jaceksburghardt@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1393954926!7713020!1 X-Originating-IP: [209.85.192.41] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23084 invoked from network); 4 Mar 2014 17:42:07 -0000 Received: from mail-qg0-f41.google.com (HELO mail-qg0-f41.google.com) (209.85.192.41) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Mar 2014 17:42:07 -0000 Received: by mail-qg0-f41.google.com with SMTP id i50so16270158qgf.0 for ; Tue, 04 Mar 2014 09:42:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=82z8wGfcF+SqGb0zh9CmzB9uNTfdgjDrLwllwmX6t0g=; b=W/uWqnDhr1DfmVRRStzs1w4CJ4SAvOZeyPjwh0pNJu8PNO/yp1oJrgrr34tbpvDr8F EzQikBAlR6dmeg22d2ldZl9zdI+Z8WJ1KwNvoXrZm8ZzkT5PI+6OAWnaA0JsfsmFOEjV KNRQlJ7o9vwaCeJtDakEDFVglsoxJDMjhvQYi/aweivMmi0cyPNb+lB8pRjdKQThbiNJ NZubkcycvjLa7ml12nt1Ckn0Z/GIwix17uL4PQN76r1xK8Dfw6hH9N8g6taZoKjQjPmO Ufs/62Y6EIJ9p1md/+i7WcEBFUU01gIHMoytS/Nx6H78dRuAyZJ8rkMb5J5vQrxuuGc+ Fznw== MIME-Version: 1.0 X-Received: by 10.140.94.113 with SMTP id f104mr1154549qge.64.1393954926316; Tue, 04 Mar 2014 09:42:06 -0800 (PST) Received: by 10.140.83.180 with HTTP; Tue, 4 Mar 2014 09:42:06 -0800 (PST) In-Reply-To: References: Date: Tue, 4 Mar 2014 10:42:06 -0700 Message-ID: From: jacek burghardt To: "xen-api@lists.xen.org" Subject: Re: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0219745688932712394==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0219745688932712394== Content-Type: multipart/alternative; boundary=001a113aabac37512404f3cb6c9c --001a113aabac37512404f3cb6c9c Content-Type: text/plain; charset=ISO-8859-1 Did anyone compiled xen-api on archlinux ? What is the source of Xs_client_lwt xenstore ? File "lib/xs.ml", line 1, characters 8-28: # Error: Unbound module Xs_client_lwt # Command exited with code 2. I am couple packages away from xen-api I had tried arch linux git version but it seems buggy as claims to be missing packages that had been installed with omap. I hope I can get some help. On Mon, Mar 3, 2014 at 11:56 PM, jacek burghardt wrote: > I am trying to install xapi on arch linux but > - install message_switch.0.9.2 > - install xenctrl.5.0.0 > - install xenstore_transport.1.0.0 > failed > xenstore_transport.1.0.0 gives this error > Error: Unbound module Xs_client_lwt how I can fix it ? > > > --001a113aabac37512404f3cb6c9c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Did anyone compiled xen-api on =A0archlinux ? What is the = source of=A0Xs_client_lwt xenstore ?
=A0File "lib/xs.ml", line 1, characters 8-28:
# Error: Unbound mod= ule Xs_client_lwt
# Command exited with code 2.
I am couple packages away from= xen-api
I had tried arch linux git version but it seems bu= ggy as claims to be missing packages that had been installed with omap.
I hope I can get some help.

=
On Mon, Mar 3, 2014 at 11:56 PM, jacek burgh= ardt <jaceksburghardt@gmail.com> wrote:
I am trying to install xapi= on arch linux but =A0
- install =A0 message_switch.0.9.2
=A0- inst= all =A0 xenctrl.5.0.0
=A0- install =A0 xenstore_transport.1.0.0
failed
x= enstore_transport.1.0.0 gives this error
=A0Error: Unbound module Xs_client_lwt how I can fix it ?



--001a113aabac37512404f3cb6c9c-- --===============0219745688932712394== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0219745688932712394==-- From xen-api-bounces@lists.xen.org Tue Mar 04 17:45:04 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 17:45:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKtOg-0000BS-4W; Tue, 04 Mar 2014 17:44:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKtOe-0000BJ-Tn for xen-api@lists.xen.org; Tue, 04 Mar 2014 17:44:53 +0000 Received: from [193.109.254.147:59177] by server-12.bemta-14.messagelabs.com id 3D/BE-17220-41116135; Tue, 04 Mar 2014 17:44:52 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-4.tower-27.messagelabs.com!1393955090!4579452!1 X-Originating-IP: [207.46.163.26] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2103 invoked from network); 4 Mar 2014 17:44:51 -0000 Received: from co9ehsobe003.messaging.microsoft.com (HELO co9outboundpool.messaging.microsoft.com) (207.46.163.26) by server-4.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 4 Mar 2014 17:44:51 -0000 Received: from mail217-co9-R.bigfish.com (10.236.132.238) by CO9EHSOBE004.bigfish.com (10.236.130.67) with Microsoft SMTP Server id 14.1.225.22; Tue, 4 Mar 2014 17:44:49 +0000 Received: from mail217-co9 (localhost [127.0.0.1]) by mail217-co9-R.bigfish.com (Postfix) with ESMTP id 4700FE0032B; Tue, 4 Mar 2014 17:44:49 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -2 X-BigFish: VPS-2(zz98dI9371Ida00hdc73hzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hz8dhz1de098h8275bh1de097hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2184h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch1155h) Received-SPF: pass (mail217-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(199002)(189002)(24454002)(377454003)(82746002)(81816001)(83716003)(85806002)(77096001)(81686001)(87266001)(95666003)(76786001)(47446002)(74502001)(92726001)(19580405001)(19580395003)(74662001)(83322001)(31966008)(76796001)(4396001)(93516002)(50986001)(47976001)(47736001)(93136001)(94316002)(65816001)(558084003)(56776001)(66066001)(74706001)(54316002)(80976001)(36756003)(49866001)(80022001)(94946001)(86362001)(85306002)(46102001)(95416001)(76482001)(92566001)(1411001)(2656002)(74366001)(87936001)(69226001)(79102001)(54356001)(53806001)(63696002)(51856001)(81542001)(81342001)(90146001)(83072002)(56816005)(33656001)(59766001)(77982001)(85852003)(74876001); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR05MB771; H:BN1PR05MB204.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:A5F1E958.1CA3D411.11E91BFF.C0C12DE8.20085; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail217-co9 (localhost.localdomain [127.0.0.1]) by mail217-co9 (MessageSwitch) id 139395508745380_13206; Tue, 4 Mar 2014 17:44:47 +0000 (UTC) Received: from CO9EHSMHS020.bigfish.com (unknown [10.236.132.243]) by mail217-co9.bigfish.com (Postfix) with ESMTP id 06D441EC004B; Tue, 4 Mar 2014 17:44:47 +0000 (UTC) Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS020.bigfish.com (10.236.130.30) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 4 Mar 2014 17:44:34 +0000 Received: from BLUPR05MB771.namprd05.prod.outlook.com (10.141.209.26) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.423.0; Tue, 4 Mar 2014 17:44:29 +0000 Received: from BN1PR05MB204.namprd05.prod.outlook.com (10.255.206.17) by BLUPR05MB771.namprd05.prod.outlook.com (10.141.209.26) with Microsoft SMTP Server (TLS) id 15.0.893.10; Tue, 4 Mar 2014 17:44:28 +0000 Received: from BN1PR05MB204.namprd05.prod.outlook.com ([169.254.1.67]) by BN1PR05MB204.namprd05.prod.outlook.com ([169.254.1.67]) with mapi id 15.00.0893.001; Tue, 4 Mar 2014 17:44:28 +0000 From: Anirban Chakraborty To: jacek burghardt Thread-Topic: [Xen-API] archlinux and xcp Thread-Index: AQHPN3cwYhxrb5zhkUi2FZVPJciinZrQgb4AgAAEMwCAAK3ngA== Date: Tue, 4 Mar 2014 17:44:27 +0000 Message-ID: <1BD05672-22EA-4C28-B113-7884DC1D7A8C@juniper.net> References: <93C78E4A-5A8B-448F-B3F8-82F4212D8EF6@juniper.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 01401330D1 Content-ID: MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mar 3, 2014, at 11:22 PM, jacek burghardt wr= ote: > Thank you for the info did you get xapi compiled ? No, I still couldn=92t get xapi compiled. I posted the error messages I am = getting another thread. Anirban _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Tue Mar 04 17:45:04 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 04 Mar 2014 17:45:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKtOg-0000BS-4W; Tue, 04 Mar 2014 17:44:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WKtOe-0000BJ-Tn for xen-api@lists.xen.org; Tue, 04 Mar 2014 17:44:53 +0000 Received: from [193.109.254.147:59177] by server-12.bemta-14.messagelabs.com id 3D/BE-17220-41116135; Tue, 04 Mar 2014 17:44:52 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-4.tower-27.messagelabs.com!1393955090!4579452!1 X-Originating-IP: [207.46.163.26] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2103 invoked from network); 4 Mar 2014 17:44:51 -0000 Received: from co9ehsobe003.messaging.microsoft.com (HELO co9outboundpool.messaging.microsoft.com) (207.46.163.26) by server-4.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 4 Mar 2014 17:44:51 -0000 Received: from mail217-co9-R.bigfish.com (10.236.132.238) by CO9EHSOBE004.bigfish.com (10.236.130.67) with Microsoft SMTP Server id 14.1.225.22; Tue, 4 Mar 2014 17:44:49 +0000 Received: from mail217-co9 (localhost [127.0.0.1]) by mail217-co9-R.bigfish.com (Postfix) with ESMTP id 4700FE0032B; Tue, 4 Mar 2014 17:44:49 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -2 X-BigFish: VPS-2(zz98dI9371Ida00hdc73hzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hz8dhz1de098h8275bh1de097hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2184h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch1155h) Received-SPF: pass (mail217-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(199002)(189002)(24454002)(377454003)(82746002)(81816001)(83716003)(85806002)(77096001)(81686001)(87266001)(95666003)(76786001)(47446002)(74502001)(92726001)(19580405001)(19580395003)(74662001)(83322001)(31966008)(76796001)(4396001)(93516002)(50986001)(47976001)(47736001)(93136001)(94316002)(65816001)(558084003)(56776001)(66066001)(74706001)(54316002)(80976001)(36756003)(49866001)(80022001)(94946001)(86362001)(85306002)(46102001)(95416001)(76482001)(92566001)(1411001)(2656002)(74366001)(87936001)(69226001)(79102001)(54356001)(53806001)(63696002)(51856001)(81542001)(81342001)(90146001)(83072002)(56816005)(33656001)(59766001)(77982001)(85852003)(74876001); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR05MB771; H:BN1PR05MB204.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:A5F1E958.1CA3D411.11E91BFF.C0C12DE8.20085; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail217-co9 (localhost.localdomain [127.0.0.1]) by mail217-co9 (MessageSwitch) id 139395508745380_13206; Tue, 4 Mar 2014 17:44:47 +0000 (UTC) Received: from CO9EHSMHS020.bigfish.com (unknown [10.236.132.243]) by mail217-co9.bigfish.com (Postfix) with ESMTP id 06D441EC004B; Tue, 4 Mar 2014 17:44:47 +0000 (UTC) Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS020.bigfish.com (10.236.130.30) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 4 Mar 2014 17:44:34 +0000 Received: from BLUPR05MB771.namprd05.prod.outlook.com (10.141.209.26) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.423.0; Tue, 4 Mar 2014 17:44:29 +0000 Received: from BN1PR05MB204.namprd05.prod.outlook.com (10.255.206.17) by BLUPR05MB771.namprd05.prod.outlook.com (10.141.209.26) with Microsoft SMTP Server (TLS) id 15.0.893.10; Tue, 4 Mar 2014 17:44:28 +0000 Received: from BN1PR05MB204.namprd05.prod.outlook.com ([169.254.1.67]) by BN1PR05MB204.namprd05.prod.outlook.com ([169.254.1.67]) with mapi id 15.00.0893.001; Tue, 4 Mar 2014 17:44:28 +0000 From: Anirban Chakraborty To: jacek burghardt Thread-Topic: [Xen-API] archlinux and xcp Thread-Index: AQHPN3cwYhxrb5zhkUi2FZVPJciinZrQgb4AgAAEMwCAAK3ngA== Date: Tue, 4 Mar 2014 17:44:27 +0000 Message-ID: <1BD05672-22EA-4C28-B113-7884DC1D7A8C@juniper.net> References: <93C78E4A-5A8B-448F-B3F8-82F4212D8EF6@juniper.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 01401330D1 Content-ID: MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] archlinux and xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On Mar 3, 2014, at 11:22 PM, jacek burghardt wr= ote: > Thank you for the info did you get xapi compiled ? No, I still couldn=92t get xapi compiled. I posted the error messages I am = getting another thread. Anirban _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Mar 05 18:12:37 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Mar 2014 18:12:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WLGIk-00005e-K1; Wed, 05 Mar 2014 18:12:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WLGIj-00005V-LA for xen-api@lists.xen.org; Wed, 05 Mar 2014 18:12:17 +0000 Received: from [193.109.254.147:25118] by server-1.bemta-14.messagelabs.com id A4/9F-29588-00967135; Wed, 05 Mar 2014 18:12:16 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-12.tower-27.messagelabs.com!1394043134!4969489!1 X-Originating-IP: [65.55.88.14] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2428 invoked from network); 5 Mar 2014 18:12:15 -0000 Received: from tx2ehsobe004.messaging.microsoft.com (HELO tx2outboundpool.messaging.microsoft.com) (65.55.88.14) by server-12.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 5 Mar 2014 18:12:15 -0000 Received: from mail8-tx2-R.bigfish.com (10.9.14.231) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.22; Wed, 5 Mar 2014 18:12:14 +0000 Received: from mail8-tx2 (localhost [127.0.0.1]) by mail8-tx2-R.bigfish.com (Postfix) with ESMTP id 46C72220279; Wed, 5 Mar 2014 18:12:14 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -3 X-BigFish: VPS-3(zz98dI9371I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch25f6h2605h1155h) Received-SPF: pass (mail8-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(199002)(189002)(377454003)(24454002)(51704005)(15202345003)(76482001)(95666003)(74876001)(33656001)(54356001)(74706001)(59766001)(86362001)(54316002)(76786001)(56776001)(36756003)(77982001)(53806001)(63696002)(66066001)(79102001)(69226001)(77096001)(46102001)(95416001)(90146001)(80022001)(81342001)(51856001)(47446002)(81542001)(76796001)(81816001)(93516002)(2656002)(4396001)(19580395003)(87266001)(83716003)(74366001)(19580405001)(82746002)(15975445006)(83322001)(74662001)(47976001)(50986001)(93136001)(94946001)(81686001)(94316002)(56816005)(80976001)(65816001)(85306002)(97186001)(74502001)(47736001)(49866001)(85852003)(92726001)(87936001)(92566001)(83072002)(31966008)(97336001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB779; H:BL2PR05MB193.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:B829D1B7.1E1247DA.F9D37797.82F4B631.20471; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail8-tx2 (localhost.localdomain [127.0.0.1]) by mail8-tx2 (MessageSwitch) id 1394043132523235_28992; Wed, 5 Mar 2014 18:12:12 +0000 (UTC) Received: from TX2EHSMHS026.bigfish.com (unknown [10.9.14.252]) by mail8-tx2.bigfish.com (Postfix) with ESMTP id 6BED03A0089; Wed, 5 Mar 2014 18:12:12 +0000 (UTC) Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS026.bigfish.com (10.9.99.126) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 5 Mar 2014 18:12:06 +0000 Received: from CO2PR05MB779.namprd05.prod.outlook.com (10.141.226.154) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.423.0; Wed, 5 Mar 2014 18:12:06 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com (10.242.198.143) by CO2PR05MB779.namprd05.prod.outlook.com (10.141.226.154) with Microsoft SMTP Server (TLS) id 15.0.888.9; Wed, 5 Mar 2014 18:12:04 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) by BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) with mapi id 15.00.0888.003; Wed, 5 Mar 2014 18:12:03 +0000 From: Anirban Chakraborty To: Anil Madhavapeddy Thread-Topic: [Xen-API] build issue with xapi Thread-Index: AQHPNqO/DQJ26lju90S7esAZ24U2dJrPX1iAgACXxACAAthvAA== Date: Wed, 5 Mar 2014 18:12:03 +0000 Message-ID: References: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> <8BA944B8-0B6B-46E6-B290-FD4541FB77DD@recoil.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 01415BB535 Content-ID: MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] build issue with xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org 2nd Attempt. I have updated xapi code to the latest change set: commit 3b707dc67642021412b5e6a78f435a645b278545 Merge: 4d931bf 738d81f Author: Jon Ludlam = and still it doesn=92t build. However, it fails with different error messag= es now: =97 omake -j 8 phase1 *** omake: reading OMakefiles *** omake: finished reading OMakefiles (0.12 sec) --- Checking for ocamlfind... (found /contrail/opam/4.00.1/bin/ocamlfind) --- Checking for ocamlc.opt... (found /contrail/opam/4.00.1/bin/ocamlc.opt) --- Checking for ocamlopt.opt... (found /contrail/opam/4.00.1/bin/ocamlopt.= opt) --- Checking whether ocamlc understands the "z" warnings... (yes) - scan ocaml scan-ocaml-fhs.ml + ocamlfind ocamldep -package stdext,uuid,gzip -native -I ../ocaml/idl -I += ocamldoc fhs.ml File "fhs.ml", line 5, characters 1-4: Error: Syntax error *** omake: 220/331 targets are up to date = = *** omake: failed (0.70 sec, 31/31 scans, 8/11 rules, 104/444 digests) *** omake: targets were not rebuilt because of errors: = = depends on: ocaml/fhs.ml make: *** [all] Error 2 =97 Am I missing anything here? Any pointer will be highly appreciated. Thanks. Anirban On Mar 3, 2014, at 2:44 PM, Anirban Chakraborty wrote: > = > On Mar 3, 2014, at 5:41 AM, Anil Madhavapeddy wrote: > = >> As a workaround, you could try: >> = >> $ opam switch 4.00.1 # or 4.01.0 >> $ opam install xapi >> = >> This topfind problem tends to only happen with the system compiler. > = > Thanks a lot. switching to 4.00.1 solved the topfind issue. However, now = I see a different issue (given below): > =97 > - build ocaml/xenops domain.o = = > + ocamlfind ocamlopt -syntax camlp4o -package oclock,xml-light2,sexpr,stu= nnel,http-svr,netdev,rpclib,threads,xenctrl,xenstore-compat,xenctrlext,stde= xt,cdrom,netdev,oUnit,uuid,xcp-inventory,xcp,xcp.xen,rpclib.syntax -g -dtyp= es -thread -warn-error +a-4-6-9-27-28-29 -thread -ccopt -fPIC -I ../xapi -I= ../util -I .. -c domain.ml > File "domain.ml", line 307, characters 6-38: > Error: Unbound module Xenctrl.Domain_info > =97 > My xapi code is at following change set: > = > commit 0320fb13cc176d0864865851672131acaad7be86 > Author: David Scott > Date: Wed Oct 30 13:58:04 2013 +0000 > = > import_raw_vdi: look for vhd-tool in %{_bindir} > = > and xenstore is at: > = > commit 03df4be36f6cb2236f813dad7b13db8b060060e8 > Author: David Scott > Date: Wed Sep 11 11:15:14 2013 +0100 > = > Regenerate OASIS > =97=97 > = > xenstore build and install went fine. ocamlfind list shows following: > = > xenstore (version: 1.2.4) > xenstore-compat (version: 0.9.3) > xenstore.client (version: 1.2.4) > xenstore.server (version: 1.2.4) > xenstore.unix (version: 1.2.4) > xenstore_transport (version: 0.9.2) > xenstore_transport.lwt (version: 0.9.2) > xenstore_transport.unix (version: 0.9.2) > = > Am I missing something in building xapi? My build OS is 2.6.32.43-0.4.1.= xs1.8.0.847.170785xen. > = > Any pointer will be highly appreciated. Thanks much. > = > Anirban > = > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > = > = _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Mar 05 18:12:37 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 05 Mar 2014 18:12:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WLGIk-00005e-K1; Wed, 05 Mar 2014 18:12:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WLGIj-00005V-LA for xen-api@lists.xen.org; Wed, 05 Mar 2014 18:12:17 +0000 Received: from [193.109.254.147:25118] by server-1.bemta-14.messagelabs.com id A4/9F-29588-00967135; Wed, 05 Mar 2014 18:12:16 +0000 X-Env-Sender: abchak@juniper.net X-Msg-Ref: server-12.tower-27.messagelabs.com!1394043134!4969489!1 X-Originating-IP: [65.55.88.14] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2428 invoked from network); 5 Mar 2014 18:12:15 -0000 Received: from tx2ehsobe004.messaging.microsoft.com (HELO tx2outboundpool.messaging.microsoft.com) (65.55.88.14) by server-12.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 5 Mar 2014 18:12:15 -0000 Received: from mail8-tx2-R.bigfish.com (10.9.14.231) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.22; Wed, 5 Mar 2014 18:12:14 +0000 Received: from mail8-tx2 (localhost [127.0.0.1]) by mail8-tx2-R.bigfish.com (Postfix) with ESMTP id 46C72220279; Wed, 5 Mar 2014 18:12:14 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -3 X-BigFish: VPS-3(zz98dI9371I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h2336h2438h2461h2487h24d7h2516h2545h255eh25cch25f6h2605h1155h) Received-SPF: pass (mail8-tx2: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=abchak@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(199002)(189002)(377454003)(24454002)(51704005)(15202345003)(76482001)(95666003)(74876001)(33656001)(54356001)(74706001)(59766001)(86362001)(54316002)(76786001)(56776001)(36756003)(77982001)(53806001)(63696002)(66066001)(79102001)(69226001)(77096001)(46102001)(95416001)(90146001)(80022001)(81342001)(51856001)(47446002)(81542001)(76796001)(81816001)(93516002)(2656002)(4396001)(19580395003)(87266001)(83716003)(74366001)(19580405001)(82746002)(15975445006)(83322001)(74662001)(47976001)(50986001)(93136001)(94946001)(81686001)(94316002)(56816005)(80976001)(65816001)(85306002)(97186001)(74502001)(47736001)(49866001)(85852003)(92726001)(87936001)(92566001)(83072002)(31966008)(97336001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB779; H:BL2PR05MB193.namprd05.prod.outlook.com; CLIP:66.129.239.13; FPR:B829D1B7.1E1247DA.F9D37797.82F4B631.20471; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail8-tx2 (localhost.localdomain [127.0.0.1]) by mail8-tx2 (MessageSwitch) id 1394043132523235_28992; Wed, 5 Mar 2014 18:12:12 +0000 (UTC) Received: from TX2EHSMHS026.bigfish.com (unknown [10.9.14.252]) by mail8-tx2.bigfish.com (Postfix) with ESMTP id 6BED03A0089; Wed, 5 Mar 2014 18:12:12 +0000 (UTC) Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS026.bigfish.com (10.9.99.126) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 5 Mar 2014 18:12:06 +0000 Received: from CO2PR05MB779.namprd05.prod.outlook.com (10.141.226.154) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.423.0; Wed, 5 Mar 2014 18:12:06 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com (10.242.198.143) by CO2PR05MB779.namprd05.prod.outlook.com (10.141.226.154) with Microsoft SMTP Server (TLS) id 15.0.888.9; Wed, 5 Mar 2014 18:12:04 +0000 Received: from BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) by BL2PR05MB193.namprd05.prod.outlook.com ([169.254.9.94]) with mapi id 15.00.0888.003; Wed, 5 Mar 2014 18:12:03 +0000 From: Anirban Chakraborty To: Anil Madhavapeddy Thread-Topic: [Xen-API] build issue with xapi Thread-Index: AQHPNqO/DQJ26lju90S7esAZ24U2dJrPX1iAgACXxACAAthvAA== Date: Wed, 5 Mar 2014 18:12:03 +0000 Message-ID: References: <7DDAF98C-B6B5-4E1A-8FE2-63609CB266A5@juniper.net> <8BA944B8-0B6B-46E6-B290-FD4541FB77DD@recoil.org> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.13] x-forefront-prvs: 01415BB535 Content-ID: MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] build issue with xapi X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org 2nd Attempt. I have updated xapi code to the latest change set: commit 3b707dc67642021412b5e6a78f435a645b278545 Merge: 4d931bf 738d81f Author: Jon Ludlam = and still it doesn=92t build. However, it fails with different error messag= es now: =97 omake -j 8 phase1 *** omake: reading OMakefiles *** omake: finished reading OMakefiles (0.12 sec) --- Checking for ocamlfind... (found /contrail/opam/4.00.1/bin/ocamlfind) --- Checking for ocamlc.opt... (found /contrail/opam/4.00.1/bin/ocamlc.opt) --- Checking for ocamlopt.opt... (found /contrail/opam/4.00.1/bin/ocamlopt.= opt) --- Checking whether ocamlc understands the "z" warnings... (yes) - scan ocaml scan-ocaml-fhs.ml + ocamlfind ocamldep -package stdext,uuid,gzip -native -I ../ocaml/idl -I += ocamldoc fhs.ml File "fhs.ml", line 5, characters 1-4: Error: Syntax error *** omake: 220/331 targets are up to date = = *** omake: failed (0.70 sec, 31/31 scans, 8/11 rules, 104/444 digests) *** omake: targets were not rebuilt because of errors: = = depends on: ocaml/fhs.ml make: *** [all] Error 2 =97 Am I missing anything here? Any pointer will be highly appreciated. Thanks. Anirban On Mar 3, 2014, at 2:44 PM, Anirban Chakraborty wrote: > = > On Mar 3, 2014, at 5:41 AM, Anil Madhavapeddy wrote: > = >> As a workaround, you could try: >> = >> $ opam switch 4.00.1 # or 4.01.0 >> $ opam install xapi >> = >> This topfind problem tends to only happen with the system compiler. > = > Thanks a lot. switching to 4.00.1 solved the topfind issue. However, now = I see a different issue (given below): > =97 > - build ocaml/xenops domain.o = = > + ocamlfind ocamlopt -syntax camlp4o -package oclock,xml-light2,sexpr,stu= nnel,http-svr,netdev,rpclib,threads,xenctrl,xenstore-compat,xenctrlext,stde= xt,cdrom,netdev,oUnit,uuid,xcp-inventory,xcp,xcp.xen,rpclib.syntax -g -dtyp= es -thread -warn-error +a-4-6-9-27-28-29 -thread -ccopt -fPIC -I ../xapi -I= ../util -I .. -c domain.ml > File "domain.ml", line 307, characters 6-38: > Error: Unbound module Xenctrl.Domain_info > =97 > My xapi code is at following change set: > = > commit 0320fb13cc176d0864865851672131acaad7be86 > Author: David Scott > Date: Wed Oct 30 13:58:04 2013 +0000 > = > import_raw_vdi: look for vhd-tool in %{_bindir} > = > and xenstore is at: > = > commit 03df4be36f6cb2236f813dad7b13db8b060060e8 > Author: David Scott > Date: Wed Sep 11 11:15:14 2013 +0100 > = > Regenerate OASIS > =97=97 > = > xenstore build and install went fine. ocamlfind list shows following: > = > xenstore (version: 1.2.4) > xenstore-compat (version: 0.9.3) > xenstore.client (version: 1.2.4) > xenstore.server (version: 1.2.4) > xenstore.unix (version: 1.2.4) > xenstore_transport (version: 0.9.2) > xenstore_transport.lwt (version: 0.9.2) > xenstore_transport.unix (version: 0.9.2) > = > Am I missing something in building xapi? My build OS is 2.6.32.43-0.4.1.= xs1.8.0.847.170785xen. > = > Any pointer will be highly appreciated. Thanks much. > = > Anirban > = > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > = > = _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 17 06:04:03 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2014 06:04:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPQeB-0003mw-W3; Mon, 17 Mar 2014 06:03:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPQeA-0003mr-W8 for xen-api@lists.xen.org; Mon, 17 Mar 2014 06:03:39 +0000 Received: from [85.158.139.211:3849] by server-15.bemta-5.messagelabs.com id B7/D7-11079-A3096235; Mon, 17 Mar 2014 06:03:38 +0000 X-Env-Sender: shakeel.butt@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1395036216!1393675!1 X-Originating-IP: [209.85.214.179] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15393 invoked from network); 17 Mar 2014 06:03:37 -0000 Received: from mail-ob0-f179.google.com (HELO mail-ob0-f179.google.com) (209.85.214.179) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Mar 2014 06:03:37 -0000 Received: by mail-ob0-f179.google.com with SMTP id va2so5053364obc.38 for ; Sun, 16 Mar 2014 23:03:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=eisDQsws6EiqMgB3pQFdIDsjq9BwEDqjnItymMSFGsU=; b=wzlI+MRVrbznAS+peaKWWDkIVJFSdCcoK63cRdCCxMNU1mmLBT1Wla320MEWO+VMLO 2gmPyISV5Xa3qqyoodvCCbfFZiCKXn8c+M2D46KS9ycvrphA8ysWrIyWRSTHa4byq6jL y01hzuYID4DRQcze5aCv73izLQmxJGwDHUbKwU/yM1HNXYEDOPe5vZfs7K62t+/JJ2/Q NuG7hOVoyLMyGcKsd04JGQq/npTY7qZ44RGxxL8TmV6cjHUU3zpg/NqyUfPPCibCyjsd SYlSZYDJLV63RpQWsBp4rJbXkVqvmdUEBF37WJTj8NCqGXHq+6dnd5nCuPWGkXXhZyw+ tJow== MIME-Version: 1.0 X-Received: by 10.182.87.42 with SMTP id u10mr18934419obz.22.1395036215930; Sun, 16 Mar 2014 23:03:35 -0700 (PDT) Received: by 10.76.70.234 with HTTP; Sun, 16 Mar 2014 23:03:35 -0700 (PDT) Date: Sun, 16 Mar 2014 23:03:35 -0700 Message-ID: From: Shakeel Butt To: "xen-api@lists.xen.org" Subject: [Xen-API] host internal management network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, I have few queries regarding Host Internal Management Network (HIMN). I see that ip range used for HIMS is 169.254.*.* and dom0 always get IP 169.254.0.1 for the interface connected to HIMS. Is this IP range and dom0 IP are statically assigned and will remain same for compatibility reason? Or can this IP range and dom0 IP can be changed dynamically? And similarly is there an xenapi to retrieve the dom0 IP for interface connecting HIMN (if it can be dynamic)? thanks, Shakeel _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 17 06:04:03 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2014 06:04:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPQeB-0003mw-W3; Mon, 17 Mar 2014 06:03:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPQeA-0003mr-W8 for xen-api@lists.xen.org; Mon, 17 Mar 2014 06:03:39 +0000 Received: from [85.158.139.211:3849] by server-15.bemta-5.messagelabs.com id B7/D7-11079-A3096235; Mon, 17 Mar 2014 06:03:38 +0000 X-Env-Sender: shakeel.butt@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1395036216!1393675!1 X-Originating-IP: [209.85.214.179] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15393 invoked from network); 17 Mar 2014 06:03:37 -0000 Received: from mail-ob0-f179.google.com (HELO mail-ob0-f179.google.com) (209.85.214.179) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Mar 2014 06:03:37 -0000 Received: by mail-ob0-f179.google.com with SMTP id va2so5053364obc.38 for ; Sun, 16 Mar 2014 23:03:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=eisDQsws6EiqMgB3pQFdIDsjq9BwEDqjnItymMSFGsU=; b=wzlI+MRVrbznAS+peaKWWDkIVJFSdCcoK63cRdCCxMNU1mmLBT1Wla320MEWO+VMLO 2gmPyISV5Xa3qqyoodvCCbfFZiCKXn8c+M2D46KS9ycvrphA8ysWrIyWRSTHa4byq6jL y01hzuYID4DRQcze5aCv73izLQmxJGwDHUbKwU/yM1HNXYEDOPe5vZfs7K62t+/JJ2/Q NuG7hOVoyLMyGcKsd04JGQq/npTY7qZ44RGxxL8TmV6cjHUU3zpg/NqyUfPPCibCyjsd SYlSZYDJLV63RpQWsBp4rJbXkVqvmdUEBF37WJTj8NCqGXHq+6dnd5nCuPWGkXXhZyw+ tJow== MIME-Version: 1.0 X-Received: by 10.182.87.42 with SMTP id u10mr18934419obz.22.1395036215930; Sun, 16 Mar 2014 23:03:35 -0700 (PDT) Received: by 10.76.70.234 with HTTP; Sun, 16 Mar 2014 23:03:35 -0700 (PDT) Date: Sun, 16 Mar 2014 23:03:35 -0700 Message-ID: From: Shakeel Butt To: "xen-api@lists.xen.org" Subject: [Xen-API] host internal management network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, I have few queries regarding Host Internal Management Network (HIMN). I see that ip range used for HIMS is 169.254.*.* and dom0 always get IP 169.254.0.1 for the interface connected to HIMS. Is this IP range and dom0 IP are statically assigned and will remain same for compatibility reason? Or can this IP range and dom0 IP can be changed dynamically? And similarly is there an xenapi to retrieve the dom0 IP for interface connecting HIMN (if it can be dynamic)? thanks, Shakeel _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 17 10:51:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2014 10:51:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPV8B-0004n9-4c; Mon, 17 Mar 2014 10:50:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPV89-0004mr-G4 for xen-api@lists.xen.org; Mon, 17 Mar 2014 10:50:53 +0000 Received: from [85.158.139.211:63086] by server-3.bemta-5.messagelabs.com id 04/5E-28132-B83D6235; Mon, 17 Mar 2014 10:50:51 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1395053450!1448110!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20779 invoked from network); 17 Mar 2014 10:50:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Mar 2014 10:50:50 -0000 X-IronPort-AV: E=Sophos;i="4.97,669,1389744000"; d="scan'208";a="11663255" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 17 Mar 2014 10:50:50 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.213]) by AMSPEX01CL02.citrite.net ([169.254.7.78]) with mapi id 14.02.0342.004; Mon, 17 Mar 2014 11:50:50 +0100 From: Rob Hoes To: 'Shakeel Butt' Thread-Topic: [Xen-API] host internal management network Thread-Index: AQHPQaccvARu5SARuU+2Bgjq+nMLj5rlGX1A Date: Mon, 17 Mar 2014 10:50:49 +0000 Message-ID: <360717C0B01E6345BCBE64B758E22C2D24D5AB@AMSPEX01CL03.citrite.net> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.65] MIME-Version: 1.0 X-DLP: AMS1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] host internal management network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shakeel, > I have few queries regarding Host Internal Management Network (HIMN). > I see that ip range used for HIMS is 169.254.*.* and dom0 always get IP > 169.254.0.1 for the interface connected to HIMS. Is this IP range and dom0 > IP are statically assigned and will remain same for compatibility reason? > Or can this IP range and dom0 IP can be changed dynamically? And similarly > is there an xenapi to retrieve the dom0 IP for interface connecting HIMN > (if it can be dynamic)? The IP range is configurable using other-config keys. I think dom0 always gets the first IP in the range. Take a look here: https://github.com/xapi-project/xen-api/blob/master/apis/udhcp.md. Cheers, Rob > thanks, > Shakeel > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 17 10:51:29 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2014 10:51:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPV8B-0004n9-4c; Mon, 17 Mar 2014 10:50:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPV89-0004mr-G4 for xen-api@lists.xen.org; Mon, 17 Mar 2014 10:50:53 +0000 Received: from [85.158.139.211:63086] by server-3.bemta-5.messagelabs.com id 04/5E-28132-B83D6235; Mon, 17 Mar 2014 10:50:51 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1395053450!1448110!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20779 invoked from network); 17 Mar 2014 10:50:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Mar 2014 10:50:50 -0000 X-IronPort-AV: E=Sophos;i="4.97,669,1389744000"; d="scan'208";a="11663255" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 17 Mar 2014 10:50:50 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.213]) by AMSPEX01CL02.citrite.net ([169.254.7.78]) with mapi id 14.02.0342.004; Mon, 17 Mar 2014 11:50:50 +0100 From: Rob Hoes To: 'Shakeel Butt' Thread-Topic: [Xen-API] host internal management network Thread-Index: AQHPQaccvARu5SARuU+2Bgjq+nMLj5rlGX1A Date: Mon, 17 Mar 2014 10:50:49 +0000 Message-ID: <360717C0B01E6345BCBE64B758E22C2D24D5AB@AMSPEX01CL03.citrite.net> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.65] MIME-Version: 1.0 X-DLP: AMS1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] host internal management network X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Shakeel, > I have few queries regarding Host Internal Management Network (HIMN). > I see that ip range used for HIMS is 169.254.*.* and dom0 always get IP > 169.254.0.1 for the interface connected to HIMS. Is this IP range and dom0 > IP are statically assigned and will remain same for compatibility reason? > Or can this IP range and dom0 IP can be changed dynamically? And similarly > is there an xenapi to retrieve the dom0 IP for interface connecting HIMN > (if it can be dynamic)? The IP range is configurable using other-config keys. I think dom0 always gets the first IP in the range. Take a look here: https://github.com/xapi-project/xen-api/blob/master/apis/udhcp.md. Cheers, Rob > thanks, > Shakeel > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 17 13:16:13 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2014 13:16:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPXOR-00021Q-Rl; Mon, 17 Mar 2014 13:15:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPXOQ-00021L-Mg for xen-api@lists.xenproject.org; Mon, 17 Mar 2014 13:15:51 +0000 Received: from [85.158.137.68:38310] by server-17.bemta-3.messagelabs.com id 8D/2F-22741-585F6235; Mon, 17 Mar 2014 13:15:49 +0000 X-Env-Sender: vasil@webconnect.bg X-Msg-Ref: server-12.tower-31.messagelabs.com!1395062148!1109856!1 X-Originating-IP: [217.18.244.52] X-SpamReason: No, hits=0.5 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MIME_BOUND_NEXTPART X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25882 invoked from network); 17 Mar 2014 13:15:48 -0000 Received: from mx1.bulpost.com (HELO mx1.bulpost.com) (217.18.244.52) by server-12.tower-31.messagelabs.com with SMTP; 17 Mar 2014 13:15:48 -0000 Received: from webconnect.bg (unknown [217.18.244.5]) by mx1.bulpost.com (Postfix) with ESMTPA id B4DD3C4E77D; Mon, 17 Mar 2014 15:24:27 +0200 (EET) MIME-Version: 1.0 X-Mailer: AfterLogic WebMail PHP X-Originating-IP: 213.91.202.97 X-Priority: 3 (Normal) Message-ID: <7a4e649.c5a5eee22f255e69e975137fa3b4d2e2@webmail2.bulpost.com> From: vasil@webconnect.bg To: "Andres Lagar-Cavilla" Date: Mon, 17 Mar 2014 14:57:00 +0200 (EET) Cc: xen-api@lists.xenproject.org Subject: [Xen-API] GSoC 2014 CPUID Programming for Humans X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5575430286381671198==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5575430286381671198== Content-Type: multipart/alternative; boundary="--=_NextPart_927d8770cab51d3f0d98aba1c4b54c81" ----=_NextPart_927d8770cab51d3f0d98aba1c4b54c81 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: Quoted-Printable Hello I'm sending the message again, because I'm not sure in what list m= ust be send,My name is Vasil Vasilev, I would like to apply for this year's GSoC 2014 for the project "CPUID Programming for Humans".I think I will = be able to handle with this project, because I have pretty good experience with the XEN APIs ( from the old days xenapi that was on Python with C bindings with some libxc to newer libxl and libvirt).I'm using libxl sin= ce it's beta versions and had to make some modifications to fit my needs, s= o I think that I'm some kind familiar with the source code,and some of the initial researching work is already done.Contributing source for Xen is like a dream.During the summer I will not be actively involved with the university and I will have enough time to work on the project. A little more about me:Currently I'm studying Architecture in New Bulgarian University, prior I studied in National High-School of Mathematics and Physics in Bulgaria. I'm working part-time in a hosting company in Bulgaria ( webconnect.bg )= , here I'm responsible for managing the Xen Virtual Machines and our web based panel for virtualization.I was also responsible to migrate all the= software that we are using from the old xenapi to newer libxl to work wi= th latest versions of the open source Xen.I have more than 5 years in C programming experience mainly with writing client-server network applications.I have learned many communication protocols and used to wit= h lots of APIs.Also in my everyday work experience I have learned to read = and modify many C code to fit my needs. I have also experience with many other languages like Python,Bash Script,Java that are not related with the project. Any comments, recommendations or questions are welcome Regards,Vasil Vasilev ----=_NextPart_927d8770cab51d3f0d98aba1c4b54c81 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: Quoted-Printable
Hello I'm sending the message again, because I'm not= sure in what list must be send,
My name is Vasil = Vasilev, I would like to apply for this year's GSoC 2014 for the project= "CPUID Programming for Humans".
I think I will be= able to handle with this project, because I have pretty good experience= with the XEN APIs ( from the old days xenapi that was on Python with C = bindings with some libxc to newer libxl and libvirt).
I'm using libxl since it's beta versions and had to make some modifi= cations to fit my needs, so I think that I'm some kind familiar with the= source code,
and some of the initial researching = work is already done.
Contributing source for Xen = is like a dream.
During the summer I will not be a= ctively involved with the university and I will have enough ti= me to work on the project.

A little more about me:
Currently I'm studying= Architecture in New Bulgarian University, prior I studied in National H= igh-School of Mathematics and Physics in Bulgaria.

I'm working part-time in a hosting company i= n Bulgaria ( webconnect.bg ), here I'm responsible for managing the Xen = Virtual Machines and our web based panel for virtualization.
I was also responsible to migrate all the software that we ar= e using from the old xenapi to newer libxl to work with latest versions = of the open source Xen.
I have more than 5 years i= n C programming experience mainly with writing client-server network app= lications.
= I have learned many communication proto= cols and used to with lots of APIs.
Also in my eve= ryday work experience I have learned to read and modify many C code to f= it my needs.

I have als= o experience with many other languages like Python,Bash Script,Java that= are not related with the project.

Any comments, recommendations or questions are welcome

Regards,
Vasil Vasilev


----=_NextPart_927d8770cab51d3f0d98aba1c4b54c81-- --===============5575430286381671198== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5575430286381671198==-- From xen-api-bounces@lists.xen.org Mon Mar 17 13:16:13 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 17 Mar 2014 13:16:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPXOR-00021Q-Rl; Mon, 17 Mar 2014 13:15:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPXOQ-00021L-Mg for xen-api@lists.xenproject.org; Mon, 17 Mar 2014 13:15:51 +0000 Received: from [85.158.137.68:38310] by server-17.bemta-3.messagelabs.com id 8D/2F-22741-585F6235; Mon, 17 Mar 2014 13:15:49 +0000 X-Env-Sender: vasil@webconnect.bg X-Msg-Ref: server-12.tower-31.messagelabs.com!1395062148!1109856!1 X-Originating-IP: [217.18.244.52] X-SpamReason: No, hits=0.5 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MIME_BOUND_NEXTPART X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25882 invoked from network); 17 Mar 2014 13:15:48 -0000 Received: from mx1.bulpost.com (HELO mx1.bulpost.com) (217.18.244.52) by server-12.tower-31.messagelabs.com with SMTP; 17 Mar 2014 13:15:48 -0000 Received: from webconnect.bg (unknown [217.18.244.5]) by mx1.bulpost.com (Postfix) with ESMTPA id B4DD3C4E77D; Mon, 17 Mar 2014 15:24:27 +0200 (EET) MIME-Version: 1.0 X-Mailer: AfterLogic WebMail PHP X-Originating-IP: 213.91.202.97 X-Priority: 3 (Normal) Message-ID: <7a4e649.c5a5eee22f255e69e975137fa3b4d2e2@webmail2.bulpost.com> From: vasil@webconnect.bg To: "Andres Lagar-Cavilla" Date: Mon, 17 Mar 2014 14:57:00 +0200 (EET) Cc: xen-api@lists.xenproject.org Subject: [Xen-API] GSoC 2014 CPUID Programming for Humans X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5575430286381671198==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5575430286381671198== Content-Type: multipart/alternative; boundary="--=_NextPart_927d8770cab51d3f0d98aba1c4b54c81" ----=_NextPart_927d8770cab51d3f0d98aba1c4b54c81 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: Quoted-Printable Hello I'm sending the message again, because I'm not sure in what list m= ust be send,My name is Vasil Vasilev, I would like to apply for this year's GSoC 2014 for the project "CPUID Programming for Humans".I think I will = be able to handle with this project, because I have pretty good experience with the XEN APIs ( from the old days xenapi that was on Python with C bindings with some libxc to newer libxl and libvirt).I'm using libxl sin= ce it's beta versions and had to make some modifications to fit my needs, s= o I think that I'm some kind familiar with the source code,and some of the initial researching work is already done.Contributing source for Xen is like a dream.During the summer I will not be actively involved with the university and I will have enough time to work on the project. A little more about me:Currently I'm studying Architecture in New Bulgarian University, prior I studied in National High-School of Mathematics and Physics in Bulgaria. I'm working part-time in a hosting company in Bulgaria ( webconnect.bg )= , here I'm responsible for managing the Xen Virtual Machines and our web based panel for virtualization.I was also responsible to migrate all the= software that we are using from the old xenapi to newer libxl to work wi= th latest versions of the open source Xen.I have more than 5 years in C programming experience mainly with writing client-server network applications.I have learned many communication protocols and used to wit= h lots of APIs.Also in my everyday work experience I have learned to read = and modify many C code to fit my needs. I have also experience with many other languages like Python,Bash Script,Java that are not related with the project. Any comments, recommendations or questions are welcome Regards,Vasil Vasilev ----=_NextPart_927d8770cab51d3f0d98aba1c4b54c81 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: Quoted-Printable
Hello I'm sending the message again, because I'm not= sure in what list must be send,
My name is Vasil = Vasilev, I would like to apply for this year's GSoC 2014 for the project= "CPUID Programming for Humans".
I think I will be= able to handle with this project, because I have pretty good experience= with the XEN APIs ( from the old days xenapi that was on Python with C = bindings with some libxc to newer libxl and libvirt).
I'm using libxl since it's beta versions and had to make some modifi= cations to fit my needs, so I think that I'm some kind familiar with the= source code,
and some of the initial researching = work is already done.
Contributing source for Xen = is like a dream.
During the summer I will not be a= ctively involved with the university and I will have enough ti= me to work on the project.

A little more about me:
Currently I'm studying= Architecture in New Bulgarian University, prior I studied in National H= igh-School of Mathematics and Physics in Bulgaria.

I'm working part-time in a hosting company i= n Bulgaria ( webconnect.bg ), here I'm responsible for managing the Xen = Virtual Machines and our web based panel for virtualization.
I was also responsible to migrate all the software that we ar= e using from the old xenapi to newer libxl to work with latest versions = of the open source Xen.
I have more than 5 years i= n C programming experience mainly with writing client-server network app= lications.
= I have learned many communication proto= cols and used to with lots of APIs.
Also in my eve= ryday work experience I have learned to read and modify many C code to f= it my needs.

I have als= o experience with many other languages like Python,Bash Script,Java that= are not related with the project.

Any comments, recommendations or questions are welcome

Regards,
Vasil Vasilev


----=_NextPart_927d8770cab51d3f0d98aba1c4b54c81-- --===============5575430286381671198== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============5575430286381671198==-- From xen-api-bounces@lists.xen.org Tue Mar 18 17:46:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Mar 2014 17:46:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPy5n-0007Z5-5Z; Tue, 18 Mar 2014 17:46:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1WPy5Z-0007Xy-Ih for xen-api@lists.xensource.com; Tue, 18 Mar 2014 17:46:18 +0000 Received: from [85.158.139.211:40738] by server-1.bemta-5.messagelabs.com id 84/AD-10259-06688235; Tue, 18 Mar 2014 17:46:08 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1395164768!1840379!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14771 invoked from network); 18 Mar 2014 17:46:08 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Mar 2014 17:46:08 -0000 Received: by mail-wi0-f177.google.com with SMTP id cc10so4065858wib.4 for ; Tue, 18 Mar 2014 10:46:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=puye9d/BhSgcyYNAVVYPh9Q3eA2m/UUHR5oKr6Wbriw=; b=oRjHnbTDmXgtlh4XfRdhYqzKES3YgKiF4DQJbVCpfvS0dNhLcT2nCFZO/3AiEsITK+ CyMhuhieCUwkival5QU2fUQpnTmBLsNBL+6i5xJbgX9vebLYcNz2+98mHjta2lFgeET1 6Y7pWReBMMoVENvSelIzt2cjPDavOgFZDI1v3VitkEhm3Fr8Pf/S7arODHN0QQFeb/Rt NVZ1O62aMp7/FCdemcEbvIAyKCnJ08GcGVHf9gHiRnZV2Z/+y4Qqdh4nidlbu5XOcclH 4tXPXJSK/fDyA+vk4FnkkrjUSWIRoc9duLSxnB15BOwabod4imxWc4eOJNydf08b5wWY TdNw== MIME-Version: 1.0 X-Received: by 10.180.219.44 with SMTP id pl12mr15598023wic.12.1395164767776; Tue, 18 Mar 2014 10:46:07 -0700 (PDT) Received: by 10.217.7.144 with HTTP; Tue, 18 Mar 2014 10:46:07 -0700 (PDT) Date: Tue, 18 Mar 2014 23:16:07 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: "xen-api@lists.xensource.com" , "xs-devel@lists.xenserver.org" Subject: [Xen-API] XenMotion does not work without tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6789393360437878131==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6789393360437878131== Content-Type: multipart/alternative; boundary=001a1134d90862f2fd04f4e51c9b --001a1134d90862f2fd04f4e51c9b Content-Type: text/plain; charset=ISO-8859-1 Dear List, With latest XenServer6.2, I have pfsense VMs which are based on FreeBSD. There are no xs-tools for it which is okay but these VMs can not be live migrated to another node. With Xen its possible to migrate any domain to remote xen host but seems its not possible in XenServer. Am I missing anything or vmware would be better ? Anyone using pfsense with Xenserver ? --001a1134d90862f2fd04f4e51c9b Content-Type: text/html; charset=ISO-8859-1
Dear List,

With latest XenServer6.2, I have pfsense VMs which are based on FreeBSD. There are no xs-tools for it which is okay but these VMs can not be live migrated to another node.

With Xen its possible to migrate any domain to remote xen host but seems its not possible in XenServer.

Am I missing anything or vmware would be better ?
Anyone using pfsense with Xenserver ?


--001a1134d90862f2fd04f4e51c9b-- --===============6789393360437878131== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6789393360437878131==-- From xen-api-bounces@lists.xen.org Tue Mar 18 17:46:40 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 18 Mar 2014 17:46:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WPy5n-0007Z5-5Z; Tue, 18 Mar 2014 17:46:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1WPy5Z-0007Xy-Ih for xen-api@lists.xensource.com; Tue, 18 Mar 2014 17:46:18 +0000 Received: from [85.158.139.211:40738] by server-1.bemta-5.messagelabs.com id 84/AD-10259-06688235; Tue, 18 Mar 2014 17:46:08 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1395164768!1840379!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14771 invoked from network); 18 Mar 2014 17:46:08 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Mar 2014 17:46:08 -0000 Received: by mail-wi0-f177.google.com with SMTP id cc10so4065858wib.4 for ; Tue, 18 Mar 2014 10:46:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=puye9d/BhSgcyYNAVVYPh9Q3eA2m/UUHR5oKr6Wbriw=; b=oRjHnbTDmXgtlh4XfRdhYqzKES3YgKiF4DQJbVCpfvS0dNhLcT2nCFZO/3AiEsITK+ CyMhuhieCUwkival5QU2fUQpnTmBLsNBL+6i5xJbgX9vebLYcNz2+98mHjta2lFgeET1 6Y7pWReBMMoVENvSelIzt2cjPDavOgFZDI1v3VitkEhm3Fr8Pf/S7arODHN0QQFeb/Rt NVZ1O62aMp7/FCdemcEbvIAyKCnJ08GcGVHf9gHiRnZV2Z/+y4Qqdh4nidlbu5XOcclH 4tXPXJSK/fDyA+vk4FnkkrjUSWIRoc9duLSxnB15BOwabod4imxWc4eOJNydf08b5wWY TdNw== MIME-Version: 1.0 X-Received: by 10.180.219.44 with SMTP id pl12mr15598023wic.12.1395164767776; Tue, 18 Mar 2014 10:46:07 -0700 (PDT) Received: by 10.217.7.144 with HTTP; Tue, 18 Mar 2014 10:46:07 -0700 (PDT) Date: Tue, 18 Mar 2014 23:16:07 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: "xen-api@lists.xensource.com" , "xs-devel@lists.xenserver.org" Subject: [Xen-API] XenMotion does not work without tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6789393360437878131==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============6789393360437878131== Content-Type: multipart/alternative; boundary=001a1134d90862f2fd04f4e51c9b --001a1134d90862f2fd04f4e51c9b Content-Type: text/plain; charset=ISO-8859-1 Dear List, With latest XenServer6.2, I have pfsense VMs which are based on FreeBSD. There are no xs-tools for it which is okay but these VMs can not be live migrated to another node. With Xen its possible to migrate any domain to remote xen host but seems its not possible in XenServer. Am I missing anything or vmware would be better ? Anyone using pfsense with Xenserver ? --001a1134d90862f2fd04f4e51c9b Content-Type: text/html; charset=ISO-8859-1
Dear List,

With latest XenServer6.2, I have pfsense VMs which are based on FreeBSD. There are no xs-tools for it which is okay but these VMs can not be live migrated to another node.

With Xen its possible to migrate any domain to remote xen host but seems its not possible in XenServer.

Am I missing anything or vmware would be better ?
Anyone using pfsense with Xenserver ?


--001a1134d90862f2fd04f4e51c9b-- --===============6789393360437878131== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============6789393360437878131==-- From xen-api-bounces@lists.xen.org Thu Mar 20 13:16:28 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Mar 2014 13:16:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WQcoy-0002Ul-0t; Thu, 20 Mar 2014 13:15:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WQcox-0002Uf-5o for xen-api@lists.xen.org; Thu, 20 Mar 2014 13:15:43 +0000 Received: from [85.158.137.68:27393] by server-10.bemta-3.messagelabs.com id 87/B5-16608-EF9EA235; Thu, 20 Mar 2014 13:15:42 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1395321341!632891!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7325 invoked from network); 20 Mar 2014 13:15:41 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 20 Mar 2014 13:15:41 -0000 Received: by mail-wg0-f47.google.com with SMTP id x12so577303wgg.18 for ; Thu, 20 Mar 2014 06:15:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=rdg6yWO9dTg6kJE3W5VxEHsc41Mjxn43BOjzUHSVfSA=; b=bwX3EdK4ej8ngEC0NdygzvCFMiffmnFZX275WuV8mnuAKechHoP1mGCYannISiwMdu LNVxPWSFtvOoH882N/cslrStUglXD+DzC+Ejv8a6Cn0RfphfxzOb6MkT1YiuJE2V3gPL hRlezadSU/fxm23bEaKzrDjJyn4SB8enRL/O3TJK3mbj6ma8v/Hl8pa04K8w+/asiIso C/nOAQh+uPg8WthBX1xPrBvV00HWSxmKuy8ssLskSvaVIb8aztg1UNpDLX5abfNtu3E9 IRWwx3rIzrcmH28iYGwByQCl4MLO/XOjK91AUntVSMsWlpjoKhhWNJWtLYq2BrIP4Wwq r4xA== X-Received: by 10.180.7.227 with SMTP id m3mr23789696wia.59.1395321340989; Thu, 20 Mar 2014 06:15:40 -0700 (PDT) Received: from [192.168.0.68] (static-nbl2-118.cytanet.com.cy. [212.31.107.118]) by mx.google.com with ESMTPSA id ga10sm4955165wjb.23.2014.03.20.06.15.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Mar 2014 06:15:40 -0700 (PDT) Message-ID: <532AE9FB.9000204@gmail.com> Date: Thu, 20 Mar 2014 15:15:39 +0200 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] XenMotion does not work without tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8212485632208636129==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8212485632208636129== Content-Type: multipart/alternative; boundary="------------030803050301060507070203" This is a multi-part message in MIME format. --------------030803050301060507070203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit There is a fake-guest-tools script to emulate those tools from outside VM. On 03/18/2014 07:46 PM, Rishi wrote: > Dear List, > > With latest XenServer6.2, I have pfsense VMs which are based on > FreeBSD. There are no xs-tools for it which is okay but these VMs can > not be live migrated to another node. > > With Xen its possible to migrate any domain to remote xen host but > seems its not possible in XenServer. > > Am I missing anything or vmware would be better ? > Anyone using pfsense with Xenserver ? > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------030803050301060507070203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
There is a fake-guest-tools script to emulate those tools from outside VM.

On 03/18/2014 07:46 PM, Rishi wrote:
Dear List,

With latest XenServer6.2, I have pfsense VMs which are based on FreeBSD. There are no xs-tools for it which is okay but these VMs can not be live migrated to another node.

With Xen its possible to migrate any domain to remote xen host but seems its not possible in XenServer.

Am I missing anything or vmware would be better ?
Anyone using pfsense with Xenserver ?




_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------030803050301060507070203-- --===============8212485632208636129== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8212485632208636129==-- From xen-api-bounces@lists.xen.org Thu Mar 20 13:16:28 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Mar 2014 13:16:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WQcoy-0002Ul-0t; Thu, 20 Mar 2014 13:15:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WQcox-0002Uf-5o for xen-api@lists.xen.org; Thu, 20 Mar 2014 13:15:43 +0000 Received: from [85.158.137.68:27393] by server-10.bemta-3.messagelabs.com id 87/B5-16608-EF9EA235; Thu, 20 Mar 2014 13:15:42 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1395321341!632891!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7325 invoked from network); 20 Mar 2014 13:15:41 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 20 Mar 2014 13:15:41 -0000 Received: by mail-wg0-f47.google.com with SMTP id x12so577303wgg.18 for ; Thu, 20 Mar 2014 06:15:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=rdg6yWO9dTg6kJE3W5VxEHsc41Mjxn43BOjzUHSVfSA=; b=bwX3EdK4ej8ngEC0NdygzvCFMiffmnFZX275WuV8mnuAKechHoP1mGCYannISiwMdu LNVxPWSFtvOoH882N/cslrStUglXD+DzC+Ejv8a6Cn0RfphfxzOb6MkT1YiuJE2V3gPL hRlezadSU/fxm23bEaKzrDjJyn4SB8enRL/O3TJK3mbj6ma8v/Hl8pa04K8w+/asiIso C/nOAQh+uPg8WthBX1xPrBvV00HWSxmKuy8ssLskSvaVIb8aztg1UNpDLX5abfNtu3E9 IRWwx3rIzrcmH28iYGwByQCl4MLO/XOjK91AUntVSMsWlpjoKhhWNJWtLYq2BrIP4Wwq r4xA== X-Received: by 10.180.7.227 with SMTP id m3mr23789696wia.59.1395321340989; Thu, 20 Mar 2014 06:15:40 -0700 (PDT) Received: from [192.168.0.68] (static-nbl2-118.cytanet.com.cy. [212.31.107.118]) by mx.google.com with ESMTPSA id ga10sm4955165wjb.23.2014.03.20.06.15.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Mar 2014 06:15:40 -0700 (PDT) Message-ID: <532AE9FB.9000204@gmail.com> Date: Thu, 20 Mar 2014 15:15:39 +0200 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] XenMotion does not work without tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8212485632208636129==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8212485632208636129== Content-Type: multipart/alternative; boundary="------------030803050301060507070203" This is a multi-part message in MIME format. --------------030803050301060507070203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit There is a fake-guest-tools script to emulate those tools from outside VM. On 03/18/2014 07:46 PM, Rishi wrote: > Dear List, > > With latest XenServer6.2, I have pfsense VMs which are based on > FreeBSD. There are no xs-tools for it which is okay but these VMs can > not be live migrated to another node. > > With Xen its possible to migrate any domain to remote xen host but > seems its not possible in XenServer. > > Am I missing anything or vmware would be better ? > Anyone using pfsense with Xenserver ? > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------030803050301060507070203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
There is a fake-guest-tools script to emulate those tools from outside VM.

On 03/18/2014 07:46 PM, Rishi wrote:
Dear List,

With latest XenServer6.2, I have pfsense VMs which are based on FreeBSD. There are no xs-tools for it which is okay but these VMs can not be live migrated to another node.

With Xen its possible to migrate any domain to remote xen host but seems its not possible in XenServer.

Am I missing anything or vmware would be better ?
Anyone using pfsense with Xenserver ?




_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--------------030803050301060507070203-- --===============8212485632208636129== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============8212485632208636129==-- From xen-api-bounces@lists.xen.org Thu Mar 20 14:04:57 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Mar 2014 14:04:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WQdaJ-0006a1-Qw; Thu, 20 Mar 2014 14:04:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1WQdaI-0006Zi-DS for xen-api@lists.xen.org; Thu, 20 Mar 2014 14:04:38 +0000 Received: from [85.158.143.35:40155] by server-1.bemta-4.messagelabs.com id 9E/3D-09853-575FA235; Thu, 20 Mar 2014 14:04:37 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1395324276!3524334!1 X-Originating-IP: [74.125.82.171] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32030 invoked from network); 20 Mar 2014 14:04:36 -0000 Received: from mail-we0-f171.google.com (HELO mail-we0-f171.google.com) (74.125.82.171) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Mar 2014 14:04:36 -0000 Received: by mail-we0-f171.google.com with SMTP id t61so640444wes.30 for ; Thu, 20 Mar 2014 07:04:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A/J+fhYmAxtWTIJ3oLCIPH2Yl6OQOmwFr0C612XTjlQ=; b=PXw1GzZHSNfCpxAFpPpp7olURt2mEhb6ouPOm8ANHG47ook3YtVYbDjZDsXuzemup9 XgOwLGU5eUL6PkenLyGa8PaqKTsMxyAjFIffpUWs73PEBRfn/JOIM8gnDJE/JWyr1JkP oGtDs+Hrlx0hkKMldrGYQ0gREkgHjTi2Jhvk6rBquessbzLuOqCBDuFB/bKK0WCtzNOZ TRylJLtPsb+aBOeDCEUPwN3WkKUy5Rr8mRWoOwnrsXbB/rDvIAVVd4VKGar4j4CErijN 8ZMERDEy137vJ48GNld8xCYNiZxc5xQ91v5+T97toaZYSDnyZd59gMZ7i5BSL8NwE4aZ j0cQ== MIME-Version: 1.0 X-Received: by 10.180.219.44 with SMTP id pl12mr24725125wic.12.1395324276125; Thu, 20 Mar 2014 07:04:36 -0700 (PDT) Received: by 10.217.7.144 with HTTP; Thu, 20 Mar 2014 07:04:36 -0700 (PDT) In-Reply-To: <532AE9FB.9000204@gmail.com> References: <532AE9FB.9000204@gmail.com> Date: Thu, 20 Mar 2014 19:34:36 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: George Shuklin Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XenMotion does not work without tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4404528915431788329==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4404528915431788329== Content-Type: multipart/alternative; boundary=001a1134d908d3364804f50a3f6d --001a1134d908d3364804f50a3f6d Content-Type: text/plain; charset=ISO-8859-1 Hi All, Thanks George, Got it working by doing below dom=46 xenstore-write /local/domain/$dom/attr/PVAddons/MajorVersion "6" xenstore-write /local/domain/$dom/attr/PVAddons/MinorVersion "2" xenstore-write /local/domain/$dom/attr/PVAddons/MicroVersion "0" xenstore-write /local/domain/$dom/attr/PVAddons/Installed "1" xenstore-write /local/domain/$dom/attr/PVAddons/BuildVersion "70446" xenstore-write /local/domain/$dom/data/updated 1 These settings wont persists between reboots, anyone has idea to make them persistent ? On Thu, Mar 20, 2014 at 6:45 PM, George Shuklin wrote: > There is a fake-guest-tools script to emulate those tools from outside > VM. > > > On 03/18/2014 07:46 PM, Rishi wrote: > > Dear List, > > With latest XenServer6.2, I have pfsense VMs which are based on FreeBSD. > There are no xs-tools for it which is okay but these VMs can not be live > migrated to another node. > > With Xen its possible to migrate any domain to remote xen host but seems > its not possible in XenServer. > > Am I missing anything or vmware would be better ? > Anyone using pfsense with Xenserver ? > > > > > _______________________________________________ > Xen-api mailing listXen-api@lists.xen.orghttp://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --001a1134d908d3364804f50a3f6d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All,

Thanks George, Got it working b= y doing below

dom=3D46
xenstore-wri= te /local/domain/$dom/attr/PVAddons/MajorVersion "6"
xe= nstore-write /local/domain/$dom/attr/PVAddons/MinorVersion "2"
xenstore-write /local/domain/$dom/attr/PVAddons/MicroVersion "0&q= uot;
xenstore-write /local/domain/$dom/attr/PVAddons/Installed &q= uot;1"
xenstore-write /local/domain/$dom/attr/PVAddons/Build= Version "70446"
xenstore-write /local/domain/$dom/data/updated 1

<= /div>

These settings wont persists between reboots, anyo= ne has idea to make them persistent ?




On Thu,= Mar 20, 2014 at 6:45 PM, George Shuklin <george.shuklin@gmail.com<= /a>> wrote:
=20 =20 =20
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--001a1134d908d3364804f50a3f6d-- --===============4404528915431788329== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4404528915431788329==-- From xen-api-bounces@lists.xen.org Thu Mar 20 14:04:57 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 20 Mar 2014 14:04:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WQdaJ-0006a1-Qw; Thu, 20 Mar 2014 14:04:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from <2rushikeshj@gmail.com>) id 1WQdaI-0006Zi-DS for xen-api@lists.xen.org; Thu, 20 Mar 2014 14:04:38 +0000 Received: from [85.158.143.35:40155] by server-1.bemta-4.messagelabs.com id 9E/3D-09853-575FA235; Thu, 20 Mar 2014 14:04:37 +0000 X-Env-Sender: 2rushikeshj@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1395324276!3524334!1 X-Originating-IP: [74.125.82.171] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32030 invoked from network); 20 Mar 2014 14:04:36 -0000 Received: from mail-we0-f171.google.com (HELO mail-we0-f171.google.com) (74.125.82.171) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Mar 2014 14:04:36 -0000 Received: by mail-we0-f171.google.com with SMTP id t61so640444wes.30 for ; Thu, 20 Mar 2014 07:04:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A/J+fhYmAxtWTIJ3oLCIPH2Yl6OQOmwFr0C612XTjlQ=; b=PXw1GzZHSNfCpxAFpPpp7olURt2mEhb6ouPOm8ANHG47ook3YtVYbDjZDsXuzemup9 XgOwLGU5eUL6PkenLyGa8PaqKTsMxyAjFIffpUWs73PEBRfn/JOIM8gnDJE/JWyr1JkP oGtDs+Hrlx0hkKMldrGYQ0gREkgHjTi2Jhvk6rBquessbzLuOqCBDuFB/bKK0WCtzNOZ TRylJLtPsb+aBOeDCEUPwN3WkKUy5Rr8mRWoOwnrsXbB/rDvIAVVd4VKGar4j4CErijN 8ZMERDEy137vJ48GNld8xCYNiZxc5xQ91v5+T97toaZYSDnyZd59gMZ7i5BSL8NwE4aZ j0cQ== MIME-Version: 1.0 X-Received: by 10.180.219.44 with SMTP id pl12mr24725125wic.12.1395324276125; Thu, 20 Mar 2014 07:04:36 -0700 (PDT) Received: by 10.217.7.144 with HTTP; Thu, 20 Mar 2014 07:04:36 -0700 (PDT) In-Reply-To: <532AE9FB.9000204@gmail.com> References: <532AE9FB.9000204@gmail.com> Date: Thu, 20 Mar 2014 19:34:36 +0530 Message-ID: From: Rishi <2rushikeshj@gmail.com> To: George Shuklin Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XenMotion does not work without tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4404528915431788329==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4404528915431788329== Content-Type: multipart/alternative; boundary=001a1134d908d3364804f50a3f6d --001a1134d908d3364804f50a3f6d Content-Type: text/plain; charset=ISO-8859-1 Hi All, Thanks George, Got it working by doing below dom=46 xenstore-write /local/domain/$dom/attr/PVAddons/MajorVersion "6" xenstore-write /local/domain/$dom/attr/PVAddons/MinorVersion "2" xenstore-write /local/domain/$dom/attr/PVAddons/MicroVersion "0" xenstore-write /local/domain/$dom/attr/PVAddons/Installed "1" xenstore-write /local/domain/$dom/attr/PVAddons/BuildVersion "70446" xenstore-write /local/domain/$dom/data/updated 1 These settings wont persists between reboots, anyone has idea to make them persistent ? On Thu, Mar 20, 2014 at 6:45 PM, George Shuklin wrote: > There is a fake-guest-tools script to emulate those tools from outside > VM. > > > On 03/18/2014 07:46 PM, Rishi wrote: > > Dear List, > > With latest XenServer6.2, I have pfsense VMs which are based on FreeBSD. > There are no xs-tools for it which is okay but these VMs can not be live > migrated to another node. > > With Xen its possible to migrate any domain to remote xen host but seems > its not possible in XenServer. > > Am I missing anything or vmware would be better ? > Anyone using pfsense with Xenserver ? > > > > > _______________________________________________ > Xen-api mailing listXen-api@lists.xen.orghttp://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > --001a1134d908d3364804f50a3f6d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi All,

Thanks George, Got it working b= y doing below

dom=3D46
xenstore-wri= te /local/domain/$dom/attr/PVAddons/MajorVersion "6"
xe= nstore-write /local/domain/$dom/attr/PVAddons/MinorVersion "2"
xenstore-write /local/domain/$dom/attr/PVAddons/MicroVersion "0&q= uot;
xenstore-write /local/domain/$dom/attr/PVAddons/Installed &q= uot;1"
xenstore-write /local/domain/$dom/attr/PVAddons/Build= Version "70446"
xenstore-write /local/domain/$dom/data/updated 1

<= /div>

These settings wont persists between reboots, anyo= ne has idea to make them persistent ?




On Thu,= Mar 20, 2014 at 6:45 PM, George Shuklin <george.shuklin@gmail.com<= /a>> wrote:
=20 =20 =20
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--001a1134d908d3364804f50a3f6d-- --===============4404528915431788329== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4404528915431788329==-- From xen-api-bounces@lists.xen.org Fri Mar 21 16:43:59 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Mar 2014 16:43:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WR2Xj-0001Ki-NA; Fri, 21 Mar 2014 16:43:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WR2Xh-0001Ka-Pa for xen-api@lists.xen.org; Fri, 21 Mar 2014 16:43:38 +0000 Received: from [85.158.137.68:32102] by server-14.bemta-3.messagelabs.com id F8/F0-30903-93C6C235; Fri, 21 Mar 2014 16:43:37 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1395420215!2197555!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21754 invoked from network); 21 Mar 2014 16:43:36 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2014 16:43:36 -0000 Received: by mail-qa0-f45.google.com with SMTP id hw13so2679386qab.18 for ; Fri, 21 Mar 2014 09:43:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Ams9KEfwMMx2WFRAIsmVXtyBq9299H7/45MKO6uk+14=; b=UGeFdBKtIdzOzqR/10SRFJ5nLh6GOrgTl7whmGVzXFYkag9HaQqzMOj1lEUigmQJOH BzJK5hShj4N7HIPvFM5t4FIuzlto3ZfRXX4bJobMeA3gvWLvipk1Hk33Y7RDOan76MpQ A8uu1j5ez6gEhc29oOyCLmJWG8s+IB68swD1BqPatJZvAyL77E5k7vTOiymrmziHSoIv MS+tQ+DFKCibnzgGAaPrgmuGplqnIJgXWxSkqKBbpHceFWW0CmknVuV/gbDu8eBGn0PA DGf3HsEq42o/BBowdN9iFuQ0G+mIkwpklIgcT8/s0L+5OXVSxtSNMLXsbMx2dozyeoks VYIA== X-Received: by 10.224.165.83 with SMTP id h19mr58831383qay.27.1395420214921; Fri, 21 Mar 2014 09:43:34 -0700 (PDT) Received: from [192.168.0.68] (static-nbl2-118.cytanet.com.cy. [212.31.107.118]) by mx.google.com with ESMTPSA id r31sm8593874qgr.12.2014.03.21.09.43.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Mar 2014 09:43:33 -0700 (PDT) Message-ID: <532C6C32.4070708@gmail.com> Date: Fri, 21 Mar 2014 18:43:30 +0200 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <532AE9FB.9000204@gmail.com> In-Reply-To: Subject: Re: [Xen-API] XenMotion does not work without tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 03/20/2014 04:04 PM, Rishi wrote: > Hi All, > > Thanks George, Got it working by doing below > > dom=46 > xenstore-write /local/domain/$dom/attr/PVAddons/MajorVersion "6" > xenstore-write /local/domain/$dom/attr/PVAddons/MinorVersion "2" > xenstore-write /local/domain/$dom/attr/PVAddons/MicroVersion "0" > xenstore-write /local/domain/$dom/attr/PVAddons/Installed "1" > xenstore-write /local/domain/$dom/attr/PVAddons/BuildVersion "70446" > xenstore-write /local/domain/$dom/data/updated 1 > > > These settings wont persists between reboots, anyone has idea to make > them persistent ? > those settings is not persistent between reboots and even domain migration. Due implementation there no way to make them persistent. But I don't know why citrix is still keeping check in xenapi service. In our system those settings are applied by special service before domain migration and after domain boot. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Mar 21 16:43:59 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 21 Mar 2014 16:43:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WR2Xj-0001Ki-NA; Fri, 21 Mar 2014 16:43:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WR2Xh-0001Ka-Pa for xen-api@lists.xen.org; Fri, 21 Mar 2014 16:43:38 +0000 Received: from [85.158.137.68:32102] by server-14.bemta-3.messagelabs.com id F8/F0-30903-93C6C235; Fri, 21 Mar 2014 16:43:37 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1395420215!2197555!1 X-Originating-IP: [209.85.216.45] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21754 invoked from network); 21 Mar 2014 16:43:36 -0000 Received: from mail-qa0-f45.google.com (HELO mail-qa0-f45.google.com) (209.85.216.45) by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2014 16:43:36 -0000 Received: by mail-qa0-f45.google.com with SMTP id hw13so2679386qab.18 for ; Fri, 21 Mar 2014 09:43:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Ams9KEfwMMx2WFRAIsmVXtyBq9299H7/45MKO6uk+14=; b=UGeFdBKtIdzOzqR/10SRFJ5nLh6GOrgTl7whmGVzXFYkag9HaQqzMOj1lEUigmQJOH BzJK5hShj4N7HIPvFM5t4FIuzlto3ZfRXX4bJobMeA3gvWLvipk1Hk33Y7RDOan76MpQ A8uu1j5ez6gEhc29oOyCLmJWG8s+IB68swD1BqPatJZvAyL77E5k7vTOiymrmziHSoIv MS+tQ+DFKCibnzgGAaPrgmuGplqnIJgXWxSkqKBbpHceFWW0CmknVuV/gbDu8eBGn0PA DGf3HsEq42o/BBowdN9iFuQ0G+mIkwpklIgcT8/s0L+5OXVSxtSNMLXsbMx2dozyeoks VYIA== X-Received: by 10.224.165.83 with SMTP id h19mr58831383qay.27.1395420214921; Fri, 21 Mar 2014 09:43:34 -0700 (PDT) Received: from [192.168.0.68] (static-nbl2-118.cytanet.com.cy. [212.31.107.118]) by mx.google.com with ESMTPSA id r31sm8593874qgr.12.2014.03.21.09.43.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Mar 2014 09:43:33 -0700 (PDT) Message-ID: <532C6C32.4070708@gmail.com> Date: Fri, 21 Mar 2014 18:43:30 +0200 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <532AE9FB.9000204@gmail.com> In-Reply-To: Subject: Re: [Xen-API] XenMotion does not work without tools X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 03/20/2014 04:04 PM, Rishi wrote: > Hi All, > > Thanks George, Got it working by doing below > > dom=46 > xenstore-write /local/domain/$dom/attr/PVAddons/MajorVersion "6" > xenstore-write /local/domain/$dom/attr/PVAddons/MinorVersion "2" > xenstore-write /local/domain/$dom/attr/PVAddons/MicroVersion "0" > xenstore-write /local/domain/$dom/attr/PVAddons/Installed "1" > xenstore-write /local/domain/$dom/attr/PVAddons/BuildVersion "70446" > xenstore-write /local/domain/$dom/data/updated 1 > > > These settings wont persists between reboots, anyone has idea to make > them persistent ? > those settings is not persistent between reboots and even domain migration. Due implementation there no way to make them persistent. But I don't know why citrix is still keeping check in xenapi service. In our system those settings are applied by special service before domain migration and after domain boot. _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Mar 22 03:45:59 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Mar 2014 03:45:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WRCsJ-00071T-46; Sat, 22 Mar 2014 03:45:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WRCsH-00071O-Ux for xen-api@lists.xen.org; Sat, 22 Mar 2014 03:45:34 +0000 Received: from [193.109.254.147:17046] by server-15.bemta-14.messagelabs.com id A4/D8-15813-D570D235; Sat, 22 Mar 2014 03:45:33 +0000 X-Env-Sender: rranjeet@juniper.net X-Msg-Ref: server-7.tower-27.messagelabs.com!1395459931!3405575!1 X-Originating-IP: [216.32.180.14] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28290 invoked from network); 22 Mar 2014 03:45:32 -0000 Received: from va3ehsobe004.messaging.microsoft.com (HELO va3outboundpool.messaging.microsoft.com) (216.32.180.14) by server-7.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 22 Mar 2014 03:45:32 -0000 Received: from mail192-va3-R.bigfish.com (10.7.14.248) by VA3EHSOBE012.bigfish.com (10.7.40.62) with Microsoft SMTP Server id 14.1.225.22; Sat, 22 Mar 2014 03:45:31 +0000 Received: from mail192-va3 (localhost [127.0.0.1]) by mail192-va3-R.bigfish.com (Postfix) with ESMTP id 1E2043200BC for ; Sat, 22 Mar 2014 03:45:31 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: 1 X-BigFish: VPS1(zze0eah14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de097hz2fh109h2a8h839h947hd24hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24d7h2516h2545h255eh25cch25f6h2605h268bh9a9j1155h) Received-SPF: pass (mail192-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rranjeet@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(189002)(199002)(53754006)(80976001)(74662001)(95416001)(83322001)(19580395003)(47446002)(74876001)(79102001)(86362001)(81686001)(81342001)(94316002)(575784001)(74502001)(81816001)(94946001)(59766001)(56776001)(77982001)(74706001)(54316002)(81542001)(46102001)(76482001)(74316001)(51856001)(93136001)(4396001)(80022001)(97336001)(76176001)(33646001)(31966008)(87936001)(56816005)(87266001)(74366001)(97186001)(76576001)(76796001)(47736001)(49866001)(50986001)(76786001)(47976001)(20776003)(63696002)(85852003)(90146001)(2656002)(92566001)(54356001)(69226001)(93516002)(53806001)(65816001)(66066001)(83072002)(85306002)(98676001)(95666003)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB710; H:BY2PR05MB711.namprd05.prod.outlook.com; FPR:A406C92D.2E074439.43F33964.84A9F373.20284; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail192-va3 (localhost.localdomain [127.0.0.1]) by mail192-va3 (MessageSwitch) id 1395459924328120_5569; Sat, 22 Mar 2014 03:45:24 +0000 (UTC) Received: from VA3EHSMHS023.bigfish.com (unknown [10.7.14.252]) by mail192-va3.bigfish.com (Postfix) with ESMTP id 3612F180047 for ; Sat, 22 Mar 2014 03:45:24 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS023.bigfish.com (10.7.99.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sat, 22 Mar 2014 03:45:23 +0000 Received: from BY2PR05MB710.namprd05.prod.outlook.com (10.141.222.147) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Sat, 22 Mar 2014 03:45:23 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BY2PR05MB710.namprd05.prod.outlook.com (10.141.222.147) with Microsoft SMTP Server (TLS) id 15.0.898.11; Sat, 22 Mar 2014 03:45:21 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) by BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) with mapi id 15.00.0898.005; Sat, 22 Mar 2014 03:45:21 +0000 From: Ranjeet R To: "xen-api@lists.xen.org" Thread-Topic: Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fw== Date: Sat, 22 Mar 2014 03:45:20 +0000 Message-ID: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.10] x-forefront-prvs: 01583E185C MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Subject: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello all I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI da= emon. I had changed the underlying network implementation (it is not a brid= ge, but an openvswitch-like network implementation) and the XAPI daemon cra= shes during bootup. Please find the XAPI logs below. = starting up database engine D:72969b3eaf8e|redo_log] Flushing database to a= ll active redo-logs starting up database engine D:72969b3eaf8e|xapi] About to flush database: /= var/lib/xcp/state.db starting up database engine D:72969b3eaf8e|redo_log] Flushing database to a= ll active redo-logs starting up database engine D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_lo= calhost dbsync (update_env) D:fd0aec7399c9|dbsync] creating localhost dmesg logs seem to suggest that xapi is crashing during startup. [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in= xapi[8048000+59f000] [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in= xapi[8048000+59f000] I looked the XAPI code to see where it fails and I don't see any logs after= the following code point in ocaml / xapi / dbsync_slave.ml let create_localhost ~__context info =3D =A0=A0let ip =3D get_my_ip_addr ~__context in I confirmed to see that "ifconfig xenbr0" has a valid management IP address= and should not fail. = How do I debug this crash further. Are there any ways to look at the stack = trace where XAPI crashed. Any pointers to debug this further will be very h= elpful. -Ranjeet _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Mar 22 03:45:59 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Mar 2014 03:45:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WRCsJ-00071T-46; Sat, 22 Mar 2014 03:45:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WRCsH-00071O-Ux for xen-api@lists.xen.org; Sat, 22 Mar 2014 03:45:34 +0000 Received: from [193.109.254.147:17046] by server-15.bemta-14.messagelabs.com id A4/D8-15813-D570D235; Sat, 22 Mar 2014 03:45:33 +0000 X-Env-Sender: rranjeet@juniper.net X-Msg-Ref: server-7.tower-27.messagelabs.com!1395459931!3405575!1 X-Originating-IP: [216.32.180.14] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28290 invoked from network); 22 Mar 2014 03:45:32 -0000 Received: from va3ehsobe004.messaging.microsoft.com (HELO va3outboundpool.messaging.microsoft.com) (216.32.180.14) by server-7.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 22 Mar 2014 03:45:32 -0000 Received: from mail192-va3-R.bigfish.com (10.7.14.248) by VA3EHSOBE012.bigfish.com (10.7.40.62) with Microsoft SMTP Server id 14.1.225.22; Sat, 22 Mar 2014 03:45:31 +0000 Received: from mail192-va3 (localhost [127.0.0.1]) by mail192-va3-R.bigfish.com (Postfix) with ESMTP id 1E2043200BC for ; Sat, 22 Mar 2014 03:45:31 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: 1 X-BigFish: VPS1(zze0eah14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de097hz2fh109h2a8h839h947hd24hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1dc1h1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24d7h2516h2545h255eh25cch25f6h2605h268bh9a9j1155h) Received-SPF: pass (mail192-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rranjeet@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(189002)(199002)(53754006)(80976001)(74662001)(95416001)(83322001)(19580395003)(47446002)(74876001)(79102001)(86362001)(81686001)(81342001)(94316002)(575784001)(74502001)(81816001)(94946001)(59766001)(56776001)(77982001)(74706001)(54316002)(81542001)(46102001)(76482001)(74316001)(51856001)(93136001)(4396001)(80022001)(97336001)(76176001)(33646001)(31966008)(87936001)(56816005)(87266001)(74366001)(97186001)(76576001)(76796001)(47736001)(49866001)(50986001)(76786001)(47976001)(20776003)(63696002)(85852003)(90146001)(2656002)(92566001)(54356001)(69226001)(93516002)(53806001)(65816001)(66066001)(83072002)(85306002)(98676001)(95666003)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB710; H:BY2PR05MB711.namprd05.prod.outlook.com; FPR:A406C92D.2E074439.43F33964.84A9F373.20284; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail192-va3 (localhost.localdomain [127.0.0.1]) by mail192-va3 (MessageSwitch) id 1395459924328120_5569; Sat, 22 Mar 2014 03:45:24 +0000 (UTC) Received: from VA3EHSMHS023.bigfish.com (unknown [10.7.14.252]) by mail192-va3.bigfish.com (Postfix) with ESMTP id 3612F180047 for ; Sat, 22 Mar 2014 03:45:24 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS023.bigfish.com (10.7.99.33) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sat, 22 Mar 2014 03:45:23 +0000 Received: from BY2PR05MB710.namprd05.prod.outlook.com (10.141.222.147) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Sat, 22 Mar 2014 03:45:23 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BY2PR05MB710.namprd05.prod.outlook.com (10.141.222.147) with Microsoft SMTP Server (TLS) id 15.0.898.11; Sat, 22 Mar 2014 03:45:21 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) by BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) with mapi id 15.00.0898.005; Sat, 22 Mar 2014 03:45:21 +0000 From: Ranjeet R To: "xen-api@lists.xen.org" Thread-Topic: Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fw== Date: Sat, 22 Mar 2014 03:45:20 +0000 Message-ID: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.10] x-forefront-prvs: 01583E185C MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Subject: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello all I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI da= emon. I had changed the underlying network implementation (it is not a brid= ge, but an openvswitch-like network implementation) and the XAPI daemon cra= shes during bootup. Please find the XAPI logs below. = starting up database engine D:72969b3eaf8e|redo_log] Flushing database to a= ll active redo-logs starting up database engine D:72969b3eaf8e|xapi] About to flush database: /= var/lib/xcp/state.db starting up database engine D:72969b3eaf8e|redo_log] Flushing database to a= ll active redo-logs starting up database engine D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_lo= calhost dbsync (update_env) D:fd0aec7399c9|dbsync] creating localhost dmesg logs seem to suggest that xapi is crashing during startup. [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in= xapi[8048000+59f000] [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in= xapi[8048000+59f000] I looked the XAPI code to see where it fails and I don't see any logs after= the following code point in ocaml / xapi / dbsync_slave.ml let create_localhost ~__context info =3D =A0=A0let ip =3D get_my_ip_addr ~__context in I confirmed to see that "ifconfig xenbr0" has a valid management IP address= and should not fail. = How do I debug this crash further. Are there any ways to look at the stack = trace where XAPI crashed. Any pointers to debug this further will be very h= elpful. -Ranjeet _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Mar 22 19:36:39 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Mar 2014 19:36:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WRRiL-0001x6-DC; Sat, 22 Mar 2014 19:36:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WRRiK-0001wx-Qu for xen-api@lists.xen.org; Sat, 22 Mar 2014 19:36:17 +0000 Received: from [85.158.139.211:43557] by server-3.bemta-5.messagelabs.com id 67/1E-28132-F26ED235; Sat, 22 Mar 2014 19:36:15 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1395516974!2719306!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19683 invoked from network); 22 Mar 2014 19:36:14 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Mar 2014 19:36:14 -0000 X-IronPort-AV: E=Sophos;i="4.97,710,1389744000"; d="scan'208";a="12156062" Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 22 Mar 2014 19:36:13 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.213]) by AMSPEX01CL01.citrite.net ([169.254.6.75]) with mapi id 14.02.0342.004; Sat, 22 Mar 2014 20:36:13 +0100 From: Dave Scott To: Ranjeet R Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: AQHPRgX7qneZxaw5P02pVdQzCUQXCg== Date: Sat, 22 Mar 2014 19:36:13 +0000 Message-ID: <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> In-Reply-To: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: AMS1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, I suspect the segfault is being caused by a bad C function binding. I've seen a similar crash before when querying an interface IP via getifaddrs (I think that was the function name) Could you run xapi in gdb and reproduce the crash? Printing the call stack would help to confirm this hypothesis. Provided the xapi binary still has debug symbols (ie hasn't been stripped) the ocaml functions (with fairly obvious mangled names) should also be on the stack too. Cheers, Dave > On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: > > Hello all > > I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI daemon. I had changed the underlying network implementation (it is not a bridge, but an openvswitch-like network implementation) and the XAPI daemon crashes during bootup. Please find the XAPI logs below. > > > starting up database engine D:72969b3eaf8e|redo_log] Flushing database to all active redo-logs > starting up database engine D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > starting up database engine D:72969b3eaf8e|redo_log] Flushing database to all active redo-logs > starting up database engine D:72969b3eaf8e|xapi] Performing initial DB GC > thread_zero|dbsync (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost > dbsync (update_env) D:fd0aec7399c9|dbsync] creating localhost > > dmesg logs seem to suggest that xapi is crashing during startup. > > [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in xapi[8048000+59f000] > [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in xapi[8048000+59f000] > > I looked the XAPI code to see where it fails and I don't see any logs after the following code point in ocaml / xapi / dbsync_slave.ml > > let create_localhost ~__context info = > let ip = get_my_ip_addr ~__context in > > I confirmed to see that "ifconfig xenbr0" has a valid management IP address and should not fail. > > How do I debug this crash further. Are there any ways to look at the stack trace where XAPI crashed. Any pointers to debug this further will be very helpful. > > -Ranjeet > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Sat Mar 22 19:36:39 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 22 Mar 2014 19:36:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WRRiL-0001x6-DC; Sat, 22 Mar 2014 19:36:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WRRiK-0001wx-Qu for xen-api@lists.xen.org; Sat, 22 Mar 2014 19:36:17 +0000 Received: from [85.158.139.211:43557] by server-3.bemta-5.messagelabs.com id 67/1E-28132-F26ED235; Sat, 22 Mar 2014 19:36:15 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1395516974!2719306!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19683 invoked from network); 22 Mar 2014 19:36:14 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Mar 2014 19:36:14 -0000 X-IronPort-AV: E=Sophos;i="4.97,710,1389744000"; d="scan'208";a="12156062" Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 22 Mar 2014 19:36:13 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.213]) by AMSPEX01CL01.citrite.net ([169.254.6.75]) with mapi id 14.02.0342.004; Sat, 22 Mar 2014 20:36:13 +0100 From: Dave Scott To: Ranjeet R Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: AQHPRgX7qneZxaw5P02pVdQzCUQXCg== Date: Sat, 22 Mar 2014 19:36:13 +0000 Message-ID: <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> In-Reply-To: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: AMS1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, I suspect the segfault is being caused by a bad C function binding. I've seen a similar crash before when querying an interface IP via getifaddrs (I think that was the function name) Could you run xapi in gdb and reproduce the crash? Printing the call stack would help to confirm this hypothesis. Provided the xapi binary still has debug symbols (ie hasn't been stripped) the ocaml functions (with fairly obvious mangled names) should also be on the stack too. Cheers, Dave > On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: > > Hello all > > I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI daemon. I had changed the underlying network implementation (it is not a bridge, but an openvswitch-like network implementation) and the XAPI daemon crashes during bootup. Please find the XAPI logs below. > > > starting up database engine D:72969b3eaf8e|redo_log] Flushing database to all active redo-logs > starting up database engine D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > starting up database engine D:72969b3eaf8e|redo_log] Flushing database to all active redo-logs > starting up database engine D:72969b3eaf8e|xapi] Performing initial DB GC > thread_zero|dbsync (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost > dbsync (update_env) D:fd0aec7399c9|dbsync] creating localhost > > dmesg logs seem to suggest that xapi is crashing during startup. > > [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in xapi[8048000+59f000] > [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in xapi[8048000+59f000] > > I looked the XAPI code to see where it fails and I don't see any logs after the following code point in ocaml / xapi / dbsync_slave.ml > > let create_localhost ~__context info = > let ip = get_my_ip_addr ~__context in > > I confirmed to see that "ifconfig xenbr0" has a valid management IP address and should not fail. > > How do I debug this crash further. Are there any ways to look at the stack trace where XAPI crashed. Any pointers to debug this further will be very helpful. > > -Ranjeet > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 24 10:30:46 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Mar 2014 10:30:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WS298-0000xQ-CP; Mon, 24 Mar 2014 10:30:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WS296-0000xJ-EH for xen-api@lists.xen.org; Mon, 24 Mar 2014 10:30:20 +0000 Received: from [85.158.139.211:63778] by server-1.bemta-5.messagelabs.com id 47/37-10259-A3900335; Mon, 24 Mar 2014 10:30:18 +0000 X-Env-Sender: rranjeet@juniper.net X-Msg-Ref: server-10.tower-206.messagelabs.com!1395657015!2918542!1 X-Originating-IP: [213.199.154.207] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32461 invoked from network); 24 Mar 2014 10:30:15 -0000 Received: from am1ehsobe004.messaging.microsoft.com (HELO am1outboundpool.messaging.microsoft.com) (213.199.154.207) by server-10.tower-206.messagelabs.com with AES128-SHA encrypted SMTP; 24 Mar 2014 10:30:15 -0000 Received: from mail85-am1-R.bigfish.com (10.3.201.245) by AM1EHSOBE004.bigfish.com (10.3.204.24) with Microsoft SMTP Server id 14.1.225.22; Mon, 24 Mar 2014 10:30:15 +0000 Received: from mail85-am1 (localhost [127.0.0.1]) by mail85-am1-R.bigfish.com (Postfix) with ESMTP id 9A43DA0182; Mon, 24 Mar 2014 10:30:15 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -10 X-BigFish: VPS-10(zz98dI9371IfecI542Ie0eah1432I1418I14e3M14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h17326ah8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24d7h2516h2545h255eh25cch25f6h2605h262fh268bh9a9j1155h) Received-SPF: pass (mail85-am1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rranjeet@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(13464003)(189002)(199002)(51444003)(377454003)(53754006)(51704005)(24454002)(77982001)(33646001)(69226001)(95416001)(59766001)(74706001)(74366001)(80022001)(65816001)(81342001)(80976001)(63696002)(66066001)(20776003)(81686001)(83322001)(19580405001)(19580395003)(81542001)(15202345003)(98676001)(85852003)(83072002)(90146001)(56816005)(92566001)(94316002)(54316002)(76482001)(54356001)(56776001)(15975445006)(46102001)(53806001)(87266001)(2656002)(74502001)(74662001)(31966008)(76786001)(50986001)(49866001)(47976001)(47736001)(87936001)(79102001)(86362001)(575784001)(93516002)(97186001)(81816001)(76796001)(95666003)(76576001)(74876001)(85306002)(4396001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB709; H:BY2PR05MB711.namprd05.prod.outlook.com; FPR:9C3CF067.E3294F1.43F315E4.46A9F783.2046C; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail85-am1 (localhost.localdomain [127.0.0.1]) by mail85-am1 (MessageSwitch) id 139565701311608_7296; Mon, 24 Mar 2014 10:30:13 +0000 (UTC) Received: from AM1EHSMHS001.bigfish.com (unknown [10.3.201.245]) by mail85-am1.bigfish.com (Postfix) with ESMTP id F2A65120083; Mon, 24 Mar 2014 10:30:12 +0000 (UTC) Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by AM1EHSMHS001.bigfish.com (10.3.207.101) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 24 Mar 2014 10:30:12 +0000 Received: from BY2PR05MB709.namprd05.prod.outlook.com (10.141.222.142) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.423.0; Mon, 24 Mar 2014 10:30:11 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BY2PR05MB709.namprd05.prod.outlook.com (10.141.222.142) with Microsoft SMTP Server (TLS) id 15.0.898.11; Mon, 24 Mar 2014 10:30:09 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) by BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) with mapi id 15.00.0898.005; Mon, 24 Mar 2014 10:30:09 +0000 From: Ranjeet R To: Dave Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAjGnCAADsSOKA= Date: Mon, 24 Mar 2014 10:30:09 +0000 Message-ID: <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> In-Reply-To: <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.14] x-forefront-prvs: 01604FB62B MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello Dave The binaries did not have debug symbols but I managed to rebuild the binaries with debug enabled. I tried starting the xapi process as it was started in the init.d scripts under gdb. However, in gdb, the xapi process forks another process and I am not able to debug it further (I tried setting detach_on_fork to off in gdb, but the primary process just goes to end of execution). I am using the following gdb command to debug gdb --args /usr/sbin/xapi -daemon -writeinitcomplete /var/run/xapi_init_complete.cookie -writereadyfile /var/run/xapi_startup.cookie -onsystemboot" Can you please help me in the steps that you use in debugging the XAPI process. Thanks for your help, -Ranjeet -----Original Message----- From: Dave Scott [mailto:Dave.Scott@citrix.com] Sent: Saturday, March 22, 2014 12:36 PM To: Ranjeet R Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Debugging XAPI daemon crash Hi, I suspect the segfault is being caused by a bad C function binding. I've seen a similar crash before when querying an interface IP via getifaddrs (I think that was the function name) Could you run xapi in gdb and reproduce the crash? Printing the call stack would help to confirm this hypothesis. Provided the xapi binary still has debug symbols (ie hasn't been stripped) the ocaml functions (with fairly obvious mangled names) should also be on the stack too. Cheers, Dave > On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: > > Hello all > > I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI daemon. I had changed the underlying network implementation (it is not a bridge, but an openvswitch-like network implementation) and the XAPI daemon crashes during bootup. Please find the XAPI logs below. > > > starting up database engine D:72969b3eaf8e|redo_log] Flushing database > to all active redo-logs starting up database engine > D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > starting up database engine D:72969b3eaf8e|redo_log] Flushing database > to all active redo-logs starting up database engine > D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync > (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost dbsync > (update_env) D:fd0aec7399c9|dbsync] creating localhost > > dmesg logs seem to suggest that xapi is crashing during startup. > > [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in xapi[8048000+59f000] > [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in xapi[8048000+59f000] > > I looked the XAPI code to see where it fails and I don't see any logs > after the following code point in ocaml / xapi / dbsync_slave.ml > > let create_localhost ~__context info = > let ip = get_my_ip_addr ~__context in > > I confirmed to see that "ifconfig xenbr0" has a valid management IP address and should not fail. > > How do I debug this crash further. Are there any ways to look at the stack trace where XAPI crashed. Any pointers to debug this further will be very helpful. > > -Ranjeet > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 24 10:30:46 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Mar 2014 10:30:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WS298-0000xQ-CP; Mon, 24 Mar 2014 10:30:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WS296-0000xJ-EH for xen-api@lists.xen.org; Mon, 24 Mar 2014 10:30:20 +0000 Received: from [85.158.139.211:63778] by server-1.bemta-5.messagelabs.com id 47/37-10259-A3900335; Mon, 24 Mar 2014 10:30:18 +0000 X-Env-Sender: rranjeet@juniper.net X-Msg-Ref: server-10.tower-206.messagelabs.com!1395657015!2918542!1 X-Originating-IP: [213.199.154.207] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32461 invoked from network); 24 Mar 2014 10:30:15 -0000 Received: from am1ehsobe004.messaging.microsoft.com (HELO am1outboundpool.messaging.microsoft.com) (213.199.154.207) by server-10.tower-206.messagelabs.com with AES128-SHA encrypted SMTP; 24 Mar 2014 10:30:15 -0000 Received: from mail85-am1-R.bigfish.com (10.3.201.245) by AM1EHSOBE004.bigfish.com (10.3.204.24) with Microsoft SMTP Server id 14.1.225.22; Mon, 24 Mar 2014 10:30:15 +0000 Received: from mail85-am1 (localhost [127.0.0.1]) by mail85-am1-R.bigfish.com (Postfix) with ESMTP id 9A43DA0182; Mon, 24 Mar 2014 10:30:15 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -10 X-BigFish: VPS-10(zz98dI9371IfecI542Ie0eah1432I1418I14e3M14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h17326ah8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24d7h2516h2545h255eh25cch25f6h2605h262fh268bh9a9j1155h) Received-SPF: pass (mail85-am1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rranjeet@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(13464003)(189002)(199002)(51444003)(377454003)(53754006)(51704005)(24454002)(77982001)(33646001)(69226001)(95416001)(59766001)(74706001)(74366001)(80022001)(65816001)(81342001)(80976001)(63696002)(66066001)(20776003)(81686001)(83322001)(19580405001)(19580395003)(81542001)(15202345003)(98676001)(85852003)(83072002)(90146001)(56816005)(92566001)(94316002)(54316002)(76482001)(54356001)(56776001)(15975445006)(46102001)(53806001)(87266001)(2656002)(74502001)(74662001)(31966008)(76786001)(50986001)(49866001)(47976001)(47736001)(87936001)(79102001)(86362001)(575784001)(93516002)(97186001)(81816001)(76796001)(95666003)(76576001)(74876001)(85306002)(4396001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB709; H:BY2PR05MB711.namprd05.prod.outlook.com; FPR:9C3CF067.E3294F1.43F315E4.46A9F783.2046C; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail85-am1 (localhost.localdomain [127.0.0.1]) by mail85-am1 (MessageSwitch) id 139565701311608_7296; Mon, 24 Mar 2014 10:30:13 +0000 (UTC) Received: from AM1EHSMHS001.bigfish.com (unknown [10.3.201.245]) by mail85-am1.bigfish.com (Postfix) with ESMTP id F2A65120083; Mon, 24 Mar 2014 10:30:12 +0000 (UTC) Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by AM1EHSMHS001.bigfish.com (10.3.207.101) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 24 Mar 2014 10:30:12 +0000 Received: from BY2PR05MB709.namprd05.prod.outlook.com (10.141.222.142) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.423.0; Mon, 24 Mar 2014 10:30:11 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BY2PR05MB709.namprd05.prod.outlook.com (10.141.222.142) with Microsoft SMTP Server (TLS) id 15.0.898.11; Mon, 24 Mar 2014 10:30:09 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) by BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) with mapi id 15.00.0898.005; Mon, 24 Mar 2014 10:30:09 +0000 From: Ranjeet R To: Dave Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAjGnCAADsSOKA= Date: Mon, 24 Mar 2014 10:30:09 +0000 Message-ID: <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> In-Reply-To: <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.14] x-forefront-prvs: 01604FB62B MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello Dave The binaries did not have debug symbols but I managed to rebuild the binaries with debug enabled. I tried starting the xapi process as it was started in the init.d scripts under gdb. However, in gdb, the xapi process forks another process and I am not able to debug it further (I tried setting detach_on_fork to off in gdb, but the primary process just goes to end of execution). I am using the following gdb command to debug gdb --args /usr/sbin/xapi -daemon -writeinitcomplete /var/run/xapi_init_complete.cookie -writereadyfile /var/run/xapi_startup.cookie -onsystemboot" Can you please help me in the steps that you use in debugging the XAPI process. Thanks for your help, -Ranjeet -----Original Message----- From: Dave Scott [mailto:Dave.Scott@citrix.com] Sent: Saturday, March 22, 2014 12:36 PM To: Ranjeet R Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Debugging XAPI daemon crash Hi, I suspect the segfault is being caused by a bad C function binding. I've seen a similar crash before when querying an interface IP via getifaddrs (I think that was the function name) Could you run xapi in gdb and reproduce the crash? Printing the call stack would help to confirm this hypothesis. Provided the xapi binary still has debug symbols (ie hasn't been stripped) the ocaml functions (with fairly obvious mangled names) should also be on the stack too. Cheers, Dave > On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: > > Hello all > > I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI daemon. I had changed the underlying network implementation (it is not a bridge, but an openvswitch-like network implementation) and the XAPI daemon crashes during bootup. Please find the XAPI logs below. > > > starting up database engine D:72969b3eaf8e|redo_log] Flushing database > to all active redo-logs starting up database engine > D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > starting up database engine D:72969b3eaf8e|redo_log] Flushing database > to all active redo-logs starting up database engine > D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync > (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost dbsync > (update_env) D:fd0aec7399c9|dbsync] creating localhost > > dmesg logs seem to suggest that xapi is crashing during startup. > > [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in xapi[8048000+59f000] > [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in xapi[8048000+59f000] > > I looked the XAPI code to see where it fails and I don't see any logs > after the following code point in ocaml / xapi / dbsync_slave.ml > > let create_localhost ~__context info = > let ip = get_my_ip_addr ~__context in > > I confirmed to see that "ifconfig xenbr0" has a valid management IP address and should not fail. > > How do I debug this crash further. Are there any ways to look at the stack trace where XAPI crashed. Any pointers to debug this further will be very helpful. > > -Ranjeet > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 24 10:47:05 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Mar 2014 10:47:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WS2P4-0002An-0o; Mon, 24 Mar 2014 10:46:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WS2P3-0002AY-6R for xen-api@lists.xen.org; Mon, 24 Mar 2014 10:46:49 +0000 Received: from [85.158.143.35:50166] by server-2.bemta-4.messagelabs.com id DC/4D-06539-81D00335; Mon, 24 Mar 2014 10:46:48 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1395658006!4246198!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11074 invoked from network); 24 Mar 2014 10:46:47 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Mar 2014 10:46:47 -0000 X-IronPort-AV: E=Sophos;i="4.97,720,1389744000"; d="scan'208";a="114255386" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 24 Mar 2014 10:46:25 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Mon, 24 Mar 2014 06:46:23 -0400 Received: from [10.80.239.111] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1WS2Od-0005ox-Ki; Mon, 24 Mar 2014 10:46:23 +0000 Message-ID: <53300CF4.1060402@eu.citrix.com> Date: Mon, 24 Mar 2014 10:46:12 +0000 From: David Scott User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Ranjeet R References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> In-Reply-To: <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> X-DLP: MIA1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/03/14 10:30, Ranjeet R wrote: > Hello Dave > > The binaries did not have debug symbols but I managed to rebuild the binaries with debug enabled. Great. > I tried starting the xapi process as it was started in the init.d scripts under gdb. However, in gdb, the xapi process forks another process and I am not able to debug it further (I tried setting detach_on_fork to off in gdb, but the primary process just goes to end of execution). > > I am using the following gdb command to debug > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete /var/run/xapi_init_complete.cookie -writereadyfile /var/run/xapi_startup.cookie -onsystemboot" > > Can you please help me in the steps that you use in debugging the XAPI process. Ah, I think xapi forks a "watchdog" process near the start -- this is probably what you're seeing. Try adding a "-nowatchdog" option to the command-line. Dave > > Thanks for your help, > > -Ranjeet > > > > -----Original Message----- > From: Dave Scott [mailto:Dave.Scott@citrix.com] > Sent: Saturday, March 22, 2014 12:36 PM > To: Ranjeet R > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > Hi, > > I suspect the segfault is being caused by a bad C function binding. I've seen a similar crash before when querying an interface IP via getifaddrs (I think that was the function name) Could you run xapi in gdb and reproduce the crash? Printing the call stack would help to confirm this hypothesis. Provided the xapi binary still has debug symbols (ie hasn't been stripped) the ocaml functions (with fairly obvious mangled names) should also be on the stack too. > > Cheers, > Dave > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: >> >> Hello all >> >> I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI daemon. I had changed the underlying network implementation (it is not a bridge, but an openvswitch-like network implementation) and the XAPI daemon crashes during bootup. Please find the XAPI logs below. >> >> >> starting up database engine D:72969b3eaf8e|redo_log] Flushing database >> to all active redo-logs starting up database engine >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db >> starting up database engine D:72969b3eaf8e|redo_log] Flushing database >> to all active redo-logs starting up database engine >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost dbsync >> (update_env) D:fd0aec7399c9|dbsync] creating localhost >> >> dmesg logs seem to suggest that xapi is crashing during startup. >> >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in xapi[8048000+59f000] >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in xapi[8048000+59f000] >> >> I looked the XAPI code to see where it fails and I don't see any logs >> after the following code point in ocaml / xapi / dbsync_slave.ml >> >> let create_localhost ~__context info = >> let ip = get_my_ip_addr ~__context in >> >> I confirmed to see that "ifconfig xenbr0" has a valid management IP address and should not fail. >> >> How do I debug this crash further. Are there any ways to look at the stack trace where XAPI crashed. Any pointers to debug this further will be very helpful. >> >> -Ranjeet >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Mar 24 10:47:05 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 24 Mar 2014 10:47:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WS2P4-0002An-0o; Mon, 24 Mar 2014 10:46:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WS2P3-0002AY-6R for xen-api@lists.xen.org; Mon, 24 Mar 2014 10:46:49 +0000 Received: from [85.158.143.35:50166] by server-2.bemta-4.messagelabs.com id DC/4D-06539-81D00335; Mon, 24 Mar 2014 10:46:48 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1395658006!4246198!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11074 invoked from network); 24 Mar 2014 10:46:47 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Mar 2014 10:46:47 -0000 X-IronPort-AV: E=Sophos;i="4.97,720,1389744000"; d="scan'208";a="114255386" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 24 Mar 2014 10:46:25 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Mon, 24 Mar 2014 06:46:23 -0400 Received: from [10.80.239.111] by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1WS2Od-0005ox-Ki; Mon, 24 Mar 2014 10:46:23 +0000 Message-ID: <53300CF4.1060402@eu.citrix.com> Date: Mon, 24 Mar 2014 10:46:12 +0000 From: David Scott User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Ranjeet R References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> In-Reply-To: <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> X-DLP: MIA1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 24/03/14 10:30, Ranjeet R wrote: > Hello Dave > > The binaries did not have debug symbols but I managed to rebuild the binaries with debug enabled. Great. > I tried starting the xapi process as it was started in the init.d scripts under gdb. However, in gdb, the xapi process forks another process and I am not able to debug it further (I tried setting detach_on_fork to off in gdb, but the primary process just goes to end of execution). > > I am using the following gdb command to debug > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete /var/run/xapi_init_complete.cookie -writereadyfile /var/run/xapi_startup.cookie -onsystemboot" > > Can you please help me in the steps that you use in debugging the XAPI process. Ah, I think xapi forks a "watchdog" process near the start -- this is probably what you're seeing. Try adding a "-nowatchdog" option to the command-line. Dave > > Thanks for your help, > > -Ranjeet > > > > -----Original Message----- > From: Dave Scott [mailto:Dave.Scott@citrix.com] > Sent: Saturday, March 22, 2014 12:36 PM > To: Ranjeet R > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > Hi, > > I suspect the segfault is being caused by a bad C function binding. I've seen a similar crash before when querying an interface IP via getifaddrs (I think that was the function name) Could you run xapi in gdb and reproduce the crash? Printing the call stack would help to confirm this hypothesis. Provided the xapi binary still has debug symbols (ie hasn't been stripped) the ocaml functions (with fairly obvious mangled names) should also be on the stack too. > > Cheers, > Dave > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: >> >> Hello all >> >> I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI daemon. I had changed the underlying network implementation (it is not a bridge, but an openvswitch-like network implementation) and the XAPI daemon crashes during bootup. Please find the XAPI logs below. >> >> >> starting up database engine D:72969b3eaf8e|redo_log] Flushing database >> to all active redo-logs starting up database engine >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db >> starting up database engine D:72969b3eaf8e|redo_log] Flushing database >> to all active redo-logs starting up database engine >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost dbsync >> (update_env) D:fd0aec7399c9|dbsync] creating localhost >> >> dmesg logs seem to suggest that xapi is crashing during startup. >> >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in xapi[8048000+59f000] >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in xapi[8048000+59f000] >> >> I looked the XAPI code to see where it fails and I don't see any logs >> after the following code point in ocaml / xapi / dbsync_slave.ml >> >> let create_localhost ~__context info = >> let ip = get_my_ip_addr ~__context in >> >> I confirmed to see that "ifconfig xenbr0" has a valid management IP address and should not fail. >> >> How do I debug this crash further. Are there any ways to look at the stack trace where XAPI crashed. Any pointers to debug this further will be very helpful. >> >> -Ranjeet >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Mar 26 04:11:16 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Mar 2014 04:11:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSfB2-0003NR-7M; Wed, 26 Mar 2014 04:10:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSfB0-0003N5-PQ for xen-api@lists.xen.org; Wed, 26 Mar 2014 04:10:55 +0000 Received: from [193.109.254.147:50973] by server-6.bemta-14.messagelabs.com id 93/95-13066-E4352335; Wed, 26 Mar 2014 04:10:54 +0000 X-Env-Sender: rranjeet@juniper.net X-Msg-Ref: server-9.tower-27.messagelabs.com!1395807052!4151652!1 X-Originating-IP: [216.32.180.16] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22248 invoked from network); 26 Mar 2014 04:10:52 -0000 Received: from va3ehsobe006.messaging.microsoft.com (HELO va3outboundpool.messaging.microsoft.com) (216.32.180.16) by server-9.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 26 Mar 2014 04:10:52 -0000 Received: from mail162-va3-R.bigfish.com (10.7.14.227) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.22; Wed, 26 Mar 2014 04:10:52 +0000 Received: from mail162-va3 (localhost [127.0.0.1]) by mail162-va3-R.bigfish.com (Postfix) with ESMTP id 7C3AB3A01B5; Wed, 26 Mar 2014 04:10:51 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -11 X-BigFish: VPS-11(zzbb2dI98dI9371IfecI542Ie0eah1432I1418I14e3M14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h17326ah8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh25cch25f6h2605h262fh268bh9a9j1155h) Received-SPF: pass (mail162-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rranjeet@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(13464003)(53474002)(189002)(199002)(377454003)(479174003)(51704005)(51444003)(24454002)(53754006)(76576001)(97186001)(97336001)(74502001)(74706001)(74662001)(47446002)(74876001)(95416001)(47976001)(85306002)(2656002)(63696002)(87266001)(92566001)(80976001)(20776003)(31966008)(19580405001)(83322001)(19580395003)(94316002)(15975445006)(95666003)(81686001)(81816001)(47736001)(94946001)(49866001)(50986001)(74316001)(74366001)(85852003)(90146001)(4396001)(83072002)(69226001)(93136001)(575784001)(93516002)(86362001)(79102001)(98676001)(51856001)(87936001)(56776001)(66066001)(80022001)(65816001)(54316002)(46102001)(81342001)(81542001)(54356001)(76482001)(15202345003)(59766001)(77982001)(53806001)(33646001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB711; H:BY2PR05MB711.namprd05.prod.outlook.com; FPR:DC3CF067.2F329471.71F315E4.41A9F781.20596; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail162-va3 (localhost.localdomain [127.0.0.1]) by mail162-va3 (MessageSwitch) id 1395807048924153_27608; Wed, 26 Mar 2014 04:10:48 +0000 (UTC) Received: from VA3EHSMHS045.bigfish.com (unknown [10.7.14.236]) by mail162-va3.bigfish.com (Postfix) with ESMTP id DB77C120054; Wed, 26 Mar 2014 04:10:48 +0000 (UTC) Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS045.bigfish.com (10.7.99.55) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 26 Mar 2014 04:10:48 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.423.0; Wed, 26 Mar 2014 04:10:48 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) with Microsoft SMTP Server (TLS) id 15.0.898.11; Wed, 26 Mar 2014 04:10:46 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) by BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) with mapi id 15.00.0898.005; Wed, 26 Mar 2014 04:10:46 +0000 From: Ranjeet R To: David Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAjGnCAADsSOKAAFwBFAABOHF9w Date: Wed, 26 Mar 2014 04:10:46 +0000 Message-ID: References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> <53300CF4.1060402@eu.citrix.com> In-Reply-To: <53300CF4.1060402@eu.citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.14] x-forefront-prvs: 0162ACCC24 MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello Dave I was able to attach the debugger only when I executed xapi without any arguments. The backtrace looks like this - 0x080693e0 in camlDbsync_slave__create_localhost_3057 () (gdb) bt #0 0x080693e0 in camlDbsync_slave__create_localhost_3057 () #1 0x0806a16c in camlDbsync_slave__update_env_4937 () #2 0xb7c99f78 in ?? () (gdb) n 0x080693a0 in camlDbsync_slave__get_my_ip_addr_3055 () It seems to be crashing in the same point as you had mentioned. Please find the SEGV backtrace attached. (gdb) c Program received signal SIGSEGV, Segmentation fault. 0x085bc2d6 in stub_if_getaddr () (gdb) bt #0 0x085cca90 in segv_handler () #1 #2 0x085bc2d6 in stub_if_getaddr () #3 0x0850ef8c in camlNetdev__get_all_ipv4_1325 () You had mentioned that this could be because of a bad C function binding. I wrote a small C stub to see whether it works for the xenbr0 interface and it seems to be working fine. How should I verify the binding. Appreciate your help. -Ranjeet -----Original Message----- From: David Scott [mailto:dave.scott@eu.citrix.com] Sent: Monday, March 24, 2014 3:46 AM To: Ranjeet R Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Debugging XAPI daemon crash On 24/03/14 10:30, Ranjeet R wrote: > Hello Dave > > The binaries did not have debug symbols but I managed to rebuild the binaries with debug enabled. Great. > I tried starting the xapi process as it was started in the init.d scripts under gdb. However, in gdb, the xapi process forks another process and I am not able to debug it further (I tried setting detach_on_fork to off in gdb, but the primary process just goes to end of execution). > > I am using the following gdb command to debug > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete /var/run/xapi_init_complete.cookie -writereadyfile /var/run/xapi_startup.cookie -onsystemboot" > > Can you please help me in the steps that you use in debugging the XAPI process. Ah, I think xapi forks a "watchdog" process near the start -- this is probably what you're seeing. Try adding a "-nowatchdog" option to the command-line. Dave > > Thanks for your help, > > -Ranjeet > > > > -----Original Message----- > From: Dave Scott [mailto:Dave.Scott@citrix.com] > Sent: Saturday, March 22, 2014 12:36 PM > To: Ranjeet R > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > Hi, > > I suspect the segfault is being caused by a bad C function binding. I've seen a similar crash before when querying an interface IP via getifaddrs (I think that was the function name) Could you run xapi in gdb and reproduce the crash? Printing the call stack would help to confirm this hypothesis. Provided the xapi binary still has debug symbols (ie hasn't been stripped) the ocaml functions (with fairly obvious mangled names) should also be on the stack too. > > Cheers, > Dave > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: >> >> Hello all >> >> I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI daemon. I had changed the underlying network implementation (it is not a bridge, but an openvswitch-like network implementation) and the XAPI daemon crashes during bootup. Please find the XAPI logs below. >> >> >> starting up database engine D:72969b3eaf8e|redo_log] Flushing >> database to all active redo-logs starting up database engine >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db >> starting up database engine D:72969b3eaf8e|redo_log] Flushing >> database to all active redo-logs starting up database engine >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost >> dbsync >> (update_env) D:fd0aec7399c9|dbsync] creating localhost >> >> dmesg logs seem to suggest that xapi is crashing during startup. >> >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in xapi[8048000+59f000] >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in xapi[8048000+59f000] >> >> I looked the XAPI code to see where it fails and I don't see any logs >> after the following code point in ocaml / xapi / dbsync_slave.ml >> >> let create_localhost ~__context info = >> let ip = get_my_ip_addr ~__context in >> >> I confirmed to see that "ifconfig xenbr0" has a valid management IP address and should not fail. >> >> How do I debug this crash further. Are there any ways to look at the stack trace where XAPI crashed. Any pointers to debug this further will be very helpful. >> >> -Ranjeet >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Mar 26 04:11:16 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Mar 2014 04:11:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSfB2-0003NR-7M; Wed, 26 Mar 2014 04:10:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSfB0-0003N5-PQ for xen-api@lists.xen.org; Wed, 26 Mar 2014 04:10:55 +0000 Received: from [193.109.254.147:50973] by server-6.bemta-14.messagelabs.com id 93/95-13066-E4352335; Wed, 26 Mar 2014 04:10:54 +0000 X-Env-Sender: rranjeet@juniper.net X-Msg-Ref: server-9.tower-27.messagelabs.com!1395807052!4151652!1 X-Originating-IP: [216.32.180.16] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22248 invoked from network); 26 Mar 2014 04:10:52 -0000 Received: from va3ehsobe006.messaging.microsoft.com (HELO va3outboundpool.messaging.microsoft.com) (216.32.180.16) by server-9.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 26 Mar 2014 04:10:52 -0000 Received: from mail162-va3-R.bigfish.com (10.7.14.227) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.22; Wed, 26 Mar 2014 04:10:52 +0000 Received: from mail162-va3 (localhost [127.0.0.1]) by mail162-va3-R.bigfish.com (Postfix) with ESMTP id 7C3AB3A01B5; Wed, 26 Mar 2014 04:10:51 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -11 X-BigFish: VPS-11(zzbb2dI98dI9371IfecI542Ie0eah1432I1418I14e3M14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h17326ah8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh25cch25f6h2605h262fh268bh9a9j1155h) Received-SPF: pass (mail162-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rranjeet@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(13464003)(53474002)(189002)(199002)(377454003)(479174003)(51704005)(51444003)(24454002)(53754006)(76576001)(97186001)(97336001)(74502001)(74706001)(74662001)(47446002)(74876001)(95416001)(47976001)(85306002)(2656002)(63696002)(87266001)(92566001)(80976001)(20776003)(31966008)(19580405001)(83322001)(19580395003)(94316002)(15975445006)(95666003)(81686001)(81816001)(47736001)(94946001)(49866001)(50986001)(74316001)(74366001)(85852003)(90146001)(4396001)(83072002)(69226001)(93136001)(575784001)(93516002)(86362001)(79102001)(98676001)(51856001)(87936001)(56776001)(66066001)(80022001)(65816001)(54316002)(46102001)(81342001)(81542001)(54356001)(76482001)(15202345003)(59766001)(77982001)(53806001)(33646001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB711; H:BY2PR05MB711.namprd05.prod.outlook.com; FPR:DC3CF067.2F329471.71F315E4.41A9F781.20596; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received: from mail162-va3 (localhost.localdomain [127.0.0.1]) by mail162-va3 (MessageSwitch) id 1395807048924153_27608; Wed, 26 Mar 2014 04:10:48 +0000 (UTC) Received: from VA3EHSMHS045.bigfish.com (unknown [10.7.14.236]) by mail162-va3.bigfish.com (Postfix) with ESMTP id DB77C120054; Wed, 26 Mar 2014 04:10:48 +0000 (UTC) Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS045.bigfish.com (10.7.99.55) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 26 Mar 2014 04:10:48 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.423.0; Wed, 26 Mar 2014 04:10:48 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) with Microsoft SMTP Server (TLS) id 15.0.898.11; Wed, 26 Mar 2014 04:10:46 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) by BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) with mapi id 15.00.0898.005; Wed, 26 Mar 2014 04:10:46 +0000 From: Ranjeet R To: David Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAjGnCAADsSOKAAFwBFAABOHF9w Date: Wed, 26 Mar 2014 04:10:46 +0000 Message-ID: References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> <53300CF4.1060402@eu.citrix.com> In-Reply-To: <53300CF4.1060402@eu.citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.14] x-forefront-prvs: 0162ACCC24 MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello Dave I was able to attach the debugger only when I executed xapi without any arguments. The backtrace looks like this - 0x080693e0 in camlDbsync_slave__create_localhost_3057 () (gdb) bt #0 0x080693e0 in camlDbsync_slave__create_localhost_3057 () #1 0x0806a16c in camlDbsync_slave__update_env_4937 () #2 0xb7c99f78 in ?? () (gdb) n 0x080693a0 in camlDbsync_slave__get_my_ip_addr_3055 () It seems to be crashing in the same point as you had mentioned. Please find the SEGV backtrace attached. (gdb) c Program received signal SIGSEGV, Segmentation fault. 0x085bc2d6 in stub_if_getaddr () (gdb) bt #0 0x085cca90 in segv_handler () #1 #2 0x085bc2d6 in stub_if_getaddr () #3 0x0850ef8c in camlNetdev__get_all_ipv4_1325 () You had mentioned that this could be because of a bad C function binding. I wrote a small C stub to see whether it works for the xenbr0 interface and it seems to be working fine. How should I verify the binding. Appreciate your help. -Ranjeet -----Original Message----- From: David Scott [mailto:dave.scott@eu.citrix.com] Sent: Monday, March 24, 2014 3:46 AM To: Ranjeet R Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Debugging XAPI daemon crash On 24/03/14 10:30, Ranjeet R wrote: > Hello Dave > > The binaries did not have debug symbols but I managed to rebuild the binaries with debug enabled. Great. > I tried starting the xapi process as it was started in the init.d scripts under gdb. However, in gdb, the xapi process forks another process and I am not able to debug it further (I tried setting detach_on_fork to off in gdb, but the primary process just goes to end of execution). > > I am using the following gdb command to debug > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete /var/run/xapi_init_complete.cookie -writereadyfile /var/run/xapi_startup.cookie -onsystemboot" > > Can you please help me in the steps that you use in debugging the XAPI process. Ah, I think xapi forks a "watchdog" process near the start -- this is probably what you're seeing. Try adding a "-nowatchdog" option to the command-line. Dave > > Thanks for your help, > > -Ranjeet > > > > -----Original Message----- > From: Dave Scott [mailto:Dave.Scott@citrix.com] > Sent: Saturday, March 22, 2014 12:36 PM > To: Ranjeet R > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > Hi, > > I suspect the segfault is being caused by a bad C function binding. I've seen a similar crash before when querying an interface IP via getifaddrs (I think that was the function name) Could you run xapi in gdb and reproduce the crash? Printing the call stack would help to confirm this hypothesis. Provided the xapi binary still has debug symbols (ie hasn't been stripped) the ocaml functions (with fairly obvious mangled names) should also be on the stack too. > > Cheers, > Dave > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: >> >> Hello all >> >> I am trying to bring a DevCloud setup which has an XCP Kronos based XAPI daemon. I had changed the underlying network implementation (it is not a bridge, but an openvswitch-like network implementation) and the XAPI daemon crashes during bootup. Please find the XAPI logs below. >> >> >> starting up database engine D:72969b3eaf8e|redo_log] Flushing >> database to all active redo-logs starting up database engine >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db >> starting up database engine D:72969b3eaf8e|redo_log] Flushing >> database to all active redo-logs starting up database engine >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost >> dbsync >> (update_env) D:fd0aec7399c9|dbsync] creating localhost >> >> dmesg logs seem to suggest that xapi is crashing during startup. >> >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error 4 in xapi[8048000+59f000] >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error 4 in xapi[8048000+59f000] >> >> I looked the XAPI code to see where it fails and I don't see any logs >> after the following code point in ocaml / xapi / dbsync_slave.ml >> >> let create_localhost ~__context info = >> let ip = get_my_ip_addr ~__context in >> >> I confirmed to see that "ifconfig xenbr0" has a valid management IP address and should not fail. >> >> How do I debug this crash further. Are there any ways to look at the stack trace where XAPI crashed. Any pointers to debug this further will be very helpful. >> >> -Ranjeet >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Mar 26 11:44:57 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Mar 2014 11:44:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSmG5-0003UG-Gy; Wed, 26 Mar 2014 11:44:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSmFh-0003Te-Ke for xen-api@lists.xen.org; Wed, 26 Mar 2014 11:44:34 +0000 Received: from [85.158.139.211:3169] by server-3.bemta-5.messagelabs.com id B8/E9-28132-C8DB2335; Wed, 26 Mar 2014 11:44:12 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1395834251!3238804!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8279 invoked from network); 26 Mar 2014 11:44:11 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2014 11:44:11 -0000 X-IronPort-AV: E=Sophos;i="4.97,735,1389744000"; d="scan'208";a="12467938" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 26 Mar 2014 11:44:11 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.213]) by AMSPEX01CL02.citrite.net ([169.254.7.78]) with mapi id 14.02.0342.004; Wed, 26 Mar 2014 12:44:11 +0100 From: Rob Hoes To: 'Ranjeet R' , Dave Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAhAf+AAFGC/oAAAI9/AABWxcIAABGwNkA= Date: Wed, 26 Mar 2014 11:44:10 +0000 Message-ID: <360717C0B01E6345BCBE64B758E22C2D258185@AMSPEX01CL03.citrite.net> References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> <53300CF4.1060402@eu.citrix.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.46] MIME-Version: 1.0 X-DLP: AMS1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Ranjeet, > It seems to be crashing in the same point as you had mentioned. Please > find the SEGV backtrace attached. > > (gdb) c > Program received signal SIGSEGV, Segmentation fault. > 0x085bc2d6 in stub_if_getaddr () > (gdb) bt > #0 0x085cca90 in segv_handler () > #1 > #2 0x085bc2d6 in stub_if_getaddr () > #3 0x0850ef8c in camlNetdev__get_all_ipv4_1325 () > > You had mentioned that this could be because of a bad C function binding. > I wrote a small C stub to see whether it works for the xenbr0 interface > and it seems to be working fine. How should I verify the binding. The function that is failing seems to be this one: https://github.com/xapi-project/xen-api-libs/blob/clearwater/netdev/addr_stubs.c#L74 It has: int ret; struct ifaddrs *ifaddrs, *tmp; [...] ret = getifaddrs(&ifaddrs); [...] for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { sock = tmp->ifa_addr; netmask = tmp->ifa_netmask; [...] Could it be that the getifaddrs function does not set ifaddrs correctly? You should be able to test this with a small C program. Or is this what you have already done? Cheers, Rob > Appreciate your help. > > -Ranjeet > > -----Original Message----- > From: David Scott [mailto:dave.scott@eu.citrix.com] > Sent: Monday, March 24, 2014 3:46 AM > To: Ranjeet R > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > On 24/03/14 10:30, Ranjeet R wrote: > > Hello Dave > > > > The binaries did not have debug symbols but I managed to rebuild the > binaries with debug enabled. > > Great. > > > I tried starting the xapi process as it was started in the init.d > scripts under gdb. However, in gdb, the xapi process forks another process > and I am not able to debug it further (I tried setting detach_on_fork to > off in gdb, but the primary process just goes to end of execution). > > > > I am using the following gdb command to debug > > > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete > /var/run/xapi_init_complete.cookie -writereadyfile > /var/run/xapi_startup.cookie -onsystemboot" > > > > Can you please help me in the steps that you use in debugging the XAPI > process. > > Ah, I think xapi forks a "watchdog" process near the start -- this is > probably what you're seeing. > > Try adding a "-nowatchdog" option to the command-line. > > Dave > > > > > Thanks for your help, > > > > -Ranjeet > > > > > > > > -----Original Message----- > > From: Dave Scott [mailto:Dave.Scott@citrix.com] > > Sent: Saturday, March 22, 2014 12:36 PM > > To: Ranjeet R > > Cc: xen-api@lists.xen.org > > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > > > Hi, > > > > I suspect the segfault is being caused by a bad C function binding. I've > seen a similar crash before when querying an interface IP via getifaddrs > (I think that was the function name) Could you run xapi in gdb and > reproduce the crash? Printing the call stack would help to confirm this > hypothesis. Provided the xapi binary still has debug symbols (ie hasn't > been stripped) the ocaml functions (with fairly obvious mangled names) > should also be on the stack too. > > > > Cheers, > > Dave > > > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: > >> > >> Hello all > >> > >> I am trying to bring a DevCloud setup which has an XCP Kronos based > XAPI daemon. I had changed the underlying network implementation (it is > not a bridge, but an openvswitch-like network implementation) and the XAPI > daemon crashes during bootup. Please find the XAPI logs below. > >> > >> > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > >> database to all active redo-logs starting up database engine > >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > >> database to all active redo-logs starting up database engine > >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync > >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost > >> dbsync > >> (update_env) D:fd0aec7399c9|dbsync] creating localhost > >> > >> dmesg logs seem to suggest that xapi is crashing during startup. > >> > >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error > 4 in xapi[8048000+59f000] > >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error > 4 in xapi[8048000+59f000] > >> > >> I looked the XAPI code to see where it fails and I don't see any logs > >> after the following code point in ocaml / xapi / dbsync_slave.ml > >> > >> let create_localhost ~__context info = > >> let ip = get_my_ip_addr ~__context in > >> > >> I confirmed to see that "ifconfig xenbr0" has a valid management IP > address and should not fail. > >> > >> How do I debug this crash further. Are there any ways to look at the > stack trace where XAPI crashed. Any pointers to debug this further will be > very helpful. > >> > >> -Ranjeet > >> > >> > >> _______________________________________________ > >> Xen-api mailing list > >> Xen-api@lists.xen.org > >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > > > > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Mar 26 11:44:57 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Mar 2014 11:44:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSmG5-0003UG-Gy; Wed, 26 Mar 2014 11:44:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSmFh-0003Te-Ke for xen-api@lists.xen.org; Wed, 26 Mar 2014 11:44:34 +0000 Received: from [85.158.139.211:3169] by server-3.bemta-5.messagelabs.com id B8/E9-28132-C8DB2335; Wed, 26 Mar 2014 11:44:12 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1395834251!3238804!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8279 invoked from network); 26 Mar 2014 11:44:11 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2014 11:44:11 -0000 X-IronPort-AV: E=Sophos;i="4.97,735,1389744000"; d="scan'208";a="12467938" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 26 Mar 2014 11:44:11 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.213]) by AMSPEX01CL02.citrite.net ([169.254.7.78]) with mapi id 14.02.0342.004; Wed, 26 Mar 2014 12:44:11 +0100 From: Rob Hoes To: 'Ranjeet R' , Dave Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAhAf+AAFGC/oAAAI9/AABWxcIAABGwNkA= Date: Wed, 26 Mar 2014 11:44:10 +0000 Message-ID: <360717C0B01E6345BCBE64B758E22C2D258185@AMSPEX01CL03.citrite.net> References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> <53300CF4.1060402@eu.citrix.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.46] MIME-Version: 1.0 X-DLP: AMS1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Ranjeet, > It seems to be crashing in the same point as you had mentioned. Please > find the SEGV backtrace attached. > > (gdb) c > Program received signal SIGSEGV, Segmentation fault. > 0x085bc2d6 in stub_if_getaddr () > (gdb) bt > #0 0x085cca90 in segv_handler () > #1 > #2 0x085bc2d6 in stub_if_getaddr () > #3 0x0850ef8c in camlNetdev__get_all_ipv4_1325 () > > You had mentioned that this could be because of a bad C function binding. > I wrote a small C stub to see whether it works for the xenbr0 interface > and it seems to be working fine. How should I verify the binding. The function that is failing seems to be this one: https://github.com/xapi-project/xen-api-libs/blob/clearwater/netdev/addr_stubs.c#L74 It has: int ret; struct ifaddrs *ifaddrs, *tmp; [...] ret = getifaddrs(&ifaddrs); [...] for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { sock = tmp->ifa_addr; netmask = tmp->ifa_netmask; [...] Could it be that the getifaddrs function does not set ifaddrs correctly? You should be able to test this with a small C program. Or is this what you have already done? Cheers, Rob > Appreciate your help. > > -Ranjeet > > -----Original Message----- > From: David Scott [mailto:dave.scott@eu.citrix.com] > Sent: Monday, March 24, 2014 3:46 AM > To: Ranjeet R > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > On 24/03/14 10:30, Ranjeet R wrote: > > Hello Dave > > > > The binaries did not have debug symbols but I managed to rebuild the > binaries with debug enabled. > > Great. > > > I tried starting the xapi process as it was started in the init.d > scripts under gdb. However, in gdb, the xapi process forks another process > and I am not able to debug it further (I tried setting detach_on_fork to > off in gdb, but the primary process just goes to end of execution). > > > > I am using the following gdb command to debug > > > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete > /var/run/xapi_init_complete.cookie -writereadyfile > /var/run/xapi_startup.cookie -onsystemboot" > > > > Can you please help me in the steps that you use in debugging the XAPI > process. > > Ah, I think xapi forks a "watchdog" process near the start -- this is > probably what you're seeing. > > Try adding a "-nowatchdog" option to the command-line. > > Dave > > > > > Thanks for your help, > > > > -Ranjeet > > > > > > > > -----Original Message----- > > From: Dave Scott [mailto:Dave.Scott@citrix.com] > > Sent: Saturday, March 22, 2014 12:36 PM > > To: Ranjeet R > > Cc: xen-api@lists.xen.org > > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > > > Hi, > > > > I suspect the segfault is being caused by a bad C function binding. I've > seen a similar crash before when querying an interface IP via getifaddrs > (I think that was the function name) Could you run xapi in gdb and > reproduce the crash? Printing the call stack would help to confirm this > hypothesis. Provided the xapi binary still has debug symbols (ie hasn't > been stripped) the ocaml functions (with fairly obvious mangled names) > should also be on the stack too. > > > > Cheers, > > Dave > > > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: > >> > >> Hello all > >> > >> I am trying to bring a DevCloud setup which has an XCP Kronos based > XAPI daemon. I had changed the underlying network implementation (it is > not a bridge, but an openvswitch-like network implementation) and the XAPI > daemon crashes during bootup. Please find the XAPI logs below. > >> > >> > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > >> database to all active redo-logs starting up database engine > >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > >> database to all active redo-logs starting up database engine > >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync > >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost > >> dbsync > >> (update_env) D:fd0aec7399c9|dbsync] creating localhost > >> > >> dmesg logs seem to suggest that xapi is crashing during startup. > >> > >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error > 4 in xapi[8048000+59f000] > >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error > 4 in xapi[8048000+59f000] > >> > >> I looked the XAPI code to see where it fails and I don't see any logs > >> after the following code point in ocaml / xapi / dbsync_slave.ml > >> > >> let create_localhost ~__context info = > >> let ip = get_my_ip_addr ~__context in > >> > >> I confirmed to see that "ifconfig xenbr0" has a valid management IP > address and should not fail. > >> > >> How do I debug this crash further. Are there any ways to look at the > stack trace where XAPI crashed. Any pointers to debug this further will be > very helpful. > >> > >> -Ranjeet > >> > >> > >> _______________________________________________ > >> Xen-api mailing list > >> Xen-api@lists.xen.org > >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > > > > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Mar 26 23:09:08 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Mar 2014 23:09:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSwwA-0007jy-60; Wed, 26 Mar 2014 23:08:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSww9-0007jg-4v for xen-api@lists.xen.org; Wed, 26 Mar 2014 23:08:45 +0000 Received: from [85.158.139.211:10773] by server-9.bemta-5.messagelabs.com id 43/80-04350-CFD53335; Wed, 26 Mar 2014 23:08:44 +0000 X-Env-Sender: rranjeet@juniper.net X-Msg-Ref: server-8.tower-206.messagelabs.com!1395875322!3380479!1 X-Originating-IP: [216.32.181.185] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29130 invoked from network); 26 Mar 2014 23:08:43 -0000 Received: from ch1ehsobe005.messaging.microsoft.com (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.185) by server-8.tower-206.messagelabs.com with AES128-SHA encrypted SMTP; 26 Mar 2014 23:08:43 -0000 Received: from mail200-ch1-R.bigfish.com (10.43.68.226) by CH1EHSOBE007.bigfish.com (10.43.70.57) with Microsoft SMTP Server id 14.1.225.22; Wed, 26 Mar 2014 23:08:41 +0000 Received: from mail200-ch1 (localhost [127.0.0.1]) by mail200-ch1-R.bigfish.com (Postfix) with ESMTP id 8CBCC4E0245; Wed, 26 Mar 2014 23:08:41 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -12 X-BigFish: VPS-12(zzbb2dI98dI9371IfecI542Ie0eah1432I1418I14e3M1447I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh25cch25f6h2605h262fh268bh9a9j1155h) Received-SPF: pass (mail200-ch1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rranjeet@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(13464003)(199002)(53474002)(189002)(51914003)(40764003)(51444003)(377454003)(53754006)(51704005)(24454002)(479174003)(95416001)(81342001)(74366001)(80022001)(69226001)(74706001)(74316001)(33646001)(19580395003)(77982001)(59766001)(65816001)(81542001)(15202345003)(94946001)(19580405001)(81686001)(66066001)(83322001)(83072002)(50986001)(80976001)(90146001)(56816005)(92566001)(94316002)(54356001)(54316002)(76482001)(74502001)(56776001)(46102001)(53806001)(87266001)(74662001)(15975445006)(31966008)(2656002)(47446002)(76786001)(95666003)(76576001)(93136001)(76796001)(97186001)(63696002)(86362001)(93516002)(20776003)(575784001)(98676001)(85852003)(81816001)(4396001)(49866001)(79102001)(85306002)(97336001)(74876001)(47736001)(47976001)(87936001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB709; H:BY2PR05MB711.namprd05.prod.outlook.com; FPR:DC3CF065.AF369871.71FB15E4.4199F681.2065D; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail200-ch1 (localhost.localdomain [127.0.0.1]) by mail200-ch1 (MessageSwitch) id 1395875318949747_21069; Wed, 26 Mar 2014 23:08:38 +0000 (UTC) Received: from CH1EHSMHS008.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.245]) by mail200-ch1.bigfish.com (Postfix) with ESMTP id D9F4546005B; Wed, 26 Mar 2014 23:08:38 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by CH1EHSMHS008.bigfish.com (10.43.70.8) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 26 Mar 2014 23:08:38 +0000 Received: from BY2PR05MB709.namprd05.prod.outlook.com (10.141.222.142) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Wed, 26 Mar 2014 23:08:33 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BY2PR05MB709.namprd05.prod.outlook.com (10.141.222.142) with Microsoft SMTP Server (TLS) id 15.0.898.11; Wed, 26 Mar 2014 23:08:24 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) by BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) with mapi id 15.00.0898.005; Wed, 26 Mar 2014 23:08:23 +0000 From: Ranjeet R To: Rob Hoes , Dave Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAjGnCAADsSOKAAFwBFAABOHF9wABh/GgAAF3zK4A== Date: Wed, 26 Mar 2014 23:08:22 +0000 Message-ID: References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> <53300CF4.1060402@eu.citrix.com> <360717C0B01E6345BCBE64B758E22C2D258185@AMSPEX01CL03.citrite.net> In-Reply-To: <360717C0B01E6345BCBE64B758E22C2D258185@AMSPEX01CL03.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.11] x-forefront-prvs: 0162ACCC24 MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello Rob/Dave Thanks for the pointers. I figured out the issue. The reason my C stub was able to list out all interfaces without crashing is - if (getifaddrs(&ifaddr) == -1) { print ("getifaddr failed"); exit(1); } struct ifaddrs *ifa = ifaddr; for (ifa = ifaddr; ifa != NULL; ifa = ifa->ifa_next) { --->>>> if (ifa->ifa_addr != NULL) { ------>> Check for ifa_addr int family = ifa->ifa_addr->sa_family; I was only looking into the ifaddrs structure only when the interface addr is set. In the stub_if_getaddr code, the code is as follows ret = getifaddrs(&ifaddrs); if (ret < 0) caml_failwith("cannot get interface address"); for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { sock = tmp->ifa_addr; ------------------------------>Assigned here netmask = tmp->ifa_netmask; if (sock->sa_family == AF_INET || sock->sa_family == AF_INET6) { -------------> Dereferenced here without checking name = caml_copy_string(tmp->ifa_name); In my case, there were two internal interfaces for which the interface address was not setup and while iterating through the list, there was a NULL pointer dereference. It might look like defensive coding but can we ignore the interfaces for which the ifa_addr is not set. I can open up a bug and fix it if there is consenus that this needs to be fixed. Ranjeet -----Original Message----- From: Rob Hoes [mailto:Rob.Hoes@citrix.com] Sent: Wednesday, March 26, 2014 4:44 AM To: Ranjeet R; Dave Scott Cc: xen-api@lists.xen.org Subject: RE: [Xen-API] Debugging XAPI daemon crash Hi Ranjeet, > It seems to be crashing in the same point as you had mentioned. Please > find the SEGV backtrace attached. > > (gdb) c > Program received signal SIGSEGV, Segmentation fault. > 0x085bc2d6 in stub_if_getaddr () > (gdb) bt > #0 0x085cca90 in segv_handler () > #1 > #2 0x085bc2d6 in stub_if_getaddr () > #3 0x0850ef8c in camlNetdev__get_all_ipv4_1325 () > > You had mentioned that this could be because of a bad C function binding. > I wrote a small C stub to see whether it works for the xenbr0 > interface and it seems to be working fine. How should I verify the binding. The function that is failing seems to be this one: https://github.com/xapi-project/xen-api-libs/blob/clearwater/netdev/addr_stubs.c#L74 It has: int ret; struct ifaddrs *ifaddrs, *tmp; [...] ret = getifaddrs(&ifaddrs); [...] for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { sock = tmp->ifa_addr; netmask = tmp->ifa_netmask; [...] Could it be that the getifaddrs function does not set ifaddrs correctly? You should be able to test this with a small C program. Or is this what you have already done? Cheers, Rob > Appreciate your help. > > -Ranjeet > > -----Original Message----- > From: David Scott [mailto:dave.scott@eu.citrix.com] > Sent: Monday, March 24, 2014 3:46 AM > To: Ranjeet R > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > On 24/03/14 10:30, Ranjeet R wrote: > > Hello Dave > > > > The binaries did not have debug symbols but I managed to rebuild the > binaries with debug enabled. > > Great. > > > I tried starting the xapi process as it was started in the init.d > scripts under gdb. However, in gdb, the xapi process forks another > process and I am not able to debug it further (I tried setting > detach_on_fork to off in gdb, but the primary process just goes to end of execution). > > > > I am using the following gdb command to debug > > > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete > /var/run/xapi_init_complete.cookie -writereadyfile > /var/run/xapi_startup.cookie -onsystemboot" > > > > Can you please help me in the steps that you use in debugging the > > XAPI > process. > > Ah, I think xapi forks a "watchdog" process near the start -- this is > probably what you're seeing. > > Try adding a "-nowatchdog" option to the command-line. > > Dave > > > > > Thanks for your help, > > > > -Ranjeet > > > > > > > > -----Original Message----- > > From: Dave Scott [mailto:Dave.Scott@citrix.com] > > Sent: Saturday, March 22, 2014 12:36 PM > > To: Ranjeet R > > Cc: xen-api@lists.xen.org > > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > > > Hi, > > > > I suspect the segfault is being caused by a bad C function binding. > > I've > seen a similar crash before when querying an interface IP via > getifaddrs (I think that was the function name) Could you run xapi in > gdb and reproduce the crash? Printing the call stack would help to > confirm this hypothesis. Provided the xapi binary still has debug > symbols (ie hasn't been stripped) the ocaml functions (with fairly > obvious mangled names) should also be on the stack too. > > > > Cheers, > > Dave > > > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: > >> > >> Hello all > >> > >> I am trying to bring a DevCloud setup which has an XCP Kronos based > XAPI daemon. I had changed the underlying network implementation (it > is not a bridge, but an openvswitch-like network implementation) and > the XAPI daemon crashes during bootup. Please find the XAPI logs below. > >> > >> > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > >> database to all active redo-logs starting up database engine > >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > >> database to all active redo-logs starting up database engine > >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync > >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost > >> dbsync > >> (update_env) D:fd0aec7399c9|dbsync] creating localhost > >> > >> dmesg logs seem to suggest that xapi is crashing during startup. > >> > >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error > 4 in xapi[8048000+59f000] > >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error > 4 in xapi[8048000+59f000] > >> > >> I looked the XAPI code to see where it fails and I don't see any > >> logs after the following code point in ocaml / xapi / > >> dbsync_slave.ml > >> > >> let create_localhost ~__context info = > >> let ip = get_my_ip_addr ~__context in > >> > >> I confirmed to see that "ifconfig xenbr0" has a valid management IP > address and should not fail. > >> > >> How do I debug this crash further. Are there any ways to look at > >> the > stack trace where XAPI crashed. Any pointers to debug this further > will be very helpful. > >> > >> -Ranjeet > >> > >> > >> _______________________________________________ > >> Xen-api mailing list > >> Xen-api@lists.xen.org > >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > > > > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Wed Mar 26 23:09:08 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 26 Mar 2014 23:09:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSwwA-0007jy-60; Wed, 26 Mar 2014 23:08:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WSww9-0007jg-4v for xen-api@lists.xen.org; Wed, 26 Mar 2014 23:08:45 +0000 Received: from [85.158.139.211:10773] by server-9.bemta-5.messagelabs.com id 43/80-04350-CFD53335; Wed, 26 Mar 2014 23:08:44 +0000 X-Env-Sender: rranjeet@juniper.net X-Msg-Ref: server-8.tower-206.messagelabs.com!1395875322!3380479!1 X-Originating-IP: [216.32.181.185] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29130 invoked from network); 26 Mar 2014 23:08:43 -0000 Received: from ch1ehsobe005.messaging.microsoft.com (HELO ch1outboundpool.messaging.microsoft.com) (216.32.181.185) by server-8.tower-206.messagelabs.com with AES128-SHA encrypted SMTP; 26 Mar 2014 23:08:43 -0000 Received: from mail200-ch1-R.bigfish.com (10.43.68.226) by CH1EHSOBE007.bigfish.com (10.43.70.57) with Microsoft SMTP Server id 14.1.225.22; Wed, 26 Mar 2014 23:08:41 +0000 Received: from mail200-ch1 (localhost [127.0.0.1]) by mail200-ch1-R.bigfish.com (Postfix) with ESMTP id 8CBCC4E0245; Wed, 26 Mar 2014 23:08:41 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -12 X-BigFish: VPS-12(zzbb2dI98dI9371IfecI542Ie0eah1432I1418I14e3M1447I14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh25cch25f6h2605h262fh268bh9a9j1155h) Received-SPF: pass (mail200-ch1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rranjeet@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(428001)(13464003)(199002)(53474002)(189002)(51914003)(40764003)(51444003)(377454003)(53754006)(51704005)(24454002)(479174003)(95416001)(81342001)(74366001)(80022001)(69226001)(74706001)(74316001)(33646001)(19580395003)(77982001)(59766001)(65816001)(81542001)(15202345003)(94946001)(19580405001)(81686001)(66066001)(83322001)(83072002)(50986001)(80976001)(90146001)(56816005)(92566001)(94316002)(54356001)(54316002)(76482001)(74502001)(56776001)(46102001)(53806001)(87266001)(74662001)(15975445006)(31966008)(2656002)(47446002)(76786001)(95666003)(76576001)(93136001)(76796001)(97186001)(63696002)(86362001)(93516002)(20776003)(575784001)(98676001)(85852003)(81816001)(4396001)(49866001)(79102001)(85306002)(97336001)(74876001)(47736001)(47976001)(87936001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR05MB709; H:BY2PR05MB711.namprd05.prod.outlook.com; FPR:DC3CF065.AF369871.71FB15E4.4199F681.2065D; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail200-ch1 (localhost.localdomain [127.0.0.1]) by mail200-ch1 (MessageSwitch) id 1395875318949747_21069; Wed, 26 Mar 2014 23:08:38 +0000 (UTC) Received: from CH1EHSMHS008.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.245]) by mail200-ch1.bigfish.com (Postfix) with ESMTP id D9F4546005B; Wed, 26 Mar 2014 23:08:38 +0000 (UTC) Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by CH1EHSMHS008.bigfish.com (10.43.70.8) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 26 Mar 2014 23:08:38 +0000 Received: from BY2PR05MB709.namprd05.prod.outlook.com (10.141.222.142) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.423.0; Wed, 26 Mar 2014 23:08:33 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com (10.141.222.149) by BY2PR05MB709.namprd05.prod.outlook.com (10.141.222.142) with Microsoft SMTP Server (TLS) id 15.0.898.11; Wed, 26 Mar 2014 23:08:24 +0000 Received: from BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) by BY2PR05MB711.namprd05.prod.outlook.com ([10.141.222.149]) with mapi id 15.00.0898.005; Wed, 26 Mar 2014 23:08:23 +0000 From: Ranjeet R To: Rob Hoes , Dave Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAjGnCAADsSOKAAFwBFAABOHF9wABh/GgAAF3zK4A== Date: Wed, 26 Mar 2014 23:08:22 +0000 Message-ID: References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> <53300CF4.1060402@eu.citrix.com> <360717C0B01E6345BCBE64B758E22C2D258185@AMSPEX01CL03.citrite.net> In-Reply-To: <360717C0B01E6345BCBE64B758E22C2D258185@AMSPEX01CL03.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.129.239.11] x-forefront-prvs: 0162ACCC24 MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello Rob/Dave Thanks for the pointers. I figured out the issue. The reason my C stub was able to list out all interfaces without crashing is - if (getifaddrs(&ifaddr) == -1) { print ("getifaddr failed"); exit(1); } struct ifaddrs *ifa = ifaddr; for (ifa = ifaddr; ifa != NULL; ifa = ifa->ifa_next) { --->>>> if (ifa->ifa_addr != NULL) { ------>> Check for ifa_addr int family = ifa->ifa_addr->sa_family; I was only looking into the ifaddrs structure only when the interface addr is set. In the stub_if_getaddr code, the code is as follows ret = getifaddrs(&ifaddrs); if (ret < 0) caml_failwith("cannot get interface address"); for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { sock = tmp->ifa_addr; ------------------------------>Assigned here netmask = tmp->ifa_netmask; if (sock->sa_family == AF_INET || sock->sa_family == AF_INET6) { -------------> Dereferenced here without checking name = caml_copy_string(tmp->ifa_name); In my case, there were two internal interfaces for which the interface address was not setup and while iterating through the list, there was a NULL pointer dereference. It might look like defensive coding but can we ignore the interfaces for which the ifa_addr is not set. I can open up a bug and fix it if there is consenus that this needs to be fixed. Ranjeet -----Original Message----- From: Rob Hoes [mailto:Rob.Hoes@citrix.com] Sent: Wednesday, March 26, 2014 4:44 AM To: Ranjeet R; Dave Scott Cc: xen-api@lists.xen.org Subject: RE: [Xen-API] Debugging XAPI daemon crash Hi Ranjeet, > It seems to be crashing in the same point as you had mentioned. Please > find the SEGV backtrace attached. > > (gdb) c > Program received signal SIGSEGV, Segmentation fault. > 0x085bc2d6 in stub_if_getaddr () > (gdb) bt > #0 0x085cca90 in segv_handler () > #1 > #2 0x085bc2d6 in stub_if_getaddr () > #3 0x0850ef8c in camlNetdev__get_all_ipv4_1325 () > > You had mentioned that this could be because of a bad C function binding. > I wrote a small C stub to see whether it works for the xenbr0 > interface and it seems to be working fine. How should I verify the binding. The function that is failing seems to be this one: https://github.com/xapi-project/xen-api-libs/blob/clearwater/netdev/addr_stubs.c#L74 It has: int ret; struct ifaddrs *ifaddrs, *tmp; [...] ret = getifaddrs(&ifaddrs); [...] for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { sock = tmp->ifa_addr; netmask = tmp->ifa_netmask; [...] Could it be that the getifaddrs function does not set ifaddrs correctly? You should be able to test this with a small C program. Or is this what you have already done? Cheers, Rob > Appreciate your help. > > -Ranjeet > > -----Original Message----- > From: David Scott [mailto:dave.scott@eu.citrix.com] > Sent: Monday, March 24, 2014 3:46 AM > To: Ranjeet R > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > On 24/03/14 10:30, Ranjeet R wrote: > > Hello Dave > > > > The binaries did not have debug symbols but I managed to rebuild the > binaries with debug enabled. > > Great. > > > I tried starting the xapi process as it was started in the init.d > scripts under gdb. However, in gdb, the xapi process forks another > process and I am not able to debug it further (I tried setting > detach_on_fork to off in gdb, but the primary process just goes to end of execution). > > > > I am using the following gdb command to debug > > > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete > /var/run/xapi_init_complete.cookie -writereadyfile > /var/run/xapi_startup.cookie -onsystemboot" > > > > Can you please help me in the steps that you use in debugging the > > XAPI > process. > > Ah, I think xapi forks a "watchdog" process near the start -- this is > probably what you're seeing. > > Try adding a "-nowatchdog" option to the command-line. > > Dave > > > > > Thanks for your help, > > > > -Ranjeet > > > > > > > > -----Original Message----- > > From: Dave Scott [mailto:Dave.Scott@citrix.com] > > Sent: Saturday, March 22, 2014 12:36 PM > > To: Ranjeet R > > Cc: xen-api@lists.xen.org > > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > > > Hi, > > > > I suspect the segfault is being caused by a bad C function binding. > > I've > seen a similar crash before when querying an interface IP via > getifaddrs (I think that was the function name) Could you run xapi in > gdb and reproduce the crash? Printing the call stack would help to > confirm this hypothesis. Provided the xapi binary still has debug > symbols (ie hasn't been stripped) the ocaml functions (with fairly > obvious mangled names) should also be on the stack too. > > > > Cheers, > > Dave > > > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" wrote: > >> > >> Hello all > >> > >> I am trying to bring a DevCloud setup which has an XCP Kronos based > XAPI daemon. I had changed the underlying network implementation (it > is not a bridge, but an openvswitch-like network implementation) and > the XAPI daemon crashes during bootup. Please find the XAPI logs below. > >> > >> > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > >> database to all active redo-logs starting up database engine > >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > >> database to all active redo-logs starting up database engine > >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync > >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost > >> dbsync > >> (update_env) D:fd0aec7399c9|dbsync] creating localhost > >> > >> dmesg logs seem to suggest that xapi is crashing during startup. > >> > >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 error > 4 in xapi[8048000+59f000] > >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 error > 4 in xapi[8048000+59f000] > >> > >> I looked the XAPI code to see where it fails and I don't see any > >> logs after the following code point in ocaml / xapi / > >> dbsync_slave.ml > >> > >> let create_localhost ~__context info = > >> let ip = get_my_ip_addr ~__context in > >> > >> I confirmed to see that "ifconfig xenbr0" has a valid management IP > address and should not fail. > >> > >> How do I debug this crash further. Are there any ways to look at > >> the > stack trace where XAPI crashed. Any pointers to debug this further > will be very helpful. > >> > >> -Ranjeet > >> > >> > >> _______________________________________________ > >> Xen-api mailing list > >> Xen-api@lists.xen.org > >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > > > > > > > > > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Mar 27 10:15:54 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 10:15:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WT7LU-0003ic-MN; Thu, 27 Mar 2014 10:15:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WT7LS-0003iO-Hn for xen-api@lists.xen.org; Thu, 27 Mar 2014 10:15:34 +0000 Received: from [85.158.137.68:60767] by server-14.bemta-3.messagelabs.com id E8/0F-30903-54AF3335; Thu, 27 Mar 2014 10:15:33 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1395915332!3258619!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28372 invoked from network); 27 Mar 2014 10:15:32 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 10:15:32 -0000 X-IronPort-AV: E=Sophos;i="4.97,741,1389744000"; d="scan'208";a="12556580" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 27 Mar 2014 10:15:32 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.213]) by AMSPEX01CL02.citrite.net ([169.254.7.78]) with mapi id 14.02.0342.004; Thu, 27 Mar 2014 11:15:32 +0100 From: Rob Hoes To: 'Ranjeet R' , Dave Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAhAf+AAFGC/oAAAI9/AABWxcIAABGwNkAAFgq6AAAYbmrw Date: Thu, 27 Mar 2014 10:15:31 +0000 Message-ID: <360717C0B01E6345BCBE64B758E22C2D293497@AMSPEX01CL03.citrite.net> References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> <53300CF4.1060402@eu.citrix.com> <360717C0B01E6345BCBE64B758E22C2D258185@AMSPEX01CL03.citrite.net> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.46] MIME-Version: 1.0 X-DLP: AMS1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Ranjeet, That makes sense. I guess the same would apply to the ifa_netmask field. The following lines would blow up if it is NULL: netmask = tmp->ifa_netmask; [...] netmaskstr = alloc_addr(netmask); because alloc_addr will try to access netmask->sa_family. So to be on the safe side, I think we should check for this as well. I think defensive coding is the right way (I hate segfaults)! For the purpose of the stub_if_addr function, I think it is sufficient to wrap the existing if-block with "if (sock && netmask)". This assumes that we always want both the address and the netmask, and we ignore the interface if either is undefined. The master branch for this code is here (since we split it off from xen-api-libs): https://github.com/xapi-project/netdev/blob/master/lib/addr_stubs.c. If you'd like to submit a pull request there (as well as keeping the fix in your development branch on clearwater), that would be great. Thanks, Rob > -----Original Message----- > From: Ranjeet R [mailto:rranjeet@juniper.net] > Sent: 26 March 2014 11:08 PM > To: Rob Hoes; Dave Scott > Cc: xen-api@lists.xen.org > Subject: RE: [Xen-API] Debugging XAPI daemon crash > > Hello Rob/Dave > > Thanks for the pointers. I figured out the issue. The reason my C stub was > able to list out all interfaces without crashing is - > > if (getifaddrs(&ifaddr) == -1) { > print ("getifaddr failed"); > exit(1); > } > > struct ifaddrs *ifa = ifaddr; > for (ifa = ifaddr; ifa != NULL; ifa = ifa->ifa_next) { > --->>>> if (ifa->ifa_addr != NULL) { ------>> Check for ifa_addr > int family = ifa->ifa_addr->sa_family; > > I was only looking into the ifaddrs structure only when the interface addr > is set. > > In the stub_if_getaddr code, the code is as follows > > ret = getifaddrs(&ifaddrs); > if (ret < 0) > caml_failwith("cannot get interface address"); > > for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { > sock = tmp->ifa_addr; ------------------------------>Assigned here > netmask = tmp->ifa_netmask; > > if (sock->sa_family == AF_INET || sock->sa_family == AF_INET6) > { -------------> Dereferenced here without checking > name = caml_copy_string(tmp->ifa_name); > > In my case, there were two internal interfaces for which the interface > address was not setup and while iterating through the list, there was a > NULL pointer dereference. > > It might look like defensive coding but can we ignore the interfaces for > which the ifa_addr is not set. I can open up a bug and fix it if there is > consenus that this needs to be fixed. > > Ranjeet > > > -----Original Message----- > From: Rob Hoes [mailto:Rob.Hoes@citrix.com] > Sent: Wednesday, March 26, 2014 4:44 AM > To: Ranjeet R; Dave Scott > Cc: xen-api@lists.xen.org > Subject: RE: [Xen-API] Debugging XAPI daemon crash > > Hi Ranjeet, > > > It seems to be crashing in the same point as you had mentioned. Please > > find the SEGV backtrace attached. > > > > (gdb) c > > Program received signal SIGSEGV, Segmentation fault. > > 0x085bc2d6 in stub_if_getaddr () > > (gdb) bt > > #0 0x085cca90 in segv_handler () > > #1 > > #2 0x085bc2d6 in stub_if_getaddr () > > #3 0x0850ef8c in camlNetdev__get_all_ipv4_1325 () > > > > You had mentioned that this could be because of a bad C function binding. > > I wrote a small C stub to see whether it works for the xenbr0 > > interface and it seems to be working fine. How should I verify the > binding. > > The function that is failing seems to be this one: > https://github.com/xapi-project/xen-api- > libs/blob/clearwater/netdev/addr_stubs.c#L74 > > It has: > > int ret; > struct ifaddrs *ifaddrs, *tmp; > [...] > ret = getifaddrs(&ifaddrs); > [...] > for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { > sock = tmp->ifa_addr; > netmask = tmp->ifa_netmask; > [...] > > Could it be that the getifaddrs function does not set ifaddrs correctly? > You should be able to test this with a small C program. Or is this what > you have already done? > > Cheers, > Rob > > > Appreciate your help. > > > > -Ranjeet > > > > -----Original Message----- > > From: David Scott [mailto:dave.scott@eu.citrix.com] > > Sent: Monday, March 24, 2014 3:46 AM > > To: Ranjeet R > > Cc: xen-api@lists.xen.org > > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > > > On 24/03/14 10:30, Ranjeet R wrote: > > > Hello Dave > > > > > > The binaries did not have debug symbols but I managed to rebuild the > > binaries with debug enabled. > > > > Great. > > > > > I tried starting the xapi process as it was started in the init.d > > scripts under gdb. However, in gdb, the xapi process forks another > > process and I am not able to debug it further (I tried setting > > detach_on_fork to off in gdb, but the primary process just goes to end > of execution). > > > > > > I am using the following gdb command to debug > > > > > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete > > /var/run/xapi_init_complete.cookie -writereadyfile > > /var/run/xapi_startup.cookie -onsystemboot" > > > > > > Can you please help me in the steps that you use in debugging the > > > XAPI > > process. > > > > Ah, I think xapi forks a "watchdog" process near the start -- this is > > probably what you're seeing. > > > > Try adding a "-nowatchdog" option to the command-line. > > > > Dave > > > > > > > > Thanks for your help, > > > > > > -Ranjeet > > > > > > > > > > > > -----Original Message----- > > > From: Dave Scott [mailto:Dave.Scott@citrix.com] > > > Sent: Saturday, March 22, 2014 12:36 PM > > > To: Ranjeet R > > > Cc: xen-api@lists.xen.org > > > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > > > > > Hi, > > > > > > I suspect the segfault is being caused by a bad C function binding. > > > I've > > seen a similar crash before when querying an interface IP via > > getifaddrs (I think that was the function name) Could you run xapi in > > gdb and reproduce the crash? Printing the call stack would help to > > confirm this hypothesis. Provided the xapi binary still has debug > > symbols (ie hasn't been stripped) the ocaml functions (with fairly > > obvious mangled names) should also be on the stack too. > > > > > > Cheers, > > > Dave > > > > > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" > wrote: > > >> > > >> Hello all > > >> > > >> I am trying to bring a DevCloud setup which has an XCP Kronos based > > XAPI daemon. I had changed the underlying network implementation (it > > is not a bridge, but an openvswitch-like network implementation) and > > the XAPI daemon crashes during bootup. Please find the XAPI logs below. > > >> > > >> > > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > > >> database to all active redo-logs starting up database engine > > >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > > >> database to all active redo-logs starting up database engine > > >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync > > >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost > > >> dbsync > > >> (update_env) D:fd0aec7399c9|dbsync] creating localhost > > >> > > >> dmesg logs seem to suggest that xapi is crashing during startup. > > >> > > >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 > error > > 4 in xapi[8048000+59f000] > > >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 > error > > 4 in xapi[8048000+59f000] > > >> > > >> I looked the XAPI code to see where it fails and I don't see any > > >> logs after the following code point in ocaml / xapi / > > >> dbsync_slave.ml > > >> > > >> let create_localhost ~__context info = > > >> let ip = get_my_ip_addr ~__context in > > >> > > >> I confirmed to see that "ifconfig xenbr0" has a valid management IP > > address and should not fail. > > >> > > >> How do I debug this crash further. Are there any ways to look at > > >> the > > stack trace where XAPI crashed. Any pointers to debug this further > > will be very helpful. > > >> > > >> -Ranjeet > > >> > > >> > > >> _______________________________________________ > > >> Xen-api mailing list > > >> Xen-api@lists.xen.org > > >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > Xen-api mailing list > > Xen-api@lists.xen.org > > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Mar 27 10:15:54 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 10:15:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WT7LU-0003ic-MN; Thu, 27 Mar 2014 10:15:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WT7LS-0003iO-Hn for xen-api@lists.xen.org; Thu, 27 Mar 2014 10:15:34 +0000 Received: from [85.158.137.68:60767] by server-14.bemta-3.messagelabs.com id E8/0F-30903-54AF3335; Thu, 27 Mar 2014 10:15:33 +0000 X-Env-Sender: Rob.Hoes@citrix.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1395915332!3258619!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28372 invoked from network); 27 Mar 2014 10:15:32 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 10:15:32 -0000 X-IronPort-AV: E=Sophos;i="4.97,741,1389744000"; d="scan'208";a="12556580" Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9]) by AMSPIP01.EU.Citrix.com with ESMTP; 27 Mar 2014 10:15:32 +0000 Received: from AMSPEX01CL03.citrite.net ([169.254.8.213]) by AMSPEX01CL02.citrite.net ([169.254.7.78]) with mapi id 14.02.0342.004; Thu, 27 Mar 2014 11:15:32 +0100 From: Rob Hoes To: 'Ranjeet R' , Dave Scott Thread-Topic: [Xen-API] Debugging XAPI daemon crash Thread-Index: Ac9FeZIEEGyvK3fqS5+yO9kiSTP+fwAhAf+AAFGC/oAAAI9/AABWxcIAABGwNkAAFgq6AAAYbmrw Date: Thu, 27 Mar 2014 10:15:31 +0000 Message-ID: <360717C0B01E6345BCBE64B758E22C2D293497@AMSPEX01CL03.citrite.net> References: <12523b35d4664c48a5b87e5761dde914@BY2PR05MB711.namprd05.prod.outlook.com> <824AE475-FBB7-4B45-88B0-F4A8A46BEEC9@eu.citrix.com> <6be5009efa7840d789040c9bf5641d1e@BY2PR05MB711.namprd05.prod.outlook.com> <53300CF4.1060402@eu.citrix.com> <360717C0B01E6345BCBE64B758E22C2D258185@AMSPEX01CL03.citrite.net> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.46] MIME-Version: 1.0 X-DLP: AMS1 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Debugging XAPI daemon crash X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Ranjeet, That makes sense. I guess the same would apply to the ifa_netmask field. The following lines would blow up if it is NULL: netmask = tmp->ifa_netmask; [...] netmaskstr = alloc_addr(netmask); because alloc_addr will try to access netmask->sa_family. So to be on the safe side, I think we should check for this as well. I think defensive coding is the right way (I hate segfaults)! For the purpose of the stub_if_addr function, I think it is sufficient to wrap the existing if-block with "if (sock && netmask)". This assumes that we always want both the address and the netmask, and we ignore the interface if either is undefined. The master branch for this code is here (since we split it off from xen-api-libs): https://github.com/xapi-project/netdev/blob/master/lib/addr_stubs.c. If you'd like to submit a pull request there (as well as keeping the fix in your development branch on clearwater), that would be great. Thanks, Rob > -----Original Message----- > From: Ranjeet R [mailto:rranjeet@juniper.net] > Sent: 26 March 2014 11:08 PM > To: Rob Hoes; Dave Scott > Cc: xen-api@lists.xen.org > Subject: RE: [Xen-API] Debugging XAPI daemon crash > > Hello Rob/Dave > > Thanks for the pointers. I figured out the issue. The reason my C stub was > able to list out all interfaces without crashing is - > > if (getifaddrs(&ifaddr) == -1) { > print ("getifaddr failed"); > exit(1); > } > > struct ifaddrs *ifa = ifaddr; > for (ifa = ifaddr; ifa != NULL; ifa = ifa->ifa_next) { > --->>>> if (ifa->ifa_addr != NULL) { ------>> Check for ifa_addr > int family = ifa->ifa_addr->sa_family; > > I was only looking into the ifaddrs structure only when the interface addr > is set. > > In the stub_if_getaddr code, the code is as follows > > ret = getifaddrs(&ifaddrs); > if (ret < 0) > caml_failwith("cannot get interface address"); > > for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { > sock = tmp->ifa_addr; ------------------------------>Assigned here > netmask = tmp->ifa_netmask; > > if (sock->sa_family == AF_INET || sock->sa_family == AF_INET6) > { -------------> Dereferenced here without checking > name = caml_copy_string(tmp->ifa_name); > > In my case, there were two internal interfaces for which the interface > address was not setup and while iterating through the list, there was a > NULL pointer dereference. > > It might look like defensive coding but can we ignore the interfaces for > which the ifa_addr is not set. I can open up a bug and fix it if there is > consenus that this needs to be fixed. > > Ranjeet > > > -----Original Message----- > From: Rob Hoes [mailto:Rob.Hoes@citrix.com] > Sent: Wednesday, March 26, 2014 4:44 AM > To: Ranjeet R; Dave Scott > Cc: xen-api@lists.xen.org > Subject: RE: [Xen-API] Debugging XAPI daemon crash > > Hi Ranjeet, > > > It seems to be crashing in the same point as you had mentioned. Please > > find the SEGV backtrace attached. > > > > (gdb) c > > Program received signal SIGSEGV, Segmentation fault. > > 0x085bc2d6 in stub_if_getaddr () > > (gdb) bt > > #0 0x085cca90 in segv_handler () > > #1 > > #2 0x085bc2d6 in stub_if_getaddr () > > #3 0x0850ef8c in camlNetdev__get_all_ipv4_1325 () > > > > You had mentioned that this could be because of a bad C function binding. > > I wrote a small C stub to see whether it works for the xenbr0 > > interface and it seems to be working fine. How should I verify the > binding. > > The function that is failing seems to be this one: > https://github.com/xapi-project/xen-api- > libs/blob/clearwater/netdev/addr_stubs.c#L74 > > It has: > > int ret; > struct ifaddrs *ifaddrs, *tmp; > [...] > ret = getifaddrs(&ifaddrs); > [...] > for (tmp = ifaddrs; tmp; tmp = tmp->ifa_next) { > sock = tmp->ifa_addr; > netmask = tmp->ifa_netmask; > [...] > > Could it be that the getifaddrs function does not set ifaddrs correctly? > You should be able to test this with a small C program. Or is this what > you have already done? > > Cheers, > Rob > > > Appreciate your help. > > > > -Ranjeet > > > > -----Original Message----- > > From: David Scott [mailto:dave.scott@eu.citrix.com] > > Sent: Monday, March 24, 2014 3:46 AM > > To: Ranjeet R > > Cc: xen-api@lists.xen.org > > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > > > On 24/03/14 10:30, Ranjeet R wrote: > > > Hello Dave > > > > > > The binaries did not have debug symbols but I managed to rebuild the > > binaries with debug enabled. > > > > Great. > > > > > I tried starting the xapi process as it was started in the init.d > > scripts under gdb. However, in gdb, the xapi process forks another > > process and I am not able to debug it further (I tried setting > > detach_on_fork to off in gdb, but the primary process just goes to end > of execution). > > > > > > I am using the following gdb command to debug > > > > > > gdb --args /usr/sbin/xapi -daemon -writeinitcomplete > > /var/run/xapi_init_complete.cookie -writereadyfile > > /var/run/xapi_startup.cookie -onsystemboot" > > > > > > Can you please help me in the steps that you use in debugging the > > > XAPI > > process. > > > > Ah, I think xapi forks a "watchdog" process near the start -- this is > > probably what you're seeing. > > > > Try adding a "-nowatchdog" option to the command-line. > > > > Dave > > > > > > > > Thanks for your help, > > > > > > -Ranjeet > > > > > > > > > > > > -----Original Message----- > > > From: Dave Scott [mailto:Dave.Scott@citrix.com] > > > Sent: Saturday, March 22, 2014 12:36 PM > > > To: Ranjeet R > > > Cc: xen-api@lists.xen.org > > > Subject: Re: [Xen-API] Debugging XAPI daemon crash > > > > > > Hi, > > > > > > I suspect the segfault is being caused by a bad C function binding. > > > I've > > seen a similar crash before when querying an interface IP via > > getifaddrs (I think that was the function name) Could you run xapi in > > gdb and reproduce the crash? Printing the call stack would help to > > confirm this hypothesis. Provided the xapi binary still has debug > > symbols (ie hasn't been stripped) the ocaml functions (with fairly > > obvious mangled names) should also be on the stack too. > > > > > > Cheers, > > > Dave > > > > > >> On Mar 22, 2014, at 3:47 AM, "Ranjeet R" > wrote: > > >> > > >> Hello all > > >> > > >> I am trying to bring a DevCloud setup which has an XCP Kronos based > > XAPI daemon. I had changed the underlying network implementation (it > > is not a bridge, but an openvswitch-like network implementation) and > > the XAPI daemon crashes during bootup. Please find the XAPI logs below. > > >> > > >> > > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > > >> database to all active redo-logs starting up database engine > > >> D:72969b3eaf8e|xapi] About to flush database: /var/lib/xcp/state.db > > >> starting up database engine D:72969b3eaf8e|redo_log] Flushing > > >> database to all active redo-logs starting up database engine > > >> D:72969b3eaf8e|xapi] Performing initial DB GC thread_zero|dbsync > > >> (update_env) D:fd0aec7399c9|dbsync] Sync: sync_create_localhost > > >> dbsync > > >> (update_env) D:fd0aec7399c9|dbsync] creating localhost > > >> > > >> dmesg logs seem to suggest that xapi is crashing during startup. > > >> > > >> [ 9.092377] xapi[2813]: segfault at 0 ip 085bc286 sp bf80ae30 > error > > 4 in xapi[8048000+59f000] > > >> [ 9.869971] xapi[2943]: segfault at 0 ip 085bc286 sp bf8ec450 > error > > 4 in xapi[8048000+59f000] > > >> > > >> I looked the XAPI code to see where it fails and I don't see any > > >> logs after the following code point in ocaml / xapi / > > >> dbsync_slave.ml > > >> > > >> let create_localhost ~__context info = > > >> let ip = get_my_ip_addr ~__context in > > >> > > >> I confirmed to see that "ifconfig xenbr0" has a valid management IP > > address and should not fail. > > >> > > >> How do I debug this crash further. Are there any ways to look at > > >> the > > stack trace where XAPI crashed. Any pointers to debug this further > > will be very helpful. > > >> > > >> -Ranjeet > > >> > > >> > > >> _______________________________________________ > > >> Xen-api mailing list > > >> Xen-api@lists.xen.org > > >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > Xen-api mailing list > > Xen-api@lists.xen.org > > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Mar 27 14:36:14 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 14:36:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTBPP-0007i1-SA; Thu, 27 Mar 2014 14:35:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTBPO-0007hV-Hj; Thu, 27 Mar 2014 14:35:54 +0000 Received: from [85.158.139.211:41857] by server-3.bemta-5.messagelabs.com id 20/E1-28132-94734335; Thu, 27 Mar 2014 14:35:53 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1395930952!3783856!1 X-Originating-IP: [209.85.215.52] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12686 invoked from network); 27 Mar 2014 14:35:52 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 14:35:52 -0000 Received: by mail-la0-f52.google.com with SMTP id ec20so2711468lab.11 for ; Thu, 27 Mar 2014 07:35:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=x0W/InCuGu1j0jEp2ZuVdJu5D1o4DiGS0Aj0AkCMUw0=; b=JfXSy0YnnfpBkkmRg8FfVfKbVCNtthPb7YlIa8FDps9owlLBn1HJqxwtk+UjpC88b5 cU0rYVnNr8gCo+G+DpGTMbX+h3m8esINwD/aPEuoTv+TFdW4qiQ3y0kVDfmgWjcmHuOy fsK5BCAifxeWfk0Nea2r+0VQ0wvi+217UAP9E27x93cabOzRTB/cc4cN1vRE32PF8pOb cekd14edC0VIiD0nqSit8wPL5cUG6eFjMGuTjrsbO8DoKNIjjgJf4hme2FQTwgJ3Y7jr bbYxvkMT7+pQ6IbSSAKlWNZ0lpdSYi1s0PvypJnwI/wbnvCf7OyksGRrYtxiO74zoVXr V+yA== MIME-Version: 1.0 X-Received: by 10.112.85.6 with SMTP id d6mr1186481lbz.8.1395930951828; Thu, 27 Mar 2014 07:35:51 -0700 (PDT) Received: by 10.112.167.198 with HTTP; Thu, 27 Mar 2014 07:35:51 -0700 (PDT) Date: Thu, 27 Mar 2014 10:35:51 -0400 X-Google-Sender-Auth: VgsppEEoBJ1UEXjheJpMEtnshhc Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, cl-mirage@lists.cam.ac.uk, xs-devel@lists.xenserver.org, xen-api@lists.xen.org Subject: [Xen-API] Xen Project Documentation Day next Monday X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Remember that the next Xen Project Document Day will be held next Monday, March 31. Xen Project Document Day is a day to help improve overall Xen documentation, with emphasis on the Xen Project Wiki. With the new 4.4 release just issued, this is a perfect time to make sure that our docs reflect the latest features and enhancements of the code. Never participated in a Document Day before? All the info you'll need is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments in the next week and a half, please take a look at the current TODO list: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Add any documentation deficiencies you have come across while working with Xen. Is there a subject you wrestled with? That's a perfect opportunity for you to help shape the documentation into something more useful for the next person who needs it! So please think about how you can join in the action. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html See you in #xendocs on Monday! Russ _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Mar 27 14:36:14 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 14:36:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTBPP-0007i1-SA; Thu, 27 Mar 2014 14:35:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTBPO-0007hV-Hj; Thu, 27 Mar 2014 14:35:54 +0000 Received: from [85.158.139.211:41857] by server-3.bemta-5.messagelabs.com id 20/E1-28132-94734335; Thu, 27 Mar 2014 14:35:53 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1395930952!3783856!1 X-Originating-IP: [209.85.215.52] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12686 invoked from network); 27 Mar 2014 14:35:52 -0000 Received: from mail-la0-f52.google.com (HELO mail-la0-f52.google.com) (209.85.215.52) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 14:35:52 -0000 Received: by mail-la0-f52.google.com with SMTP id ec20so2711468lab.11 for ; Thu, 27 Mar 2014 07:35:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=x0W/InCuGu1j0jEp2ZuVdJu5D1o4DiGS0Aj0AkCMUw0=; b=JfXSy0YnnfpBkkmRg8FfVfKbVCNtthPb7YlIa8FDps9owlLBn1HJqxwtk+UjpC88b5 cU0rYVnNr8gCo+G+DpGTMbX+h3m8esINwD/aPEuoTv+TFdW4qiQ3y0kVDfmgWjcmHuOy fsK5BCAifxeWfk0Nea2r+0VQ0wvi+217UAP9E27x93cabOzRTB/cc4cN1vRE32PF8pOb cekd14edC0VIiD0nqSit8wPL5cUG6eFjMGuTjrsbO8DoKNIjjgJf4hme2FQTwgJ3Y7jr bbYxvkMT7+pQ6IbSSAKlWNZ0lpdSYi1s0PvypJnwI/wbnvCf7OyksGRrYtxiO74zoVXr V+yA== MIME-Version: 1.0 X-Received: by 10.112.85.6 with SMTP id d6mr1186481lbz.8.1395930951828; Thu, 27 Mar 2014 07:35:51 -0700 (PDT) Received: by 10.112.167.198 with HTTP; Thu, 27 Mar 2014 07:35:51 -0700 (PDT) Date: Thu, 27 Mar 2014 10:35:51 -0400 X-Google-Sender-Auth: VgsppEEoBJ1UEXjheJpMEtnshhc Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, cl-mirage@lists.cam.ac.uk, xs-devel@lists.xenserver.org, xen-api@lists.xen.org Subject: [Xen-API] Xen Project Documentation Day next Monday X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Remember that the next Xen Project Document Day will be held next Monday, March 31. Xen Project Document Day is a day to help improve overall Xen documentation, with emphasis on the Xen Project Wiki. With the new 4.4 release just issued, this is a perfect time to make sure that our docs reflect the latest features and enhancements of the code. Never participated in a Document Day before? All the info you'll need is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments in the next week and a half, please take a look at the current TODO list: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO Add any documentation deficiencies you have come across while working with Xen. Is there a subject you wrestled with? That's a perfect opportunity for you to help shape the documentation into something more useful for the next person who needs it! So please think about how you can join in the action. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html See you in #xendocs on Monday! Russ _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Mar 27 14:59:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 14:59:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTBmJ-0001yP-QH; Thu, 27 Mar 2014 14:59:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTBmI-0001xk-29; Thu, 27 Mar 2014 14:59:34 +0000 Received: from [193.109.254.147:40939] by server-9.bemta-14.messagelabs.com id 30/E4-03644-5DC34335; Thu, 27 Mar 2014 14:59:33 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1395932372!4546225!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10920 invoked from network); 27 Mar 2014 14:59:32 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 14:59:32 -0000 Received: by mail-wi0-f174.google.com with SMTP id d1so6070886wiv.13 for ; Thu, 27 Mar 2014 07:59:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=8v6ZjgyN+iGhnwF8/dmZVHKLFlYuY9sSuFviic1wFSc=; b=dMbsOQOpIFir/xcr7iNKM6Xe/uUBHuSaNcoZQed88iFt4iYLQz3BLFUFFLj22wrBCQ +ZNrguB+WkVNZ+Rer0MecGMjMmUZyupMN9A/NcCt1jSaUkub8XbX2LggARgq9vOFxMgN YA+VWY4cM62qDKpn5WwOI/KDnAMaqispwcWCmBZWrMoo2h6JUJ/lxUZ3BNRyJ/MDEgek QIGdAuCXYoz0REzyHvR7rUwRq23bcueWKT9WdthPRecZRtz7EY24UcLWVkAGPIIZBJmA 6TYnRFmjDRIepP956rnScrglA9sasDmDv9+SjdYuD8M+ZifAdLyNi13ryhNRW1VGQ+hK Uppg== X-Received: by 10.180.12.115 with SMTP id x19mr40641811wib.19.1395932365750; Thu, 27 Mar 2014 07:59:25 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id mw3sm13053924wic.7.2014.03.27.07.59.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Mar 2014 07:59:24 -0700 (PDT) Message-ID: <53343CCB.8000008@xen.org> Date: Thu, 27 Mar 2014 14:59:23 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [Xen-API] Xen Project Hackathon - more information & trade-off X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I posted more information related to the Xen Project Hackathon at http://wiki.xenproject.org/wiki/Hackathon/May2014. Some of the locals have raised questions whether to stay in Paddington (and take a train to/from the venue) or whether to stay locally. Here is the trade-off you need to consider: * If you stay locally you are staying on the edge of London. Hayes is not dangerous, but it is a slightly industrial area. I was assured that the serviced apartments are nice. However, if you are looking to stay in a nice and vibrant neighbourhood, you probably want to stay in Paddington. * Staying in Ealing is a reasonable compromose. However note that Ealing is basically a leafy residential suburb of London. There are some places to do stuff at night, but not as much as in Paddington. * If you stay in Paddington, you are pretty much in the center of London and it is easy to get to there from Heathrow. You will need to take a train during the rush hour. However, as you go against the flow of the rush hour it should be pretty OK. But Paddington station itself will be rather busy. I added a drop down and free form field to the invitation request form, which allows you to tell us where you are planning to stay. If you fill this out, we will post the info on the wiki. But you may of course want to coordinate this amongst yourself. For the evening event on the 29th we will either do a BBQ next to Rackspace or use a venue near Paddington. We have not decided yet. This depends on overall costs. Best Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Mar 27 14:59:49 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 14:59:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTBmJ-0001yP-QH; Thu, 27 Mar 2014 14:59:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTBmI-0001xk-29; Thu, 27 Mar 2014 14:59:34 +0000 Received: from [193.109.254.147:40939] by server-9.bemta-14.messagelabs.com id 30/E4-03644-5DC34335; Thu, 27 Mar 2014 14:59:33 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1395932372!4546225!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10920 invoked from network); 27 Mar 2014 14:59:32 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 14:59:32 -0000 Received: by mail-wi0-f174.google.com with SMTP id d1so6070886wiv.13 for ; Thu, 27 Mar 2014 07:59:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=8v6ZjgyN+iGhnwF8/dmZVHKLFlYuY9sSuFviic1wFSc=; b=dMbsOQOpIFir/xcr7iNKM6Xe/uUBHuSaNcoZQed88iFt4iYLQz3BLFUFFLj22wrBCQ +ZNrguB+WkVNZ+Rer0MecGMjMmUZyupMN9A/NcCt1jSaUkub8XbX2LggARgq9vOFxMgN YA+VWY4cM62qDKpn5WwOI/KDnAMaqispwcWCmBZWrMoo2h6JUJ/lxUZ3BNRyJ/MDEgek QIGdAuCXYoz0REzyHvR7rUwRq23bcueWKT9WdthPRecZRtz7EY24UcLWVkAGPIIZBJmA 6TYnRFmjDRIepP956rnScrglA9sasDmDv9+SjdYuD8M+ZifAdLyNi13ryhNRW1VGQ+hK Uppg== X-Received: by 10.180.12.115 with SMTP id x19mr40641811wib.19.1395932365750; Thu, 27 Mar 2014 07:59:25 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id mw3sm13053924wic.7.2014.03.27.07.59.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Mar 2014 07:59:24 -0700 (PDT) Message-ID: <53343CCB.8000008@xen.org> Date: Thu, 27 Mar 2014 14:59:23 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [Xen-API] Xen Project Hackathon - more information & trade-off X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi all, I posted more information related to the Xen Project Hackathon at http://wiki.xenproject.org/wiki/Hackathon/May2014. Some of the locals have raised questions whether to stay in Paddington (and take a train to/from the venue) or whether to stay locally. Here is the trade-off you need to consider: * If you stay locally you are staying on the edge of London. Hayes is not dangerous, but it is a slightly industrial area. I was assured that the serviced apartments are nice. However, if you are looking to stay in a nice and vibrant neighbourhood, you probably want to stay in Paddington. * Staying in Ealing is a reasonable compromose. However note that Ealing is basically a leafy residential suburb of London. There are some places to do stuff at night, but not as much as in Paddington. * If you stay in Paddington, you are pretty much in the center of London and it is easy to get to there from Heathrow. You will need to take a train during the rush hour. However, as you go against the flow of the rush hour it should be pretty OK. But Paddington station itself will be rather busy. I added a drop down and free form field to the invitation request form, which allows you to tell us where you are planning to stay. If you fill this out, we will post the info on the wiki. But you may of course want to coordinate this amongst yourself. For the evening event on the 29th we will either do a BBQ next to Rackspace or use a venue near Paddington. We have not decided yet. This depends on overall costs. Best Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Thu Mar 27 16:25:05 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 16:25:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTD6l-0006NF-0P; Thu, 27 Mar 2014 16:24:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTD6j-0006My-7l for xen-api@lists.xen.org; Thu, 27 Mar 2014 16:24:45 +0000 Received: from [193.109.254.147:59739] by server-10.bemta-14.messagelabs.com id F4/F6-04546-BC054335; Thu, 27 Mar 2014 16:24:43 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1395937479!4599459!1 X-Originating-IP: [74.125.82.179] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27706 invoked from network); 27 Mar 2014 16:24:40 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 16:24:40 -0000 Received: by mail-we0-f179.google.com with SMTP id x48so1904582wes.24 for ; Thu, 27 Mar 2014 09:24:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=fi1vny4RUqjgaokwX/eGX4nEFvM9loDV+SN5sh6IEDU=; b=d8U8V7XPqnnt+ep2Zi7zaG/JCJqFO22RsvM6lf6AKpEZsOKiCiE5QsFY+2TNKhqSln l6nD2enuWU8nr9hoNkIHyCII/v6mo7u4dQhpWJGHOZBomBtxZnrcXlwSg7snmfVCD+/i 6meY5V0A5ZOnvkL3Lush9LhoGCLtN1dLjePzLuFVlDAR5OqVjMp33UVGad1cdtDcl7l3 nGZv3q8nX+kJw06YuEIxOm1Yc+PX7T8gFsveTPC5zk4kvIIE8yR6FSRDn3BykaE2G1ea qU8K0VQpEmrizarxiuCDJZ7prbQ3HaVXL8oADS9ufZX8aPXvWgOekqL+TAcDEjxzvyqg N0lA== X-Received: by 10.180.75.202 with SMTP id e10mr41535394wiw.50.1395937479648; Thu, 27 Mar 2014 09:24:39 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id h19sm8581987wiw.17.2014.03.27.09.24.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Mar 2014 09:24:38 -0700 (PDT) Message-ID: <533450C5.5070005@xen.org> Date: Thu, 27 Mar 2014 16:24:37 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" References: <1395927366.3749.13.camel@Guybrush> In-Reply-To: <1395927366.3749.13.camel@Guybrush> X-Forwarded-Message-Id: <1395927366.3749.13.camel@Guybrush> Content-Type: multipart/mixed; boundary="------------060301080903010301010403" Subject: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --------------060301080903010301010403 Content-Type: multipart/alternative; boundary="------------070906040507060704010004" --------------070906040507060704010004 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi all, a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in XAPI and MirageOS repositories on github. Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below ... Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam Regards Lars = Detected forks in XAPI Project = xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git PRDup git://github.com/xapi-project/PRDup.git blktap-dkms git://github.com/xapi-project/blktap-dkms.git cdrom git://github.com/xapi-project/cdrom.git ffs git://github.com/xapi-project/ffs.git libvhd git://github.com/xapi-project/libvhd.git nbd git://github.com/xapi-project/nbd.git netdev git://github.com/xapi-project/netdev.git ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git ocaml-sha git://github.com/xapi-project/ocaml-sha.git ocaml-tar git://github.com/xapi-project/ocaml-tar.git ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git ocaml-xenstore-clients git://github.com/xapi-project/ocaml-xenstore-clients.git ocamltest git://github.com/xapi-project/ocamltest.git oclock git://github.com/xapi-project/oclock.git opam git://github.com/xapi-project/opam.git opam-repository git://github.com/xapi-project/opam-repository.git python-github2 git://github.com/xapi-project/python-github2.git tapctl git://github.com/xapi-project/tapctl.git vhd-tool git://github.com/xapi-project/vhd-tool.git vncterm git://github.com/xapi-project/vncterm.git wsproxy git://github.com/xapi-project/wsproxy.git xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git xcp-idl git://github.com/xapi-project/xcp-idl.git xcp-storage-managers git://github.com/xapi-project/xcp-storage-managers.git xen-api-backports git://github.com/xapi-project/xen-api-backports.git xen-api-client git://github.com/xapi-project/xen-api-client.git xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git xen-api-libs-transitional git://github.com/xapi-project/xen-api-libs-transitional.git xs-pull-request-build-scripts git://github.com/xapi-project/xs-pull-request-build-scripts.git = Detected forks in Mirage OS = xen git://github.com/mirage/xen.git mirari git://github.com/mirage/mirari.git ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git ocaml-dns git://github.com/mirage/ocaml-dns.git ocaml-openflow git://github.com/mirage/ocaml-openflow.git ocaml-re git://github.com/mirage/ocaml-re.git ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git ocaml-uri git://github.com/mirage/ocaml-uri.git ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git opam-repository git://github.com/mirage/opam-repository.git -------- Original Message -------- Subject: Removing forks from the analysis Date: Thu, 27 Mar 2014 14:36:06 +0100 From: Santiago Dueñas To: Lars Kurth CC: citrix@lists.bitergia.com Hi again Lars, during our analysis, we found that some of your git repos are forks from upstream repositories. I don not know whether you talk to Manrique or Jesus about that but I prefer to remember you which possibilities we offer and which one we have follow. The repositories that we have already analyzed are listed on the scm-repos page: http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html We offer three possibilities for treating these cases: - Do not analyze forks. This is the default option. We have removed from the analysis those repositories marked as forks in Github and others from upstream such as "ocaml" and "opam" series (see the attached file that includes the full list of forks). Probably, you will want to remove more. If this is your choice, please have a look at the repositories page and send me an email with the list of git repositories you want to remove from the analysis. - Analyze forks. Take into account that this can affect the whole numbers and stats, particularly if your team is not really active in these repos. - Analyze differences between upstream and local repositories. Due this functionality is out of the basic dashboard, please talk to Manrique or Jesus to get more details, if interested. Santi -- Santiago Dueñas sduenas@bitergia.com Bitergia S.L.L --------------070906040507060704010004 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi all,

a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in  XAPI and MirageOS repositories on github. Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below ...

Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam

Regards
Lars

= Detected forks in XAPI Project =
xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git
PRDup git://github.com/xapi-project/PRDup.git
blktap-dkms git://github.com/xapi-project/blktap-dkms.git
cdrom git://github.com/xapi-project/cdrom.git
ffs git://github.com/xapi-project/ffs.git
libvhd git://github.com/xapi-project/libvhd.git
nbd git://github.com/xapi-project/nbd.git
netdev git://github.com/xapi-project/netdev.git
ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git
ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git
ocaml-sha git://github.com/xapi-project/ocaml-sha.git
ocaml-tar git://github.com/xapi-project/ocaml-tar.git
ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git
ocaml-xenstore-clients git://github.com/xapi-project/ocaml-xenstore-clients.git
ocamltest git://github.com/xapi-project/ocamltest.git
oclock git://github.com/xapi-project/oclock.git
opam git://github.com/xapi-project/opam.git
opam-repository git://github.com/xapi-project/opam-repository.git
python-github2 git://github.com/xapi-project/python-github2.git
tapctl git://github.com/xapi-project/tapctl.git
vhd-tool git://github.com/xapi-project/vhd-tool.git
vncterm git://github.com/xapi-project/vncterm.git
wsproxy git://github.com/xapi-project/wsproxy.git
xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git
xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git
xcp-idl git://github.com/xapi-project/xcp-idl.git
xcp-storage-managers git://github.com/xapi-project/xcp-storage-managers.git
xen-api-backports git://github.com/xapi-project/xen-api-backports.git
xen-api-client git://github.com/xapi-project/xen-api-client.git
xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git
xen-api-libs-transitional git://github.com/xapi-project/xen-api-libs-transitional.git
xs-pull-request-build-scripts git://github.com/xapi-project/xs-pull-request-build-scripts.git

= Detected forks in Mirage OS =
xen git://github.com/mirage/xen.git
mirari git://github.com/mirage/mirari.git
ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git
ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git
ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git
ocaml-dns git://github.com/mirage/ocaml-dns.git
ocaml-openflow git://github.com/mirage/ocaml-openflow.git
ocaml-re git://github.com/mirage/ocaml-re.git
ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git
ocaml-uri git://github.com/mirage/ocaml-uri.git
ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git
opam-repository git://github.com/mirage/opam-repository.git




-------- Original Message --------
Subject: Removing forks from the analysis
Date: Thu, 27 Mar 2014 14:36:06 +0100
From: Santiago Dueñas <sduenas@bitergia.com>
To: Lars Kurth <lars.kurth@xen.org>
CC: citrix@lists.bitergia.com 


Hi again Lars,

during our analysis, we found that some of your git repos are forks from
upstream repositories. I don not know whether you talk to Manrique or
Jesus about that but I prefer to remember you which possibilities we
offer and which one we have follow.

The repositories that we have already analyzed are listed on the
scm-repos page:

http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html

We offer three possibilities for treating these cases:

- Do not analyze forks. This is the default option. We have removed from
the analysis those repositories marked as forks in Github and others
from upstream such as "ocaml" and "opam" series (see the attached file
that includes the full list of forks).

Probably, you will want to remove more. If this is your choice, please
have a look at the repositories page and send me an email with the list
of git repositories you want to remove from the analysis.

- Analyze forks. Take into account that this can affect the whole
numbers and stats, particularly if your team is not really active in
these repos.

- Analyze differences between upstream and local repositories. Due this
functionality is out of the basic dashboard, please talk to Manrique or
Jesus to get more details, if interested.

Santi
-- 
Santiago Dueñas
sduenas@bitergia.com
Bitergia S.L.L


--------------070906040507060704010004-- --------------060301080903010301010403 Content-Type: text/plain; charset=windows-1252; name="xen_forks.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xen_forks.txt" PSBEZXRlY3RlZCBmb3JrcyBpbiBYQVBJIFByb2plY3QgPQ0KeGVuLXVuc3RhYmxlLW1pcnJv ciBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC94ZW4tdW5zdGFibGUtbWlycm9yLmdp dA0KUFJEdXAgZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXByb2plY3QvUFJEdXAuZ2l0DQpibGt0 YXAtZGttcyBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC9ibGt0YXAtZGttcy5naXQN CmNkcm9tIGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L2Nkcm9tLmdpdA0KZmZzIGdp dDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L2Zmcy5naXQNCmxpYnZoZCBnaXQ6Ly9naXRo dWIuY29tL3hhcGktcHJvamVjdC9saWJ2aGQuZ2l0DQpuYmQgZ2l0Oi8vZ2l0aHViLmNvbS94 YXBpLXByb2plY3QvbmJkLmdpdA0KbmV0ZGV2IGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9q ZWN0L25ldGRldi5naXQNCm9jYW1sLWZkLXNlbmQtcmVjdiBnaXQ6Ly9naXRodWIuY29tL3hh cGktcHJvamVjdC9vY2FtbC1mZC1zZW5kLXJlY3YuZ2l0DQpvY2FtbC1vcGFzc3dkIGdpdDov L2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L29jYW1sLW9wYXNzd2QuZ2l0DQpvY2FtbC1zaGEg Z2l0Oi8vZ2l0aHViLmNvbS94YXBpLXByb2plY3Qvb2NhbWwtc2hhLmdpdA0Kb2NhbWwtdGFy IGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L29jYW1sLXRhci5naXQNCm9jYW1sLXZo ZCBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC9vY2FtbC12aGQuZ2l0DQpvY2FtbC14 ZW5zdG9yZS1jbGllbnRzIGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L29jYW1sLXhl bnN0b3JlLWNsaWVudHMuZ2l0DQpvY2FtbHRlc3QgZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXBy b2plY3Qvb2NhbWx0ZXN0LmdpdA0Kb2Nsb2NrIGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9q ZWN0L29jbG9jay5naXQNCm9wYW0gZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXByb2plY3Qvb3Bh bS5naXQNCm9wYW0tcmVwb3NpdG9yeSBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC9v cGFtLXJlcG9zaXRvcnkuZ2l0DQpweXRob24tZ2l0aHViMiBnaXQ6Ly9naXRodWIuY29tL3hh cGktcHJvamVjdC9weXRob24tZ2l0aHViMi5naXQNCnRhcGN0bCBnaXQ6Ly9naXRodWIuY29t L3hhcGktcHJvamVjdC90YXBjdGwuZ2l0DQp2aGQtdG9vbCBnaXQ6Ly9naXRodWIuY29tL3hh cGktcHJvamVjdC92aGQtdG9vbC5naXQNCnZuY3Rlcm0gZ2l0Oi8vZ2l0aHViLmNvbS94YXBp LXByb2plY3Qvdm5jdGVybS5naXQNCndzcHJveHkgZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXBy b2plY3Qvd3Nwcm94eS5naXQNCnhjcC1lbGlsb2FkZXIgZ2l0Oi8vZ2l0aHViLmNvbS94YXBp LXByb2plY3QveGNwLWVsaWxvYWRlci5naXQNCnhjcC1ndWVzdC10ZW1wbGF0ZXMgZ2l0Oi8v Z2l0aHViLmNvbS94YXBpLXByb2plY3QveGNwLWd1ZXN0LXRlbXBsYXRlcy5naXQNCnhjcC1p ZGwgZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXByb2plY3QveGNwLWlkbC5naXQNCnhjcC1zdG9y YWdlLW1hbmFnZXJzIGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L3hjcC1zdG9yYWdl LW1hbmFnZXJzLmdpdA0KeGVuLWFwaS1iYWNrcG9ydHMgZ2l0Oi8vZ2l0aHViLmNvbS94YXBp LXByb2plY3QveGVuLWFwaS1iYWNrcG9ydHMuZ2l0DQp4ZW4tYXBpLWNsaWVudCBnaXQ6Ly9n aXRodWIuY29tL3hhcGktcHJvamVjdC94ZW4tYXBpLWNsaWVudC5naXQNCnhlbi1hcGktbGli cy1zcGVjcyBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC94ZW4tYXBpLWxpYnMtc3Bl Y3MuZ2l0DQp4ZW4tYXBpLWxpYnMtdHJhbnNpdGlvbmFsIGdpdDovL2dpdGh1Yi5jb20veGFw aS1wcm9qZWN0L3hlbi1hcGktbGlicy10cmFuc2l0aW9uYWwuZ2l0DQp4cy1wdWxsLXJlcXVl c3QtYnVpbGQtc2NyaXB0cyBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC94cy1wdWxs LXJlcXVlc3QtYnVpbGQtc2NyaXB0cy5naXQNCg0KPSBEZXRlY3RlZCBmb3JrcyBpbiBNaXJh Z2UgT1MgPQ0KDQp4ZW4gZ2l0Oi8vZ2l0aHViLmNvbS9taXJhZ2UveGVuLmdpdA0KbWlyYXJp IGdpdDovL2dpdGh1Yi5jb20vbWlyYWdlL21pcmFyaS5naXQNCm9jYW1sLWNvaHR0cCBnaXQ6 Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC1jb2h0dHAuZ2l0DQpvY2FtbC1jcnlwdG8ta2V5 cyBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC1jcnlwdG8ta2V5cy5naXQNCm9jYW1s LWNzdHJ1Y3QgZ2l0Oi8vZ2l0aHViLmNvbS9taXJhZ2Uvb2NhbWwtY3N0cnVjdC5naXQNCm9j YW1sLWRucyBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC1kbnMuZ2l0DQpvY2FtbC1v cGVuZmxvdyBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC1vcGVuZmxvdy5naXQNCm9j YW1sLXJlIGdpdDovL2dpdGh1Yi5jb20vbWlyYWdlL29jYW1sLXJlLmdpdA0Kb2NhbWwtdHVu dGFwIGdpdDovL2dpdGh1Yi5jb20vbWlyYWdlL29jYW1sLXR1bnRhcC5naXQNCm9jYW1sLXVy aSBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC11cmkuZ2l0DQpvY2FtbC14ZW5zdG9y ZSBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC14ZW5zdG9yZS5naXQNCm9wYW0tcmVw b3NpdG9yeSBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vcGFtLXJlcG9zaXRvcnkuZ2l0DQoN Cg0K --------------060301080903010301010403 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------060301080903010301010403-- From xen-api-bounces@lists.xen.org Thu Mar 27 16:25:05 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 16:25:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTD6l-0006NF-0P; Thu, 27 Mar 2014 16:24:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTD6j-0006My-7l for xen-api@lists.xen.org; Thu, 27 Mar 2014 16:24:45 +0000 Received: from [193.109.254.147:59739] by server-10.bemta-14.messagelabs.com id F4/F6-04546-BC054335; Thu, 27 Mar 2014 16:24:43 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1395937479!4599459!1 X-Originating-IP: [74.125.82.179] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27706 invoked from network); 27 Mar 2014 16:24:40 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 16:24:40 -0000 Received: by mail-we0-f179.google.com with SMTP id x48so1904582wes.24 for ; Thu, 27 Mar 2014 09:24:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=fi1vny4RUqjgaokwX/eGX4nEFvM9loDV+SN5sh6IEDU=; b=d8U8V7XPqnnt+ep2Zi7zaG/JCJqFO22RsvM6lf6AKpEZsOKiCiE5QsFY+2TNKhqSln l6nD2enuWU8nr9hoNkIHyCII/v6mo7u4dQhpWJGHOZBomBtxZnrcXlwSg7snmfVCD+/i 6meY5V0A5ZOnvkL3Lush9LhoGCLtN1dLjePzLuFVlDAR5OqVjMp33UVGad1cdtDcl7l3 nGZv3q8nX+kJw06YuEIxOm1Yc+PX7T8gFsveTPC5zk4kvIIE8yR6FSRDn3BykaE2G1ea qU8K0VQpEmrizarxiuCDJZ7prbQ3HaVXL8oADS9ufZX8aPXvWgOekqL+TAcDEjxzvyqg N0lA== X-Received: by 10.180.75.202 with SMTP id e10mr41535394wiw.50.1395937479648; Thu, 27 Mar 2014 09:24:39 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id h19sm8581987wiw.17.2014.03.27.09.24.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Mar 2014 09:24:38 -0700 (PDT) Message-ID: <533450C5.5070005@xen.org> Date: Thu, 27 Mar 2014 16:24:37 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" References: <1395927366.3749.13.camel@Guybrush> In-Reply-To: <1395927366.3749.13.camel@Guybrush> X-Forwarded-Message-Id: <1395927366.3749.13.camel@Guybrush> Content-Type: multipart/mixed; boundary="------------060301080903010301010403" Subject: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --------------060301080903010301010403 Content-Type: multipart/alternative; boundary="------------070906040507060704010004" --------------070906040507060704010004 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi all, a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in XAPI and MirageOS repositories on github. Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below ... Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam Regards Lars = Detected forks in XAPI Project = xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git PRDup git://github.com/xapi-project/PRDup.git blktap-dkms git://github.com/xapi-project/blktap-dkms.git cdrom git://github.com/xapi-project/cdrom.git ffs git://github.com/xapi-project/ffs.git libvhd git://github.com/xapi-project/libvhd.git nbd git://github.com/xapi-project/nbd.git netdev git://github.com/xapi-project/netdev.git ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git ocaml-sha git://github.com/xapi-project/ocaml-sha.git ocaml-tar git://github.com/xapi-project/ocaml-tar.git ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git ocaml-xenstore-clients git://github.com/xapi-project/ocaml-xenstore-clients.git ocamltest git://github.com/xapi-project/ocamltest.git oclock git://github.com/xapi-project/oclock.git opam git://github.com/xapi-project/opam.git opam-repository git://github.com/xapi-project/opam-repository.git python-github2 git://github.com/xapi-project/python-github2.git tapctl git://github.com/xapi-project/tapctl.git vhd-tool git://github.com/xapi-project/vhd-tool.git vncterm git://github.com/xapi-project/vncterm.git wsproxy git://github.com/xapi-project/wsproxy.git xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git xcp-idl git://github.com/xapi-project/xcp-idl.git xcp-storage-managers git://github.com/xapi-project/xcp-storage-managers.git xen-api-backports git://github.com/xapi-project/xen-api-backports.git xen-api-client git://github.com/xapi-project/xen-api-client.git xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git xen-api-libs-transitional git://github.com/xapi-project/xen-api-libs-transitional.git xs-pull-request-build-scripts git://github.com/xapi-project/xs-pull-request-build-scripts.git = Detected forks in Mirage OS = xen git://github.com/mirage/xen.git mirari git://github.com/mirage/mirari.git ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git ocaml-dns git://github.com/mirage/ocaml-dns.git ocaml-openflow git://github.com/mirage/ocaml-openflow.git ocaml-re git://github.com/mirage/ocaml-re.git ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git ocaml-uri git://github.com/mirage/ocaml-uri.git ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git opam-repository git://github.com/mirage/opam-repository.git -------- Original Message -------- Subject: Removing forks from the analysis Date: Thu, 27 Mar 2014 14:36:06 +0100 From: Santiago Dueñas To: Lars Kurth CC: citrix@lists.bitergia.com Hi again Lars, during our analysis, we found that some of your git repos are forks from upstream repositories. I don not know whether you talk to Manrique or Jesus about that but I prefer to remember you which possibilities we offer and which one we have follow. The repositories that we have already analyzed are listed on the scm-repos page: http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html We offer three possibilities for treating these cases: - Do not analyze forks. This is the default option. We have removed from the analysis those repositories marked as forks in Github and others from upstream such as "ocaml" and "opam" series (see the attached file that includes the full list of forks). Probably, you will want to remove more. If this is your choice, please have a look at the repositories page and send me an email with the list of git repositories you want to remove from the analysis. - Analyze forks. Take into account that this can affect the whole numbers and stats, particularly if your team is not really active in these repos. - Analyze differences between upstream and local repositories. Due this functionality is out of the basic dashboard, please talk to Manrique or Jesus to get more details, if interested. Santi -- Santiago Dueñas sduenas@bitergia.com Bitergia S.L.L --------------070906040507060704010004 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi all,

a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in  XAPI and MirageOS repositories on github. Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below ...

Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam

Regards
Lars

= Detected forks in XAPI Project =
xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git
PRDup git://github.com/xapi-project/PRDup.git
blktap-dkms git://github.com/xapi-project/blktap-dkms.git
cdrom git://github.com/xapi-project/cdrom.git
ffs git://github.com/xapi-project/ffs.git
libvhd git://github.com/xapi-project/libvhd.git
nbd git://github.com/xapi-project/nbd.git
netdev git://github.com/xapi-project/netdev.git
ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git
ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git
ocaml-sha git://github.com/xapi-project/ocaml-sha.git
ocaml-tar git://github.com/xapi-project/ocaml-tar.git
ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git
ocaml-xenstore-clients git://github.com/xapi-project/ocaml-xenstore-clients.git
ocamltest git://github.com/xapi-project/ocamltest.git
oclock git://github.com/xapi-project/oclock.git
opam git://github.com/xapi-project/opam.git
opam-repository git://github.com/xapi-project/opam-repository.git
python-github2 git://github.com/xapi-project/python-github2.git
tapctl git://github.com/xapi-project/tapctl.git
vhd-tool git://github.com/xapi-project/vhd-tool.git
vncterm git://github.com/xapi-project/vncterm.git
wsproxy git://github.com/xapi-project/wsproxy.git
xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git
xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git
xcp-idl git://github.com/xapi-project/xcp-idl.git
xcp-storage-managers git://github.com/xapi-project/xcp-storage-managers.git
xen-api-backports git://github.com/xapi-project/xen-api-backports.git
xen-api-client git://github.com/xapi-project/xen-api-client.git
xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git
xen-api-libs-transitional git://github.com/xapi-project/xen-api-libs-transitional.git
xs-pull-request-build-scripts git://github.com/xapi-project/xs-pull-request-build-scripts.git

= Detected forks in Mirage OS =
xen git://github.com/mirage/xen.git
mirari git://github.com/mirage/mirari.git
ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git
ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git
ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git
ocaml-dns git://github.com/mirage/ocaml-dns.git
ocaml-openflow git://github.com/mirage/ocaml-openflow.git
ocaml-re git://github.com/mirage/ocaml-re.git
ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git
ocaml-uri git://github.com/mirage/ocaml-uri.git
ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git
opam-repository git://github.com/mirage/opam-repository.git




-------- Original Message --------
Subject: Removing forks from the analysis
Date: Thu, 27 Mar 2014 14:36:06 +0100
From: Santiago Dueñas <sduenas@bitergia.com>
To: Lars Kurth <lars.kurth@xen.org>
CC: citrix@lists.bitergia.com 


Hi again Lars,

during our analysis, we found that some of your git repos are forks from
upstream repositories. I don not know whether you talk to Manrique or
Jesus about that but I prefer to remember you which possibilities we
offer and which one we have follow.

The repositories that we have already analyzed are listed on the
scm-repos page:

http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html

We offer three possibilities for treating these cases:

- Do not analyze forks. This is the default option. We have removed from
the analysis those repositories marked as forks in Github and others
from upstream such as "ocaml" and "opam" series (see the attached file
that includes the full list of forks).

Probably, you will want to remove more. If this is your choice, please
have a look at the repositories page and send me an email with the list
of git repositories you want to remove from the analysis.

- Analyze forks. Take into account that this can affect the whole
numbers and stats, particularly if your team is not really active in
these repos.

- Analyze differences between upstream and local repositories. Due this
functionality is out of the basic dashboard, please talk to Manrique or
Jesus to get more details, if interested.

Santi
-- 
Santiago Dueñas
sduenas@bitergia.com
Bitergia S.L.L


--------------070906040507060704010004-- --------------060301080903010301010403 Content-Type: text/plain; charset=windows-1252; name="xen_forks.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xen_forks.txt" PSBEZXRlY3RlZCBmb3JrcyBpbiBYQVBJIFByb2plY3QgPQ0KeGVuLXVuc3RhYmxlLW1pcnJv ciBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC94ZW4tdW5zdGFibGUtbWlycm9yLmdp dA0KUFJEdXAgZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXByb2plY3QvUFJEdXAuZ2l0DQpibGt0 YXAtZGttcyBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC9ibGt0YXAtZGttcy5naXQN CmNkcm9tIGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L2Nkcm9tLmdpdA0KZmZzIGdp dDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L2Zmcy5naXQNCmxpYnZoZCBnaXQ6Ly9naXRo dWIuY29tL3hhcGktcHJvamVjdC9saWJ2aGQuZ2l0DQpuYmQgZ2l0Oi8vZ2l0aHViLmNvbS94 YXBpLXByb2plY3QvbmJkLmdpdA0KbmV0ZGV2IGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9q ZWN0L25ldGRldi5naXQNCm9jYW1sLWZkLXNlbmQtcmVjdiBnaXQ6Ly9naXRodWIuY29tL3hh cGktcHJvamVjdC9vY2FtbC1mZC1zZW5kLXJlY3YuZ2l0DQpvY2FtbC1vcGFzc3dkIGdpdDov L2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L29jYW1sLW9wYXNzd2QuZ2l0DQpvY2FtbC1zaGEg Z2l0Oi8vZ2l0aHViLmNvbS94YXBpLXByb2plY3Qvb2NhbWwtc2hhLmdpdA0Kb2NhbWwtdGFy IGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L29jYW1sLXRhci5naXQNCm9jYW1sLXZo ZCBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC9vY2FtbC12aGQuZ2l0DQpvY2FtbC14 ZW5zdG9yZS1jbGllbnRzIGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L29jYW1sLXhl bnN0b3JlLWNsaWVudHMuZ2l0DQpvY2FtbHRlc3QgZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXBy b2plY3Qvb2NhbWx0ZXN0LmdpdA0Kb2Nsb2NrIGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9q ZWN0L29jbG9jay5naXQNCm9wYW0gZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXByb2plY3Qvb3Bh bS5naXQNCm9wYW0tcmVwb3NpdG9yeSBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC9v cGFtLXJlcG9zaXRvcnkuZ2l0DQpweXRob24tZ2l0aHViMiBnaXQ6Ly9naXRodWIuY29tL3hh cGktcHJvamVjdC9weXRob24tZ2l0aHViMi5naXQNCnRhcGN0bCBnaXQ6Ly9naXRodWIuY29t L3hhcGktcHJvamVjdC90YXBjdGwuZ2l0DQp2aGQtdG9vbCBnaXQ6Ly9naXRodWIuY29tL3hh cGktcHJvamVjdC92aGQtdG9vbC5naXQNCnZuY3Rlcm0gZ2l0Oi8vZ2l0aHViLmNvbS94YXBp LXByb2plY3Qvdm5jdGVybS5naXQNCndzcHJveHkgZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXBy b2plY3Qvd3Nwcm94eS5naXQNCnhjcC1lbGlsb2FkZXIgZ2l0Oi8vZ2l0aHViLmNvbS94YXBp LXByb2plY3QveGNwLWVsaWxvYWRlci5naXQNCnhjcC1ndWVzdC10ZW1wbGF0ZXMgZ2l0Oi8v Z2l0aHViLmNvbS94YXBpLXByb2plY3QveGNwLWd1ZXN0LXRlbXBsYXRlcy5naXQNCnhjcC1p ZGwgZ2l0Oi8vZ2l0aHViLmNvbS94YXBpLXByb2plY3QveGNwLWlkbC5naXQNCnhjcC1zdG9y YWdlLW1hbmFnZXJzIGdpdDovL2dpdGh1Yi5jb20veGFwaS1wcm9qZWN0L3hjcC1zdG9yYWdl LW1hbmFnZXJzLmdpdA0KeGVuLWFwaS1iYWNrcG9ydHMgZ2l0Oi8vZ2l0aHViLmNvbS94YXBp LXByb2plY3QveGVuLWFwaS1iYWNrcG9ydHMuZ2l0DQp4ZW4tYXBpLWNsaWVudCBnaXQ6Ly9n aXRodWIuY29tL3hhcGktcHJvamVjdC94ZW4tYXBpLWNsaWVudC5naXQNCnhlbi1hcGktbGli cy1zcGVjcyBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC94ZW4tYXBpLWxpYnMtc3Bl Y3MuZ2l0DQp4ZW4tYXBpLWxpYnMtdHJhbnNpdGlvbmFsIGdpdDovL2dpdGh1Yi5jb20veGFw aS1wcm9qZWN0L3hlbi1hcGktbGlicy10cmFuc2l0aW9uYWwuZ2l0DQp4cy1wdWxsLXJlcXVl c3QtYnVpbGQtc2NyaXB0cyBnaXQ6Ly9naXRodWIuY29tL3hhcGktcHJvamVjdC94cy1wdWxs LXJlcXVlc3QtYnVpbGQtc2NyaXB0cy5naXQNCg0KPSBEZXRlY3RlZCBmb3JrcyBpbiBNaXJh Z2UgT1MgPQ0KDQp4ZW4gZ2l0Oi8vZ2l0aHViLmNvbS9taXJhZ2UveGVuLmdpdA0KbWlyYXJp IGdpdDovL2dpdGh1Yi5jb20vbWlyYWdlL21pcmFyaS5naXQNCm9jYW1sLWNvaHR0cCBnaXQ6 Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC1jb2h0dHAuZ2l0DQpvY2FtbC1jcnlwdG8ta2V5 cyBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC1jcnlwdG8ta2V5cy5naXQNCm9jYW1s LWNzdHJ1Y3QgZ2l0Oi8vZ2l0aHViLmNvbS9taXJhZ2Uvb2NhbWwtY3N0cnVjdC5naXQNCm9j YW1sLWRucyBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC1kbnMuZ2l0DQpvY2FtbC1v cGVuZmxvdyBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC1vcGVuZmxvdy5naXQNCm9j YW1sLXJlIGdpdDovL2dpdGh1Yi5jb20vbWlyYWdlL29jYW1sLXJlLmdpdA0Kb2NhbWwtdHVu dGFwIGdpdDovL2dpdGh1Yi5jb20vbWlyYWdlL29jYW1sLXR1bnRhcC5naXQNCm9jYW1sLXVy aSBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC11cmkuZ2l0DQpvY2FtbC14ZW5zdG9y ZSBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vY2FtbC14ZW5zdG9yZS5naXQNCm9wYW0tcmVw b3NpdG9yeSBnaXQ6Ly9naXRodWIuY29tL21pcmFnZS9vcGFtLXJlcG9zaXRvcnkuZ2l0DQoN Cg0K --------------060301080903010301010403 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------060301080903010301010403-- From xen-api-bounces@lists.xen.org Thu Mar 27 16:29:22 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 16:29:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTDAv-0006ZB-Iw; Thu, 27 Mar 2014 16:29:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTDAt-0006Z0-L2 for xen-api@lists.xen.org; Thu, 27 Mar 2014 16:29:04 +0000 Received: from [85.158.139.211:26209] by server-16.bemta-5.messagelabs.com id 27/B1-19700-EC154335; Thu, 27 Mar 2014 16:29:02 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-206.messagelabs.com!1395937739!3776914!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22134 invoked from network); 27 Mar 2014 16:28:59 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-206.messagelabs.com with SMTP; 27 Mar 2014 16:28:59 -0000 Received: (qmail 7780 invoked by uid 634); 27 Mar 2014 16:28:59 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 27 Mar 2014 16:28:58 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <533450C5.5070005@xen.org> Date: Thu, 27 Mar 2014 16:28:57 +0000 Message-Id: <3A5650C9-9F0F-47F1-9204-4A90D1A04F9D@recoil.org> References: <1395927366.3749.13.camel@Guybrush> <533450C5.5070005@xen.org> To: lars.kurth@xen.org X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4473929198037242640==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4473929198037242640== Content-Type: multipart/alternative; boundary="Apple-Mail=_949F347A-B5C1-46B8-9307-CE8185BC36C4" --Apple-Mail=_949F347A-B5C1-46B8-9307-CE8185BC36C4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Dave and I are currently going through our repository list to normalize = this for Mirage. https://github.com/mirage/mirage/issues/236 We'll update you shortly when the "trove" is completed. That will have = an authoritative list of libraries, as well as spotting any licensing = inconsistencies or incorrect fork orders. cheers, Anil On 27 Mar 2014, at 16:24, Lars Kurth wrote: > Hi all, >=20 > a while ago I kicked a conversation related to putting a dashboard for = the Xen project sub projects together. As it turns out there is an issue = in XAPI and MirageOS repositories on github. Some of them are forks of = upstreams, which are hard for the tool to analyze. My proposal would be = to *not analyse them* and include them into statistics. If I don't hear = any screams, then this will be the default. The list of forks detected = are listed below ... >=20 > Also, it would be good to let me know of any other repos that you dont = want to analyse. The full list is at = http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html = (note that there is 79 pages of them) which should be aggregated into = buckets for XAPI and opam >=20 > Regards > Lars >=20 > =3D Detected forks in XAPI Project =3D > xen-unstable-mirror = git://github.com/xapi-project/xen-unstable-mirror.git > PRDup git://github.com/xapi-project/PRDup.git > blktap-dkms git://github.com/xapi-project/blktap-dkms.git > cdrom git://github.com/xapi-project/cdrom.git > ffs git://github.com/xapi-project/ffs.git > libvhd git://github.com/xapi-project/libvhd.git > nbd git://github.com/xapi-project/nbd.git > netdev git://github.com/xapi-project/netdev.git > ocaml-fd-send-recv = git://github.com/xapi-project/ocaml-fd-send-recv.git > ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git > ocaml-sha git://github.com/xapi-project/ocaml-sha.git > ocaml-tar git://github.com/xapi-project/ocaml-tar.git > ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git > ocaml-xenstore-clients = git://github.com/xapi-project/ocaml-xenstore-clients.git > ocamltest git://github.com/xapi-project/ocamltest.git > oclock git://github.com/xapi-project/oclock.git > opam git://github.com/xapi-project/opam.git > opam-repository git://github.com/xapi-project/opam-repository.git > python-github2 git://github.com/xapi-project/python-github2.git > tapctl git://github.com/xapi-project/tapctl.git > vhd-tool git://github.com/xapi-project/vhd-tool.git > vncterm git://github.com/xapi-project/vncterm.git > wsproxy git://github.com/xapi-project/wsproxy.git > xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git > xcp-guest-templates = git://github.com/xapi-project/xcp-guest-templates.git > xcp-idl git://github.com/xapi-project/xcp-idl.git > xcp-storage-managers = git://github.com/xapi-project/xcp-storage-managers.git > xen-api-backports git://github.com/xapi-project/xen-api-backports.git > xen-api-client git://github.com/xapi-project/xen-api-client.git > xen-api-libs-specs = git://github.com/xapi-project/xen-api-libs-specs.git > xen-api-libs-transitional = git://github.com/xapi-project/xen-api-libs-transitional.git > xs-pull-request-build-scripts = git://github.com/xapi-project/xs-pull-request-build-scripts.git >=20 > =3D Detected forks in Mirage OS =3D > xen git://github.com/mirage/xen.git > mirari git://github.com/mirage/mirari.git > ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git > ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git > ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git > ocaml-dns git://github.com/mirage/ocaml-dns.git > ocaml-openflow git://github.com/mirage/ocaml-openflow.git > ocaml-re git://github.com/mirage/ocaml-re.git > ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git > ocaml-uri git://github.com/mirage/ocaml-uri.git > ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git > opam-repository git://github.com/mirage/opam-repository.git >=20 >=20 >=20 >=20 > -------- Original Message -------- > Subject: Removing forks from the analysis > Date: Thu, 27 Mar 2014 14:36:06 +0100 > From: Santiago Due=F1as > To: Lars Kurth > CC: citrix@lists.bitergia.com >=20 > Hi again Lars, >=20 > during our analysis, we found that some of your git repos are forks = from > upstream repositories. I don not know whether you talk to Manrique or > Jesus about that but I prefer to remember you which possibilities we > offer and which one we have follow. >=20 > The repositories that we have already analyzed are listed on the > scm-repos page: >=20 > = http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html >=20 > We offer three possibilities for treating these cases: >=20 > - Do not analyze forks. This is the default option. We have removed = from > the analysis those repositories marked as forks in Github and others > from upstream such as "ocaml" and "opam" series (see the attached file > that includes the full list of forks). >=20 > Probably, you will want to remove more. If this is your choice, please > have a look at the repositories page and send me an email with the = list > of git repositories you want to remove from the analysis. >=20 > - Analyze forks. Take into account that this can affect the whole > numbers and stats, particularly if your team is not really active in > these repos. >=20 > - Analyze differences between upstream and local repositories. Due = this > functionality is out of the basic dashboard, please talk to Manrique = or > Jesus to get more details, if interested. >=20 > Santi > --=20 > Santiago Due=F1as > sduenas@bitergia.com > Bitergia S.L.L >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --Apple-Mail=_949F347A-B5C1-46B8-9307-CE8185BC36C4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Dave = and I are currently going through our repository list to normalize this = for Mirage.


We'll update you = shortly when the "trove" is completed.  That will have an = authoritative list of libraries, as well as spotting any licensing = inconsistencies or incorrect fork = orders.

cheers,
Anil

On 27 Mar 2014, at 16:24, Lars Kurth <lars.kurth@xen.org> = wrote:

=20 =20
Hi all,

a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in  XAPI and MirageOS repositories on github. = Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below = ...

Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repo= s.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam

Regards
Lars

=3D Detected forks in XAPI Project =3D
xen-unstable-mirror git://githu= b.com/xapi-project/xen-unstable-mirror.git
PRDup git://github.com/xapi-pro= ject/PRDup.git
blktap-dkms git://github.com/xa= pi-project/blktap-dkms.git
cdrom git://github.com/xapi-pro= ject/cdrom.git
ffs git://github.com/xapi-proje= ct/ffs.git
libvhd git://github.com/xapi-pr= oject/libvhd.git
nbd git://github.com/xapi-proje= ct/nbd.git
netdev git://github.com/xapi-pr= oject/netdev.git
ocaml-fd-send-recv git://github= .com/xapi-project/ocaml-fd-send-recv.git
ocaml-opasswd git://github.com/= xapi-project/ocaml-opasswd.git
ocaml-sha git://github.com/xapi= -project/ocaml-sha.git
ocaml-tar git://github.com/xapi= -project/ocaml-tar.git
ocaml-vhd git://github.com/xapi= -project/ocaml-vhd.git
ocaml-xenstore-clients git://gi= thub.com/xapi-project/ocaml-xenstore-clients.git
ocamltest git://github.com/xapi= -project/ocamltest.git
oclock git://github.com/xapi-pr= oject/oclock.git
opam git://github.com/xapi-proj= ect/opam.git
opam-repository git://github.co= m/xapi-project/opam-repository.git
python-github2 git://github.com= /xapi-project/python-github2.git
tapctl git://github.com/xapi-pr= oject/tapctl.git
vhd-tool git://github.com/xapi-= project/vhd-tool.git
vncterm git://github.com/xapi-p= roject/vncterm.git
wsproxy git://github.com/xapi-p= roject/wsproxy.git
xcp-eliloader git://github.com/= xapi-project/xcp-eliloader.git
xcp-guest-templates git://githu= b.com/xapi-project/xcp-guest-templates.git
xcp-idl git://github.com/xapi-p= roject/xcp-idl.git
xcp-storage-managers git://gith= ub.com/xapi-project/xcp-storage-managers.git
xen-api-backports git://github.= com/xapi-project/xen-api-backports.git
xen-api-client git://github.com= /xapi-project/xen-api-client.git
xen-api-libs-specs git://github= .com/xapi-project/xen-api-libs-specs.git
xen-api-libs-transitional git:/= /github.com/xapi-project/xen-api-libs-transitional.git
xs-pull-request-build-scripts g= it://github.com/xapi-project/xs-pull-request-build-scripts.git

=3D Detected forks in Mirage OS =3D
xen git://github.com/mirage/xen.git
mirari git://github.com/mirage/mirari= .git
ocaml-cohttp git://github.com/mirage/= ocaml-cohttp.git
ocaml-crypto-keys git://github.com/mi= rage/ocaml-crypto-keys.git
ocaml-cstruct git://github.com/mirage= /ocaml-cstruct.git
ocaml-dns git://github.com/mirage/oca= ml-dns.git
ocaml-openflow git://github.com/mirag= e/ocaml-openflow.git
ocaml-re git://github.com/mirage/ocam= l-re.git
ocaml-tuntap git://github.com/mirage/= ocaml-tuntap.git
ocaml-uri git://github.com/mirage/oca= ml-uri.git
ocaml-xenstore git://github.com/mirag= e/ocaml-xenstore.git
opam-repository git://github.com/mira= ge/opam-repository.git




-------- Original Message -------- =
Subject: Removing forks from the analysis
Date: Thu, 27 Mar 2014 14:36:06 +0100
From: Santiago Due=F1as <sduenas@bitergia.com>
To: = Lars Kurth <lars.kurth@xen.org>
CC: = citrix@lists.bitergia.com 


Hi again Lars,

during our analysis, we found that some of your git repos are forks from
upstream repositories. I don not know whether you talk to Manrique or
Jesus about that but I prefer to remember you which possibilities we
offer and which one we have follow.

The repositories that we have already analyzed are listed on the
scm-repos page:

http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repo=
s.html

We offer three possibilities for treating these cases:

- Do not analyze forks. This is the default option. We have removed from
the analysis those repositories marked as forks in Github and others
from upstream such as "ocaml" and "opam" series (see the attached file
that includes the full list of forks).

Probably, you will want to remove more. If this is your choice, please
have a look at the repositories page and send me an email with the list
of git repositories you want to remove from the analysis.

- Analyze forks. Take into account that this can affect the whole
numbers and stats, particularly if your team is not really active in
these repos.

- Analyze differences between upstream and local repositories. Due this
functionality is out of the basic dashboard, please talk to Manrique or
Jesus to get more details, if interested.

Santi
--=20
Santiago Due=F1as
sduenas@bitergia.com
Bitergia S.L.L


= <xen_forks.txt>________________________________________= _______
Xen-api mailing list
Xen-api@lists.xen.org
http://= lists.xen.org/cgi-bin/mailman/listinfo/xen-api

<= /div>= --Apple-Mail=_949F347A-B5C1-46B8-9307-CE8185BC36C4-- --===============4473929198037242640== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4473929198037242640==-- From xen-api-bounces@lists.xen.org Thu Mar 27 16:29:22 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 16:29:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTDAv-0006ZB-Iw; Thu, 27 Mar 2014 16:29:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTDAt-0006Z0-L2 for xen-api@lists.xen.org; Thu, 27 Mar 2014 16:29:04 +0000 Received: from [85.158.139.211:26209] by server-16.bemta-5.messagelabs.com id 27/B1-19700-EC154335; Thu, 27 Mar 2014 16:29:02 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-206.messagelabs.com!1395937739!3776914!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22134 invoked from network); 27 Mar 2014 16:28:59 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-206.messagelabs.com with SMTP; 27 Mar 2014 16:28:59 -0000 Received: (qmail 7780 invoked by uid 634); 27 Mar 2014 16:28:59 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 27 Mar 2014 16:28:58 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Anil Madhavapeddy In-Reply-To: <533450C5.5070005@xen.org> Date: Thu, 27 Mar 2014 16:28:57 +0000 Message-Id: <3A5650C9-9F0F-47F1-9204-4A90D1A04F9D@recoil.org> References: <1395927366.3749.13.camel@Guybrush> <533450C5.5070005@xen.org> To: lars.kurth@xen.org X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4473929198037242640==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============4473929198037242640== Content-Type: multipart/alternative; boundary="Apple-Mail=_949F347A-B5C1-46B8-9307-CE8185BC36C4" --Apple-Mail=_949F347A-B5C1-46B8-9307-CE8185BC36C4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Dave and I are currently going through our repository list to normalize = this for Mirage. https://github.com/mirage/mirage/issues/236 We'll update you shortly when the "trove" is completed. That will have = an authoritative list of libraries, as well as spotting any licensing = inconsistencies or incorrect fork orders. cheers, Anil On 27 Mar 2014, at 16:24, Lars Kurth wrote: > Hi all, >=20 > a while ago I kicked a conversation related to putting a dashboard for = the Xen project sub projects together. As it turns out there is an issue = in XAPI and MirageOS repositories on github. Some of them are forks of = upstreams, which are hard for the tool to analyze. My proposal would be = to *not analyse them* and include them into statistics. If I don't hear = any screams, then this will be the default. The list of forks detected = are listed below ... >=20 > Also, it would be good to let me know of any other repos that you dont = want to analyse. The full list is at = http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html = (note that there is 79 pages of them) which should be aggregated into = buckets for XAPI and opam >=20 > Regards > Lars >=20 > =3D Detected forks in XAPI Project =3D > xen-unstable-mirror = git://github.com/xapi-project/xen-unstable-mirror.git > PRDup git://github.com/xapi-project/PRDup.git > blktap-dkms git://github.com/xapi-project/blktap-dkms.git > cdrom git://github.com/xapi-project/cdrom.git > ffs git://github.com/xapi-project/ffs.git > libvhd git://github.com/xapi-project/libvhd.git > nbd git://github.com/xapi-project/nbd.git > netdev git://github.com/xapi-project/netdev.git > ocaml-fd-send-recv = git://github.com/xapi-project/ocaml-fd-send-recv.git > ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git > ocaml-sha git://github.com/xapi-project/ocaml-sha.git > ocaml-tar git://github.com/xapi-project/ocaml-tar.git > ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git > ocaml-xenstore-clients = git://github.com/xapi-project/ocaml-xenstore-clients.git > ocamltest git://github.com/xapi-project/ocamltest.git > oclock git://github.com/xapi-project/oclock.git > opam git://github.com/xapi-project/opam.git > opam-repository git://github.com/xapi-project/opam-repository.git > python-github2 git://github.com/xapi-project/python-github2.git > tapctl git://github.com/xapi-project/tapctl.git > vhd-tool git://github.com/xapi-project/vhd-tool.git > vncterm git://github.com/xapi-project/vncterm.git > wsproxy git://github.com/xapi-project/wsproxy.git > xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git > xcp-guest-templates = git://github.com/xapi-project/xcp-guest-templates.git > xcp-idl git://github.com/xapi-project/xcp-idl.git > xcp-storage-managers = git://github.com/xapi-project/xcp-storage-managers.git > xen-api-backports git://github.com/xapi-project/xen-api-backports.git > xen-api-client git://github.com/xapi-project/xen-api-client.git > xen-api-libs-specs = git://github.com/xapi-project/xen-api-libs-specs.git > xen-api-libs-transitional = git://github.com/xapi-project/xen-api-libs-transitional.git > xs-pull-request-build-scripts = git://github.com/xapi-project/xs-pull-request-build-scripts.git >=20 > =3D Detected forks in Mirage OS =3D > xen git://github.com/mirage/xen.git > mirari git://github.com/mirage/mirari.git > ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git > ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git > ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git > ocaml-dns git://github.com/mirage/ocaml-dns.git > ocaml-openflow git://github.com/mirage/ocaml-openflow.git > ocaml-re git://github.com/mirage/ocaml-re.git > ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git > ocaml-uri git://github.com/mirage/ocaml-uri.git > ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git > opam-repository git://github.com/mirage/opam-repository.git >=20 >=20 >=20 >=20 > -------- Original Message -------- > Subject: Removing forks from the analysis > Date: Thu, 27 Mar 2014 14:36:06 +0100 > From: Santiago Due=F1as > To: Lars Kurth > CC: citrix@lists.bitergia.com >=20 > Hi again Lars, >=20 > during our analysis, we found that some of your git repos are forks = from > upstream repositories. I don not know whether you talk to Manrique or > Jesus about that but I prefer to remember you which possibilities we > offer and which one we have follow. >=20 > The repositories that we have already analyzed are listed on the > scm-repos page: >=20 > = http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html >=20 > We offer three possibilities for treating these cases: >=20 > - Do not analyze forks. This is the default option. We have removed = from > the analysis those repositories marked as forks in Github and others > from upstream such as "ocaml" and "opam" series (see the attached file > that includes the full list of forks). >=20 > Probably, you will want to remove more. If this is your choice, please > have a look at the repositories page and send me an email with the = list > of git repositories you want to remove from the analysis. >=20 > - Analyze forks. Take into account that this can affect the whole > numbers and stats, particularly if your team is not really active in > these repos. >=20 > - Analyze differences between upstream and local repositories. Due = this > functionality is out of the basic dashboard, please talk to Manrique = or > Jesus to get more details, if interested. >=20 > Santi > --=20 > Santiago Due=F1as > sduenas@bitergia.com > Bitergia S.L.L >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-api mailing list > Xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --Apple-Mail=_949F347A-B5C1-46B8-9307-CE8185BC36C4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Dave = and I are currently going through our repository list to normalize this = for Mirage.


We'll update you = shortly when the "trove" is completed.  That will have an = authoritative list of libraries, as well as spotting any licensing = inconsistencies or incorrect fork = orders.

cheers,
Anil

On 27 Mar 2014, at 16:24, Lars Kurth <lars.kurth@xen.org> = wrote:

=20 =20
Hi all,

a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in  XAPI and MirageOS repositories on github. = Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below = ...

Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repo= s.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam

Regards
Lars

=3D Detected forks in XAPI Project =3D
xen-unstable-mirror git://githu= b.com/xapi-project/xen-unstable-mirror.git
PRDup git://github.com/xapi-pro= ject/PRDup.git
blktap-dkms git://github.com/xa= pi-project/blktap-dkms.git
cdrom git://github.com/xapi-pro= ject/cdrom.git
ffs git://github.com/xapi-proje= ct/ffs.git
libvhd git://github.com/xapi-pr= oject/libvhd.git
nbd git://github.com/xapi-proje= ct/nbd.git
netdev git://github.com/xapi-pr= oject/netdev.git
ocaml-fd-send-recv git://github= .com/xapi-project/ocaml-fd-send-recv.git
ocaml-opasswd git://github.com/= xapi-project/ocaml-opasswd.git
ocaml-sha git://github.com/xapi= -project/ocaml-sha.git
ocaml-tar git://github.com/xapi= -project/ocaml-tar.git
ocaml-vhd git://github.com/xapi= -project/ocaml-vhd.git
ocaml-xenstore-clients git://gi= thub.com/xapi-project/ocaml-xenstore-clients.git
ocamltest git://github.com/xapi= -project/ocamltest.git
oclock git://github.com/xapi-pr= oject/oclock.git
opam git://github.com/xapi-proj= ect/opam.git
opam-repository git://github.co= m/xapi-project/opam-repository.git
python-github2 git://github.com= /xapi-project/python-github2.git
tapctl git://github.com/xapi-pr= oject/tapctl.git
vhd-tool git://github.com/xapi-= project/vhd-tool.git
vncterm git://github.com/xapi-p= roject/vncterm.git
wsproxy git://github.com/xapi-p= roject/wsproxy.git
xcp-eliloader git://github.com/= xapi-project/xcp-eliloader.git
xcp-guest-templates git://githu= b.com/xapi-project/xcp-guest-templates.git
xcp-idl git://github.com/xapi-p= roject/xcp-idl.git
xcp-storage-managers git://gith= ub.com/xapi-project/xcp-storage-managers.git
xen-api-backports git://github.= com/xapi-project/xen-api-backports.git
xen-api-client git://github.com= /xapi-project/xen-api-client.git
xen-api-libs-specs git://github= .com/xapi-project/xen-api-libs-specs.git
xen-api-libs-transitional git:/= /github.com/xapi-project/xen-api-libs-transitional.git
xs-pull-request-build-scripts g= it://github.com/xapi-project/xs-pull-request-build-scripts.git

=3D Detected forks in Mirage OS =3D
xen git://github.com/mirage/xen.git
mirari git://github.com/mirage/mirari= .git
ocaml-cohttp git://github.com/mirage/= ocaml-cohttp.git
ocaml-crypto-keys git://github.com/mi= rage/ocaml-crypto-keys.git
ocaml-cstruct git://github.com/mirage= /ocaml-cstruct.git
ocaml-dns git://github.com/mirage/oca= ml-dns.git
ocaml-openflow git://github.com/mirag= e/ocaml-openflow.git
ocaml-re git://github.com/mirage/ocam= l-re.git
ocaml-tuntap git://github.com/mirage/= ocaml-tuntap.git
ocaml-uri git://github.com/mirage/oca= ml-uri.git
ocaml-xenstore git://github.com/mirag= e/ocaml-xenstore.git
opam-repository git://github.com/mira= ge/opam-repository.git




-------- Original Message -------- =
Subject: Removing forks from the analysis
Date: Thu, 27 Mar 2014 14:36:06 +0100
From: Santiago Due=F1as <sduenas@bitergia.com>
To: = Lars Kurth <lars.kurth@xen.org>
CC: = citrix@lists.bitergia.com 


Hi again Lars,

during our analysis, we found that some of your git repos are forks from
upstream repositories. I don not know whether you talk to Manrique or
Jesus about that but I prefer to remember you which possibilities we
offer and which one we have follow.

The repositories that we have already analyzed are listed on the
scm-repos page:

http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repo=
s.html

We offer three possibilities for treating these cases:

- Do not analyze forks. This is the default option. We have removed from
the analysis those repositories marked as forks in Github and others
from upstream such as "ocaml" and "opam" series (see the attached file
that includes the full list of forks).

Probably, you will want to remove more. If this is your choice, please
have a look at the repositories page and send me an email with the list
of git repositories you want to remove from the analysis.

- Analyze forks. Take into account that this can affect the whole
numbers and stats, particularly if your team is not really active in
these repos.

- Analyze differences between upstream and local repositories. Due this
functionality is out of the basic dashboard, please talk to Manrique or
Jesus to get more details, if interested.

Santi
--=20
Santiago Due=F1as
sduenas@bitergia.com
Bitergia S.L.L


= <xen_forks.txt>________________________________________= _______
Xen-api mailing list
Xen-api@lists.xen.org
http://= lists.xen.org/cgi-bin/mailman/listinfo/xen-api

<= /div>= --Apple-Mail=_949F347A-B5C1-46B8-9307-CE8185BC36C4-- --===============4473929198037242640== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============4473929198037242640==-- From xen-api-bounces@lists.xen.org Thu Mar 27 16:36:19 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 16:36:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTDHu-00073X-3h; Thu, 27 Mar 2014 16:36:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTDHs-00073E-I1 for xen-api@lists.xen.org; Thu, 27 Mar 2014 16:36:17 +0000 Received: from [193.109.254.147:35109] by server-10.bemta-14.messagelabs.com id 55/A8-04546-F7354335; Thu, 27 Mar 2014 16:36:15 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1395938172!4612446!1 X-Originating-IP: [74.125.82.50] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20702 invoked from network); 27 Mar 2014 16:36:13 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 16:36:13 -0000 Received: by mail-wg0-f50.google.com with SMTP id x13so2593679wgg.33 for ; Thu, 27 Mar 2014 09:36:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=Lr4KvMXBqrxxBTs2vtR0hilQCFou4lOo23zHJ+r/s3I=; b=uypzu6YvOvo6yol+d/ZPHDCr+VdCyHTgBXXcuFCKExBLOStJQyE0jadlsGcJHnkotQ knBu/EjvjXrNi99WiTXt2KdsRUHnqZY5gUbKiGj41t1y9dHyB3+9n8QyTmVIY4jLq9ew mOd7QgqPNquEYqo6i0zQlkaidbaS2Pf06skImK15NI8k3bshW51Z9nBhSiQJVQUH42sl uN3L5C2cEF62/Eq0CEH2xgSUw95JkA4HbSrTLnl9TufoFTFU6SKrHNL8rQF2q29SMcZ0 lLQBfO0ZLa3VyqLJrG7jephwR+eBQebyFPRV/amVwXRSkKWRumPiEK3XQFFKl6IBMALY kEXw== X-Received: by 10.180.38.41 with SMTP id d9mr6264841wik.9.1395938172772; Thu, 27 Mar 2014 09:36:12 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id q2sm10516780wix.5.2014.03.27.09.36.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Mar 2014 09:36:11 -0700 (PDT) Message-ID: <5334537A.1090306@xen.org> Date: Thu, 27 Mar 2014 16:36:10 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Anil Madhavapeddy References: <1395927366.3749.13.camel@Guybrush> <533450C5.5070005@xen.org> <3A5650C9-9F0F-47F1-9204-4A90D1A04F9D@recoil.org> In-Reply-To: <3A5650C9-9F0F-47F1-9204-4A90D1A04F9D@recoil.org> Cc: "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3359892235363968371==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3359892235363968371== Content-Type: multipart/alternative; boundary="------------080800010300060207020206" This is a multi-part message in MIME format. --------------080800010300060207020206 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit That would be fantastic. Please makes sure that the list you come up with has some sort of relation to the baseline. Aka "add xyz", remove "xyz". Otherwise it will be a pain for bitergia to do this and they may charge us extra Lars On 27/03/2014 16:28, Anil Madhavapeddy wrote: > Dave and I are currently going through our repository list to > normalize this for Mirage. > > https://github.com/mirage/mirage/issues/236 > > We'll update you shortly when the "trove" is completed. That will > have an authoritative list of libraries, as well as spotting any > licensing inconsistencies or incorrect fork orders. > > cheers, > Anil > > On 27 Mar 2014, at 16:24, Lars Kurth > wrote: > >> Hi all, >> >> a while ago I kicked a conversation related to putting a dashboard >> for the Xen project sub projects together. As it turns out there is >> an issue in XAPI and MirageOS repositories on github. Some of them >> are forks of upstreams, which are hard for the tool to analyze. My >> proposal would be to *not analyse them* and include them into >> statistics. If I don't hear any screams, then this will be the >> default. The list of forks detected are listed below ... >> >> Also, it would be good to let me know of any other repos that you >> dont want to analyse. The full list is at >> http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html >> (note that there is 79 pages of them) which should be aggregated into >> buckets for XAPI and opam >> >> Regards >> Lars >> >> = Detected forks in XAPI Project = >> xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git >> PRDup git://github.com/xapi-project/PRDup.git >> blktap-dkms git://github.com/xapi-project/blktap-dkms.git >> cdrom git://github.com/xapi-project/cdrom.git >> ffs git://github.com/xapi-project/ffs.git >> libvhd git://github.com/xapi-project/libvhd.git >> nbd git://github.com/xapi-project/nbd.git >> netdev git://github.com/xapi-project/netdev.git >> ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git >> ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git >> ocaml-sha git://github.com/xapi-project/ocaml-sha.git >> ocaml-tar git://github.com/xapi-project/ocaml-tar.git >> ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git >> ocaml-xenstore-clients >> git://github.com/xapi-project/ocaml-xenstore-clients.git >> ocamltest git://github.com/xapi-project/ocamltest.git >> oclock git://github.com/xapi-project/oclock.git >> opam git://github.com/xapi-project/opam.git >> opam-repository git://github.com/xapi-project/opam-repository.git >> python-github2 git://github.com/xapi-project/python-github2.git >> tapctl git://github.com/xapi-project/tapctl.git >> vhd-tool git://github.com/xapi-project/vhd-tool.git >> vncterm git://github.com/xapi-project/vncterm.git >> wsproxy git://github.com/xapi-project/wsproxy.git >> xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git >> xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git >> xcp-idl git://github.com/xapi-project/xcp-idl.git >> xcp-storage-managers >> git://github.com/xapi-project/xcp-storage-managers.git >> xen-api-backports git://github.com/xapi-project/xen-api-backports.git >> xen-api-client git://github.com/xapi-project/xen-api-client.git >> xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git >> xen-api-libs-transitional >> git://github.com/xapi-project/xen-api-libs-transitional.git >> xs-pull-request-build-scripts >> git://github.com/xapi-project/xs-pull-request-build-scripts.git >> >> = Detected forks in Mirage OS = >> xen git://github.com/mirage/xen.git >> mirari git://github.com/mirage/mirari.git >> ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git >> ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git >> ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git >> ocaml-dns git://github.com/mirage/ocaml-dns.git >> ocaml-openflow git://github.com/mirage/ocaml-openflow.git >> ocaml-re git://github.com/mirage/ocaml-re.git >> ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git >> ocaml-uri git://github.com/mirage/ocaml-uri.git >> ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git >> opam-repository git://github.com/mirage/opam-repository.git >> >> >> >> >> -------- Original Message -------- >> Subject: Removing forks from the analysis >> Date: Thu, 27 Mar 2014 14:36:06 +0100 >> From: Santiago Dueñas >> To: Lars Kurth >> CC: citrix@lists.bitergia.com >> >> >> >> Hi again Lars, >> >> during our analysis, we found that some of your git repos are forks from >> upstream repositories. I don not know whether you talk to Manrique or >> Jesus about that but I prefer to remember you which possibilities we >> offer and which one we have follow. >> >> The repositories that we have already analyzed are listed on the >> scm-repos page: >> >> http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html >> >> We offer three possibilities for treating these cases: >> >> - Do not analyze forks. This is the default option. We have removed from >> the analysis those repositories marked as forks in Github and others >> from upstream such as "ocaml" and "opam" series (see the attached file >> that includes the full list of forks). >> >> Probably, you will want to remove more. If this is your choice, please >> have a look at the repositories page and send me an email with the list >> of git repositories you want to remove from the analysis. >> >> - Analyze forks. Take into account that this can affect the whole >> numbers and stats, particularly if your team is not really active in >> these repos. >> >> - Analyze differences between upstream and local repositories. Due this >> functionality is out of the basic dashboard, please talk to Manrique or >> Jesus to get more details, if interested. >> >> Santi >> -- >> Santiago Dueñas >> sduenas@bitergia.com >> Bitergia S.L.L >> >> >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --------------080800010300060207020206 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit
That would be fantastic. Please makes sure that the list you come up with has some sort of relation to the baseline. Aka "add xyz", remove "xyz". Otherwise it will be a pain for bitergia to do this and they may charge us extra
Lars

On 27/03/2014 16:28, Anil Madhavapeddy wrote:
Dave and I are currently going through our repository list to normalize this for Mirage.


We'll update you shortly when the "trove" is completed.  That will have an authoritative list of libraries, as well as spotting any licensing inconsistencies or incorrect fork orders.

cheers,
Anil

On 27 Mar 2014, at 16:24, Lars Kurth <lars.kurth@xen.org> wrote:

Hi all,

a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in  XAPI and MirageOS repositories on github. Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below ...

Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam

Regards
Lars

= Detected forks in XAPI Project =
xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git
PRDup git://github.com/xapi-project/PRDup.git
blktap-dkms git://github.com/xapi-project/blktap-dkms.git
cdrom git://github.com/xapi-project/cdrom.git
ffs git://github.com/xapi-project/ffs.git
libvhd git://github.com/xapi-project/libvhd.git
nbd git://github.com/xapi-project/nbd.git
netdev git://github.com/xapi-project/netdev.git
ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git
ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git
ocaml-sha git://github.com/xapi-project/ocaml-sha.git
ocaml-tar git://github.com/xapi-project/ocaml-tar.git
ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git
ocaml-xenstore-clients git://github.com/xapi-project/ocaml-xenstore-clients.git
ocamltest git://github.com/xapi-project/ocamltest.git
oclock git://github.com/xapi-project/oclock.git
opam git://github.com/xapi-project/opam.git
opam-repository git://github.com/xapi-project/opam-repository.git
python-github2 git://github.com/xapi-project/python-github2.git
tapctl git://github.com/xapi-project/tapctl.git
vhd-tool git://github.com/xapi-project/vhd-tool.git
vncterm git://github.com/xapi-project/vncterm.git
wsproxy git://github.com/xapi-project/wsproxy.git
xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git
xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git
xcp-idl git://github.com/xapi-project/xcp-idl.git
xcp-storage-managers git://github.com/xapi-project/xcp-storage-managers.git
xen-api-backports git://github.com/xapi-project/xen-api-backports.git
xen-api-client git://github.com/xapi-project/xen-api-client.git
xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git
xen-api-libs-transitional git://github.com/xapi-project/xen-api-libs-transitional.git
xs-pull-request-build-scripts git://github.com/xapi-project/xs-pull-request-build-scripts.git

= Detected forks in Mirage OS =
xen git://github.com/mirage/xen.git
mirari git://github.com/mirage/mirari.git
ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git
ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git
ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git
ocaml-dns git://github.com/mirage/ocaml-dns.git
ocaml-openflow git://github.com/mirage/ocaml-openflow.git
ocaml-re git://github.com/mirage/ocaml-re.git
ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git
ocaml-uri git://github.com/mirage/ocaml-uri.git
ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git
opam-repository git://github.com/mirage/opam-repository.git




-------- Original Message --------
Subject: Removing forks from the analysis
Date: Thu, 27 Mar 2014 14:36:06 +0100
From: Santiago Dueñas <sduenas@bitergia.com>
To: Lars Kurth <lars.kurth@xen.org>
CC: citrix@lists.bitergia.com 


Hi again Lars,

during our analysis, we found that some of your git repos are forks from
upstream repositories. I don not know whether you talk to Manrique or
Jesus about that but I prefer to remember you which possibilities we
offer and which one we have follow.

The repositories that we have already analyzed are listed on the
scm-repos page:

http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html

We offer three possibilities for treating these cases:

- Do not analyze forks. This is the default option. We have removed from
the analysis those repositories marked as forks in Github and others
from upstream such as "ocaml" and "opam" series (see the attached file
that includes the full list of forks).

Probably, you will want to remove more. If this is your choice, please
have a look at the repositories page and send me an email with the list
of git repositories you want to remove from the analysis.

- Analyze forks. Take into account that this can affect the whole
numbers and stats, particularly if your team is not really active in
these repos.

- Analyze differences between upstream and local repositories. Due this
functionality is out of the basic dashboard, please talk to Manrique or
Jesus to get more details, if interested.

Santi
-- 
Santiago Dueñas
sduenas@bitergia.com
Bitergia S.L.L


<xen_forks.txt>_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--------------080800010300060207020206-- --===============3359892235363968371== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3359892235363968371==-- From xen-api-bounces@lists.xen.org Thu Mar 27 16:36:19 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 27 Mar 2014 16:36:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTDHu-00073X-3h; Thu, 27 Mar 2014 16:36:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WTDHs-00073E-I1 for xen-api@lists.xen.org; Thu, 27 Mar 2014 16:36:17 +0000 Received: from [193.109.254.147:35109] by server-10.bemta-14.messagelabs.com id 55/A8-04546-F7354335; Thu, 27 Mar 2014 16:36:15 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1395938172!4612446!1 X-Originating-IP: [74.125.82.50] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20702 invoked from network); 27 Mar 2014 16:36:13 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2014 16:36:13 -0000 Received: by mail-wg0-f50.google.com with SMTP id x13so2593679wgg.33 for ; Thu, 27 Mar 2014 09:36:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type; bh=Lr4KvMXBqrxxBTs2vtR0hilQCFou4lOo23zHJ+r/s3I=; b=uypzu6YvOvo6yol+d/ZPHDCr+VdCyHTgBXXcuFCKExBLOStJQyE0jadlsGcJHnkotQ knBu/EjvjXrNi99WiTXt2KdsRUHnqZY5gUbKiGj41t1y9dHyB3+9n8QyTmVIY4jLq9ew mOd7QgqPNquEYqo6i0zQlkaidbaS2Pf06skImK15NI8k3bshW51Z9nBhSiQJVQUH42sl uN3L5C2cEF62/Eq0CEH2xgSUw95JkA4HbSrTLnl9TufoFTFU6SKrHNL8rQF2q29SMcZ0 lLQBfO0ZLa3VyqLJrG7jephwR+eBQebyFPRV/amVwXRSkKWRumPiEK3XQFFKl6IBMALY kEXw== X-Received: by 10.180.38.41 with SMTP id d9mr6264841wik.9.1395938172772; Thu, 27 Mar 2014 09:36:12 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id q2sm10516780wix.5.2014.03.27.09.36.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 27 Mar 2014 09:36:11 -0700 (PDT) Message-ID: <5334537A.1090306@xen.org> Date: Thu, 27 Mar 2014 16:36:10 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Anil Madhavapeddy References: <1395927366.3749.13.camel@Guybrush> <533450C5.5070005@xen.org> <3A5650C9-9F0F-47F1-9204-4A90D1A04F9D@recoil.org> In-Reply-To: <3A5650C9-9F0F-47F1-9204-4A90D1A04F9D@recoil.org> Cc: "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] Issues and questions related to contribution metrics dashboard for XAPI and Mirage OS X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3359892235363968371==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3359892235363968371== Content-Type: multipart/alternative; boundary="------------080800010300060207020206" This is a multi-part message in MIME format. --------------080800010300060207020206 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit That would be fantastic. Please makes sure that the list you come up with has some sort of relation to the baseline. Aka "add xyz", remove "xyz". Otherwise it will be a pain for bitergia to do this and they may charge us extra Lars On 27/03/2014 16:28, Anil Madhavapeddy wrote: > Dave and I are currently going through our repository list to > normalize this for Mirage. > > https://github.com/mirage/mirage/issues/236 > > We'll update you shortly when the "trove" is completed. That will > have an authoritative list of libraries, as well as spotting any > licensing inconsistencies or incorrect fork orders. > > cheers, > Anil > > On 27 Mar 2014, at 16:24, Lars Kurth > wrote: > >> Hi all, >> >> a while ago I kicked a conversation related to putting a dashboard >> for the Xen project sub projects together. As it turns out there is >> an issue in XAPI and MirageOS repositories on github. Some of them >> are forks of upstreams, which are hard for the tool to analyze. My >> proposal would be to *not analyse them* and include them into >> statistics. If I don't hear any screams, then this will be the >> default. The list of forks detected are listed below ... >> >> Also, it would be good to let me know of any other repos that you >> dont want to analyse. The full list is at >> http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html >> (note that there is 79 pages of them) which should be aggregated into >> buckets for XAPI and opam >> >> Regards >> Lars >> >> = Detected forks in XAPI Project = >> xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git >> PRDup git://github.com/xapi-project/PRDup.git >> blktap-dkms git://github.com/xapi-project/blktap-dkms.git >> cdrom git://github.com/xapi-project/cdrom.git >> ffs git://github.com/xapi-project/ffs.git >> libvhd git://github.com/xapi-project/libvhd.git >> nbd git://github.com/xapi-project/nbd.git >> netdev git://github.com/xapi-project/netdev.git >> ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git >> ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git >> ocaml-sha git://github.com/xapi-project/ocaml-sha.git >> ocaml-tar git://github.com/xapi-project/ocaml-tar.git >> ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git >> ocaml-xenstore-clients >> git://github.com/xapi-project/ocaml-xenstore-clients.git >> ocamltest git://github.com/xapi-project/ocamltest.git >> oclock git://github.com/xapi-project/oclock.git >> opam git://github.com/xapi-project/opam.git >> opam-repository git://github.com/xapi-project/opam-repository.git >> python-github2 git://github.com/xapi-project/python-github2.git >> tapctl git://github.com/xapi-project/tapctl.git >> vhd-tool git://github.com/xapi-project/vhd-tool.git >> vncterm git://github.com/xapi-project/vncterm.git >> wsproxy git://github.com/xapi-project/wsproxy.git >> xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git >> xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git >> xcp-idl git://github.com/xapi-project/xcp-idl.git >> xcp-storage-managers >> git://github.com/xapi-project/xcp-storage-managers.git >> xen-api-backports git://github.com/xapi-project/xen-api-backports.git >> xen-api-client git://github.com/xapi-project/xen-api-client.git >> xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git >> xen-api-libs-transitional >> git://github.com/xapi-project/xen-api-libs-transitional.git >> xs-pull-request-build-scripts >> git://github.com/xapi-project/xs-pull-request-build-scripts.git >> >> = Detected forks in Mirage OS = >> xen git://github.com/mirage/xen.git >> mirari git://github.com/mirage/mirari.git >> ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git >> ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git >> ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git >> ocaml-dns git://github.com/mirage/ocaml-dns.git >> ocaml-openflow git://github.com/mirage/ocaml-openflow.git >> ocaml-re git://github.com/mirage/ocaml-re.git >> ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git >> ocaml-uri git://github.com/mirage/ocaml-uri.git >> ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git >> opam-repository git://github.com/mirage/opam-repository.git >> >> >> >> >> -------- Original Message -------- >> Subject: Removing forks from the analysis >> Date: Thu, 27 Mar 2014 14:36:06 +0100 >> From: Santiago Dueñas >> To: Lars Kurth >> CC: citrix@lists.bitergia.com >> >> >> >> Hi again Lars, >> >> during our analysis, we found that some of your git repos are forks from >> upstream repositories. I don not know whether you talk to Manrique or >> Jesus about that but I prefer to remember you which possibilities we >> offer and which one we have follow. >> >> The repositories that we have already analyzed are listed on the >> scm-repos page: >> >> http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html >> >> We offer three possibilities for treating these cases: >> >> - Do not analyze forks. This is the default option. We have removed from >> the analysis those repositories marked as forks in Github and others >> from upstream such as "ocaml" and "opam" series (see the attached file >> that includes the full list of forks). >> >> Probably, you will want to remove more. If this is your choice, please >> have a look at the repositories page and send me an email with the list >> of git repositories you want to remove from the analysis. >> >> - Analyze forks. Take into account that this can affect the whole >> numbers and stats, particularly if your team is not really active in >> these repos. >> >> - Analyze differences between upstream and local repositories. Due this >> functionality is out of the basic dashboard, please talk to Manrique or >> Jesus to get more details, if interested. >> >> Santi >> -- >> Santiago Dueñas >> sduenas@bitergia.com >> Bitergia S.L.L >> >> >> >> >> _______________________________________________ >> Xen-api mailing list >> Xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --------------080800010300060207020206 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit
That would be fantastic. Please makes sure that the list you come up with has some sort of relation to the baseline. Aka "add xyz", remove "xyz". Otherwise it will be a pain for bitergia to do this and they may charge us extra
Lars

On 27/03/2014 16:28, Anil Madhavapeddy wrote:
Dave and I are currently going through our repository list to normalize this for Mirage.


We'll update you shortly when the "trove" is completed.  That will have an authoritative list of libraries, as well as spotting any licensing inconsistencies or incorrect fork orders.

cheers,
Anil

On 27 Mar 2014, at 16:24, Lars Kurth <lars.kurth@xen.org> wrote:

Hi all,

a while ago I kicked a conversation related to putting a dashboard for the Xen project sub projects together. As it turns out there is an issue in  XAPI and MirageOS repositories on github. Some of them are forks of upstreams, which are hard for the tool to analyze. My proposal would be to *not analyse them* and include them into statistics. If I don't hear any screams, then this will be the default. The list of forks detected are listed below ...

Also, it would be good to let me know of any other repos that you dont want to analyse. The full list is at http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html (note that there is 79 pages of them) which should be aggregated into buckets for XAPI and opam

Regards
Lars

= Detected forks in XAPI Project =
xen-unstable-mirror git://github.com/xapi-project/xen-unstable-mirror.git
PRDup git://github.com/xapi-project/PRDup.git
blktap-dkms git://github.com/xapi-project/blktap-dkms.git
cdrom git://github.com/xapi-project/cdrom.git
ffs git://github.com/xapi-project/ffs.git
libvhd git://github.com/xapi-project/libvhd.git
nbd git://github.com/xapi-project/nbd.git
netdev git://github.com/xapi-project/netdev.git
ocaml-fd-send-recv git://github.com/xapi-project/ocaml-fd-send-recv.git
ocaml-opasswd git://github.com/xapi-project/ocaml-opasswd.git
ocaml-sha git://github.com/xapi-project/ocaml-sha.git
ocaml-tar git://github.com/xapi-project/ocaml-tar.git
ocaml-vhd git://github.com/xapi-project/ocaml-vhd.git
ocaml-xenstore-clients git://github.com/xapi-project/ocaml-xenstore-clients.git
ocamltest git://github.com/xapi-project/ocamltest.git
oclock git://github.com/xapi-project/oclock.git
opam git://github.com/xapi-project/opam.git
opam-repository git://github.com/xapi-project/opam-repository.git
python-github2 git://github.com/xapi-project/python-github2.git
tapctl git://github.com/xapi-project/tapctl.git
vhd-tool git://github.com/xapi-project/vhd-tool.git
vncterm git://github.com/xapi-project/vncterm.git
wsproxy git://github.com/xapi-project/wsproxy.git
xcp-eliloader git://github.com/xapi-project/xcp-eliloader.git
xcp-guest-templates git://github.com/xapi-project/xcp-guest-templates.git
xcp-idl git://github.com/xapi-project/xcp-idl.git
xcp-storage-managers git://github.com/xapi-project/xcp-storage-managers.git
xen-api-backports git://github.com/xapi-project/xen-api-backports.git
xen-api-client git://github.com/xapi-project/xen-api-client.git
xen-api-libs-specs git://github.com/xapi-project/xen-api-libs-specs.git
xen-api-libs-transitional git://github.com/xapi-project/xen-api-libs-transitional.git
xs-pull-request-build-scripts git://github.com/xapi-project/xs-pull-request-build-scripts.git

= Detected forks in Mirage OS =
xen git://github.com/mirage/xen.git
mirari git://github.com/mirage/mirari.git
ocaml-cohttp git://github.com/mirage/ocaml-cohttp.git
ocaml-crypto-keys git://github.com/mirage/ocaml-crypto-keys.git
ocaml-cstruct git://github.com/mirage/ocaml-cstruct.git
ocaml-dns git://github.com/mirage/ocaml-dns.git
ocaml-openflow git://github.com/mirage/ocaml-openflow.git
ocaml-re git://github.com/mirage/ocaml-re.git
ocaml-tuntap git://github.com/mirage/ocaml-tuntap.git
ocaml-uri git://github.com/mirage/ocaml-uri.git
ocaml-xenstore git://github.com/mirage/ocaml-xenstore.git
opam-repository git://github.com/mirage/opam-repository.git




-------- Original Message --------
Subject: Removing forks from the analysis
Date: Thu, 27 Mar 2014 14:36:06 +0100
From: Santiago Dueñas <sduenas@bitergia.com>
To: Lars Kurth <lars.kurth@xen.org>
CC: citrix@lists.bitergia.com 


Hi again Lars,

during our analysis, we found that some of your git repos are forks from
upstream repositories. I don not know whether you talk to Manrique or
Jesus about that but I prefer to remember you which possibilities we
offer and which one we have follow.

The repositories that we have already analyzed are listed on the
scm-repos page:

http://bitergia.com/projects/citrix-xen-dashboard/browser/scm-repos.html

We offer three possibilities for treating these cases:

- Do not analyze forks. This is the default option. We have removed from
the analysis those repositories marked as forks in Github and others
from upstream such as "ocaml" and "opam" series (see the attached file
that includes the full list of forks).

Probably, you will want to remove more. If this is your choice, please
have a look at the repositories page and send me an email with the list
of git repositories you want to remove from the analysis.

- Analyze forks. Take into account that this can affect the whole
numbers and stats, particularly if your team is not really active in
these repos.

- Analyze differences between upstream and local repositories. Due this
functionality is out of the basic dashboard, please talk to Manrique or
Jesus to get more details, if interested.

Santi
-- 
Santiago Dueñas
sduenas@bitergia.com
Bitergia S.L.L


<xen_forks.txt>_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


--------------080800010300060207020206-- --===============3359892235363968371== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============3359892235363968371==-- From xen-api-bounces@lists.xen.org Mon Mar 31 07:47:13 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 31 Mar 2014 07:47:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WUWvn-0000I7-6e; Mon, 31 Mar 2014 07:46:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WUWvl-0000Hm-L1; Mon, 31 Mar 2014 07:46:53 +0000 Received: from [85.158.139.211:41002] by server-14.bemta-5.messagelabs.com id 1E/9E-15696-C6D19335; Mon, 31 Mar 2014 07:46:52 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1396252010!4334416!1 X-Originating-IP: [74.125.82.176] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25478 invoked from network); 31 Mar 2014 07:46:50 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 31 Mar 2014 07:46:50 -0000 Received: by mail-we0-f176.google.com with SMTP id x48so4266825wes.21 for ; Mon, 31 Mar 2014 00:46:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=4VgPQxj9QoFIPBkQOYejUud+TqdxBrbTfhffSa8NAv4=; b=OxD3+CLWobZoasYZ5HdEOXuPMi4eHQMD3rUPgCyknap9RFN2jgIivaG9+P9qWFhnyg rNiWYVPvqU0+ZRj/LIWWc+j4Mwcr8pI/1vg8eo0DG064M4w5IJFIQERp48ZZ3sIAx9Q3 qkcBz56Eqv1Qwtfc40RB/UgKjXBZWyxlYgTcBbK4c8mVaKsCz5RCZCJ/nT58qh/aneZK 5zyZ5aqme/hf27c3yTeCvwVpLMjitODqKZCqY0rqgL13ZW/iK5dJqbheABuTNpY6vkPx /Xut+R6UgIFVoCLcOizPY6dGL345nZmHosdPfOehaGFQd1DxRpsA1RBNy8ftaiOubzXs K2cw== X-Received: by 10.194.77.50 with SMTP id p18mr2315709wjw.68.1396252010249; Mon, 31 Mar 2014 00:46:50 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id t18sm25039800wiv.16.2014.03.31.00.46.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 31 Mar 2014 00:46:49 -0700 (PDT) Message-ID: <53391D67.1070700@xen.org> Date: Mon, 31 Mar 2014 08:46:47 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [Xen-API] Xen Project Document Day is Today X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0915440893427453816==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0915440893427453816== Content-Type: multipart/alternative; boundary="------------000504090908070508000104" This is a multi-part message in MIME format. --------------000504090908070508000104 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, just a quick reminder that Xen Project Document Day is today. Our TODO list is at http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO We will be hanging out on Freenode channel #xendocs - please join I will see whether I can somehow fix Chrome rendering (see http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Sidebar_rendering_in_Chrome_.28broken_again.29). One of the last Chome updates messed up the wiki layout for older mediawiki instances. For Xen Project Hypervisor Developers ================================= Good things to work on are http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO#Xen_4.4_Documentation ... I will pick up http://wiki.xenproject.org/wiki/Xen_4.4_Acknowledgements Also, someone needs to have a quick look over http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Update_Xen_Repositories and ACK whether the changers Russell made are OK. For XAPI Developers ================== As you may recall, we had a vote to migrate XCP binaries and related documentation from Xen Project to XenServer.org. XenServer.org will have a wiki ( https://wiki.xenserver.org ), which is not quite live yet. The plan of record is to export all articles on the Xen Project wiki that are in the XCP category, and export them to https://wiki.xenserver.org/index.php?title=Category:XCP. And then point or redirect from old Xen Project pages to the new ones. Russell has investigated this earlier and it works well. Thus, I will review the categories http://wiki.xenproject.org/wiki/Category:XAPI_Devel Devel & http://wiki.xenproject.org/wiki/Category:XAPI_Users for correctness and make them more prominent on the Xen Project wiki front page. This is related to http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO#Restructure_XCP_Related_Categories ... please feel free to participate and help out For Mirage OS Developers ======================= There is fairly little on Mirage OS on the xen project wiki. http://wiki.xenproject.org/wiki/Category:Mirage is all but a shell. Maybe you want to start addressing this. Also, I am proposing to rename the category from Mirage to MirageOS. See you on IRC Lars --------------000504090908070508000104 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

just a quick reminder that Xen Project Document Day is today. Our TODO list is at http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO
We will be hanging out on Freenode channel #xendocs - please join

I will see whether I can somehow fix Chrome rendering (see http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Sidebar_rendering_in_Chrome_.28broken_again.29). One of the last Chome updates messed up the wiki layout for older mediawiki instances.

For Xen Project Hypervisor Developers
=================================
Good things to work on are http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO#Xen_4.4_Documentation ... I will pick up http://wiki.xenproject.org/wiki/Xen_4.4_Acknowledgements

Also, someone needs to have a quick look over http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Update_Xen_Repositories and ACK whether the changers Russell made are OK.

For XAPI Developers
==================
As you may recall, we had a vote to migrate XCP binaries and related documentation from Xen Project to XenServer.org. XenServer.org will have a wiki ( https://wiki.xenserver.org), which is not quite live yet. The plan of record is to export all articles on the Xen Project wiki that are in the XCP category, and export them to https://wiki.xenserver.org/index.php?title=Category:XCP. And then point or redirect from old Xen Project pages to the new ones. Russell has investigated this earlier and it works well.

Thus, I will review the categories http://wiki.xenproject.org/wiki/Category:XAPI_Devel Devel & http://wiki.xenproject.org/wiki/Category:XAPI_Users for correctness and make them more prominent on the Xen Project wiki front page.

This is related to http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO#Restructure_XCP_Related_Categories ... please feel free to participate and help out

For  Mirage OS Developers
=======================
There is fairly little on Mirage OS on the xen project wiki. http://wiki.xenproject.org/wiki/Category:Mirage is all but a shell. Maybe you want to start addressing this. Also, I am proposing to rename the category from Mirage to MirageOS.

See you on IRC
Lars

--------------000504090908070508000104-- --===============0915440893427453816== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0915440893427453816==-- From xen-api-bounces@lists.xen.org Mon Mar 31 07:47:13 2014 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 31 Mar 2014 07:47:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WUWvn-0000I7-6e; Mon, 31 Mar 2014 07:46:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WUWvl-0000Hm-L1; Mon, 31 Mar 2014 07:46:53 +0000 Received: from [85.158.139.211:41002] by server-14.bemta-5.messagelabs.com id 1E/9E-15696-C6D19335; Mon, 31 Mar 2014 07:46:52 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1396252010!4334416!1 X-Originating-IP: [74.125.82.176] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25478 invoked from network); 31 Mar 2014 07:46:50 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 31 Mar 2014 07:46:50 -0000 Received: by mail-we0-f176.google.com with SMTP id x48so4266825wes.21 for ; Mon, 31 Mar 2014 00:46:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=4VgPQxj9QoFIPBkQOYejUud+TqdxBrbTfhffSa8NAv4=; b=OxD3+CLWobZoasYZ5HdEOXuPMi4eHQMD3rUPgCyknap9RFN2jgIivaG9+P9qWFhnyg rNiWYVPvqU0+ZRj/LIWWc+j4Mwcr8pI/1vg8eo0DG064M4w5IJFIQERp48ZZ3sIAx9Q3 qkcBz56Eqv1Qwtfc40RB/UgKjXBZWyxlYgTcBbK4c8mVaKsCz5RCZCJ/nT58qh/aneZK 5zyZ5aqme/hf27c3yTeCvwVpLMjitODqKZCqY0rqgL13ZW/iK5dJqbheABuTNpY6vkPx /Xut+R6UgIFVoCLcOizPY6dGL345nZmHosdPfOehaGFQd1DxRpsA1RBNy8ftaiOubzXs K2cw== X-Received: by 10.194.77.50 with SMTP id p18mr2315709wjw.68.1396252010249; Mon, 31 Mar 2014 00:46:50 -0700 (PDT) Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205]) by mx.google.com with ESMTPSA id t18sm25039800wiv.16.2014.03.31.00.46.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 31 Mar 2014 00:46:49 -0700 (PDT) Message-ID: <53391D67.1070700@xen.org> Date: Mon, 31 Mar 2014 08:46:47 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [Xen-API] Xen Project Document Day is Today X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: User and development list for XCP and XAPI List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0915440893427453816==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0915440893427453816== Content-Type: multipart/alternative; boundary="------------000504090908070508000104" This is a multi-part message in MIME format. --------------000504090908070508000104 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, just a quick reminder that Xen Project Document Day is today. Our TODO list is at http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO We will be hanging out on Freenode channel #xendocs - please join I will see whether I can somehow fix Chrome rendering (see http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Sidebar_rendering_in_Chrome_.28broken_again.29). One of the last Chome updates messed up the wiki layout for older mediawiki instances. For Xen Project Hypervisor Developers ================================= Good things to work on are http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO#Xen_4.4_Documentation ... I will pick up http://wiki.xenproject.org/wiki/Xen_4.4_Acknowledgements Also, someone needs to have a quick look over http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Update_Xen_Repositories and ACK whether the changers Russell made are OK. For XAPI Developers ================== As you may recall, we had a vote to migrate XCP binaries and related documentation from Xen Project to XenServer.org. XenServer.org will have a wiki ( https://wiki.xenserver.org ), which is not quite live yet. The plan of record is to export all articles on the Xen Project wiki that are in the XCP category, and export them to https://wiki.xenserver.org/index.php?title=Category:XCP. And then point or redirect from old Xen Project pages to the new ones. Russell has investigated this earlier and it works well. Thus, I will review the categories http://wiki.xenproject.org/wiki/Category:XAPI_Devel Devel & http://wiki.xenproject.org/wiki/Category:XAPI_Users for correctness and make them more prominent on the Xen Project wiki front page. This is related to http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO#Restructure_XCP_Related_Categories ... please feel free to participate and help out For Mirage OS Developers ======================= There is fairly little on Mirage OS on the xen project wiki. http://wiki.xenproject.org/wiki/Category:Mirage is all but a shell. Maybe you want to start addressing this. Also, I am proposing to rename the category from Mirage to MirageOS. See you on IRC Lars --------------000504090908070508000104 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all,

just a quick reminder that Xen Project Document Day is today. Our TODO list is at http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO
We will be hanging out on Freenode channel #xendocs - please join

I will see whether I can somehow fix Chrome rendering (see http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Sidebar_rendering_in_Chrome_.28broken_again.29). One of the last Chome updates messed up the wiki layout for older mediawiki instances.

For Xen Project Hypervisor Developers
=================================
Good things to work on are http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO#Xen_4.4_Documentation ... I will pick up http://wiki.xenproject.org/wiki/Xen_4.4_Acknowledgements

Also, someone needs to have a quick look over http://wiki.xen.org/wiki/Xen_Document_Days/TODO#Update_Xen_Repositories and ACK whether the changers Russell made are OK.

For XAPI Developers
==================
As you may recall, we had a vote to migrate XCP binaries and related documentation from Xen Project to XenServer.org. XenServer.org will have a wiki ( https://wiki.xenserver.org), which is not quite live yet. The plan of record is to export all articles on the Xen Project wiki that are in the XCP category, and export them to https://wiki.xenserver.org/index.php?title=Category:XCP. And then point or redirect from old Xen Project pages to the new ones. Russell has investigated this earlier and it works well.

Thus, I will review the categories http://wiki.xenproject.org/wiki/Category:XAPI_Devel Devel & http://wiki.xenproject.org/wiki/Category:XAPI_Users for correctness and make them more prominent on the Xen Project wiki front page.

This is related to http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO#Restructure_XCP_Related_Categories ... please feel free to participate and help out

For  Mirage OS Developers
=======================
There is fairly little on Mirage OS on the xen project wiki. http://wiki.xenproject.org/wiki/Category:Mirage is all but a shell. Maybe you want to start addressing this. Also, I am proposing to rename the category from Mirage to MirageOS.

See you on IRC
Lars

--------------000504090908070508000104-- --===============0915440893427453816== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --===============0915440893427453816==--