From xen-api-bounces@lists.xen.org Thu Mar 01 16:10:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 01 Mar 2012 16:10: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 1S38Zq-0006eO-UE; Thu, 01 Mar 2012 16:09:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S38Zp-0006eA-Hw for xen-api@lists.xensource.com; Thu, 01 Mar 2012 16:09:57 +0000 Received: from [85.158.138.51:64285] by server-1.bemta-3.messagelabs.com id A9/C0-02415-45F9F4F4; Thu, 01 Mar 2012 16:09:56 +0000 X-Env-Sender: Andrei.Lifchits@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1330618195!13837301!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4NjQ2Mw==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3563 invoked from network); 1 Mar 2012 16:09:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2012 16:09:56 -0000 X-IronPort-AV: E=Sophos;i="4.73,511,1325462400"; d="scan'208,217";a="11039425" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Mar 2012 16:09:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 1 Mar 2012 16:09:55 +0000 From: Andrei Lifchits To: "xen-api (xen-api@lists.xensource.com)" Date: Thu, 1 Mar 2012 16:09:54 +0000 Thread-Topic: [Xen-API] vhd_read_short_footer failed Thread-Index: Acz3ubtlS29lR269SQ2IieZFczbsSAACzjlw Message-ID: References: <4F4EAA4A.9090700@gmail.com> <77CE58D6-669D-4B9F-AC8C-DE7F9A9BD136@eu.citrix.com> In-Reply-To: <77CE58D6-669D-4B9F-AC8C-DE7F9A9BD136@eu.citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] vhd_read_short_footer failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5399956017448078542==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5399956017448078542== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B45B24330584FB4AAE78E08B8F5E5B5ECBF51EDD5ELONPMAILBOX01_" --_000_B45B24330584FB4AAE78E08B8F5E5B5ECBF51EDD5ELONPMAILBOX01_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgR2VvcmdlLA0KDQpUaGlzIGNvdWxkIGhhcHBlbiBpZiB0aGUgTG9naWNhbCBWb2x1bWUgd2Fz IGluY29ycmVjdGx5IHJlc2l6ZWQgKGUuZy4gbWFudWFsbHkpLiBUaGUgbWVzc2FnZXMgbG9nIG1p Z2h0IGdpdmUgeW91IHNvbWUgbW9yZSBpbmZvcm1hdGlvbi4gQ2hlY2sgdGhhdCB0aGUgTFYgc2l6 ZSBjb3JyZXNwb25kcyB0byB0aGUgdmlydHVhbCBzaXplLiBJdCBjb3VsZCBhbHNvIGJlIGEgZ2Vu dWluZSBjb3JydXB0aW9uIGZvciBzb21lIG90aGVyIHJlYXNvbi4gV2hhdCB3ZXJlIHlvdSBkb2lu ZyB3aGVuIHlvdSBnb3QgdGhpcyBlcnJvcj8NCg0KQW5kcmVpDQoNCkZyb206IEdlb3JnZSBTaHVr bGluIDxnZW9yZ2Uuc2h1a2xpbkBnbWFpbC5jb208bWFpbHRvOmdlb3JnZS5zaHVrbGluQGdtYWls LmNvbT4+DQpEYXRlOiBGZWJydWFyeSAyOSwgMjAxMiAxMDo0NDoyNiBQTSBHTVQNClRvOiAieGVu LWFwaUBsaXN0cy54ZW5zb3VyY2UuY29tPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbnNvdXJjZS5j b20+IiA8eGVuLWFwaUBsaXN0cy54ZW5zb3VyY2UuY29tPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhl bnNvdXJjZS5jb20+Pg0KU3ViamVjdDogW1hlbi1BUEldIHZoZF9yZWFkX3Nob3J0X2Zvb3RlciBm YWlsZWQNCkdvb2QgZGF5Lg0KDQpHb3QgbWVzc2FnZSBmb3IgZmV3IFZESSdzOg0KDQp2aGQtdXRp bDogbGlidmhkOjp2aGRfcmVhZF9mb290ZXJfYXQ6DQovZGV2L1ZHX1hlblN0b3JhZ2UtMTAyMTQ3 NjMtNzE4MS05OTgwLWIwYjUtNjg4YzkwMGM0ODJhL1ZIRC05NWUyODUxNy1jMDYzLTQwYzEtYjJk Yi0yMGVjZWFkZmFlMTQ6DQpyZWFkaW5nIGZvb3RlciBhdCAweDQwMjdmZmUwMCBmYWlsZWQ6IC0y Mg0KDQpJJ20gbm90IHJlYWxseSB3ZWxsIHVuZGVyc3RhbmQgdGhlaXIgbWVhbmluZy4uLiBJcyBW SEQgY2hhaW4gYnJva2VuPyBPcg0Kc29tZXRoaW5nIGVsc2U/IEkgZ290IHRoZW0gZm9yIFZESSBv biBJU0NTSSBTUiB3aXRob3V0IHNuYXBzaG90ZXMuLi4NCg0KDQoNCl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQp4ZW4tYXBpIG1haWxpbmcgbGlzdA0KeGVu LWFwaUBsaXN0cy54ZW4ub3JnPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbi5vcmc+DQpodHRwOi8v bGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQ0K --_000_B45B24330584FB4AAE78E08B8F5E5B5ECBF51EDD5ELONPMAILBOX01_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5 OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZp bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0 LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj b3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNv QWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxv b24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm b250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNw YW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkJh bGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1z by1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglm b250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNv LXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3Jk U2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGlu IDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9z dHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVk aXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28g OV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJl ZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPjwvaGVh ZD48Ym9keSBiZ2NvbG9yPXdoaXRlIGxhbmc9RU4tVVMgbGluaz1ibHVlIHZsaW5rPXB1cnBsZT48 ZGl2IGNsYXNzPVdvcmRTZWN0aW9uMT48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2Zv bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjoj MUY0OTdEJz5IaSBHZW9yZ2UsPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1h bD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNh bnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBj bGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6 IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5UaGlzIGNvdWxkIGhhcHBlbiBp ZiB0aGUgTG9naWNhbCBWb2x1bWUgd2FzIGluY29ycmVjdGx5IHJlc2l6ZWQgKGUuZy4gbWFudWFs bHkpLiBUaGUgbWVzc2FnZXMgbG9nIG1pZ2h0IGdpdmUgeW91IHNvbWUgbW9yZSBpbmZvcm1hdGlv bi4gQ2hlY2sgdGhhdCB0aGUgTFYgc2l6ZSBjb3JyZXNwb25kcyB0byB0aGUgdmlydHVhbCBzaXpl LiBJdCBjb3VsZCBhbHNvIGJlIGEgZ2VudWluZSBjb3JydXB0aW9uIGZvciBzb21lIG90aGVyIHJl YXNvbi4gV2hhdCB3ZXJlIHlvdSBkb2luZyB3aGVuIHlvdSBnb3QgdGhpcyBlcnJvcj88bzpwPjwv bzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6 MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+ PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHls ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv bG9yOiMxRjQ5N0QnPkFuZHJlaTxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3Jt YWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJz YW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRp diBzdHlsZT0nYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5n OjBpbiAwaW4gMGluIDQuMHB0Jz48YmxvY2txdW90ZSBzdHlsZT0nbWFyZ2luLXRvcDo1LjBwdDtt YXJnaW4tYm90dG9tOjUuMHB0Jz48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2lu LWJvdHRvbToxMi4wcHQnPjxiPkZyb206PC9iPiBHZW9yZ2UgU2h1a2xpbiAmbHQ7PGEgaHJlZj0i bWFpbHRvOmdlb3JnZS5zaHVrbGluQGdtYWlsLmNvbSI+Z2VvcmdlLnNodWtsaW5AZ21haWwuY29t PC9hPiZndDs8YnI+PGI+RGF0ZTo8L2I+IEZlYnJ1YXJ5IDI5LCAyMDEyIDEwOjQ0OjI2IFBNIEdN VDxicj48Yj5Ubzo8L2I+ICZxdW90OzxhIGhyZWY9Im1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbnNv dXJjZS5jb20iPnhlbi1hcGlAbGlzdHMueGVuc291cmNlLmNvbTwvYT4mcXVvdDsgJmx0OzxhIGhy ZWY9Im1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbnNvdXJjZS5jb20iPnhlbi1hcGlAbGlzdHMueGVu c291cmNlLmNvbTwvYT4mZ3Q7PGJyPjxiPlN1YmplY3Q6PC9iPiA8Yj5bWGVuLUFQSV0gdmhkX3Jl YWRfc2hvcnRfZm9vdGVyIGZhaWxlZDwvYj48bzpwPjwvbzpwPjwvcD48L2Rpdj48L2Jsb2NrcXVv dGU+PGJsb2NrcXVvdGUgc3R5bGU9J21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBw dCc+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWw+R29vZCBkYXkuPGJyPjxicj5Hb3QgbWVzc2FnZSBm b3IgZmV3IFZESSdzOjxicj48YnI+dmhkLXV0aWw6IGxpYnZoZDo6dmhkX3JlYWRfZm9vdGVyX2F0 OiA8YnI+L2Rldi9WR19YZW5TdG9yYWdlLTEwMjE0NzYzLTcxODEtOTk4MC1iMGI1LTY4OGM5MDBj NDgyYS9WSEQtOTVlMjg1MTctYzA2My00MGMxLWIyZGItMjBlY2VhZGZhZTE0OiA8YnI+cmVhZGlu ZyBmb290ZXIgYXQgMHg0MDI3ZmZlMDAgZmFpbGVkOiAtMjI8YnI+PGJyPkknbSBub3QgcmVhbGx5 IHdlbGwgdW5kZXJzdGFuZCB0aGVpciBtZWFuaW5nLi4uIElzIFZIRCBjaGFpbiBicm9rZW4/IE9y IDxicj5zb21ldGhpbmcgZWxzZT8gSSBnb3QgdGhlbSBmb3IgVkRJIG9uIElTQ1NJIFNSIHdpdGhv dXQgc25hcHNob3Rlcy4uLjxicj48YnI+PGJyPjxicj5fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXzxicj54ZW4tYXBpIG1haWxpbmcgbGlzdDxicj48YSBocmVm PSJtYWlsdG86eGVuLWFwaUBsaXN0cy54ZW4ub3JnIj54ZW4tYXBpQGxpc3RzLnhlbi5vcmc8L2E+ PGJyPjxhIGhyZWY9Imh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5m by94ZW4tYXBpIj5odHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8v eGVuLWFwaTwvYT48bzpwPjwvbzpwPjwvcD48L2Rpdj48L2Jsb2NrcXVvdGU+PC9kaXY+PC9kaXY+ PC9ib2R5PjwvaHRtbD4= --_000_B45B24330584FB4AAE78E08B8F5E5B5ECBF51EDD5ELONPMAILBOX01_-- --===============5399956017448078542== 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 --===============5399956017448078542==-- From xen-api-bounces@lists.xen.org Thu Mar 01 16:10:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 01 Mar 2012 16:10: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 1S38Zq-0006eO-UE; Thu, 01 Mar 2012 16:09:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S38Zp-0006eA-Hw for xen-api@lists.xensource.com; Thu, 01 Mar 2012 16:09:57 +0000 Received: from [85.158.138.51:64285] by server-1.bemta-3.messagelabs.com id A9/C0-02415-45F9F4F4; Thu, 01 Mar 2012 16:09:56 +0000 X-Env-Sender: Andrei.Lifchits@citrix.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1330618195!13837301!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4NjQ2Mw==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3563 invoked from network); 1 Mar 2012 16:09:56 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2012 16:09:56 -0000 X-IronPort-AV: E=Sophos;i="4.73,511,1325462400"; d="scan'208,217";a="11039425" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 01 Mar 2012 16:09:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 1 Mar 2012 16:09:55 +0000 From: Andrei Lifchits To: "xen-api (xen-api@lists.xensource.com)" Date: Thu, 1 Mar 2012 16:09:54 +0000 Thread-Topic: [Xen-API] vhd_read_short_footer failed Thread-Index: Acz3ubtlS29lR269SQ2IieZFczbsSAACzjlw Message-ID: References: <4F4EAA4A.9090700@gmail.com> <77CE58D6-669D-4B9F-AC8C-DE7F9A9BD136@eu.citrix.com> In-Reply-To: <77CE58D6-669D-4B9F-AC8C-DE7F9A9BD136@eu.citrix.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] vhd_read_short_footer failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5399956017448078542==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5399956017448078542== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_B45B24330584FB4AAE78E08B8F5E5B5ECBF51EDD5ELONPMAILBOX01_" --_000_B45B24330584FB4AAE78E08B8F5E5B5ECBF51EDD5ELONPMAILBOX01_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgR2VvcmdlLA0KDQpUaGlzIGNvdWxkIGhhcHBlbiBpZiB0aGUgTG9naWNhbCBWb2x1bWUgd2Fz IGluY29ycmVjdGx5IHJlc2l6ZWQgKGUuZy4gbWFudWFsbHkpLiBUaGUgbWVzc2FnZXMgbG9nIG1p Z2h0IGdpdmUgeW91IHNvbWUgbW9yZSBpbmZvcm1hdGlvbi4gQ2hlY2sgdGhhdCB0aGUgTFYgc2l6 ZSBjb3JyZXNwb25kcyB0byB0aGUgdmlydHVhbCBzaXplLiBJdCBjb3VsZCBhbHNvIGJlIGEgZ2Vu dWluZSBjb3JydXB0aW9uIGZvciBzb21lIG90aGVyIHJlYXNvbi4gV2hhdCB3ZXJlIHlvdSBkb2lu ZyB3aGVuIHlvdSBnb3QgdGhpcyBlcnJvcj8NCg0KQW5kcmVpDQoNCkZyb206IEdlb3JnZSBTaHVr bGluIDxnZW9yZ2Uuc2h1a2xpbkBnbWFpbC5jb208bWFpbHRvOmdlb3JnZS5zaHVrbGluQGdtYWls LmNvbT4+DQpEYXRlOiBGZWJydWFyeSAyOSwgMjAxMiAxMDo0NDoyNiBQTSBHTVQNClRvOiAieGVu LWFwaUBsaXN0cy54ZW5zb3VyY2UuY29tPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbnNvdXJjZS5j b20+IiA8eGVuLWFwaUBsaXN0cy54ZW5zb3VyY2UuY29tPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhl bnNvdXJjZS5jb20+Pg0KU3ViamVjdDogW1hlbi1BUEldIHZoZF9yZWFkX3Nob3J0X2Zvb3RlciBm YWlsZWQNCkdvb2QgZGF5Lg0KDQpHb3QgbWVzc2FnZSBmb3IgZmV3IFZESSdzOg0KDQp2aGQtdXRp bDogbGlidmhkOjp2aGRfcmVhZF9mb290ZXJfYXQ6DQovZGV2L1ZHX1hlblN0b3JhZ2UtMTAyMTQ3 NjMtNzE4MS05OTgwLWIwYjUtNjg4YzkwMGM0ODJhL1ZIRC05NWUyODUxNy1jMDYzLTQwYzEtYjJk Yi0yMGVjZWFkZmFlMTQ6DQpyZWFkaW5nIGZvb3RlciBhdCAweDQwMjdmZmUwMCBmYWlsZWQ6IC0y Mg0KDQpJJ20gbm90IHJlYWxseSB3ZWxsIHVuZGVyc3RhbmQgdGhlaXIgbWVhbmluZy4uLiBJcyBW SEQgY2hhaW4gYnJva2VuPyBPcg0Kc29tZXRoaW5nIGVsc2U/IEkgZ290IHRoZW0gZm9yIFZESSBv biBJU0NTSSBTUiB3aXRob3V0IHNuYXBzaG90ZXMuLi4NCg0KDQoNCl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQp4ZW4tYXBpIG1haWxpbmcgbGlzdA0KeGVu LWFwaUBsaXN0cy54ZW4ub3JnPG1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbi5vcmc+DQpodHRwOi8v bGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQ0K --_000_B45B24330584FB4AAE78E08B8F5E5B5ECBF51EDD5ELONPMAILBOX01_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50 PSJNaWNyb3NvZnQgV29yZCAxNCAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5 OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQovKiBTdHlsZSBEZWZp bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0 LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj b3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNv QWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxv b24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm b250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnNw YW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt ZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFuLkJh bGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1z by1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglm b250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNv LXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3Jk U2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGlu IDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9z dHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVk aXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28g OV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJl ZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPjwvaGVh ZD48Ym9keSBiZ2NvbG9yPXdoaXRlIGxhbmc9RU4tVVMgbGluaz1ibHVlIHZsaW5rPXB1cnBsZT48 ZGl2IGNsYXNzPVdvcmRTZWN0aW9uMT48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2Zv bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjoj MUY0OTdEJz5IaSBHZW9yZ2UsPG86cD48L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1h bD48c3BhbiBzdHlsZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNh bnMtc2VyaWYiO2NvbG9yOiMxRjQ5N0QnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBj bGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6 IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5UaGlzIGNvdWxkIGhhcHBlbiBp ZiB0aGUgTG9naWNhbCBWb2x1bWUgd2FzIGluY29ycmVjdGx5IHJlc2l6ZWQgKGUuZy4gbWFudWFs bHkpLiBUaGUgbWVzc2FnZXMgbG9nIG1pZ2h0IGdpdmUgeW91IHNvbWUgbW9yZSBpbmZvcm1hdGlv bi4gQ2hlY2sgdGhhdCB0aGUgTFYgc2l6ZSBjb3JyZXNwb25kcyB0byB0aGUgdmlydHVhbCBzaXpl LiBJdCBjb3VsZCBhbHNvIGJlIGEgZ2VudWluZSBjb3JydXB0aW9uIGZvciBzb21lIG90aGVyIHJl YXNvbi4gV2hhdCB3ZXJlIHlvdSBkb2luZyB3aGVuIHlvdSBnb3QgdGhpcyBlcnJvcj88bzpwPjwv bzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6 MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+ PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbD48c3BhbiBzdHls ZT0nZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiO2Nv bG9yOiMxRjQ5N0QnPkFuZHJlaTxvOnA+PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3Jt YWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJz YW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PGRp diBzdHlsZT0nYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5n OjBpbiAwaW4gMGluIDQuMHB0Jz48YmxvY2txdW90ZSBzdHlsZT0nbWFyZ2luLXRvcDo1LjBwdDtt YXJnaW4tYm90dG9tOjUuMHB0Jz48ZGl2PjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbWFyZ2lu LWJvdHRvbToxMi4wcHQnPjxiPkZyb206PC9iPiBHZW9yZ2UgU2h1a2xpbiAmbHQ7PGEgaHJlZj0i bWFpbHRvOmdlb3JnZS5zaHVrbGluQGdtYWlsLmNvbSI+Z2VvcmdlLnNodWtsaW5AZ21haWwuY29t PC9hPiZndDs8YnI+PGI+RGF0ZTo8L2I+IEZlYnJ1YXJ5IDI5LCAyMDEyIDEwOjQ0OjI2IFBNIEdN VDxicj48Yj5Ubzo8L2I+ICZxdW90OzxhIGhyZWY9Im1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbnNv dXJjZS5jb20iPnhlbi1hcGlAbGlzdHMueGVuc291cmNlLmNvbTwvYT4mcXVvdDsgJmx0OzxhIGhy ZWY9Im1haWx0bzp4ZW4tYXBpQGxpc3RzLnhlbnNvdXJjZS5jb20iPnhlbi1hcGlAbGlzdHMueGVu c291cmNlLmNvbTwvYT4mZ3Q7PGJyPjxiPlN1YmplY3Q6PC9iPiA8Yj5bWGVuLUFQSV0gdmhkX3Jl YWRfc2hvcnRfZm9vdGVyIGZhaWxlZDwvYj48bzpwPjwvbzpwPjwvcD48L2Rpdj48L2Jsb2NrcXVv dGU+PGJsb2NrcXVvdGUgc3R5bGU9J21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBw dCc+PGRpdj48cCBjbGFzcz1Nc29Ob3JtYWw+R29vZCBkYXkuPGJyPjxicj5Hb3QgbWVzc2FnZSBm b3IgZmV3IFZESSdzOjxicj48YnI+dmhkLXV0aWw6IGxpYnZoZDo6dmhkX3JlYWRfZm9vdGVyX2F0 OiA8YnI+L2Rldi9WR19YZW5TdG9yYWdlLTEwMjE0NzYzLTcxODEtOTk4MC1iMGI1LTY4OGM5MDBj NDgyYS9WSEQtOTVlMjg1MTctYzA2My00MGMxLWIyZGItMjBlY2VhZGZhZTE0OiA8YnI+cmVhZGlu ZyBmb290ZXIgYXQgMHg0MDI3ZmZlMDAgZmFpbGVkOiAtMjI8YnI+PGJyPkknbSBub3QgcmVhbGx5 IHdlbGwgdW5kZXJzdGFuZCB0aGVpciBtZWFuaW5nLi4uIElzIFZIRCBjaGFpbiBicm9rZW4/IE9y IDxicj5zb21ldGhpbmcgZWxzZT8gSSBnb3QgdGhlbSBmb3IgVkRJIG9uIElTQ1NJIFNSIHdpdGhv dXQgc25hcHNob3Rlcy4uLjxicj48YnI+PGJyPjxicj5fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXzxicj54ZW4tYXBpIG1haWxpbmcgbGlzdDxicj48YSBocmVm PSJtYWlsdG86eGVuLWFwaUBsaXN0cy54ZW4ub3JnIj54ZW4tYXBpQGxpc3RzLnhlbi5vcmc8L2E+ PGJyPjxhIGhyZWY9Imh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5m by94ZW4tYXBpIj5odHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8v eGVuLWFwaTwvYT48bzpwPjwvbzpwPjwvcD48L2Rpdj48L2Jsb2NrcXVvdGU+PC9kaXY+PC9kaXY+ PC9ib2R5PjwvaHRtbD4= --_000_B45B24330584FB4AAE78E08B8F5E5B5ECBF51EDD5ELONPMAILBOX01_-- --===============5399956017448078542== 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 --===============5399956017448078542==-- From xen-api-bounces@lists.xen.org Thu Mar 01 19:03:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 01 Mar 2012 19:03:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3BHI-0004k9-PM; Thu, 01 Mar 2012 19:03:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3BHH-0004jy-0v for xen-api@lists.xen.org; Thu, 01 Mar 2012 19:02:59 +0000 Received: from [85.158.139.83:40968] by server-4.bemta-5.messagelabs.com id 40/29-10788-2E7CF4F4; Thu, 01 Mar 2012 19:02:58 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1330628576!17459516!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22127 invoked from network); 1 Mar 2012 19:02:56 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2012 19:02:56 -0000 Received: by bkcjg9 with SMTP id jg9so1038808bkc.32 for ; Thu, 01 Mar 2012 11:02:56 -0800 (PST) Received-SPF: pass (google.com: domain of george.shuklin@gmail.com designates 10.204.150.78 as permitted sender) client-ip=10.204.150.78; Authentication-Results: mr.google.com; spf=pass (google.com: domain of george.shuklin@gmail.com designates 10.204.150.78 as permitted sender) smtp.mail=george.shuklin@gmail.com; dkim=pass header.i=george.shuklin@gmail.com Received: from mr.google.com ([10.204.150.78]) by 10.204.150.78 with SMTP id x14mr3367904bkv.114.1330628576613 (num_hops = 1); Thu, 01 Mar 2012 11:02:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=hGXI5YhBUmQKwex0DPrQm71UWAkK9cX+ZZX09+1h9OY=; b=S77lfIVXz0lg4E9S3xFLOe1EWLnQ18pwJfk7z2Swcvopdf0LfUWYCuGn2aU04npJl5 O47E61aGRYtzoBpk8eMAk1fSicUwcAyTui5I7dI+F5OrxH00NwMut9HXzmMJlf/isTJI 6MZ1CCL8pM0pE/e2k6Hsf8nD91Ps1jhSkA+yw= Received: by 10.204.150.78 with SMTP id x14mr2704035bkv.114.1330628576448; Thu, 01 Mar 2012 11:02:56 -0800 (PST) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id o7sm5146170bkw.16.2012.03.01.11.02.54 (version=SSLv3 cipher=OTHER); Thu, 01 Mar 2012 11:02:55 -0800 (PST) Message-ID: <4F4FC7ED.2000402@gmail.com> Date: Thu, 01 Mar 2012 23:03:09 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F4EAA4A.9090700@gmail.com> <77CE58D6-669D-4B9F-AC8C-DE7F9A9BD136@eu.citrix.com> In-Reply-To: Subject: Re: [Xen-API] vhd_read_short_footer failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7507547750074882760==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7507547750074882760== Content-Type: multipart/alternative; boundary="------------050101090505030400080109" This is a multi-part message in MIME format. --------------050101090505030400080109 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Good day. I've never resize LV inside XCP LVM, I'm sure about this. I've getting those messages for many SR's in XCP 0.5 (yep, still in product) and in XCP 1.1. Here samples for few VDI's with this message: vhd-util: libvhd::vhd_validate_footer: invalid footer cookie: ÇÇÇÇÇÇÇÇ vhd-util: libvhd::vhd_read_footer_at: /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: reading footer at 0x281bffe00 failed: -22 vhd-util: libvhd::vhd_read: /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: read of 512 returned 0, errno: -22 vhd-util: libvhd::vhd_read_short_footer: /dev/VG_XenStorage-301127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: failed reading short footer: -22 xe vdi-list uuid=16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b params=virtual-size,physical-utilisation virtual-size ( RO) : 10737418240 physical-utilisation ( RO): 10766778368 lvdisplay /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b --- Logical volume --- LV Name /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b VG Name VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa LV UUID YaXNrJ-GOYV-z0WO-3pq6-y5Fm-3TW1-R7W0Mf LV Write Access read/write LV Status available # open 1 LV Size 10.03 GB Current LE 2567 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 1024 Block device 252:16 Can this be due physcal-utilization != virtual-size? Anyway, what consequences I can met with those messages? Thanks. On 01.03.2012 20:09, Andrei Lifchits wrote: > > Hi George, > > This could happen if the Logical Volume was incorrectly resized (e.g. > manually). The messages log might give you some more information. > Check that the LV size corresponds to the virtual size. It could also > be a genuine corruption for some other reason. What were you doing > when you got this error? > > Andrei > > *From:* George Shuklin > > *Date:* February 29, 2012 10:44:26 PM GMT > *To:* "xen-api@lists.xensource.com > " > > *Subject:* *[Xen-API] vhd_read_short_footer failed* > > Good day. > > Got message for few VDI's: > > vhd-util: libvhd::vhd_read_footer_at: > /dev/VG_XenStorage-10214763-7181-9980-b0b5-688c900c482a/VHD-95e28517-c063-40c1-b2db-20eceadfae14: > > reading footer at 0x4027ffe00 failed: -22 > > I'm not really well understand their meaning... Is VHD chain > broken? Or > something else? I got them for VDI on ISCSI SR without snapshotes... > > > > _______________________________________________ > 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 --------------050101090505030400080109 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Good day.

I've never resize LV inside XCP LVM, I'm sure about this.

I've getting those messages for many SR's in XCP 0.5 (yep, still in product) and in XCP 1.1.

Here samples for few VDI's with this message:

 vhd-util: libvhd::vhd_validate_footer: invalid footer cookie: ÇÇÇÇÇÇÇÇ
 vhd-util: libvhd::vhd_read_footer_at: /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: reading footer at 0x281bffe00 failed: -22
 vhd-util: libvhd::vhd_read: /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: read of 512 returned 0, errno: -22


vhd-util: libvhd::vhd_read_short_footer: /dev/VG_XenStorage-301127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: failed reading short footer: -22

xe vdi-list uuid=16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b params=virtual-size,physical-utilisation
virtual-size ( RO)            : 10737418240
    physical-utilisation ( RO): 10766778368

lvdisplay /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b
  --- Logical volume ---
  LV Name                /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b
  VG Name                VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa
  LV UUID                YaXNrJ-GOYV-z0WO-3pq6-y5Fm-3TW1-R7W0Mf
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                10.03 GB
  Current LE             2567
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     1024
  Block device           252:16


Can this be due physcal-utilization != virtual-size?

Anyway, what consequences I can met with those messages?

Thanks.


On 01.03.2012 20:09, Andrei Lifchits wrote:

Hi George,

 

This could happen if the Logical Volume was incorrectly resized (e.g. manually). The messages log might give you some more information. Check that the LV size corresponds to the virtual size. It could also be a genuine corruption for some other reason. What were you doing when you got this error?

 

Andrei

 

From: George Shuklin <george.shuklin@gmail.com>
Date: February 29, 2012 10:44:26 PM GMT
To: "xen-api@lists.xensource.com" <xen-api@lists.xensource.com>
Subject: [Xen-API] vhd_read_short_footer failed

Good day.

Got message for few VDI's:

vhd-util: libvhd::vhd_read_footer_at:
/dev/VG_XenStorage-10214763-7181-9980-b0b5-688c900c482a/VHD-95e28517-c063-40c1-b2db-20eceadfae14:
reading footer at 0x4027ffe00 failed: -22

I'm not really well understand their meaning... Is VHD chain broken? Or
something else? I got them for VDI on ISCSI SR without snapshotes...



_______________________________________________
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
--------------050101090505030400080109-- --===============7507547750074882760== 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 --===============7507547750074882760==-- From xen-api-bounces@lists.xen.org Thu Mar 01 19:03:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 01 Mar 2012 19:03:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3BHI-0004k9-PM; Thu, 01 Mar 2012 19:03:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3BHH-0004jy-0v for xen-api@lists.xen.org; Thu, 01 Mar 2012 19:02:59 +0000 Received: from [85.158.139.83:40968] by server-4.bemta-5.messagelabs.com id 40/29-10788-2E7CF4F4; Thu, 01 Mar 2012 19:02:58 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1330628576!17459516!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22127 invoked from network); 1 Mar 2012 19:02:56 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-3.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2012 19:02:56 -0000 Received: by bkcjg9 with SMTP id jg9so1038808bkc.32 for ; Thu, 01 Mar 2012 11:02:56 -0800 (PST) Received-SPF: pass (google.com: domain of george.shuklin@gmail.com designates 10.204.150.78 as permitted sender) client-ip=10.204.150.78; Authentication-Results: mr.google.com; spf=pass (google.com: domain of george.shuklin@gmail.com designates 10.204.150.78 as permitted sender) smtp.mail=george.shuklin@gmail.com; dkim=pass header.i=george.shuklin@gmail.com Received: from mr.google.com ([10.204.150.78]) by 10.204.150.78 with SMTP id x14mr3367904bkv.114.1330628576613 (num_hops = 1); Thu, 01 Mar 2012 11:02:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=hGXI5YhBUmQKwex0DPrQm71UWAkK9cX+ZZX09+1h9OY=; b=S77lfIVXz0lg4E9S3xFLOe1EWLnQ18pwJfk7z2Swcvopdf0LfUWYCuGn2aU04npJl5 O47E61aGRYtzoBpk8eMAk1fSicUwcAyTui5I7dI+F5OrxH00NwMut9HXzmMJlf/isTJI 6MZ1CCL8pM0pE/e2k6Hsf8nD91Ps1jhSkA+yw= Received: by 10.204.150.78 with SMTP id x14mr2704035bkv.114.1330628576448; Thu, 01 Mar 2012 11:02:56 -0800 (PST) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id o7sm5146170bkw.16.2012.03.01.11.02.54 (version=SSLv3 cipher=OTHER); Thu, 01 Mar 2012 11:02:55 -0800 (PST) Message-ID: <4F4FC7ED.2000402@gmail.com> Date: Thu, 01 Mar 2012 23:03:09 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F4EAA4A.9090700@gmail.com> <77CE58D6-669D-4B9F-AC8C-DE7F9A9BD136@eu.citrix.com> In-Reply-To: Subject: Re: [Xen-API] vhd_read_short_footer failed X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7507547750074882760==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7507547750074882760== Content-Type: multipart/alternative; boundary="------------050101090505030400080109" This is a multi-part message in MIME format. --------------050101090505030400080109 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Good day. I've never resize LV inside XCP LVM, I'm sure about this. I've getting those messages for many SR's in XCP 0.5 (yep, still in product) and in XCP 1.1. Here samples for few VDI's with this message: vhd-util: libvhd::vhd_validate_footer: invalid footer cookie: ÇÇÇÇÇÇÇÇ vhd-util: libvhd::vhd_read_footer_at: /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: reading footer at 0x281bffe00 failed: -22 vhd-util: libvhd::vhd_read: /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: read of 512 returned 0, errno: -22 vhd-util: libvhd::vhd_read_short_footer: /dev/VG_XenStorage-301127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: failed reading short footer: -22 xe vdi-list uuid=16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b params=virtual-size,physical-utilisation virtual-size ( RO) : 10737418240 physical-utilisation ( RO): 10766778368 lvdisplay /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b --- Logical volume --- LV Name /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b VG Name VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa LV UUID YaXNrJ-GOYV-z0WO-3pq6-y5Fm-3TW1-R7W0Mf LV Write Access read/write LV Status available # open 1 LV Size 10.03 GB Current LE 2567 Segments 2 Allocation inherit Read ahead sectors auto - currently set to 1024 Block device 252:16 Can this be due physcal-utilization != virtual-size? Anyway, what consequences I can met with those messages? Thanks. On 01.03.2012 20:09, Andrei Lifchits wrote: > > Hi George, > > This could happen if the Logical Volume was incorrectly resized (e.g. > manually). The messages log might give you some more information. > Check that the LV size corresponds to the virtual size. It could also > be a genuine corruption for some other reason. What were you doing > when you got this error? > > Andrei > > *From:* George Shuklin > > *Date:* February 29, 2012 10:44:26 PM GMT > *To:* "xen-api@lists.xensource.com > " > > *Subject:* *[Xen-API] vhd_read_short_footer failed* > > Good day. > > Got message for few VDI's: > > vhd-util: libvhd::vhd_read_footer_at: > /dev/VG_XenStorage-10214763-7181-9980-b0b5-688c900c482a/VHD-95e28517-c063-40c1-b2db-20eceadfae14: > > reading footer at 0x4027ffe00 failed: -22 > > I'm not really well understand their meaning... Is VHD chain > broken? Or > something else? I got them for VDI on ISCSI SR without snapshotes... > > > > _______________________________________________ > 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 --------------050101090505030400080109 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Good day.

I've never resize LV inside XCP LVM, I'm sure about this.

I've getting those messages for many SR's in XCP 0.5 (yep, still in product) and in XCP 1.1.

Here samples for few VDI's with this message:

 vhd-util: libvhd::vhd_validate_footer: invalid footer cookie: ÇÇÇÇÇÇÇÇ
 vhd-util: libvhd::vhd_read_footer_at: /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: reading footer at 0x281bffe00 failed: -22
 vhd-util: libvhd::vhd_read: /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: read of 512 returned 0, errno: -22


vhd-util: libvhd::vhd_read_short_footer: /dev/VG_XenStorage-301127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b: failed reading short footer: -22

xe vdi-list uuid=16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b params=virtual-size,physical-utilisation
virtual-size ( RO)            : 10737418240
    physical-utilisation ( RO): 10766778368

lvdisplay /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b
  --- Logical volume ---
  LV Name                /dev/VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa/VHD-16ee54bb-9c47-4edf-8cc9-e6ddc6bf7c6b
  VG Name                VG_XenStorage-309127d3-61a1-9c8d-ceb5-486c608c58aa
  LV UUID                YaXNrJ-GOYV-z0WO-3pq6-y5Fm-3TW1-R7W0Mf
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                10.03 GB
  Current LE             2567
  Segments               2
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     1024
  Block device           252:16


Can this be due physcal-utilization != virtual-size?

Anyway, what consequences I can met with those messages?

Thanks.


On 01.03.2012 20:09, Andrei Lifchits wrote:

Hi George,

 

This could happen if the Logical Volume was incorrectly resized (e.g. manually). The messages log might give you some more information. Check that the LV size corresponds to the virtual size. It could also be a genuine corruption for some other reason. What were you doing when you got this error?

 

Andrei

 

From: George Shuklin <george.shuklin@gmail.com>
Date: February 29, 2012 10:44:26 PM GMT
To: "xen-api@lists.xensource.com" <xen-api@lists.xensource.com>
Subject: [Xen-API] vhd_read_short_footer failed

Good day.

Got message for few VDI's:

vhd-util: libvhd::vhd_read_footer_at:
/dev/VG_XenStorage-10214763-7181-9980-b0b5-688c900c482a/VHD-95e28517-c063-40c1-b2db-20eceadfae14:
reading footer at 0x4027ffe00 failed: -22

I'm not really well understand their meaning... Is VHD chain broken? Or
something else? I got them for VDI on ISCSI SR without snapshotes...



_______________________________________________
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
--------------050101090505030400080109-- --===============7507547750074882760== 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 --===============7507547750074882760==-- From xen-api-bounces@lists.xen.org Fri Mar 02 09:54:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 09:54: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 1S3PBU-0006Ko-Pv; Fri, 02 Mar 2012 09:53:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3PBS-0006KK-LX for xen-api@lists.xensource.com; Fri, 02 Mar 2012 09:53:54 +0000 Received: from [85.158.143.35:7255] by server-1.bemta-4.messagelabs.com id 0B/B5-20925-1B8905F4; Fri, 02 Mar 2012 09:53:53 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1330682032!10196028!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4NjcwNg==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7478 invoked from network); 2 Mar 2012 09:53:53 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Mar 2012 09:53:53 -0000 X-IronPort-AV: E=Sophos;i="4.73,517,1325462400"; d="scan'208";a="11054447" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Mar 2012 09:53:52 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 2 Mar 2012 09:53:52 +0000 Message-ID: <1330682031.18632.58.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "xen-devel@lists.xensource.com" , "xen-api@lists.xensource.com" , "xen-users@lists.xensource.com" , "xen-arm@lists.xensource.com" Date: Fri, 2 Mar 2012 09:53:51 +0000 In-Reply-To: <4F297929.3070907@xen.org> References: <4F297929.3070907@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Subject: [Xen-API] Reminder: NEXT WEEK: Xen Hackathon hosted by Oracle, March 6-8, Santa Clara, CA, USA X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Just a reminder that the hackathon is Tuesday-Thursday next week. We currently have 24 people signed up but there is space for around 35 so if you want to attend there is still room. Please do sign up on the wiki page at http://wiki.xen.org/wiki/Hackathon/March2012. Looking forward to seeing many of you there! Ian. On Wed, 2012-02-01 at 17:40 +0000, Lars Kurth wrote: > Hi everybody, > > just a quick reminder that the Xen Hackathon is in Oracle, March 6-8, > Santa Clara, CA, USA. We have originally planned for about 25 people, > but already we have 14 people signed up. If you are planning to attend > please sign up quickly, such that I get a feeling for the number of > attendees. I can then go back to Oracle and see whether we can > accommodate more people than we planned for. > > * If you think you will attend please sign up at: > http://wiki.xen.org/wiki/Hackathon/March2012 > * If you think you may attend, but are not sure yet add, e.g. because > you do not yet have travel approved, please add "(provisional)" next to > your name > * If you can only attend part-time, please let us know which dates you > want to attend. > * If you do not regularly contribute to the Xen a mailing lists, please > add your e-mail address such that I can get in touch with you > > Please also add topics and stuff you want to cover. Also please suggest > evening social activities if you are from the area. > > Best Regards > Lars > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-arm _______________________________________________ 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 02 09:54:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 09:54: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 1S3PBU-0006Ko-Pv; Fri, 02 Mar 2012 09:53:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3PBS-0006KK-LX for xen-api@lists.xensource.com; Fri, 02 Mar 2012 09:53:54 +0000 Received: from [85.158.143.35:7255] by server-1.bemta-4.messagelabs.com id 0B/B5-20925-1B8905F4; Fri, 02 Mar 2012 09:53:53 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1330682032!10196028!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4NjcwNg==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7478 invoked from network); 2 Mar 2012 09:53:53 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Mar 2012 09:53:53 -0000 X-IronPort-AV: E=Sophos;i="4.73,517,1325462400"; d="scan'208";a="11054447" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Mar 2012 09:53:52 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 2 Mar 2012 09:53:52 +0000 Message-ID: <1330682031.18632.58.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "xen-devel@lists.xensource.com" , "xen-api@lists.xensource.com" , "xen-users@lists.xensource.com" , "xen-arm@lists.xensource.com" Date: Fri, 2 Mar 2012 09:53:51 +0000 In-Reply-To: <4F297929.3070907@xen.org> References: <4F297929.3070907@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Subject: [Xen-API] Reminder: NEXT WEEK: Xen Hackathon hosted by Oracle, March 6-8, Santa Clara, CA, USA X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Just a reminder that the hackathon is Tuesday-Thursday next week. We currently have 24 people signed up but there is space for around 35 so if you want to attend there is still room. Please do sign up on the wiki page at http://wiki.xen.org/wiki/Hackathon/March2012. Looking forward to seeing many of you there! Ian. On Wed, 2012-02-01 at 17:40 +0000, Lars Kurth wrote: > Hi everybody, > > just a quick reminder that the Xen Hackathon is in Oracle, March 6-8, > Santa Clara, CA, USA. We have originally planned for about 25 people, > but already we have 14 people signed up. If you are planning to attend > please sign up quickly, such that I get a feeling for the number of > attendees. I can then go back to Oracle and see whether we can > accommodate more people than we planned for. > > * If you think you will attend please sign up at: > http://wiki.xen.org/wiki/Hackathon/March2012 > * If you think you may attend, but are not sure yet add, e.g. because > you do not yet have travel approved, please add "(provisional)" next to > your name > * If you can only attend part-time, please let us know which dates you > want to attend. > * If you do not regularly contribute to the Xen a mailing lists, please > add your e-mail address such that I can get in touch with you > > Please also add topics and stuff you want to cover. Also please suggest > evening social activities if you are from the area. > > Best Regards > Lars > > _______________________________________________ > Xen-arm mailing list > Xen-arm@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-arm _______________________________________________ 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 02 22:12:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiV-0000M7-2C; Fri, 02 Mar 2012 22:12:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ry2nA-0001Lq-Ri for xen-api@lists.xensource.com; Thu, 16 Feb 2012 14:58:41 +0000 Received: from [85.158.139.83:39286] by server-5.bemta-5.messagelabs.com id F6/34-13566-0A91D3F4; Thu, 16 Feb 2012 14:58:40 +0000 X-Env-Sender: tim@xen.org X-Msg-Ref: server-3.tower-182.messagelabs.com!1329404318!15359107!1 X-Originating-IP: [81.29.64.94] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15410 invoked from network); 16 Feb 2012 14:58:38 -0000 Received: from ocelot.phlegethon.org (HELO mail.phlegethon.org) (81.29.64.94) by server-3.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Feb 2012 14:58:38 -0000 Received: from tjd by mail.phlegethon.org with local (Exim 4.67 (FreeBSD)) (envelope-from ) id 1Ry2n7-000BK0-8s; Thu, 16 Feb 2012 14:58:37 +0000 Date: Thu, 16 Feb 2012 14:58:37 +0000 From: Tim Deegan To: Andres Lagar-Cavilla Message-ID: <20120216145837.GA41163@ocelot.phlegethon.org> References: <11fd4e0a1e1a76ca3bc1.1329364624@xdev.gridcentric.ca> <20120216102014.GA40020@ocelot.phlegethon.org> <5612c7c996f87bb6a0e864258766e926.squirrel@webmail.lagarcavilla.org> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <5612c7c996f87bb6a0e864258766e926.squirrel@webmail.lagarcavilla.org> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Cc: xen-api@lists.xensource.com, andres@gridcentric.ca, xen-devel@lists.xensource.com, adin@gridcentric.ca Subject: Re: [Xen-API] [PATCH 1 of 4] Prevent low values of max_pages for domains doing sharing or paging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 At 06:45 -0800 on 16 Feb (1329374751), Andres Lagar-Cavilla wrote: > Fair enough (also referring to Jan's comments). We would be building > policy into the hypervisor. > > But I've seen squeezed set criminally low max_pages value (i.e. 256). > Granted, this is squeezed's problem, but shouldn't some sanity checking be > wired into the hypervisor? Some operating systems do just fine in 640K. :) But seriously, what lower limit would we use? Stupidly low max_pages for some uses would be just fine for others. > Why should we even allow max_pages < tot_pages? The reasoning is: - the tools want a hard guarantee that a rogue balloon driver can't mess up their calculations of how much free RAM there is. - when a VM is ballooning down we don't want to have the tools spinning watching actual max_pages and adjusting tot_pages down as it changes. It's not a particularly nice interface, though, and I'd be happy to see it revert to the old one (where new max had to be <= current tot). But that will need a fix for Xapi/squeezed to handle the ballooning-down case some other way. Cc-ing xen-API. Any XCP folks got an opinion about this? Would it be easy to make squeezed not need this behaviour? Cheers, Tim. _______________________________________________ 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 02 22:12:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiV-0000M7-2C; Fri, 02 Mar 2012 22:12:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ry2nA-0001Lq-Ri for xen-api@lists.xensource.com; Thu, 16 Feb 2012 14:58:41 +0000 Received: from [85.158.139.83:39286] by server-5.bemta-5.messagelabs.com id F6/34-13566-0A91D3F4; Thu, 16 Feb 2012 14:58:40 +0000 X-Env-Sender: tim@xen.org X-Msg-Ref: server-3.tower-182.messagelabs.com!1329404318!15359107!1 X-Originating-IP: [81.29.64.94] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15410 invoked from network); 16 Feb 2012 14:58:38 -0000 Received: from ocelot.phlegethon.org (HELO mail.phlegethon.org) (81.29.64.94) by server-3.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Feb 2012 14:58:38 -0000 Received: from tjd by mail.phlegethon.org with local (Exim 4.67 (FreeBSD)) (envelope-from ) id 1Ry2n7-000BK0-8s; Thu, 16 Feb 2012 14:58:37 +0000 Date: Thu, 16 Feb 2012 14:58:37 +0000 From: Tim Deegan To: Andres Lagar-Cavilla Message-ID: <20120216145837.GA41163@ocelot.phlegethon.org> References: <11fd4e0a1e1a76ca3bc1.1329364624@xdev.gridcentric.ca> <20120216102014.GA40020@ocelot.phlegethon.org> <5612c7c996f87bb6a0e864258766e926.squirrel@webmail.lagarcavilla.org> Mime-Version: 1.0 Content-Disposition: inline In-Reply-To: <5612c7c996f87bb6a0e864258766e926.squirrel@webmail.lagarcavilla.org> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Cc: xen-api@lists.xensource.com, andres@gridcentric.ca, xen-devel@lists.xensource.com, adin@gridcentric.ca Subject: Re: [Xen-API] [PATCH 1 of 4] Prevent low values of max_pages for domains doing sharing or paging X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 At 06:45 -0800 on 16 Feb (1329374751), Andres Lagar-Cavilla wrote: > Fair enough (also referring to Jan's comments). We would be building > policy into the hypervisor. > > But I've seen squeezed set criminally low max_pages value (i.e. 256). > Granted, this is squeezed's problem, but shouldn't some sanity checking be > wired into the hypervisor? Some operating systems do just fine in 640K. :) But seriously, what lower limit would we use? Stupidly low max_pages for some uses would be just fine for others. > Why should we even allow max_pages < tot_pages? The reasoning is: - the tools want a hard guarantee that a rogue balloon driver can't mess up their calculations of how much free RAM there is. - when a VM is ballooning down we don't want to have the tools spinning watching actual max_pages and adjusting tot_pages down as it changes. It's not a particularly nice interface, though, and I'd be happy to see it revert to the old one (where new max had to be <= current tot). But that will need a fix for Xapi/squeezed to handle the ballooning-down case some other way. Cc-ing xen-API. Any XCP folks got an opinion about this? Would it be easy to make squeezed not need this behaviour? Cheers, Tim. _______________________________________________ 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 02 22:12:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiU-0000Ll-HB; Fri, 02 Mar 2012 22:12:46 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwIBB-0003qt-N6; Sat, 11 Feb 2012 19:00:14 +0000 X-Env-Sender: wannes321@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1328986806!12982098!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24881 invoked from network); 11 Feb 2012 19:00:06 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2012 19:00:06 -0000 Received: by wibhm2 with SMTP id hm2so11316776wib.30 for ; Sat, 11 Feb 2012 11:00:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:subject:date:message-id:to:mime-version:x-mailer; bh=XJUY3CIqVHRSmnBXzTun9uFlj8pa/+7pUgvGzfOLSvM=; b=XPGNjYt8UA6jclU6L6WTldqvOGJ2HgE9VlfaIHMP0NVarAS3t1Up0BqEhAUBBr55mH 68vtGIFNl37xSRBb9NC7yMbYFKUmW1hyZXC0d7yAoDopX2XbWL72DfOIudp1no7pTy3t 8LSSdnC+TnZidWNjuvvlpSYZCnszxo0Yme5ac= Received: by 10.180.81.66 with SMTP id y2mr15812175wix.20.1328986805930; Sat, 11 Feb 2012 11:00:05 -0800 (PST) Received: from [172.16.223.52] (151.20-241-81.adsl-dyn.isp.belgacom.be. [81.241.20.151]) by mx.google.com with ESMTPS id cs4sm29873785wib.8.2012.02.11.11.00.03 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 11 Feb 2012 11:00:04 -0800 (PST) From: Wannes De Smet Date: Sat, 11 Feb 2012 20:00:02 +0100 Message-Id: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> To: xen-api@lists.xensource.com, xen-users@lists.xensource.com Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Subject: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8872956836822293646==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8872956836822293646== Content-Type: multipart/alternative; boundary="Apple-Mail=_0146A629-49DC-48F9-8EA0-E2EF15DC4087" --Apple-Mail=_0146A629-49DC-48F9-8EA0-E2EF15DC4087 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii We're happy to announce XenMaster, which has the ambitious goal to = become the de facto frontend for Xen with XCP. We've had the opportunity to present our project to some of the Xen/XCP = developers and now it's time to announce the project to a larger public. XenMaster, in short, is a HTML5 frontend coupled to a Java backend = delivering a rich UI for Xen, targeted at end users. At the moment, one is able to successfully add NFS ISO repositories and = iSCSI/NFS storage repositories (iSCSI currently only works on XenServer = 5.6), create a HVM VM and control it via a VNC shell.=20 Development thus far has been carried out by Jorgen Evens, frontend lead = and Wannes De Smet, project lead and backend developer. Of course, we = now would like to welcome you in becoming a tester and/or contributor!=20= You can find more information at xen-master.org, to install and = configure XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it! If you have any questions at all, we'll be happy to answer them here or = through GitHub. We hope to welcome you in using XenMaster! Jorgen Evens Wannes De Smet XenMaster=20= --Apple-Mail=_0146A629-49DC-48F9-8EA0-E2EF15DC4087 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii We're happy to announce XenMaster, which has = the ambitious goalto become the de facto frontend for Xen with = XCP.

We've had the opportunity to present our = project to some of the Xen/XCP developers and now it's time to announce = the project to a larger public.
XenMaster, in short, is a HTML5 = frontend coupled to a Java backend delivering a rich UI for Xen, = targeted at end users.
At the moment, one is able to successfully add = NFS ISO repositories and iSCSI/NFS storage repositories (iSCSI currently = only works on XenServer 5.6), create a HVM VM and control it via a VNC = shell.

Development thus far has been carried out by = Jorgen Evens, frontend lead and Wannes De Smet, project lead and backend = developer. Of course, we now would like to welcome you in becoming a = tester and/or contributor!
You can find more information at = xen-master.orginstall and configure = XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it!

If you have any questions at all, = we'll be happy to answer them here or through GitHub.

Wannes De Smet
XenMaster = = --Apple-Mail=_0146A629-49DC-48F9-8EA0-E2EF15DC4087-- --===============8872956836822293646== 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 --===============8872956836822293646==-- From xen-api-bounces@lists.xen.org Fri Mar 02 22:12:51 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiU-0000Ll-HB; Fri, 02 Mar 2012 22:12:46 +0000 Received: from mail174.messagelabs.com ([85.158.138.51]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwIBB-0003qt-N6; Sat, 11 Feb 2012 19:00:14 +0000 X-Env-Sender: wannes321@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1328986806!12982098!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24881 invoked from network); 11 Feb 2012 19:00:06 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2012 19:00:06 -0000 Received: by wibhm2 with SMTP id hm2so11316776wib.30 for ; Sat, 11 Feb 2012 11:00:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:subject:date:message-id:to:mime-version:x-mailer; bh=XJUY3CIqVHRSmnBXzTun9uFlj8pa/+7pUgvGzfOLSvM=; b=XPGNjYt8UA6jclU6L6WTldqvOGJ2HgE9VlfaIHMP0NVarAS3t1Up0BqEhAUBBr55mH 68vtGIFNl37xSRBb9NC7yMbYFKUmW1hyZXC0d7yAoDopX2XbWL72DfOIudp1no7pTy3t 8LSSdnC+TnZidWNjuvvlpSYZCnszxo0Yme5ac= Received: by 10.180.81.66 with SMTP id y2mr15812175wix.20.1328986805930; Sat, 11 Feb 2012 11:00:05 -0800 (PST) Received: from [172.16.223.52] (151.20-241-81.adsl-dyn.isp.belgacom.be. [81.241.20.151]) by mx.google.com with ESMTPS id cs4sm29873785wib.8.2012.02.11.11.00.03 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 11 Feb 2012 11:00:04 -0800 (PST) From: Wannes De Smet Date: Sat, 11 Feb 2012 20:00:02 +0100 Message-Id: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> To: xen-api@lists.xensource.com, xen-users@lists.xensource.com Mime-Version: 1.0 (Apple Message framework v1257) X-Mailer: Apple Mail (2.1257) X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Subject: [Xen-API] Announcing XenMaster X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8872956836822293646==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8872956836822293646== Content-Type: multipart/alternative; boundary="Apple-Mail=_0146A629-49DC-48F9-8EA0-E2EF15DC4087" --Apple-Mail=_0146A629-49DC-48F9-8EA0-E2EF15DC4087 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii We're happy to announce XenMaster, which has the ambitious goal to = become the de facto frontend for Xen with XCP. We've had the opportunity to present our project to some of the Xen/XCP = developers and now it's time to announce the project to a larger public. XenMaster, in short, is a HTML5 frontend coupled to a Java backend = delivering a rich UI for Xen, targeted at end users. At the moment, one is able to successfully add NFS ISO repositories and = iSCSI/NFS storage repositories (iSCSI currently only works on XenServer = 5.6), create a HVM VM and control it via a VNC shell.=20 Development thus far has been carried out by Jorgen Evens, frontend lead = and Wannes De Smet, project lead and backend developer. Of course, we = now would like to welcome you in becoming a tester and/or contributor!=20= You can find more information at xen-master.org, to install and = configure XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it! If you have any questions at all, we'll be happy to answer them here or = through GitHub. We hope to welcome you in using XenMaster! Jorgen Evens Wannes De Smet XenMaster=20= --Apple-Mail=_0146A629-49DC-48F9-8EA0-E2EF15DC4087 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii We're happy to announce XenMaster, which has = the ambitious goalto become the de facto frontend for Xen with = XCP.

We've had the opportunity to present our = project to some of the Xen/XCP developers and now it's time to announce = the project to a larger public.
XenMaster, in short, is a HTML5 = frontend coupled to a Java backend delivering a rich UI for Xen, = targeted at end users.
At the moment, one is able to successfully add = NFS ISO repositories and iSCSI/NFS storage repositories (iSCSI currently = only works on XenServer 5.6), create a HVM VM and control it via a VNC = shell.

Development thus far has been carried out by = Jorgen Evens, frontend lead and Wannes De Smet, project lead and backend = developer. Of course, we now would like to welcome you in becoming a = tester and/or contributor!
You can find more information at = xen-master.orginstall and configure = XenMaster. If you'd like to help and have experience in = developing Java and/or Javascript, load the source in your favorite IDE = and have at it!

If you have any questions at all, = we'll be happy to answer them here or through GitHub.

Wannes De Smet
XenMaster = = --Apple-Mail=_0146A629-49DC-48F9-8EA0-E2EF15DC4087-- --===============8872956836822293646== 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 --===============8872956836822293646==-- From xen-api-bounces@lists.xen.org Fri Mar 02 22:12:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiU-0000Lv-Pj; Fri, 02 Mar 2012 22:12:46 +0000 Received: from mail21.messagelabs.com ([85.158.143.35]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwwS1-0001X1-V3; Mon, 13 Feb 2012 14:00:18 +0000 X-Env-Sender: ciprian.pantea@innovocompany.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1329141607!9017700!1 X-Originating-IP: [209.85.216.171] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9338 invoked from network); 13 Feb 2012 14:00:08 -0000 Received: from mail-qy0-f171.google.com (HELO mail-qy0-f171.google.com) (209.85.216.171) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 14:00:08 -0000 Received: by qcsp15 with SMTP id p15so18524237qcs.30 for ; Mon, 13 Feb 2012 06:00:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=innovocompany.com; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=H4T7Y+HCc8lZ5E7TrlKwWmR7h2qPSfYG3j/uDtVQ3XY=; b=I0EOXzjxp9i68nXYGB6YVyX5xaV2slxT68bgh+7Ak5No0DPIL4X8lzYH9VWn4HIUFW M95MCdhaea4rXdOV2gFi0y1xGKyOM5auzThCMbAgWbPR9ntIidarTvd0FQqyX83YskUx Q1XD3C6VFtnV13KXDDAmVUhH1T3C4jiUiEwaQ= Received: by 10.229.136.130 with SMTP id r2mr3287010qct.60.1329141607307; Mon, 13 Feb 2012 06:00:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.230.204 with HTTP; Mon, 13 Feb 2012 05:59:27 -0800 (PST) In-Reply-To: References: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> From: Ciprian Pantea Date: Mon, 13 Feb 2012 15:59:27 +0200 X-Google-Sender-Auth: EQv-kcLiUGhcrAtX9oP-tR7elyM Message-ID: To: Scott Damron X-Gm-Message-State: ALoCoQlF0NH46oLOGCpYlGdG22u574O90uEaYbHbiNqa7Bo5COyY17uaeTAfc3Rdqm1/e3QEFxI8 X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] Announcing XenMaster X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7845211704576959451==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7845211704576959451== Content-Type: multipart/alternative; boundary=00248c768f925c1d3904b8d8e53a --00248c768f925c1d3904b8d8e53a Content-Type: text/plain; charset=ISO-8859-1 Oh yeah, sorry, didn't find that last week. Does it support installations from templates and user based access? On Mon, Feb 13, 2012 at 15:21, Scott Damron wrote: > Screen shots are included on the Wiki... > > On Mon, Feb 13, 2012 at 7:19 AM, Ciprian Pantea wrote: > > I'd love to give it a try too but screenshots would have been better :) > > I'm not clear though on the list of features and I don't find any on your > > site either. > > > > > > Good job! > > PS: try to get rid of java in the future > > > > > > On Mon, Feb 13, 2012 at 14:41, Scott Damron wrote: > >> > >> Instead of harshing on your for using Java, I am going to say - Nicely > >> done! I use either Linux or Mac OS X workstations, and have to run a > >> VM of Windows if I want to use a GUI to manage my Xen boxes. I > >> actually prefer to do the management via a GUI because I don't have a > >> lot of time to waste on trying to remember all of the commands to do > >> stuff. Thank you for the hard work, I will certainly be giving it a > >> try. > >> > >> Regards, > >> > >> Scott > >> > >> On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet > >> wrote: > >> > We're happy to announce XenMaster, which has the ambitious goal to > >> > become > >> > the de facto frontend for Xen with XCP. > >> > > >> > We've had the opportunity to present our project to some of the > Xen/XCP > >> > developers and now it's time to announce the project to a larger > public. > >> > XenMaster, in short, is a HTML5 frontend coupled to a Java backend > >> > delivering a rich UI for Xen, targeted at end users. > >> > At the moment, one is able to successfully add NFS ISO repositories > and > >> > iSCSI/NFS storage repositories (iSCSI currently only works on > XenServer > >> > 5.6), create a HVM VM and control it via a VNC shell. > >> > > >> > Development thus far has been carried out by Jorgen Evens, frontend > lead > >> > and > >> > Wannes De Smet, project lead and backend developer. Of course, we now > >> > would > >> > like to welcome you in becoming a tester and/or contributor! > >> > You can find more information at xen-master.org, to install and > >> > configure > >> > XenMaster. If you'd like to help and have experience in developing > Java > >> > and/or Javascript, load the source in your favorite IDE and have at > it! > >> > > >> > If you have any questions at all, we'll be happy to answer them here > or > >> > through GitHub. > >> > > >> > We hope to welcome you in using XenMaster! > >> > Jorgen Evens > >> > Wannes De Smet > >> > XenMaster > >> > > >> > _______________________________________________ > >> > Xen-users mailing list > >> > Xen-users@lists.xensource.com > >> > http://lists.xensource.com/xen-users > >> > >> _______________________________________________ > >> Xen-users mailing list > >> Xen-users@lists.xensource.com > >> http://lists.xensource.com/xen-users > > > > > --00248c768f925c1d3904b8d8e53a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oh yeah, sorry, didn't find that last week. Does it support installatio= ns from templates and user based access?

= On Mon, Feb 13, 2012 at 15:21, Scott Damron <sdamron@gmail.com> wrote:
Screen shots are included on the Wiki...

On Mon, Feb 13, 2012 at 7:19 AM, Ciprian Pantea <cipixul@gmail.com> wrote:
> I'd love to give it a try too but screenshots would have been bett= er :)
> I'm not clear though on the list of features and I don't find = any on your
> site either.
>
>
> Good job!
> PS: try to get rid of java in the future
>
>
> On Mon, Feb 13, 2012 at 14:41, Scott Damron <sdamron@gmail.com> wrote:
>>
>> Instead of harshing on your for using Java, I am going to say - Ni= cely
>> done! =A0I use either Linux or Mac OS X workstations, and have to = run a
>> VM of Windows if I want to use a GUI to manage my Xen boxes. =A0I<= br> >> actually prefer to do the management via a GUI because I don't= have a
>> lot of time to waste on trying to remember all of the commands to = do
>> stuff. =A0Thank you for the hard work, I will certainly be giving = it a
>> try.
>>
>> Regards,
>>
>> Scott
>>
>> On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet <wannes321@gmail.com>
>> wrote:
>> > We're happy to announce XenMaster, which has the ambitiou= s goal to
>> > become
>> > the de facto frontend for Xen with XCP.
>> >
>> > We've had the opportunity to present our project to some = of the Xen/XCP
>> > developers and now it's time to announce the project to a= larger public.
>> > XenMaster, in short, is a HTML5 frontend coupled to a Java ba= ckend
>> > delivering a rich UI for Xen, targeted at end users.
>> > At the moment, one is able to successfully add NFS ISO reposi= tories and
>> > iSCSI/NFS storage repositories (iSCSI currently only works on= XenServer
>> > 5.6), create a HVM VM and control it via a VNC shell.
>> >
>> > Development thus far has been carried out by Jorgen Evens, fr= ontend lead
>> > and
>> > Wannes De Smet, project lead and backend developer. Of course= , we now
>> > would
>> > like to welcome you in becoming a tester and/or contributor!<= br> >> > You can find more information at xen-master.org, to install and
>> > configure
>> > XenMaster. If you'd like to help and have experience in d= eveloping Java
>> > and/or Javascript, load the source in your favorite IDE and h= ave at it!
>> >
>> > If you have any questions at all, we'll be happy to answe= r them here or
>> > through GitHub.
>> >
>> > We hope to welcome you in using XenMaster!
>> > Jorgen Evens
>> > Wannes De Smet
>> > XenMaster
>> >
>> > _______________________________________________
>> > Xen-users mailing list
>> > Xen-users@li= sts.xensource.com
>> > http://lists.xensource.com/xen-users
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.x= ensource.com
>> http://lists.xensource.com/xen-users
>
>

--00248c768f925c1d3904b8d8e53a-- --===============7845211704576959451== 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 --===============7845211704576959451==-- From xen-api-bounces@lists.xen.org Fri Mar 02 22:12:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiU-0000Lv-Pj; Fri, 02 Mar 2012 22:12:46 +0000 Received: from mail21.messagelabs.com ([85.158.143.35]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwwS1-0001X1-V3; Mon, 13 Feb 2012 14:00:18 +0000 X-Env-Sender: ciprian.pantea@innovocompany.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1329141607!9017700!1 X-Originating-IP: [209.85.216.171] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9338 invoked from network); 13 Feb 2012 14:00:08 -0000 Received: from mail-qy0-f171.google.com (HELO mail-qy0-f171.google.com) (209.85.216.171) by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 14:00:08 -0000 Received: by qcsp15 with SMTP id p15so18524237qcs.30 for ; Mon, 13 Feb 2012 06:00:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=innovocompany.com; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=H4T7Y+HCc8lZ5E7TrlKwWmR7h2qPSfYG3j/uDtVQ3XY=; b=I0EOXzjxp9i68nXYGB6YVyX5xaV2slxT68bgh+7Ak5No0DPIL4X8lzYH9VWn4HIUFW M95MCdhaea4rXdOV2gFi0y1xGKyOM5auzThCMbAgWbPR9ntIidarTvd0FQqyX83YskUx Q1XD3C6VFtnV13KXDDAmVUhH1T3C4jiUiEwaQ= Received: by 10.229.136.130 with SMTP id r2mr3287010qct.60.1329141607307; Mon, 13 Feb 2012 06:00:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.230.204 with HTTP; Mon, 13 Feb 2012 05:59:27 -0800 (PST) In-Reply-To: References: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> From: Ciprian Pantea Date: Mon, 13 Feb 2012 15:59:27 +0200 X-Google-Sender-Auth: EQv-kcLiUGhcrAtX9oP-tR7elyM Message-ID: To: Scott Damron X-Gm-Message-State: ALoCoQlF0NH46oLOGCpYlGdG22u574O90uEaYbHbiNqa7Bo5COyY17uaeTAfc3Rdqm1/e3QEFxI8 X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] Announcing XenMaster X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7845211704576959451==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7845211704576959451== Content-Type: multipart/alternative; boundary=00248c768f925c1d3904b8d8e53a --00248c768f925c1d3904b8d8e53a Content-Type: text/plain; charset=ISO-8859-1 Oh yeah, sorry, didn't find that last week. Does it support installations from templates and user based access? On Mon, Feb 13, 2012 at 15:21, Scott Damron wrote: > Screen shots are included on the Wiki... > > On Mon, Feb 13, 2012 at 7:19 AM, Ciprian Pantea wrote: > > I'd love to give it a try too but screenshots would have been better :) > > I'm not clear though on the list of features and I don't find any on your > > site either. > > > > > > Good job! > > PS: try to get rid of java in the future > > > > > > On Mon, Feb 13, 2012 at 14:41, Scott Damron wrote: > >> > >> Instead of harshing on your for using Java, I am going to say - Nicely > >> done! I use either Linux or Mac OS X workstations, and have to run a > >> VM of Windows if I want to use a GUI to manage my Xen boxes. I > >> actually prefer to do the management via a GUI because I don't have a > >> lot of time to waste on trying to remember all of the commands to do > >> stuff. Thank you for the hard work, I will certainly be giving it a > >> try. > >> > >> Regards, > >> > >> Scott > >> > >> On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet > >> wrote: > >> > We're happy to announce XenMaster, which has the ambitious goal to > >> > become > >> > the de facto frontend for Xen with XCP. > >> > > >> > We've had the opportunity to present our project to some of the > Xen/XCP > >> > developers and now it's time to announce the project to a larger > public. > >> > XenMaster, in short, is a HTML5 frontend coupled to a Java backend > >> > delivering a rich UI for Xen, targeted at end users. > >> > At the moment, one is able to successfully add NFS ISO repositories > and > >> > iSCSI/NFS storage repositories (iSCSI currently only works on > XenServer > >> > 5.6), create a HVM VM and control it via a VNC shell. > >> > > >> > Development thus far has been carried out by Jorgen Evens, frontend > lead > >> > and > >> > Wannes De Smet, project lead and backend developer. Of course, we now > >> > would > >> > like to welcome you in becoming a tester and/or contributor! > >> > You can find more information at xen-master.org, to install and > >> > configure > >> > XenMaster. If you'd like to help and have experience in developing > Java > >> > and/or Javascript, load the source in your favorite IDE and have at > it! > >> > > >> > If you have any questions at all, we'll be happy to answer them here > or > >> > through GitHub. > >> > > >> > We hope to welcome you in using XenMaster! > >> > Jorgen Evens > >> > Wannes De Smet > >> > XenMaster > >> > > >> > _______________________________________________ > >> > Xen-users mailing list > >> > Xen-users@lists.xensource.com > >> > http://lists.xensource.com/xen-users > >> > >> _______________________________________________ > >> Xen-users mailing list > >> Xen-users@lists.xensource.com > >> http://lists.xensource.com/xen-users > > > > > --00248c768f925c1d3904b8d8e53a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Oh yeah, sorry, didn't find that last week. Does it support installatio= ns from templates and user based access?

= On Mon, Feb 13, 2012 at 15:21, Scott Damron <sdamron@gmail.com> wrote:
Screen shots are included on the Wiki...

On Mon, Feb 13, 2012 at 7:19 AM, Ciprian Pantea <cipixul@gmail.com> wrote:
> I'd love to give it a try too but screenshots would have been bett= er :)
> I'm not clear though on the list of features and I don't find = any on your
> site either.
>
>
> Good job!
> PS: try to get rid of java in the future
>
>
> On Mon, Feb 13, 2012 at 14:41, Scott Damron <sdamron@gmail.com> wrote:
>>
>> Instead of harshing on your for using Java, I am going to say - Ni= cely
>> done! =A0I use either Linux or Mac OS X workstations, and have to = run a
>> VM of Windows if I want to use a GUI to manage my Xen boxes. =A0I<= br> >> actually prefer to do the management via a GUI because I don't= have a
>> lot of time to waste on trying to remember all of the commands to = do
>> stuff. =A0Thank you for the hard work, I will certainly be giving = it a
>> try.
>>
>> Regards,
>>
>> Scott
>>
>> On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet <wannes321@gmail.com>
>> wrote:
>> > We're happy to announce XenMaster, which has the ambitiou= s goal to
>> > become
>> > the de facto frontend for Xen with XCP.
>> >
>> > We've had the opportunity to present our project to some = of the Xen/XCP
>> > developers and now it's time to announce the project to a= larger public.
>> > XenMaster, in short, is a HTML5 frontend coupled to a Java ba= ckend
>> > delivering a rich UI for Xen, targeted at end users.
>> > At the moment, one is able to successfully add NFS ISO reposi= tories and
>> > iSCSI/NFS storage repositories (iSCSI currently only works on= XenServer
>> > 5.6), create a HVM VM and control it via a VNC shell.
>> >
>> > Development thus far has been carried out by Jorgen Evens, fr= ontend lead
>> > and
>> > Wannes De Smet, project lead and backend developer. Of course= , we now
>> > would
>> > like to welcome you in becoming a tester and/or contributor!<= br> >> > You can find more information at xen-master.org, to install and
>> > configure
>> > XenMaster. If you'd like to help and have experience in d= eveloping Java
>> > and/or Javascript, load the source in your favorite IDE and h= ave at it!
>> >
>> > If you have any questions at all, we'll be happy to answe= r them here or
>> > through GitHub.
>> >
>> > We hope to welcome you in using XenMaster!
>> > Jorgen Evens
>> > Wannes De Smet
>> > XenMaster
>> >
>> > _______________________________________________
>> > Xen-users mailing list
>> > Xen-users@li= sts.xensource.com
>> > http://lists.xensource.com/xen-users
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.x= ensource.com
>> http://lists.xensource.com/xen-users
>
>

--00248c768f925c1d3904b8d8e53a-- --===============7845211704576959451== 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 --===============7845211704576959451==-- From xen-api-bounces@lists.xen.org Fri Mar 02 22:12:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiU-0000M0-UU; Fri, 02 Mar 2012 22:12:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ry0Hk-0005zs-F7 for xen-api@lists.xensource.com; Thu, 16 Feb 2012 12:18:04 +0000 Received: from [85.158.139.83:5794] by server-10.bemta-5.messagelabs.com id EB/C9-07861-BF3FC3F4; Thu, 16 Feb 2012 12:18:03 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1329394681!15258795!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29949 invoked from network); 16 Feb 2012 12:18:02 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2012 12:18:02 -0000 Received: by iaeh11 with SMTP id h11so15658213iae.30 for ; Thu, 16 Feb 2012 04:18:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8pTAyESiwdZSCPlcJJnJJpas5+sDR3gehfsQPKlg48c=; b=lVdDpsELdGvH5Yzarccoeetwcyh1sXe9G0Qj/QmFy5Sln3wRYBbjIarnPxAK1Bh1rz Bjrj6uSOaGnD4xPRynTjd8VLJBZOYU/z6slrZQ/ko0uzlmVBIqI90mpTTcVivLrtZTqz HrpozOjvXJOWAVAQyD4tLOXEOBYpP6px7waRY= MIME-Version: 1.0 Received: by 10.50.160.131 with SMTP id xk3mr2623726igb.19.1329394680771; Thu, 16 Feb 2012 04:18:00 -0800 (PST) Received: by 10.231.7.14 with HTTP; Thu, 16 Feb 2012 04:18:00 -0800 (PST) In-Reply-To: <1329323919.31256.329.camel@zakaz.uk.xensource.com> References: <4F3A90AD.50804@xen.org> <87r4xx9ubs.fsf@blp.benpfaff.org> <1329323919.31256.329.camel@zakaz.uk.xensource.com> Date: Thu, 16 Feb 2012 12:18:00 +0000 Message-ID: From: Lars Kurth To: Ian Campbell X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Cc: Ben Pfaff , "xen-devel@lists.xensource.com" , "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [Xen-devel] Pre4paration for the Xen Hackathon, March 6-8 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5710528084553248310==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5710528084553248310== Content-Type: multipart/alternative; boundary=14dae9340443b6b56604b913d19c --14dae9340443b6b56604b913d19c Content-Type: text/plain; charset=ISO-8859-1 Ben, Mike told me that there are some issues with XCP and Open vSwitch 1.4, where it would make sense to get Nicira and XCP guys into one room. In particular using OpenvSwitch 1.4 with the XCP toolstack on Debian Sid and Linux 3.2. The previous stable OVS release doesn't compile on Linux 3.2, so unless 1.4 works out of the box, we won't have OVS support in XCP toolstack on Ubuntu 12.04. That, plus maybe doing some early proof-of-concept work with Zeus (XCP on Fedora) may also make sense. Regards Lars On Wed, Feb 15, 2012 at 4:38 PM, Ian Campbell wrote: > On Tue, 2012-02-14 at 17:51 +0000, Ben Pfaff wrote: > > Lars Kurth writes: > > > > > I have made preparations to reach out to further groups in SIlicon > > > valley, and want to ensure that the core people are signed up before I > > > do this. > > > > Would it be helpful to have one of Nicira's Open vSwitch > > developers come? (Is anyone interested in discussing > > networking-related topics?) > > Hi Ben, > > I think there will some xapi/XCP folks there who I expect would be > interested in talking networking and vswitch in that context. > > In the context of xen-unstable and the libx/xl toolstacks there's not > much required for vswitch integration -- just a working hotplug script > mechanism and a suitable script. I actually have patches for the script > growing stale in my queue -- they don't work because of issues with > hotplug script running on shutdown (basically the xenstore info is gone > when the script runs so we can't remove the VIF from the switch). Roger > Pau Monee has a patch series fixing hotplug scripts and once it goes in > I'll resurrect my old patches. > > Ian. > > > I've tentatively received permission > > from management here to join for one or more days if it would be > > useful. We're in Silicon Valley anyway so it doesn't require > > much planning on our end. > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api > --14dae9340443b6b56604b913d19c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ben,

Mike told me that there are some issues with XCP and Open vSwit= ch 1.4, where it would make sense to get Nicira and XCP guys into one room.= In particular using OpenvSwitch 1.4 with the XCP toolstack on Debian Sid a= nd Linux 3.2. The previous stable OVS release doesn't compile on Linux = 3.2, so unless 1.4 works out of the box, we won't have OVS support in X= CP toolstack on Ubuntu 12.04. That, plus maybe doing some early proof-of-co= ncept work with Zeus (XCP on Fedora) may also make sense.

Regards
Lars

On Wed, Feb 15, 2012 = at 4:38 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
On Tue, 2012-02-14 at 17:51 +0000, Ben Pfaff wrote:
> Lars Kurth <lars.kurth@xen.or= g> writes:
>
> > I have made preparations to reach out to further groups in SIlico= n
> > valley, and want to ensure that the core people are signed up bef= ore I
> > do this.
>
> Would it be helpful to have one of Nicira's Open vSwitch
> developers come? (Is anyone interested in discussing
> networking-related topics?)

Hi Ben,

I think there will some xapi/XCP folks there who I expect would be
interested in talking networking and vswitch in that context.

In the context of xen-unstable and the libx/xl toolstacks there's not much required for vswitch integration -- just a working hotplug script
mechanism and a suitable script. I actually have patches for the script
growing stale in my queue -- they don't work because of issues with
hotplug script running on shutdown (basically the xenstore info is gone
when the script runs so we can't remove the VIF from the switch). Roger=
Pau Monee has a patch series fixing hotplug scripts and once it goes in
I'll resurrect my old patches.

Ian.

> =A0 I've tentatively received permission
> from management here to join for one or more days if it would be
> useful. =A0We're in Silicon Valley anyway so it doesn't requir= e
> much planning on our end.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenso= urce.com
> htt= p://lists.xensource.com/xen-devel



_______________________________________________
xen-api mailing list
xen-api@lists.xensource.com<= /a>
http://lists.xensource.com/mailman/listinfo/xen-api

--14dae9340443b6b56604b913d19c-- --===============5710528084553248310== 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 --===============5710528084553248310==-- From xen-api-bounces@lists.xen.org Fri Mar 02 22:12:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiU-0000M0-UU; Fri, 02 Mar 2012 22:12:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Ry0Hk-0005zs-F7 for xen-api@lists.xensource.com; Thu, 16 Feb 2012 12:18:04 +0000 Received: from [85.158.139.83:5794] by server-10.bemta-5.messagelabs.com id EB/C9-07861-BF3FC3F4; Thu, 16 Feb 2012 12:18:03 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1329394681!15258795!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29949 invoked from network); 16 Feb 2012 12:18:02 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 16 Feb 2012 12:18:02 -0000 Received: by iaeh11 with SMTP id h11so15658213iae.30 for ; Thu, 16 Feb 2012 04:18:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8pTAyESiwdZSCPlcJJnJJpas5+sDR3gehfsQPKlg48c=; b=lVdDpsELdGvH5Yzarccoeetwcyh1sXe9G0Qj/QmFy5Sln3wRYBbjIarnPxAK1Bh1rz Bjrj6uSOaGnD4xPRynTjd8VLJBZOYU/z6slrZQ/ko0uzlmVBIqI90mpTTcVivLrtZTqz HrpozOjvXJOWAVAQyD4tLOXEOBYpP6px7waRY= MIME-Version: 1.0 Received: by 10.50.160.131 with SMTP id xk3mr2623726igb.19.1329394680771; Thu, 16 Feb 2012 04:18:00 -0800 (PST) Received: by 10.231.7.14 with HTTP; Thu, 16 Feb 2012 04:18:00 -0800 (PST) In-Reply-To: <1329323919.31256.329.camel@zakaz.uk.xensource.com> References: <4F3A90AD.50804@xen.org> <87r4xx9ubs.fsf@blp.benpfaff.org> <1329323919.31256.329.camel@zakaz.uk.xensource.com> Date: Thu, 16 Feb 2012 12:18:00 +0000 Message-ID: From: Lars Kurth To: Ian Campbell X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Cc: Ben Pfaff , "xen-devel@lists.xensource.com" , "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [Xen-devel] Pre4paration for the Xen Hackathon, March 6-8 X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5710528084553248310==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5710528084553248310== Content-Type: multipart/alternative; boundary=14dae9340443b6b56604b913d19c --14dae9340443b6b56604b913d19c Content-Type: text/plain; charset=ISO-8859-1 Ben, Mike told me that there are some issues with XCP and Open vSwitch 1.4, where it would make sense to get Nicira and XCP guys into one room. In particular using OpenvSwitch 1.4 with the XCP toolstack on Debian Sid and Linux 3.2. The previous stable OVS release doesn't compile on Linux 3.2, so unless 1.4 works out of the box, we won't have OVS support in XCP toolstack on Ubuntu 12.04. That, plus maybe doing some early proof-of-concept work with Zeus (XCP on Fedora) may also make sense. Regards Lars On Wed, Feb 15, 2012 at 4:38 PM, Ian Campbell wrote: > On Tue, 2012-02-14 at 17:51 +0000, Ben Pfaff wrote: > > Lars Kurth writes: > > > > > I have made preparations to reach out to further groups in SIlicon > > > valley, and want to ensure that the core people are signed up before I > > > do this. > > > > Would it be helpful to have one of Nicira's Open vSwitch > > developers come? (Is anyone interested in discussing > > networking-related topics?) > > Hi Ben, > > I think there will some xapi/XCP folks there who I expect would be > interested in talking networking and vswitch in that context. > > In the context of xen-unstable and the libx/xl toolstacks there's not > much required for vswitch integration -- just a working hotplug script > mechanism and a suitable script. I actually have patches for the script > growing stale in my queue -- they don't work because of issues with > hotplug script running on shutdown (basically the xenstore info is gone > when the script runs so we can't remove the VIF from the switch). Roger > Pau Monee has a patch series fixing hotplug scripts and once it goes in > I'll resurrect my old patches. > > Ian. > > > I've tentatively received permission > > from management here to join for one or more days if it would be > > useful. We're in Silicon Valley anyway so it doesn't require > > much planning on our end. > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xensource.com > http://lists.xensource.com/mailman/listinfo/xen-api > --14dae9340443b6b56604b913d19c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ben,

Mike told me that there are some issues with XCP and Open vSwit= ch 1.4, where it would make sense to get Nicira and XCP guys into one room.= In particular using OpenvSwitch 1.4 with the XCP toolstack on Debian Sid a= nd Linux 3.2. The previous stable OVS release doesn't compile on Linux = 3.2, so unless 1.4 works out of the box, we won't have OVS support in X= CP toolstack on Ubuntu 12.04. That, plus maybe doing some early proof-of-co= ncept work with Zeus (XCP on Fedora) may also make sense.

Regards
Lars

On Wed, Feb 15, 2012 = at 4:38 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
On Tue, 2012-02-14 at 17:51 +0000, Ben Pfaff wrote:
> Lars Kurth <lars.kurth@xen.or= g> writes:
>
> > I have made preparations to reach out to further groups in SIlico= n
> > valley, and want to ensure that the core people are signed up bef= ore I
> > do this.
>
> Would it be helpful to have one of Nicira's Open vSwitch
> developers come? (Is anyone interested in discussing
> networking-related topics?)

Hi Ben,

I think there will some xapi/XCP folks there who I expect would be
interested in talking networking and vswitch in that context.

In the context of xen-unstable and the libx/xl toolstacks there's not much required for vswitch integration -- just a working hotplug script
mechanism and a suitable script. I actually have patches for the script
growing stale in my queue -- they don't work because of issues with
hotplug script running on shutdown (basically the xenstore info is gone
when the script runs so we can't remove the VIF from the switch). Roger=
Pau Monee has a patch series fixing hotplug scripts and once it goes in
I'll resurrect my old patches.

Ian.

> =A0 I've tentatively received permission
> from management here to join for one or more days if it would be
> useful. =A0We're in Silicon Valley anyway so it doesn't requir= e
> much planning on our end.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xenso= urce.com
> htt= p://lists.xensource.com/xen-devel



_______________________________________________
xen-api mailing list
xen-api@lists.xensource.com<= /a>
http://lists.xensource.com/mailman/listinfo/xen-api

--14dae9340443b6b56604b913d19c-- --===============5710528084553248310== 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 --===============5710528084553248310==-- From xen-api-bounces@lists.xen.org Fri Mar 02 22:12:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiU-0000Lq-L4; Fri, 02 Mar 2012 22:12:46 +0000 Received: from mail216.messagelabs.com ([85.158.143.99]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvpY-0006t5-4l; Mon, 13 Feb 2012 13:20:32 +0000 X-Env-Sender: ciprian.pantea@innovocompany.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1329139223!14102790!1 X-Originating-IP: [209.85.216.50] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23559 invoked from network); 13 Feb 2012 13:20:24 -0000 Received: from mail-qw0-f50.google.com (HELO mail-qw0-f50.google.com) (209.85.216.50) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 13:20:24 -0000 Received: by qabg27 with SMTP id g27so11449130qab.9 for ; Mon, 13 Feb 2012 05:20:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=innovocompany.com; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=Lh46/jTKJpimDu6LB0P94GMDFeeLahT0eq6qrKVqpmk=; b=ICCuAVs4bpGmnl8GVeGXfZunIvm+pkmjPYwOx09C1qLmV8iYyzKsoCbuyeaCP2MTxK SiR7fdtvThLzvs5nlLYeMsBFVK9JHfgqAd7Km+AbVcKb8S5qHZN3LxtC3y0xgYhyhtbx lUrcyixfvbtJa2QNf1HvJog6uCVkFceRQKU7Q= Received: by 10.229.111.165 with SMTP id s37mr9441751qcp.80.1329139223326; Mon, 13 Feb 2012 05:20:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.230.204 with HTTP; Mon, 13 Feb 2012 05:19:43 -0800 (PST) In-Reply-To: References: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> From: Ciprian Pantea Date: Mon, 13 Feb 2012 15:19:43 +0200 X-Google-Sender-Auth: bktvN5FeHOxoBappZ7ceFZq2C5g Message-ID: To: Scott Damron X-Gm-Message-State: ALoCoQlM9IIC0wfiMxJ7WS3lm06oUze3CoJ1Ba3LxCXD1gsEkbHMbAnBH2ew+TQCiUcx9bX4EDEA X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] Announcing XenMaster X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3620411554387458702==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3620411554387458702== Content-Type: multipart/alternative; boundary=002354470b88436fb004b8d85797 --002354470b88436fb004b8d85797 Content-Type: text/plain; charset=ISO-8859-1 I'd love to give it a try too but screenshots would have been better :) I'm not clear though on the list of features and I don't find any on your site either. Good job! PS: try to get rid of java in the future On Mon, Feb 13, 2012 at 14:41, Scott Damron wrote: > Instead of harshing on your for using Java, I am going to say - Nicely > done! I use either Linux or Mac OS X workstations, and have to run a > VM of Windows if I want to use a GUI to manage my Xen boxes. I > actually prefer to do the management via a GUI because I don't have a > lot of time to waste on trying to remember all of the commands to do > stuff. Thank you for the hard work, I will certainly be giving it a > try. > > Regards, > > Scott > > On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet > wrote: > > We're happy to announce XenMaster, which has the ambitious goal to become > > the de facto frontend for Xen with XCP. > > > > We've had the opportunity to present our project to some of the Xen/XCP > > developers and now it's time to announce the project to a larger public. > > XenMaster, in short, is a HTML5 frontend coupled to a Java backend > > delivering a rich UI for Xen, targeted at end users. > > At the moment, one is able to successfully add NFS ISO repositories and > > iSCSI/NFS storage repositories (iSCSI currently only works on XenServer > > 5.6), create a HVM VM and control it via a VNC shell. > > > > Development thus far has been carried out by Jorgen Evens, frontend lead > and > > Wannes De Smet, project lead and backend developer. Of course, we now > would > > like to welcome you in becoming a tester and/or contributor! > > You can find more information at xen-master.org, to install and > configure > > XenMaster. If you'd like to help and have experience in developing Java > > and/or Javascript, load the source in your favorite IDE and have at it! > > > > If you have any questions at all, we'll be happy to answer them here or > > through GitHub. > > > > We hope to welcome you in using XenMaster! > > Jorgen Evens > > Wannes De Smet > > XenMaster > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > --002354470b88436fb004b8d85797 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'd love to give it a try too but screenshots would have been better :)=
I'm not clear though on the list of features and I don't find = any on your site either.


Good job!<= /div>
PS: try to get rid of java in the future


=
On Mon, Feb 13, 2012 at 14:41, Scott Damron <sdamron@gmail.com> wrote:
Instead of harshing on your for using Java, = I am going to say - Nicely
done! =A0I use either Linux or Mac OS X workstations, and have to run a
VM of Windows if I want to use a GUI to manage my Xen boxes. =A0I
actually prefer to do the management via a GUI because I don't have a lot of time to waste on trying to remember all of the commands to do
stuff. =A0Thank you for the hard work, I will certainly be giving it a
try.

Regards,

Scott

On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet <wannes321@gmail.com> wrote:
> We're happy to announce XenMaster, which has the ambitious goal to= become
> the de facto frontend for Xen with XCP.
>
> We've had the opportunity to present our project to some of the Xe= n/XCP
> developers and now it's time to announce the project to a larger p= ublic.
> XenMaster, in short, is a HTML5 frontend coupled to a Java backend
> delivering a rich UI for Xen, targeted at end users.
> At the moment, one is able to successfully add NFS ISO repositories an= d
> iSCSI/NFS storage repositories (iSCSI currently only works on XenServe= r
> 5.6), create a HVM VM and control it via a VNC shell.
>
> Development thus far has been carried out by Jorgen Evens, frontend le= ad and
> Wannes De Smet, project lead and backend developer. Of course, we now = would
> like to welcome you in becoming a tester and/or contributor!
> You can find more information at xen-master.org, to install and configure
> XenMaster. If you'd like to help and have experience in developing= Java
> and/or Javascript, load the source in your favorite IDE and have at it= !
>
> If you have any questions at all, we'll be happy to answer them he= re or
> through GitHub.
>
> We hope to welcome you in using XenMaster!
> Jorgen Evens
> Wannes De Smet
> XenMaster
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xenso= urce.com
> htt= p://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.= com
http://l= ists.xensource.com/xen-users

--002354470b88436fb004b8d85797-- --===============3620411554387458702== 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 --===============3620411554387458702==-- From xen-api-bounces@lists.xen.org Fri Mar 02 22:12:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 02 Mar 2012 22:12:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S3aiU-0000Lq-L4; Fri, 02 Mar 2012 22:12:46 +0000 Received: from mail216.messagelabs.com ([85.158.143.99]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1RwvpY-0006t5-4l; Mon, 13 Feb 2012 13:20:32 +0000 X-Env-Sender: ciprian.pantea@innovocompany.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1329139223!14102790!1 X-Originating-IP: [209.85.216.50] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23559 invoked from network); 13 Feb 2012 13:20:24 -0000 Received: from mail-qw0-f50.google.com (HELO mail-qw0-f50.google.com) (209.85.216.50) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Feb 2012 13:20:24 -0000 Received: by qabg27 with SMTP id g27so11449130qab.9 for ; Mon, 13 Feb 2012 05:20:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=innovocompany.com; s=google; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=Lh46/jTKJpimDu6LB0P94GMDFeeLahT0eq6qrKVqpmk=; b=ICCuAVs4bpGmnl8GVeGXfZunIvm+pkmjPYwOx09C1qLmV8iYyzKsoCbuyeaCP2MTxK SiR7fdtvThLzvs5nlLYeMsBFVK9JHfgqAd7Km+AbVcKb8S5qHZN3LxtC3y0xgYhyhtbx lUrcyixfvbtJa2QNf1HvJog6uCVkFceRQKU7Q= Received: by 10.229.111.165 with SMTP id s37mr9441751qcp.80.1329139223326; Mon, 13 Feb 2012 05:20:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.230.204 with HTTP; Mon, 13 Feb 2012 05:19:43 -0800 (PST) In-Reply-To: References: <0C8A6062-597B-4914-B150-0FF8917D81C8@gmail.com> From: Ciprian Pantea Date: Mon, 13 Feb 2012 15:19:43 +0200 X-Google-Sender-Auth: bktvN5FeHOxoBappZ7ceFZq2C5g Message-ID: To: Scott Damron X-Gm-Message-State: ALoCoQlM9IIC0wfiMxJ7WS3lm06oUze3CoJ1Ba3LxCXD1gsEkbHMbAnBH2ew+TQCiUcx9bX4EDEA X-Mailman-Approved-At: Fri, 02 Mar 2012 22:12:45 +0000 Cc: xen-users@lists.xensource.com, xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] Announcing XenMaster X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3620411554387458702==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============3620411554387458702== Content-Type: multipart/alternative; boundary=002354470b88436fb004b8d85797 --002354470b88436fb004b8d85797 Content-Type: text/plain; charset=ISO-8859-1 I'd love to give it a try too but screenshots would have been better :) I'm not clear though on the list of features and I don't find any on your site either. Good job! PS: try to get rid of java in the future On Mon, Feb 13, 2012 at 14:41, Scott Damron wrote: > Instead of harshing on your for using Java, I am going to say - Nicely > done! I use either Linux or Mac OS X workstations, and have to run a > VM of Windows if I want to use a GUI to manage my Xen boxes. I > actually prefer to do the management via a GUI because I don't have a > lot of time to waste on trying to remember all of the commands to do > stuff. Thank you for the hard work, I will certainly be giving it a > try. > > Regards, > > Scott > > On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet > wrote: > > We're happy to announce XenMaster, which has the ambitious goal to become > > the de facto frontend for Xen with XCP. > > > > We've had the opportunity to present our project to some of the Xen/XCP > > developers and now it's time to announce the project to a larger public. > > XenMaster, in short, is a HTML5 frontend coupled to a Java backend > > delivering a rich UI for Xen, targeted at end users. > > At the moment, one is able to successfully add NFS ISO repositories and > > iSCSI/NFS storage repositories (iSCSI currently only works on XenServer > > 5.6), create a HVM VM and control it via a VNC shell. > > > > Development thus far has been carried out by Jorgen Evens, frontend lead > and > > Wannes De Smet, project lead and backend developer. Of course, we now > would > > like to welcome you in becoming a tester and/or contributor! > > You can find more information at xen-master.org, to install and > configure > > XenMaster. If you'd like to help and have experience in developing Java > > and/or Javascript, load the source in your favorite IDE and have at it! > > > > If you have any questions at all, we'll be happy to answer them here or > > through GitHub. > > > > We hope to welcome you in using XenMaster! > > Jorgen Evens > > Wannes De Smet > > XenMaster > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > --002354470b88436fb004b8d85797 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'd love to give it a try too but screenshots would have been better :)=
I'm not clear though on the list of features and I don't find = any on your site either.


Good job!<= /div>
PS: try to get rid of java in the future


=
On Mon, Feb 13, 2012 at 14:41, Scott Damron <sdamron@gmail.com> wrote:
Instead of harshing on your for using Java, = I am going to say - Nicely
done! =A0I use either Linux or Mac OS X workstations, and have to run a
VM of Windows if I want to use a GUI to manage my Xen boxes. =A0I
actually prefer to do the management via a GUI because I don't have a lot of time to waste on trying to remember all of the commands to do
stuff. =A0Thank you for the hard work, I will certainly be giving it a
try.

Regards,

Scott

On Sat, Feb 11, 2012 at 1:00 PM, Wannes De Smet <wannes321@gmail.com> wrote:
> We're happy to announce XenMaster, which has the ambitious goal to= become
> the de facto frontend for Xen with XCP.
>
> We've had the opportunity to present our project to some of the Xe= n/XCP
> developers and now it's time to announce the project to a larger p= ublic.
> XenMaster, in short, is a HTML5 frontend coupled to a Java backend
> delivering a rich UI for Xen, targeted at end users.
> At the moment, one is able to successfully add NFS ISO repositories an= d
> iSCSI/NFS storage repositories (iSCSI currently only works on XenServe= r
> 5.6), create a HVM VM and control it via a VNC shell.
>
> Development thus far has been carried out by Jorgen Evens, frontend le= ad and
> Wannes De Smet, project lead and backend developer. Of course, we now = would
> like to welcome you in becoming a tester and/or contributor!
> You can find more information at xen-master.org, to install and configure
> XenMaster. If you'd like to help and have experience in developing= Java
> and/or Javascript, load the source in your favorite IDE and have at it= !
>
> If you have any questions at all, we'll be happy to answer them he= re or
> through GitHub.
>
> We hope to welcome you in using XenMaster!
> Jorgen Evens
> Wannes De Smet
> XenMaster
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xenso= urce.com
> htt= p://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.= com
http://l= ists.xensource.com/xen-users

--002354470b88436fb004b8d85797-- --===============3620411554387458702== 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 --===============3620411554387458702==-- From xen-api-bounces@lists.xen.org Tue Mar 06 09:47:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 09:47:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4qzE-0005ft-Oz; Tue, 06 Mar 2012 09:47:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4qzD-0005fo-VY for xen-api@lists.xensource.com; Tue, 06 Mar 2012 09:47:16 +0000 Received: from [85.158.139.83:48247] by server-11.bemta-5.messagelabs.com id 42/2F-12959-32DD55F4; Tue, 06 Mar 2012 09:47:15 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-14.tower-182.messagelabs.com!1331027234!17197763!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12324 invoked from network); 6 Mar 2012 09:47:14 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-14.tower-182.messagelabs.com with SMTP; 6 Mar 2012 09:47:14 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id i9nE1i0033zjds1039nEEg; Tue, 06 Mar 2012 10:47:14 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 0F4F0744E2 for ; Tue, 6 Mar 2012 10:47:14 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JHXcPJRELC4K; Tue, 6 Mar 2012 10:47:13 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id ACF9874078; Tue, 6 Mar 2012 10:47:12 +0100 (CET) Message-ID: <4F55DD20.3090507@tranquil-it-systems.fr> Date: Tue, 06 Mar 2012 10:47:12 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" Subject: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello everyone, I wanted to know if any of you had some experience with building a = redundant xcp/xenserver cluster based on drbd. In this setup I would = like to avoid a separate iscsi SAN, and have replicated local storage. There are docs on the internet showing how to set up a dual primary drbd = SR on xenserver/xcp. It works fine with live migration and all, but when = trying disaster scenario, like severing the drbd replication link, one = gets a split brain scenario that cannot be unsolved. It should be doable = if xapi had a smart understanding of drbd, but currently it is just a SR = like others. So it is a no-go for the time being. I also tried a drbd primary-secondary scenario, with re-export with iet = iscsi target, but for the moment I have unresolved performance issues = (will try also with scst target). So I wanted to know if any of you had any experience or hints with this = kind of setup : a dual active/active XCP servers with local SR = replicated with primary-secondary DRBD, re-exported with iscsi or aoe or = whatever. Cheers, Denis Cardon -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 06 09:47:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 09:47:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4qzE-0005ft-Oz; Tue, 06 Mar 2012 09:47:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4qzD-0005fo-VY for xen-api@lists.xensource.com; Tue, 06 Mar 2012 09:47:16 +0000 Received: from [85.158.139.83:48247] by server-11.bemta-5.messagelabs.com id 42/2F-12959-32DD55F4; Tue, 06 Mar 2012 09:47:15 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-14.tower-182.messagelabs.com!1331027234!17197763!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12324 invoked from network); 6 Mar 2012 09:47:14 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-14.tower-182.messagelabs.com with SMTP; 6 Mar 2012 09:47:14 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id i9nE1i0033zjds1039nEEg; Tue, 06 Mar 2012 10:47:14 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 0F4F0744E2 for ; Tue, 6 Mar 2012 10:47:14 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JHXcPJRELC4K; Tue, 6 Mar 2012 10:47:13 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id ACF9874078; Tue, 6 Mar 2012 10:47:12 +0100 (CET) Message-ID: <4F55DD20.3090507@tranquil-it-systems.fr> Date: Tue, 06 Mar 2012 10:47:12 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" Subject: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hello everyone, I wanted to know if any of you had some experience with building a = redundant xcp/xenserver cluster based on drbd. In this setup I would = like to avoid a separate iscsi SAN, and have replicated local storage. There are docs on the internet showing how to set up a dual primary drbd = SR on xenserver/xcp. It works fine with live migration and all, but when = trying disaster scenario, like severing the drbd replication link, one = gets a split brain scenario that cannot be unsolved. It should be doable = if xapi had a smart understanding of drbd, but currently it is just a SR = like others. So it is a no-go for the time being. I also tried a drbd primary-secondary scenario, with re-export with iet = iscsi target, but for the moment I have unresolved performance issues = (will try also with scst target). So I wanted to know if any of you had any experience or hints with this = kind of setup : a dual active/active XCP servers with local SR = replicated with primary-secondary DRBD, re-exported with iscsi or aoe or = whatever. Cheers, Denis Cardon -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 06 10:22:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 10:22:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4rXP-0006I4-Dg; Tue, 06 Mar 2012 10:22:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4rXO-0006Hz-23 for xen-api@lists.xen.org; Tue, 06 Mar 2012 10:22:34 +0000 Received: from [85.158.138.51:30144] by server-10.bemta-3.messagelabs.com id BE/C0-13338-965E55F4; Tue, 06 Mar 2012 10:22:33 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1331029352!16344415!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19329 invoked from network); 6 Mar 2012 10:22:32 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Mar 2012 10:22:32 -0000 Received: by lahe6 with SMTP id e6so7699204lah.32 for ; Tue, 06 Mar 2012 02:22:31 -0800 (PST) Received-SPF: pass (google.com: domain of george.shuklin@gmail.com designates 10.112.48.164 as permitted sender) client-ip=10.112.48.164; Authentication-Results: mr.google.com; spf=pass (google.com: domain of george.shuklin@gmail.com designates 10.112.48.164 as permitted sender) smtp.mail=george.shuklin@gmail.com; dkim=pass header.i=george.shuklin@gmail.com Received: from mr.google.com ([10.112.48.164]) by 10.112.48.164 with SMTP id m4mr1042067lbn.79.1331029351977 (num_hops = 1); Tue, 06 Mar 2012 02:22:31 -0800 (PST) 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=Wsrk0oeUoHd/dBkn2WRUjPUjoBQVGYc2y/0+Y7UgLJA=; b=Pg4G1HIzOPbRUgpe65VGSSo9m/FyFc1ioRJ31s1m1Q8FsUiTrazsB8FiAYPtzIrU5X eM4S6b3SqdTBpd8gMguaXSgZ8Yusu2STdZFpPtEduvChVSHsr7ODW/1RUhFWiP4cL+e1 z+SDk196f0db/UPrL89t7pDFYI7asNOqfauEa+NYpUP10cBqWoxMUa3ddHDb/iCosfv9 cN8tR3GK/1Ljiw0JwmDhhuTXtfLS9W6Q60otL2Pqa8+P2GGh/9zA0eokoomhu/ysszEf x0ZxggCB/ssb57/1FbwHl2fFQaeo48cXZU66BNYe1UxgXqvvnVPOG6GcINe4Sp/nHZAE IiVw== Received: by 10.112.48.164 with SMTP id m4mr854258lbn.79.1331029351843; Tue, 06 Mar 2012 02:22:31 -0800 (PST) Received: from [192.168.40.44] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id nq2sm11619965lab.4.2012.03.06.02.22.29 (version=SSLv3 cipher=OTHER); Tue, 06 Mar 2012 02:22:30 -0800 (PST) Message-ID: <4F55E563.1020402@gmail.com> Date: Tue, 06 Mar 2012 14:22:27 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120217 Thunderbird/11.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F55DD20.3090507@tranquil-it-systems.fr> In-Reply-To: <4F55DD20.3090507@tranquil-it-systems.fr> Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Good day. We've tried that for internal laboratory. Problem: sometime drbd do additional IO and making storage out of sync. We've spend few weeks on this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), but it getting unstable after some time, so we gave up. On 06.03.2012 13:47, Denis Cardon wrote: > Hello everyone, > > I wanted to know if any of you had some experience with building a > redundant xcp/xenserver cluster based on drbd. In this setup I would > like to avoid a separate iscsi SAN, and have replicated local storage. > > There are docs on the internet showing how to set up a dual primary > drbd SR on xenserver/xcp. It works fine with live migration and all, > but when trying disaster scenario, like severing the drbd replication > link, one gets a split brain scenario that cannot be unsolved. It > should be doable if xapi had a smart understanding of drbd, but > currently it is just a SR like others. So it is a no-go for the time > being. > > I also tried a drbd primary-secondary scenario, with re-export with > iet iscsi target, but for the moment I have unresolved performance > issues (will try also with scst target). > > So I wanted to know if any of you had any experience or hints with > this kind of setup : a dual active/active XCP servers with local SR > replicated with primary-secondary DRBD, re-exported with iscsi or aoe > or whatever. > > Cheers, > > Denis Cardon > _______________________________________________ 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 06 10:22:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 10:22:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4rXP-0006I4-Dg; Tue, 06 Mar 2012 10:22:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4rXO-0006Hz-23 for xen-api@lists.xen.org; Tue, 06 Mar 2012 10:22:34 +0000 Received: from [85.158.138.51:30144] by server-10.bemta-3.messagelabs.com id BE/C0-13338-965E55F4; Tue, 06 Mar 2012 10:22:33 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1331029352!16344415!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19329 invoked from network); 6 Mar 2012 10:22:32 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 6 Mar 2012 10:22:32 -0000 Received: by lahe6 with SMTP id e6so7699204lah.32 for ; Tue, 06 Mar 2012 02:22:31 -0800 (PST) Received-SPF: pass (google.com: domain of george.shuklin@gmail.com designates 10.112.48.164 as permitted sender) client-ip=10.112.48.164; Authentication-Results: mr.google.com; spf=pass (google.com: domain of george.shuklin@gmail.com designates 10.112.48.164 as permitted sender) smtp.mail=george.shuklin@gmail.com; dkim=pass header.i=george.shuklin@gmail.com Received: from mr.google.com ([10.112.48.164]) by 10.112.48.164 with SMTP id m4mr1042067lbn.79.1331029351977 (num_hops = 1); Tue, 06 Mar 2012 02:22:31 -0800 (PST) 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=Wsrk0oeUoHd/dBkn2WRUjPUjoBQVGYc2y/0+Y7UgLJA=; b=Pg4G1HIzOPbRUgpe65VGSSo9m/FyFc1ioRJ31s1m1Q8FsUiTrazsB8FiAYPtzIrU5X eM4S6b3SqdTBpd8gMguaXSgZ8Yusu2STdZFpPtEduvChVSHsr7ODW/1RUhFWiP4cL+e1 z+SDk196f0db/UPrL89t7pDFYI7asNOqfauEa+NYpUP10cBqWoxMUa3ddHDb/iCosfv9 cN8tR3GK/1Ljiw0JwmDhhuTXtfLS9W6Q60otL2Pqa8+P2GGh/9zA0eokoomhu/ysszEf x0ZxggCB/ssb57/1FbwHl2fFQaeo48cXZU66BNYe1UxgXqvvnVPOG6GcINe4Sp/nHZAE IiVw== Received: by 10.112.48.164 with SMTP id m4mr854258lbn.79.1331029351843; Tue, 06 Mar 2012 02:22:31 -0800 (PST) Received: from [192.168.40.44] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id nq2sm11619965lab.4.2012.03.06.02.22.29 (version=SSLv3 cipher=OTHER); Tue, 06 Mar 2012 02:22:30 -0800 (PST) Message-ID: <4F55E563.1020402@gmail.com> Date: Tue, 06 Mar 2012 14:22:27 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120217 Thunderbird/11.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F55DD20.3090507@tranquil-it-systems.fr> In-Reply-To: <4F55DD20.3090507@tranquil-it-systems.fr> Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Good day. We've tried that for internal laboratory. Problem: sometime drbd do additional IO and making storage out of sync. We've spend few weeks on this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), but it getting unstable after some time, so we gave up. On 06.03.2012 13:47, Denis Cardon wrote: > Hello everyone, > > I wanted to know if any of you had some experience with building a > redundant xcp/xenserver cluster based on drbd. In this setup I would > like to avoid a separate iscsi SAN, and have replicated local storage. > > There are docs on the internet showing how to set up a dual primary > drbd SR on xenserver/xcp. It works fine with live migration and all, > but when trying disaster scenario, like severing the drbd replication > link, one gets a split brain scenario that cannot be unsolved. It > should be doable if xapi had a smart understanding of drbd, but > currently it is just a SR like others. So it is a no-go for the time > being. > > I also tried a drbd primary-secondary scenario, with re-export with > iet iscsi target, but for the moment I have unresolved performance > issues (will try also with scst target). > > So I wanted to know if any of you had any experience or hints with > this kind of setup : a dual active/active XCP servers with local SR > replicated with primary-secondary DRBD, re-exported with iscsi or aoe > or whatever. > > Cheers, > > Denis Cardon > _______________________________________________ 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 06 17:12:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 17:12: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 1S4xvX-0006TO-9r; Tue, 06 Mar 2012 17:11:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4xvW-0006TJ-56 for xen-api@lists.xen.org; Tue, 06 Mar 2012 17:11:54 +0000 Received: from [193.109.254.147:36703] by server-3.bemta-14.messagelabs.com id 4D/0A-31466-955465F4; Tue, 06 Mar 2012 17:11:53 +0000 X-Env-Sender: a.balg@xincs.eu X-Msg-Ref: server-2.tower-27.messagelabs.com!1331053842!58799103!1 X-Originating-IP: [77.87.128.20] X-SpamReason: No, hits=1.8 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,HTML_MIME_NO_HTML_TAG,MIME_HTML_ONLY X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7299 invoked from network); 6 Mar 2012 17:10:42 -0000 Received: from mail.xincs.eu (HELO mail.xincs.eu) (77.87.128.20) by server-2.tower-27.messagelabs.com with SMTP; 6 Mar 2012 17:10:42 -0000 Received: from localhost (localhost [127.0.0.1]) by mail.xincs.eu (Postfix) with ESMTP id 62AFB603D; Tue, 6 Mar 2012 18:11:52 +0100 (CET) User-Agent: SOGoMail 2.0.0 MIME-Version: 1.0 from: "Andreas Balg" message-id: <1705-4f564580-21-1237ece0@23465200> to: "George Shuklin" date: Tue, 06 Mar 2012 17:11:52 +0000 in-reply-to: <4F55E563.1020402@gmail.com> Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2999639737490663887==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2999639737490663887== content-type: text/html; charset="utf-8" content-transfer-encoding: 7bit
Hi there maybe have a look at GlusterFs -

We have a running setup here (8 Nodes, 100 VMs) that share localstorage - but we use GlusterFS (running in Dom0 - yes something you should not do under no circumstances I know) instead of DRBD - and of course there is no iSCSI or other block-level storage in this set-up but NFS or just a BIG folder of apparently local Storage using native glusterFS that works well by now

  -  maybe you'll have alook at such an option ...

Gruss

Andreas Balg





Am Dienstag, 06. März 2012 11:22 CET, George Shuklin <george.shuklin@gmail.com> schrieb:

Good day.

We've tried that for internal laboratory. Problem: sometime drbd do
additional IO and making storage out of sync. We've spend few weeks on
this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR),
but it getting unstable after some time, so we gave up.



On 06.03.2012 13:47, Denis Cardon wrote:
> Hello everyone,
>
> I wanted to know if any of you had some experience with building a
> redundant xcp/xenserver cluster based on drbd. In this setup I would
> like to avoid a separate iscsi SAN, and have replicated local storage.
>
> There are docs on the internet showing how to set up a dual primary
> drbd SR on xenserver/xcp. It works fine with live migration and all,
> but when trying disaster scenario, like severing the drbd replication
> link, one gets a split brain scenario that cannot be unsolved. It
> should be doable if xapi had a smart understanding of drbd, but
> currently it is just a SR like others. So it is a no-go for the time
> being.
>
> I also tried a drbd primary-secondary scenario, with re-export with
> iet iscsi target, but for the moment I have unresolved performance
> issues (will try also with scst target).
>
> So I wanted to know if any of you had any experience or hints with
> this kind of setup : a dual active/active XCP servers with local SR
> replicated with primary-secondary DRBD, re-exported with iscsi or aoe
> or whatever.
>
> Cheers,
>
> Denis Cardon
>


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


--===============2999639737490663887== 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 --===============2999639737490663887==-- From xen-api-bounces@lists.xen.org Tue Mar 06 17:12:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 17:12: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 1S4xvX-0006TO-9r; Tue, 06 Mar 2012 17:11:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4xvW-0006TJ-56 for xen-api@lists.xen.org; Tue, 06 Mar 2012 17:11:54 +0000 Received: from [193.109.254.147:36703] by server-3.bemta-14.messagelabs.com id 4D/0A-31466-955465F4; Tue, 06 Mar 2012 17:11:53 +0000 X-Env-Sender: a.balg@xincs.eu X-Msg-Ref: server-2.tower-27.messagelabs.com!1331053842!58799103!1 X-Originating-IP: [77.87.128.20] X-SpamReason: No, hits=1.8 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,HTML_MIME_NO_HTML_TAG,MIME_HTML_ONLY X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7299 invoked from network); 6 Mar 2012 17:10:42 -0000 Received: from mail.xincs.eu (HELO mail.xincs.eu) (77.87.128.20) by server-2.tower-27.messagelabs.com with SMTP; 6 Mar 2012 17:10:42 -0000 Received: from localhost (localhost [127.0.0.1]) by mail.xincs.eu (Postfix) with ESMTP id 62AFB603D; Tue, 6 Mar 2012 18:11:52 +0100 (CET) User-Agent: SOGoMail 2.0.0 MIME-Version: 1.0 from: "Andreas Balg" message-id: <1705-4f564580-21-1237ece0@23465200> to: "George Shuklin" date: Tue, 06 Mar 2012 17:11:52 +0000 in-reply-to: <4F55E563.1020402@gmail.com> Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2999639737490663887==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2999639737490663887== content-type: text/html; charset="utf-8" content-transfer-encoding: 7bit
Hi there maybe have a look at GlusterFs -

We have a running setup here (8 Nodes, 100 VMs) that share localstorage - but we use GlusterFS (running in Dom0 - yes something you should not do under no circumstances I know) instead of DRBD - and of course there is no iSCSI or other block-level storage in this set-up but NFS or just a BIG folder of apparently local Storage using native glusterFS that works well by now

  -  maybe you'll have alook at such an option ...

Gruss

Andreas Balg





Am Dienstag, 06. März 2012 11:22 CET, George Shuklin <george.shuklin@gmail.com> schrieb:

Good day.

We've tried that for internal laboratory. Problem: sometime drbd do
additional IO and making storage out of sync. We've spend few weeks on
this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR),
but it getting unstable after some time, so we gave up.



On 06.03.2012 13:47, Denis Cardon wrote:
> Hello everyone,
>
> I wanted to know if any of you had some experience with building a
> redundant xcp/xenserver cluster based on drbd. In this setup I would
> like to avoid a separate iscsi SAN, and have replicated local storage.
>
> There are docs on the internet showing how to set up a dual primary
> drbd SR on xenserver/xcp. It works fine with live migration and all,
> but when trying disaster scenario, like severing the drbd replication
> link, one gets a split brain scenario that cannot be unsolved. It
> should be doable if xapi had a smart understanding of drbd, but
> currently it is just a SR like others. So it is a no-go for the time
> being.
>
> I also tried a drbd primary-secondary scenario, with re-export with
> iet iscsi target, but for the moment I have unresolved performance
> issues (will try also with scst target).
>
> So I wanted to know if any of you had any experience or hints with
> this kind of setup : a dual active/active XCP servers with local SR
> replicated with primary-secondary DRBD, re-exported with iscsi or aoe
> or whatever.
>
> Cheers,
>
> Denis Cardon
>


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


--===============2999639737490663887== 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 --===============2999639737490663887==-- From xen-api-bounces@lists.xen.org Tue Mar 06 18:06:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 18:06: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 1S4ymh-00079N-IG; Tue, 06 Mar 2012 18:06:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4ymg-00079I-S1 for xen-api@lists.xen.org; Tue, 06 Mar 2012 18:06:51 +0000 Received: from [193.109.254.147:22916] by server-8.bemta-14.messagelabs.com id B8/75-04087-A32565F4; Tue, 06 Mar 2012 18:06:50 +0000 X-Env-Sender: lucasdss@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1331057160!57999123!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23140 invoked from network); 6 Mar 2012 18:06:01 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Mar 2012 18:06:01 -0000 Received: by iafj26 with SMTP id j26so9820807iaf.32 for ; Tue, 06 Mar 2012 10:06:47 -0800 (PST) Received-SPF: pass (google.com: domain of lucasdss@gmail.com designates 10.50.85.227 as permitted sender) client-ip=10.50.85.227; Authentication-Results: mr.google.com; spf=pass (google.com: domain of lucasdss@gmail.com designates 10.50.85.227 as permitted sender) smtp.mail=lucasdss@gmail.com; dkim=pass header.i=lucasdss@gmail.com Received: from mr.google.com ([10.50.85.227]) by 10.50.85.227 with SMTP id k3mr11252498igz.17.1331057207302 (num_hops = 1); Tue, 06 Mar 2012 10:06:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7aEt0rIPJdDArIeLECylxTBuK4tAgrJrmH52DzokoQ0=; b=P66ACwi5iRUjQ1eHzOlR1xdHY+yYICDDjM22fCbZtrjzMRJJ78Aa1w9NxDcYtA2edo m/HyBy6q5Gz5rc7Iz7mhvVN/BF9L9n/GThshsg/EC1g1fuwaiwCbqYHxCPqqXBfqZoMc +MLQBWelFE6jNsklo+KGksyYmaMyfLfMJPHhPrGHhiH4wpm3uuFbHPODtCQrOJUhdB/9 UOJqZnudrvXMw8hbu5xqv+ws+xhK/TENu95Yv3po7xMnVuShnz12VdK9U0e5OctDO7Ro y6OyyUZ83CZ4mvgFZjFAFgJyEoCs7fSRyyUBjozBq7aq8UJ5JzETl5VF58IygDGml2hF fUQg== Received: by 10.50.85.227 with SMTP id k3mr9370365igz.17.1331057207234; Tue, 06 Mar 2012 10:06:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.181.133 with HTTP; Tue, 6 Mar 2012 10:06:07 -0800 (PST) In-Reply-To: <1705-4f564580-21-1237ece0@23465200> References: <4F55E563.1020402@gmail.com> <1705-4f564580-21-1237ece0@23465200> From: Lucas de Souza Santos Date: Tue, 6 Mar 2012 15:06:07 -0300 Message-ID: To: Andreas Balg Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5274900653774358729==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5274900653774358729== Content-Type: multipart/alternative; boundary=e89a8f3baee503516104ba96e8d9 --e89a8f3baee503516104ba96e8d9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Did you look at http://code.google.com/p/ganeti/ ? - Support for Xen virtualization: - Support for PVM and HVM instances - Live migration support - Virtual console (on PVM) or VNC (on HVM) to control instances - Support for virtio or emulated devices ..... - Disk management: - Plain LVM volumes - Files (from Ganeti 2.0) - across-the-network raid1 (using DRBD ) for quick recovery in case of physical system failure - Instance disk partitioning supported from Ganeti 2.0 - Export/import mechanism for backup purposes or migration between clusters, or - Automated instance migration across clusters (since Ganeti 2.2) Lucas de Souza Santos (ldss) On Tue, Mar 6, 2012 at 2:11 PM, Andreas Balg wrote: > > Hi there maybe have a look at GlusterFs - > > We have a running setup here (8 Nodes, 100 VMs) that share localstorage - > but we use GlusterFS (running in Dom0 - yes something you should not do > under no circumstances I know) instead of DRBD - and of course there is n= o > iSCSI or other block-level storage in this set-up but NFS or just a BIG > folder of apparently local Storage using native glusterFS that works well > by now > > - maybe you'll have alook at such an option ... > > Gruss > > Andreas Balg > > > > > > Am Dienstag, 06. M=E4rz 2012 11:22 CET, George Shuklin < > george.shuklin@gmail.com> schrieb: > > > Good day. > > We've tried that for internal laboratory. Problem: sometime drbd do > additional IO and making storage out of sync. We've spend few weeks on > this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), > but it getting unstable after some time, so we gave up. > > > > On 06.03.2012 13:47, Denis Cardon wrote: > > Hello everyone, > > > > I wanted to know if any of you had some experience with building a > > redundant xcp/xenserver cluster based on drbd. In this setup I would > > like to avoid a separate iscsi SAN, and have replicated local storage. > > > > There are docs on the internet showing how to set up a dual primary > > drbd SR on xenserver/xcp. It works fine with live migration and all, > > but when trying disaster scenario, like severing the drbd replication > > link, one gets a split brain scenario that cannot be unsolved. It > > should be doable if xapi had a smart understanding of drbd, but > > currently it is just a SR like others. So it is a no-go for the time > > being. > > > > I also tried a drbd primary-secondary scenario, with re-export with > > iet iscsi target, but for the moment I have unresolved performance > > issues (will try also with scst target). > > > > So I wanted to know if any of you had any experience or hints with > > this kind of setup : a dual active/active XCP servers with local SR > > replicated with primary-secondary DRBD, re-exported with iscsi or aoe > > or whatever. > > > > Cheers, > > > > Denis Cardon > > > > > _______________________________________________ > 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 > > --e89a8f3baee503516104ba96e8d9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Did you look at=A0http://code.= google.com/p/ganeti/=A0?

  • Support for Xen virtualization:
    • Support for PVM and HVM instances
    • Li= ve migration support
    • Virtual console (on PVM) or VNC (on HVM) = to control instances
    • Support for virt= io or emulated devices
= .....

  • = Disk management:
    • Plain LVM volumes
    • Files (from G= aneti 2.0)
    • across-the-network raid1 (= using=A0DRBD) for quick recovery in case of physical system failure=
  • Instance disk partitioning supported= from Ganeti 2.0
  • Export/import mechan= ism for backup purposes or migration between clusters, or
  • Automated instance migration across clusters (since Ganeti 2.2)

Lucas de Souza Santos (ldss)


On Tue, Mar 6, 2012 at 2:11 PM, Andreas = Balg <a.balg@xincs.= eu> wrote:

Hi there maybe have a look at GlusterFs -

We have a running setup here (8 Nodes, 100 VMs) that share localstorage - b= ut we use GlusterFS (running in Dom0 - yes something you should not do unde= r no circumstances I know) instead of DRBD - and of course there is no iSCS= I or other block-level storage in this set-up but NFS or just a BIG folder = of apparently local Storage using native glusterFS that works well by now
=A0 -=A0 maybe you'll have alook at such an option ...

Gruss

Andreas Balg





Am Dienstag, 06. M=E4rz 2012 11:22 CET, George Shuklin <george.shuklin@gmail.com&= gt; schrieb:


Good day.

We've tried that for internal laboratory. Problem: sometime drbd do additional IO and making storage out of sync. We've spend few weeks on=
this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), but it getting unstable after some time, so we gave up.



On 06.03.2012 13:47, Denis Cardon wrote:
> Hello everyone,
>
> I wanted to know if any of you had some experience with building a > redundant xcp/xenserver cluster based on drbd. In this setup I would<= br> > like to avoid a separate iscsi SAN, and have replicated local storage= .
>
> There are docs on the internet showing how to set up a dual primary > drbd SR on xenserver/xcp. It works fine with live migration and all,<= br> > but when trying disaster scenario, like severing the drbd replication=
> link, one gets a split brain scenario that cannot be unsolved. It
> should be doable if xapi had a smart understanding of drbd, but
> currently it is just a SR like others. So it is a no-go for the time<= br> > being.
>
> I also tried a drbd primary-secondary scenario, with re-export with > iet iscsi target, but for the moment I have unresolved performance > issues (will try also with scst target).
>
> So I wanted to know if any of you had any experience or hints with > this kind of setup : a dual active/active XCP servers with local SR > replicated with primary-secondary DRBD, re-exported with iscsi or aoe=
> or whatever.
>
> Cheers,
>
> Denis Cardon
>


_______________________________________________
xen-api mailing list
xen-api@lists.x= en.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


--e89a8f3baee503516104ba96e8d9-- --===============5274900653774358729== 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 --===============5274900653774358729==-- From xen-api-bounces@lists.xen.org Tue Mar 06 18:06:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 18:06: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 1S4ymh-00079N-IG; Tue, 06 Mar 2012 18:06:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4ymg-00079I-S1 for xen-api@lists.xen.org; Tue, 06 Mar 2012 18:06:51 +0000 Received: from [193.109.254.147:22916] by server-8.bemta-14.messagelabs.com id B8/75-04087-A32565F4; Tue, 06 Mar 2012 18:06:50 +0000 X-Env-Sender: lucasdss@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1331057160!57999123!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=1.4 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23140 invoked from network); 6 Mar 2012 18:06:01 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Mar 2012 18:06:01 -0000 Received: by iafj26 with SMTP id j26so9820807iaf.32 for ; Tue, 06 Mar 2012 10:06:47 -0800 (PST) Received-SPF: pass (google.com: domain of lucasdss@gmail.com designates 10.50.85.227 as permitted sender) client-ip=10.50.85.227; Authentication-Results: mr.google.com; spf=pass (google.com: domain of lucasdss@gmail.com designates 10.50.85.227 as permitted sender) smtp.mail=lucasdss@gmail.com; dkim=pass header.i=lucasdss@gmail.com Received: from mr.google.com ([10.50.85.227]) by 10.50.85.227 with SMTP id k3mr11252498igz.17.1331057207302 (num_hops = 1); Tue, 06 Mar 2012 10:06:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7aEt0rIPJdDArIeLECylxTBuK4tAgrJrmH52DzokoQ0=; b=P66ACwi5iRUjQ1eHzOlR1xdHY+yYICDDjM22fCbZtrjzMRJJ78Aa1w9NxDcYtA2edo m/HyBy6q5Gz5rc7Iz7mhvVN/BF9L9n/GThshsg/EC1g1fuwaiwCbqYHxCPqqXBfqZoMc +MLQBWelFE6jNsklo+KGksyYmaMyfLfMJPHhPrGHhiH4wpm3uuFbHPODtCQrOJUhdB/9 UOJqZnudrvXMw8hbu5xqv+ws+xhK/TENu95Yv3po7xMnVuShnz12VdK9U0e5OctDO7Ro y6OyyUZ83CZ4mvgFZjFAFgJyEoCs7fSRyyUBjozBq7aq8UJ5JzETl5VF58IygDGml2hF fUQg== Received: by 10.50.85.227 with SMTP id k3mr9370365igz.17.1331057207234; Tue, 06 Mar 2012 10:06:47 -0800 (PST) MIME-Version: 1.0 Received: by 10.231.181.133 with HTTP; Tue, 6 Mar 2012 10:06:07 -0800 (PST) In-Reply-To: <1705-4f564580-21-1237ece0@23465200> References: <4F55E563.1020402@gmail.com> <1705-4f564580-21-1237ece0@23465200> From: Lucas de Souza Santos Date: Tue, 6 Mar 2012 15:06:07 -0300 Message-ID: To: Andreas Balg Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5274900653774358729==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============5274900653774358729== Content-Type: multipart/alternative; boundary=e89a8f3baee503516104ba96e8d9 --e89a8f3baee503516104ba96e8d9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Did you look at http://code.google.com/p/ganeti/ ? - Support for Xen virtualization: - Support for PVM and HVM instances - Live migration support - Virtual console (on PVM) or VNC (on HVM) to control instances - Support for virtio or emulated devices ..... - Disk management: - Plain LVM volumes - Files (from Ganeti 2.0) - across-the-network raid1 (using DRBD ) for quick recovery in case of physical system failure - Instance disk partitioning supported from Ganeti 2.0 - Export/import mechanism for backup purposes or migration between clusters, or - Automated instance migration across clusters (since Ganeti 2.2) Lucas de Souza Santos (ldss) On Tue, Mar 6, 2012 at 2:11 PM, Andreas Balg wrote: > > Hi there maybe have a look at GlusterFs - > > We have a running setup here (8 Nodes, 100 VMs) that share localstorage - > but we use GlusterFS (running in Dom0 - yes something you should not do > under no circumstances I know) instead of DRBD - and of course there is n= o > iSCSI or other block-level storage in this set-up but NFS or just a BIG > folder of apparently local Storage using native glusterFS that works well > by now > > - maybe you'll have alook at such an option ... > > Gruss > > Andreas Balg > > > > > > Am Dienstag, 06. M=E4rz 2012 11:22 CET, George Shuklin < > george.shuklin@gmail.com> schrieb: > > > Good day. > > We've tried that for internal laboratory. Problem: sometime drbd do > additional IO and making storage out of sync. We've spend few weeks on > this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), > but it getting unstable after some time, so we gave up. > > > > On 06.03.2012 13:47, Denis Cardon wrote: > > Hello everyone, > > > > I wanted to know if any of you had some experience with building a > > redundant xcp/xenserver cluster based on drbd. In this setup I would > > like to avoid a separate iscsi SAN, and have replicated local storage. > > > > There are docs on the internet showing how to set up a dual primary > > drbd SR on xenserver/xcp. It works fine with live migration and all, > > but when trying disaster scenario, like severing the drbd replication > > link, one gets a split brain scenario that cannot be unsolved. It > > should be doable if xapi had a smart understanding of drbd, but > > currently it is just a SR like others. So it is a no-go for the time > > being. > > > > I also tried a drbd primary-secondary scenario, with re-export with > > iet iscsi target, but for the moment I have unresolved performance > > issues (will try also with scst target). > > > > So I wanted to know if any of you had any experience or hints with > > this kind of setup : a dual active/active XCP servers with local SR > > replicated with primary-secondary DRBD, re-exported with iscsi or aoe > > or whatever. > > > > Cheers, > > > > Denis Cardon > > > > > _______________________________________________ > 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 > > --e89a8f3baee503516104ba96e8d9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Did you look at=A0http://code.= google.com/p/ganeti/=A0?

  • Support for Xen virtualization:
    • Support for PVM and HVM instances
    • Li= ve migration support
    • Virtual console (on PVM) or VNC (on HVM) = to control instances
    • Support for virt= io or emulated devices
= .....

  • = Disk management:
    • Plain LVM volumes
    • Files (from G= aneti 2.0)
    • across-the-network raid1 (= using=A0DRBD) for quick recovery in case of physical system failure=
  • Instance disk partitioning supported= from Ganeti 2.0
  • Export/import mechan= ism for backup purposes or migration between clusters, or
  • Automated instance migration across clusters (since Ganeti 2.2)

Lucas de Souza Santos (ldss)


On Tue, Mar 6, 2012 at 2:11 PM, Andreas = Balg <a.balg@xincs.= eu> wrote:

Hi there maybe have a look at GlusterFs -

We have a running setup here (8 Nodes, 100 VMs) that share localstorage - b= ut we use GlusterFS (running in Dom0 - yes something you should not do unde= r no circumstances I know) instead of DRBD - and of course there is no iSCS= I or other block-level storage in this set-up but NFS or just a BIG folder = of apparently local Storage using native glusterFS that works well by now
=A0 -=A0 maybe you'll have alook at such an option ...

Gruss

Andreas Balg





Am Dienstag, 06. M=E4rz 2012 11:22 CET, George Shuklin <george.shuklin@gmail.com&= gt; schrieb:


Good day.

We've tried that for internal laboratory. Problem: sometime drbd do additional IO and making storage out of sync. We've spend few weeks on=
this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), but it getting unstable after some time, so we gave up.



On 06.03.2012 13:47, Denis Cardon wrote:
> Hello everyone,
>
> I wanted to know if any of you had some experience with building a > redundant xcp/xenserver cluster based on drbd. In this setup I would<= br> > like to avoid a separate iscsi SAN, and have replicated local storage= .
>
> There are docs on the internet showing how to set up a dual primary > drbd SR on xenserver/xcp. It works fine with live migration and all,<= br> > but when trying disaster scenario, like severing the drbd replication=
> link, one gets a split brain scenario that cannot be unsolved. It
> should be doable if xapi had a smart understanding of drbd, but
> currently it is just a SR like others. So it is a no-go for the time<= br> > being.
>
> I also tried a drbd primary-secondary scenario, with re-export with > iet iscsi target, but for the moment I have unresolved performance > issues (will try also with scst target).
>
> So I wanted to know if any of you had any experience or hints with > this kind of setup : a dual active/active XCP servers with local SR > replicated with primary-secondary DRBD, re-exported with iscsi or aoe=
> or whatever.
>
> Cheers,
>
> Denis Cardon
>


_______________________________________________
xen-api mailing list
xen-api@lists.x= en.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


--e89a8f3baee503516104ba96e8d9-- --===============5274900653774358729== 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 --===============5274900653774358729==-- From xen-api-bounces@lists.xen.org Tue Mar 06 19:15:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 19:15:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4zrD-0008Jv-0S; Tue, 06 Mar 2012 19:15:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4zrB-0008Jq-LQ for xen-api@lists.xen.org; Tue, 06 Mar 2012 19:15:33 +0000 Received: from [85.158.143.35:23210] by server-1.bemta-4.messagelabs.com id 03/DA-20925-452665F4; Tue, 06 Mar 2012 19:15:32 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-15.tower-21.messagelabs.com!1331061330!12432529!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26643 invoked from network); 6 Mar 2012 19:15:31 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-15.tower-21.messagelabs.com with SMTP; 6 Mar 2012 19:15:31 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id iKFV1i00B3zjds103KFVKe; Tue, 06 Mar 2012 20:15:30 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A80277450B; Tue, 6 Mar 2012 20:15:29 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r-kR0O5jL2eJ; Tue, 6 Mar 2012 20:15:28 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A280A7449C; Tue, 6 Mar 2012 20:15:28 +0100 (CET) Message-ID: <4F566250.30805@tranquil-it-systems.fr> Date: Tue, 06 Mar 2012 20:15:28 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F55DD20.3090507@tranquil-it-systems.fr> <4F55E563.1020402@gmail.com> In-Reply-To: <4F55E563.1020402@gmail.com> Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Georges, > We've tried that for internal laboratory. Problem: sometime drbd do > additional IO and making storage out of sync. We've spend few weeks on > this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), > but it getting unstable after some time, so we gave up. Actually I have not encountered instability in my test setup (the SR was = define directly over /dev/drbd0, no iscsi in between). During the test, = I was running iozone in a loop in VMs that were switch from host every = few minutes in a loop (linux and windows VMs) for a whole 48 hours. I have'nt encountered any issues during that stress test (set aside the = global warming). But when I went ahead with disaster recovery scenario, = it was a no go : severing the primary-primary drbd link left me with a = brain split to solve by hand. I was thinking to use the more conservative approach with the following = scenario. It adds the iscsi latency to the io path, but : XCP1 in xenpool XCP2 in xenpool =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D drbd-sr1 (primary) <-----> drbd-sr1 (secondary) exported to xenpool through iscsi target drbd-sr2 (secondary) <-----> drbd-sr2 (primary) exported to xenpool through iscsi target I have a few year of practice of drbd with primary/secondary setup on = iscsi san, and I am pretty confident the data should be safe with this = kind of setup, but I'm wondering of the behavior of a dom0 xen in this = situation. I'll give it a shot in the next few days. Thanks for your input. Denis > > > > On 06.03.2012 13:47, Denis Cardon wrote: >> Hello everyone, >> >> I wanted to know if any of you had some experience with building a >> redundant xcp/xenserver cluster based on drbd. In this setup I would >> like to avoid a separate iscsi SAN, and have replicated local storage. >> >> There are docs on the internet showing how to set up a dual primary >> drbd SR on xenserver/xcp. It works fine with live migration and all, >> but when trying disaster scenario, like severing the drbd replication >> link, one gets a split brain scenario that cannot be unsolved. It >> should be doable if xapi had a smart understanding of drbd, but >> currently it is just a SR like others. So it is a no-go for the time >> being. >> >> I also tried a drbd primary-secondary scenario, with re-export with >> iet iscsi target, but for the moment I have unresolved performance >> issues (will try also with scst target). >> >> So I wanted to know if any of you had any experience or hints with >> this kind of setup : a dual active/active XCP servers with local SR >> replicated with primary-secondary DRBD, re-exported with iscsi or aoe >> or whatever. >> >> Cheers, >> >> Denis Cardon >> > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 06 19:15:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 19:15:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4zrD-0008Jv-0S; Tue, 06 Mar 2012 19:15:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S4zrB-0008Jq-LQ for xen-api@lists.xen.org; Tue, 06 Mar 2012 19:15:33 +0000 Received: from [85.158.143.35:23210] by server-1.bemta-4.messagelabs.com id 03/DA-20925-452665F4; Tue, 06 Mar 2012 19:15:32 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-15.tower-21.messagelabs.com!1331061330!12432529!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26643 invoked from network); 6 Mar 2012 19:15:31 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-15.tower-21.messagelabs.com with SMTP; 6 Mar 2012 19:15:31 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id iKFV1i00B3zjds103KFVKe; Tue, 06 Mar 2012 20:15:30 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A80277450B; Tue, 6 Mar 2012 20:15:29 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r-kR0O5jL2eJ; Tue, 6 Mar 2012 20:15:28 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A280A7449C; Tue, 6 Mar 2012 20:15:28 +0100 (CET) Message-ID: <4F566250.30805@tranquil-it-systems.fr> Date: Tue, 06 Mar 2012 20:15:28 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F55DD20.3090507@tranquil-it-systems.fr> <4F55E563.1020402@gmail.com> In-Reply-To: <4F55E563.1020402@gmail.com> Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Georges, > We've tried that for internal laboratory. Problem: sometime drbd do > additional IO and making storage out of sync. We've spend few weeks on > this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), > but it getting unstable after some time, so we gave up. Actually I have not encountered instability in my test setup (the SR was = define directly over /dev/drbd0, no iscsi in between). During the test, = I was running iozone in a loop in VMs that were switch from host every = few minutes in a loop (linux and windows VMs) for a whole 48 hours. I have'nt encountered any issues during that stress test (set aside the = global warming). But when I went ahead with disaster recovery scenario, = it was a no go : severing the primary-primary drbd link left me with a = brain split to solve by hand. I was thinking to use the more conservative approach with the following = scenario. It adds the iscsi latency to the io path, but : XCP1 in xenpool XCP2 in xenpool =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D drbd-sr1 (primary) <-----> drbd-sr1 (secondary) exported to xenpool through iscsi target drbd-sr2 (secondary) <-----> drbd-sr2 (primary) exported to xenpool through iscsi target I have a few year of practice of drbd with primary/secondary setup on = iscsi san, and I am pretty confident the data should be safe with this = kind of setup, but I'm wondering of the behavior of a dom0 xen in this = situation. I'll give it a shot in the next few days. Thanks for your input. Denis > > > > On 06.03.2012 13:47, Denis Cardon wrote: >> Hello everyone, >> >> I wanted to know if any of you had some experience with building a >> redundant xcp/xenserver cluster based on drbd. In this setup I would >> like to avoid a separate iscsi SAN, and have replicated local storage. >> >> There are docs on the internet showing how to set up a dual primary >> drbd SR on xenserver/xcp. It works fine with live migration and all, >> but when trying disaster scenario, like severing the drbd replication >> link, one gets a split brain scenario that cannot be unsolved. It >> should be doable if xapi had a smart understanding of drbd, but >> currently it is just a SR like others. So it is a no-go for the time >> being. >> >> I also tried a drbd primary-secondary scenario, with re-export with >> iet iscsi target, but for the moment I have unresolved performance >> issues (will try also with scst target). >> >> So I wanted to know if any of you had any experience or hints with >> this kind of setup : a dual active/active XCP servers with local SR >> replicated with primary-secondary DRBD, re-exported with iscsi or aoe >> or whatever. >> >> Cheers, >> >> Denis Cardon >> > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 06 19:26:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 19:26:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S501C-0008Q6-Vn; Tue, 06 Mar 2012 19:25:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S501A-0008Q1-QE for xen-api@lists.xen.org; Tue, 06 Mar 2012 19:25:53 +0000 Received: from [85.158.143.99:53478] by server-2.bemta-4.messagelabs.com id 98/45-17550-FB4665F4; Tue, 06 Mar 2012 19:25:51 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-6.tower-216.messagelabs.com!1331061951!17897248!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18353 invoked from network); 6 Mar 2012 19:25:51 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-6.tower-216.messagelabs.com with SMTP; 6 Mar 2012 19:25:51 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id iKRq1i00D3zjds103KRqDn; Tue, 06 Mar 2012 20:25:50 +0100 X-CNFS-Analysis: v=2.0 cv=IuqcgcDg c=1 sm=1 a=AEg8uEn4syH+5OJmtawHBQ==:17 a=iY4vCD-PpcIA:10 a=l_naeu1CRK8A:10 a=wPDyFdB5xvgA:10 a=8nJEP1OIZ-IA:10 a=pGLkceISAAAA:8 a=mLnsDVdbAAAA:8 a=xUYM7ab_AAAA:8 a=tuGUK1l7Frj3umZdKzIA:9 a=L_vKnG8pI8-WnuAR1l0A:7 a=wPNLvfGTeEIA:10 a=MSl-tDqOz04A:10 a=AEg8uEn4syH+5OJmtawHBQ==:117 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 4962C7450B; Tue, 6 Mar 2012 20:25:50 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MxQlcBKGWz91; Tue, 6 Mar 2012 20:25:49 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 6E2BE7449C; Tue, 6 Mar 2012 20:25:49 +0100 (CET) Message-ID: <4F5664BD.20205@tranquil-it-systems.fr> Date: Tue, 06 Mar 2012 20:25:49 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: George Shuklin References: <1705-4f564580-21-1237ece0@23465200> In-Reply-To: <1705-4f564580-21-1237ece0@23465200> Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Andreas, > Hi there maybe have a look at GlusterFs - > > We have a running setup here (8 Nodes, 100 VMs) that share localstorage > - but we use GlusterFS (running in Dom0 - yes something you should not > do under no circumstances I know) instead of DRBD - and of course there > is no iSCSI or other block-level storage in this set-up but NFS or just > a BIG folder of apparently local Storage using native glusterFS that > works well by now > > - maybe you'll have alook at such an option ... definitly looks interesting ! Moreover you can use thin provisioning = with real thin vhd :-) How is the setup behaving in disaster recovery = scenarios? If you severe the link in between the two servers and the vhd needs to = grow, how does the slave server knows the next few blocks are still = available and have not been handed down to another vhd on the master server? Cheers, Denis > > Gruss > > Andreas Balg > > > > > > Am Dienstag, 06. M=E4rz 2012 11:22 CET, George Shuklin > schrieb: > >> Good day. >> >> We've tried that for internal laboratory. Problem: sometime drbd do >> additional IO and making storage out of sync. We've spend few weeks on >> this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), >> but it getting unstable after some time, so we gave up. >> >> >> >> On 06.03.2012 13:47, Denis Cardon wrote: >> > Hello everyone, >> > >> > I wanted to know if any of you had some experience with building a >> > redundant xcp/xenserver cluster based on drbd. In this setup I would >> > like to avoid a separate iscsi SAN, and have replicated local storage. >> > >> > There are docs on the internet showing how to set up a dual primary >> > drbd SR on xenserver/xcp. It works fine with live migration and all, >> > but when trying disaster scenario, like severing the drbd replication >> > link, one gets a split brain scenario that cannot be unsolved. It >> > should be doable if xapi had a smart understanding of drbd, but >> > currently it is just a SR like others. So it is a no-go for the time >> > being. >> > >> > I also tried a drbd primary-secondary scenario, with re-export with >> > iet iscsi target, but for the moment I have unresolved performance >> > issues (will try also with scst target). >> > >> > So I wanted to know if any of you had any experience or hints with >> > this kind of setup : a dual active/active XCP servers with local SR >> > replicated with primary-secondary DRBD, re-exported with iscsi or aoe >> > or whatever. >> > >> > Cheers, >> > >> > Denis Cardon >> > >> >> >> _______________________________________________ >> xen-api mailing list >> xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > > This body part will be downloaded on demand. -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 06 19:26:01 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 19:26:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S501C-0008Q6-Vn; Tue, 06 Mar 2012 19:25:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S501A-0008Q1-QE for xen-api@lists.xen.org; Tue, 06 Mar 2012 19:25:53 +0000 Received: from [85.158.143.99:53478] by server-2.bemta-4.messagelabs.com id 98/45-17550-FB4665F4; Tue, 06 Mar 2012 19:25:51 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-6.tower-216.messagelabs.com!1331061951!17897248!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18353 invoked from network); 6 Mar 2012 19:25:51 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-6.tower-216.messagelabs.com with SMTP; 6 Mar 2012 19:25:51 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id iKRq1i00D3zjds103KRqDn; Tue, 06 Mar 2012 20:25:50 +0100 X-CNFS-Analysis: v=2.0 cv=IuqcgcDg c=1 sm=1 a=AEg8uEn4syH+5OJmtawHBQ==:17 a=iY4vCD-PpcIA:10 a=l_naeu1CRK8A:10 a=wPDyFdB5xvgA:10 a=8nJEP1OIZ-IA:10 a=pGLkceISAAAA:8 a=mLnsDVdbAAAA:8 a=xUYM7ab_AAAA:8 a=tuGUK1l7Frj3umZdKzIA:9 a=L_vKnG8pI8-WnuAR1l0A:7 a=wPNLvfGTeEIA:10 a=MSl-tDqOz04A:10 a=AEg8uEn4syH+5OJmtawHBQ==:117 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 4962C7450B; Tue, 6 Mar 2012 20:25:50 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MxQlcBKGWz91; Tue, 6 Mar 2012 20:25:49 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 6E2BE7449C; Tue, 6 Mar 2012 20:25:49 +0100 (CET) Message-ID: <4F5664BD.20205@tranquil-it-systems.fr> Date: Tue, 06 Mar 2012 20:25:49 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: George Shuklin References: <1705-4f564580-21-1237ece0@23465200> In-Reply-To: <1705-4f564580-21-1237ece0@23465200> Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi Andreas, > Hi there maybe have a look at GlusterFs - > > We have a running setup here (8 Nodes, 100 VMs) that share localstorage > - but we use GlusterFS (running in Dom0 - yes something you should not > do under no circumstances I know) instead of DRBD - and of course there > is no iSCSI or other block-level storage in this set-up but NFS or just > a BIG folder of apparently local Storage using native glusterFS that > works well by now > > - maybe you'll have alook at such an option ... definitly looks interesting ! Moreover you can use thin provisioning = with real thin vhd :-) How is the setup behaving in disaster recovery = scenarios? If you severe the link in between the two servers and the vhd needs to = grow, how does the slave server knows the next few blocks are still = available and have not been handed down to another vhd on the master server? Cheers, Denis > > Gruss > > Andreas Balg > > > > > > Am Dienstag, 06. M=E4rz 2012 11:22 CET, George Shuklin > schrieb: > >> Good day. >> >> We've tried that for internal laboratory. Problem: sometime drbd do >> additional IO and making storage out of sync. We've spend few weeks on >> this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), >> but it getting unstable after some time, so we gave up. >> >> >> >> On 06.03.2012 13:47, Denis Cardon wrote: >> > Hello everyone, >> > >> > I wanted to know if any of you had some experience with building a >> > redundant xcp/xenserver cluster based on drbd. In this setup I would >> > like to avoid a separate iscsi SAN, and have replicated local storage. >> > >> > There are docs on the internet showing how to set up a dual primary >> > drbd SR on xenserver/xcp. It works fine with live migration and all, >> > but when trying disaster scenario, like severing the drbd replication >> > link, one gets a split brain scenario that cannot be unsolved. It >> > should be doable if xapi had a smart understanding of drbd, but >> > currently it is just a SR like others. So it is a no-go for the time >> > being. >> > >> > I also tried a drbd primary-secondary scenario, with re-export with >> > iet iscsi target, but for the moment I have unresolved performance >> > issues (will try also with scst target). >> > >> > So I wanted to know if any of you had any experience or hints with >> > this kind of setup : a dual active/active XCP servers with local SR >> > replicated with primary-secondary DRBD, re-exported with iscsi or aoe >> > or whatever. >> > >> > Cheers, >> > >> > Denis Cardon >> > >> >> >> _______________________________________________ >> xen-api mailing list >> xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > > > > > This body part will be downloaded on demand. -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 06 20:57:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 20:57:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S51Re-0001ms-RA; Tue, 06 Mar 2012 20:57:18 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S51Rc-0001mn-WF for xen-api@lists.xen.org; Tue, 06 Mar 2012 20:57:17 +0000 Received: from [85.158.139.83:59565] by server-5.bemta-5.messagelabs.com id 45/0F-13566-C2A765F4; Tue, 06 Mar 2012 20:57:16 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1331067435!18153716!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30024 invoked from network); 6 Mar 2012 20:57:15 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Mar 2012 20:57:15 -0000 Received: by bkcjg9 with SMTP id jg9so5687781bkc.32 for ; Tue, 06 Mar 2012 12:57:14 -0800 (PST) Received-SPF: pass (google.com: domain of george.shuklin@gmail.com designates 10.204.157.138 as permitted sender) client-ip=10.204.157.138; Authentication-Results: mr.google.com; spf=pass (google.com: domain of george.shuklin@gmail.com designates 10.204.157.138 as permitted sender) smtp.mail=george.shuklin@gmail.com; dkim=pass header.i=george.shuklin@gmail.com Received: from mr.google.com ([10.204.157.138]) by 10.204.157.138 with SMTP id b10mr13578871bkx.75.1331067434829 (num_hops = 1); Tue, 06 Mar 2012 12:57:14 -0800 (PST) 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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xXN9pvNb2SiEdkRQL73txVpELXMfu8EZWetI9A3kHEk=; b=UnIw+MdyUc11aXCg81OkSfXCQSXxklquKL9ow6yTUEyQIOmuPZbW8Y0u6in7/ohSgz RG0Uy4C7TSwQCBFW1pOqfyAzqvRvcj4O9kZdgEDI20y5PCQMwW5PaoTrPzt1TXvR0vGQ 1Nm3EdglhAF0oeSZ8uHFXl5hPJa+w7b33Oy9eEoDUO9AG80MsYXfrgIJ5wVg9pfefQhM UxlA20/fS/0tGsZhZH0nVnP/9rtrbV3pWlXnbe5FG99O/whjwhebhT8w85Ytw30KODpl jsuWYBDnHI5gRFv/BuEpuvXD7fr73VZvkaJ4yzvu6Tbk82/9qNAUG0Dc3KW1w6Dwpn96 IAIQ== Received: by 10.204.157.138 with SMTP id b10mr10582946bkx.75.1331067434672; Tue, 06 Mar 2012 12:57:14 -0800 (PST) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id jj1sm1473372bkb.13.2012.03.06.12.57.12 (version=SSLv3 cipher=OTHER); Tue, 06 Mar 2012 12:57:13 -0800 (PST) Message-ID: <4F567A4E.2080109@gmail.com> Date: Wed, 07 Mar 2012 00:57:50 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: Denis Cardon References: <4F55DD20.3090507@tranquil-it-systems.fr> <4F55E563.1020402@gmail.com> <4F566250.30805@tranquil-it-systems.fr> In-Reply-To: <4F566250.30805@tranquil-it-systems.fr> Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Well, We've choose iscsi fiiling to make it 'shareable' (I means allows XCP to think it shared). Are you using XCP or just xen (xend)? How you made storage manager to think about /dev/drbd as shared storage? On 06.03.2012 23:15, Denis Cardon wrote: > Hi Georges, > >> We've tried that for internal laboratory. Problem: sometime drbd do >> additional IO and making storage out of sync. We've spend few weeks on >> this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), >> but it getting unstable after some time, so we gave up. > > Actually I have not encountered instability in my test setup (the SR > was define directly over /dev/drbd0, no iscsi in between). During the > test, I was running iozone in a loop in VMs that were switch from host > every few minutes in a loop (linux and windows VMs) for a whole 48 hours. > > I have'nt encountered any issues during that stress test (set aside > the global warming). But when I went ahead with disaster recovery > scenario, it was a no go : severing the primary-primary drbd link left > me with a brain split to solve by hand. > > I was thinking to use the more conservative approach with the > following scenario. It adds the iscsi latency to the io path, but : > > XCP1 in xenpool XCP2 in xenpool > ================== ==================== > drbd-sr1 (primary) <-----> drbd-sr1 (secondary) > exported to xenpool > through iscsi target > > drbd-sr2 (secondary) <-----> drbd-sr2 (primary) > exported to xenpool > through iscsi target > > I have a few year of practice of drbd with primary/secondary setup on > iscsi san, and I am pretty confident the data should be safe with this > kind of setup, but I'm wondering of the behavior of a dom0 xen in this > situation. > > I'll give it a shot in the next few days. > > Thanks for your input. > > Denis > > > > > >> >> >> >> On 06.03.2012 13:47, Denis Cardon wrote: >>> Hello everyone, >>> >>> I wanted to know if any of you had some experience with building a >>> redundant xcp/xenserver cluster based on drbd. In this setup I would >>> like to avoid a separate iscsi SAN, and have replicated local storage. >>> >>> There are docs on the internet showing how to set up a dual primary >>> drbd SR on xenserver/xcp. It works fine with live migration and all, >>> but when trying disaster scenario, like severing the drbd replication >>> link, one gets a split brain scenario that cannot be unsolved. It >>> should be doable if xapi had a smart understanding of drbd, but >>> currently it is just a SR like others. So it is a no-go for the time >>> being. >>> >>> I also tried a drbd primary-secondary scenario, with re-export with >>> iet iscsi target, but for the moment I have unresolved performance >>> issues (will try also with scst target). >>> >>> So I wanted to know if any of you had any experience or hints with >>> this kind of setup : a dual active/active XCP servers with local SR >>> replicated with primary-secondary DRBD, re-exported with iscsi or aoe >>> or whatever. >>> >>> Cheers, >>> >>> Denis Cardon >>> >> >> >> _______________________________________________ >> 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 Tue Mar 06 20:57:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 20:57:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S51Re-0001ms-RA; Tue, 06 Mar 2012 20:57:18 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S51Rc-0001mn-WF for xen-api@lists.xen.org; Tue, 06 Mar 2012 20:57:17 +0000 Received: from [85.158.139.83:59565] by server-5.bemta-5.messagelabs.com id 45/0F-13566-C2A765F4; Tue, 06 Mar 2012 20:57:16 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-12.tower-182.messagelabs.com!1331067435!18153716!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30024 invoked from network); 6 Mar 2012 20:57:15 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-12.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 6 Mar 2012 20:57:15 -0000 Received: by bkcjg9 with SMTP id jg9so5687781bkc.32 for ; Tue, 06 Mar 2012 12:57:14 -0800 (PST) Received-SPF: pass (google.com: domain of george.shuklin@gmail.com designates 10.204.157.138 as permitted sender) client-ip=10.204.157.138; Authentication-Results: mr.google.com; spf=pass (google.com: domain of george.shuklin@gmail.com designates 10.204.157.138 as permitted sender) smtp.mail=george.shuklin@gmail.com; dkim=pass header.i=george.shuklin@gmail.com Received: from mr.google.com ([10.204.157.138]) by 10.204.157.138 with SMTP id b10mr13578871bkx.75.1331067434829 (num_hops = 1); Tue, 06 Mar 2012 12:57:14 -0800 (PST) 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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xXN9pvNb2SiEdkRQL73txVpELXMfu8EZWetI9A3kHEk=; b=UnIw+MdyUc11aXCg81OkSfXCQSXxklquKL9ow6yTUEyQIOmuPZbW8Y0u6in7/ohSgz RG0Uy4C7TSwQCBFW1pOqfyAzqvRvcj4O9kZdgEDI20y5PCQMwW5PaoTrPzt1TXvR0vGQ 1Nm3EdglhAF0oeSZ8uHFXl5hPJa+w7b33Oy9eEoDUO9AG80MsYXfrgIJ5wVg9pfefQhM UxlA20/fS/0tGsZhZH0nVnP/9rtrbV3pWlXnbe5FG99O/whjwhebhT8w85Ytw30KODpl jsuWYBDnHI5gRFv/BuEpuvXD7fr73VZvkaJ4yzvu6Tbk82/9qNAUG0Dc3KW1w6Dwpn96 IAIQ== Received: by 10.204.157.138 with SMTP id b10mr10582946bkx.75.1331067434672; Tue, 06 Mar 2012 12:57:14 -0800 (PST) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id jj1sm1473372bkb.13.2012.03.06.12.57.12 (version=SSLv3 cipher=OTHER); Tue, 06 Mar 2012 12:57:13 -0800 (PST) Message-ID: <4F567A4E.2080109@gmail.com> Date: Wed, 07 Mar 2012 00:57:50 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: Denis Cardon References: <4F55DD20.3090507@tranquil-it-systems.fr> <4F55E563.1020402@gmail.com> <4F566250.30805@tranquil-it-systems.fr> In-Reply-To: <4F566250.30805@tranquil-it-systems.fr> Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] redundant xcp server with drbd X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Well, We've choose iscsi fiiling to make it 'shareable' (I means allows XCP to think it shared). Are you using XCP or just xen (xend)? How you made storage manager to think about /dev/drbd as shared storage? On 06.03.2012 23:15, Denis Cardon wrote: > Hi Georges, > >> We've tried that for internal laboratory. Problem: sometime drbd do >> additional IO and making storage out of sync. We've spend few weeks on >> this set up (primary/primary drbd, and iscsi export with LVMoISCSI SR), >> but it getting unstable after some time, so we gave up. > > Actually I have not encountered instability in my test setup (the SR > was define directly over /dev/drbd0, no iscsi in between). During the > test, I was running iozone in a loop in VMs that were switch from host > every few minutes in a loop (linux and windows VMs) for a whole 48 hours. > > I have'nt encountered any issues during that stress test (set aside > the global warming). But when I went ahead with disaster recovery > scenario, it was a no go : severing the primary-primary drbd link left > me with a brain split to solve by hand. > > I was thinking to use the more conservative approach with the > following scenario. It adds the iscsi latency to the io path, but : > > XCP1 in xenpool XCP2 in xenpool > ================== ==================== > drbd-sr1 (primary) <-----> drbd-sr1 (secondary) > exported to xenpool > through iscsi target > > drbd-sr2 (secondary) <-----> drbd-sr2 (primary) > exported to xenpool > through iscsi target > > I have a few year of practice of drbd with primary/secondary setup on > iscsi san, and I am pretty confident the data should be safe with this > kind of setup, but I'm wondering of the behavior of a dom0 xen in this > situation. > > I'll give it a shot in the next few days. > > Thanks for your input. > > Denis > > > > > >> >> >> >> On 06.03.2012 13:47, Denis Cardon wrote: >>> Hello everyone, >>> >>> I wanted to know if any of you had some experience with building a >>> redundant xcp/xenserver cluster based on drbd. In this setup I would >>> like to avoid a separate iscsi SAN, and have replicated local storage. >>> >>> There are docs on the internet showing how to set up a dual primary >>> drbd SR on xenserver/xcp. It works fine with live migration and all, >>> but when trying disaster scenario, like severing the drbd replication >>> link, one gets a split brain scenario that cannot be unsolved. It >>> should be doable if xapi had a smart understanding of drbd, but >>> currently it is just a SR like others. So it is a no-go for the time >>> being. >>> >>> I also tried a drbd primary-secondary scenario, with re-export with >>> iet iscsi target, but for the moment I have unresolved performance >>> issues (will try also with scst target). >>> >>> So I wanted to know if any of you had any experience or hints with >>> this kind of setup : a dual active/active XCP servers with local SR >>> replicated with primary-secondary DRBD, re-exported with iscsi or aoe >>> or whatever. >>> >>> Cheers, >>> >>> Denis Cardon >>> >> >> >> _______________________________________________ >> 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 Tue Mar 06 23:07:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 23:07:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S53T4-0003dt-ND; Tue, 06 Mar 2012 23:06:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S53T3-0003do-Eg for xen-api@lists.xen.org; Tue, 06 Mar 2012 23:06:53 +0000 Received: from [85.158.143.35:16189] by server-1.bemta-4.messagelabs.com id 4D/16-20925-C88965F4; Tue, 06 Mar 2012 23:06:52 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-2.tower-21.messagelabs.com!1331075212!3824173!1 X-Originating-IP: [80.12.242.124] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18872 invoked from network); 6 Mar 2012 23:06:52 -0000 Received: from smtp02.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.124) by server-2.tower-21.messagelabs.com with SMTP; 6 Mar 2012 23:06:52 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d49 with ME id iP6r1i00B3zjds103P6rWF; Wed, 07 Mar 2012 00:06:51 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 3AD6A7450C for ; Wed, 7 Mar 2012 00:06:51 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lHD8SWUYOHyA for ; Wed, 7 Mar 2012 00:06:50 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 07F8C74002 for ; Wed, 7 Mar 2012 00:06:50 +0100 (CET) Message-ID: <4F569889.7080805@tranquil-it-systems.fr> Date: Wed, 07 Mar 2012 00:06:49 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] xe vm-export and stunnel on xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everyone, recently I have been looking into off-site/off-line export of VMs on = external drive. Using xe vm-export is ok when exporting directly from = pool master on an external usb drive. But I prefer not to play with dom0 = if I can. And when one export a xva of a VM over a network, it is kind of slow and = cpu hungry, I guess primarily because of the stunnel. When working on a safe subnet, would it be possible to vm-export without = the overhead of the stunnel in order to have at least a 40MBps = throughput? How do you all do your exports? Have you found a way to get = decent speed? cheers, Denis -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 06 23:07:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 06 Mar 2012 23:07:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S53T4-0003dt-ND; Tue, 06 Mar 2012 23:06:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S53T3-0003do-Eg for xen-api@lists.xen.org; Tue, 06 Mar 2012 23:06:53 +0000 Received: from [85.158.143.35:16189] by server-1.bemta-4.messagelabs.com id 4D/16-20925-C88965F4; Tue, 06 Mar 2012 23:06:52 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-2.tower-21.messagelabs.com!1331075212!3824173!1 X-Originating-IP: [80.12.242.124] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18872 invoked from network); 6 Mar 2012 23:06:52 -0000 Received: from smtp02.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.124) by server-2.tower-21.messagelabs.com with SMTP; 6 Mar 2012 23:06:52 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d49 with ME id iP6r1i00B3zjds103P6rWF; Wed, 07 Mar 2012 00:06:51 +0100 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 3AD6A7450C for ; Wed, 7 Mar 2012 00:06:51 +0100 (CET) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lHD8SWUYOHyA for ; Wed, 7 Mar 2012 00:06:50 +0100 (CET) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 07F8C74002 for ; Wed, 7 Mar 2012 00:06:50 +0100 (CET) Message-ID: <4F569889.7080805@tranquil-it-systems.fr> Date: Wed, 07 Mar 2012 00:06:49 +0100 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] xe vm-export and stunnel on xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi everyone, recently I have been looking into off-site/off-line export of VMs on = external drive. Using xe vm-export is ok when exporting directly from = pool master on an external usb drive. But I prefer not to play with dom0 = if I can. And when one export a xva of a VM over a network, it is kind of slow and = cpu hungry, I guess primarily because of the stunnel. When working on a safe subnet, would it be possible to vm-export without = the overhead of the stunnel in order to have at least a 40MBps = throughput? How do you all do your exports? Have you found a way to get = decent speed? cheers, Denis -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 07 11:22:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 07 Mar 2012 11:22:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S5Ewv-0001rp-OS; Wed, 07 Mar 2012 11:22:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S5Ewu-0001rk-Lr for xen-api@lists.xen.org; Wed, 07 Mar 2012 11:22:28 +0000 Received: from [85.158.143.99:15478] by server-1.bemta-4.messagelabs.com id A1/FD-20925-3F4475F4; Wed, 07 Mar 2012 11:22:27 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1331119347!18067859!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4NzU1Mg==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5703 invoked from network); 7 Mar 2012 11:22:27 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 7 Mar 2012 11:22:27 -0000 X-IronPort-AV: E=Sophos;i="4.73,545,1325462400"; d="scan'208";a="11139736" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Mar 2012 11:22:27 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Wed, 7 Mar 2012 11:22:27 +0000 From: Dave Scott To: 'Denis Cardon' , "xen-api@lists.xen.org" Date: Wed, 7 Mar 2012 11:22:25 +0000 Thread-Topic: [Xen-API] xe vm-export and stunnel on xcp Thread-Index: Acz77g/+a5ScG1t4Q3+yow4a4Zy2kAAZmFWQ Message-ID: <81A73678E76EA642801C8F2E4823AD21D7724CF9F1@LONPMAILBOX01.citrite.net> References: <4F569889.7080805@tranquil-it-systems.fr> In-Reply-To: <4F569889.7080805@tranquil-it-systems.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] xe vm-export and stunnel on xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, > Hi everyone, > > recently I have been looking into off-site/off-line export of VMs on > external drive. Using xe vm-export is ok when exporting directly from > pool master on an external usb drive. But I prefer not to play with > dom0 > if I can. > > And when one export a xva of a VM over a network, it is kind of slow > and > cpu hungry, I guess primarily because of the stunnel. > > When working on a safe subnet, would it be possible to vm-export > without > the overhead of the stunnel in order to have at least a 40MBps > throughput? How do you all do your exports? Have you found a way to get > decent speed? Try $ xe -s -u root -pw -p 80 vm-export vm= filename= --nossl This should use raw HTTP over port 80. Cheers, Dave _______________________________________________ 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 07 11:22:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 07 Mar 2012 11:22:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S5Ewv-0001rp-OS; Wed, 07 Mar 2012 11:22:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S5Ewu-0001rk-Lr for xen-api@lists.xen.org; Wed, 07 Mar 2012 11:22:28 +0000 Received: from [85.158.143.99:15478] by server-1.bemta-4.messagelabs.com id A1/FD-20925-3F4475F4; Wed, 07 Mar 2012 11:22:27 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1331119347!18067859!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4NzU1Mg==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5703 invoked from network); 7 Mar 2012 11:22:27 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 7 Mar 2012 11:22:27 -0000 X-IronPort-AV: E=Sophos;i="4.73,545,1325462400"; d="scan'208";a="11139736" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Mar 2012 11:22:27 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Wed, 7 Mar 2012 11:22:27 +0000 From: Dave Scott To: 'Denis Cardon' , "xen-api@lists.xen.org" Date: Wed, 7 Mar 2012 11:22:25 +0000 Thread-Topic: [Xen-API] xe vm-export and stunnel on xcp Thread-Index: Acz77g/+a5ScG1t4Q3+yow4a4Zy2kAAZmFWQ Message-ID: <81A73678E76EA642801C8F2E4823AD21D7724CF9F1@LONPMAILBOX01.citrite.net> References: <4F569889.7080805@tranquil-it-systems.fr> In-Reply-To: <4F569889.7080805@tranquil-it-systems.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] xe vm-export and stunnel on xcp X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, > Hi everyone, > > recently I have been looking into off-site/off-line export of VMs on > external drive. Using xe vm-export is ok when exporting directly from > pool master on an external usb drive. But I prefer not to play with > dom0 > if I can. > > And when one export a xva of a VM over a network, it is kind of slow > and > cpu hungry, I guess primarily because of the stunnel. > > When working on a safe subnet, would it be possible to vm-export > without > the overhead of the stunnel in order to have at least a 40MBps > throughput? How do you all do your exports? Have you found a way to get > decent speed? Try $ xe -s -u root -pw -p 80 vm-export vm= filename= --nossl This should use raw HTTP over port 80. Cheers, Dave _______________________________________________ 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 12 17:04:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 12 Mar 2012 17:04:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S78fT-0002M8-Qe; Mon, 12 Mar 2012 17:04:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S78fS-0002Lw-Bh for xen-api@lists.xen.org; Mon, 12 Mar 2012 17:04:18 +0000 Received: from [85.158.143.99:58692] by server-1.bemta-4.messagelabs.com id E7/D8-20925-19C2E5F4; Mon, 12 Mar 2012 17:04:17 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1331571853!13578616!1 X-Originating-IP: [148.87.113.117] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQ4Ljg3LjExMy4xMTcgPT4gNTkxOTI5\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31789 invoked from network); 12 Mar 2012 17:04:14 -0000 Received: from rcsinet15.oracle.com (HELO rcsinet15.oracle.com) (148.87.113.117) by server-12.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Mar 2012 17:04:14 -0000 Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q2CH49w0014646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Mar 2012 17:04:10 GMT Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q2CH48TH014917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Mar 2012 17:04:09 GMT Received: from abhmt102.oracle.com (abhmt102.oracle.com [141.146.116.54]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q2CH48vN016730; Mon, 12 Mar 2012 12:04:08 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 12 Mar 2012 10:04:08 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 6AB9240287; Mon, 12 Mar 2012 13:00:12 -0400 (EDT) Date: Mon, 12 Mar 2012 13:00:12 -0400 From: Konrad Rzeszutek Wilk To: Ian Campbell Message-ID: <20120312170012.GI5369@phenom.dumpdata.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1330534437.4270.143.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: acsinet21.oracle.com [141.146.126.237] X-CT-RefId: str=0001.0A090202.4F5E2C8B.003F,ss=1,re=0.000,fgs=0 Cc: xen-devel , xen-api@lists.xen.org Subject: Re: [Xen-API] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Wed, Feb 29, 2012 at 04:53:57PM +0000, Ian Campbell wrote: > Below are a few ideas which have been floating around as potential > projects (or broad subject areas for projects) for GSoC this year. > > If you want any more information on any particular item then please ask. > Likewise if you have any ideas of your own please feel free to chip in. > > If you think you might be interested in a project, either as mentor or > potential student, then please add it to the wiki page at > http://wiki.xen.org/wiki/GSoC_2012_Ideas > > Ian. > > TOOLS > ----- > - pv grub2 > - xapi support in libvirt > - make xapi use libxl > - compile xapi on ARM > - OpenXenManager > - driver domains > - PV dbus > - HA daemon for Remus > - HA daemon for XCP > > PERF > ---- > - Oprofile So the oprofile mega patch posted by Michale seems to work. But it is riddled with #ifdef CONFIG_XEN so not very nice. > - Linux perf tools in guest from this e-mail thread: https://lkml.org/lkml/2012/2/12/74 it actually seems to work in dom0 - well, there is a bug so not exactly good. But having the tool to work with dom0 and domU would be super. Sign me up as a mentor for that! > > HYPERVISOR > ---------- > - insmod Xen > - event channel limits > - NUMA Yeah, we need that. I think there were some patches posted for that.. whatever happend to them? > > MEMORY > ------ > - disk based memory sharing > - memory scanner > - paging replacing PoD > - VM Fork > - Copy on read (past VDI boot) > > > IO > -- > - PV OpenGL/Gallium > - PV USB > - PV USB3 > - PV SCSI > - PVFB in Xorg > - Infiniband Huh? InfiniBand PV drivers? > > > STORAGE > ------- > - gluster/ceph plugins > > > QEMU > ---- > - BSD libc > - upstream QEMU stubdoms > > > TESTS > ----- > - better web reporting > - more tests > - upstream linux > > > DISTROS > ------- > - packaging stubdoms > - xen on centos6 > - driver domains > - figure out the VM format issue > - XSM in distros > > > > _______________________________________________ > 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 12 17:04:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 12 Mar 2012 17:04:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S78fT-0002M8-Qe; Mon, 12 Mar 2012 17:04:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S78fS-0002Lw-Bh for xen-api@lists.xen.org; Mon, 12 Mar 2012 17:04:18 +0000 Received: from [85.158.143.99:58692] by server-1.bemta-4.messagelabs.com id E7/D8-20925-19C2E5F4; Mon, 12 Mar 2012 17:04:17 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1331571853!13578616!1 X-Originating-IP: [148.87.113.117] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQ4Ljg3LjExMy4xMTcgPT4gNTkxOTI5\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31789 invoked from network); 12 Mar 2012 17:04:14 -0000 Received: from rcsinet15.oracle.com (HELO rcsinet15.oracle.com) (148.87.113.117) by server-12.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Mar 2012 17:04:14 -0000 Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q2CH49w0014646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Mar 2012 17:04:10 GMT Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q2CH48TH014917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Mar 2012 17:04:09 GMT Received: from abhmt102.oracle.com (abhmt102.oracle.com [141.146.116.54]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q2CH48vN016730; Mon, 12 Mar 2012 12:04:08 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 12 Mar 2012 10:04:08 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 6AB9240287; Mon, 12 Mar 2012 13:00:12 -0400 (EDT) Date: Mon, 12 Mar 2012 13:00:12 -0400 From: Konrad Rzeszutek Wilk To: Ian Campbell Message-ID: <20120312170012.GI5369@phenom.dumpdata.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1330534437.4270.143.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: acsinet21.oracle.com [141.146.126.237] X-CT-RefId: str=0001.0A090202.4F5E2C8B.003F,ss=1,re=0.000,fgs=0 Cc: xen-devel , xen-api@lists.xen.org Subject: Re: [Xen-API] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Wed, Feb 29, 2012 at 04:53:57PM +0000, Ian Campbell wrote: > Below are a few ideas which have been floating around as potential > projects (or broad subject areas for projects) for GSoC this year. > > If you want any more information on any particular item then please ask. > Likewise if you have any ideas of your own please feel free to chip in. > > If you think you might be interested in a project, either as mentor or > potential student, then please add it to the wiki page at > http://wiki.xen.org/wiki/GSoC_2012_Ideas > > Ian. > > TOOLS > ----- > - pv grub2 > - xapi support in libvirt > - make xapi use libxl > - compile xapi on ARM > - OpenXenManager > - driver domains > - PV dbus > - HA daemon for Remus > - HA daemon for XCP > > PERF > ---- > - Oprofile So the oprofile mega patch posted by Michale seems to work. But it is riddled with #ifdef CONFIG_XEN so not very nice. > - Linux perf tools in guest from this e-mail thread: https://lkml.org/lkml/2012/2/12/74 it actually seems to work in dom0 - well, there is a bug so not exactly good. But having the tool to work with dom0 and domU would be super. Sign me up as a mentor for that! > > HYPERVISOR > ---------- > - insmod Xen > - event channel limits > - NUMA Yeah, we need that. I think there were some patches posted for that.. whatever happend to them? > > MEMORY > ------ > - disk based memory sharing > - memory scanner > - paging replacing PoD > - VM Fork > - Copy on read (past VDI boot) > > > IO > -- > - PV OpenGL/Gallium > - PV USB > - PV USB3 > - PV SCSI > - PVFB in Xorg > - Infiniband Huh? InfiniBand PV drivers? > > > STORAGE > ------- > - gluster/ceph plugins > > > QEMU > ---- > - BSD libc > - upstream QEMU stubdoms > > > TESTS > ----- > - better web reporting > - more tests > - upstream linux > > > DISTROS > ------- > - packaging stubdoms > - xen on centos6 > - driver domains > - figure out the VM format issue > - XSM in distros > > > > _______________________________________________ > 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 12 17:25:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 12 Mar 2012 17:25:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7905-00038Z-L8; Mon, 12 Mar 2012 17:25:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7903-00038C-Ps for xen-api@lists.xen.org; Mon, 12 Mar 2012 17:25:36 +0000 Received: from [85.158.138.51:49759] by server-5.bemta-3.messagelabs.com id E8/71-09139-E813E5F4; Mon, 12 Mar 2012 17:25:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1331573133!17310253!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODAwMA==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12965 invoked from network); 12 Mar 2012 17:25:34 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Mar 2012 17:25:34 -0000 X-IronPort-AV: E=Sophos;i="4.73,572,1325462400"; d="scan'208";a="11243425" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Mar 2012 17:25:33 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Mon, 12 Mar 2012 17:25:33 +0000 Message-ID: <1331573131.23971.165.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Konrad Rzeszutek Wilk Date: Mon, 12 Mar 2012 17:25:31 +0000 In-Reply-To: <20120312170012.GI5369@phenom.dumpdata.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <20120312170012.GI5369@phenom.dumpdata.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Mon, 2012-03-12 at 17:00 +0000, Konrad Rzeszutek Wilk wrote: > On Wed, Feb 29, 2012 at 04:53:57PM +0000, Ian Campbell wrote: > > Below are a few ideas which have been floating around as potential > > projects (or broad subject areas for projects) for GSoC this year. > > > > If you want any more information on any particular item then please ask. > > Likewise if you have any ideas of your own please feel free to chip in. > > > > If you think you might be interested in a project, either as mentor or > > potential student, then please add it to the wiki page at > > http://wiki.xen.org/wiki/GSoC_2012_Ideas > > > > Ian. > > > > TOOLS > > ----- > > - pv grub2 > > - xapi support in libvirt > > - make xapi use libxl > > - compile xapi on ARM > > - OpenXenManager > > - driver domains > > - PV dbus > > - HA daemon for Remus > > - HA daemon for XCP > > > > PERF > > ---- > > - Oprofile > > So the oprofile mega patch posted by Michale seems to work. But it is > riddled with #ifdef CONFIG_XEN so not very nice. > > > - Linux perf tools in guest > > from this e-mail thread: > > https://lkml.org/lkml/2012/2/12/74 > > it actually seems to work in dom0 - well, there is a bug so not exactly good. > > But having the tool to work with dom0 and domU would be super. > > Sign me up as a mentor for that! Please update http://wiki.xen.org/wiki/GSoC_2012_Ideas as appropriate ;-) > > > > HYPERVISOR > > ---------- > > - insmod Xen > > - event channel limits > > - NUMA > > Yeah, we need that. I think there were some patches posted for that.. whatever > happend to them? I think there are some patches, which have gone in and various ideas for ongoing work but I'm not sure what the details were -- hopefully whoever shouted out NUMA (this was a brainstorm remember ;-)) will chime in. > > > > - Infiniband > > Huh? InfiniBand PV drivers? I think this is about using Infiniband for extra fast migration, by pumping the migration data over infiniband instead of a normal network. But again hopefully someone who knows what that bullet was will chime in. I seem to remember someone mentioning it at the Munich hackathon. Ian. _______________________________________________ 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 12 17:25:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 12 Mar 2012 17:25:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7905-00038Z-L8; Mon, 12 Mar 2012 17:25:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7903-00038C-Ps for xen-api@lists.xen.org; Mon, 12 Mar 2012 17:25:36 +0000 Received: from [85.158.138.51:49759] by server-5.bemta-3.messagelabs.com id E8/71-09139-E813E5F4; Mon, 12 Mar 2012 17:25:34 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1331573133!17310253!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODAwMA==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12965 invoked from network); 12 Mar 2012 17:25:34 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-10.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 12 Mar 2012 17:25:34 -0000 X-IronPort-AV: E=Sophos;i="4.73,572,1325462400"; d="scan'208";a="11243425" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 12 Mar 2012 17:25:33 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Mon, 12 Mar 2012 17:25:33 +0000 Message-ID: <1331573131.23971.165.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Konrad Rzeszutek Wilk Date: Mon, 12 Mar 2012 17:25:31 +0000 In-Reply-To: <20120312170012.GI5369@phenom.dumpdata.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <20120312170012.GI5369@phenom.dumpdata.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Mon, 2012-03-12 at 17:00 +0000, Konrad Rzeszutek Wilk wrote: > On Wed, Feb 29, 2012 at 04:53:57PM +0000, Ian Campbell wrote: > > Below are a few ideas which have been floating around as potential > > projects (or broad subject areas for projects) for GSoC this year. > > > > If you want any more information on any particular item then please ask. > > Likewise if you have any ideas of your own please feel free to chip in. > > > > If you think you might be interested in a project, either as mentor or > > potential student, then please add it to the wiki page at > > http://wiki.xen.org/wiki/GSoC_2012_Ideas > > > > Ian. > > > > TOOLS > > ----- > > - pv grub2 > > - xapi support in libvirt > > - make xapi use libxl > > - compile xapi on ARM > > - OpenXenManager > > - driver domains > > - PV dbus > > - HA daemon for Remus > > - HA daemon for XCP > > > > PERF > > ---- > > - Oprofile > > So the oprofile mega patch posted by Michale seems to work. But it is > riddled with #ifdef CONFIG_XEN so not very nice. > > > - Linux perf tools in guest > > from this e-mail thread: > > https://lkml.org/lkml/2012/2/12/74 > > it actually seems to work in dom0 - well, there is a bug so not exactly good. > > But having the tool to work with dom0 and domU would be super. > > Sign me up as a mentor for that! Please update http://wiki.xen.org/wiki/GSoC_2012_Ideas as appropriate ;-) > > > > HYPERVISOR > > ---------- > > - insmod Xen > > - event channel limits > > - NUMA > > Yeah, we need that. I think there were some patches posted for that.. whatever > happend to them? I think there are some patches, which have gone in and various ideas for ongoing work but I'm not sure what the details were -- hopefully whoever shouted out NUMA (this was a brainstorm remember ;-)) will chime in. > > > > - Infiniband > > Huh? InfiniBand PV drivers? I think this is about using Infiniband for extra fast migration, by pumping the migration data over infiniband instead of a normal network. But again hopefully someone who knows what that bullet was will chime in. I seem to remember someone mentioning it at the Munich hackathon. Ian. _______________________________________________ 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 13 10:30:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 13 Mar 2012 10:30: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 1S7OzO-0006RZ-Ag; Tue, 13 Mar 2012 10:29:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7OzM-0006RU-U9 for xen-api@lists.xen.org; Tue, 13 Mar 2012 10:29:57 +0000 Received: from [85.158.139.83:59355] by server-11.bemta-5.messagelabs.com id 0C/04-12959-4A12F5F4; Tue, 13 Mar 2012 10:29:56 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1331634595!16418553!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODM2Nw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5857 invoked from network); 13 Mar 2012 10:29:55 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 10:29:55 -0000 X-IronPort-AV: E=Sophos;i="4.73,576,1325462400"; d="scan'208";a="11256601" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Mar 2012 10:29:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Tue, 13 Mar 2012 10:29:55 +0000 From: John Garbutt To: 'Thomas Goirand' , Renuka Apte Date: Tue, 13 Mar 2012 10:29:54 +0000 Thread-Topic: [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos Thread-Index: Ac0A+yrAqISBIwAkRSyC/qi8J1hGGgABfkDg Message-ID: References: <4F5F10AA.1040206@goirand.fr> In-Reply-To: <4F5F10AA.1040206@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > On Behalf Of Thomas Goirand > which installs the above in the correct folders (which are *NOT* the same as > for CentOS). I'd love to have a bit of help from Citrix to test all this by the way. I hear you, and want to help out :-) I hope we can setup some Jenkins tests on various XenServer/XCP/Kronos flavors, public and running against trunk, in the near future. We have the beginnings of a devstack + XenServer one here (it kinda works in our lab, I want to simplyify it and get it using more scripts in DevStack trunk): https://github.com/citrix-openstack/qa/blob/everett/jenkins/run-devstack.sh Cheers, John _______________________________________________ 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 13 10:30:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 13 Mar 2012 10:30: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 1S7OzO-0006RZ-Ag; Tue, 13 Mar 2012 10:29:58 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7OzM-0006RU-U9 for xen-api@lists.xen.org; Tue, 13 Mar 2012 10:29:57 +0000 Received: from [85.158.139.83:59355] by server-11.bemta-5.messagelabs.com id 0C/04-12959-4A12F5F4; Tue, 13 Mar 2012 10:29:56 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1331634595!16418553!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODM2Nw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5857 invoked from network); 13 Mar 2012 10:29:55 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 10:29:55 -0000 X-IronPort-AV: E=Sophos;i="4.73,576,1325462400"; d="scan'208";a="11256601" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Mar 2012 10:29:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Tue, 13 Mar 2012 10:29:55 +0000 From: John Garbutt To: 'Thomas Goirand' , Renuka Apte Date: Tue, 13 Mar 2012 10:29:54 +0000 Thread-Topic: [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos Thread-Index: Ac0A+yrAqISBIwAkRSyC/qi8J1hGGgABfkDg Message-ID: References: <4F5F10AA.1040206@goirand.fr> In-Reply-To: <4F5F10AA.1040206@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > On Behalf Of Thomas Goirand > which installs the above in the correct folders (which are *NOT* the same as > for CentOS). I'd love to have a bit of help from Citrix to test all this by the way. I hear you, and want to help out :-) I hope we can setup some Jenkins tests on various XenServer/XCP/Kronos flavors, public and running against trunk, in the near future. We have the beginnings of a devstack + XenServer one here (it kinda works in our lab, I want to simplyify it and get it using more scripts in DevStack trunk): https://github.com/citrix-openstack/qa/blob/everett/jenkins/run-devstack.sh Cheers, John _______________________________________________ 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 13 10:58:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 13 Mar 2012 10:58: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 1S7PQT-0007OM-8Y; Tue, 13 Mar 2012 10:57:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7PQS-0007OH-N7 for xen-api@lists.xen.org; Tue, 13 Mar 2012 10:57:56 +0000 Received: from [85.158.143.99:9302] by server-1.bemta-4.messagelabs.com id 76/7E-20925-4382F5F4; Tue, 13 Mar 2012 10:57:56 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1331636275!20587312!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODM2Nw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13126 invoked from network); 13 Mar 2012 10:57:55 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 10:57:55 -0000 X-IronPort-AV: E=Sophos;i="4.73,576,1325462400"; d="scan'208";a="11257378" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Mar 2012 10:57:47 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Tue, 13 Mar 2012 10:57:47 +0000 From: John Garbutt To: 'Thomas Goirand' , Renuka Apte Date: Tue, 13 Mar 2012 10:57:47 +0000 Thread-Topic: [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos Thread-Index: Ac0A+yrAqISBIwAkRSyC/qi8J1hGGgADMcqg Message-ID: References: <4F5F10AA.1040206@goirand.fr> In-Reply-To: <4F5F10AA.1040206@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > I'm not using CentOS, but Debian (project Kronos). And in there, you just > need to do: > apt-get install nova-xcp-plugins nova-xcp-network > which installs the above in the correct folders (which are *NOT* the same as > for CentOS). I'd love to have a bit of help from Citrix to test all this by the way. Cool, that is the usual cause of that error out the way. First, looks like you have some dodgy configuration (worth looking at devstack to see some useful flag changes, the defaults only really work for KVM): 2012-03-13 05:41:31 WARNING nova.virt.libvirt.firewall [-] Libvirt module could not be loaded. NWFilterFirewall will not work correctly. A better choice is: firewall_driver="nova.virt.firewall.IptablesFirewallDriver" (or the Dom0 based one) But I doubt that is causing you a problem yet. Normally I would expect to see a stack trace telling me the error in the xcp-xapi log (presumably similar to /var/log/xensource.log on XenServer?): [20120313T05:41:31.468Z| info|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] spawning a new thread to handle the current task (trackid=bf1fbbc06724826b0912a76e2f8e75ff) [20120313T05:41:31.468Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|audit] Host.call_plugin host = 'ee61ea48-ad10-a478-3f7a-3bb9fd7df802 (node4407.gplhost.com)'; plugin = 'xenhost'; fn = 'host_data'; args = [ ] [20120313T05:41:31.478Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|xapi] Raised at forkhelpers.ml:181.30-76 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.478Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at xapi_plugins.ml:45.7-100 -> message_forwarding.ml:233.25-44 -> rbac.ml:229.16-23 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] Server_helpers.exec exception_handler: Got exception XENAPI_PLUGIN_FAILURE: [ non-zero exit; ; ] It is worth noting that the plugins were written for XenServer 5.6, which means they are written for python 2.4, but I don't think that is the problem here either. A few possible issues: * you might not have the execute permissions set on the xenhost plugin file? On XenServer that means it fails to register the plugin. * Does kronos have xe installed? And does the user running the compute service have access? The first line of code in the plugin that might fail is: _run_command("xe host-param-list uuid=%s" % host_uuid) Hope that helps, John _______________________________________________ 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 13 10:58:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 13 Mar 2012 10:58: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 1S7PQT-0007OM-8Y; Tue, 13 Mar 2012 10:57:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7PQS-0007OH-N7 for xen-api@lists.xen.org; Tue, 13 Mar 2012 10:57:56 +0000 Received: from [85.158.143.99:9302] by server-1.bemta-4.messagelabs.com id 76/7E-20925-4382F5F4; Tue, 13 Mar 2012 10:57:56 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-2.tower-216.messagelabs.com!1331636275!20587312!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODM2Nw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13126 invoked from network); 13 Mar 2012 10:57:55 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 10:57:55 -0000 X-IronPort-AV: E=Sophos;i="4.73,576,1325462400"; d="scan'208";a="11257378" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Mar 2012 10:57:47 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Tue, 13 Mar 2012 10:57:47 +0000 From: John Garbutt To: 'Thomas Goirand' , Renuka Apte Date: Tue, 13 Mar 2012 10:57:47 +0000 Thread-Topic: [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos Thread-Index: Ac0A+yrAqISBIwAkRSyC/qi8J1hGGgADMcqg Message-ID: References: <4F5F10AA.1040206@goirand.fr> In-Reply-To: <4F5F10AA.1040206@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > I'm not using CentOS, but Debian (project Kronos). And in there, you just > need to do: > apt-get install nova-xcp-plugins nova-xcp-network > which installs the above in the correct folders (which are *NOT* the same as > for CentOS). I'd love to have a bit of help from Citrix to test all this by the way. Cool, that is the usual cause of that error out the way. First, looks like you have some dodgy configuration (worth looking at devstack to see some useful flag changes, the defaults only really work for KVM): 2012-03-13 05:41:31 WARNING nova.virt.libvirt.firewall [-] Libvirt module could not be loaded. NWFilterFirewall will not work correctly. A better choice is: firewall_driver="nova.virt.firewall.IptablesFirewallDriver" (or the Dom0 based one) But I doubt that is causing you a problem yet. Normally I would expect to see a stack trace telling me the error in the xcp-xapi log (presumably similar to /var/log/xensource.log on XenServer?): [20120313T05:41:31.468Z| info|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] spawning a new thread to handle the current task (trackid=bf1fbbc06724826b0912a76e2f8e75ff) [20120313T05:41:31.468Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|audit] Host.call_plugin host = 'ee61ea48-ad10-a478-3f7a-3bb9fd7df802 (node4407.gplhost.com)'; plugin = 'xenhost'; fn = 'host_data'; args = [ ] [20120313T05:41:31.478Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|xapi] Raised at forkhelpers.ml:181.30-76 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.478Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at xapi_plugins.ml:45.7-100 -> message_forwarding.ml:233.25-44 -> rbac.ml:229.16-23 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] Server_helpers.exec exception_handler: Got exception XENAPI_PLUGIN_FAILURE: [ non-zero exit; ; ] It is worth noting that the plugins were written for XenServer 5.6, which means they are written for python 2.4, but I don't think that is the problem here either. A few possible issues: * you might not have the execute permissions set on the xenhost plugin file? On XenServer that means it fails to register the plugin. * Does kronos have xe installed? And does the user running the compute service have access? The first line of code in the plugin that might fail is: _run_command("xe host-param-list uuid=%s" % host_uuid) Hope that helps, John _______________________________________________ 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 13 17:09:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 13 Mar 2012 17:09:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7VDR-0007ki-FO; Tue, 13 Mar 2012 17:08:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7VDP-0007kE-Ny for xen-api@lists.xen.org; Tue, 13 Mar 2012 17:08:51 +0000 Received: from [193.109.254.147:60088] by server-5.bemta-14.messagelabs.com id 40/A7-01689-32F7F5F4; Tue, 13 Mar 2012 17:08:51 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1331658530!386852!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODM2Nw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12114 invoked from network); 13 Mar 2012 17:08:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 17:08:50 -0000 X-IronPort-AV: E=Sophos;i="4.73,577,1325462400"; d="scan'208";a="11270808" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Mar 2012 17:08:50 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Tue, 13 Mar 2012 17:08:50 +0000 Message-ID: <1331658528.23971.324.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "xen-devel@lists.xen.org" Date: Tue, 13 Mar 2012 17:08:48 +0000 In-Reply-To: <1331554278.23971.63.camel@zakaz.uk.xensource.com> References: <1331554278.23971.63.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: Jim Fehlig , xen-api@lists.xen.org, Bamvor Jian Zhang Subject: [Xen-API] libxl stable API (Re: [Xen-devel] 4.2 TODO update) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Mon, 2012-03-12 at 12:11 +0000, Ian Campbell wrote: > [...] > tools, blockers: > * libxl stable API -- we would like 4.2 to define a stable API > which downstream's can start to rely on not changing. Aspects of > this are: So now would be a good time for potential users of libxl in 4.2 onwards to do a quick sanity check of the interfaces such that any omissions can be added to the 4.2 list. Now is also a good time to decide on the policy and mechanisms which we will use to make life easy for our downstreams (some of whom I have CC'd). The goal and default assumption should obviously be that a downstream which builds against libxl from 4.2 will continue to build (and work!) against future versions of libxl without source modification. In order to help us achieve this we can define some interfaces / mechanisms now which will make everyone's lives easier in the future. I propose that downstreams who want to be exposed to a particular API should be required to #define LIBXL_API_VERSION before including libxl.h. This will allow libxl.h to introduce the necessary compat/shim layer. e.g. if they want the 4.2.0 interface they must: #define LIBXL_API_VERSION 0x040200 Assuming that 4.3.0 eventually releases with an identical API then users would be expected to continue to use 0x040200 (i.e. we wouldn't explicitly duplicate up the #ifdef's for compatible releases) but if in 4.4.0 changes are required then users could either continue to use 0x040200 (and expect libxl.h to provide suitable impedance matching to make that work) or switch to 0x040400 and make the necessary source level changes. Lack of LIBXL_API_VERSION would be taken to mean "the latest". Specifying an unknown LIBXL_API_VERSION would result in #error (e.g. in the above example 0x040300 and 0x123456 would both be an error). We should try especially hard to avoid changing the API during a stable series, i.e. it should be unusual for the last byte to be non-zero. If there is broad agreement with this scheme I will write up a patch to add it to some documentation / header somewhere. Do we need to define a horizon for how far we are willing to support this level of compatibility? A new major release seems like the obvious watershed -- i.e. at Xen 5.0.0 we may decide to drop support for LIBXL_API_VERSION 0x04xxxx and earlier (although we don't have to). Much as I hate to admit it I expect there will eventually/inevitably be changes which cannot be papered over with this scheme. In order to make it possible for downstreams to support the use of a single code base across such changes I suggest that we always add a #define LIBXL_HAVE_foo_interface for any such change. The assumption should be that the barrier for backporting to a stable branch will be very high for any change of this type. Lastly we also to decide what we want to do about ABI (as opposed to API) compatibility. Obviously if we change the ABI then we should change the SONAME, but is this something we want to commit to avoiding? i.e. should it be possible to build a downstream against libxl.so.2.0 (the current libxl soname) from 4.2 and expect that dropping in libxl.so.2.0 from 4.3 will Just Work against the new hypervisor interfaces? Or do we expect that 4.3 will provide libxl.so.2.1 and that the same downstream source can be built twice? (e.g. with the correct one selected via some plugin mechanism). Obviously avoiding ABI changes is a lot harder and I'm not sure if that is something we are able to commit to at this stage (and I'm not sure how good we would be at it even if we did try and make that commitment). > * add libxl_defbool and generally try and arrange that > memset(foo,0,...) requests the defaults (Ian Campbell, > DONE) > * Safe fork vs. fd handling hooks. This is an API > addition, so maybe not required fro stable API, bit need > to have for 4.2? (Ian J, patches posted) Ian. _______________________________________________ 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 13 17:09:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 13 Mar 2012 17:09:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7VDR-0007ki-FO; Tue, 13 Mar 2012 17:08:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7VDP-0007kE-Ny for xen-api@lists.xen.org; Tue, 13 Mar 2012 17:08:51 +0000 Received: from [193.109.254.147:60088] by server-5.bemta-14.messagelabs.com id 40/A7-01689-32F7F5F4; Tue, 13 Mar 2012 17:08:51 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1331658530!386852!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODM2Nw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12114 invoked from network); 13 Mar 2012 17:08:50 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 17:08:50 -0000 X-IronPort-AV: E=Sophos;i="4.73,577,1325462400"; d="scan'208";a="11270808" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Mar 2012 17:08:50 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Tue, 13 Mar 2012 17:08:50 +0000 Message-ID: <1331658528.23971.324.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "xen-devel@lists.xen.org" Date: Tue, 13 Mar 2012 17:08:48 +0000 In-Reply-To: <1331554278.23971.63.camel@zakaz.uk.xensource.com> References: <1331554278.23971.63.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: Jim Fehlig , xen-api@lists.xen.org, Bamvor Jian Zhang Subject: [Xen-API] libxl stable API (Re: [Xen-devel] 4.2 TODO update) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Mon, 2012-03-12 at 12:11 +0000, Ian Campbell wrote: > [...] > tools, blockers: > * libxl stable API -- we would like 4.2 to define a stable API > which downstream's can start to rely on not changing. Aspects of > this are: So now would be a good time for potential users of libxl in 4.2 onwards to do a quick sanity check of the interfaces such that any omissions can be added to the 4.2 list. Now is also a good time to decide on the policy and mechanisms which we will use to make life easy for our downstreams (some of whom I have CC'd). The goal and default assumption should obviously be that a downstream which builds against libxl from 4.2 will continue to build (and work!) against future versions of libxl without source modification. In order to help us achieve this we can define some interfaces / mechanisms now which will make everyone's lives easier in the future. I propose that downstreams who want to be exposed to a particular API should be required to #define LIBXL_API_VERSION before including libxl.h. This will allow libxl.h to introduce the necessary compat/shim layer. e.g. if they want the 4.2.0 interface they must: #define LIBXL_API_VERSION 0x040200 Assuming that 4.3.0 eventually releases with an identical API then users would be expected to continue to use 0x040200 (i.e. we wouldn't explicitly duplicate up the #ifdef's for compatible releases) but if in 4.4.0 changes are required then users could either continue to use 0x040200 (and expect libxl.h to provide suitable impedance matching to make that work) or switch to 0x040400 and make the necessary source level changes. Lack of LIBXL_API_VERSION would be taken to mean "the latest". Specifying an unknown LIBXL_API_VERSION would result in #error (e.g. in the above example 0x040300 and 0x123456 would both be an error). We should try especially hard to avoid changing the API during a stable series, i.e. it should be unusual for the last byte to be non-zero. If there is broad agreement with this scheme I will write up a patch to add it to some documentation / header somewhere. Do we need to define a horizon for how far we are willing to support this level of compatibility? A new major release seems like the obvious watershed -- i.e. at Xen 5.0.0 we may decide to drop support for LIBXL_API_VERSION 0x04xxxx and earlier (although we don't have to). Much as I hate to admit it I expect there will eventually/inevitably be changes which cannot be papered over with this scheme. In order to make it possible for downstreams to support the use of a single code base across such changes I suggest that we always add a #define LIBXL_HAVE_foo_interface for any such change. The assumption should be that the barrier for backporting to a stable branch will be very high for any change of this type. Lastly we also to decide what we want to do about ABI (as opposed to API) compatibility. Obviously if we change the ABI then we should change the SONAME, but is this something we want to commit to avoiding? i.e. should it be possible to build a downstream against libxl.so.2.0 (the current libxl soname) from 4.2 and expect that dropping in libxl.so.2.0 from 4.3 will Just Work against the new hypervisor interfaces? Or do we expect that 4.3 will provide libxl.so.2.1 and that the same downstream source can be built twice? (e.g. with the correct one selected via some plugin mechanism). Obviously avoiding ABI changes is a lot harder and I'm not sure if that is something we are able to commit to at this stage (and I'm not sure how good we would be at it even if we did try and make that commitment). > * add libxl_defbool and generally try and arrange that > memset(foo,0,...) requests the defaults (Ian Campbell, > DONE) > * Safe fork vs. fd handling hooks. This is an API > addition, so maybe not required fro stable API, bit need > to have for 4.2? (Ian J, patches posted) Ian. _______________________________________________ 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 14 11:16:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 11:16:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7mC5-0006XP-3P; Wed, 14 Mar 2012 11:16:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7mC4-0006WH-0g for xen-api@lists.xen.org; Wed, 14 Mar 2012 11:16:36 +0000 Received: from [193.109.254.147:33921] by server-1.bemta-14.messagelabs.com id 2B/63-12485-31E706F4; Wed, 14 Mar 2012 11:16:35 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1331723792!492319!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODc5Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26363 invoked from network); 14 Mar 2012 11:16:33 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Mar 2012 11:16:33 -0000 X-IronPort-AV: E=Sophos;i="4.73,583,1325462400"; d="scan'208";a="11286346" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Mar 2012 11:16:32 +0000 Received: from norwich.cam.xci-test.com (10.80.248.129) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 14 Mar 2012 11:16:32 +0000 Received: from mariner.cam.xci-test.com ([10.80.2.22] helo=mariner.uk.xensource.com ident=Debian-exim) by norwich.cam.xci-test.com with esmtp (Exim 4.72) (envelope-from ) id 1S7mC0-0000lM-FU; Wed, 14 Mar 2012 11:16:32 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1S7mC0-0005g0-EW; Wed, 14 Mar 2012 11:16:32 +0000 From: Ian Jackson MIME-Version: 1.0 Message-ID: <20320.32272.203100.527161@mariner.uk.xensource.com> Date: Wed, 14 Mar 2012 11:16:32 +0000 To: Ian Campbell Newsgroups: chiark.mail.xen.devel In-Reply-To: References: <1331554278.23971.63.camel@zakaz.uk.xensource.com> X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu) Cc: Bamvor Jian Zhang , Jim Fehlig , xen-api@lists.xen.org, "xen-devel@lists.xen.org" Subject: [Xen-API] [Xen-devel] libxl stable API (Re: 4.2 TODO update) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Ian Campbell writes ("[Xen-devel] libxl stable API (Re: 4.2 TODO update)"): > Lastly we also to decide what we want to do about ABI (as opposed to > API) compatibility. Obviously if we change the ABI then we should change > the SONAME, but is this something we want to commit to avoiding? i.e. > should it be possible to build a downstream against libxl.so.2.0 (the > current libxl soname) from 4.2 and expect that dropping in libxl.so.2.0 > >from 4.3 will Just Work against the new hypervisor interfaces? Or do we > expect that 4.3 will provide libxl.so.2.1 and that the same downstream > source can be built twice? (e.g. with the correct one selected via some > plugin mechanism). Obviously avoiding ABI changes is a lot harder and > I'm not sure if that is something we are able to commit to at this stage > (and I'm not sure how good we would be at it even if we did try and make > that commitment). I agree with most of what you say. I don't think we can commit to not making ABI changes. It is thus an unfortunate fact that the whole stack, from libxl caller on down to the hypervisor, will have to change together when the version of Xen is updated. > > * Safe fork vs. fd handling hooks. This is an API > > addition, so maybe not required fro stable API, bit need > > to have for 4.2? (Ian J, patches posted) I think this is important to have. It will imply changes to quite a few ordinary api functions. Ian. _______________________________________________ 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 14 11:16:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 11:16:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7mC5-0006XP-3P; Wed, 14 Mar 2012 11:16:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7mC4-0006WH-0g for xen-api@lists.xen.org; Wed, 14 Mar 2012 11:16:36 +0000 Received: from [193.109.254.147:33921] by server-1.bemta-14.messagelabs.com id 2B/63-12485-31E706F4; Wed, 14 Mar 2012 11:16:35 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1331723792!492319!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODc5Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26363 invoked from network); 14 Mar 2012 11:16:33 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Mar 2012 11:16:33 -0000 X-IronPort-AV: E=Sophos;i="4.73,583,1325462400"; d="scan'208";a="11286346" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Mar 2012 11:16:32 +0000 Received: from norwich.cam.xci-test.com (10.80.248.129) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 14 Mar 2012 11:16:32 +0000 Received: from mariner.cam.xci-test.com ([10.80.2.22] helo=mariner.uk.xensource.com ident=Debian-exim) by norwich.cam.xci-test.com with esmtp (Exim 4.72) (envelope-from ) id 1S7mC0-0000lM-FU; Wed, 14 Mar 2012 11:16:32 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1S7mC0-0005g0-EW; Wed, 14 Mar 2012 11:16:32 +0000 From: Ian Jackson MIME-Version: 1.0 Message-ID: <20320.32272.203100.527161@mariner.uk.xensource.com> Date: Wed, 14 Mar 2012 11:16:32 +0000 To: Ian Campbell Newsgroups: chiark.mail.xen.devel In-Reply-To: References: <1331554278.23971.63.camel@zakaz.uk.xensource.com> X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu) Cc: Bamvor Jian Zhang , Jim Fehlig , xen-api@lists.xen.org, "xen-devel@lists.xen.org" Subject: [Xen-API] [Xen-devel] libxl stable API (Re: 4.2 TODO update) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Ian Campbell writes ("[Xen-devel] libxl stable API (Re: 4.2 TODO update)"): > Lastly we also to decide what we want to do about ABI (as opposed to > API) compatibility. Obviously if we change the ABI then we should change > the SONAME, but is this something we want to commit to avoiding? i.e. > should it be possible to build a downstream against libxl.so.2.0 (the > current libxl soname) from 4.2 and expect that dropping in libxl.so.2.0 > >from 4.3 will Just Work against the new hypervisor interfaces? Or do we > expect that 4.3 will provide libxl.so.2.1 and that the same downstream > source can be built twice? (e.g. with the correct one selected via some > plugin mechanism). Obviously avoiding ABI changes is a lot harder and > I'm not sure if that is something we are able to commit to at this stage > (and I'm not sure how good we would be at it even if we did try and make > that commitment). I agree with most of what you say. I don't think we can commit to not making ABI changes. It is thus an unfortunate fact that the whole stack, from libxl caller on down to the hypervisor, will have to change together when the version of Xen is updated. > > * Safe fork vs. fd handling hooks. This is an API > > addition, so maybe not required fro stable API, bit need > > to have for 4.2? (Ian J, patches posted) I think this is important to have. It will imply changes to quite a few ordinary api functions. Ian. _______________________________________________ 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 14 13:38:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 13:38: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 1S7oP0-0004RK-JC; Wed, 14 Mar 2012 13:38:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7oOy-0004RB-PM for xen-api@lists.xen.org; Wed, 14 Mar 2012 13:38:04 +0000 Received: from [85.158.143.99:44688] by server-2.bemta-4.messagelabs.com id 6A/70-17550-B3F906F4; Wed, 14 Mar 2012 13:38:03 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1331732283!18615676!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODc5Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26543 invoked from network); 14 Mar 2012 13:38:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 14 Mar 2012 13:38:03 -0000 X-IronPort-AV: E=Sophos;i="4.73,584,1325462400"; d="scan'208";a="11290671" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Mar 2012 13:37:29 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 14 Mar 2012 13:37:29 +0000 Message-ID: <1331732247.23971.438.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Ian Jackson Date: Wed, 14 Mar 2012 13:37:27 +0000 In-Reply-To: <20320.32272.203100.527161@mariner.uk.xensource.com> References: <1331554278.23971.63.camel@zakaz.uk.xensource.com> <20320.32272.203100.527161@mariner.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: Bamvor Jian Zhang , Jim Fehlig , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] libxl stable API (Re: 4.2 TODO update) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Wed, 2012-03-14 at 11:16 +0000, Ian Jackson wrote: > Ian Campbell writes ("[Xen-devel] libxl stable API (Re: 4.2 TODO update)"): > > Lastly we also to decide what we want to do about ABI (as opposed to > > API) compatibility. Obviously if we change the ABI then we should change > > the SONAME, but is this something we want to commit to avoiding? i.e. > > should it be possible to build a downstream against libxl.so.2.0 (the > > current libxl soname) from 4.2 and expect that dropping in libxl.so.2.0 > > >from 4.3 will Just Work against the new hypervisor interfaces? Or do we > > expect that 4.3 will provide libxl.so.2.1 and that the same downstream > > source can be built twice? (e.g. with the correct one selected via some > > plugin mechanism). Obviously avoiding ABI changes is a lot harder and > > I'm not sure if that is something we are able to commit to at this stage > > (and I'm not sure how good we would be at it even if we did try and make > > that commitment). > > I agree with most of what you say. Thanks. I shall add "agree & document compatibility guarantees + associated technical measures" to the TODO list. > I don't think we can commit to not making ABI changes. It is thus an > unfortunate fact that the whole stack, from libxl caller on down to > the hypervisor, will have to change together when the version of Xen > is updated. Right. We can strive to make this a straight rebuild with no source changes (somewhat akin to a binNMU in Debian-speak). > > > > * Safe fork vs. fd handling hooks. This is an API > > > addition, so maybe not required fro stable API, bit need > > > to have for 4.2? (Ian J, patches posted) > > I think this is important to have. It will imply changes to quite a > few ordinary api functions. Thanks, I will update the commentary accordingly in the next iteration. Ian. _______________________________________________ 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 14 13:38:14 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 13:38: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 1S7oP0-0004RK-JC; Wed, 14 Mar 2012 13:38:06 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7oOy-0004RB-PM for xen-api@lists.xen.org; Wed, 14 Mar 2012 13:38:04 +0000 Received: from [85.158.143.99:44688] by server-2.bemta-4.messagelabs.com id 6A/70-17550-B3F906F4; Wed, 14 Mar 2012 13:38:03 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1331732283!18615676!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODc5Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26543 invoked from network); 14 Mar 2012 13:38:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 14 Mar 2012 13:38:03 -0000 X-IronPort-AV: E=Sophos;i="4.73,584,1325462400"; d="scan'208";a="11290671" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Mar 2012 13:37:29 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 14 Mar 2012 13:37:29 +0000 Message-ID: <1331732247.23971.438.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Ian Jackson Date: Wed, 14 Mar 2012 13:37:27 +0000 In-Reply-To: <20320.32272.203100.527161@mariner.uk.xensource.com> References: <1331554278.23971.63.camel@zakaz.uk.xensource.com> <20320.32272.203100.527161@mariner.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: Bamvor Jian Zhang , Jim Fehlig , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] libxl stable API (Re: 4.2 TODO update) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Wed, 2012-03-14 at 11:16 +0000, Ian Jackson wrote: > Ian Campbell writes ("[Xen-devel] libxl stable API (Re: 4.2 TODO update)"): > > Lastly we also to decide what we want to do about ABI (as opposed to > > API) compatibility. Obviously if we change the ABI then we should change > > the SONAME, but is this something we want to commit to avoiding? i.e. > > should it be possible to build a downstream against libxl.so.2.0 (the > > current libxl soname) from 4.2 and expect that dropping in libxl.so.2.0 > > >from 4.3 will Just Work against the new hypervisor interfaces? Or do we > > expect that 4.3 will provide libxl.so.2.1 and that the same downstream > > source can be built twice? (e.g. with the correct one selected via some > > plugin mechanism). Obviously avoiding ABI changes is a lot harder and > > I'm not sure if that is something we are able to commit to at this stage > > (and I'm not sure how good we would be at it even if we did try and make > > that commitment). > > I agree with most of what you say. Thanks. I shall add "agree & document compatibility guarantees + associated technical measures" to the TODO list. > I don't think we can commit to not making ABI changes. It is thus an > unfortunate fact that the whole stack, from libxl caller on down to > the hypervisor, will have to change together when the version of Xen > is updated. Right. We can strive to make this a straight rebuild with no source changes (somewhat akin to a binNMU in Debian-speak). > > > > * Safe fork vs. fd handling hooks. This is an API > > > addition, so maybe not required fro stable API, bit need > > > to have for 4.2? (Ian J, patches posted) > > I think this is important to have. It will imply changes to quite a > few ordinary api functions. Thanks, I will update the commentary accordingly in the next iteration. Ian. _______________________________________________ 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 14 16:59:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 16:59:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7rYG-0006e6-DQ; Wed, 14 Mar 2012 16:59:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7rYE-0006dp-BR for xen-api@lists.xen.org; Wed, 14 Mar 2012 16:59:50 +0000 Received: from [85.158.138.51:44816] by server-7.bemta-3.messagelabs.com id A5/CF-21324-58EC06F4; Wed, 14 Mar 2012 16:59:49 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1331744388!17675332!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODc5Mw==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25881 invoked from network); 14 Mar 2012 16:59:48 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 14 Mar 2012 16:59:48 -0000 X-IronPort-AV: E=Sophos;i="4.73,584,1325462400"; d="scan'208";a="11298175" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Mar 2012 16:59:48 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 14 Mar 2012 16:59:48 +0000 Message-ID: <1331744386.23971.496.camel@zakaz.uk.xensource.com> From: Ian Campbell To: xen-devel Date: Wed, 14 Mar 2012 16:59:46 +0000 In-Reply-To: <1330534437.4270.143.camel@zakaz.uk.xensource.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Wed, 2012-02-29 at 16:53 +0000, Ian Campbell wrote: > Below are a few ideas which have been floating around as potential > projects (or broad subject areas for projects) for GSoC this year. > > If you want any more information on any particular item then please ask. > Likewise if you have any ideas of your own please feel free to chip in. > > If you think you might be interested in a project, either as mentor or > potential student, then please add it to the wiki page at > http://wiki.xen.org/wiki/GSoC_2012_Ideas > I've just added a proposal for "xl to xapi offline VM migration utility". I know the xl side well and I'm reasonably familiar with XenAPI etc but it would be really useful to have a co-/backup-mentor from the xen-api@ side of things. Ian. > TOOLS > ----- > - pv grub2 > - xapi support in libvirt > - make xapi use libxl > - compile xapi on ARM > - OpenXenManager > - driver domains > - PV dbus > - HA daemon for Remus > - HA daemon for XCP > > PERF > ---- > - Oprofile > - Linux perf tools in guest > > HYPERVISOR > ---------- > - insmod Xen > - event channel limits > - NUMA > > MEMORY > ------ > - disk based memory sharing > - memory scanner > - paging replacing PoD > - VM Fork > - Copy on read (past VDI boot) > > > IO > -- > - PV OpenGL/Gallium > - PV USB > - PV USB3 > - PV SCSI > - PVFB in Xorg > - Infiniband > > > STORAGE > ------- > - gluster/ceph plugins > > > QEMU > ---- > - BSD libc > - upstream QEMU stubdoms > > > TESTS > ----- > - better web reporting > - more tests > - upstream linux > > > DISTROS > ------- > - packaging stubdoms > - xen on centos6 > - driver domains > - figure out the VM format issue > - XSM in distros > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel _______________________________________________ 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 14 16:59:58 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 16:59:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7rYG-0006e6-DQ; Wed, 14 Mar 2012 16:59:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7rYE-0006dp-BR for xen-api@lists.xen.org; Wed, 14 Mar 2012 16:59:50 +0000 Received: from [85.158.138.51:44816] by server-7.bemta-3.messagelabs.com id A5/CF-21324-58EC06F4; Wed, 14 Mar 2012 16:59:49 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1331744388!17675332!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODc5Mw==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25881 invoked from network); 14 Mar 2012 16:59:48 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 14 Mar 2012 16:59:48 -0000 X-IronPort-AV: E=Sophos;i="4.73,584,1325462400"; d="scan'208";a="11298175" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Mar 2012 16:59:48 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Wed, 14 Mar 2012 16:59:48 +0000 Message-ID: <1331744386.23971.496.camel@zakaz.uk.xensource.com> From: Ian Campbell To: xen-devel Date: Wed, 14 Mar 2012 16:59:46 +0000 In-Reply-To: <1330534437.4270.143.camel@zakaz.uk.xensource.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Wed, 2012-02-29 at 16:53 +0000, Ian Campbell wrote: > Below are a few ideas which have been floating around as potential > projects (or broad subject areas for projects) for GSoC this year. > > If you want any more information on any particular item then please ask. > Likewise if you have any ideas of your own please feel free to chip in. > > If you think you might be interested in a project, either as mentor or > potential student, then please add it to the wiki page at > http://wiki.xen.org/wiki/GSoC_2012_Ideas > I've just added a proposal for "xl to xapi offline VM migration utility". I know the xl side well and I'm reasonably familiar with XenAPI etc but it would be really useful to have a co-/backup-mentor from the xen-api@ side of things. Ian. > TOOLS > ----- > - pv grub2 > - xapi support in libvirt > - make xapi use libxl > - compile xapi on ARM > - OpenXenManager > - driver domains > - PV dbus > - HA daemon for Remus > - HA daemon for XCP > > PERF > ---- > - Oprofile > - Linux perf tools in guest > > HYPERVISOR > ---------- > - insmod Xen > - event channel limits > - NUMA > > MEMORY > ------ > - disk based memory sharing > - memory scanner > - paging replacing PoD > - VM Fork > - Copy on read (past VDI boot) > > > IO > -- > - PV OpenGL/Gallium > - PV USB > - PV USB3 > - PV SCSI > - PVFB in Xorg > - Infiniband > > > STORAGE > ------- > - gluster/ceph plugins > > > QEMU > ---- > - BSD libc > - upstream QEMU stubdoms > > > TESTS > ----- > - better web reporting > - more tests > - upstream linux > > > DISTROS > ------- > - packaging stubdoms > - xen on centos6 > - driver domains > - figure out the VM format issue > - XSM in distros > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel _______________________________________________ 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 14 17:56:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 17:56:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7sQV-000897-2S; Wed, 14 Mar 2012 17:55:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7sQU-000890-GH for xen-api@lists.xen.org; Wed, 14 Mar 2012 17:55:54 +0000 Received: from [85.158.143.35:26572] by server-1.bemta-4.messagelabs.com id E5/83-20925-9ABD06F4; Wed, 14 Mar 2012 17:55:53 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1331747752!13996265!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODc5Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15601 invoked from network); 14 Mar 2012 17:55:52 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 14 Mar 2012 17:55:52 -0000 X-IronPort-AV: E=Sophos;i="4.73,585,1325462400"; d="scan'208";a="11299524" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Mar 2012 17:55:51 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Wed, 14 Mar 2012 17:55:51 +0000 From: Dave Scott To: Ian Campbell , xen-devel Date: Wed, 14 Mar 2012 17:55:50 +0000 Thread-Topic: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming Thread-Index: Ac0CBBqPWxj3a7qLRWC+Jp5tRv/xXgABlfvg Message-ID: <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> In-Reply-To: <1331744386.23971.496.camel@zakaz.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Ian Campbell wrote: > On Wed, 2012-02-29 at 16:53 +0000, Ian Campbell wrote: > > Below are a few ideas which have been floating around as potential > > projects (or broad subject areas for projects) for GSoC this year. > > > > If you want any more information on any particular item then please > ask. > > Likewise if you have any ideas of your own please feel free to chip > in. > > > > If you think you might be interested in a project, either as mentor > or > > potential student, then please add it to the wiki page at > > http://wiki.xen.org/wiki/GSoC_2012_Ideas > > > > I've just added a proposal for "xl to xapi offline VM migration > utility". I know the xl side well and I'm reasonably familiar with > XenAPI etc but it would be really useful to have a co-/backup-mentor > from the xen-api@ side of things. I could be a co-/backup-mentor for that. I've been busy recently moving all the domain management parts of xapi into a separate daemon, which later can be libxl'ed up. For testing (and for fun) I've made it understand some of xm/xl config file syntax eg [root@st20 ~]# xn export-metadata-xm win7 win7.xm [root@st20 ~]# cat win7.xm name='win7' builder='hvmloader' boot='dc' vcpus=1 memory=2048 disk=[ 'sm:7af570d8-f8c5-4103-ac1d-969fe28bfc11,hda,w', 'sm:137c8a61-113c-ab46-20fa-5c0574eaff77,hdb:cdrom,r' ] vif=[ ] pci=[ ] pci_msitranslate=1 pci_power_mgmt=0 # transient=true Another goal of the refactoring is to allow xapi to co-exist with domains created by someone else (e.g. xl/libxl). This should allow a migration to be done piecemeal, one VM at a time on the same host. Cheers, Dave > > Ian. > > > TOOLS > > ----- > > - pv grub2 > > - xapi support in libvirt > > - make xapi use libxl > > - compile xapi on ARM > > - OpenXenManager > > - driver domains > > - PV dbus > > - HA daemon for Remus > > - HA daemon for XCP > > > > PERF > > ---- > > - Oprofile > > - Linux perf tools in guest > > > > HYPERVISOR > > ---------- > > - insmod Xen > > - event channel limits > > - NUMA > > > > MEMORY > > ------ > > - disk based memory sharing > > - memory scanner > > - paging replacing PoD > > - VM Fork > > - Copy on read (past VDI boot) > > > > > > IO > > -- > > - PV OpenGL/Gallium > > - PV USB > > - PV USB3 > > - PV SCSI > > - PVFB in Xorg > > - Infiniband > > > > > > STORAGE > > ------- > > - gluster/ceph plugins > > > > > > QEMU > > ---- > > - BSD libc > > - upstream QEMU stubdoms > > > > > > TESTS > > ----- > > - better web reporting > > - more tests > > - upstream linux > > > > > > DISTROS > > ------- > > - packaging stubdoms > > - xen on centos6 > > - driver domains > > - figure out the VM format issue > > - XSM in distros > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > > > > _______________________________________________ > 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 14 17:56:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 17:56:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7sQV-000897-2S; Wed, 14 Mar 2012 17:55:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7sQU-000890-GH for xen-api@lists.xen.org; Wed, 14 Mar 2012 17:55:54 +0000 Received: from [85.158.143.35:26572] by server-1.bemta-4.messagelabs.com id E5/83-20925-9ABD06F4; Wed, 14 Mar 2012 17:55:53 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1331747752!13996265!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4ODc5Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15601 invoked from network); 14 Mar 2012 17:55:52 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 14 Mar 2012 17:55:52 -0000 X-IronPort-AV: E=Sophos;i="4.73,585,1325462400"; d="scan'208";a="11299524" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 14 Mar 2012 17:55:51 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Wed, 14 Mar 2012 17:55:51 +0000 From: Dave Scott To: Ian Campbell , xen-devel Date: Wed, 14 Mar 2012 17:55:50 +0000 Thread-Topic: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming Thread-Index: Ac0CBBqPWxj3a7qLRWC+Jp5tRv/xXgABlfvg Message-ID: <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> In-Reply-To: <1331744386.23971.496.camel@zakaz.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Ian Campbell wrote: > On Wed, 2012-02-29 at 16:53 +0000, Ian Campbell wrote: > > Below are a few ideas which have been floating around as potential > > projects (or broad subject areas for projects) for GSoC this year. > > > > If you want any more information on any particular item then please > ask. > > Likewise if you have any ideas of your own please feel free to chip > in. > > > > If you think you might be interested in a project, either as mentor > or > > potential student, then please add it to the wiki page at > > http://wiki.xen.org/wiki/GSoC_2012_Ideas > > > > I've just added a proposal for "xl to xapi offline VM migration > utility". I know the xl side well and I'm reasonably familiar with > XenAPI etc but it would be really useful to have a co-/backup-mentor > from the xen-api@ side of things. I could be a co-/backup-mentor for that. I've been busy recently moving all the domain management parts of xapi into a separate daemon, which later can be libxl'ed up. For testing (and for fun) I've made it understand some of xm/xl config file syntax eg [root@st20 ~]# xn export-metadata-xm win7 win7.xm [root@st20 ~]# cat win7.xm name='win7' builder='hvmloader' boot='dc' vcpus=1 memory=2048 disk=[ 'sm:7af570d8-f8c5-4103-ac1d-969fe28bfc11,hda,w', 'sm:137c8a61-113c-ab46-20fa-5c0574eaff77,hdb:cdrom,r' ] vif=[ ] pci=[ ] pci_msitranslate=1 pci_power_mgmt=0 # transient=true Another goal of the refactoring is to allow xapi to co-exist with domains created by someone else (e.g. xl/libxl). This should allow a migration to be done piecemeal, one VM at a time on the same host. Cheers, Dave > > Ian. > > > TOOLS > > ----- > > - pv grub2 > > - xapi support in libvirt > > - make xapi use libxl > > - compile xapi on ARM > > - OpenXenManager > > - driver domains > > - PV dbus > > - HA daemon for Remus > > - HA daemon for XCP > > > > PERF > > ---- > > - Oprofile > > - Linux perf tools in guest > > > > HYPERVISOR > > ---------- > > - insmod Xen > > - event channel limits > > - NUMA > > > > MEMORY > > ------ > > - disk based memory sharing > > - memory scanner > > - paging replacing PoD > > - VM Fork > > - Copy on read (past VDI boot) > > > > > > IO > > -- > > - PV OpenGL/Gallium > > - PV USB > > - PV USB3 > > - PV SCSI > > - PVFB in Xorg > > - Infiniband > > > > > > STORAGE > > ------- > > - gluster/ceph plugins > > > > > > QEMU > > ---- > > - BSD libc > > - upstream QEMU stubdoms > > > > > > TESTS > > ----- > > - better web reporting > > - more tests > > - upstream linux > > > > > > DISTROS > > ------- > > - packaging stubdoms > > - xen on centos6 > > - driver domains > > - figure out the VM format issue > > - XSM in distros > > > > > > > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > > > > _______________________________________________ > 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 14 19:00:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 19:00: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 1S7tRA-00022h-38; Wed, 14 Mar 2012 19:00:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7tR8-00022Q-QE for xen-api@lists.xen.org; Wed, 14 Mar 2012 19:00:39 +0000 Received: from [85.158.143.99:12732] by server-1.bemta-4.messagelabs.com id 30/E3-20925-5DAE06F4; Wed, 14 Mar 2012 19:00:37 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1331751635!19227539!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDM5MjAzNQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18447 invoked from network); 14 Mar 2012 19:00:37 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-9.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Mar 2012 19:00:37 -0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q2EJ0WU2015144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Mar 2012 19:00:33 GMT Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q2EJ0Vbj009669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Mar 2012 19:00:32 GMT Received: from abhmt107.oracle.com (abhmt107.oracle.com [141.146.116.59]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q2EJ0UWg015958; Wed, 14 Mar 2012 14:00:30 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 14 Mar 2012 12:00:30 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 14CCB40203; Wed, 14 Mar 2012 14:56:29 -0400 (EDT) Date: Wed, 14 Mar 2012 14:56:29 -0400 From: Konrad Rzeszutek Wilk To: Ian Campbell Message-ID: <20120314185629.GB5341@phenom.dumpdata.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <20120312170012.GI5369@phenom.dumpdata.com> <1331573131.23971.165.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1331573131.23971.165.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet21.oracle.com [156.151.31.93] X-CT-RefId: str=0001.0A090203.4F60EAD2.000A,ss=1,re=0.000,fgs=0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > > Sign me up as a mentor for that! > > Please update http://wiki.xen.org/wiki/GSoC_2012_Ideas as > appropriate ;-) Done! > > > > > > > HYPERVISOR > > > ---------- > > > - insmod Xen > > > - event channel limits > > > - NUMA > > > > Yeah, we need that. I think there were some patches posted for that.. whatever > > happend to them? > > I think there are some patches, which have gone in and various ideas for > ongoing work but I'm not sure what the details were -- hopefully whoever > shouted out NUMA (this was a brainstorm remember ;-)) will chime in. Dulloor Rao had some patches: http://old-list-archives.xen.org/archives/html/xen-devel/2010-04/msg00105.html > > > > > > > - Infiniband > > > > Huh? InfiniBand PV drivers? > > I think this is about using Infiniband for extra fast migration, by > pumping the migration data over infiniband instead of a normal network. > But again hopefully someone who knows what that bullet was will chime > in. I seem to remember someone mentioning it at the Munich hackathon. > > Ian. _______________________________________________ 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 14 19:00:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 14 Mar 2012 19:00: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 1S7tRA-00022h-38; Wed, 14 Mar 2012 19:00:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7tR8-00022Q-QE for xen-api@lists.xen.org; Wed, 14 Mar 2012 19:00:39 +0000 Received: from [85.158.143.99:12732] by server-1.bemta-4.messagelabs.com id 30/E3-20925-5DAE06F4; Wed, 14 Mar 2012 19:00:37 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1331751635!19227539!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDM5MjAzNQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18447 invoked from network); 14 Mar 2012 19:00:37 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-9.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Mar 2012 19:00:37 -0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q2EJ0WU2015144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Mar 2012 19:00:33 GMT Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q2EJ0Vbj009669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Mar 2012 19:00:32 GMT Received: from abhmt107.oracle.com (abhmt107.oracle.com [141.146.116.59]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q2EJ0UWg015958; Wed, 14 Mar 2012 14:00:30 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 14 Mar 2012 12:00:30 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 14CCB40203; Wed, 14 Mar 2012 14:56:29 -0400 (EDT) Date: Wed, 14 Mar 2012 14:56:29 -0400 From: Konrad Rzeszutek Wilk To: Ian Campbell Message-ID: <20120314185629.GB5341@phenom.dumpdata.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <20120312170012.GI5369@phenom.dumpdata.com> <1331573131.23971.165.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1331573131.23971.165.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet21.oracle.com [156.151.31.93] X-CT-RefId: str=0001.0A090203.4F60EAD2.000A,ss=1,re=0.000,fgs=0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > > Sign me up as a mentor for that! > > Please update http://wiki.xen.org/wiki/GSoC_2012_Ideas as > appropriate ;-) Done! > > > > > > > HYPERVISOR > > > ---------- > > > - insmod Xen > > > - event channel limits > > > - NUMA > > > > Yeah, we need that. I think there were some patches posted for that.. whatever > > happend to them? > > I think there are some patches, which have gone in and various ideas for > ongoing work but I'm not sure what the details were -- hopefully whoever > shouted out NUMA (this was a brainstorm remember ;-)) will chime in. Dulloor Rao had some patches: http://old-list-archives.xen.org/archives/html/xen-devel/2010-04/msg00105.html > > > > > > > - Infiniband > > > > Huh? InfiniBand PV drivers? > > I think this is about using Infiniband for extra fast migration, by > pumping the migration data over infiniband instead of a normal network. > But again hopefully someone who knows what that bullet was will chime > in. I seem to remember someone mentioning it at the Munich hackathon. > > Ian. _______________________________________________ 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 15 07:52:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 07:52:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S85Te-0004rD-Bp; Thu, 15 Mar 2012 07:52:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S85Tc-0004qx-Rb for xen-api@lists.xen.org; Thu, 15 Mar 2012 07:52:01 +0000 Received: from [85.158.139.83:40873] by server-11.bemta-5.messagelabs.com id 37/19-12959-0AF916F4; Thu, 15 Mar 2012 07:52:00 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1331797919!15507276!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTEwNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10971 invoked from network); 15 Mar 2012 07:51:59 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 07:51:59 -0000 X-IronPort-AV: E=Sophos;i="4.73,589,1325462400"; d="scan'208";a="11308991" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Mar 2012 07:51:58 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 15 Mar 2012 07:51:59 +0000 Message-ID: <1331797918.13956.27.camel@dagon.hellion.org.uk> From: Ian Campbell To: Dave Scott Date: Thu, 15 Mar 2012 07:51:58 +0000 In-Reply-To: <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Wed, 2012-03-14 at 17:55 +0000, Dave Scott wrote: > Ian Campbell wrote: > > I've just added a proposal for "xl to xapi offline VM migration > > utility". I know the xl side well and I'm reasonably familiar with > > XenAPI etc but it would be really useful to have a co-/backup-mentor > > from the xen-api@ side of things. > > I could be a co-/backup-mentor for that. Excellent, thanks! > I've been busy recently moving all the domain management parts of xapi > into a separate daemon, which later can be libxl'ed up. For testing > (and for fun) I've made it understand some of xm/xl config file syntax eg Interesting. Pure ocaml I presume? > [root@st20 ~]# xn export-metadata-xm win7 win7.xm xn? We're going to run out of letters soon ;-) Do you handle import as well as export? One of the more interesting use cases (I think) is handling folks who want to migrate from an xm/xl based setup to a xapi setup (e.g. by installing Kronos on their existing Debian system). That's was the primary aim of the proposed project. > [root@st20 ~]# cat win7.xm > name='win7' > builder='hvmloader' > boot='dc' > vcpus=1 > memory=2048 > disk=[ 'sm:7af570d8-f8c5-4103-ac1d-969fe28bfc11,hda,w', 'sm:137c8a61-113c-ab46-20fa-5c0574eaff77,hdb:cdrom,r' ] Half-assed wondering -- I wonder if sm: (or script=sm or similar) support could work in xl... > vif=[ ] > pci=[ ] > pci_msitranslate=1 > pci_power_mgmt=0 > # transient=true > > Another goal of the refactoring is to allow xapi to co-exist with domains > created by someone else (e.g. xl/libxl). This should allow a migration to > be done piecemeal, one VM at a time on the same host. The brainstoming list below includes "make xapi use libxl". Is this (or a subset of this) the sort of thing which could be done by a GSoC student? I suppose it is only fair that I offer to be co-/backup-mentor to a main mentor from the xapi side of things for such a project... Ian. > > Cheers, > Dave > > > > > Ian. > > > > > TOOLS > > > ----- > > > - pv grub2 > > > - xapi support in libvirt > > > - make xapi use libxl > > > - compile xapi on ARM > > > - OpenXenManager > > > - driver domains > > > - PV dbus > > > - HA daemon for Remus > > > - HA daemon for XCP > > > > > > PERF > > > ---- > > > - Oprofile > > > - Linux perf tools in guest > > > > > > HYPERVISOR > > > ---------- > > > - insmod Xen > > > - event channel limits > > > - NUMA > > > > > > MEMORY > > > ------ > > > - disk based memory sharing > > > - memory scanner > > > - paging replacing PoD > > > - VM Fork > > > - Copy on read (past VDI boot) > > > > > > > > > IO > > > -- > > > - PV OpenGL/Gallium > > > - PV USB > > > - PV USB3 > > > - PV SCSI > > > - PVFB in Xorg > > > - Infiniband > > > > > > > > > STORAGE > > > ------- > > > - gluster/ceph plugins > > > > > > > > > QEMU > > > ---- > > > - BSD libc > > > - upstream QEMU stubdoms > > > > > > > > > TESTS > > > ----- > > > - better web reporting > > > - more tests > > > - upstream linux > > > > > > > > > DISTROS > > > ------- > > > - packaging stubdoms > > > - xen on centos6 > > > - driver domains > > > - figure out the VM format issue > > > - XSM in distros > > > > > > > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xen.org > > > http://lists.xen.org/xen-devel > > > > > > > > _______________________________________________ > > 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 15 07:52:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 07:52:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S85Te-0004rD-Bp; Thu, 15 Mar 2012 07:52:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S85Tc-0004qx-Rb for xen-api@lists.xen.org; Thu, 15 Mar 2012 07:52:01 +0000 Received: from [85.158.139.83:40873] by server-11.bemta-5.messagelabs.com id 37/19-12959-0AF916F4; Thu, 15 Mar 2012 07:52:00 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1331797919!15507276!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTEwNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10971 invoked from network); 15 Mar 2012 07:51:59 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 07:51:59 -0000 X-IronPort-AV: E=Sophos;i="4.73,589,1325462400"; d="scan'208";a="11308991" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Mar 2012 07:51:58 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 15 Mar 2012 07:51:59 +0000 Message-ID: <1331797918.13956.27.camel@dagon.hellion.org.uk> From: Ian Campbell To: Dave Scott Date: Thu, 15 Mar 2012 07:51:58 +0000 In-Reply-To: <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Wed, 2012-03-14 at 17:55 +0000, Dave Scott wrote: > Ian Campbell wrote: > > I've just added a proposal for "xl to xapi offline VM migration > > utility". I know the xl side well and I'm reasonably familiar with > > XenAPI etc but it would be really useful to have a co-/backup-mentor > > from the xen-api@ side of things. > > I could be a co-/backup-mentor for that. Excellent, thanks! > I've been busy recently moving all the domain management parts of xapi > into a separate daemon, which later can be libxl'ed up. For testing > (and for fun) I've made it understand some of xm/xl config file syntax eg Interesting. Pure ocaml I presume? > [root@st20 ~]# xn export-metadata-xm win7 win7.xm xn? We're going to run out of letters soon ;-) Do you handle import as well as export? One of the more interesting use cases (I think) is handling folks who want to migrate from an xm/xl based setup to a xapi setup (e.g. by installing Kronos on their existing Debian system). That's was the primary aim of the proposed project. > [root@st20 ~]# cat win7.xm > name='win7' > builder='hvmloader' > boot='dc' > vcpus=1 > memory=2048 > disk=[ 'sm:7af570d8-f8c5-4103-ac1d-969fe28bfc11,hda,w', 'sm:137c8a61-113c-ab46-20fa-5c0574eaff77,hdb:cdrom,r' ] Half-assed wondering -- I wonder if sm: (or script=sm or similar) support could work in xl... > vif=[ ] > pci=[ ] > pci_msitranslate=1 > pci_power_mgmt=0 > # transient=true > > Another goal of the refactoring is to allow xapi to co-exist with domains > created by someone else (e.g. xl/libxl). This should allow a migration to > be done piecemeal, one VM at a time on the same host. The brainstoming list below includes "make xapi use libxl". Is this (or a subset of this) the sort of thing which could be done by a GSoC student? I suppose it is only fair that I offer to be co-/backup-mentor to a main mentor from the xapi side of things for such a project... Ian. > > Cheers, > Dave > > > > > Ian. > > > > > TOOLS > > > ----- > > > - pv grub2 > > > - xapi support in libvirt > > > - make xapi use libxl > > > - compile xapi on ARM > > > - OpenXenManager > > > - driver domains > > > - PV dbus > > > - HA daemon for Remus > > > - HA daemon for XCP > > > > > > PERF > > > ---- > > > - Oprofile > > > - Linux perf tools in guest > > > > > > HYPERVISOR > > > ---------- > > > - insmod Xen > > > - event channel limits > > > - NUMA > > > > > > MEMORY > > > ------ > > > - disk based memory sharing > > > - memory scanner > > > - paging replacing PoD > > > - VM Fork > > > - Copy on read (past VDI boot) > > > > > > > > > IO > > > -- > > > - PV OpenGL/Gallium > > > - PV USB > > > - PV USB3 > > > - PV SCSI > > > - PVFB in Xorg > > > - Infiniband > > > > > > > > > STORAGE > > > ------- > > > - gluster/ceph plugins > > > > > > > > > QEMU > > > ---- > > > - BSD libc > > > - upstream QEMU stubdoms > > > > > > > > > TESTS > > > ----- > > > - better web reporting > > > - more tests > > > - upstream linux > > > > > > > > > DISTROS > > > ------- > > > - packaging stubdoms > > > - xen on centos6 > > > - driver domains > > > - figure out the VM format issue > > > - XSM in distros > > > > > > > > > > > > _______________________________________________ > > > Xen-devel mailing list > > > Xen-devel@lists.xen.org > > > http://lists.xen.org/xen-devel > > > > > > > > _______________________________________________ > > 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 15 10:02:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 10:02: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 1S87Vn-0002Nt-M0; Thu, 15 Mar 2012 10:02:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S87Vm-0002Ne-5K for xen-api@lists.xen.org; Thu, 15 Mar 2012 10:02:22 +0000 Received: from [193.109.254.147:65394] by server-2.bemta-14.messagelabs.com id 62/7C-11301-D2EB16F4; Thu, 15 Mar 2012 10:02:21 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1331805740!640427!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTI0MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25719 invoked from network); 15 Mar 2012 10:02:20 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 10:02:20 -0000 X-IronPort-AV: E=Sophos;i="4.73,590,1325462400"; d="scan'208";a="11313314" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Mar 2012 10:02:20 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 15 Mar 2012 10:02:20 +0000 From: Dave Scott To: Ian Campbell Date: Thu, 15 Mar 2012 10:02:19 +0000 Thread-Topic: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming Thread-Index: Ac0CgH/V+RT4d7qEQ3WZ+epZzMwzpgAD1Ibg Message-ID: <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> <1331797918.13956.27.camel@dagon.hellion.org.uk> In-Reply-To: <1331797918.13956.27.camel@dagon.hellion.org.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Ian Campbell wrote: > On Wed, 2012-03-14 at 17:55 +0000, Dave Scott wrote: > > I've been busy recently moving all the domain management parts of > xapi > > into a separate daemon, which later can be libxl'ed up. For testing > > (and for fun) I've made it understand some of xm/xl config file > syntax eg > > Interesting. Pure ocaml I presume? Yep. > > [root@st20 ~]# xn export-metadata-xm win7 win7.xm > > xn? We're going to run out of letters soon ;-) :-) > Do you handle import as well as export? One of the more interesting use > cases (I think) is handling folks who want to migrate from an xm/xl > based setup to a xapi setup (e.g. by installing Kronos on their > existing > Debian system). That's was the primary aim of the proposed project. IIRC it can import simple things, but it's quite incomplete. If the goal is to migrate from an xm/xl setup to xapi then it probably makes more sense to use the existing (and by definition correct) xl config parser and then talk the XenAPI directly. Or emit a xapi "metadata export". One of the interesting areas will be storage... > > [root@st20 ~]# cat win7.xm > > name='win7' > > builder='hvmloader' > > boot='dc' > > vcpus=1 > > memory=2048 > > disk=[ 'sm:7af570d8-f8c5-4103-ac1d-969fe28bfc11,hda,w', 'sm:137c8a61- > 113c-ab46-20fa-5c0574eaff77,hdb:cdrom,r' ] > > Half-assed wondering -- I wonder if sm: (or script=sm or similar) > support could work in xl... Yeah I've been wondering that too. As well as tidying up the domain handling code in xapi I've also been trying to generate docs for the xapi <-> storage interface (aka "SMAPI"). The current version is here: http://dave.recoil.org/xen/storage.html I'd also like to make the current storage plugins run standalone (currently they require xapi to be running). If we did that then we could potentially add support for XCP storage types directly into libxl (or the hotplug scripts). As well as generate docs for the SMAPI I can also generate python skeleton code, to make it easier to write storage plugins. A custom one of these might make it easier to migrate from xm/xl to xapi too, by leaving the disks where they are, rather than moving them into a regular SR. > > > vif=[ ] > > pci=[ ] > > pci_msitranslate=1 > > pci_power_mgmt=0 > > # transient=true > > > > Another goal of the refactoring is to allow xapi to co-exist with > domains > > created by someone else (e.g. xl/libxl). This should allow a > migration to > > be done piecemeal, one VM at a time on the same host. > > The brainstoming list below includes "make xapi use libxl". Is this (or > a subset of this) the sort of thing which could be done by a GSoC > student? I think a subset could probably be done in the GSoC timeframe. Before the summer starts I should have merged my refactoring into the xapi mainline. A student could then fire up the ocaml libxl bindings (they might need a bit of tweaking here or there) and then start patching things through. All the critical libxc code is now called (indirectly) via a single module: https://github.com/djs55/xen-api/blob/cooper/ocaml/xenops/xenops_server_xen.ml If that were made to use libxl then the job would be basically done. All that would be left would be little things like statistics gathering. > > I suppose it is only fair that I offer to be co-/backup-mentor to a > main > mentor from the xapi side of things for such a project... Great :-) Cheers, Dave > > Ian. > > > > > > Cheers, > > Dave > > > > > > > > Ian. > > > > > > > TOOLS > > > > ----- > > > > - pv grub2 > > > > - xapi support in libvirt > > > > - make xapi use libxl > > > > - compile xapi on ARM > > > > - OpenXenManager > > > > - driver domains > > > > - PV dbus > > > > - HA daemon for Remus > > > > - HA daemon for XCP > > > > > > > > PERF > > > > ---- > > > > - Oprofile > > > > - Linux perf tools in guest > > > > > > > > HYPERVISOR > > > > ---------- > > > > - insmod Xen > > > > - event channel limits > > > > - NUMA > > > > > > > > MEMORY > > > > ------ > > > > - disk based memory sharing > > > > - memory scanner > > > > - paging replacing PoD > > > > - VM Fork > > > > - Copy on read (past VDI boot) > > > > > > > > > > > > IO > > > > -- > > > > - PV OpenGL/Gallium > > > > - PV USB > > > > - PV USB3 > > > > - PV SCSI > > > > - PVFB in Xorg > > > > - Infiniband > > > > > > > > > > > > STORAGE > > > > ------- > > > > - gluster/ceph plugins > > > > > > > > > > > > QEMU > > > > ---- > > > > - BSD libc > > > > - upstream QEMU stubdoms > > > > > > > > > > > > TESTS > > > > ----- > > > > - better web reporting > > > > - more tests > > > > - upstream linux > > > > > > > > > > > > DISTROS > > > > ------- > > > > - packaging stubdoms > > > > - xen on centos6 > > > > - driver domains > > > > - figure out the VM format issue > > > > - XSM in distros > > > > > > > > > > > > > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.xen.org > > > > http://lists.xen.org/xen-devel > > > > > > > > > > > > _______________________________________________ > > > 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 15 10:02:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 10:02: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 1S87Vn-0002Nt-M0; Thu, 15 Mar 2012 10:02:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S87Vm-0002Ne-5K for xen-api@lists.xen.org; Thu, 15 Mar 2012 10:02:22 +0000 Received: from [193.109.254.147:65394] by server-2.bemta-14.messagelabs.com id 62/7C-11301-D2EB16F4; Thu, 15 Mar 2012 10:02:21 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1331805740!640427!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTI0MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25719 invoked from network); 15 Mar 2012 10:02:20 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 10:02:20 -0000 X-IronPort-AV: E=Sophos;i="4.73,590,1325462400"; d="scan'208";a="11313314" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Mar 2012 10:02:20 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Thu, 15 Mar 2012 10:02:20 +0000 From: Dave Scott To: Ian Campbell Date: Thu, 15 Mar 2012 10:02:19 +0000 Thread-Topic: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming Thread-Index: Ac0CgH/V+RT4d7qEQ3WZ+epZzMwzpgAD1Ibg Message-ID: <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> <1331797918.13956.27.camel@dagon.hellion.org.uk> In-Reply-To: <1331797918.13956.27.camel@dagon.hellion.org.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Ian Campbell wrote: > On Wed, 2012-03-14 at 17:55 +0000, Dave Scott wrote: > > I've been busy recently moving all the domain management parts of > xapi > > into a separate daemon, which later can be libxl'ed up. For testing > > (and for fun) I've made it understand some of xm/xl config file > syntax eg > > Interesting. Pure ocaml I presume? Yep. > > [root@st20 ~]# xn export-metadata-xm win7 win7.xm > > xn? We're going to run out of letters soon ;-) :-) > Do you handle import as well as export? One of the more interesting use > cases (I think) is handling folks who want to migrate from an xm/xl > based setup to a xapi setup (e.g. by installing Kronos on their > existing > Debian system). That's was the primary aim of the proposed project. IIRC it can import simple things, but it's quite incomplete. If the goal is to migrate from an xm/xl setup to xapi then it probably makes more sense to use the existing (and by definition correct) xl config parser and then talk the XenAPI directly. Or emit a xapi "metadata export". One of the interesting areas will be storage... > > [root@st20 ~]# cat win7.xm > > name='win7' > > builder='hvmloader' > > boot='dc' > > vcpus=1 > > memory=2048 > > disk=[ 'sm:7af570d8-f8c5-4103-ac1d-969fe28bfc11,hda,w', 'sm:137c8a61- > 113c-ab46-20fa-5c0574eaff77,hdb:cdrom,r' ] > > Half-assed wondering -- I wonder if sm: (or script=sm or similar) > support could work in xl... Yeah I've been wondering that too. As well as tidying up the domain handling code in xapi I've also been trying to generate docs for the xapi <-> storage interface (aka "SMAPI"). The current version is here: http://dave.recoil.org/xen/storage.html I'd also like to make the current storage plugins run standalone (currently they require xapi to be running). If we did that then we could potentially add support for XCP storage types directly into libxl (or the hotplug scripts). As well as generate docs for the SMAPI I can also generate python skeleton code, to make it easier to write storage plugins. A custom one of these might make it easier to migrate from xm/xl to xapi too, by leaving the disks where they are, rather than moving them into a regular SR. > > > vif=[ ] > > pci=[ ] > > pci_msitranslate=1 > > pci_power_mgmt=0 > > # transient=true > > > > Another goal of the refactoring is to allow xapi to co-exist with > domains > > created by someone else (e.g. xl/libxl). This should allow a > migration to > > be done piecemeal, one VM at a time on the same host. > > The brainstoming list below includes "make xapi use libxl". Is this (or > a subset of this) the sort of thing which could be done by a GSoC > student? I think a subset could probably be done in the GSoC timeframe. Before the summer starts I should have merged my refactoring into the xapi mainline. A student could then fire up the ocaml libxl bindings (they might need a bit of tweaking here or there) and then start patching things through. All the critical libxc code is now called (indirectly) via a single module: https://github.com/djs55/xen-api/blob/cooper/ocaml/xenops/xenops_server_xen.ml If that were made to use libxl then the job would be basically done. All that would be left would be little things like statistics gathering. > > I suppose it is only fair that I offer to be co-/backup-mentor to a > main > mentor from the xapi side of things for such a project... Great :-) Cheers, Dave > > Ian. > > > > > > Cheers, > > Dave > > > > > > > > Ian. > > > > > > > TOOLS > > > > ----- > > > > - pv grub2 > > > > - xapi support in libvirt > > > > - make xapi use libxl > > > > - compile xapi on ARM > > > > - OpenXenManager > > > > - driver domains > > > > - PV dbus > > > > - HA daemon for Remus > > > > - HA daemon for XCP > > > > > > > > PERF > > > > ---- > > > > - Oprofile > > > > - Linux perf tools in guest > > > > > > > > HYPERVISOR > > > > ---------- > > > > - insmod Xen > > > > - event channel limits > > > > - NUMA > > > > > > > > MEMORY > > > > ------ > > > > - disk based memory sharing > > > > - memory scanner > > > > - paging replacing PoD > > > > - VM Fork > > > > - Copy on read (past VDI boot) > > > > > > > > > > > > IO > > > > -- > > > > - PV OpenGL/Gallium > > > > - PV USB > > > > - PV USB3 > > > > - PV SCSI > > > > - PVFB in Xorg > > > > - Infiniband > > > > > > > > > > > > STORAGE > > > > ------- > > > > - gluster/ceph plugins > > > > > > > > > > > > QEMU > > > > ---- > > > > - BSD libc > > > > - upstream QEMU stubdoms > > > > > > > > > > > > TESTS > > > > ----- > > > > - better web reporting > > > > - more tests > > > > - upstream linux > > > > > > > > > > > > DISTROS > > > > ------- > > > > - packaging stubdoms > > > > - xen on centos6 > > > > - driver domains > > > > - figure out the VM format issue > > > > - XSM in distros > > > > > > > > > > > > > > > > _______________________________________________ > > > > Xen-devel mailing list > > > > Xen-devel@lists.xen.org > > > > http://lists.xen.org/xen-devel > > > > > > > > > > > > _______________________________________________ > > > 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 15 10:13:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 10:13: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 1S87ga-0002sI-CS; Thu, 15 Mar 2012 10:13:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S87gY-0002ri-KE for xen-api@lists.xen.org; Thu, 15 Mar 2012 10:13:31 +0000 Received: from [85.158.138.51:49093] by server-10.bemta-3.messagelabs.com id 2D/2B-13338-9C0C16F4; Thu, 15 Mar 2012 10:13:29 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1331806408!17728871!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTI0MQ==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4863 invoked from network); 15 Mar 2012 10:13:29 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 10:13:29 -0000 X-IronPort-AV: E=Sophos;i="4.73,590,1325462400"; d="scan'208";a="11313705" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Mar 2012 10:13:28 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 15 Mar 2012 10:13:28 +0000 Message-ID: <1331806407.26979.63.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Dave Scott Date: Thu, 15 Mar 2012 10:13:27 +0000 In-Reply-To: <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> <1331797918.13956.27.camel@dagon.hellion.org.uk> <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Thu, 2012-03-15 at 10:02 +0000, Dave Scott wrote: > Ian Campbell wrote: > > On Wed, 2012-03-14 at 17:55 +0000, Dave Scott wrote: > > Do you handle import as well as export? One of the more interesting use > > cases (I think) is handling folks who want to migrate from an xm/xl > > based setup to a xapi setup (e.g. by installing Kronos on their > > existing > > Debian system). That's was the primary aim of the proposed project. > > IIRC it can import simple things, but it's quite incomplete. If the > goal is to migrate from an xm/xl setup to xapi then it probably makes > more sense to use the existing (and by definition correct) xl config > parser and then talk the XenAPI directly. That was my line of thinking. > Or emit a xapi "metadata export". Hadn't considered this one -- how well specified is that format? Another thing I'd wondered about was the ability to consume/exhume OVA (or is it OVF?) thing. > One of the interesting areas will be storage... > > > > [root@st20 ~]# cat win7.xm > > > name='win7' > > > builder='hvmloader' > > > boot='dc' > > > vcpus=1 > > > memory=2048 > > > disk=[ 'sm:7af570d8-f8c5-4103-ac1d-969fe28bfc11,hda,w', 'sm:137c8a61- > > 113c-ab46-20fa-5c0574eaff77,hdb:cdrom,r' ] > > > > Half-assed wondering -- I wonder if sm: (or script=sm or similar) > > support could work in xl... > > Yeah I've been wondering that too. As well as tidying up the domain > handling code in xapi I've also been trying to generate docs for the > xapi <-> storage interface (aka "SMAPI"). The current version is here: > > http://dave.recoil.org/xen/storage.html > > I'd also like to make the current storage plugins run standalone (currently > they require xapi to be running). If we did that then we could potentially > add support for XCP storage types directly into libxl (or the hotplug scripts). > > As well as generate docs for the SMAPI I can also generate python skeleton > code, to make it easier to write storage plugins. A custom one of these > might make it easier to migrate from xm/xl to xapi too, by leaving the > disks where they are, rather than moving them into a regular SR. That could be a good plan. Given such an SR plugin could you then do some sort of "xe vdi-move" to move a VDI from that plugin to one of the "standard" ones? > > > > > > vif=[ ] > > > pci=[ ] > > > pci_msitranslate=1 > > > pci_power_mgmt=0 > > > # transient=true > > > > > > Another goal of the refactoring is to allow xapi to co-exist with > > domains > > > created by someone else (e.g. xl/libxl). This should allow a > > migration to > > > be done piecemeal, one VM at a time on the same host. > > > > The brainstoming list below includes "make xapi use libxl". Is this (or > > a subset of this) the sort of thing which could be done by a GSoC > > student? > > I think a subset could probably be done in the GSoC timeframe. Before the > summer starts I should have merged my refactoring into the xapi mainline. > A student could then fire up the ocaml libxl bindings (they might need a bit > of tweaking here or there) and then start patching things through. All the > critical libxc code is now called (indirectly) via a single module: > > https://github.com/djs55/xen-api/blob/cooper/ocaml/xenops/xenops_server_xen.ml That's a surprisingly (in a good way) small amount of code! > If that were made to use libxl then the job would be basically done. All that > would be left would be little things like statistics gathering. > > > > > > I suppose it is only fair that I offer to be co-/backup-mentor to a > > main > > mentor from the xapi side of things for such a project... > > Great :-) Was that the sound of you offering to be (or to find a) main mentor ;-) Ian. _______________________________________________ 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 15 10:13:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 10:13: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 1S87ga-0002sI-CS; Thu, 15 Mar 2012 10:13:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S87gY-0002ri-KE for xen-api@lists.xen.org; Thu, 15 Mar 2012 10:13:31 +0000 Received: from [85.158.138.51:49093] by server-10.bemta-3.messagelabs.com id 2D/2B-13338-9C0C16F4; Thu, 15 Mar 2012 10:13:29 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1331806408!17728871!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTI0MQ==\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4863 invoked from network); 15 Mar 2012 10:13:29 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 10:13:29 -0000 X-IronPort-AV: E=Sophos;i="4.73,590,1325462400"; d="scan'208";a="11313705" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Mar 2012 10:13:28 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 15 Mar 2012 10:13:28 +0000 Message-ID: <1331806407.26979.63.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Dave Scott Date: Thu, 15 Mar 2012 10:13:27 +0000 In-Reply-To: <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> <1331797918.13956.27.camel@dagon.hellion.org.uk> <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: xen-devel , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Thu, 2012-03-15 at 10:02 +0000, Dave Scott wrote: > Ian Campbell wrote: > > On Wed, 2012-03-14 at 17:55 +0000, Dave Scott wrote: > > Do you handle import as well as export? One of the more interesting use > > cases (I think) is handling folks who want to migrate from an xm/xl > > based setup to a xapi setup (e.g. by installing Kronos on their > > existing > > Debian system). That's was the primary aim of the proposed project. > > IIRC it can import simple things, but it's quite incomplete. If the > goal is to migrate from an xm/xl setup to xapi then it probably makes > more sense to use the existing (and by definition correct) xl config > parser and then talk the XenAPI directly. That was my line of thinking. > Or emit a xapi "metadata export". Hadn't considered this one -- how well specified is that format? Another thing I'd wondered about was the ability to consume/exhume OVA (or is it OVF?) thing. > One of the interesting areas will be storage... > > > > [root@st20 ~]# cat win7.xm > > > name='win7' > > > builder='hvmloader' > > > boot='dc' > > > vcpus=1 > > > memory=2048 > > > disk=[ 'sm:7af570d8-f8c5-4103-ac1d-969fe28bfc11,hda,w', 'sm:137c8a61- > > 113c-ab46-20fa-5c0574eaff77,hdb:cdrom,r' ] > > > > Half-assed wondering -- I wonder if sm: (or script=sm or similar) > > support could work in xl... > > Yeah I've been wondering that too. As well as tidying up the domain > handling code in xapi I've also been trying to generate docs for the > xapi <-> storage interface (aka "SMAPI"). The current version is here: > > http://dave.recoil.org/xen/storage.html > > I'd also like to make the current storage plugins run standalone (currently > they require xapi to be running). If we did that then we could potentially > add support for XCP storage types directly into libxl (or the hotplug scripts). > > As well as generate docs for the SMAPI I can also generate python skeleton > code, to make it easier to write storage plugins. A custom one of these > might make it easier to migrate from xm/xl to xapi too, by leaving the > disks where they are, rather than moving them into a regular SR. That could be a good plan. Given such an SR plugin could you then do some sort of "xe vdi-move" to move a VDI from that plugin to one of the "standard" ones? > > > > > > vif=[ ] > > > pci=[ ] > > > pci_msitranslate=1 > > > pci_power_mgmt=0 > > > # transient=true > > > > > > Another goal of the refactoring is to allow xapi to co-exist with > > domains > > > created by someone else (e.g. xl/libxl). This should allow a > > migration to > > > be done piecemeal, one VM at a time on the same host. > > > > The brainstoming list below includes "make xapi use libxl". Is this (or > > a subset of this) the sort of thing which could be done by a GSoC > > student? > > I think a subset could probably be done in the GSoC timeframe. Before the > summer starts I should have merged my refactoring into the xapi mainline. > A student could then fire up the ocaml libxl bindings (they might need a bit > of tweaking here or there) and then start patching things through. All the > critical libxc code is now called (indirectly) via a single module: > > https://github.com/djs55/xen-api/blob/cooper/ocaml/xenops/xenops_server_xen.ml That's a surprisingly (in a good way) small amount of code! > If that were made to use libxl then the job would be basically done. All that > would be left would be little things like statistics gathering. > > > > > > I suppose it is only fair that I offer to be co-/backup-mentor to a > > main > > mentor from the xapi side of things for such a project... > > Great :-) Was that the sound of you offering to be (or to find a) main mentor ;-) Ian. _______________________________________________ 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 15 15:01:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 15:01: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 1S8CBS-0006ZH-Rs; Thu, 15 Mar 2012 15:01:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8CBR-0006Z7-Tw for xen-api@lists.xen.org; Thu, 15 Mar 2012 15:01:42 +0000 Received: from [193.109.254.147:7180] by server-2.bemta-14.messagelabs.com id 5B/85-11301-554026F4; Thu, 15 Mar 2012 15:01:41 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1331823700!692085!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTI0MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24857 invoked from network); 15 Mar 2012 15:01:40 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 15:01:40 -0000 X-IronPort-AV: E=Sophos;i="4.73,591,1325462400"; d="scan'208";a="11327116" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Mar 2012 15:01:40 +0000 Received: from kaball.uk.xensource.com (10.80.2.59) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 15 Mar 2012 15:01:40 +0000 Date: Thu, 15 Mar 2012 15:11:03 +0000 From: Stefano Stabellini X-X-Sender: sstabellini@kaball-desktop To: Dave Scott In-Reply-To: <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> Message-ID: References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> <1331797918.13956.27.camel@dagon.hellion.org.uk> <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Cc: xen-devel , Ian Campbell , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Thu, 15 Mar 2012, Dave Scott wrote: > > Do you handle import as well as export? One of the more interesting use > > cases (I think) is handling folks who want to migrate from an xm/xl > > based setup to a xapi setup (e.g. by installing Kronos on their > > existing > > Debian system). That's was the primary aim of the proposed project. > > IIRC it can import simple things, but it's quite incomplete. If the > goal is to migrate from an xm/xl setup to xapi then it probably makes > more sense to use the existing (and by definition correct) xl config > parser and then talk the XenAPI directly. Or emit a xapi "metadata export". Maybe we could interface XAPI with xl via JSON? We were considering a machine readable input/output system for xl anyway... This way you could reuse all the existing code in xl as well as libxl and have XAPI being a drop in addon on top of xl. At that point xn could be the glue between xl and XAPI via JSON and XenAPI. > I'd also like to make the current storage plugins run standalone (currently > they require xapi to be running). If we did that then we could potentially > add support for XCP storage types directly into libxl (or the hotplug scripts). > > As well as generate docs for the SMAPI I can also generate python skeleton > code, to make it easier to write storage plugins. A custom one of these > might make it easier to migrate from xm/xl to xapi too, by leaving the > disks where they are, rather than moving them into a regular SR. That would certainly make a lot of sense. It would be great if the XCP storage plugins could be used from libxl, so maybe XAPI could actually use libxl to setup storage too. We are currently rewriting the interface between libxl and the hotplug scripts, introducing the concept of a xenbackend daemon that takes care of calling these scripts and setup the xenstore backend entries. Alternatively this could be another place where the SM could hook into. _______________________________________________ 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 15 15:01:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 15:01: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 1S8CBS-0006ZH-Rs; Thu, 15 Mar 2012 15:01:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8CBR-0006Z7-Tw for xen-api@lists.xen.org; Thu, 15 Mar 2012 15:01:42 +0000 Received: from [193.109.254.147:7180] by server-2.bemta-14.messagelabs.com id 5B/85-11301-554026F4; Thu, 15 Mar 2012 15:01:41 +0000 X-Env-Sender: Stefano.Stabellini@eu.citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1331823700!692085!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTI0MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24857 invoked from network); 15 Mar 2012 15:01:40 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 15:01:40 -0000 X-IronPort-AV: E=Sophos;i="4.73,591,1325462400"; d="scan'208";a="11327116" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 15 Mar 2012 15:01:40 +0000 Received: from kaball.uk.xensource.com (10.80.2.59) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Thu, 15 Mar 2012 15:01:40 +0000 Date: Thu, 15 Mar 2012 15:11:03 +0000 From: Stefano Stabellini X-X-Sender: sstabellini@kaball-desktop To: Dave Scott In-Reply-To: <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> Message-ID: References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <1331744386.23971.496.camel@zakaz.uk.xensource.com> <81A73678E76EA642801C8F2E4823AD21D7724CFA2D@LONPMAILBOX01.citrite.net> <1331797918.13956.27.camel@dagon.hellion.org.uk> <81A73678E76EA642801C8F2E4823AD21D7724CFA32@LONPMAILBOX01.citrite.net> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Cc: xen-devel , Ian Campbell , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Thu, 15 Mar 2012, Dave Scott wrote: > > Do you handle import as well as export? One of the more interesting use > > cases (I think) is handling folks who want to migrate from an xm/xl > > based setup to a xapi setup (e.g. by installing Kronos on their > > existing > > Debian system). That's was the primary aim of the proposed project. > > IIRC it can import simple things, but it's quite incomplete. If the > goal is to migrate from an xm/xl setup to xapi then it probably makes > more sense to use the existing (and by definition correct) xl config > parser and then talk the XenAPI directly. Or emit a xapi "metadata export". Maybe we could interface XAPI with xl via JSON? We were considering a machine readable input/output system for xl anyway... This way you could reuse all the existing code in xl as well as libxl and have XAPI being a drop in addon on top of xl. At that point xn could be the glue between xl and XAPI via JSON and XenAPI. > I'd also like to make the current storage plugins run standalone (currently > they require xapi to be running). If we did that then we could potentially > add support for XCP storage types directly into libxl (or the hotplug scripts). > > As well as generate docs for the SMAPI I can also generate python skeleton > code, to make it easier to write storage plugins. A custom one of these > might make it easier to migrate from xm/xl to xapi too, by leaving the > disks where they are, rather than moving them into a regular SR. That would certainly make a lot of sense. It would be great if the XCP storage plugins could be used from libxl, so maybe XAPI could actually use libxl to setup storage too. We are currently rewriting the interface between libxl and the hotplug scripts, introducing the concept of a xenbackend daemon that takes care of calling these scripts and setup the xenstore backend entries. Alternatively this could be another place where the SM could hook into. _______________________________________________ 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 15 17:35:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 17:35: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 1S8EZo-0006lV-6B; Thu, 15 Mar 2012 17:35:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8EZl-0006ko-Ur for xen-api@lists.xen.org; Thu, 15 Mar 2012 17:34:58 +0000 Received: from [193.109.254.147:33234] by server-4.bemta-14.messagelabs.com id 82/FF-08205-148226F4; Thu, 15 Mar 2012 17:34:57 +0000 X-Env-Sender: vahaxp@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1331832895!718641!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21144 invoked from network); 15 Mar 2012 17:34:56 -0000 Received: from mail-vx0-f173.google.com (HELO mail-vx0-f173.google.com) (209.85.220.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 17:34:56 -0000 Received: by vcbfl11 with SMTP id fl11so4792883vcb.32 for ; Thu, 15 Mar 2012 10:34:55 -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=Ld8KlWZHxSLMmsKg9QhKejDQxFu4kjtqS6QCLkMNyKU=; b=xxmb9dKIcjOfu3gkeEfehEi7m8PNSDmZUHB1QPBq0lutSp2AkgHmsowFYpOIaggF+e TOUHUiC+uI9GvPwj6M4xJFhoOY1BXturLdv/hoSKEbTinEYibLxoTiSeEpbmMo89qCO/ 6G9PvbGaDiMl3mLjwMVdGhNwEJLFngECL3LWqaJrrBWtWZWaq7Yay4ec9XdRmIlAUb+p mCjHDbE0Onl1X4rR8ffkLps+85ILQc1l+qoIedwdgvhHWUTPBFkU7h0DvvNfCs24Y7sT dZtkHDUiwRBQFE65aaY4bD72TlGEubOSBOuu34/6NQC2LDIgEW3k37Kia1okcE3dYmQn UOSA== MIME-Version: 1.0 Received: by 10.52.93.138 with SMTP id cu10mr5171139vdb.86.1331832894942; Thu, 15 Mar 2012 10:34:54 -0700 (PDT) Received: by 10.52.88.206 with HTTP; Thu, 15 Mar 2012 10:34:54 -0700 (PDT) Date: Thu, 15 Mar 2012 10:34:54 -0700 Message-ID: From: Vahidin Memic To: xen-api@lists.xen.org Subject: [Xen-API] XCP 1.1 AMD Bulldozer Support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0747922787767211165==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0747922787767211165== Content-Type: multipart/alternative; boundary=20cf307cfeaa9a6d1b04bb4b8265 --20cf307cfeaa9a6d1b04bb4b8265 Content-Type: text/plain; charset=ISO-8859-1 Hello, I was wondering if you have any information if the XCP 1.1 has support for the AMD Bulldozer platform. I know that the ISO image has the kernel version: 2.6.32.12-0.7.1.xs1.1.0.327.170596xen which seems to be a backbuild of a certain kernel. We know that kernel 2.6.38 and higher has support for AMD Bulldozer but I am not sure if this one does. Let me know if you can give me any insight on this. Thanks, Vaha --20cf307cfeaa9a6d1b04bb4b8265 Content-Type: text/html; charset=ISO-8859-1 Hello,

I was wondering if you have any information if the XCP 1.1 has support for the AMD Bulldozer platform. I know that the ISO image has the kernel version: 2.6.32.12-0.7.1.xs1.1.0.327.170596xen which seems to be a backbuild of a certain kernel. We know that kernel 2.6.38 and higher has support for AMD Bulldozer but I am not sure if this one does.

Let me know if you can give me any insight on this.

Thanks,

Vaha
--20cf307cfeaa9a6d1b04bb4b8265-- --===============0747922787767211165== 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 --===============0747922787767211165==-- From xen-api-bounces@lists.xen.org Thu Mar 15 17:35:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 15 Mar 2012 17:35: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 1S8EZo-0006lV-6B; Thu, 15 Mar 2012 17:35:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8EZl-0006ko-Ur for xen-api@lists.xen.org; Thu, 15 Mar 2012 17:34:58 +0000 Received: from [193.109.254.147:33234] by server-4.bemta-14.messagelabs.com id 82/FF-08205-148226F4; Thu, 15 Mar 2012 17:34:57 +0000 X-Env-Sender: vahaxp@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1331832895!718641!1 X-Originating-IP: [209.85.220.173] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21144 invoked from network); 15 Mar 2012 17:34:56 -0000 Received: from mail-vx0-f173.google.com (HELO mail-vx0-f173.google.com) (209.85.220.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Mar 2012 17:34:56 -0000 Received: by vcbfl11 with SMTP id fl11so4792883vcb.32 for ; Thu, 15 Mar 2012 10:34:55 -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=Ld8KlWZHxSLMmsKg9QhKejDQxFu4kjtqS6QCLkMNyKU=; b=xxmb9dKIcjOfu3gkeEfehEi7m8PNSDmZUHB1QPBq0lutSp2AkgHmsowFYpOIaggF+e TOUHUiC+uI9GvPwj6M4xJFhoOY1BXturLdv/hoSKEbTinEYibLxoTiSeEpbmMo89qCO/ 6G9PvbGaDiMl3mLjwMVdGhNwEJLFngECL3LWqaJrrBWtWZWaq7Yay4ec9XdRmIlAUb+p mCjHDbE0Onl1X4rR8ffkLps+85ILQc1l+qoIedwdgvhHWUTPBFkU7h0DvvNfCs24Y7sT dZtkHDUiwRBQFE65aaY4bD72TlGEubOSBOuu34/6NQC2LDIgEW3k37Kia1okcE3dYmQn UOSA== MIME-Version: 1.0 Received: by 10.52.93.138 with SMTP id cu10mr5171139vdb.86.1331832894942; Thu, 15 Mar 2012 10:34:54 -0700 (PDT) Received: by 10.52.88.206 with HTTP; Thu, 15 Mar 2012 10:34:54 -0700 (PDT) Date: Thu, 15 Mar 2012 10:34:54 -0700 Message-ID: From: Vahidin Memic To: xen-api@lists.xen.org Subject: [Xen-API] XCP 1.1 AMD Bulldozer Support X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0747922787767211165==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0747922787767211165== Content-Type: multipart/alternative; boundary=20cf307cfeaa9a6d1b04bb4b8265 --20cf307cfeaa9a6d1b04bb4b8265 Content-Type: text/plain; charset=ISO-8859-1 Hello, I was wondering if you have any information if the XCP 1.1 has support for the AMD Bulldozer platform. I know that the ISO image has the kernel version: 2.6.32.12-0.7.1.xs1.1.0.327.170596xen which seems to be a backbuild of a certain kernel. We know that kernel 2.6.38 and higher has support for AMD Bulldozer but I am not sure if this one does. Let me know if you can give me any insight on this. Thanks, Vaha --20cf307cfeaa9a6d1b04bb4b8265 Content-Type: text/html; charset=ISO-8859-1 Hello,

I was wondering if you have any information if the XCP 1.1 has support for the AMD Bulldozer platform. I know that the ISO image has the kernel version: 2.6.32.12-0.7.1.xs1.1.0.327.170596xen which seems to be a backbuild of a certain kernel. We know that kernel 2.6.38 and higher has support for AMD Bulldozer but I am not sure if this one does.

Let me know if you can give me any insight on this.

Thanks,

Vaha
--20cf307cfeaa9a6d1b04bb4b8265-- --===============0747922787767211165== 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 --===============0747922787767211165==-- From xen-api-bounces@lists.xen.org Fri Mar 16 11:15:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 11:15: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 1S8V7r-0000Ow-Tr; Fri, 16 Mar 2012 11:15:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8V7q-0000Om-GK for xen-api@lists.xen.org; Fri, 16 Mar 2012 11:15:14 +0000 Received: from [85.158.143.35:62887] by server-2.bemta-4.messagelabs.com id 0F/64-17550-1C0236F4; Fri, 16 Mar 2012 11:15:13 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1331896512!6027651!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTYxNA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7177 invoked from network); 16 Mar 2012 11:15:12 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 11:15:12 -0000 X-IronPort-AV: E=Sophos;i="4.73,597,1325462400"; d="scan'208";a="11344902" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Mar 2012 11:15:11 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 16 Mar 2012 11:15:11 +0000 Message-ID: <1331896510.26979.208.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Gustavo Henrique de Brito Andrade Date: Fri, 16 Mar 2012 11:15:10 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] [Xen-devel] [XCP]xe host-cpu-param-get param-name=utilisation metric? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 XCP stuff is best discussed on xen-api@lists.xen.org rather than here -- that's where most of the XCP/xapi developers hang out. CCing that list and BCCing xen-devel@. Ian. On Fri, 2012-03-16 at 11:07 +0000, Gustavo Henrique de Brito Andrade wrote: > Hello, > > I'm using the command "xe host-cpu-param-get param-name=utilisation" > metric to get the Host Cpu utilization. But I cant find any info > about what metric is used. > As an output of this I got for example: > > > 0,005 > 0,002 > 0,002 > 0 > 0 > 0 > 0 > 0 > > > Is this a % of utilization? And if this is %, what means 5% of cpu > usage? > ps: I have 8 cores. > > > Thanks. > > > Gustavo _______________________________________________ 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 16 11:15:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 11:15: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 1S8V7r-0000Ow-Tr; Fri, 16 Mar 2012 11:15:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8V7q-0000Om-GK for xen-api@lists.xen.org; Fri, 16 Mar 2012 11:15:14 +0000 Received: from [85.158.143.35:62887] by server-2.bemta-4.messagelabs.com id 0F/64-17550-1C0236F4; Fri, 16 Mar 2012 11:15:13 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1331896512!6027651!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA4OTYxNA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7177 invoked from network); 16 Mar 2012 11:15:12 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 11:15:12 -0000 X-IronPort-AV: E=Sophos;i="4.73,597,1325462400"; d="scan'208";a="11344902" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 16 Mar 2012 11:15:11 +0000 Received: from [10.80.2.42] (10.80.2.42) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 16 Mar 2012 11:15:11 +0000 Message-ID: <1331896510.26979.208.camel@zakaz.uk.xensource.com> From: Ian Campbell To: Gustavo Henrique de Brito Andrade Date: Fri, 16 Mar 2012 11:15:10 +0000 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] [Xen-devel] [XCP]xe host-cpu-param-get param-name=utilisation metric? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 XCP stuff is best discussed on xen-api@lists.xen.org rather than here -- that's where most of the XCP/xapi developers hang out. CCing that list and BCCing xen-devel@. Ian. On Fri, 2012-03-16 at 11:07 +0000, Gustavo Henrique de Brito Andrade wrote: > Hello, > > I'm using the command "xe host-cpu-param-get param-name=utilisation" > metric to get the Host Cpu utilization. But I cant find any info > about what metric is used. > As an output of this I got for example: > > > 0,005 > 0,002 > 0,002 > 0 > 0 > 0 > 0 > 0 > > > Is this a % of utilization? And if this is %, what means 5% of cpu > usage? > ps: I have 8 cores. > > > Thanks. > > > Gustavo _______________________________________________ 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 16 13:00:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 13:00:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8WlD-0005Iq-TZ; Fri, 16 Mar 2012 12:59:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8WlD-0005Il-FR for xen-api@lists.xen.org; Fri, 16 Mar 2012 12:59:59 +0000 Received: from [85.158.138.51:14330] by server-1.bemta-3.messagelabs.com id 2E/3E-04539-E49336F4; Fri, 16 Mar 2012 12:59:58 +0000 X-Env-Sender: p.pridt@chello.at X-Msg-Ref: server-14.tower-174.messagelabs.com!1331902797!17780170!1 X-Originating-IP: [62.179.121.33] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA2Mi4xNzkuMTIxLjMzID0+IDQxNTIw\n,sa_preprocessor: QmFkIElQOiA2Mi4xNzkuMTIxLjMzID0+IDQxNTIw\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28377 invoked from network); 16 Mar 2012 12:59:58 -0000 Received: from fep13.mx.upcmail.net (HELO fep13.mx.upcmail.net) (62.179.121.33) by server-14.tower-174.messagelabs.com with SMTP; 16 Mar 2012 12:59:58 -0000 Received: from edge04.upcmail.net ([192.168.13.239]) by viefep13-int.chello.at (InterMail vM.8.01.05.04 201-2260-151-105-20111014) with ESMTP id <20120316125957.JMOZ3333.viefep13-int.chello.at@edge04.upcmail.net> for ; Fri, 16 Mar 2012 13:59:57 +0100 Received: from [192.168.235.110] ([62.178.35.61]) by edge04.upcmail.net with edge id mCzx1i00Q1K8qS604CzxgH; Fri, 16 Mar 2012 13:59:57 +0100 X-SourceIP: 62.178.35.61 X-Authenticated-Sender: compudoc Message-ID: <4F633941.8040307@chello.at> Date: Fri, 16 Mar 2012 13:59:45 +0100 From: Paul Pridt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Debian Local Storage/CD Sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, Currently I am in the process of evaluating Debian Wheezy and xcp-xapi, since the performance of both XCP 1.5 and Citrix Xenserver is very poor, compared to the "old" xm stack. In Citrix Xenserver and in XCP 1.5 there are 2 SRs for local storage and cd, appearantly built by udev. It seems that the drivers are there in Debian, since I found them in /usr/lib/xcp/sm as part of the xcp-storage-managers package. There are, however, no udev rules. Whey I try to create the SR, I get the following messages: The SR could not be connected because the driver was not recognised. driver: udev Has somebody managed to create these SRs? Paul _______________________________________________ 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 16 13:00:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 13:00:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8WlD-0005Iq-TZ; Fri, 16 Mar 2012 12:59:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8WlD-0005Il-FR for xen-api@lists.xen.org; Fri, 16 Mar 2012 12:59:59 +0000 Received: from [85.158.138.51:14330] by server-1.bemta-3.messagelabs.com id 2E/3E-04539-E49336F4; Fri, 16 Mar 2012 12:59:58 +0000 X-Env-Sender: p.pridt@chello.at X-Msg-Ref: server-14.tower-174.messagelabs.com!1331902797!17780170!1 X-Originating-IP: [62.179.121.33] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiA2Mi4xNzkuMTIxLjMzID0+IDQxNTIw\n,sa_preprocessor: QmFkIElQOiA2Mi4xNzkuMTIxLjMzID0+IDQxNTIw\n X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28377 invoked from network); 16 Mar 2012 12:59:58 -0000 Received: from fep13.mx.upcmail.net (HELO fep13.mx.upcmail.net) (62.179.121.33) by server-14.tower-174.messagelabs.com with SMTP; 16 Mar 2012 12:59:58 -0000 Received: from edge04.upcmail.net ([192.168.13.239]) by viefep13-int.chello.at (InterMail vM.8.01.05.04 201-2260-151-105-20111014) with ESMTP id <20120316125957.JMOZ3333.viefep13-int.chello.at@edge04.upcmail.net> for ; Fri, 16 Mar 2012 13:59:57 +0100 Received: from [192.168.235.110] ([62.178.35.61]) by edge04.upcmail.net with edge id mCzx1i00Q1K8qS604CzxgH; Fri, 16 Mar 2012 13:59:57 +0100 X-SourceIP: 62.178.35.61 X-Authenticated-Sender: compudoc Message-ID: <4F633941.8040307@chello.at> Date: Fri, 16 Mar 2012 13:59:45 +0100 From: Paul Pridt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Debian Local Storage/CD Sr X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, Currently I am in the process of evaluating Debian Wheezy and xcp-xapi, since the performance of both XCP 1.5 and Citrix Xenserver is very poor, compared to the "old" xm stack. In Citrix Xenserver and in XCP 1.5 there are 2 SRs for local storage and cd, appearantly built by udev. It seems that the drivers are there in Debian, since I found them in /usr/lib/xcp/sm as part of the xcp-storage-managers package. There are, however, no udev rules. Whey I try to create the SR, I get the following messages: The SR could not be connected because the driver was not recognised. driver: udev Has somebody managed to create these SRs? Paul _______________________________________________ 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 16 14:22:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 14:22:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8Y2u-0007ib-Aw; Fri, 16 Mar 2012 14:22:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8Y2t-0007iV-Px for xen-api@lists.xen.org; Fri, 16 Mar 2012 14:22:19 +0000 Received: from [85.158.143.99:47236] by server-3.bemta-4.messagelabs.com id A1/E5-05853-B9C436F4; Fri, 16 Mar 2012 14:22:19 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-9.tower-216.messagelabs.com!1331907738!19538372!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0MTI1NzM=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 499 invoked from network); 16 Mar 2012 14:22:18 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-9.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Mar 2012 14:22:18 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 57D062AA7; Fri, 16 Mar 2012 16:22:17 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 88F66200F0; Fri, 16 Mar 2012 16:22:15 +0200 (EET) Date: Fri, 16 Mar 2012 16:22:15 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Gustavo Henrique de Brito Andrade Message-ID: <20120316142215.GH12984@reaktio.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: xen-api@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [Xen-API] [Xen-devel] [XCP]xe host-cpu-param-get param-name=utilisation metric? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Fri, Mar 16, 2012 at 08:07:48AM -0300, Gustavo Henrique de Brito Andrade wrote: > Hello, > Hello, > I'm using the command "xe host-cpu-param-get param-name=utilisation" > metric to get the Host Cpu utilization. But I cant find any info about > what metric is used. > As an output of this I got for example: > > 0,005 0,002 0,002 0 0 0 0 0 > > Is this a % of utilization? And if this is %, what means 5% of cpu usage? > ps: I have 8 cores. > Thanks. > Gustavo Added xen-api mailinglist to CC list.. -- Pasi _______________________________________________ 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 16 14:22:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 14:22:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8Y2u-0007ib-Aw; Fri, 16 Mar 2012 14:22:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8Y2t-0007iV-Px for xen-api@lists.xen.org; Fri, 16 Mar 2012 14:22:19 +0000 Received: from [85.158.143.99:47236] by server-3.bemta-4.messagelabs.com id A1/E5-05853-B9C436F4; Fri, 16 Mar 2012 14:22:19 +0000 X-Env-Sender: pasik@iki.fi X-Msg-Ref: server-9.tower-216.messagelabs.com!1331907738!19538372!1 X-Originating-IP: [192.89.123.25] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0MTI1NzM=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 499 invoked from network); 16 Mar 2012 14:22:18 -0000 Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by server-9.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Mar 2012 14:22:18 -0000 X-Originating-Ip: [194.89.68.22] Received: from ydin.reaktio.net (reaktio.net [194.89.68.22]) by smtp.tele.fi (Postfix) with ESMTP id 57D062AA7; Fri, 16 Mar 2012 16:22:17 +0200 (EET) Received: by ydin.reaktio.net (Postfix, from userid 1001) id 88F66200F0; Fri, 16 Mar 2012 16:22:15 +0200 (EET) Date: Fri, 16 Mar 2012 16:22:15 +0200 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= To: Gustavo Henrique de Brito Andrade Message-ID: <20120316142215.GH12984@reaktio.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: xen-api@lists.xen.org, xen-devel@lists.xen.org Subject: Re: [Xen-API] [Xen-devel] [XCP]xe host-cpu-param-get param-name=utilisation metric? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Fri, Mar 16, 2012 at 08:07:48AM -0300, Gustavo Henrique de Brito Andrade wrote: > Hello, > Hello, > I'm using the command "xe host-cpu-param-get param-name=utilisation" > metric to get the Host Cpu utilization. But I cant find any info about > what metric is used. > As an output of this I got for example: > > 0,005 0,002 0,002 0 0 0 0 0 > > Is this a % of utilization? And if this is %, what means 5% of cpu usage? > ps: I have 8 cores. > Thanks. > Gustavo Added xen-api mailinglist to CC list.. -- Pasi _______________________________________________ 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 16 15:36:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB2-0002ie-SJ; Fri, 16 Mar 2012 15:34:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S79M8-0003hi-Qq for xen-api@lists.xen.org; Mon, 12 Mar 2012 17:48:25 +0000 Received: from [85.158.143.35:53244] by server-1.bemta-4.messagelabs.com id 2F/65-20925-7E63E5F4; Mon, 12 Mar 2012 17:48:23 +0000 X-Env-Sender: raistlin@linux.it X-Msg-Ref: server-15.tower-21.messagelabs.com!1331574501!13433193!1 X-Originating-IP: [193.205.80.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5697 invoked from network); 12 Mar 2012 17:48:21 -0000 Received: from ms01.sssup.it (HELO sssup.it) (193.205.80.99) by server-15.tower-21.messagelabs.com with SMTP; 12 Mar 2012 17:48:21 -0000 Received: from [62.94.181.47] (account d.faggioli@sssup.it HELO [192.168.0.40]) by sssup.it (CommuniGate Pro SMTP 5.3.14) with ESMTPSA id 76274977; Mon, 12 Mar 2012 18:48:21 +0100 Message-ID: <1331574484.8995.10.camel@Solace> From: Dario Faggioli To: Konrad Rzeszutek Wilk Date: Mon, 12 Mar 2012 18:48:04 +0100 In-Reply-To: <20120312170012.GI5369@phenom.dumpdata.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <20120312170012.GI5369@phenom.dumpdata.com> X-Mailer: Evolution 3.2.2-1 Mime-Version: 1.0 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Andre Przywara , xen-devel , Ian Campbell , xen-api@lists.xen.org Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0127235435436826634==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0127235435436826634== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-nIKKP1ZXXwgO2c0Gyrt/" --=-nIKKP1ZXXwgO2c0Gyrt/ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2012-03-12 at 13:00 -0400, Konrad Rzeszutek Wilk wrote: > > HYPERVISOR > > ---------- > > - insmod Xen > > - event channel limits > > - NUMA >=20 > Yeah, we need that. > I'm looking into some aspects of this. Basically, I'm (trying to? :-D) putting some NUMA-aware VM placement logic in xl, basing the decision on how much free memory we have in each node. I'm also trying to have a meaningful set of benchmarks to better understand the performance implications of a sub-optimal placement. I'm hoping to have the implementation of this (memory-wise only for now) placemen logic soon, and I have a quite hard deadline for it placed at the end of the month, so... :-) As usual, any comment and ideas are more than welcome. > I think there were some patches posted for that.. whatever > happend to them? >=20 I've searched the list and the web for things like that and didn't find anything, but that could of course be my fault. Currently, my reference is what xm/xend does in order to deply VMs on the various nodes... I really hope the final result will look better than that, but that's enough for the first step. Finally, I'm not yet sure if there will be something suitable for GsoC here, but again I'm open to discuss any idea! :-) Regards, Dario --=20 <> (Raistlin Majere) ------------------------------------------------------------------- Dario Faggioli, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) PhD Candidate, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy) --=-nIKKP1ZXXwgO2c0Gyrt/ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAk9eNtUACgkQk4XaBE3IOsTKHgCgpo3eelK/0GeQTcMGOGUQ4dGx 6wwAoJo8XwsvXtLWpF8hq5XDIOHxNLfs =ewQg -----END PGP SIGNATURE----- --=-nIKKP1ZXXwgO2c0Gyrt/-- --===============0127235435436826634== 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 --===============0127235435436826634==-- From xen-api-bounces@lists.xen.org Fri Mar 16 15:36:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB2-0002ie-SJ; Fri, 16 Mar 2012 15:34:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S79M8-0003hi-Qq for xen-api@lists.xen.org; Mon, 12 Mar 2012 17:48:25 +0000 Received: from [85.158.143.35:53244] by server-1.bemta-4.messagelabs.com id 2F/65-20925-7E63E5F4; Mon, 12 Mar 2012 17:48:23 +0000 X-Env-Sender: raistlin@linux.it X-Msg-Ref: server-15.tower-21.messagelabs.com!1331574501!13433193!1 X-Originating-IP: [193.205.80.99] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5697 invoked from network); 12 Mar 2012 17:48:21 -0000 Received: from ms01.sssup.it (HELO sssup.it) (193.205.80.99) by server-15.tower-21.messagelabs.com with SMTP; 12 Mar 2012 17:48:21 -0000 Received: from [62.94.181.47] (account d.faggioli@sssup.it HELO [192.168.0.40]) by sssup.it (CommuniGate Pro SMTP 5.3.14) with ESMTPSA id 76274977; Mon, 12 Mar 2012 18:48:21 +0100 Message-ID: <1331574484.8995.10.camel@Solace> From: Dario Faggioli To: Konrad Rzeszutek Wilk Date: Mon, 12 Mar 2012 18:48:04 +0100 In-Reply-To: <20120312170012.GI5369@phenom.dumpdata.com> References: <1330534437.4270.143.camel@zakaz.uk.xensource.com> <20120312170012.GI5369@phenom.dumpdata.com> X-Mailer: Evolution 3.2.2-1 Mime-Version: 1.0 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Andre Przywara , xen-devel , Ian Campbell , xen-api@lists.xen.org Subject: Re: [Xen-API] [Xen-devel] GSoC 2012 project brainstorming X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0127235435436826634==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0127235435436826634== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-nIKKP1ZXXwgO2c0Gyrt/" --=-nIKKP1ZXXwgO2c0Gyrt/ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2012-03-12 at 13:00 -0400, Konrad Rzeszutek Wilk wrote: > > HYPERVISOR > > ---------- > > - insmod Xen > > - event channel limits > > - NUMA >=20 > Yeah, we need that. > I'm looking into some aspects of this. Basically, I'm (trying to? :-D) putting some NUMA-aware VM placement logic in xl, basing the decision on how much free memory we have in each node. I'm also trying to have a meaningful set of benchmarks to better understand the performance implications of a sub-optimal placement. I'm hoping to have the implementation of this (memory-wise only for now) placemen logic soon, and I have a quite hard deadline for it placed at the end of the month, so... :-) As usual, any comment and ideas are more than welcome. > I think there were some patches posted for that.. whatever > happend to them? >=20 I've searched the list and the web for things like that and didn't find anything, but that could of course be my fault. Currently, my reference is what xm/xend does in order to deply VMs on the various nodes... I really hope the final result will look better than that, but that's enough for the first step. Finally, I'm not yet sure if there will be something suitable for GsoC here, but again I'm open to discuss any idea! :-) Regards, Dario --=20 <> (Raistlin Majere) ------------------------------------------------------------------- Dario Faggioli, http://retis.sssup.it/people/faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) PhD Candidate, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy) --=-nIKKP1ZXXwgO2c0Gyrt/ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEABECAAYFAk9eNtUACgkQk4XaBE3IOsTKHgCgpo3eelK/0GeQTcMGOGUQ4dGx 6wwAoJo8XwsvXtLWpF8hq5XDIOHxNLfs =ewQg -----END PGP SIGNATURE----- --=-nIKKP1ZXXwgO2c0Gyrt/-- --===============0127235435436826634== 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 --===============0127235435436826634==-- From xen-api-bounces@lists.xen.org Fri Mar 16 15:36:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB4-0002jc-Jk; Fri, 16 Mar 2012 15:34:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7NrN-00056e-UM for xen-api@lists.xen.org; Tue, 13 Mar 2012 09:17:38 +0000 Received: from [85.158.139.83:55606] by server-6.bemta-5.messagelabs.com id AB/3F-13222-1B01F5F4; Tue, 13 Mar 2012 09:17:37 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-16.tower-182.messagelabs.com!1331630255!11761621!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25189 invoked from network); 13 Mar 2012 09:17:36 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-16.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2012 09:17:36 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 0070CFE436; Tue, 13 Mar 2012 09:18:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=V1hKYl+3M l9u9rZU7O+WSdaSwso=; b=magUYg+G3X2RuXdIBKEKnhNOaiUN2FBBd3+pTxRHS 4mwL6HvselgMKPBqcR5he0ICTFBoipO+7sEwcDx5+K3FjbSg6m/zJsc+ifEUQmbP bZ1drA9hfOhp+70wWXy/7uIlVvC6W6JKqugRvDcDfunyB7+MmhlNMwPvT6PSYx51 Dw= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=QzV fkaPP9PdOlyEeLcqp1/Z59XZwN1oyy8UYdTrTUn2DfyM1AYBuleddk3NNpry0nAp c2Sjh8mOCKZvw1re2kzPsuqpv2jpsh//MM4tOV3ymoiCVhUfQJXXdonxnLQ5l68m UJjhyCCy2X4DiYQUSi+gM6QzPYfdA3MdGubSDfEk= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id DF3B9FE1D0; Tue, 13 Mar 2012 09:18:49 +0000 (UTC) Message-ID: <4F5F10AA.1040206@goirand.fr> Date: Tue, 13 Mar 2012 17:17:30 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: Renuka Apte References: In-Reply-To: X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Mike McClurg , "openstack@lists.launchpad.net" , Salvatore Orlando , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack-devel] [Openstack] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On 03/13/2012 02:32 PM, Renuka Apte wrote: > You need to install the xenapi plugins: > > If you are using devstack (https://github.com/openstack-dev/devstack), the > code below from build_domU.sh does this for you. I'm part of the debian Openstack packaging team, and I worked with Mike on packaging XCP in Debian (project Kronos). I do not wish to try devstack, I wish to fix the Debian packaging! > # Checkout nova > if [ ! -d $TOP_DIR/nova ]; then > env GIT_SSL_NO_VERIFY=true git clone $NOVA_REPO > cd $TOP_DIR/nova > git checkout $NOVA_BRANCH > fi > > # Install plugins > cp -pr $TOP_DIR/nova/plugins/xenserver/xenapi/etc/xapi.d /etc/ > chmod a+x /etc/xapi.d/plugins/* > yum --enablerepo=base install -y parted > mkdir -p /boot/guest I'm not using CentOS, but Debian (project Kronos). And in there, you just need to do: apt-get install nova-xcp-plugins nova-xcp-network which installs the above in the correct folders (which are *NOT* the same as for CentOS). I'd love to have a bit of help from Citrix to test all this by the way. Thomas _______________________________________________ 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 16 15:36:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB4-0002jc-Jk; Fri, 16 Mar 2012 15:34:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7NrN-00056e-UM for xen-api@lists.xen.org; Tue, 13 Mar 2012 09:17:38 +0000 Received: from [85.158.139.83:55606] by server-6.bemta-5.messagelabs.com id AB/3F-13222-1B01F5F4; Tue, 13 Mar 2012 09:17:37 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-16.tower-182.messagelabs.com!1331630255!11761621!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25189 invoked from network); 13 Mar 2012 09:17:36 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-16.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2012 09:17:36 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 0070CFE436; Tue, 13 Mar 2012 09:18:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=V1hKYl+3M l9u9rZU7O+WSdaSwso=; b=magUYg+G3X2RuXdIBKEKnhNOaiUN2FBBd3+pTxRHS 4mwL6HvselgMKPBqcR5he0ICTFBoipO+7sEwcDx5+K3FjbSg6m/zJsc+ifEUQmbP bZ1drA9hfOhp+70wWXy/7uIlVvC6W6JKqugRvDcDfunyB7+MmhlNMwPvT6PSYx51 Dw= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=QzV fkaPP9PdOlyEeLcqp1/Z59XZwN1oyy8UYdTrTUn2DfyM1AYBuleddk3NNpry0nAp c2Sjh8mOCKZvw1re2kzPsuqpv2jpsh//MM4tOV3ymoiCVhUfQJXXdonxnLQ5l68m UJjhyCCy2X4DiYQUSi+gM6QzPYfdA3MdGubSDfEk= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id DF3B9FE1D0; Tue, 13 Mar 2012 09:18:49 +0000 (UTC) Message-ID: <4F5F10AA.1040206@goirand.fr> Date: Tue, 13 Mar 2012 17:17:30 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: Renuka Apte References: In-Reply-To: X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Mike McClurg , "openstack@lists.launchpad.net" , Salvatore Orlando , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack-devel] [Openstack] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On 03/13/2012 02:32 PM, Renuka Apte wrote: > You need to install the xenapi plugins: > > If you are using devstack (https://github.com/openstack-dev/devstack), the > code below from build_domU.sh does this for you. I'm part of the debian Openstack packaging team, and I worked with Mike on packaging XCP in Debian (project Kronos). I do not wish to try devstack, I wish to fix the Debian packaging! > # Checkout nova > if [ ! -d $TOP_DIR/nova ]; then > env GIT_SSL_NO_VERIFY=true git clone $NOVA_REPO > cd $TOP_DIR/nova > git checkout $NOVA_BRANCH > fi > > # Install plugins > cp -pr $TOP_DIR/nova/plugins/xenserver/xenapi/etc/xapi.d /etc/ > chmod a+x /etc/xapi.d/plugins/* > yum --enablerepo=base install -y parted > mkdir -p /boot/guest I'm not using CentOS, but Debian (project Kronos). And in there, you just need to do: apt-get install nova-xcp-plugins nova-xcp-network which installs the above in the correct folders (which are *NOT* the same as for CentOS). I'd love to have a bit of help from Citrix to test all this by the way. Thomas _______________________________________________ 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 16 15:36:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB3-0002iq-9A; Fri, 16 Mar 2012 15:34:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7Kfu-0000mh-EK for xen-api@lists.xen.org; Tue, 13 Mar 2012 05:53:35 +0000 Received: from [193.109.254.147:37183] by server-2.bemta-14.messagelabs.com id C9/A6-11301-DD0EE5F4; Tue, 13 Mar 2012 05:53:33 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-11.tower-27.messagelabs.com!1331618008!267015!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=1.0 required=7.0 tests=BODY_RANDOMQ X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4306 invoked from network); 13 Mar 2012 05:53:29 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2012 05:53:29 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 063BDFE0B3; Tue, 13 Mar 2012 05:54:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type; s=postfix; bh=d FZehurig8/9j9afBVUmD7nSn9o=; b=jykEV29EfNx26PyGZhvJoZhlsL+Ordrgl HxA9XuMjmxmT0CtxA3Sta/T0P0ZogdR9Jf3zS9/iFl2zzwBpIp2PhAnsitn1jndn AqGrmumBUmzAJPXZxAULo7i0OB081HQXCaPAQ1v9fgZK/iuQ3w5YOtPo2yaODEBx hUVUG7L8dk= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type; q=dns; s= postfix; b=IawxKbo594g6KZG1tx1Yclk22r6PEWhKg7GJZv4+vycIssQhLTP5B DIH9JQoDoi1yh0TWlGp2sUFFh/k9YdXZ1dWzSFtVDWOBOLJBmBjJH422nmmn0cT9 MkY3f8VoTxuqm7eRsKa3yvt5v030LrTVFqJyhOysArWH3x1fe+pjRw= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 22FFDFE06B; Tue, 13 Mar 2012 05:54:41 +0000 (UTC) Message-ID: <4F5EE0D3.6040405@goirand.fr> Date: Tue, 13 Mar 2012 13:53:23 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org, "openstack@lists.launchpad.net" , Ewan Mellor , Mike McClurg , Jon Ludlam , PKG OpenStack X-Enigmail-Version: 1.0.1 Content-Type: multipart/mixed; boundary="------------080508070801000609060802" X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Subject: [Xen-API] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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. --------------080508070801000609060802 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I am trying to setup nova-compute with a Kronos setup. Everything comes from the packages in SID (including nova-xcp-network and nova-xcp-pluggins in the dom0, which we now package in Debian). When starting nova-compute, I have a python stack dump caused by a XENAPI_PLUGIN_FAILURE. I have attached the nova-compute.log and xcp-xapi.log files showing the trace of the crash. Ewan, Mike, Jon, do you know what's going on? Also, my understanding of Quantum is that it's for Openstack + KVM, and that XCP doesn't need it, as the xcp-networkd will do the vFlows work by itself. Am I right? How does it work? BTW, I'm writing an automated script, inspired from Ghe's debostack, for setting-up a domU that would connect to XCP. I might be a good idea to run this as a Jenkins job. Once I have the above working (eg: Openstack working with Kronos), I'll share the script, so we always make sure everything works. Let me know, Cheers, Thomas Goirand (zigo) --------------080508070801000609060802 Content-Type: text/plain; name="compute.log.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="compute.log.txt" 2012-03-13 05:41:31 WARNING nova.virt.libvirt.firewall [-] Libvirt module could not be loaded. NWFilterFirewall will not work correctly. 2012-03-13 05:41:31 DEBUG nova.service [-] Full set of FLAGS: from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:402 2012-03-13 05:41:31 DEBUG nova.service [-] default_floating_pool : nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] storage_availability_zone : nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rescue_image_id : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] num_networks : 1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vc_image_name : vc_image from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_dmz_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fixed_range : 10.0.0.0/8 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] compute_topic : compute from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vsa_topic : vsa from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] glance_port : 9292 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] glance_api_servers : ['--compute-host-ip--:9292'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_listen_port : 8774 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] user_cert_subject : /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] s3_dmz : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_ram : 51200 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_sparse_copy : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_listen : 0.0.0.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cache_images : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vlan_interface : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] aws_access_key_id : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] bandwith_poll_interval : 600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_sr_base_path : /var/run/sr-mount from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_size : 256 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] host_state_interval : 120 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] virt_mkfs : ['default=mkfs.ext3 -L %(fs_label)s -F %(target)s', 'linux=mkfs.ext3 -L %(fs_label)s -F %(target)s', 'windows=mkfs.ntfs --force --fast --label %(fs_label)s %(target)s'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] enable_new_services : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] my_ip : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] live_migration_flag : VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] live_migration_retry_count : 30 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] password_length : 12 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_max_injected_files : 5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] security_group_handler : nova.network.quantum.sg.NullSecurityGroupHandler from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] public_interface : eth0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] iqn_prefix : iqn.2010-10.org.openstack from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_schedule_zone : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_disk_prefix : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logdir : /var/log/nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_volume_listen : 0.0.0.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sqlite_db : nova.sqlite from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_extension : ['nova.api.openstack.compute.contrib.standard_extensions'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] allow_resize_to_same_host : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] reclaim_instance_interval : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_device_mtu : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cert_manager : nova.cert.manager.CertManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_usb_tablet : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ipv6_backend : rfc2462 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] notification_driver : nova.notifier.no_op_notifier from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_max_limit : 1000 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] enable_instance_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] compute_api_class : nova.compute.api.API from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] remove_unused_base_images : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_port : 5672 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dns_server : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_host_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] default_access_ip_network_name : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_max_retries : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] resume_guests_state_on_host_boot : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] snapshot_image_format : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dhcp_lease_time : 120 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_listen : 0.0.0.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logfile : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] floating_ip_dns_manager : nova.network.dns_driver.DNSDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cpuinfo_xml_template : /usr/lib/python2.7/dist-packages/nova/virt/cpuinfo.xml.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_remap_vbd_dev_prefix : sd from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] injected_network_template : /usr/lib/python2.7/dist-packages/nova/virt/interfaces.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_host : debian from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] send_arp_for_ha : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_connection_concurrent : 5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] snapshot_name_template : snapshot-%08x from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_host_username : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] resize_confirm_window : 86400 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vncserver_proxyclient_address : 127.0.0.1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_connection_username : root from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_cores : 20 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] heal_instance_info_cache_interval : 60 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] debug : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_project_ca : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] routing_source_ip : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vsa_name_template : vsa-%08x from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_log_levels : ['amqplib=WARN', 'sqlalchemy=WARN', 'boto=WARN', 'suds=INFO', 'eventlet.wsgi.server=WARN'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_topic : volume from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_use_virtio_for_bridges : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dnsmasq_config_file : from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_link_prefix : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_wsdl_loc : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_name_template : volume-%08x from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] lock_path : /var/lock/nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] live_migration_uri : qemu+tcp://%s/system from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] state_path : /var/lib/nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] allow_same_net_traffic : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_manager : nova.api.manager.MetadataManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_image_cache_manager : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_vif_type : bridge from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_agent_path : usr/sbin/xe-update-networking from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] flat_network_dns : 8.8.4.4 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] remove_unused_original_minimum_age_seconds : 86400 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_vsa_instance_type : m1.small from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_config : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_stderr : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] connection_type : xenapi from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] update_dhcp_on_disassociate : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_project : openstack from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] s3_port : 3333 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] max_kernel_ramdisk_size : 16777216 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logfile_mode : 0644 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_ephemeral_format : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logging_context_format_string : %(asctime)s %(levelname)s %(name)s [%(request_id)s %(user_id)s %(project_id)s] %(instance)s%(message)s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_listen_port : 8775 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_ip : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] isolated_hosts : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_name_template : instance-%08x from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_usage_audit_period : month from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_dir : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_durable_queues : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credential_key_file : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] quota_metadata_items : 128 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logging_debug_format_suffix : from (pid=%(process)d) %(funcName)s %(pathname)s:%(lineno)d from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] stub_network : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] console_manager : nova.console.manager.ConsoleProxyManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] zombie_instance_updated_at_window : 172800 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_join_force : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rpc_backend : nova.rpc.impl_kombu from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_userid : guest from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] running_deleted_instance_poll_interval : 30 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] agent_version_timeout : 300 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_volume_extension : ['nova.api.openstack.volume.contrib.standard_extensions'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_scheme : http from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credential_rc_file : %src from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dhcp_domain : novalocal from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sql_connection : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] console_topic : console from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instances_path : /var/lib/nova/instances from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] flat_injected : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_local_volumes : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] host : debian from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_dns_domain : from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] target_port : 3260 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fixed_ip_disassociate_timeout : 600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] running_deleted_instance_action : noop from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] console_host : debian from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_remap_vbd_dev : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_max_injected_file_content_bytes : 10240 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] key_file : private/cakey.pem from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] floating_range : 4.4.4.0/24 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] reboot_timeout : 600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] multi_host : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] glance_num_retries : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] db_backend : sqlalchemy from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credentials_template : /usr/lib/python2.7/dist-packages/nova/auth/novarc.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] image_cache_manager_interval : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sql_retry_interval : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_task_poll_interval : 5.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_driver : nova.volume.driver.ISCSIDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] networks_path : /var/lib/nova/networks from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] crl_file : crl.pem from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] gateway_v6 : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] monkey_patch : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rpc_conn_pool_size : 30 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] s3_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] qemu_img : qemu-img from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sqlite_synchronous : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_host_ip : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] max_nbd_devices : 16 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] policy_file : policy.json from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] linuxnet_ovs_integration_bridge : br-int from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_force_update_capabilities : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] scheduler_topic : scheduler from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] verbose : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] flat_network_bridge : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sql_max_retries : 12 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_ovs_integration_bridge : xapi1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_instance_type : m1.small from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_listen : 0.0.0.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] firewall_driver : nova.virt.firewall.IptablesFirewallDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_type : kvm from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] periodic_interval : 60 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_deprecated_auth : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_key_suffix : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_vif_driver : nova.virt.xenapi.vif.XenAPIBridgeDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_cow_images : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_volume_listen_port : 8776 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] gateway : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] null_kernel : nokernel from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] target_host : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] flat_interface : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] force_raw_images : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_client_template : /usr/lib/python2.7/dist-packages/nova/cloudpipe/client.ovpn.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_format : [instance: %(uuid)s] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_glance_link_prefix : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dmz_cidr : 10.128.0.0/24 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_vif_driver : nova.virt.libvirt.vif.LibvirtBridgeDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rpc_response_timeout : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_xml_template : /usr/lib/python2.7/dist-packages/nova/virt/libvirt.xml.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credential_vpn_file : nova-vpn.conf from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_ext_list : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_notification_level : INFO from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] publish_errors : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] consoleauth_topic : consoleauth from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credential_cert_file : cert.pem from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] auto_assign_floating_ip : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] novncproxy_base_url : http://--compute-host-ip--:6080/vnc_auto.html from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] service_down_time : 60 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logging_exception_prefix : (%(name)s): TRACE: from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] enabled_apis : ['ec2', 'osapi_compute', 'osapi_volume', 'metadata'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_api_class : nova.volume.api.API from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_vlan_interface : vmnic0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] report_interval : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] scheduler_manager : nova.scheduler.manager.SchedulerManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_port : 8773 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_running_timeout : 60 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] monkey_patch_modules : ['nova.api.ec2.cloud:nova.notifier.api.notify_decorator', 'nova.compute.api:nova.notifier.api.notify_decorator'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rescue_kernel_id : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fixed_range_v6 : fd00::/48 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_retry_backoff : 2 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] auth_token_ttl : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_volumes : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_uri : from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_listen_port : 8773 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_scheme : http from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] keys_path : /var/lib/nova/keys from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_image_id : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] disable_process_locking : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmware_vif_driver : nova.virt.vmwareapi.vif.VMWareVlanBridgeDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] block_migration_flag : VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, VIR_MIGRATE_NON_SHARED_INC from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] live_migration_bandwidth : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cert_topic : cert from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_max_injected_file_path_bytes : 255 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_floating_ips : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] max_vcs_in_vsa : 32 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fake_call : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_publisher_id : debian from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_dns_manager : nova.network.dns_driver.DNSDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sql_idle_timeout : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] glance_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xvpvncproxy_base_url : http://127.0.0.1:6081/console from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_image : ami-11111 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] aws_secret_access_key : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] use_ipv6 : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_format : %(asctime)s %(levelname)8s [%(name)s] %(message)s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] allowed_roles : ['cloudadmin', 'itsec', 'sysadmin', 'netadmin', 'developer'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fake_network : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_port : 8775 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] force_dhcp_release : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dhcpbridge_flagfile : /etc/nova/nova-dhcpbridge.conf from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_gigabytes : 1000 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] region_list : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_vhd_coalesce_poll_interval : 5.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dhcpbridge : /usr/lib/python2.7/dist-packages/bin/nova-dhcpbridge from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_start : 1000 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_vhd_coalesce_max_attempts : 5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] running_deleted_instance_timeout : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] auth_driver : nova.auth.dbdriver.DbDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_manager : nova.network.manager.VlanManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] root_helper : sudo from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rescue_ramdisk_id : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] checksum_base_images : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] memcached_servers : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logging_default_format_string : %(asctime)s %(levelname)s %(name)s [-] %(instance)s%(message)s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_volume_ext_list : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] find_host_timeout : 30 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vsa_manager : nova.vsa.manager.VsaManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_os_type : linux from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fake_rabbit : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_date_format : %Y-%m-%d %H:%M:%S from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] timeout_nbd : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] block_device_creation_timeout : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vnc_keymap : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] rescue_timeout : 86400 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ca_path : /var/lib/nova/CA from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] policy_default_rule : default from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_login_timeout : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vncserver_listen : 127.0.0.1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_syslog : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_single_default_gateway : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] superuser_roles : ['cloudadmin'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_path : /v1.1/ from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] syslog_log_facility : LOG_USER from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_path : /services/Cloud from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] remove_unused_resized_minimum_age_seconds : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_api_retry_count : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] linuxnet_interface_driver : nova.network.linux_net.LinuxBridgeInterfaceDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_use_ssl : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_retry_interval : 1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] config_file : ['/tmp/nova-conf-k_FZuG/tmpQyjVbE.conf'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ca_file : cacert.pem from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_api_class : nova.network.api.API from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] node_availability_zone : nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_task_poll_interval : 0.5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] db_driver : nova.db from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] create_unique_mac_address_attempts : 5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] img_handlers : ['loop', 'nbd', 'guestfs'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_manager : nova.volume.manager.VolumeManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] start_guests_on_host_boot : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_generate_swap : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vlan_start : 100 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rpc_thread_pool_size : 1024 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sr_matching_filter : other-config:i18n-key=local-storage from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] l3_lib : nova.network.l3.LinuxNetL3 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] isolated_images : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vnc_enabled : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_log_instance_actions : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] api_paste_config : api-paste.ini from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] global_roles : ['cloudadmin', 'itsec'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_connection_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_virtual_host : / from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_volume_drivers : ['iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver', 'local=nova.virt.libvirt.volume.LibvirtVolumeDriver', 'fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver', 'rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver', 'sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_connection_url : https://---kronos-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_driver : nova.network.linux_net from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_instances : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] project_cert_subject : /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=project-ca-%.16s-%s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] image_service : nova.image.glance.GlanceImageService from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_inject_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] control_exchange : nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cnt_vpn_clients : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vsa_part_size_gb : 100 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_file : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] compute_manager : nova.compute.manager.ComputeManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] compute_driver : nova.virt.connection.get_connection from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_topic : network from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 AUDIT nova.service [-] Starting compute node (version 2012.1-LOCALBRANCH:LOCALREVISION) 2012-03-13 05:41:31 DEBUG nova.utils [req-1226d918-e523-402d-9821-7fd44c738e16 None None] backend from (pid=20186) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:607 2012-03-13 05:41:32 DEBUG nova.virt.xenapi.host [-] Updating host stats from (pid=20186) update_status /usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py:124 2012-03-13 05:41:32 WARNING nova.virt.xenapi_conn [-] Task [Async.host.call_plugin] OpaqueRef:71f0f3bb-3086-9a05-4313-d8a423ab9d45 status: failure ['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', ''] 2012-03-13 05:41:32 ERROR nova.virt.xenapi.host [-] The call to host_data returned an error: ['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', '']. 2012-03-13 05:41:32 CRITICAL nova [-] 'str' object does not support item assignment (nova): TRACE: Traceback (most recent call last): (nova): TRACE: File "/usr/bin/nova-compute", line 49, in (nova): TRACE: service.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 413, in wait (nova): TRACE: _launcher.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 131, in wait (nova): TRACE: service.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 166, in wait (nova): TRACE: return self._exit_event.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait (nova): TRACE: return hubs.get_hub().switch() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 177, in switch (nova): TRACE: return self.greenlet.switch() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in main (nova): TRACE: result = function(*args, **kwargs) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 101, in run_server (nova): TRACE: server.start() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 174, in start (nova): TRACE: self.manager.update_available_resource(ctxt) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2293, in update_available_resource (nova): TRACE: self.driver.update_available_resource(context, self.host) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 398, in update_available_resource (nova): TRACE: host_stats = self.get_host_stats(refresh=True) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 472, in get_host_stats (nova): TRACE: return self.host_state.get_host_stats(refresh=refresh) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 187, in host_state (nova): TRACE: self._host_state = host.HostState(self._session) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py", line 110, in __init__ (nova): TRACE: self.update_status() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py", line 137, in update_status (nova): TRACE: data["disk_total"] = total (nova): TRACE: TypeError: 'str' object does not support item assignment (nova): TRACE: --------------080508070801000609060802 Content-Type: text/plain; name="xcp-xapi.log.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xcp-xapi.log.txt" [20120313T05:41:30.668Z|debug|node4407.gplhost.com|1353 INET 127.0.0.1:80|session.login_with_password D:c8c336d594af|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.669Z| info|node4407.gplhost.com|1353 INET 127.0.0.1:80|session.login_with_password D:c8c336d594af|xapi] Session.create trackid=bf1fbbc06724826b0912a76e2f8e75ff pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.669Z|debug|node4407.gplhost.com|1353 INET 127.0.0.1:80|session.login_with_password D:c8c336d594af|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.670Z|debug|node4407.gplhost.com|1354 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:66fa8df77fb9 created by task D:c8c336d594af [20120313T05:41:30.733Z|debug|node4407.gplhost.com|1355 INET 127.0.0.1:80|session.login_with_password D:84d09b037816|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.734Z| info|node4407.gplhost.com|1355 INET 127.0.0.1:80|session.login_with_password D:84d09b037816|xapi] Session.create trackid=8ddf2b2e641ee52697e094f56c828866 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.735Z|debug|node4407.gplhost.com|1355 INET 127.0.0.1:80|session.login_with_password D:84d09b037816|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.736Z|debug|node4407.gplhost.com|1356 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:94ce61f48526 created by task D:84d09b037816 [20120313T05:41:30.800Z|debug|node4407.gplhost.com|1357 INET 127.0.0.1:80|session.login_with_password D:54ac9dfe53bc|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.801Z| info|node4407.gplhost.com|1357 INET 127.0.0.1:80|session.login_with_password D:54ac9dfe53bc|xapi] Session.create trackid=e662601de316e3f408100b6c1a388b3e pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.802Z|debug|node4407.gplhost.com|1357 INET 127.0.0.1:80|session.login_with_password D:54ac9dfe53bc|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.802Z|debug|node4407.gplhost.com|1358 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:9b45e2c22c93 created by task D:54ac9dfe53bc [20120313T05:41:30.868Z|debug|node4407.gplhost.com|1359 INET 127.0.0.1:80|session.login_with_password D:74791661f3f1|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.869Z| info|node4407.gplhost.com|1359 INET 127.0.0.1:80|session.login_with_password D:74791661f3f1|xapi] Session.create trackid=8c2a0436698aeee34c2ace5f08ddf5dd pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.869Z|debug|node4407.gplhost.com|1359 INET 127.0.0.1:80|session.login_with_password D:74791661f3f1|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.870Z|debug|node4407.gplhost.com|1360 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:fdcd22a684c4 created by task D:74791661f3f1 [20120313T05:41:30.934Z|debug|node4407.gplhost.com|1361 INET 127.0.0.1:80|session.login_with_password D:5d149033466a|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.935Z| info|node4407.gplhost.com|1361 INET 127.0.0.1:80|session.login_with_password D:5d149033466a|xapi] Session.create trackid=03010b0e2d18f2d8f7dafc8e84ebb119 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.936Z|debug|node4407.gplhost.com|1361 INET 127.0.0.1:80|session.login_with_password D:5d149033466a|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.937Z|debug|node4407.gplhost.com|1362 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:d7d20acd7029 created by task D:5d149033466a [20120313T05:41:31.468Z| info|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] spawning a new thread to handle the current task (trackid=bf1fbbc06724826b0912a76e2f8e75ff) [20120313T05:41:31.468Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|audit] Host.call_plugin host = 'ee61ea48-ad10-a478-3f7a-3bb9fd7df802 (node4407.gplhost.com)'; plugin = 'xenhost'; fn = 'host_data'; args = [ ] [20120313T05:41:31.478Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|xapi] Raised at forkhelpers.ml:181.30-76 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.478Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at xapi_plugins.ml:45.7-100 -> message_forwarding.ml:233.25-44 -> rbac.ml:229.16-23 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] Server_helpers.exec exception_handler: Got exception XENAPI_PLUGIN_FAILURE: [ non-zero exit; ; ] [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120313T05:41:31.482Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.482Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.482Z|debug|node4407.gplhost.com|1363||xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.482Z|debug|node4407.gplhost.com|1363||xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1357 INET 127.0.0.1:80||http_critical] Premature termination of connection! [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1353 INET 127.0.0.1:80||http_critical] Premature termination of connection! [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1355 INET 127.0.0.1:80||http_critical] Premature termination of connection! [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1359 INET 127.0.0.1:80||http_critical] Premature termination of connection! [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1361 INET 127.0.0.1:80||http_critical] Premature termination of connection! --------------080508070801000609060802 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 --------------080508070801000609060802-- From xen-api-bounces@lists.xen.org Fri Mar 16 15:36:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB3-0002iq-9A; Fri, 16 Mar 2012 15:34:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7Kfu-0000mh-EK for xen-api@lists.xen.org; Tue, 13 Mar 2012 05:53:35 +0000 Received: from [193.109.254.147:37183] by server-2.bemta-14.messagelabs.com id C9/A6-11301-DD0EE5F4; Tue, 13 Mar 2012 05:53:33 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-11.tower-27.messagelabs.com!1331618008!267015!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=1.0 required=7.0 tests=BODY_RANDOMQ X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4306 invoked from network); 13 Mar 2012 05:53:29 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2012 05:53:29 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 063BDFE0B3; Tue, 13 Mar 2012 05:54:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type; s=postfix; bh=d FZehurig8/9j9afBVUmD7nSn9o=; b=jykEV29EfNx26PyGZhvJoZhlsL+Ordrgl HxA9XuMjmxmT0CtxA3Sta/T0P0ZogdR9Jf3zS9/iFl2zzwBpIp2PhAnsitn1jndn AqGrmumBUmzAJPXZxAULo7i0OB081HQXCaPAQ1v9fgZK/iuQ3w5YOtPo2yaODEBx hUVUG7L8dk= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type; q=dns; s= postfix; b=IawxKbo594g6KZG1tx1Yclk22r6PEWhKg7GJZv4+vycIssQhLTP5B DIH9JQoDoi1yh0TWlGp2sUFFh/k9YdXZ1dWzSFtVDWOBOLJBmBjJH422nmmn0cT9 MkY3f8VoTxuqm7eRsKa3yvt5v030LrTVFqJyhOysArWH3x1fe+pjRw= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 22FFDFE06B; Tue, 13 Mar 2012 05:54:41 +0000 (UTC) Message-ID: <4F5EE0D3.6040405@goirand.fr> Date: Tue, 13 Mar 2012 13:53:23 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org, "openstack@lists.launchpad.net" , Ewan Mellor , Mike McClurg , Jon Ludlam , PKG OpenStack X-Enigmail-Version: 1.0.1 Content-Type: multipart/mixed; boundary="------------080508070801000609060802" X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Subject: [Xen-API] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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. --------------080508070801000609060802 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I am trying to setup nova-compute with a Kronos setup. Everything comes from the packages in SID (including nova-xcp-network and nova-xcp-pluggins in the dom0, which we now package in Debian). When starting nova-compute, I have a python stack dump caused by a XENAPI_PLUGIN_FAILURE. I have attached the nova-compute.log and xcp-xapi.log files showing the trace of the crash. Ewan, Mike, Jon, do you know what's going on? Also, my understanding of Quantum is that it's for Openstack + KVM, and that XCP doesn't need it, as the xcp-networkd will do the vFlows work by itself. Am I right? How does it work? BTW, I'm writing an automated script, inspired from Ghe's debostack, for setting-up a domU that would connect to XCP. I might be a good idea to run this as a Jenkins job. Once I have the above working (eg: Openstack working with Kronos), I'll share the script, so we always make sure everything works. Let me know, Cheers, Thomas Goirand (zigo) --------------080508070801000609060802 Content-Type: text/plain; name="compute.log.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="compute.log.txt" 2012-03-13 05:41:31 WARNING nova.virt.libvirt.firewall [-] Libvirt module could not be loaded. NWFilterFirewall will not work correctly. 2012-03-13 05:41:31 DEBUG nova.service [-] Full set of FLAGS: from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:402 2012-03-13 05:41:31 DEBUG nova.service [-] default_floating_pool : nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] storage_availability_zone : nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rescue_image_id : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] num_networks : 1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vc_image_name : vc_image from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_dmz_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fixed_range : 10.0.0.0/8 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] compute_topic : compute from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vsa_topic : vsa from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] glance_port : 9292 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] glance_api_servers : ['--compute-host-ip--:9292'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_listen_port : 8774 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] user_cert_subject : /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=%.16s-%.16s-%s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] s3_dmz : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_ram : 51200 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_sparse_copy : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_listen : 0.0.0.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cache_images : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vlan_interface : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] aws_access_key_id : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] bandwith_poll_interval : 600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_sr_base_path : /var/run/sr-mount from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_size : 256 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] host_state_interval : 120 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] virt_mkfs : ['default=mkfs.ext3 -L %(fs_label)s -F %(target)s', 'linux=mkfs.ext3 -L %(fs_label)s -F %(target)s', 'windows=mkfs.ntfs --force --fast --label %(fs_label)s %(target)s'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] enable_new_services : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] my_ip : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] live_migration_flag : VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] live_migration_retry_count : 30 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] password_length : 12 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_max_injected_files : 5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] security_group_handler : nova.network.quantum.sg.NullSecurityGroupHandler from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] public_interface : eth0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] iqn_prefix : iqn.2010-10.org.openstack from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_schedule_zone : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_disk_prefix : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logdir : /var/log/nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_volume_listen : 0.0.0.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sqlite_db : nova.sqlite from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_extension : ['nova.api.openstack.compute.contrib.standard_extensions'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] allow_resize_to_same_host : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] reclaim_instance_interval : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_device_mtu : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cert_manager : nova.cert.manager.CertManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_usb_tablet : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ipv6_backend : rfc2462 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] notification_driver : nova.notifier.no_op_notifier from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_max_limit : 1000 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] enable_instance_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] compute_api_class : nova.compute.api.API from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] remove_unused_base_images : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_port : 5672 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dns_server : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_host_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] default_access_ip_network_name : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_max_retries : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] resume_guests_state_on_host_boot : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] snapshot_image_format : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dhcp_lease_time : 120 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_listen : 0.0.0.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logfile : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] floating_ip_dns_manager : nova.network.dns_driver.DNSDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cpuinfo_xml_template : /usr/lib/python2.7/dist-packages/nova/virt/cpuinfo.xml.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_remap_vbd_dev_prefix : sd from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] injected_network_template : /usr/lib/python2.7/dist-packages/nova/virt/interfaces.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_host : debian from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] send_arp_for_ha : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_connection_concurrent : 5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] snapshot_name_template : snapshot-%08x from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_host_username : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] resize_confirm_window : 86400 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vncserver_proxyclient_address : 127.0.0.1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_connection_username : root from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_cores : 20 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] heal_instance_info_cache_interval : 60 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] debug : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_project_ca : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] routing_source_ip : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vsa_name_template : vsa-%08x from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_log_levels : ['amqplib=WARN', 'sqlalchemy=WARN', 'boto=WARN', 'suds=INFO', 'eventlet.wsgi.server=WARN'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_topic : volume from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_use_virtio_for_bridges : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dnsmasq_config_file : from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_link_prefix : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_wsdl_loc : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_name_template : volume-%08x from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] lock_path : /var/lock/nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] live_migration_uri : qemu+tcp://%s/system from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] state_path : /var/lib/nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] allow_same_net_traffic : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_manager : nova.api.manager.MetadataManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_image_cache_manager : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_vif_type : bridge from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_agent_path : usr/sbin/xe-update-networking from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] flat_network_dns : 8.8.4.4 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] remove_unused_original_minimum_age_seconds : 86400 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_vsa_instance_type : m1.small from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_config : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_stderr : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] connection_type : xenapi from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] update_dhcp_on_disassociate : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_project : openstack from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] s3_port : 3333 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] max_kernel_ramdisk_size : 16777216 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logfile_mode : 0644 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_ephemeral_format : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logging_context_format_string : %(asctime)s %(levelname)s %(name)s [%(request_id)s %(user_id)s %(project_id)s] %(instance)s%(message)s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_listen_port : 8775 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_ip : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] isolated_hosts : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_name_template : instance-%08x from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_usage_audit_period : month from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_dir : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_durable_queues : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credential_key_file : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] quota_metadata_items : 128 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logging_debug_format_suffix : from (pid=%(process)d) %(funcName)s %(pathname)s:%(lineno)d from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] stub_network : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] console_manager : nova.console.manager.ConsoleProxyManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] zombie_instance_updated_at_window : 172800 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_join_force : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rpc_backend : nova.rpc.impl_kombu from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_userid : guest from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] running_deleted_instance_poll_interval : 30 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] agent_version_timeout : 300 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_volume_extension : ['nova.api.openstack.volume.contrib.standard_extensions'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_scheme : http from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credential_rc_file : %src from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dhcp_domain : novalocal from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sql_connection : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] console_topic : console from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instances_path : /var/lib/nova/instances from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] flat_injected : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_local_volumes : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] host : debian from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_dns_domain : from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] target_port : 3260 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fixed_ip_disassociate_timeout : 600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] running_deleted_instance_action : noop from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] console_host : debian from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_remap_vbd_dev : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_max_injected_file_content_bytes : 10240 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] key_file : private/cakey.pem from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] floating_range : 4.4.4.0/24 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] reboot_timeout : 600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] multi_host : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] glance_num_retries : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] db_backend : sqlalchemy from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credentials_template : /usr/lib/python2.7/dist-packages/nova/auth/novarc.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] image_cache_manager_interval : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sql_retry_interval : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_task_poll_interval : 5.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_driver : nova.volume.driver.ISCSIDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] networks_path : /var/lib/nova/networks from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] crl_file : crl.pem from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] gateway_v6 : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] monkey_patch : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rpc_conn_pool_size : 30 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] s3_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] qemu_img : qemu-img from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sqlite_synchronous : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_host_ip : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] max_nbd_devices : 16 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] policy_file : policy.json from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] linuxnet_ovs_integration_bridge : br-int from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_force_update_capabilities : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] scheduler_topic : scheduler from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] verbose : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] flat_network_bridge : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sql_max_retries : 12 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_ovs_integration_bridge : xapi1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_instance_type : m1.small from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_listen : 0.0.0.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] firewall_driver : nova.virt.firewall.IptablesFirewallDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_type : kvm from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] periodic_interval : 60 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_deprecated_auth : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_key_suffix : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_vif_driver : nova.virt.xenapi.vif.XenAPIBridgeDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_cow_images : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_volume_listen_port : 8776 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] gateway : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] null_kernel : nokernel from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] target_host : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] flat_interface : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] force_raw_images : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_client_template : /usr/lib/python2.7/dist-packages/nova/cloudpipe/client.ovpn.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_format : [instance: %(uuid)s] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_glance_link_prefix : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dmz_cidr : 10.128.0.0/24 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_vif_driver : nova.virt.libvirt.vif.LibvirtBridgeDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rpc_response_timeout : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_xml_template : /usr/lib/python2.7/dist-packages/nova/virt/libvirt.xml.template from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credential_vpn_file : nova-vpn.conf from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_compute_ext_list : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_notification_level : INFO from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] publish_errors : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] consoleauth_topic : consoleauth from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] credential_cert_file : cert.pem from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] auto_assign_floating_ip : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] novncproxy_base_url : http://--compute-host-ip--:6080/vnc_auto.html from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] service_down_time : 60 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logging_exception_prefix : (%(name)s): TRACE: from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] enabled_apis : ['ec2', 'osapi_compute', 'osapi_volume', 'metadata'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_api_class : nova.volume.api.API from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_vlan_interface : vmnic0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] report_interval : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] scheduler_manager : nova.scheduler.manager.SchedulerManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_port : 8773 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_running_timeout : 60 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] monkey_patch_modules : ['nova.api.ec2.cloud:nova.notifier.api.notify_decorator', 'nova.compute.api:nova.notifier.api.notify_decorator'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rescue_kernel_id : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fixed_range_v6 : fd00::/48 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_retry_backoff : 2 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] auth_token_ttl : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_volumes : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_uri : from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_listen_port : 8773 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_scheme : http from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] keys_path : /var/lib/nova/keys from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_image_id : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] disable_process_locking : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmware_vif_driver : nova.virt.vmwareapi.vif.VMWareVlanBridgeDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] block_migration_flag : VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, VIR_MIGRATE_NON_SHARED_INC from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] live_migration_bandwidth : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cert_topic : cert from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_max_injected_file_path_bytes : 255 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_floating_ips : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] max_vcs_in_vsa : 32 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fake_call : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_publisher_id : debian from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] instance_dns_manager : nova.network.dns_driver.DNSDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sql_idle_timeout : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] glance_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xvpvncproxy_base_url : http://127.0.0.1:6081/console from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_image : ami-11111 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] aws_secret_access_key : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] use_ipv6 : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_format : %(asctime)s %(levelname)8s [%(name)s] %(message)s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] allowed_roles : ['cloudadmin', 'itsec', 'sysadmin', 'netadmin', 'developer'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fake_network : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] metadata_port : 8775 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] force_dhcp_release : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dhcpbridge_flagfile : /etc/nova/nova-dhcpbridge.conf from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_gigabytes : 1000 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] region_list : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_vhd_coalesce_poll_interval : 5.0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] dhcpbridge : /usr/lib/python2.7/dist-packages/bin/nova-dhcpbridge from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vpn_start : 1000 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_vhd_coalesce_max_attempts : 5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] running_deleted_instance_timeout : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] auth_driver : nova.auth.dbdriver.DbDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_manager : nova.network.manager.VlanManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] root_helper : sudo from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rescue_ramdisk_id : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] checksum_base_images : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] memcached_servers : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] logging_default_format_string : %(asctime)s %(levelname)s %(name)s [-] %(instance)s%(message)s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_volume_ext_list : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] find_host_timeout : 30 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vsa_manager : nova.vsa.manager.VsaManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] default_os_type : linux from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] fake_rabbit : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_date_format : %Y-%m-%d %H:%M:%S from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] timeout_nbd : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] block_device_creation_timeout : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_host : --compute-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vnc_keymap : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] rescue_timeout : 86400 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ca_path : /var/lib/nova/CA from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] policy_default_rule : default from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_login_timeout : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vncserver_listen : 127.0.0.1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_syslog : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] use_single_default_gateway : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] superuser_roles : ['cloudadmin'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] osapi_path : /v1.1/ from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] syslog_log_facility : LOG_USER from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ec2_path : /services/Cloud from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] remove_unused_resized_minimum_age_seconds : 3600 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vmwareapi_api_retry_count : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] linuxnet_interface_driver : nova.network.linux_net.LinuxBridgeInterfaceDriver from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_use_ssl : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_retry_interval : 1 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] config_file : ['/tmp/nova-conf-k_FZuG/tmpQyjVbE.conf'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] ca_file : cacert.pem from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_api_class : nova.network.api.API from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] node_availability_zone : nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_task_poll_interval : 0.5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] db_driver : nova.db from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] create_unique_mac_address_attempts : 5 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] img_handlers : ['loop', 'nbd', 'guestfs'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] volume_manager : nova.volume.manager.VolumeManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] start_guests_on_host_boot : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_generate_swap : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vlan_start : 100 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] rpc_thread_pool_size : 1024 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] sr_matching_filter : other-config:i18n-key=local-storage from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] l3_lib : nova.network.l3.LinuxNetL3 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] isolated_images : [] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vnc_enabled : True from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_log_instance_actions : False from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] api_paste_config : api-paste.ini from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] global_roles : ['cloudadmin', 'itsec'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_connection_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] rabbit_virtual_host : / from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_volume_drivers : ['iscsi=nova.virt.libvirt.volume.LibvirtISCSIVolumeDriver', 'local=nova.virt.libvirt.volume.LibvirtVolumeDriver', 'fake=nova.virt.libvirt.volume.LibvirtFakeVolumeDriver', 'rbd=nova.virt.libvirt.volume.LibvirtNetVolumeDriver', 'sheepdog=nova.virt.libvirt.volume.LibvirtNetVolumeDriver'] from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] xenapi_connection_url : https://---kronos-host-ip-- from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_driver : nova.network.linux_net from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] quota_instances : 10 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] project_cert_subject : /C=US/ST=California/O=OpenStack/OU=NovaDev/CN=project-ca-%.16s-%s from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] image_service : nova.image.glance.GlanceImageService from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] libvirt_inject_password : FLAG SET from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:409 2012-03-13 05:41:31 DEBUG nova.service [-] control_exchange : nova from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] cnt_vpn_clients : 0 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] vsa_part_size_gb : 100 from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] log_file : None from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] compute_manager : nova.compute.manager.ComputeManager from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] compute_driver : nova.virt.connection.get_connection from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 DEBUG nova.service [-] network_topic : network from (pid=20186) wait /usr/lib/python2.7/dist-packages/nova/service.py:411 2012-03-13 05:41:31 AUDIT nova.service [-] Starting compute node (version 2012.1-LOCALBRANCH:LOCALREVISION) 2012-03-13 05:41:31 DEBUG nova.utils [req-1226d918-e523-402d-9821-7fd44c738e16 None None] backend from (pid=20186) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:607 2012-03-13 05:41:32 DEBUG nova.virt.xenapi.host [-] Updating host stats from (pid=20186) update_status /usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py:124 2012-03-13 05:41:32 WARNING nova.virt.xenapi_conn [-] Task [Async.host.call_plugin] OpaqueRef:71f0f3bb-3086-9a05-4313-d8a423ab9d45 status: failure ['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', ''] 2012-03-13 05:41:32 ERROR nova.virt.xenapi.host [-] The call to host_data returned an error: ['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', '']. 2012-03-13 05:41:32 CRITICAL nova [-] 'str' object does not support item assignment (nova): TRACE: Traceback (most recent call last): (nova): TRACE: File "/usr/bin/nova-compute", line 49, in (nova): TRACE: service.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 413, in wait (nova): TRACE: _launcher.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 131, in wait (nova): TRACE: service.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 166, in wait (nova): TRACE: return self._exit_event.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait (nova): TRACE: return hubs.get_hub().switch() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 177, in switch (nova): TRACE: return self.greenlet.switch() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in main (nova): TRACE: result = function(*args, **kwargs) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 101, in run_server (nova): TRACE: server.start() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 174, in start (nova): TRACE: self.manager.update_available_resource(ctxt) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2293, in update_available_resource (nova): TRACE: self.driver.update_available_resource(context, self.host) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 398, in update_available_resource (nova): TRACE: host_stats = self.get_host_stats(refresh=True) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 472, in get_host_stats (nova): TRACE: return self.host_state.get_host_stats(refresh=refresh) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 187, in host_state (nova): TRACE: self._host_state = host.HostState(self._session) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py", line 110, in __init__ (nova): TRACE: self.update_status() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py", line 137, in update_status (nova): TRACE: data["disk_total"] = total (nova): TRACE: TypeError: 'str' object does not support item assignment (nova): TRACE: --------------080508070801000609060802 Content-Type: text/plain; name="xcp-xapi.log.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="xcp-xapi.log.txt" [20120313T05:41:30.668Z|debug|node4407.gplhost.com|1353 INET 127.0.0.1:80|session.login_with_password D:c8c336d594af|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.669Z| info|node4407.gplhost.com|1353 INET 127.0.0.1:80|session.login_with_password D:c8c336d594af|xapi] Session.create trackid=bf1fbbc06724826b0912a76e2f8e75ff pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.669Z|debug|node4407.gplhost.com|1353 INET 127.0.0.1:80|session.login_with_password D:c8c336d594af|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.670Z|debug|node4407.gplhost.com|1354 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:66fa8df77fb9 created by task D:c8c336d594af [20120313T05:41:30.733Z|debug|node4407.gplhost.com|1355 INET 127.0.0.1:80|session.login_with_password D:84d09b037816|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.734Z| info|node4407.gplhost.com|1355 INET 127.0.0.1:80|session.login_with_password D:84d09b037816|xapi] Session.create trackid=8ddf2b2e641ee52697e094f56c828866 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.735Z|debug|node4407.gplhost.com|1355 INET 127.0.0.1:80|session.login_with_password D:84d09b037816|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.736Z|debug|node4407.gplhost.com|1356 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:94ce61f48526 created by task D:84d09b037816 [20120313T05:41:30.800Z|debug|node4407.gplhost.com|1357 INET 127.0.0.1:80|session.login_with_password D:54ac9dfe53bc|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.801Z| info|node4407.gplhost.com|1357 INET 127.0.0.1:80|session.login_with_password D:54ac9dfe53bc|xapi] Session.create trackid=e662601de316e3f408100b6c1a388b3e pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.802Z|debug|node4407.gplhost.com|1357 INET 127.0.0.1:80|session.login_with_password D:54ac9dfe53bc|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.802Z|debug|node4407.gplhost.com|1358 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:9b45e2c22c93 created by task D:54ac9dfe53bc [20120313T05:41:30.868Z|debug|node4407.gplhost.com|1359 INET 127.0.0.1:80|session.login_with_password D:74791661f3f1|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.869Z| info|node4407.gplhost.com|1359 INET 127.0.0.1:80|session.login_with_password D:74791661f3f1|xapi] Session.create trackid=8c2a0436698aeee34c2ace5f08ddf5dd pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.869Z|debug|node4407.gplhost.com|1359 INET 127.0.0.1:80|session.login_with_password D:74791661f3f1|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.870Z|debug|node4407.gplhost.com|1360 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:fdcd22a684c4 created by task D:74791661f3f1 [20120313T05:41:30.934Z|debug|node4407.gplhost.com|1361 INET 127.0.0.1:80|session.login_with_password D:5d149033466a|xapi] Successful local authentication user root from HTTP request from Internet with User-Agent: xmlrpclib.py/1.0.1 (by www.pythonware.com) [20120313T05:41:30.935Z| info|node4407.gplhost.com|1361 INET 127.0.0.1:80|session.login_with_password D:5d149033466a|xapi] Session.create trackid=03010b0e2d18f2d8f7dafc8e84ebb119 pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120313T05:41:30.936Z|debug|node4407.gplhost.com|1361 INET 127.0.0.1:80|session.login_with_password D:5d149033466a|xapi] Attempting to open /var/lib/xcp/xapi [20120313T05:41:30.937Z|debug|node4407.gplhost.com|1362 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:d7d20acd7029 created by task D:5d149033466a [20120313T05:41:31.468Z| info|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] spawning a new thread to handle the current task (trackid=bf1fbbc06724826b0912a76e2f8e75ff) [20120313T05:41:31.468Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|audit] Host.call_plugin host = 'ee61ea48-ad10-a478-3f7a-3bb9fd7df802 (node4407.gplhost.com)'; plugin = 'xenhost'; fn = 'host_data'; args = [ ] [20120313T05:41:31.478Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|xapi] Raised at forkhelpers.ml:181.30-76 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.478Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at xapi_plugins.ml:45.7-100 -> message_forwarding.ml:233.25-44 -> rbac.ml:229.16-23 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] Server_helpers.exec exception_handler: Got exception XENAPI_PLUGIN_FAILURE: [ non-zero exit; ; ] [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|dispatcher] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120313T05:41:31.479Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|backtrace] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120313T05:41:31.482Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.482Z|debug|node4407.gplhost.com|1363|Async.host.call_plugin R:71f0f3bb3086|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.482Z|debug|node4407.gplhost.com|1363||xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120313T05:41:31.482Z|debug|node4407.gplhost.com|1363||xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1357 INET 127.0.0.1:80||http_critical] Premature termination of connection! [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1353 INET 127.0.0.1:80||http_critical] Premature termination of connection! [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1355 INET 127.0.0.1:80||http_critical] Premature termination of connection! [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1359 INET 127.0.0.1:80||http_critical] Premature termination of connection! [20120313T05:41:32.056Z|debug|node4407.gplhost.com|1361 INET 127.0.0.1:80||http_critical] Premature termination of connection! --------------080508070801000609060802 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 --------------080508070801000609060802-- From xen-api-bounces@lists.xen.org Fri Mar 16 15:36:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB5-0002kX-J8; Fri, 16 Mar 2012 15:34:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7VAt-0007GV-C4 for xen-api@lists.xen.org; Tue, 13 Mar 2012 17:06:15 +0000 Received: from [85.158.143.99:5992] by server-2.bemta-4.messagelabs.com id EE/4E-17550-68E7F5F4; Tue, 13 Mar 2012 17:06:14 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-12.tower-216.messagelabs.com!1331658373!13760875!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7356 invoked from network); 13 Mar 2012 17:06:14 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-12.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2012 17:06:14 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 4D7BBFE436; Tue, 13 Mar 2012 17:07:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=VUrEA0xll N7uOu4/dCKDVs9Znwc=; b=GFLE6AjTKjYELHOsgfa4dCMjy1uI0wdQkpJUxRwhp KOJN2Demt0sMhVOydAw9GM7Aa/3zPlKXp7S4Nf58RwLe9TCmaqnFw5UUiluajBmR klUiR7Xxml91i05dWBa4ZYjMJx/y0O49K9FYE5nPR64QkyWHSokDndWW2m0RYQIu Us= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=V97 aP+ITDm25SqLEWaIxr/+fJIpXv6vTK35L8abZ/fhovWsEn6F0z0fJojAHnthGV8D y7OociDGnDgWgTLde9b5Ljs2oRFN+FMaV47oM2X7pedV/6wHG0qIOFeGkN+v6lwe zlDilu4KZTN44mHntxQD93YoBGkXaXqxRZG/yp3s= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 4B302FE25C; Tue, 13 Mar 2012 17:07:29 +0000 (UTC) Message-ID: <4F5F7E80.4000500@goirand.fr> Date: Wed, 14 Mar 2012 01:06:08 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: John Garbutt References: <4F5F10AA.1040206@goirand.fr> In-Reply-To: X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Renuka Apte , Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack-devel] [Openstack] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On 03/13/2012 06:57 PM, John Garbutt wrote: > A few possible issues: > * you might not have the execute permissions set on the xenhost plugin file? On XenServer that means it fails to register the plugin. Yup, it was that. Thanks for the hint. IMO, the error message should have been a little bit more explicit, as I really wasn't expecting something like this... Thomas _______________________________________________ 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 16 15:36:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB4-0002jN-5K; Fri, 16 Mar 2012 15:34:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7LU3-0001fA-Oq for xen-api@lists.xen.org; Tue, 13 Mar 2012 06:45:23 +0000 Received: from [85.158.139.83:2325] by server-6.bemta-5.messagelabs.com id 0D/5C-13222-20DEE5F4; Tue, 13 Mar 2012 06:45:22 +0000 X-Env-Sender: dan@nicira.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1331621119!15206056!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16193 invoked from network); 13 Mar 2012 06:45:21 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 06:45:21 -0000 Received: by iafj26 with SMTP id j26so451784iaf.32 for ; Mon, 12 Mar 2012 23:45:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=0J9RGubFzo6jPjUDvuqSB5AEwu04Owi1h7rjDH3jJ2s=; b=U01f74Qckl25M8Jp8DRJA2hwuTVMBCQR0UNEjvh2/AJPO43xLs5mqYMl5ADuBMNFIb Cyga0QcAuxI8/wmpAOsCXx/tZTY3wEyeIdzHFSK2YiE/wFsfhItIRKuZ64t7q9XYitiY 0JSHjLQc/XygJUP7G2NNzFeuYRRa/5gDAoLpiIMsxm8rdgap0gyWozBxBW6xBCi5rubp ntP+fw1q/c1U8L/ZVnYI0PsU+ZpqJ63Y/1eVEIMRXJ00D7W5uwLJTrd46MCtrL6nx/Ge T0SxvWwD3rGZif7r8M/C3Sec6avsy0QXfbrvC3zDKEgm/8OPHUFHeDupGhkIuHGD7BRR e3Bw== Received: by 10.68.230.229 with SMTP id tb5mr5094950pbc.0.1331621119048; Mon, 12 Mar 2012 23:45:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.223.103 with HTTP; Mon, 12 Mar 2012 23:44:59 -0700 (PDT) In-Reply-To: <4F5EE0D3.6040405@goirand.fr> References: <4F5EE0D3.6040405@goirand.fr> From: Dan Wendlandt Date: Mon, 12 Mar 2012 23:44:59 -0700 Message-ID: To: Thomas Goirand X-Gm-Message-State: ALoCoQkqsSPuWDYRi0F3Pk+hvNTBmAvnGPvVWp6RqG04OvEyE9S/iCAniX3PkTO0UoRruRnexzP6 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , xen-api@lists.xen.org Subject: Re: [Xen-API] [Openstack] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2545317601875936588==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2545317601875936588== Content-Type: multipart/alternative; boundary=047d7b339ca5c6bc9c04bb1a33cf --047d7b339ca5c6bc9c04bb1a33cf Content-Type: text/plain; charset=ISO-8859-1 On Mon, Mar 12, 2012 at 10:53 PM, Thomas Goirand wrote: > > > Also, my understanding of Quantum is that it's for Openstack + KVM, and > that XCP doesn't need it, as the xcp-networkd will do the vFlows work by > itself. Am I right? How does it work? > As an FYI, there's nothing KVM-specific about Quantum. I know of significant deployments of Quantum on both KVM and XenServer platforms with OpenStack. I'm not familiar with xcp-networkd so I can't really provide a comparison, but at a high-level Quantum is about exposing an API for tenant control of networking, and allowing different technologies to act as pluggable backends to implement this generic network API. Dan > BTW, I'm writing an automated script, inspired from Ghe's debostack, for > setting-up a domU that would connect to XCP. I might be a good idea to > run this as a Jenkins job. Once I have the above working (eg: Openstack > working with Kronos), I'll share the script, so we always make sure > everything works. > > Let me know, > Cheers, > > Thomas Goirand (zigo) > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~ --047d7b339ca5c6bc9c04bb1a33cf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Mar 12, 2012 at 10:53 PM, Thomas= Goirand <thomas@= goirand.fr> wrote:

Also, my understanding of Quantum is that it's for Openstack + KVM, and=
that XCP doesn't need it, as the xcp-networkd will do the vFlows work b= y
itself. Am I right? How does it work?

A= s an FYI, there's nothing KVM-specific about Quantum. =A0I know of sign= ificant deployments of Quantum on both KVM and XenServer platforms with Ope= nStack. =A0=A0

I'm not=A0familiar=A0with xcp-networkd so I can'= ;t really provide a comparison, but at a high-level Quantum is about exposi= ng an API for tenant control of networking, and allowing different technolo= gies to act as pluggable backends to implement this generic network API. = =A0

Dan=A0


BTW, I'm writing an automated script, inspired from Ghe's debostack= , for
setting-up a domU that would connect to XCP. I might be a good idea to
run this as a Jenkins job. Once I have the above working (eg: Openstack
working with Kronos), I'll share the script, so we always make sure
everything works.

Let me know,
Cheers,

Thomas Goirand (zigo)

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to =A0 =A0 : openstac= k@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help =A0 : https://help.launchpad.net/ListHelp




--
~~~~~~~~= ~~~~~~~~~~~~~~~~~~~
Dan Wendlandt=A0
Nicira Networks:=A0www.nicira.com
twitter:= danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~

--047d7b339ca5c6bc9c04bb1a33cf-- --===============2545317601875936588== 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 --===============2545317601875936588==-- From xen-api-bounces@lists.xen.org Fri Mar 16 15:36:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB4-0002jN-5K; Fri, 16 Mar 2012 15:34:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7LU3-0001fA-Oq for xen-api@lists.xen.org; Tue, 13 Mar 2012 06:45:23 +0000 Received: from [85.158.139.83:2325] by server-6.bemta-5.messagelabs.com id 0D/5C-13222-20DEE5F4; Tue, 13 Mar 2012 06:45:22 +0000 X-Env-Sender: dan@nicira.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1331621119!15206056!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16193 invoked from network); 13 Mar 2012 06:45:21 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 06:45:21 -0000 Received: by iafj26 with SMTP id j26so451784iaf.32 for ; Mon, 12 Mar 2012 23:45:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=0J9RGubFzo6jPjUDvuqSB5AEwu04Owi1h7rjDH3jJ2s=; b=U01f74Qckl25M8Jp8DRJA2hwuTVMBCQR0UNEjvh2/AJPO43xLs5mqYMl5ADuBMNFIb Cyga0QcAuxI8/wmpAOsCXx/tZTY3wEyeIdzHFSK2YiE/wFsfhItIRKuZ64t7q9XYitiY 0JSHjLQc/XygJUP7G2NNzFeuYRRa/5gDAoLpiIMsxm8rdgap0gyWozBxBW6xBCi5rubp ntP+fw1q/c1U8L/ZVnYI0PsU+ZpqJ63Y/1eVEIMRXJ00D7W5uwLJTrd46MCtrL6nx/Ge T0SxvWwD3rGZif7r8M/C3Sec6avsy0QXfbrvC3zDKEgm/8OPHUFHeDupGhkIuHGD7BRR e3Bw== Received: by 10.68.230.229 with SMTP id tb5mr5094950pbc.0.1331621119048; Mon, 12 Mar 2012 23:45:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.223.103 with HTTP; Mon, 12 Mar 2012 23:44:59 -0700 (PDT) In-Reply-To: <4F5EE0D3.6040405@goirand.fr> References: <4F5EE0D3.6040405@goirand.fr> From: Dan Wendlandt Date: Mon, 12 Mar 2012 23:44:59 -0700 Message-ID: To: Thomas Goirand X-Gm-Message-State: ALoCoQkqsSPuWDYRi0F3Pk+hvNTBmAvnGPvVWp6RqG04OvEyE9S/iCAniX3PkTO0UoRruRnexzP6 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , xen-api@lists.xen.org Subject: Re: [Xen-API] [Openstack] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2545317601875936588==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2545317601875936588== Content-Type: multipart/alternative; boundary=047d7b339ca5c6bc9c04bb1a33cf --047d7b339ca5c6bc9c04bb1a33cf Content-Type: text/plain; charset=ISO-8859-1 On Mon, Mar 12, 2012 at 10:53 PM, Thomas Goirand wrote: > > > Also, my understanding of Quantum is that it's for Openstack + KVM, and > that XCP doesn't need it, as the xcp-networkd will do the vFlows work by > itself. Am I right? How does it work? > As an FYI, there's nothing KVM-specific about Quantum. I know of significant deployments of Quantum on both KVM and XenServer platforms with OpenStack. I'm not familiar with xcp-networkd so I can't really provide a comparison, but at a high-level Quantum is about exposing an API for tenant control of networking, and allowing different technologies to act as pluggable backends to implement this generic network API. Dan > BTW, I'm writing an automated script, inspired from Ghe's debostack, for > setting-up a domU that would connect to XCP. I might be a good idea to > run this as a Jenkins job. Once I have the above working (eg: Openstack > working with Kronos), I'll share the script, so we always make sure > everything works. > > Let me know, > Cheers, > > Thomas Goirand (zigo) > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~ --047d7b339ca5c6bc9c04bb1a33cf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Mar 12, 2012 at 10:53 PM, Thomas= Goirand <thomas@= goirand.fr> wrote:

Also, my understanding of Quantum is that it's for Openstack + KVM, and=
that XCP doesn't need it, as the xcp-networkd will do the vFlows work b= y
itself. Am I right? How does it work?

A= s an FYI, there's nothing KVM-specific about Quantum. =A0I know of sign= ificant deployments of Quantum on both KVM and XenServer platforms with Ope= nStack. =A0=A0

I'm not=A0familiar=A0with xcp-networkd so I can'= ;t really provide a comparison, but at a high-level Quantum is about exposi= ng an API for tenant control of networking, and allowing different technolo= gies to act as pluggable backends to implement this generic network API. = =A0

Dan=A0


BTW, I'm writing an automated script, inspired from Ghe's debostack= , for
setting-up a domU that would connect to XCP. I might be a good idea to
run this as a Jenkins job. Once I have the above working (eg: Openstack
working with Kronos), I'll share the script, so we always make sure
everything works.

Let me know,
Cheers,

Thomas Goirand (zigo)

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to =A0 =A0 : openstac= k@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help =A0 : https://help.launchpad.net/ListHelp




--
~~~~~~~~= ~~~~~~~~~~~~~~~~~~~
Dan Wendlandt=A0
Nicira Networks:=A0www.nicira.com
twitter:= danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~

--047d7b339ca5c6bc9c04bb1a33cf-- --===============2545317601875936588== 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 --===============2545317601875936588==-- From xen-api-bounces@lists.xen.org Fri Mar 16 15:36:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB5-0002kX-J8; Fri, 16 Mar 2012 15:34:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7VAt-0007GV-C4 for xen-api@lists.xen.org; Tue, 13 Mar 2012 17:06:15 +0000 Received: from [85.158.143.99:5992] by server-2.bemta-4.messagelabs.com id EE/4E-17550-68E7F5F4; Tue, 13 Mar 2012 17:06:14 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-12.tower-216.messagelabs.com!1331658373!13760875!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7356 invoked from network); 13 Mar 2012 17:06:14 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-12.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2012 17:06:14 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 4D7BBFE436; Tue, 13 Mar 2012 17:07:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=VUrEA0xll N7uOu4/dCKDVs9Znwc=; b=GFLE6AjTKjYELHOsgfa4dCMjy1uI0wdQkpJUxRwhp KOJN2Demt0sMhVOydAw9GM7Aa/3zPlKXp7S4Nf58RwLe9TCmaqnFw5UUiluajBmR klUiR7Xxml91i05dWBa4ZYjMJx/y0O49K9FYE5nPR64QkyWHSokDndWW2m0RYQIu Us= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=V97 aP+ITDm25SqLEWaIxr/+fJIpXv6vTK35L8abZ/fhovWsEn6F0z0fJojAHnthGV8D y7OociDGnDgWgTLde9b5Ljs2oRFN+FMaV47oM2X7pedV/6wHG0qIOFeGkN+v6lwe zlDilu4KZTN44mHntxQD93YoBGkXaXqxRZG/yp3s= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 4B302FE25C; Tue, 13 Mar 2012 17:07:29 +0000 (UTC) Message-ID: <4F5F7E80.4000500@goirand.fr> Date: Wed, 14 Mar 2012 01:06:08 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: John Garbutt References: <4F5F10AA.1040206@goirand.fr> In-Reply-To: X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Renuka Apte , Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack-devel] [Openstack] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On 03/13/2012 06:57 PM, John Garbutt wrote: > A few possible issues: > * you might not have the execute permissions set on the xenhost plugin file? On XenServer that means it fails to register the plugin. Yup, it was that. Thanks for the hint. IMO, the error message should have been a little bit more explicit, as I really wasn't expecting something like this... Thomas _______________________________________________ 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 16 15:36:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB3-0002j5-N1; Fri, 16 Mar 2012 15:34:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7LHh-0001dD-5N for xen-api@lists.xen.org; Tue, 13 Mar 2012 06:32:37 +0000 Received: from [85.158.143.99:11198] by server-2.bemta-4.messagelabs.com id 0D/46-17550-40AEE5F4; Tue, 13 Mar 2012 06:32:36 +0000 X-Env-Sender: renuka.apte@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1331620353!18918019!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxMjc3ODg=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 670 invoked from network); 13 Mar 2012 06:32:35 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 06:32:35 -0000 X-IronPort-AV: E=Sophos;i="4.73,575,1325480400"; d="scan'208";a="22995040" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Mar 2012 02:32:18 -0400 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Mon, 12 Mar 2012 23:32:17 -0700 From: Renuka Apte To: Thomas Goirand , "xen-api@lists.xen.org" , "openstack@lists.launchpad.net" , Ewan Mellor , Mike McClurg , Jonathan Ludlam , PKG OpenStack Date: Mon, 12 Mar 2012 23:32:15 -0700 Thread-Topic: [Openstack] XENAPI_PLUGIN_FAILURE with kronos Thread-Index: Ac0A4wklbMeHxmHCSU+X9ljFjbrf0Q== Message-ID: In-Reply-To: <4F5EE0D3.6040405@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.14.0.111121 acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Salvatore Orlando Subject: Re: [Xen-API] [Openstack] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 You need to install the xenapi plugins: If you are using devstack (https://github.com/openstack-dev/devstack), the code below from build_domU.sh does this for you. # Checkout nova if [ ! -d $TOP_DIR/nova ]; then env GIT_SSL_NO_VERIFY=true git clone $NOVA_REPO cd $TOP_DIR/nova git checkout $NOVA_BRANCH fi # Install plugins cp -pr $TOP_DIR/nova/plugins/xenserver/xenapi/etc/xapi.d /etc/ chmod a+x /etc/xapi.d/plugins/* yum --enablerepo=base install -y parted mkdir -p /boot/guest Thanks, Renuka. On 3/12/12 10:53 PM, "Thomas Goirand" wrote: >Hi, > >I am trying to setup nova-compute with a Kronos setup. Everything comes >from the packages in SID (including nova-xcp-network and >nova-xcp-pluggins in the dom0, which we now package in Debian). > >When starting nova-compute, I have a python stack dump caused by a >XENAPI_PLUGIN_FAILURE. I have attached the nova-compute.log and >xcp-xapi.log files showing the trace of the crash. > >Ewan, Mike, Jon, do you know what's going on? > >Also, my understanding of Quantum is that it's for Openstack + KVM, and >that XCP doesn't need it, as the xcp-networkd will do the vFlows work by >itself. Am I right? How does it work? > >BTW, I'm writing an automated script, inspired from Ghe's debostack, for >setting-up a domU that would connect to XCP. I might be a good idea to >run this as a Jenkins job. Once I have the above working (eg: Openstack >working with Kronos), I'll share the script, so we always make sure >everything works. > >Let me know, >Cheers, > >Thomas Goirand (zigo) _______________________________________________ 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 16 15:36:05 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36: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 1S8ZB3-0002j5-N1; Fri, 16 Mar 2012 15:34:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7LHh-0001dD-5N for xen-api@lists.xen.org; Tue, 13 Mar 2012 06:32:37 +0000 Received: from [85.158.143.99:11198] by server-2.bemta-4.messagelabs.com id 0D/46-17550-40AEE5F4; Tue, 13 Mar 2012 06:32:36 +0000 X-Env-Sender: renuka.apte@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1331620353!18918019!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxMjc3ODg=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 670 invoked from network); 13 Mar 2012 06:32:35 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Mar 2012 06:32:35 -0000 X-IronPort-AV: E=Sophos;i="4.73,575,1325480400"; d="scan'208";a="22995040" Received: from sjcpmailmx01.citrite.net ([10.216.14.74]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Mar 2012 02:32:18 -0400 Received: from SJCPMAILBOX01.citrite.net ([10.216.4.73]) by SJCPMAILMX01.citrite.net ([10.216.14.74]) with mapi; Mon, 12 Mar 2012 23:32:17 -0700 From: Renuka Apte To: Thomas Goirand , "xen-api@lists.xen.org" , "openstack@lists.launchpad.net" , Ewan Mellor , Mike McClurg , Jonathan Ludlam , PKG OpenStack Date: Mon, 12 Mar 2012 23:32:15 -0700 Thread-Topic: [Openstack] XENAPI_PLUGIN_FAILURE with kronos Thread-Index: Ac0A4wklbMeHxmHCSU+X9ljFjbrf0Q== Message-ID: In-Reply-To: <4F5EE0D3.6040405@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.14.0.111121 acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Salvatore Orlando Subject: Re: [Xen-API] [Openstack] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 You need to install the xenapi plugins: If you are using devstack (https://github.com/openstack-dev/devstack), the code below from build_domU.sh does this for you. # Checkout nova if [ ! -d $TOP_DIR/nova ]; then env GIT_SSL_NO_VERIFY=true git clone $NOVA_REPO cd $TOP_DIR/nova git checkout $NOVA_BRANCH fi # Install plugins cp -pr $TOP_DIR/nova/plugins/xenserver/xenapi/etc/xapi.d /etc/ chmod a+x /etc/xapi.d/plugins/* yum --enablerepo=base install -y parted mkdir -p /boot/guest Thanks, Renuka. On 3/12/12 10:53 PM, "Thomas Goirand" wrote: >Hi, > >I am trying to setup nova-compute with a Kronos setup. Everything comes >from the packages in SID (including nova-xcp-network and >nova-xcp-pluggins in the dom0, which we now package in Debian). > >When starting nova-compute, I have a python stack dump caused by a >XENAPI_PLUGIN_FAILURE. I have attached the nova-compute.log and >xcp-xapi.log files showing the trace of the crash. > >Ewan, Mike, Jon, do you know what's going on? > >Also, my understanding of Quantum is that it's for Openstack + KVM, and >that XCP doesn't need it, as the xcp-networkd will do the vFlows work by >itself. Am I right? How does it work? > >BTW, I'm writing an automated script, inspired from Ghe's debostack, for >setting-up a domU that would connect to XCP. I might be a good idea to >run this as a Jenkins job. Once I have the above working (eg: Openstack >working with Kronos), I'll share the script, so we always make sure >everything works. > >Let me know, >Cheers, > >Thomas Goirand (zigo) _______________________________________________ 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 16 15:36:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8ZB5-0002k8-8I; Fri, 16 Mar 2012 15:34:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7V8a-0006od-UJ for xen-api@lists.xen.org; Tue, 13 Mar 2012 17:03:53 +0000 Received: from [85.158.143.35:40979] by server-1.bemta-4.messagelabs.com id 8F/C5-20925-8FD7F5F4; Tue, 13 Mar 2012 17:03:52 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-6.tower-21.messagelabs.com!1331658230!11016723!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3140 invoked from network); 13 Mar 2012 17:03:51 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2012 17:03:51 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 2947FFE436; Tue, 13 Mar 2012 17:05:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=DvPu6WbOc oqeaT0ASTOG4MXjTIo=; b=fAPWfEtuVK7Fo0ix1XQcQzytu8+/jWk9/3LjXDTYn o8HBniiQMnKkFhStqEjH2MDqlfeHjqy9TdNYJoF+q2UatD/o9kEAo53b6kPdb7It w+hhsyVMYzbuMaGH2khovPVKIJNXtZbZUmFEZ02cJvbaYmNZhVwGMGd2iu0VzQ4f fc= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=syu jw7hgQ2vneiPNiVMu4/wrBgSfEHKqlMG5KfEiTQehQTkyuCxB7p0R2199TeiRHwb PP7pmUxkuc4R24+WBx7zsPGytY5emBAeQmi7t7cwkwt7UYc4uP1mFd8AznnQ8dSl mND1jzokDronvYtutgiYcZbFcOWL3+jj8Aqan9wE= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 19D40FE25C; Tue, 13 Mar 2012 17:05:05 +0000 (UTC) Message-ID: <4F5F7DF1.6070909@goirand.fr> Date: Wed, 14 Mar 2012 01:03:45 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: "Armando M." References: <4F5F10AA.1040206@goirand.fr> In-Reply-To: X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Renuka Apte , Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 all, Thanks for those trying to help. Indeed, it was a stupid Unix right issue. The python scripts of nova for XCP aren't chmod +x in the Git (well, in fact, some are, some aren't chmod +x). Now it does seem to work. I'm testing more now, the debian packaging already chmod +x the python files now. Sorry for the noise, Thomas _______________________________________________ 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 16 15:36:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8ZB5-0002k8-8I; Fri, 16 Mar 2012 15:34:51 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7V8a-0006od-UJ for xen-api@lists.xen.org; Tue, 13 Mar 2012 17:03:53 +0000 Received: from [85.158.143.35:40979] by server-1.bemta-4.messagelabs.com id 8F/C5-20925-8FD7F5F4; Tue, 13 Mar 2012 17:03:52 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-6.tower-21.messagelabs.com!1331658230!11016723!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3140 invoked from network); 13 Mar 2012 17:03:51 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Mar 2012 17:03:51 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 2947FFE436; Tue, 13 Mar 2012 17:05:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=DvPu6WbOc oqeaT0ASTOG4MXjTIo=; b=fAPWfEtuVK7Fo0ix1XQcQzytu8+/jWk9/3LjXDTYn o8HBniiQMnKkFhStqEjH2MDqlfeHjqy9TdNYJoF+q2UatD/o9kEAo53b6kPdb7It w+hhsyVMYzbuMaGH2khovPVKIJNXtZbZUmFEZ02cJvbaYmNZhVwGMGd2iu0VzQ4f fc= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=syu jw7hgQ2vneiPNiVMu4/wrBgSfEHKqlMG5KfEiTQehQTkyuCxB7p0R2199TeiRHwb PP7pmUxkuc4R24+WBx7zsPGytY5emBAeQmi7t7cwkwt7UYc4uP1mFd8AznnQ8dSl mND1jzokDronvYtutgiYcZbFcOWL3+jj8Aqan9wE= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id 19D40FE25C; Tue, 13 Mar 2012 17:05:05 +0000 (UTC) Message-ID: <4F5F7DF1.6070909@goirand.fr> Date: Wed, 14 Mar 2012 01:03:45 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: "Armando M." References: <4F5F10AA.1040206@goirand.fr> In-Reply-To: X-Enigmail-Version: 1.0.1 X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Renuka Apte , Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 all, Thanks for those trying to help. Indeed, it was a stupid Unix right issue. The python scripts of nova for XCP aren't chmod +x in the Git (well, in fact, some are, some aren't chmod +x). Now it does seem to work. I'm testing more now, the debian packaging already chmod +x the python files now. Sorry for the noise, Thomas _______________________________________________ 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 16 15:36:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8ZB4-0002jl-Tp; Fri, 16 Mar 2012 15:34:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7OzD-0006RE-Kv for xen-api@lists.xen.org; Tue, 13 Mar 2012 10:29:47 +0000 Received: from [85.158.143.99:42469] by server-1.bemta-4.messagelabs.com id BB/63-20925-A912F5F4; Tue, 13 Mar 2012 10:29:46 +0000 X-Env-Sender: amigliaccio@internap.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1331634584!18025912!1 X-Originating-IP: [63.251.68.28] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29411 invoked from network); 13 Mar 2012 10:29:46 -0000 Received: from mx4.internap.com (HELO mx4.internap.com) (63.251.68.28) by server-13.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 13 Mar 2012 10:29:46 -0000 Received: from mail-bk0-f44.google.com ([209.85.214.44]) by mx4.internap.com with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.60) (envelope-from ) id 1S7OzA-0003Pj-0K for xen-api@lists.xen.org; Tue, 13 Mar 2012 06:29:44 -0400 Received: by bkuw5 with SMTP id w5so311975bku.31 for ; Tue, 13 Mar 2012 03:29:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=G2jJzOg5gMBIMDMdbzDzuL4kos70ve1a5a5w7fRyu/k=; b=otE5bK4OPjlrf7mNRKMBS2ELoBlX/A4SNzjoQw0/3clmIvNBOMGUfW3OAOcguHqi9n 0fviFDcD5BZsbExTTpKXLfg2xd2m55dgUuOXApVoEvP+nCNnDx4B37y63hGJxkLSX+lI PkXgTIqeRl6OubYjrqj+mvUwjZBIdze+O/HOwa2uyfplqG9vWwPxGqFFgjWO9sP+S1cB iC/l6jHqIq2rRZiOSZ+I9jAp8xKrm5qHabImtIqlVtaXiooHocuJZhT1HXYPzNk432Qb DayczQNE4gIg3RFOr5yUHvOa29c0TLWNzGV1pi+GtCKVkN7zNQHAPeZBLHQWvIupwBVM cbmg== Received: by 10.205.132.73 with SMTP id ht9mr1698790bkc.46.1331634582286; Tue, 13 Mar 2012 03:29:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.166.79 with HTTP; Tue, 13 Mar 2012 03:29:22 -0700 (PDT) In-Reply-To: <4F5F10AA.1040206@goirand.fr> References: <4F5F10AA.1040206@goirand.fr> From: "Armando M." Date: Tue, 13 Mar 2012 10:29:22 +0000 X-Google-Sender-Auth: bsSdZWFJBoiZl5_uqLHbobBmSrI Message-ID: To: Thomas Goirand X-Gm-Message-State: ALoCoQkVim8rxYYFHTvVEm8wuBlMIW6FCMR5w/St/k5VAJ6OJLmLqxW1hKyu/e6Vib+IOImuFSVz X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Renuka Apte , Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Your stacktrace: ['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', ''] 2012-03-13 05:41:32 ERROR nova.virt.xenapi.host [-] The call to host_data returned an error: ['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', '']. 2012-03-13 05:41:32 CRITICAL nova [-] 'str' object does not support item assignment (nova): TRACE: Traceback (most recent call last): (nova): TRACE: File "/usr/bin/nova-compute", line 49, in (nova): TRACE: service.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 413, in wait (nova): TRACE: _launcher.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 131, in wait (nova): TRACE: service.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 166, in wait (nova): TRACE: return self._exit_event.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait (nova): TRACE: return hubs.get_hub().switch() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 177, in switch (nova): TRACE: return self.greenlet.switch() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in main (nova): TRACE: result =3D function(*args, **kwargs) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 101, in run_server (nova): TRACE: server.start() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 174, in start (nova): TRACE: self.manager.update_available_resource(ctxt) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2293, in update_available_resource (nova): TRACE: self.driver.update_available_resource(context, self.host) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 398, in update_available_resource (nova): TRACE: host_stats =3D self.get_host_stats(refresh=3DTrue) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 472, in get_host_stats (nova): TRACE: return self.host_state.get_host_stats(refresh=3Drefresh) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 187, in host_state (nova): TRACE: self._host_state =3D host.HostState(self._session) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py", line 110, in __init__ (nova): TRACE: self.update_status() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py", line 137, in update_status (nova): TRACE: data["disk_total"] =3D total (nova): TRACE: TypeError: 'str' object does not support item assignment (nova): TRACE: Says that what it's been returned from the plugin function 'host_data' (located in /etc/xapi.d/plugins/xenhost) is not what it is expected by nova-compute. Nova-compute expects a dictionary and it's gets a str, probably an error message. Try to trace what's going on in the plugin code or log the content of 'data' available in host.py. Perhaps your nova and xenserver plugins are not in sync? On Tue, Mar 13, 2012 at 9:17 AM, Thomas Goirand wrote: > On 03/13/2012 02:32 PM, Renuka Apte wrote: >> You need to install the xenapi plugins: >> >> If you are using devstack (https://github.com/openstack-dev/devstack), t= he >> code below from build_domU.sh does this for you. > > I'm part of the debian Openstack packaging team, and I worked with Mike > on packaging XCP in Debian (project Kronos). I do not wish to try > devstack, I wish to fix the Debian packaging! > >> # Checkout nova >> if [ ! -d $TOP_DIR/nova ]; then >> =A0 =A0 env GIT_SSL_NO_VERIFY=3Dtrue git clone $NOVA_REPO >> =A0 =A0 cd $TOP_DIR/nova >> =A0 =A0 git checkout $NOVA_BRANCH >> fi >> >> # Install plugins >> cp -pr $TOP_DIR/nova/plugins/xenserver/xenapi/etc/xapi.d /etc/ >> chmod a+x /etc/xapi.d/plugins/* >> yum --enablerepo=3Dbase install -y parted >> mkdir -p /boot/guest > > I'm not using CentOS, but Debian (project Kronos). And in there, you > just need to do: > > apt-get install nova-xcp-plugins nova-xcp-network > > which installs the above in the correct folders (which are *NOT* > the same as for CentOS). I'd love to have a bit of help from Citrix to > test all this by the way. > > Thomas > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to =A0 =A0 : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help =A0 : https://help.launchpad.net/ListHelp _______________________________________________ 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 16 15:36:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 15:36:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8ZB4-0002jl-Tp; Fri, 16 Mar 2012 15:34:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S7OzD-0006RE-Kv for xen-api@lists.xen.org; Tue, 13 Mar 2012 10:29:47 +0000 Received: from [85.158.143.99:42469] by server-1.bemta-4.messagelabs.com id BB/63-20925-A912F5F4; Tue, 13 Mar 2012 10:29:46 +0000 X-Env-Sender: amigliaccio@internap.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1331634584!18025912!1 X-Originating-IP: [63.251.68.28] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29411 invoked from network); 13 Mar 2012 10:29:46 -0000 Received: from mx4.internap.com (HELO mx4.internap.com) (63.251.68.28) by server-13.tower-216.messagelabs.com with AES256-SHA encrypted SMTP; 13 Mar 2012 10:29:46 -0000 Received: from mail-bk0-f44.google.com ([209.85.214.44]) by mx4.internap.com with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.60) (envelope-from ) id 1S7OzA-0003Pj-0K for xen-api@lists.xen.org; Tue, 13 Mar 2012 06:29:44 -0400 Received: by bkuw5 with SMTP id w5so311975bku.31 for ; Tue, 13 Mar 2012 03:29:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=G2jJzOg5gMBIMDMdbzDzuL4kos70ve1a5a5w7fRyu/k=; b=otE5bK4OPjlrf7mNRKMBS2ELoBlX/A4SNzjoQw0/3clmIvNBOMGUfW3OAOcguHqi9n 0fviFDcD5BZsbExTTpKXLfg2xd2m55dgUuOXApVoEvP+nCNnDx4B37y63hGJxkLSX+lI PkXgTIqeRl6OubYjrqj+mvUwjZBIdze+O/HOwa2uyfplqG9vWwPxGqFFgjWO9sP+S1cB iC/l6jHqIq2rRZiOSZ+I9jAp8xKrm5qHabImtIqlVtaXiooHocuJZhT1HXYPzNk432Qb DayczQNE4gIg3RFOr5yUHvOa29c0TLWNzGV1pi+GtCKVkN7zNQHAPeZBLHQWvIupwBVM cbmg== Received: by 10.205.132.73 with SMTP id ht9mr1698790bkc.46.1331634582286; Tue, 13 Mar 2012 03:29:42 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.166.79 with HTTP; Tue, 13 Mar 2012 03:29:22 -0700 (PDT) In-Reply-To: <4F5F10AA.1040206@goirand.fr> References: <4F5F10AA.1040206@goirand.fr> From: "Armando M." Date: Tue, 13 Mar 2012 10:29:22 +0000 X-Google-Sender-Auth: bsSdZWFJBoiZl5_uqLHbobBmSrI Message-ID: To: Thomas Goirand X-Gm-Message-State: ALoCoQkVim8rxYYFHTvVEm8wuBlMIW6FCMR5w/St/k5VAJ6OJLmLqxW1hKyu/e6Vib+IOImuFSVz X-Mailman-Approved-At: Fri, 16 Mar 2012 15:34:47 +0000 Cc: Renuka Apte , Mike McClurg , "openstack@lists.launchpad.net" , Ewan Mellor , PKG OpenStack , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [Openstack] [Openstack-devel] XENAPI_PLUGIN_FAILURE with kronos X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Your stacktrace: ['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', ''] 2012-03-13 05:41:32 ERROR nova.virt.xenapi.host [-] The call to host_data returned an error: ['XENAPI_PLUGIN_FAILURE', 'non-zero exit', '', '']. 2012-03-13 05:41:32 CRITICAL nova [-] 'str' object does not support item assignment (nova): TRACE: Traceback (most recent call last): (nova): TRACE: File "/usr/bin/nova-compute", line 49, in (nova): TRACE: service.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 413, in wait (nova): TRACE: _launcher.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 131, in wait (nova): TRACE: service.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 166, in wait (nova): TRACE: return self._exit_event.wait() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait (nova): TRACE: return hubs.get_hub().switch() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 177, in switch (nova): TRACE: return self.greenlet.switch() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/eventlet/greenthread.py", line 192, in main (nova): TRACE: result =3D function(*args, **kwargs) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 101, in run_server (nova): TRACE: server.start() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/service.py", line 174, in start (nova): TRACE: self.manager.update_available_resource(ctxt) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2293, in update_available_resource (nova): TRACE: self.driver.update_available_resource(context, self.host) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 398, in update_available_resource (nova): TRACE: host_stats =3D self.get_host_stats(refresh=3DTrue) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 472, in get_host_stats (nova): TRACE: return self.host_state.get_host_stats(refresh=3Drefresh) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py", line 187, in host_state (nova): TRACE: self._host_state =3D host.HostState(self._session) (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py", line 110, in __init__ (nova): TRACE: self.update_status() (nova): TRACE: File "/usr/lib/python2.7/dist-packages/nova/virt/xenapi/host.py", line 137, in update_status (nova): TRACE: data["disk_total"] =3D total (nova): TRACE: TypeError: 'str' object does not support item assignment (nova): TRACE: Says that what it's been returned from the plugin function 'host_data' (located in /etc/xapi.d/plugins/xenhost) is not what it is expected by nova-compute. Nova-compute expects a dictionary and it's gets a str, probably an error message. Try to trace what's going on in the plugin code or log the content of 'data' available in host.py. Perhaps your nova and xenserver plugins are not in sync? On Tue, Mar 13, 2012 at 9:17 AM, Thomas Goirand wrote: > On 03/13/2012 02:32 PM, Renuka Apte wrote: >> You need to install the xenapi plugins: >> >> If you are using devstack (https://github.com/openstack-dev/devstack), t= he >> code below from build_domU.sh does this for you. > > I'm part of the debian Openstack packaging team, and I worked with Mike > on packaging XCP in Debian (project Kronos). I do not wish to try > devstack, I wish to fix the Debian packaging! > >> # Checkout nova >> if [ ! -d $TOP_DIR/nova ]; then >> =A0 =A0 env GIT_SSL_NO_VERIFY=3Dtrue git clone $NOVA_REPO >> =A0 =A0 cd $TOP_DIR/nova >> =A0 =A0 git checkout $NOVA_BRANCH >> fi >> >> # Install plugins >> cp -pr $TOP_DIR/nova/plugins/xenserver/xenapi/etc/xapi.d /etc/ >> chmod a+x /etc/xapi.d/plugins/* >> yum --enablerepo=3Dbase install -y parted >> mkdir -p /boot/guest > > I'm not using CentOS, but Debian (project Kronos). And in there, you > just need to do: > > apt-get install nova-xcp-plugins nova-xcp-network > > which installs the above in the correct folders (which are *NOT* > the same as for CentOS). I'd love to have a bit of help from Citrix to > test all this by the way. > > Thomas > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to =A0 =A0 : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help =A0 : https://help.launchpad.net/ListHelp _______________________________________________ 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 16 18:21:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 18:21:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8bm2-0007Bh-IC; Fri, 16 Mar 2012 18:21:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8bm0-0007BO-DB for xen-api@lists.xen.org; Fri, 16 Mar 2012 18:21:08 +0000 Received: from [85.158.143.99:31075] by server-1.bemta-4.messagelabs.com id 25/9D-20925-394836F4; Fri, 16 Mar 2012 18:21:07 +0000 X-Env-Sender: outbackdingo@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1331922066!19243294!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28210 invoked from network); 16 Mar 2012 18:21:07 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 18:21:07 -0000 Received: by bkcjg9 with SMTP id jg9so3871531bkc.32 for ; Fri, 16 Mar 2012 11:21:06 -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=BoUNfXkLvLxLHHTfYnOz2Zu5YVJLdZj+obzuiJC0YLo=; b=cR4uxYHh7lSyW2ijiWpUnGMk8hGMG2HJSJci3P2KaNzCjig8MVwuQGn5rMLyfpB142 VLOAAXnUNB3da07TBZrqQXragsJcdY1MIb+rfE1HHyCKywugG8Q0T9iAyZtD8bQERY7P yd6rx4d5Jh/sNJ2dGr242ROrle5/gaaJMYwHVZEUlGiwa/19dcw45c2yPtxT8L4U7Cua YwZfkaIsZMj4CcfUMVpKjyNMm0yNueed8id8E06ZwrHGI7uJyfaCP8EQmx3VBVWwoZhc tm0jTo9gllSX3GXwwL8P6G5S8IoJWZ2ygRf/3OoQElxTd5Fl3zPRmS1zv3V0iaTUTD0q nrxQ== MIME-Version: 1.0 Received: by 10.204.143.138 with SMTP id v10mr1289537bku.99.1331922066644; Fri, 16 Mar 2012 11:21:06 -0700 (PDT) Received: by 10.204.174.75 with HTTP; Fri, 16 Mar 2012 11:21:06 -0700 (PDT) Date: Fri, 16 Mar 2012 14:21:06 -0400 Message-ID: From: Outback Dingo To: xen-api@lists.xen.org Subject: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 So in Cloustack 3.0 trying to add an XCP host fails with CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6, XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.90, so i need it to emulate XCP 1.1.0 but xapi fails to run with a memory exception It appears that we now need to emulate XCP 1.1, yet doing the API version over ride trick, makes xapi fail with sed -i 's/1\.4\.90/1.1.0/g' xapi [root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start Starting xapi: Fatal error: exception Out_of_memory failed to start xapi. [FAILED] [root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi cp: overwrite `xapi'? y `xapi.original' -> `xapi' So it doesnt appear possible to emulate much other then sed -i 's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupported by CS 3.0 still..... any ideas how to get the version emulation to function _______________________________________________ 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 16 18:21:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 18:21:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8bm2-0007Bh-IC; Fri, 16 Mar 2012 18:21:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8bm0-0007BO-DB for xen-api@lists.xen.org; Fri, 16 Mar 2012 18:21:08 +0000 Received: from [85.158.143.99:31075] by server-1.bemta-4.messagelabs.com id 25/9D-20925-394836F4; Fri, 16 Mar 2012 18:21:07 +0000 X-Env-Sender: outbackdingo@gmail.com X-Msg-Ref: server-5.tower-216.messagelabs.com!1331922066!19243294!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28210 invoked from network); 16 Mar 2012 18:21:07 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-5.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 18:21:07 -0000 Received: by bkcjg9 with SMTP id jg9so3871531bkc.32 for ; Fri, 16 Mar 2012 11:21:06 -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=BoUNfXkLvLxLHHTfYnOz2Zu5YVJLdZj+obzuiJC0YLo=; b=cR4uxYHh7lSyW2ijiWpUnGMk8hGMG2HJSJci3P2KaNzCjig8MVwuQGn5rMLyfpB142 VLOAAXnUNB3da07TBZrqQXragsJcdY1MIb+rfE1HHyCKywugG8Q0T9iAyZtD8bQERY7P yd6rx4d5Jh/sNJ2dGr242ROrle5/gaaJMYwHVZEUlGiwa/19dcw45c2yPtxT8L4U7Cua YwZfkaIsZMj4CcfUMVpKjyNMm0yNueed8id8E06ZwrHGI7uJyfaCP8EQmx3VBVWwoZhc tm0jTo9gllSX3GXwwL8P6G5S8IoJWZ2ygRf/3OoQElxTd5Fl3zPRmS1zv3V0iaTUTD0q nrxQ== MIME-Version: 1.0 Received: by 10.204.143.138 with SMTP id v10mr1289537bku.99.1331922066644; Fri, 16 Mar 2012 11:21:06 -0700 (PDT) Received: by 10.204.174.75 with HTTP; Fri, 16 Mar 2012 11:21:06 -0700 (PDT) Date: Fri, 16 Mar 2012 14:21:06 -0400 Message-ID: From: Outback Dingo To: xen-api@lists.xen.org Subject: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 So in Cloustack 3.0 trying to add an XCP host fails with CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6, XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.90, so i need it to emulate XCP 1.1.0 but xapi fails to run with a memory exception It appears that we now need to emulate XCP 1.1, yet doing the API version over ride trick, makes xapi fail with sed -i 's/1\.4\.90/1.1.0/g' xapi [root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start Starting xapi: Fatal error: exception Out_of_memory failed to start xapi. [FAILED] [root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi cp: overwrite `xapi'? y `xapi.original' -> `xapi' So it doesnt appear possible to emulate much other then sed -i 's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupported by CS 3.0 still..... any ideas how to get the version emulation to function _______________________________________________ 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 16 22:43:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 22:43:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8fs1-0005w9-TP; Fri, 16 Mar 2012 22:43:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8fs0-0005w1-U3 for xen-api@lists.xen.org; Fri, 16 Mar 2012 22:43:37 +0000 Received: from [85.158.138.51:20927] by server-11.bemta-3.messagelabs.com id E2/FD-12049-812C36F4; Fri, 16 Mar 2012 22:43:36 +0000 X-Env-Sender: pip.chan@gmail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1331937813!18053244!1 X-Originating-IP: [209.85.210.173] 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-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17169 invoked from network); 16 Mar 2012 22:43:34 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 22:43:34 -0000 Received: by iafj26 with SMTP id j26so7450011iaf.32 for ; Fri, 16 Mar 2012 15:43:33 -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=gny66OwqMXDkamzKvlKryI59k3+74zlTf/lFq6JvgnQ=; b=H8KEN7cKfOcSGZbFWOq04apHjZBdnYJIrpusn3qjfJDEk6vTUyh30OyJdWcr1rM4Ir Qk4U8OizbXv8cPeeyC9JzgWDkld/8alWuxWOkugQT/9+2EXovxmxQxHbyVBJ//TbwZED HW28e9fzbPZU2vsG78m5jYxnuAfNv2dFTcPAJ/EaGPsQoNnL9NdHsJIFD0AFQf7vYdWy 1DH3vby/nA+nUC2Dd4TgHxNBR2UNOvCWH8zzvjX4eUOYWFSYfHRkQez9DpeQUoeb+Rnj pAiq2GmDknR8qCKYYNo75mRXr/EYqdymgYiFWfuBV+KFvzhWr0MqobNRvHelQHMrhw/M PxSA== MIME-Version: 1.0 Received: by 10.50.222.196 with SMTP id qo4mr666208igc.59.1331937812831; Fri, 16 Mar 2012 15:43:32 -0700 (PDT) Received: by 10.42.135.200 with HTTP; Fri, 16 Mar 2012 15:43:32 -0700 (PDT) Received: by 10.42.135.200 with HTTP; Fri, 16 Mar 2012 15:43:32 -0700 (PDT) In-Reply-To: References: Date: Sat, 17 Mar 2012 06:43:32 +0800 Message-ID: From: Philip Chan To: Outback Dingo Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2868138907440219597==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2868138907440219597== Content-Type: multipart/alternative; boundary=14dae9340daf325ca704bb63f0bd --14dae9340daf325ca704bb63f0bd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Try 1.1.00 On 2012-3-17 =E4=B8=8A=E5=8D=882:22, "Outback Dingo" wrote: > So in Cloustack 3.0 trying to add an XCP host fails with > > CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6, > XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.90, > so i need it to emulate XCP 1.1.0 but xapi fails to run with a memory > exception > > It appears that we now need to emulate XCP 1.1, yet doing the API > version over ride trick, makes xapi fail with > > > sed -i 's/1\.4\.90/1.1.0/g' xapi > [root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start > Starting xapi: Fatal error: exception Out_of_memory > failed to start xapi. [FAILED] > [root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi > cp: overwrite `xapi'? y > `xapi.original' -> `xapi' > > > So it doesnt appear possible to emulate much other then sed -i > 's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupported by CS 3.0 > still..... > > any ideas how to get the version emulation to function > > _______________________________________________ > xen-api mailing list > xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --14dae9340daf325ca704bb63f0bd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Try 1.1.00

On 2012-3-17 =E4=B8=8A=E5=8D=882:22, "Outba= ck Dingo" <outbackdingo@g= mail.com> wrote:
So in Cloustack 3.0 trying to add an XCP host fails with

CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6,
XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.90,
so i need it to emulate XCP 1.1.0 but xapi fails to run with a memory
exception

It appears that we now need to emulate XCP 1.1, yet doing the API
version over ride trick, makes xapi fail with


sed -i 's/1\.4\.90/1.1.0/g' xapi
[root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start
Starting xapi: Fatal error: exception Out_of_memory
failed to start xapi. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0[FAILED]
[root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi
cp: overwrite `xapi'? y
`xapi.original' -> `xapi'


So it doesnt appear possible to emulate much other then sed -i
's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupported by CS = 3.0
still.....

any ideas how to get the version emulation to function

_______________________________________________
xen-api mailing list
xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--14dae9340daf325ca704bb63f0bd-- --===============2868138907440219597== 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 --===============2868138907440219597==-- From xen-api-bounces@lists.xen.org Fri Mar 16 22:43:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 22:43:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8fs1-0005w9-TP; Fri, 16 Mar 2012 22:43:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8fs0-0005w1-U3 for xen-api@lists.xen.org; Fri, 16 Mar 2012 22:43:37 +0000 Received: from [85.158.138.51:20927] by server-11.bemta-3.messagelabs.com id E2/FD-12049-812C36F4; Fri, 16 Mar 2012 22:43:36 +0000 X-Env-Sender: pip.chan@gmail.com X-Msg-Ref: server-5.tower-174.messagelabs.com!1331937813!18053244!1 X-Originating-IP: [209.85.210.173] 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-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17169 invoked from network); 16 Mar 2012 22:43:34 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-5.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 22:43:34 -0000 Received: by iafj26 with SMTP id j26so7450011iaf.32 for ; Fri, 16 Mar 2012 15:43:33 -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=gny66OwqMXDkamzKvlKryI59k3+74zlTf/lFq6JvgnQ=; b=H8KEN7cKfOcSGZbFWOq04apHjZBdnYJIrpusn3qjfJDEk6vTUyh30OyJdWcr1rM4Ir Qk4U8OizbXv8cPeeyC9JzgWDkld/8alWuxWOkugQT/9+2EXovxmxQxHbyVBJ//TbwZED HW28e9fzbPZU2vsG78m5jYxnuAfNv2dFTcPAJ/EaGPsQoNnL9NdHsJIFD0AFQf7vYdWy 1DH3vby/nA+nUC2Dd4TgHxNBR2UNOvCWH8zzvjX4eUOYWFSYfHRkQez9DpeQUoeb+Rnj pAiq2GmDknR8qCKYYNo75mRXr/EYqdymgYiFWfuBV+KFvzhWr0MqobNRvHelQHMrhw/M PxSA== MIME-Version: 1.0 Received: by 10.50.222.196 with SMTP id qo4mr666208igc.59.1331937812831; Fri, 16 Mar 2012 15:43:32 -0700 (PDT) Received: by 10.42.135.200 with HTTP; Fri, 16 Mar 2012 15:43:32 -0700 (PDT) Received: by 10.42.135.200 with HTTP; Fri, 16 Mar 2012 15:43:32 -0700 (PDT) In-Reply-To: References: Date: Sat, 17 Mar 2012 06:43:32 +0800 Message-ID: From: Philip Chan To: Outback Dingo Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2868138907440219597==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2868138907440219597== Content-Type: multipart/alternative; boundary=14dae9340daf325ca704bb63f0bd --14dae9340daf325ca704bb63f0bd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Try 1.1.00 On 2012-3-17 =E4=B8=8A=E5=8D=882:22, "Outback Dingo" wrote: > So in Cloustack 3.0 trying to add an XCP host fails with > > CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6, > XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.90, > so i need it to emulate XCP 1.1.0 but xapi fails to run with a memory > exception > > It appears that we now need to emulate XCP 1.1, yet doing the API > version over ride trick, makes xapi fail with > > > sed -i 's/1\.4\.90/1.1.0/g' xapi > [root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start > Starting xapi: Fatal error: exception Out_of_memory > failed to start xapi. [FAILED] > [root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi > cp: overwrite `xapi'? y > `xapi.original' -> `xapi' > > > So it doesnt appear possible to emulate much other then sed -i > 's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupported by CS 3.0 > still..... > > any ideas how to get the version emulation to function > > _______________________________________________ > xen-api mailing list > xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --14dae9340daf325ca704bb63f0bd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Try 1.1.00

On 2012-3-17 =E4=B8=8A=E5=8D=882:22, "Outba= ck Dingo" <outbackdingo@g= mail.com> wrote:
So in Cloustack 3.0 trying to add an XCP host fails with

CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6,
XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.90,
so i need it to emulate XCP 1.1.0 but xapi fails to run with a memory
exception

It appears that we now need to emulate XCP 1.1, yet doing the API
version over ride trick, makes xapi fail with


sed -i 's/1\.4\.90/1.1.0/g' xapi
[root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start
Starting xapi: Fatal error: exception Out_of_memory
failed to start xapi. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0[FAILED]
[root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi
cp: overwrite `xapi'? y
`xapi.original' -> `xapi'


So it doesnt appear possible to emulate much other then sed -i
's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupported by CS = 3.0
still.....

any ideas how to get the version emulation to function

_______________________________________________
xen-api mailing list
xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--14dae9340daf325ca704bb63f0bd-- --===============2868138907440219597== 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 --===============2868138907440219597==-- From xen-api-bounces@lists.xen.org Fri Mar 16 23:55:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 23:55:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8gzb-0007ej-J8; Fri, 16 Mar 2012 23:55:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8gzZ-0007ec-HR for xen-api@lists.xen.org; Fri, 16 Mar 2012 23:55:29 +0000 Received: from [85.158.138.51:24164] by server-7.bemta-3.messagelabs.com id B7/30-07528-0F2D36F4; Fri, 16 Mar 2012 23:55:28 +0000 X-Env-Sender: outbackdingo@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1331942127!17848802!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10686 invoked from network); 16 Mar 2012 23:55:27 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 23:55:27 -0000 Received: by bkcjg9 with SMTP id jg9so4048362bkc.32 for ; Fri, 16 Mar 2012 16:55:27 -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:content-transfer-encoding; bh=4RE73I5Wf4RhozdgJok1ObNQIJ9M96YDh2oNQYTAYpU=; b=RoIL+q3voZwnr0ZeuJuPy/PDCDJ2m04ryn8re0koXXa0pQ/GlWaFY7TJ4mOelPgKG6 5FXrAdtTq1e98Ow7ZQUw0dGzHabuRBM/tFTG8n1CeGNBe2BvJjACIDk7I+6cvQr/IEyw eqFsWlO/25wDgRGQlHVRgDFfQxu0aZHgEmHVN84slnn1oYCRzg/0NzFrb9ika/SegTnF HE4sacr+ajH8tjGDdvMdl8NkqpWjmWXv9ygrp9ZKKuvglDVdoSzwWfWW8Y3A0ikHK5tI O86RhaR9Asi6V9GQ0U8o6xR8VnIdp9O7ByJRhBoMdpTGksQr/RXg3lSEtgc0FvUQ70r7 xa1w== MIME-Version: 1.0 Received: by 10.204.151.86 with SMTP id b22mr1673480bkw.81.1331942127042; Fri, 16 Mar 2012 16:55:27 -0700 (PDT) Received: by 10.204.174.75 with HTTP; Fri, 16 Mar 2012 16:55:27 -0700 (PDT) In-Reply-To: References: Date: Fri, 16 Mar 2012 19:55:27 -0400 Message-ID: From: Outback Dingo To: Philip Chan Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gRnJpLCBNYXIgMTYsIDIwMTIgYXQgNjo0MyBQTSwgUGhpbGlwIENoYW4gPHBpcC5jaGFuQGdt YWlsLmNvbT4gd3JvdGU6Cj4gVHJ5IDEuMS4wMAo+CgpXZWxwIHVzaW5nIDEuMS4wMCBkaWQgaW4g ZmFjdCBhbGxvdyB4YXBpIHRvIHN0YXJ0IHVwLCBidXQgc3RpbGwgQ1MKZmFpbHMgdG8gYWRkIHRo ZSBob3N0LCBhdCBsZWFzdCB4YXBpIGRpZCBzdGFydAoKPiBPbiAyMDEyLTMtMTcg5LiK5Y2IMjoy MiwgIk91dGJhY2sgRGluZ28iIDxvdXRiYWNrZGluZ29AZ21haWwuY29tPiB3cm90ZToKPj4KPj4g U28gaW4gQ2xvdXN0YWNrIDMuMCB0cnlpbmcgdG8gYWRkIGFuIFhDUCBob3N0IGZhaWxzIHdpdGgK Pj4KPj4gQ1MgbG9nIHNheXMgT25seSBzdXBwb3J0IFhDUCAxLjAuMCwgWENQIDEuMS4wLCBYZW5T ZXJ2ZXIgNS42LAo+PiBYZW5TZXJ2ZXIgNS42IEZQMSBhbmQgWGVuU2VydmVyIDUuNiBTUDIsIGJ1 dCB0aGlzIG9uZSBpcyBYQ1AgMS40LjkwLAo+PiBzbyBpIG5lZWQgaXQgdG8gZW11bGF0ZSBYQ1Ag MS4xLjAgYnV0IHhhcGkgZmFpbHMgdG8gcnVuIHdpdGggYSBtZW1vcnkKPj4gZXhjZXB0aW9uCj4+ Cj4+IEl0IGFwcGVhcnMgdGhhdCB3ZSBub3cgbmVlZCB0byBlbXVsYXRlIFhDUCAxLjEsIHlldCBk b2luZyB0aGUgQVBJCj4+IHZlcnNpb24gb3ZlciByaWRlIHRyaWNrLCBtYWtlcyB4YXBpIGZhaWwg d2l0aAo+Pgo+Pgo+PiBzZWQgLWkgJ3MvMVwuNFwuOTAvMS4xLjAvZycgeGFwaQo+PiBbcm9vdEB4 ZW5zZXJ2ZXItZmh6bWVnZm4gYmluXSMgL2V0Yy9pbml0LmQveGFwaSBzdGFydAo+PiBTdGFydGlu ZyB4YXBpOiBGYXRhbCBlcnJvcjogZXhjZXB0aW9uIE91dF9vZl9tZW1vcnkKPj4gZmFpbGVkIHRv IHN0YXJ0IHhhcGkuIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg IMKgIMKgIMKgIMKgW0ZBSUxFRF0KPj4gW3Jvb3RAeGVuc2VydmVyLWZoem1lZ2ZuIGJpbl0jIGNw IC12cCB4YXBpLm9yaWdpbmFsIHhhcGkKPj4gY3A6IG92ZXJ3cml0ZSBgeGFwaSc/IHkKPj4gYHhh cGkub3JpZ2luYWwnIC0+IGB4YXBpJwo+Pgo+Pgo+PiBTbyBpdCBkb2VzbnQgYXBwZWFyIHBvc3Np YmxlIHRvIGVtdWxhdGUgbXVjaCBvdGhlciB0aGVuIHNlZCAtaQo+PiAncy8xXC40XC45MC82LjAu OTkvZycgeGFwaSAsIGhvd2V2ZXIgNi4wIGlzIGFsc28gdW5zdXBwb3J0ZWQgYnkgQ1MgMy4wCj4+ IHN0aWxsLi4uLi4KPj4KPj4gYW55IGlkZWFzIGhvdyB0byBnZXQgdGhlIHZlcnNpb24gZW11bGF0 aW9uIHRvIGZ1bmN0aW9uCj4+Cj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCj4+IHhlbi1hcGkgbWFpbGluZyBsaXN0Cj4+IHhlbi1hcGlAbGlzdHMueGVu Lm9yZwo+PiBodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVu LWFwaQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KeGVu LWFwaSBtYWlsaW5nIGxpc3QKeGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4u b3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Mar 16 23:55:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 23:55:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8gzb-0007ej-J8; Fri, 16 Mar 2012 23:55:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8gzZ-0007ec-HR for xen-api@lists.xen.org; Fri, 16 Mar 2012 23:55:29 +0000 Received: from [85.158.138.51:24164] by server-7.bemta-3.messagelabs.com id B7/30-07528-0F2D36F4; Fri, 16 Mar 2012 23:55:28 +0000 X-Env-Sender: outbackdingo@gmail.com X-Msg-Ref: server-14.tower-174.messagelabs.com!1331942127!17848802!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.5; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10686 invoked from network); 16 Mar 2012 23:55:27 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 23:55:27 -0000 Received: by bkcjg9 with SMTP id jg9so4048362bkc.32 for ; Fri, 16 Mar 2012 16:55:27 -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:content-transfer-encoding; bh=4RE73I5Wf4RhozdgJok1ObNQIJ9M96YDh2oNQYTAYpU=; b=RoIL+q3voZwnr0ZeuJuPy/PDCDJ2m04ryn8re0koXXa0pQ/GlWaFY7TJ4mOelPgKG6 5FXrAdtTq1e98Ow7ZQUw0dGzHabuRBM/tFTG8n1CeGNBe2BvJjACIDk7I+6cvQr/IEyw eqFsWlO/25wDgRGQlHVRgDFfQxu0aZHgEmHVN84slnn1oYCRzg/0NzFrb9ika/SegTnF HE4sacr+ajH8tjGDdvMdl8NkqpWjmWXv9ygrp9ZKKuvglDVdoSzwWfWW8Y3A0ikHK5tI O86RhaR9Asi6V9GQ0U8o6xR8VnIdp9O7ByJRhBoMdpTGksQr/RXg3lSEtgc0FvUQ70r7 xa1w== MIME-Version: 1.0 Received: by 10.204.151.86 with SMTP id b22mr1673480bkw.81.1331942127042; Fri, 16 Mar 2012 16:55:27 -0700 (PDT) Received: by 10.204.174.75 with HTTP; Fri, 16 Mar 2012 16:55:27 -0700 (PDT) In-Reply-To: References: Date: Fri, 16 Mar 2012 19:55:27 -0400 Message-ID: From: Outback Dingo To: Philip Chan Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gRnJpLCBNYXIgMTYsIDIwMTIgYXQgNjo0MyBQTSwgUGhpbGlwIENoYW4gPHBpcC5jaGFuQGdt YWlsLmNvbT4gd3JvdGU6Cj4gVHJ5IDEuMS4wMAo+CgpXZWxwIHVzaW5nIDEuMS4wMCBkaWQgaW4g ZmFjdCBhbGxvdyB4YXBpIHRvIHN0YXJ0IHVwLCBidXQgc3RpbGwgQ1MKZmFpbHMgdG8gYWRkIHRo ZSBob3N0LCBhdCBsZWFzdCB4YXBpIGRpZCBzdGFydAoKPiBPbiAyMDEyLTMtMTcg5LiK5Y2IMjoy MiwgIk91dGJhY2sgRGluZ28iIDxvdXRiYWNrZGluZ29AZ21haWwuY29tPiB3cm90ZToKPj4KPj4g U28gaW4gQ2xvdXN0YWNrIDMuMCB0cnlpbmcgdG8gYWRkIGFuIFhDUCBob3N0IGZhaWxzIHdpdGgK Pj4KPj4gQ1MgbG9nIHNheXMgT25seSBzdXBwb3J0IFhDUCAxLjAuMCwgWENQIDEuMS4wLCBYZW5T ZXJ2ZXIgNS42LAo+PiBYZW5TZXJ2ZXIgNS42IEZQMSBhbmQgWGVuU2VydmVyIDUuNiBTUDIsIGJ1 dCB0aGlzIG9uZSBpcyBYQ1AgMS40LjkwLAo+PiBzbyBpIG5lZWQgaXQgdG8gZW11bGF0ZSBYQ1Ag MS4xLjAgYnV0IHhhcGkgZmFpbHMgdG8gcnVuIHdpdGggYSBtZW1vcnkKPj4gZXhjZXB0aW9uCj4+ Cj4+IEl0IGFwcGVhcnMgdGhhdCB3ZSBub3cgbmVlZCB0byBlbXVsYXRlIFhDUCAxLjEsIHlldCBk b2luZyB0aGUgQVBJCj4+IHZlcnNpb24gb3ZlciByaWRlIHRyaWNrLCBtYWtlcyB4YXBpIGZhaWwg d2l0aAo+Pgo+Pgo+PiBzZWQgLWkgJ3MvMVwuNFwuOTAvMS4xLjAvZycgeGFwaQo+PiBbcm9vdEB4 ZW5zZXJ2ZXItZmh6bWVnZm4gYmluXSMgL2V0Yy9pbml0LmQveGFwaSBzdGFydAo+PiBTdGFydGlu ZyB4YXBpOiBGYXRhbCBlcnJvcjogZXhjZXB0aW9uIE91dF9vZl9tZW1vcnkKPj4gZmFpbGVkIHRv IHN0YXJ0IHhhcGkuIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg IMKgIMKgIMKgIMKgW0ZBSUxFRF0KPj4gW3Jvb3RAeGVuc2VydmVyLWZoem1lZ2ZuIGJpbl0jIGNw IC12cCB4YXBpLm9yaWdpbmFsIHhhcGkKPj4gY3A6IG92ZXJ3cml0ZSBgeGFwaSc/IHkKPj4gYHhh cGkub3JpZ2luYWwnIC0+IGB4YXBpJwo+Pgo+Pgo+PiBTbyBpdCBkb2VzbnQgYXBwZWFyIHBvc3Np YmxlIHRvIGVtdWxhdGUgbXVjaCBvdGhlciB0aGVuIHNlZCAtaQo+PiAncy8xXC40XC45MC82LjAu OTkvZycgeGFwaSAsIGhvd2V2ZXIgNi4wIGlzIGFsc28gdW5zdXBwb3J0ZWQgYnkgQ1MgMy4wCj4+ IHN0aWxsLi4uLi4KPj4KPj4gYW55IGlkZWFzIGhvdyB0byBnZXQgdGhlIHZlcnNpb24gZW11bGF0 aW9uIHRvIGZ1bmN0aW9uCj4+Cj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fCj4+IHhlbi1hcGkgbWFpbGluZyBsaXN0Cj4+IHhlbi1hcGlAbGlzdHMueGVu Lm9yZwo+PiBodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVu LWFwaQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KeGVu LWFwaSBtYWlsaW5nIGxpc3QKeGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4u b3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Fri Mar 16 23:56:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 23:56:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8h0p-0007ha-Q1; Fri, 16 Mar 2012 23:56:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8h0o-0007hO-3M for xen-api@lists.xen.org; Fri, 16 Mar 2012 23:56:46 +0000 Received: from [193.109.254.147:11661] by server-7.bemta-14.messagelabs.com id AD/18-01627-D33D36F4; Fri, 16 Mar 2012 23:56:45 +0000 X-Env-Sender: pip.chan@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1331942203!905971!1 X-Originating-IP: [209.85.210.173] 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-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17120 invoked from network); 16 Mar 2012 23:56:44 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 23:56:44 -0000 Received: by iafj26 with SMTP id j26so7539349iaf.32 for ; Fri, 16 Mar 2012 16:56:42 -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=AvkBZ1nutFv32pBXg4utW6v27kG3R/g8scgL7WevcyI=; b=FQyQB5nrnr8Dn6sPJ/y5tPvoxBIZH9X5+E4Q30SSgaF8ez+/9lM2RIRT/B1lj3R0Xq eX2FjFafYVIG0pTLmW4xBvsrO86PEI/urmLKu8n9FzCjCarutODHdpjX8LRLc0lld2US VIfoS3N0q9Q6bpHxFd2IgJKEgMCNijq37Cx6BDi82iQI9DPmLOb5mEIqEUIfrR2Lht9A i6dj/YU6LxAo3t8NXQlhjO2M3G/lOkD+f8hORFQQ1m3FCIsTET+kPsLpkD2o+FzWXJCx SN9cDap+tXXB5Yd116OJxEUyQ9DzhrFJCsQKiU1JGV9jvQgvIdh+CkVr1a5dj0dOiBYm 9EjQ== MIME-Version: 1.0 Received: by 10.50.194.163 with SMTP id hx3mr776441igc.49.1331942202614; Fri, 16 Mar 2012 16:56:42 -0700 (PDT) Received: by 10.42.135.200 with HTTP; Fri, 16 Mar 2012 16:56:42 -0700 (PDT) Received: by 10.42.135.200 with HTTP; Fri, 16 Mar 2012 16:56:42 -0700 (PDT) In-Reply-To: References: Date: Sat, 17 Mar 2012 07:56:42 +0800 Message-ID: From: Philip Chan To: Outback Dingo Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0378383610777865832==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0378383610777865832== Content-Type: multipart/alternative; boundary=14dae9340cabd9230804bb64f5a3 --14dae9340cabd9230804bb64f5a3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable How about using 6.0.00 On 2012-3-17 =E4=B8=8A=E5=8D=887:55, "Outback Dingo" wrote: > On Fri, Mar 16, 2012 at 6:43 PM, Philip Chan wrote: > > Try 1.1.00 > > > > Welp using 1.1.00 did in fact allow xapi to start up, but still CS > fails to add the host, at least xapi did start > > > On 2012-3-17 =E4=B8=8A=E5=8D=882:22, "Outback Dingo" wrote: > >> > >> So in Cloustack 3.0 trying to add an XCP host fails with > >> > >> CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6, > >> XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.90, > >> so i need it to emulate XCP 1.1.0 but xapi fails to run with a memory > >> exception > >> > >> It appears that we now need to emulate XCP 1.1, yet doing the API > >> version over ride trick, makes xapi fail with > >> > >> > >> sed -i 's/1\.4\.90/1.1.0/g' xapi > >> [root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start > >> Starting xapi: Fatal error: exception Out_of_memory > >> failed to start xapi. [FAILED] > >> [root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi > >> cp: overwrite `xapi'? y > >> `xapi.original' -> `xapi' > >> > >> > >> So it doesnt appear possible to emulate much other then sed -i > >> 's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupported by CS 3.0 > >> still..... > >> > >> any ideas how to get the version emulation to function > >> > >> _______________________________________________ > >> xen-api mailing list > >> xen-api@lists.xen.org > >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --14dae9340cabd9230804bb64f5a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

How about using 6.0.00

On 2012-3-17 =E4=B8=8A=E5=8D=887:55, "Outba= ck Dingo" <outbackdingo@g= mail.com> wrote:
On Fri, Mar 16, 2012 at 6:43 PM, Philip Chan <pip.chan@gmail.com> wrote:
> Try 1.1.00
>

Welp using 1.1.00 did in fact allow xapi to start up, but still CS
fails to add the host, at least xapi did start

> On 2012-3-17 =E4=B8=8A=E5=8D=882:22, "Outback Dingo" <outbackdingo@gmail.com> wrote= :
>>
>> So in Cloustack 3.0 trying to add an XCP host fails with
>>
>> CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6,
>> XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.9= 0,
>> so i need it to emulate XCP 1.1.0 but xapi fails to run with a mem= ory
>> exception
>>
>> It appears that we now need to emulate XCP 1.1, yet doing the API<= br> >> version over ride trick, makes xapi fail with
>>
>>
>> sed -i 's/1\.4\.90/1.1.0/g' xapi
>> [root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start
>> Starting xapi: Fatal error: exception Out_of_memory
>> failed to start xapi. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0[FAILED]
>> [root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi
>> cp: overwrite `xapi'? y
>> `xapi.original' -> `xapi'
>>
>>
>> So it doesnt appear possible to emulate much other then sed -i
>> 's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupport= ed by CS 3.0
>> still.....
>>
>> any ideas how to get the version emulation to function
>>
>> _______________________________________________
>> xen-api mailing list
>> xen-api@lists.xen.org=
>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api=
--14dae9340cabd9230804bb64f5a3-- --===============0378383610777865832== 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 --===============0378383610777865832==-- From xen-api-bounces@lists.xen.org Fri Mar 16 23:56:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 16 Mar 2012 23:56:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8h0p-0007ha-Q1; Fri, 16 Mar 2012 23:56:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8h0o-0007hO-3M for xen-api@lists.xen.org; Fri, 16 Mar 2012 23:56:46 +0000 Received: from [193.109.254.147:11661] by server-7.bemta-14.messagelabs.com id AD/18-01627-D33D36F4; Fri, 16 Mar 2012 23:56:45 +0000 X-Env-Sender: pip.chan@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1331942203!905971!1 X-Originating-IP: [209.85.210.173] 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-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17120 invoked from network); 16 Mar 2012 23:56:44 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Mar 2012 23:56:44 -0000 Received: by iafj26 with SMTP id j26so7539349iaf.32 for ; Fri, 16 Mar 2012 16:56:42 -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=AvkBZ1nutFv32pBXg4utW6v27kG3R/g8scgL7WevcyI=; b=FQyQB5nrnr8Dn6sPJ/y5tPvoxBIZH9X5+E4Q30SSgaF8ez+/9lM2RIRT/B1lj3R0Xq eX2FjFafYVIG0pTLmW4xBvsrO86PEI/urmLKu8n9FzCjCarutODHdpjX8LRLc0lld2US VIfoS3N0q9Q6bpHxFd2IgJKEgMCNijq37Cx6BDi82iQI9DPmLOb5mEIqEUIfrR2Lht9A i6dj/YU6LxAo3t8NXQlhjO2M3G/lOkD+f8hORFQQ1m3FCIsTET+kPsLpkD2o+FzWXJCx SN9cDap+tXXB5Yd116OJxEUyQ9DzhrFJCsQKiU1JGV9jvQgvIdh+CkVr1a5dj0dOiBYm 9EjQ== MIME-Version: 1.0 Received: by 10.50.194.163 with SMTP id hx3mr776441igc.49.1331942202614; Fri, 16 Mar 2012 16:56:42 -0700 (PDT) Received: by 10.42.135.200 with HTTP; Fri, 16 Mar 2012 16:56:42 -0700 (PDT) Received: by 10.42.135.200 with HTTP; Fri, 16 Mar 2012 16:56:42 -0700 (PDT) In-Reply-To: References: Date: Sat, 17 Mar 2012 07:56:42 +0800 Message-ID: From: Philip Chan To: Outback Dingo Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0378383610777865832==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0378383610777865832== Content-Type: multipart/alternative; boundary=14dae9340cabd9230804bb64f5a3 --14dae9340cabd9230804bb64f5a3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable How about using 6.0.00 On 2012-3-17 =E4=B8=8A=E5=8D=887:55, "Outback Dingo" wrote: > On Fri, Mar 16, 2012 at 6:43 PM, Philip Chan wrote: > > Try 1.1.00 > > > > Welp using 1.1.00 did in fact allow xapi to start up, but still CS > fails to add the host, at least xapi did start > > > On 2012-3-17 =E4=B8=8A=E5=8D=882:22, "Outback Dingo" wrote: > >> > >> So in Cloustack 3.0 trying to add an XCP host fails with > >> > >> CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6, > >> XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.90, > >> so i need it to emulate XCP 1.1.0 but xapi fails to run with a memory > >> exception > >> > >> It appears that we now need to emulate XCP 1.1, yet doing the API > >> version over ride trick, makes xapi fail with > >> > >> > >> sed -i 's/1\.4\.90/1.1.0/g' xapi > >> [root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start > >> Starting xapi: Fatal error: exception Out_of_memory > >> failed to start xapi. [FAILED] > >> [root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi > >> cp: overwrite `xapi'? y > >> `xapi.original' -> `xapi' > >> > >> > >> So it doesnt appear possible to emulate much other then sed -i > >> 's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupported by CS 3.0 > >> still..... > >> > >> any ideas how to get the version emulation to function > >> > >> _______________________________________________ > >> xen-api mailing list > >> xen-api@lists.xen.org > >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api > --14dae9340cabd9230804bb64f5a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

How about using 6.0.00

On 2012-3-17 =E4=B8=8A=E5=8D=887:55, "Outba= ck Dingo" <outbackdingo@g= mail.com> wrote:
On Fri, Mar 16, 2012 at 6:43 PM, Philip Chan <pip.chan@gmail.com> wrote:
> Try 1.1.00
>

Welp using 1.1.00 did in fact allow xapi to start up, but still CS
fails to add the host, at least xapi did start

> On 2012-3-17 =E4=B8=8A=E5=8D=882:22, "Outback Dingo" <outbackdingo@gmail.com> wrote= :
>>
>> So in Cloustack 3.0 trying to add an XCP host fails with
>>
>> CS log says Only support XCP 1.0.0, XCP 1.1.0, XenServer 5.6,
>> XenServer 5.6 FP1 and XenServer 5.6 SP2, but this one is XCP 1.4.9= 0,
>> so i need it to emulate XCP 1.1.0 but xapi fails to run with a mem= ory
>> exception
>>
>> It appears that we now need to emulate XCP 1.1, yet doing the API<= br> >> version over ride trick, makes xapi fail with
>>
>>
>> sed -i 's/1\.4\.90/1.1.0/g' xapi
>> [root@xenserver-fhzmegfn bin]# /etc/init.d/xapi start
>> Starting xapi: Fatal error: exception Out_of_memory
>> failed to start xapi. =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0[FAILED]
>> [root@xenserver-fhzmegfn bin]# cp -vp xapi.original xapi
>> cp: overwrite `xapi'? y
>> `xapi.original' -> `xapi'
>>
>>
>> So it doesnt appear possible to emulate much other then sed -i
>> 's/1\.4\.90/6.0.99/g' xapi , however 6.0 is also unsupport= ed by CS 3.0
>> still.....
>>
>> any ideas how to get the version emulation to function
>>
>> _______________________________________________
>> xen-api mailing list
>> xen-api@lists.xen.org=
>> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api=
--14dae9340cabd9230804bb64f5a3-- --===============0378383610777865832== 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 --===============0378383610777865832==-- From xen-api-bounces@lists.xen.org Sat Mar 17 00:16:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 17 Mar 2012 00: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 1S8hJn-0008Jm-8K; Sat, 17 Mar 2012 00:16:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8hJl-0008JU-8x for xen-api@lists.xen.org; Sat, 17 Mar 2012 00:16:21 +0000 Received: from [85.158.143.35:12643] by server-1.bemta-4.messagelabs.com id ED/16-20925-4D7D36F4; Sat, 17 Mar 2012 00:16:20 +0000 X-Env-Sender: outbackdingo@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1331943379!12304764!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19621 invoked from network); 17 Mar 2012 00:16:19 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Mar 2012 00:16:19 -0000 Received: by bkcjg9 with SMTP id jg9so4055720bkc.32 for ; Fri, 16 Mar 2012 17:16:19 -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:content-transfer-encoding; bh=IhFtMmWcO8QtVVpemoVAxUsF+3zx+ntEVEdcJeBzfpk=; b=ZHNNwwnhEEi3f/U+AumUc9k9s6zZLAI+D2b4AGNXx8O/8YdkIfZVyr1Qn4Eucgqyn4 tvPqIJdluZizBVmVMEU66XuS49LgsPHU0yXNorRhQvPzXyp+28HtR1NE4IPcqKmuOl/7 QVCtbiINQNq2srK1KCV7m5hCHsqYT6qOaYeKp3p4h6vSZVW6xHBj82DqtRPdchN8q9oE XFsY40KdugzBddb+MucfQYPUABx2j7Ilq+rYiwt1ILEsu6tq0tH03fDtnSLY4a8eERfj vr4QL1hrhVqGMqL2Y7QFfjttYeA877DGv9e8vQsOdu9SDg+uR1+/jpxVN2yZI+dLUXaW 2H+Q== MIME-Version: 1.0 Received: by 10.204.143.151 with SMTP id v23mr1695204bku.63.1331943379018; Fri, 16 Mar 2012 17:16:19 -0700 (PDT) Received: by 10.204.174.75 with HTTP; Fri, 16 Mar 2012 17:16:18 -0700 (PDT) In-Reply-To: References: Date: Fri, 16 Mar 2012 20:16:18 -0400 Message-ID: From: Outback Dingo To: Philip Chan Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gRnJpLCBNYXIgMTYsIDIwMTIgYXQgNzo1NiBQTSwgUGhpbGlwIENoYW4gPHBpcC5jaGFuQGdt YWlsLmNvbT4gd3JvdGU6Cj4gSG93IGFib3V0IHVzaW5nIDYuMC4wMAoKbm9wZS4uLi4KCm90aGVy IGV4Y2VwdGlvbnM6IGphdmEubGFuZy5SdW50aW1lRXhjZXB0aW9uOiBPbmx5IHN1cHBvcnQgWENQ IDEuMC4wLApYQ1AgMS4xLjAsIFhlblNlcnZlciA1LjYsICBYZW5TZXJ2ZXIgNS42IEZQMSBhbmQg WGVuU2VydmVyIDUuNiBTUDIsCmJ1dCB0aGlzIG9uZSBpcyBYQ1AgNi4wLjAwCmphdmEubGFuZy5S dW50aW1lRXhjZXB0aW9uOiBPbmx5IHN1cHBvcnQgWENQIDEuMC4wLCBYQ1AgMS4xLjAsClhlblNl cnZlciA1LjYsICBYZW5TZXJ2ZXIgNS42IEZQMSBhbmQgWGVuU2VydmVyIDUuNiBTUDIsIGJ1dCB0 aGlzIG9uZQppcyBYQ1AgNi4wLjAwCgoKPgo+IE9uIDIwMTItMy0xNyDkuIrljYg3OjU1LCAiT3V0 YmFjayBEaW5nbyIgPG91dGJhY2tkaW5nb0BnbWFpbC5jb20+IHdyb3RlOgo+Pgo+PiBPbiBGcmks IE1hciAxNiwgMjAxMiBhdCA2OjQzIFBNLCBQaGlsaXAgQ2hhbiA8cGlwLmNoYW5AZ21haWwuY29t PiB3cm90ZToKPj4gPiBUcnkgMS4xLjAwCj4+ID4KPj4KPj4gV2VscCB1c2luZyAxLjEuMDAgZGlk IGluIGZhY3QgYWxsb3cgeGFwaSB0byBzdGFydCB1cCwgYnV0IHN0aWxsIENTCj4+IGZhaWxzIHRv IGFkZCB0aGUgaG9zdCwgYXQgbGVhc3QgeGFwaSBkaWQgc3RhcnQKPj4KPj4gPiBPbiAyMDEyLTMt MTcg5LiK5Y2IMjoyMiwgIk91dGJhY2sgRGluZ28iIDxvdXRiYWNrZGluZ29AZ21haWwuY29tPiB3 cm90ZToKPj4gPj4KPj4gPj4gU28gaW4gQ2xvdXN0YWNrIDMuMCB0cnlpbmcgdG8gYWRkIGFuIFhD UCBob3N0IGZhaWxzIHdpdGgKPj4gPj4KPj4gPj4gQ1MgbG9nIHNheXMgT25seSBzdXBwb3J0IFhD UCAxLjAuMCwgWENQIDEuMS4wLCBYZW5TZXJ2ZXIgNS42LAo+PiA+PiBYZW5TZXJ2ZXIgNS42IEZQ MSBhbmQgWGVuU2VydmVyIDUuNiBTUDIsIGJ1dCB0aGlzIG9uZSBpcyBYQ1AgMS40LjkwLAo+PiA+ PiBzbyBpIG5lZWQgaXQgdG8gZW11bGF0ZSBYQ1AgMS4xLjAgYnV0IHhhcGkgZmFpbHMgdG8gcnVu IHdpdGggYSBtZW1vcnkKPj4gPj4gZXhjZXB0aW9uCj4+ID4+Cj4+ID4+IEl0IGFwcGVhcnMgdGhh dCB3ZSBub3cgbmVlZCB0byBlbXVsYXRlIFhDUCAxLjEsIHlldCBkb2luZyB0aGUgQVBJCj4+ID4+ IHZlcnNpb24gb3ZlciByaWRlIHRyaWNrLCBtYWtlcyB4YXBpIGZhaWwgd2l0aAo+PiA+Pgo+PiA+ Pgo+PiA+PiBzZWQgLWkgJ3MvMVwuNFwuOTAvMS4xLjAvZycgeGFwaQo+PiA+PiBbcm9vdEB4ZW5z ZXJ2ZXItZmh6bWVnZm4gYmluXSMgL2V0Yy9pbml0LmQveGFwaSBzdGFydAo+PiA+PiBTdGFydGlu ZyB4YXBpOiBGYXRhbCBlcnJvcjogZXhjZXB0aW9uIE91dF9vZl9tZW1vcnkKPj4gPj4gZmFpbGVk IHRvIHN0YXJ0IHhhcGkuIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg IMKgIMKgIMKgIMKgIMKgW0ZBSUxFRF0KPj4gPj4gW3Jvb3RAeGVuc2VydmVyLWZoem1lZ2ZuIGJp bl0jIGNwIC12cCB4YXBpLm9yaWdpbmFsIHhhcGkKPj4gPj4gY3A6IG92ZXJ3cml0ZSBgeGFwaSc/ IHkKPj4gPj4gYHhhcGkub3JpZ2luYWwnIC0+IGB4YXBpJwo+PiA+Pgo+PiA+Pgo+PiA+PiBTbyBp dCBkb2VzbnQgYXBwZWFyIHBvc3NpYmxlIHRvIGVtdWxhdGUgbXVjaCBvdGhlciB0aGVuIHNlZCAt aQo+PiA+PiAncy8xXC40XC45MC82LjAuOTkvZycgeGFwaSAsIGhvd2V2ZXIgNi4wIGlzIGFsc28g dW5zdXBwb3J0ZWQgYnkgQ1MgMy4wCj4+ID4+IHN0aWxsLi4uLi4KPj4gPj4KPj4gPj4gYW55IGlk ZWFzIGhvdyB0byBnZXQgdGhlIHZlcnNpb24gZW11bGF0aW9uIHRvIGZ1bmN0aW9uCj4+ID4+Cj4+ ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4+ID4+ IHhlbi1hcGkgbWFpbGluZyBsaXN0Cj4+ID4+IHhlbi1hcGlAbGlzdHMueGVuLm9yZwo+PiA+PiBo dHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KeGVuLWFwaSBtYWls aW5nIGxpc3QKeGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Sat Mar 17 00:16:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 17 Mar 2012 00: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 1S8hJn-0008Jm-8K; Sat, 17 Mar 2012 00:16:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8hJl-0008JU-8x for xen-api@lists.xen.org; Sat, 17 Mar 2012 00:16:21 +0000 Received: from [85.158.143.35:12643] by server-1.bemta-4.messagelabs.com id ED/16-20925-4D7D36F4; Sat, 17 Mar 2012 00:16:20 +0000 X-Env-Sender: outbackdingo@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1331943379!12304764!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19621 invoked from network); 17 Mar 2012 00:16:19 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Mar 2012 00:16:19 -0000 Received: by bkcjg9 with SMTP id jg9so4055720bkc.32 for ; Fri, 16 Mar 2012 17:16:19 -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:content-transfer-encoding; bh=IhFtMmWcO8QtVVpemoVAxUsF+3zx+ntEVEdcJeBzfpk=; b=ZHNNwwnhEEi3f/U+AumUc9k9s6zZLAI+D2b4AGNXx8O/8YdkIfZVyr1Qn4Eucgqyn4 tvPqIJdluZizBVmVMEU66XuS49LgsPHU0yXNorRhQvPzXyp+28HtR1NE4IPcqKmuOl/7 QVCtbiINQNq2srK1KCV7m5hCHsqYT6qOaYeKp3p4h6vSZVW6xHBj82DqtRPdchN8q9oE XFsY40KdugzBddb+MucfQYPUABx2j7Ilq+rYiwt1ILEsu6tq0tH03fDtnSLY4a8eERfj vr4QL1hrhVqGMqL2Y7QFfjttYeA877DGv9e8vQsOdu9SDg+uR1+/jpxVN2yZI+dLUXaW 2H+Q== MIME-Version: 1.0 Received: by 10.204.143.151 with SMTP id v23mr1695204bku.63.1331943379018; Fri, 16 Mar 2012 17:16:19 -0700 (PDT) Received: by 10.204.174.75 with HTTP; Fri, 16 Mar 2012 17:16:18 -0700 (PDT) In-Reply-To: References: Date: Fri, 16 Mar 2012 20:16:18 -0400 Message-ID: From: Outback Dingo To: Philip Chan Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] XCP 1.5 and CloudStack 3.0 in the LAB X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gRnJpLCBNYXIgMTYsIDIwMTIgYXQgNzo1NiBQTSwgUGhpbGlwIENoYW4gPHBpcC5jaGFuQGdt YWlsLmNvbT4gd3JvdGU6Cj4gSG93IGFib3V0IHVzaW5nIDYuMC4wMAoKbm9wZS4uLi4KCm90aGVy IGV4Y2VwdGlvbnM6IGphdmEubGFuZy5SdW50aW1lRXhjZXB0aW9uOiBPbmx5IHN1cHBvcnQgWENQ IDEuMC4wLApYQ1AgMS4xLjAsIFhlblNlcnZlciA1LjYsICBYZW5TZXJ2ZXIgNS42IEZQMSBhbmQg WGVuU2VydmVyIDUuNiBTUDIsCmJ1dCB0aGlzIG9uZSBpcyBYQ1AgNi4wLjAwCmphdmEubGFuZy5S dW50aW1lRXhjZXB0aW9uOiBPbmx5IHN1cHBvcnQgWENQIDEuMC4wLCBYQ1AgMS4xLjAsClhlblNl cnZlciA1LjYsICBYZW5TZXJ2ZXIgNS42IEZQMSBhbmQgWGVuU2VydmVyIDUuNiBTUDIsIGJ1dCB0 aGlzIG9uZQppcyBYQ1AgNi4wLjAwCgoKPgo+IE9uIDIwMTItMy0xNyDkuIrljYg3OjU1LCAiT3V0 YmFjayBEaW5nbyIgPG91dGJhY2tkaW5nb0BnbWFpbC5jb20+IHdyb3RlOgo+Pgo+PiBPbiBGcmks IE1hciAxNiwgMjAxMiBhdCA2OjQzIFBNLCBQaGlsaXAgQ2hhbiA8cGlwLmNoYW5AZ21haWwuY29t PiB3cm90ZToKPj4gPiBUcnkgMS4xLjAwCj4+ID4KPj4KPj4gV2VscCB1c2luZyAxLjEuMDAgZGlk IGluIGZhY3QgYWxsb3cgeGFwaSB0byBzdGFydCB1cCwgYnV0IHN0aWxsIENTCj4+IGZhaWxzIHRv IGFkZCB0aGUgaG9zdCwgYXQgbGVhc3QgeGFwaSBkaWQgc3RhcnQKPj4KPj4gPiBPbiAyMDEyLTMt MTcg5LiK5Y2IMjoyMiwgIk91dGJhY2sgRGluZ28iIDxvdXRiYWNrZGluZ29AZ21haWwuY29tPiB3 cm90ZToKPj4gPj4KPj4gPj4gU28gaW4gQ2xvdXN0YWNrIDMuMCB0cnlpbmcgdG8gYWRkIGFuIFhD UCBob3N0IGZhaWxzIHdpdGgKPj4gPj4KPj4gPj4gQ1MgbG9nIHNheXMgT25seSBzdXBwb3J0IFhD UCAxLjAuMCwgWENQIDEuMS4wLCBYZW5TZXJ2ZXIgNS42LAo+PiA+PiBYZW5TZXJ2ZXIgNS42IEZQ MSBhbmQgWGVuU2VydmVyIDUuNiBTUDIsIGJ1dCB0aGlzIG9uZSBpcyBYQ1AgMS40LjkwLAo+PiA+ PiBzbyBpIG5lZWQgaXQgdG8gZW11bGF0ZSBYQ1AgMS4xLjAgYnV0IHhhcGkgZmFpbHMgdG8gcnVu IHdpdGggYSBtZW1vcnkKPj4gPj4gZXhjZXB0aW9uCj4+ID4+Cj4+ID4+IEl0IGFwcGVhcnMgdGhh dCB3ZSBub3cgbmVlZCB0byBlbXVsYXRlIFhDUCAxLjEsIHlldCBkb2luZyB0aGUgQVBJCj4+ID4+ IHZlcnNpb24gb3ZlciByaWRlIHRyaWNrLCBtYWtlcyB4YXBpIGZhaWwgd2l0aAo+PiA+Pgo+PiA+ Pgo+PiA+PiBzZWQgLWkgJ3MvMVwuNFwuOTAvMS4xLjAvZycgeGFwaQo+PiA+PiBbcm9vdEB4ZW5z ZXJ2ZXItZmh6bWVnZm4gYmluXSMgL2V0Yy9pbml0LmQveGFwaSBzdGFydAo+PiA+PiBTdGFydGlu ZyB4YXBpOiBGYXRhbCBlcnJvcjogZXhjZXB0aW9uIE91dF9vZl9tZW1vcnkKPj4gPj4gZmFpbGVk IHRvIHN0YXJ0IHhhcGkuIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg IMKgIMKgIMKgIMKgIMKgW0ZBSUxFRF0KPj4gPj4gW3Jvb3RAeGVuc2VydmVyLWZoem1lZ2ZuIGJp bl0jIGNwIC12cCB4YXBpLm9yaWdpbmFsIHhhcGkKPj4gPj4gY3A6IG92ZXJ3cml0ZSBgeGFwaSc/ IHkKPj4gPj4gYHhhcGkub3JpZ2luYWwnIC0+IGB4YXBpJwo+PiA+Pgo+PiA+Pgo+PiA+PiBTbyBp dCBkb2VzbnQgYXBwZWFyIHBvc3NpYmxlIHRvIGVtdWxhdGUgbXVjaCBvdGhlciB0aGVuIHNlZCAt aQo+PiA+PiAncy8xXC40XC45MC82LjAuOTkvZycgeGFwaSAsIGhvd2V2ZXIgNi4wIGlzIGFsc28g dW5zdXBwb3J0ZWQgYnkgQ1MgMy4wCj4+ID4+IHN0aWxsLi4uLi4KPj4gPj4KPj4gPj4gYW55IGlk ZWFzIGhvdyB0byBnZXQgdGhlIHZlcnNpb24gZW11bGF0aW9uIHRvIGZ1bmN0aW9uCj4+ID4+Cj4+ ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCj4+ID4+ IHhlbi1hcGkgbWFpbGluZyBsaXN0Cj4+ID4+IHhlbi1hcGlAbGlzdHMueGVuLm9yZwo+PiA+PiBo dHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQoKX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KeGVuLWFwaSBtYWls aW5nIGxpc3QKeGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Sat Mar 17 15:52:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 17 Mar 2012 15:52: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 1S8vv8-0006UF-FX; Sat, 17 Mar 2012 15:51:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8vv7-0006UA-RZ for xen-api@lists.xensource.com; Sat, 17 Mar 2012 15:51:54 +0000 Received: from [85.158.143.99:30307] by server-3.bemta-4.messagelabs.com id 31/2D-05853-913B46F4; Sat, 17 Mar 2012 15:51:53 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-14.tower-216.messagelabs.com!1331999511!13340039!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9891 invoked from network); 17 Mar 2012 15:51:52 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Mar 2012 15:51:52 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id B1BEFB423F; Sat, 17 Mar 2012 15:53:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; s=postfix; bh=NXzMCTzelEojjbkW67o45X lHysg=; b=xvrf+PBbK/EIiqL5uOmZNttnf87zPluYE9kbMODBZt9O2CeQ7ttrgs AdLjOINl9NQoeLeLyHmY+9krcppoJ/gAr9ZTIC9EQDJ4LYLQt8GHOJ64A3tg1JNE Rm2H3NBCRSMzFBHPVpvOIHeHlBxg9cIXbEsKmf8ec+XZ75XLWPZGY= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; q=dns; s=postfix; b=CxTg1gvoZW9nFneO SxRMAKKloKIXiO0yqAkX/qk0nBMl3pYFH9CCOsPotDzq/EYzGEal/XepxsZ0VSIK KE52sqZXQ+dSjjFSXnFgfBfBMGtxqovu0gevhDWU4swyWQh3eDX5hQSjiyRDYH3m XAoUsu+OFW9U7HPF6kWK/I1MVWU= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id AA04FB423E; Sat, 17 Mar 2012 15:53:20 +0000 (UTC) Message-ID: <4F64B311.8060709@goirand.fr> Date: Sat, 17 Mar 2012 23:51:45 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api , PKG OpenStack , "openstack@lists.launchpad.net" , John Garbutt X-Enigmail-Version: 1.0.1 Subject: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, When I start instances with Nova, using XCP on a Debian dom0, it seems that the Nova XenAPI plugin needs to access to a xapi0 network interface. If it's not their, the plugin just fails, and there's a python stack dump. So I have created a bridge called xapi0 on my dom0, and now I can start instances. But then, I have no network connectivity to my VMs. I wonder what this xapi0 network interface is for, and what is the correct networking model to have connectivity to my instances. When starting VMs, I don't see any network topology change in the dom0, or in my Openstack domU, which I think isn't right. Is the "normal" setup supposed to work with Quantum? Can it work without it? Can someone from the XenServer team enlighten me with the necessary knowledge? (The documentation about the necessary network setup is very scarce: I didn't find anything!) Cheers, Thomas P.S: Apart from that, it seems to work now with our Debian packages, even though it seems *very* slow to start instances, and I still can't get in the console of the VMs... :( _______________________________________________ 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 17 15:52:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 17 Mar 2012 15:52: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 1S8vv8-0006UF-FX; Sat, 17 Mar 2012 15:51:54 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S8vv7-0006UA-RZ for xen-api@lists.xensource.com; Sat, 17 Mar 2012 15:51:54 +0000 Received: from [85.158.143.99:30307] by server-3.bemta-4.messagelabs.com id 31/2D-05853-913B46F4; Sat, 17 Mar 2012 15:51:53 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-14.tower-216.messagelabs.com!1331999511!13340039!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9891 invoked from network); 17 Mar 2012 15:51:52 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-14.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Mar 2012 15:51:52 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id B1BEFB423F; Sat, 17 Mar 2012 15:53:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; s=postfix; bh=NXzMCTzelEojjbkW67o45X lHysg=; b=xvrf+PBbK/EIiqL5uOmZNttnf87zPluYE9kbMODBZt9O2CeQ7ttrgs AdLjOINl9NQoeLeLyHmY+9krcppoJ/gAr9ZTIC9EQDJ4LYLQt8GHOJ64A3tg1JNE Rm2H3NBCRSMzFBHPVpvOIHeHlBxg9cIXbEsKmf8ec+XZ75XLWPZGY= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; q=dns; s=postfix; b=CxTg1gvoZW9nFneO SxRMAKKloKIXiO0yqAkX/qk0nBMl3pYFH9CCOsPotDzq/EYzGEal/XepxsZ0VSIK KE52sqZXQ+dSjjFSXnFgfBfBMGtxqovu0gevhDWU4swyWQh3eDX5hQSjiyRDYH3m XAoUsu+OFW9U7HPF6kWK/I1MVWU= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id AA04FB423E; Sat, 17 Mar 2012 15:53:20 +0000 (UTC) Message-ID: <4F64B311.8060709@goirand.fr> Date: Sat, 17 Mar 2012 23:51:45 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api , PKG OpenStack , "openstack@lists.launchpad.net" , John Garbutt X-Enigmail-Version: 1.0.1 Subject: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, When I start instances with Nova, using XCP on a Debian dom0, it seems that the Nova XenAPI plugin needs to access to a xapi0 network interface. If it's not their, the plugin just fails, and there's a python stack dump. So I have created a bridge called xapi0 on my dom0, and now I can start instances. But then, I have no network connectivity to my VMs. I wonder what this xapi0 network interface is for, and what is the correct networking model to have connectivity to my instances. When starting VMs, I don't see any network topology change in the dom0, or in my Openstack domU, which I think isn't right. Is the "normal" setup supposed to work with Quantum? Can it work without it? Can someone from the XenServer team enlighten me with the necessary knowledge? (The documentation about the necessary network setup is very scarce: I didn't find anything!) Cheers, Thomas P.S: Apart from that, it seems to work now with our Debian packages, even though it seems *very* slow to start instances, and I still can't get in the console of the VMs... :( _______________________________________________ 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 19 10:04:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 10:04:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9ZRf-0007ca-GE; Mon, 19 Mar 2012 10:04:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9ZRe-0007cV-5M for xen-api@lists.xensource.com; Mon, 19 Mar 2012 10:04:06 +0000 Received: from [85.158.138.51:6176] by server-6.bemta-3.messagelabs.com id 02/56-08206-594076F4; Mon, 19 Mar 2012 10:04:05 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1332151443!18252603!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDAxNA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28384 invoked from network); 19 Mar 2012 10:04:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Mar 2012 10:04:03 -0000 X-IronPort-AV: E=Sophos;i="4.73,611,1325462400"; d="scan'208";a="11379589" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2012 10:04:03 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Mon, 19 Mar 2012 10:04:03 +0000 From: Dave Scott To: 'Thomas Goirand' , xen-api , PKG OpenStack , "openstack@lists.launchpad.net" , John Garbutt Date: Mon, 19 Mar 2012 10:04:02 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0EVg+rlxYFloOwSc+zVadR0zbQxABYITCQ Message-ID: <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> References: <4F64B311.8060709@goirand.fr> In-Reply-To: <4F64B311.8060709@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, > When I start instances with Nova, using XCP on a Debian dom0, it seems > that the Nova XenAPI plugin needs to access to a xapi0 network > interface. If it's not their, the plugin just fails, and there's a > python stack dump. > > So I have created a bridge called xapi0 on my dom0, and now I can start > instances. But then, I have no network connectivity to my VMs. > > I wonder what this xapi0 network interface is for, and what is the > correct networking model to have connectivity to my instances. When > starting VMs, I don't see any network topology change in the dom0, or > in > my Openstack domU, which I think isn't right. Is the "normal" setup > supposed to work with Quantum? Can it work without it? I'm not familiar with the design of the Nova plugins but my guess is that they're trying to use the "Host internal management network" -- a network from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). On recent XCP versions the default bridge name changed to "xenapi" to make it easier to distinguish from a firewall rules PoV. # xe network-list bridge=xenapi uuid ( RO) : 7e4b05a7-2135-a71f-f02e-7762ff56fa0d name-label ( RW): Host internal management network name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI bridge ( RO): xenapi Note that the actual linux bridge (or openvswitch) is created on demand so you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. Try changing "xapi0" to "xenapi" in the plugins and see if they work better? -- Dave Scott > > Can someone from the XenServer team enlighten me with the necessary > knowledge? (The documentation about the necessary network setup is very > scarce: I didn't find anything!) > > Cheers, > > Thomas > > P.S: Apart from that, it seems to work now with our Debian packages, > even though it seems *very* slow to start instances, and I still can't > get in the console of the VMs... :( > > _______________________________________________ > 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 19 10:04:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 10:04:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9ZRf-0007ca-GE; Mon, 19 Mar 2012 10:04:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9ZRe-0007cV-5M for xen-api@lists.xensource.com; Mon, 19 Mar 2012 10:04:06 +0000 Received: from [85.158.138.51:6176] by server-6.bemta-3.messagelabs.com id 02/56-08206-594076F4; Mon, 19 Mar 2012 10:04:05 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-8.tower-174.messagelabs.com!1332151443!18252603!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDAxNA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28384 invoked from network); 19 Mar 2012 10:04:03 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Mar 2012 10:04:03 -0000 X-IronPort-AV: E=Sophos;i="4.73,611,1325462400"; d="scan'208";a="11379589" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2012 10:04:03 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Mon, 19 Mar 2012 10:04:03 +0000 From: Dave Scott To: 'Thomas Goirand' , xen-api , PKG OpenStack , "openstack@lists.launchpad.net" , John Garbutt Date: Mon, 19 Mar 2012 10:04:02 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0EVg+rlxYFloOwSc+zVadR0zbQxABYITCQ Message-ID: <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> References: <4F64B311.8060709@goirand.fr> In-Reply-To: <4F64B311.8060709@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, > When I start instances with Nova, using XCP on a Debian dom0, it seems > that the Nova XenAPI plugin needs to access to a xapi0 network > interface. If it's not their, the plugin just fails, and there's a > python stack dump. > > So I have created a bridge called xapi0 on my dom0, and now I can start > instances. But then, I have no network connectivity to my VMs. > > I wonder what this xapi0 network interface is for, and what is the > correct networking model to have connectivity to my instances. When > starting VMs, I don't see any network topology change in the dom0, or > in > my Openstack domU, which I think isn't right. Is the "normal" setup > supposed to work with Quantum? Can it work without it? I'm not familiar with the design of the Nova plugins but my guess is that they're trying to use the "Host internal management network" -- a network from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). On recent XCP versions the default bridge name changed to "xenapi" to make it easier to distinguish from a firewall rules PoV. # xe network-list bridge=xenapi uuid ( RO) : 7e4b05a7-2135-a71f-f02e-7762ff56fa0d name-label ( RW): Host internal management network name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI bridge ( RO): xenapi Note that the actual linux bridge (or openvswitch) is created on demand so you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. Try changing "xapi0" to "xenapi" in the plugins and see if they work better? -- Dave Scott > > Can someone from the XenServer team enlighten me with the necessary > knowledge? (The documentation about the necessary network setup is very > scarce: I didn't find anything!) > > Cheers, > > Thomas > > P.S: Apart from that, it seems to work now with our Debian packages, > even though it seems *very* slow to start instances, and I still can't > get in the console of the VMs... :( > > _______________________________________________ > 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 19 15:14:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 15:14: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 1S9eI1-00053o-5d; Mon, 19 Mar 2012 15:14:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9eHz-00053e-P8 for xen-api@lists.xen.org; Mon, 19 Mar 2012 15:14:27 +0000 Received: from [85.158.139.83:53746] by server-7.bemta-5.messagelabs.com id 9B/05-16195-25D476F4; Mon, 19 Mar 2012 15:14:26 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1332170064!20035437!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxMjk1ODI=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4482 invoked from network); 19 Mar 2012 15:14:26 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Mar 2012 15:14:26 -0000 X-IronPort-AV: E=Sophos;i="4.73,612,1325480400"; d="scan'208";a="23220611" Received: from ftlpmailmx02.citrite.net ([10.13.107.66]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2012 11:14:24 -0400 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.66) with Microsoft SMTP Server id 8.3.213.0; Mon, 19 Mar 2012 11:14:24 -0400 Received: from cosworth.uk.xensource.com ([10.80.16.52] ident=ianc) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1S9eHv-0007bS-Dc; Mon, 19 Mar 2012 15:14:23 +0000 MIME-Version: 1.0 X-Mercurial-Node: f588c69fd12f17e81d3289653ae1e3b20cd41c11 Message-ID: In-Reply-To: <1331732247.23971.438.camel@zakaz.uk.xensource.com> References: <1331732247.23971.438.camel@zakaz.uk.xensource.com> User-Agent: Mercurial-patchbomb/1.6.4 Date: Mon, 19 Mar 2012 15:14:23 +0000 From: Ian Campbell To: xen-devel@lists.xen.org Cc: Jim Fehlig , xen-api@lists.xen.org, Ian Jackson , Bamvor Jian Zhang Subject: [Xen-API] [PATCH] libxl: Document API and ABI compatibility guarantees X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 # HG changeset patch # User Ian Campbell # Date 1332169579 0 # Node ID f588c69fd12f17e81d3289653ae1e3b20cd41c11 # Parent e10c4b937e8fa9159070584113e9378ca175f728 libxl: Document API and ABI compatibility guarantees. Signed-off-by: Ian Campbell diff -r e10c4b937e8f -r f588c69fd12f tools/libxl/libxl.h --- a/tools/libxl/libxl.h Mon Mar 19 14:24:01 2012 +0000 +++ b/tools/libxl/libxl.h Mon Mar 19 15:06:19 2012 +0000 @@ -14,6 +14,77 @@ */ /* + * libxl API compatibility + * + * From Xen 4.2 onwards the API of libxl will be maintained in a + * stable manner. This means that it should be possible to write an + * application against the API provided by libxl in Xen 4.2 and expect + * that it will continue to compile against future versions of Xen + * without source modification. + * + * In order to make such compatibility possible it is required that + * application which want to be exposed to a particular API #define + * LIBXL_API_VERSION before including libxl.h or any other libxl + * header. The syntax of the LIBXL_API_VERSION is: + * 0xVVSSEE + * where ($(XEN_xxx) from xen/Makefile): + * VV is the Xen major release number, $(XEN_VERSION) + * SS is the Xen sub version number, $(XEN_SUBVERSION) + * EE is the Xen extra version digit, first numeric part of + * $(XEN_EXTRAVERSION) not including the leading "." + * For example the first stable API version, supported by Xen 4.2.0, + * is 0x040200. + * + * Lack of LIBXL_API_VERSION means "the latest" which will + * change. Specifying an unknown LIBXL_API_VERSION will result in a + * compile time error. + * + * Identical versions of the libxl API will represented by the version + * containing the earliest instance of that API. e.g. if 4.2.0 and + * 4.3.0 contain an identical libxl API then only LIBXL_API_VERSION + * 0x040200 will be valid. + * + * We will try especially hard to avoid changing the API during a + * stable series, i.e. it should be unusual for the last byte of + * LIBXL_API_VERSION to be non-zero. + * + * In the event that a change is required which cannot be made + * backwards compatible in this manner a #define of the form + * LIBXL_HAVE_ will always be added in order to make it + * possible to write applciations which build against any version of + * libxl. Such changes are expected to be exceptional and used as a + * last resort. The barrier for backporting such a change to a stable + * branch will be very high. + * + * These guarantees apply only to stable releases of Xen. When an + * incompatible change is made in the unstable tree then + * LIBXL_API_VERSION will be bumped to the next expected stable + * release number on the first such change only. Applications which + * want to support building against Xen unstable are expected to track + * API changes in that tree until it is released as a stable release. + * + * API compatibility will be maintained for all versions of Xen using + * the same $(XEN_VERSION) (e.g. throughout a major release). + */ + +/* + * libxl ABI compatibility + * + * The only guarantee which libxl makes regarding ABI compatibility + * across releases is that the SONAME will always be bumped whenever + * the ABI is changed in an incompatible way. + * + * This applies within stable branches as well as + * development branches. It is possible that a new stable release of + * Xen may require a rebuild of applications using the + * library. However per the API compatibility gaurantees such a + * rebuild should not normally require any source level changes. + * + * As with the API compatiblity the SONAME will only be bumped for the + * first ABI incompatible change in a development branch. + */ + +/* * libxl memory management * * From the point of view of the application (ie, libxl's caller), @@ -184,6 +255,13 @@ #include #include <_libxl_list.h> +/* API compatibility. Only 0x040200 is supported at this time. */ +#ifdef LIBXL_API_VERSION +#if LIBXL_API_VERSION != 0x040200 +#error Unknown LIBXL_API_VERSION +#endif +#endif + typedef uint8_t libxl_mac[6]; #define LIBXL_MAC_FMT "%02hhx:%02hhx:%02hhx:%02hhx:%02hhx:%02hhx" #define LIBXL_MAC_FMTLEN ((2*6)+5) /* 6 hex bytes plus 5 colons */ _______________________________________________ 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 19 15:14:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 15:14: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 1S9eI1-00053o-5d; Mon, 19 Mar 2012 15:14:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9eHz-00053e-P8 for xen-api@lists.xen.org; Mon, 19 Mar 2012 15:14:27 +0000 Received: from [85.158.139.83:53746] by server-7.bemta-5.messagelabs.com id 9B/05-16195-25D476F4; Mon, 19 Mar 2012 15:14:26 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1332170064!20035437!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAxMjk1ODI=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4482 invoked from network); 19 Mar 2012 15:14:26 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Mar 2012 15:14:26 -0000 X-IronPort-AV: E=Sophos;i="4.73,612,1325480400"; d="scan'208";a="23220611" Received: from ftlpmailmx02.citrite.net ([10.13.107.66]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2012 11:14:24 -0400 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.66) with Microsoft SMTP Server id 8.3.213.0; Mon, 19 Mar 2012 11:14:24 -0400 Received: from cosworth.uk.xensource.com ([10.80.16.52] ident=ianc) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1S9eHv-0007bS-Dc; Mon, 19 Mar 2012 15:14:23 +0000 MIME-Version: 1.0 X-Mercurial-Node: f588c69fd12f17e81d3289653ae1e3b20cd41c11 Message-ID: In-Reply-To: <1331732247.23971.438.camel@zakaz.uk.xensource.com> References: <1331732247.23971.438.camel@zakaz.uk.xensource.com> User-Agent: Mercurial-patchbomb/1.6.4 Date: Mon, 19 Mar 2012 15:14:23 +0000 From: Ian Campbell To: xen-devel@lists.xen.org Cc: Jim Fehlig , xen-api@lists.xen.org, Ian Jackson , Bamvor Jian Zhang Subject: [Xen-API] [PATCH] libxl: Document API and ABI compatibility guarantees X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 # HG changeset patch # User Ian Campbell # Date 1332169579 0 # Node ID f588c69fd12f17e81d3289653ae1e3b20cd41c11 # Parent e10c4b937e8fa9159070584113e9378ca175f728 libxl: Document API and ABI compatibility guarantees. Signed-off-by: Ian Campbell diff -r e10c4b937e8f -r f588c69fd12f tools/libxl/libxl.h --- a/tools/libxl/libxl.h Mon Mar 19 14:24:01 2012 +0000 +++ b/tools/libxl/libxl.h Mon Mar 19 15:06:19 2012 +0000 @@ -14,6 +14,77 @@ */ /* + * libxl API compatibility + * + * From Xen 4.2 onwards the API of libxl will be maintained in a + * stable manner. This means that it should be possible to write an + * application against the API provided by libxl in Xen 4.2 and expect + * that it will continue to compile against future versions of Xen + * without source modification. + * + * In order to make such compatibility possible it is required that + * application which want to be exposed to a particular API #define + * LIBXL_API_VERSION before including libxl.h or any other libxl + * header. The syntax of the LIBXL_API_VERSION is: + * 0xVVSSEE + * where ($(XEN_xxx) from xen/Makefile): + * VV is the Xen major release number, $(XEN_VERSION) + * SS is the Xen sub version number, $(XEN_SUBVERSION) + * EE is the Xen extra version digit, first numeric part of + * $(XEN_EXTRAVERSION) not including the leading "." + * For example the first stable API version, supported by Xen 4.2.0, + * is 0x040200. + * + * Lack of LIBXL_API_VERSION means "the latest" which will + * change. Specifying an unknown LIBXL_API_VERSION will result in a + * compile time error. + * + * Identical versions of the libxl API will represented by the version + * containing the earliest instance of that API. e.g. if 4.2.0 and + * 4.3.0 contain an identical libxl API then only LIBXL_API_VERSION + * 0x040200 will be valid. + * + * We will try especially hard to avoid changing the API during a + * stable series, i.e. it should be unusual for the last byte of + * LIBXL_API_VERSION to be non-zero. + * + * In the event that a change is required which cannot be made + * backwards compatible in this manner a #define of the form + * LIBXL_HAVE_ will always be added in order to make it + * possible to write applciations which build against any version of + * libxl. Such changes are expected to be exceptional and used as a + * last resort. The barrier for backporting such a change to a stable + * branch will be very high. + * + * These guarantees apply only to stable releases of Xen. When an + * incompatible change is made in the unstable tree then + * LIBXL_API_VERSION will be bumped to the next expected stable + * release number on the first such change only. Applications which + * want to support building against Xen unstable are expected to track + * API changes in that tree until it is released as a stable release. + * + * API compatibility will be maintained for all versions of Xen using + * the same $(XEN_VERSION) (e.g. throughout a major release). + */ + +/* + * libxl ABI compatibility + * + * The only guarantee which libxl makes regarding ABI compatibility + * across releases is that the SONAME will always be bumped whenever + * the ABI is changed in an incompatible way. + * + * This applies within stable branches as well as + * development branches. It is possible that a new stable release of + * Xen may require a rebuild of applications using the + * library. However per the API compatibility gaurantees such a + * rebuild should not normally require any source level changes. + * + * As with the API compatiblity the SONAME will only be bumped for the + * first ABI incompatible change in a development branch. + */ + +/* * libxl memory management * * From the point of view of the application (ie, libxl's caller), @@ -184,6 +255,13 @@ #include #include <_libxl_list.h> +/* API compatibility. Only 0x040200 is supported at this time. */ +#ifdef LIBXL_API_VERSION +#if LIBXL_API_VERSION != 0x040200 +#error Unknown LIBXL_API_VERSION +#endif +#endif + typedef uint8_t libxl_mac[6]; #define LIBXL_MAC_FMT "%02hhx:%02hhx:%02hhx:%02hhx:%02hhx:%02hhx" #define LIBXL_MAC_FMTLEN ((2*6)+5) /* 6 hex bytes plus 5 colons */ _______________________________________________ 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 19 16:06:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 16:06:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9f5w-0007mJ-SY; Mon, 19 Mar 2012 16:06:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9f5v-0007mE-TD for xen-api@lists.xensource.com; Mon, 19 Mar 2012 16:06:04 +0000 Received: from [85.158.139.83:22395] by server-9.bemta-5.messagelabs.com id 59/61-09826-B69576F4; Mon, 19 Mar 2012 16:06:03 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1332173161!20043974!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDAxNA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30079 invoked from network); 19 Mar 2012 16:06:01 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Mar 2012 16:06:01 -0000 X-IronPort-AV: E=Sophos;i="4.73,612,1325462400"; d="scan'208";a="11390216" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2012 16:06:00 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 19 Mar 2012 16:06:00 +0000 From: John Garbutt To: Dave Scott , 'Thomas Goirand' , xen-api , PKG OpenStack , "openstack@lists.launchpad.net" Date: Mon, 19 Mar 2012 16:05:59 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0EVg+rlxYFloOwSc+zVadR0zbQxABYITCQAAzYVnA= Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 This sounds a lot like a configuration issue with your guest network bridge. Are you OK to supply your nova.conf file? Also, have you tried using DevStack first? It is a good way to get the hang of how the flags work. Thanks, John -----Original Message----- From: Dave Scott Sent: 19 March 2012 10:04 To: 'Thomas Goirand'; xen-api; PKG OpenStack; openstack@lists.launchpad.net; John Garbutt Subject: RE: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Hi, > When I start instances with Nova, using XCP on a Debian dom0, it seems > that the Nova XenAPI plugin needs to access to a xapi0 network > interface. If it's not their, the plugin just fails, and there's a > python stack dump. > > So I have created a bridge called xapi0 on my dom0, and now I can > start instances. But then, I have no network connectivity to my VMs. > > I wonder what this xapi0 network interface is for, and what is the > correct networking model to have connectivity to my instances. When > starting VMs, I don't see any network topology change in the dom0, or > in my Openstack domU, which I think isn't right. Is the "normal" setup > supposed to work with Quantum? Can it work without it? I'm not familiar with the design of the Nova plugins but my guess is that they're trying to use the "Host internal management network" -- a network from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). On recent XCP versions the default bridge name changed to "xenapi" to make it easier to distinguish from a firewall rules PoV. # xe network-list bridge=xenapi uuid ( RO) : 7e4b05a7-2135-a71f-f02e-7762ff56fa0d name-label ( RW): Host internal management network name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI bridge ( RO): xenapi Note that the actual linux bridge (or openvswitch) is created on demand so you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. Try changing "xapi0" to "xenapi" in the plugins and see if they work better? -- Dave Scott > > Can someone from the XenServer team enlighten me with the necessary > knowledge? (The documentation about the necessary network setup is > very > scarce: I didn't find anything!) > > Cheers, > > Thomas > > P.S: Apart from that, it seems to work now with our Debian packages, > even though it seems *very* slow to start instances, and I still can't > get in the console of the VMs... :( > > _______________________________________________ > 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 19 16:06:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 16:06:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9f5w-0007mJ-SY; Mon, 19 Mar 2012 16:06:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9f5v-0007mE-TD for xen-api@lists.xensource.com; Mon, 19 Mar 2012 16:06:04 +0000 Received: from [85.158.139.83:22395] by server-9.bemta-5.messagelabs.com id 59/61-09826-B69576F4; Mon, 19 Mar 2012 16:06:03 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1332173161!20043974!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDAxNA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30079 invoked from network); 19 Mar 2012 16:06:01 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Mar 2012 16:06:01 -0000 X-IronPort-AV: E=Sophos;i="4.73,612,1325462400"; d="scan'208";a="11390216" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2012 16:06:00 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 19 Mar 2012 16:06:00 +0000 From: John Garbutt To: Dave Scott , 'Thomas Goirand' , xen-api , PKG OpenStack , "openstack@lists.launchpad.net" Date: Mon, 19 Mar 2012 16:05:59 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0EVg+rlxYFloOwSc+zVadR0zbQxABYITCQAAzYVnA= Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 This sounds a lot like a configuration issue with your guest network bridge. Are you OK to supply your nova.conf file? Also, have you tried using DevStack first? It is a good way to get the hang of how the flags work. Thanks, John -----Original Message----- From: Dave Scott Sent: 19 March 2012 10:04 To: 'Thomas Goirand'; xen-api; PKG OpenStack; openstack@lists.launchpad.net; John Garbutt Subject: RE: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Hi, > When I start instances with Nova, using XCP on a Debian dom0, it seems > that the Nova XenAPI plugin needs to access to a xapi0 network > interface. If it's not their, the plugin just fails, and there's a > python stack dump. > > So I have created a bridge called xapi0 on my dom0, and now I can > start instances. But then, I have no network connectivity to my VMs. > > I wonder what this xapi0 network interface is for, and what is the > correct networking model to have connectivity to my instances. When > starting VMs, I don't see any network topology change in the dom0, or > in my Openstack domU, which I think isn't right. Is the "normal" setup > supposed to work with Quantum? Can it work without it? I'm not familiar with the design of the Nova plugins but my guess is that they're trying to use the "Host internal management network" -- a network from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). On recent XCP versions the default bridge name changed to "xenapi" to make it easier to distinguish from a firewall rules PoV. # xe network-list bridge=xenapi uuid ( RO) : 7e4b05a7-2135-a71f-f02e-7762ff56fa0d name-label ( RW): Host internal management network name-description ( RW): Network on which guests will be assigned a private link-local IP address which can be used to talk XenAPI bridge ( RO): xenapi Note that the actual linux bridge (or openvswitch) is created on demand so you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. Try changing "xapi0" to "xenapi" in the plugins and see if they work better? -- Dave Scott > > Can someone from the XenServer team enlighten me with the necessary > knowledge? (The documentation about the necessary network setup is > very > scarce: I didn't find anything!) > > Cheers, > > Thomas > > P.S: Apart from that, it seems to work now with our Debian packages, > even though it seems *very* slow to start instances, and I still can't > get in the console of the VMs... :( > > _______________________________________________ > 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 19 17:25:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 17:25:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9gKi-0003pf-B3; Mon, 19 Mar 2012 17:25:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9gKg-0003pZ-SS for xen-api@lists.xensource.com; Mon, 19 Mar 2012 17:25:23 +0000 Received: from [193.109.254.147:14792] by server-8.bemta-14.messagelabs.com id 6A/52-23244-20C676F4; Mon, 19 Mar 2012 17:25:22 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-11.tower-27.messagelabs.com!1332177920!1178015!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25634 invoked from network); 19 Mar 2012 17:25:21 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Mar 2012 17:25:21 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 5BF5DFE0CE; Mon, 19 Mar 2012 17:26:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=cufuQtIXP yAA8lJQrpjLY/a96zY=; b=NniJwxvzS/oIu8H5b7Rom3TzOiE7dfnMFHqtPgjQQ gGJu+ZqfbHnmAqXsKnpee6xGLbX+fcGG8msLHYPTpXbPjwna4TFYiateBLnhMrZn +uGO5gIKh6kKbLs7aFnSEIocfT2jKFFnRNXwN1HJwh7w5pqAmg/Mrm/m5NxZbQfm tc= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=H6s NW8oewux/Zx3Udha5sfWIRsglHDcNi0Wi3vPAKOnk8bamot0gM43qK8Fw8Kae4UC zFA/55zaE6C5vMsvFrX8A+zP7kG431bsTiuWBbIAwSARRTvOEGSm3HRvBKDRuNMG BI4vCpQ9w2h1fB3HiQwIrUYFOJlL71g1dIdP57+M= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id ED72FFE0B7; Mon, 19 Mar 2012 17:26:57 +0000 (UTC) Message-ID: <4F676BFC.702@goirand.fr> Date: Tue, 20 Mar 2012 01:25:16 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: John Garbutt References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> In-Reply-To: X-Enigmail-Version: 1.0.1 Cc: PKG OpenStack , "openstack@lists.launchpad.net" , xen-api Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On 03/20/2012 12:05 AM, John Garbutt wrote: > This sounds a lot like a configuration issue with your guest network bridge. Are you OK to supply your nova.conf file? Sure! Here it is: --sql_connection=mysql://nova:admin@127.0.0.1/nova --novncproxy_base_url=http://:6080/vnc_auto.html --rabbit_host= --glance_api_servers=:9292 --network_manager=nova.network.manager.VlanManager --vlan_interface=br100 --dhcpbridge=/usr/bin/nova-dhcpbridge --firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver --connection_type=xenapi --xenapi_connection_url=https:// --xenapi_connection_username=root --xenapi_connection_password=XXXXXXX --reboot_timeout=600 --rescue_timeout=86400 --resize_confirm_window=86400 --auth_strategy=keystone --allow_admin_api --allow_resize_to_same_host --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --vncserver_listen=0.0.0.0 --force_dhcp_release --use_deprecated_auth --use_project_ca --verbose Note that since I restarted xcp-xapi, it seems that the xapi0 bridge is created each time I create a VM, which is what I was expecting. So that parts seems to work now, but the issue is that now, I have no networking at all (eg: I can't reach the instance from the Openstack domU). Here's what "xe network-list" returns on my dom0: uuid ( RO) : name-label ( RW): br100 name-description ( RW): network for nova bridge br100 bridge ( RO): xapi0 So it really is nova who created this. But shouldn't it be linked to my xenbr0 as well? What is the normal networking setup that should be done? There's absolutely zero documentation which I could find about this. Of course, I'll write one directly in our Debian packages as soon as this works. > Also, have you tried using DevStack first? It is a good way to get the hang of how the flags work. No it's not! DevStack is for testing with XenServer, and assumes that you'd be working with Ubuntu. Here, I'm testing the Debian packages that we are working on in Debian. Please don't direct me to DevStack, this wont help. > I'm not familiar with the design of the Nova plugins but my guess is that they're trying to use the "Host internal management network" -- a network from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). > > On recent XCP versions the default bridge name changed to "xenapi" to make it easier to distinguish from a firewall rules PoV. As per Mike on IRC, (from Citrix, upstream for XCP, XenServer and Kronos), each time there's a new network being created, XCP create a xapiX bridge automatically. I shouldn't have even try to bring the xapi0 bridge myself, XCP does it (if it doesn't, then there's an issue). > Note that the actual linux bridge (or openvswitch) is created on demand so you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. > > Try changing "xapi0" to "xenapi" in the plugins and see if they work better? Nop, that wont help, xapi0 is really what to expect. My only issue now is to have it connected to the br100 of Openstack in my domU. Thanks for the help already, Cheers, Thomas _______________________________________________ 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 19 17:25:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 17:25:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9gKi-0003pf-B3; Mon, 19 Mar 2012 17:25:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9gKg-0003pZ-SS for xen-api@lists.xensource.com; Mon, 19 Mar 2012 17:25:23 +0000 Received: from [193.109.254.147:14792] by server-8.bemta-14.messagelabs.com id 6A/52-23244-20C676F4; Mon, 19 Mar 2012 17:25:22 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-11.tower-27.messagelabs.com!1332177920!1178015!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25634 invoked from network); 19 Mar 2012 17:25:21 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Mar 2012 17:25:21 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 5BF5DFE0CE; Mon, 19 Mar 2012 17:26:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=cufuQtIXP yAA8lJQrpjLY/a96zY=; b=NniJwxvzS/oIu8H5b7Rom3TzOiE7dfnMFHqtPgjQQ gGJu+ZqfbHnmAqXsKnpee6xGLbX+fcGG8msLHYPTpXbPjwna4TFYiateBLnhMrZn +uGO5gIKh6kKbLs7aFnSEIocfT2jKFFnRNXwN1HJwh7w5pqAmg/Mrm/m5NxZbQfm tc= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=H6s NW8oewux/Zx3Udha5sfWIRsglHDcNi0Wi3vPAKOnk8bamot0gM43qK8Fw8Kae4UC zFA/55zaE6C5vMsvFrX8A+zP7kG431bsTiuWBbIAwSARRTvOEGSm3HRvBKDRuNMG BI4vCpQ9w2h1fB3HiQwIrUYFOJlL71g1dIdP57+M= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id ED72FFE0B7; Mon, 19 Mar 2012 17:26:57 +0000 (UTC) Message-ID: <4F676BFC.702@goirand.fr> Date: Tue, 20 Mar 2012 01:25:16 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: John Garbutt References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> In-Reply-To: X-Enigmail-Version: 1.0.1 Cc: PKG OpenStack , "openstack@lists.launchpad.net" , xen-api Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On 03/20/2012 12:05 AM, John Garbutt wrote: > This sounds a lot like a configuration issue with your guest network bridge. Are you OK to supply your nova.conf file? Sure! Here it is: --sql_connection=mysql://nova:admin@127.0.0.1/nova --novncproxy_base_url=http://:6080/vnc_auto.html --rabbit_host= --glance_api_servers=:9292 --network_manager=nova.network.manager.VlanManager --vlan_interface=br100 --dhcpbridge=/usr/bin/nova-dhcpbridge --firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver --connection_type=xenapi --xenapi_connection_url=https:// --xenapi_connection_username=root --xenapi_connection_password=XXXXXXX --reboot_timeout=600 --rescue_timeout=86400 --resize_confirm_window=86400 --auth_strategy=keystone --allow_admin_api --allow_resize_to_same_host --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --vncserver_listen=0.0.0.0 --force_dhcp_release --use_deprecated_auth --use_project_ca --verbose Note that since I restarted xcp-xapi, it seems that the xapi0 bridge is created each time I create a VM, which is what I was expecting. So that parts seems to work now, but the issue is that now, I have no networking at all (eg: I can't reach the instance from the Openstack domU). Here's what "xe network-list" returns on my dom0: uuid ( RO) : name-label ( RW): br100 name-description ( RW): network for nova bridge br100 bridge ( RO): xapi0 So it really is nova who created this. But shouldn't it be linked to my xenbr0 as well? What is the normal networking setup that should be done? There's absolutely zero documentation which I could find about this. Of course, I'll write one directly in our Debian packages as soon as this works. > Also, have you tried using DevStack first? It is a good way to get the hang of how the flags work. No it's not! DevStack is for testing with XenServer, and assumes that you'd be working with Ubuntu. Here, I'm testing the Debian packages that we are working on in Debian. Please don't direct me to DevStack, this wont help. > I'm not familiar with the design of the Nova plugins but my guess is that they're trying to use the "Host internal management network" -- a network from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). > > On recent XCP versions the default bridge name changed to "xenapi" to make it easier to distinguish from a firewall rules PoV. As per Mike on IRC, (from Citrix, upstream for XCP, XenServer and Kronos), each time there's a new network being created, XCP create a xapiX bridge automatically. I shouldn't have even try to bring the xapi0 bridge myself, XCP does it (if it doesn't, then there's an issue). > Note that the actual linux bridge (or openvswitch) is created on demand so you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. > > Try changing "xapi0" to "xenapi" in the plugins and see if they work better? Nop, that wont help, xapi0 is really what to expect. My only issue now is to have it connected to the br100 of Openstack in my domU. Thanks for the help already, Cheers, Thomas _______________________________________________ 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 19 18:01:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 18:01:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9gt8-0007gt-P0; Mon, 19 Mar 2012 18:00:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9gt6-0007gh-Oh for xen-api@lists.xensource.com; Mon, 19 Mar 2012 18:00:56 +0000 Received: from [85.158.143.99:13276] by server-1.bemta-4.messagelabs.com id D8/DE-20925-854776F4; Mon, 19 Mar 2012 18:00:56 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1332180055!19902748!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDAxNA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20872 invoked from network); 19 Mar 2012 18:00:55 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Mar 2012 18:00:55 -0000 X-IronPort-AV: E=Sophos;i="4.73,612,1325462400"; d="scan'208";a="11393904" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2012 18:00:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Mon, 19 Mar 2012 18:00:55 +0000 From: John Garbutt To: 'Thomas Goirand' Date: Mon, 19 Mar 2012 18:00:54 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0F9UNWekWgfyUaSyS4ijd0Z7gHfQAAlEHg Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: <4F676BFC.702@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: PKG OpenStack , "openstack@lists.launchpad.net" , xen-api Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, Looks like the network configuration is not quite right. Have a look at this, for an example of how things could look networking wise (when using DevStack and XenServer with two nics): http://wiki.openstack.org/XenServer/XenXCPAndXenServer The manuals have a good description, although it is a little KVM specific: http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-flat-dhcp-networking.html I suggested using DevStack because it is the best "documentation" for a working set of flags right now (yes, not ideal, we must fix that asap!). Take a look: https://github.com/openstack-dev/devstack/blob/master/stack.sh#L291 Note the defaults in the nova code might work for KVM, but will not work for XenServer, so you will need to set those flags with more appropriate values. Hope that helps, John -----Original Message----- From: Thomas Goirand [mailto:thomas@goirand.fr] Sent: 19 March 2012 5:25 To: John Garbutt Cc: Dave Scott; xen-api; PKG OpenStack; openstack@lists.launchpad.net Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface On 03/20/2012 12:05 AM, John Garbutt wrote: > This sounds a lot like a configuration issue with your guest network bridge. Are you OK to supply your nova.conf file? Sure! Here it is: --sql_connection=mysql://nova:admin@127.0.0.1/nova --novncproxy_base_url=http://:6080/vnc_auto.html --rabbit_host= --glance_api_servers=:9292 --network_manager=nova.network.manager.VlanManager --vlan_interface=br100 --dhcpbridge=/usr/bin/nova-dhcpbridge --firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver --connection_type=xenapi --xenapi_connection_url=https:// --xenapi_connection_username=root --xenapi_connection_password=XXXXXXX --reboot_timeout=600 --rescue_timeout=86400 --resize_confirm_window=86400 --auth_strategy=keystone --allow_admin_api --allow_resize_to_same_host --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --vncserver_listen=0.0.0.0 --force_dhcp_release --use_deprecated_auth --use_project_ca --verbose Note that since I restarted xcp-xapi, it seems that the xapi0 bridge is created each time I create a VM, which is what I was expecting. So that parts seems to work now, but the issue is that now, I have no networking at all (eg: I can't reach the instance from the Openstack domU). Here's what "xe network-list" returns on my dom0: uuid ( RO) : name-label ( RW): br100 name-description ( RW): network for nova bridge br100 bridge ( RO): xapi0 So it really is nova who created this. But shouldn't it be linked to my xenbr0 as well? What is the normal networking setup that should be done? There's absolutely zero documentation which I could find about this. Of course, I'll write one directly in our Debian packages as soon as this works. > Also, have you tried using DevStack first? It is a good way to get the hang of how the flags work. No it's not! DevStack is for testing with XenServer, and assumes that you'd be working with Ubuntu. Here, I'm testing the Debian packages that we are working on in Debian. Please don't direct me to DevStack, this wont help. > I'm not familiar with the design of the Nova plugins but my guess is that they're trying to use the "Host internal management network" -- a network from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). > > On recent XCP versions the default bridge name changed to "xenapi" to make it easier to distinguish from a firewall rules PoV. As per Mike on IRC, (from Citrix, upstream for XCP, XenServer and Kronos), each time there's a new network being created, XCP create a xapiX bridge automatically. I shouldn't have even try to bring the xapi0 bridge myself, XCP does it (if it doesn't, then there's an issue). > Note that the actual linux bridge (or openvswitch) is created on demand so you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. > > Try changing "xapi0" to "xenapi" in the plugins and see if they work better? Nop, that wont help, xapi0 is really what to expect. My only issue now is to have it connected to the br100 of Openstack in my domU. Thanks for the help already, Cheers, Thomas _______________________________________________ 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 19 18:01:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 18:01:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9gt8-0007gt-P0; Mon, 19 Mar 2012 18:00:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9gt6-0007gh-Oh for xen-api@lists.xensource.com; Mon, 19 Mar 2012 18:00:56 +0000 Received: from [85.158.143.99:13276] by server-1.bemta-4.messagelabs.com id D8/DE-20925-854776F4; Mon, 19 Mar 2012 18:00:56 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1332180055!19902748!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDAxNA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20872 invoked from network); 19 Mar 2012 18:00:55 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Mar 2012 18:00:55 -0000 X-IronPort-AV: E=Sophos;i="4.73,612,1325462400"; d="scan'208";a="11393904" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Mar 2012 18:00:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Mon, 19 Mar 2012 18:00:55 +0000 From: John Garbutt To: 'Thomas Goirand' Date: Mon, 19 Mar 2012 18:00:54 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0F9UNWekWgfyUaSyS4ijd0Z7gHfQAAlEHg Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: <4F676BFC.702@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: PKG OpenStack , "openstack@lists.launchpad.net" , xen-api Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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, Looks like the network configuration is not quite right. Have a look at this, for an example of how things could look networking wise (when using DevStack and XenServer with two nics): http://wiki.openstack.org/XenServer/XenXCPAndXenServer The manuals have a good description, although it is a little KVM specific: http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-flat-dhcp-networking.html I suggested using DevStack because it is the best "documentation" for a working set of flags right now (yes, not ideal, we must fix that asap!). Take a look: https://github.com/openstack-dev/devstack/blob/master/stack.sh#L291 Note the defaults in the nova code might work for KVM, but will not work for XenServer, so you will need to set those flags with more appropriate values. Hope that helps, John -----Original Message----- From: Thomas Goirand [mailto:thomas@goirand.fr] Sent: 19 March 2012 5:25 To: John Garbutt Cc: Dave Scott; xen-api; PKG OpenStack; openstack@lists.launchpad.net Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface On 03/20/2012 12:05 AM, John Garbutt wrote: > This sounds a lot like a configuration issue with your guest network bridge. Are you OK to supply your nova.conf file? Sure! Here it is: --sql_connection=mysql://nova:admin@127.0.0.1/nova --novncproxy_base_url=http://:6080/vnc_auto.html --rabbit_host= --glance_api_servers=:9292 --network_manager=nova.network.manager.VlanManager --vlan_interface=br100 --dhcpbridge=/usr/bin/nova-dhcpbridge --firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver --connection_type=xenapi --xenapi_connection_url=https:// --xenapi_connection_username=root --xenapi_connection_password=XXXXXXX --reboot_timeout=600 --rescue_timeout=86400 --resize_confirm_window=86400 --auth_strategy=keystone --allow_admin_api --allow_resize_to_same_host --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/var/lock/nova --vncserver_listen=0.0.0.0 --force_dhcp_release --use_deprecated_auth --use_project_ca --verbose Note that since I restarted xcp-xapi, it seems that the xapi0 bridge is created each time I create a VM, which is what I was expecting. So that parts seems to work now, but the issue is that now, I have no networking at all (eg: I can't reach the instance from the Openstack domU). Here's what "xe network-list" returns on my dom0: uuid ( RO) : name-label ( RW): br100 name-description ( RW): network for nova bridge br100 bridge ( RO): xapi0 So it really is nova who created this. But shouldn't it be linked to my xenbr0 as well? What is the normal networking setup that should be done? There's absolutely zero documentation which I could find about this. Of course, I'll write one directly in our Debian packages as soon as this works. > Also, have you tried using DevStack first? It is a good way to get the hang of how the flags work. No it's not! DevStack is for testing with XenServer, and assumes that you'd be working with Ubuntu. Here, I'm testing the Debian packages that we are working on in Debian. Please don't direct me to DevStack, this wont help. > I'm not familiar with the design of the Nova plugins but my guess is that they're trying to use the "Host internal management network" -- a network from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). > > On recent XCP versions the default bridge name changed to "xenapi" to make it easier to distinguish from a firewall rules PoV. As per Mike on IRC, (from Citrix, upstream for XCP, XenServer and Kronos), each time there's a new network being created, XCP create a xapiX bridge automatically. I shouldn't have even try to bring the xapi0 bridge myself, XCP does it (if it doesn't, then there's an issue). > Note that the actual linux bridge (or openvswitch) is created on demand so you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. > > Try changing "xapi0" to "xenapi" in the plugins and see if they work better? Nop, that wont help, xapi0 is really what to expect. My only issue now is to have it connected to the br100 of Openstack in my domU. Thanks for the help already, Cheers, Thomas _______________________________________________ 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 19 18:20:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 18:20: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 1S9hC5-0007u7-Fa; Mon, 19 Mar 2012 18:20:33 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9hC4-0007ty-9M for xen-api@lists.xen.org; Mon, 19 Mar 2012 18:20:32 +0000 Received: from [85.158.143.35:60891] by server-1.bemta-4.messagelabs.com id CB/BA-20925-FE8776F4; Mon, 19 Mar 2012 18:20:31 +0000 X-Env-Sender: zhigang.x.wang@oracle.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1332181226!11337171!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDQwOTY4NA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5895 invoked from network); 19 Mar 2012 18:20:27 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Mar 2012 18:20:27 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q2JIKJ35008439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Mar 2012 18:20:20 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q2JIKHrA003622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Mar 2012 18:20:18 GMT Received: from abhmt114.oracle.com (abhmt114.oracle.com [141.146.116.66]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q2JIKGDU021092; Mon, 19 Mar 2012 13:20:17 -0500 Received: from zhigang.us.oracle.com (/10.149.236.110) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 19 Mar 2012 11:20:16 -0700 Message-ID: <4F6778F9.1080609@oracle.com> Date: Mon, 19 Mar 2012 14:20:41 -0400 From: Zhigang Wang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: Ian Campbell References: <1331732247.23971.438.camel@zakaz.uk.xensource.com> In-Reply-To: X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-CT-RefId: str=0001.0A090204.4F6778E4.00B3,ss=1,re=0.000,fgs=0 Cc: xen-api@lists.xen.org, Jim Fehlig , Bamvor Jian Zhang , Ian Jackson , xen-devel@lists.xen.org Subject: Re: [Xen-API] [PATCH] libxl: Document API and ABI compatibility guarantees X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Any thought on Python/OCaml bindings for this? Thanks, Zhigang On 03/19/2012 11:14 AM, Ian Campbell wrote: > # HG changeset patch > # User Ian Campbell > # Date 1332169579 0 > # Node ID f588c69fd12f17e81d3289653ae1e3b20cd41c11 > # Parent e10c4b937e8fa9159070584113e9378ca175f728 > libxl: Document API and ABI compatibility guarantees. > > Signed-off-by: Ian Campbell > > diff -r e10c4b937e8f -r f588c69fd12f tools/libxl/libxl.h > --- a/tools/libxl/libxl.h Mon Mar 19 14:24:01 2012 +0000 > +++ b/tools/libxl/libxl.h Mon Mar 19 15:06:19 2012 +0000 > @@ -14,6 +14,77 @@ > */ > > /* > + * libxl API compatibility > + * > + * From Xen 4.2 onwards the API of libxl will be maintained in a > + * stable manner. This means that it should be possible to write an > + * application against the API provided by libxl in Xen 4.2 and expect > + * that it will continue to compile against future versions of Xen > + * without source modification. > + * > + * In order to make such compatibility possible it is required that > + * application which want to be exposed to a particular API #define > + * LIBXL_API_VERSION before including libxl.h or any other libxl > + * header. The syntax of the LIBXL_API_VERSION is: > + * 0xVVSSEE > + * where ($(XEN_xxx) from xen/Makefile): > + * VV is the Xen major release number, $(XEN_VERSION) > + * SS is the Xen sub version number, $(XEN_SUBVERSION) > + * EE is the Xen extra version digit, first numeric part of > + * $(XEN_EXTRAVERSION) not including the leading "." > + * For example the first stable API version, supported by Xen 4.2.0, > + * is 0x040200. > + * > + * Lack of LIBXL_API_VERSION means "the latest" which will > + * change. Specifying an unknown LIBXL_API_VERSION will result in a > + * compile time error. > + * > + * Identical versions of the libxl API will represented by the version > + * containing the earliest instance of that API. e.g. if 4.2.0 and > + * 4.3.0 contain an identical libxl API then only LIBXL_API_VERSION > + * 0x040200 will be valid. > + * > + * We will try especially hard to avoid changing the API during a > + * stable series, i.e. it should be unusual for the last byte of > + * LIBXL_API_VERSION to be non-zero. > + * > + * In the event that a change is required which cannot be made > + * backwards compatible in this manner a #define of the form > + * LIBXL_HAVE_ will always be added in order to make it > + * possible to write applciations which build against any version of > + * libxl. Such changes are expected to be exceptional and used as a > + * last resort. The barrier for backporting such a change to a stable > + * branch will be very high. > + * > + * These guarantees apply only to stable releases of Xen. When an > + * incompatible change is made in the unstable tree then > + * LIBXL_API_VERSION will be bumped to the next expected stable > + * release number on the first such change only. Applications which > + * want to support building against Xen unstable are expected to track > + * API changes in that tree until it is released as a stable release. > + * > + * API compatibility will be maintained for all versions of Xen using > + * the same $(XEN_VERSION) (e.g. throughout a major release). > + */ > + > +/* > + * libxl ABI compatibility > + * > + * The only guarantee which libxl makes regarding ABI compatibility > + * across releases is that the SONAME will always be bumped whenever > + * the ABI is changed in an incompatible way. > + * > + * This applies within stable branches as well as > + * development branches. It is possible that a new stable release of > + * Xen may require a rebuild of applications using the > + * library. However per the API compatibility gaurantees such a > + * rebuild should not normally require any source level changes. > + * > + * As with the API compatiblity the SONAME will only be bumped for the > + * first ABI incompatible change in a development branch. > + */ > + > +/* > * libxl memory management > * > * From the point of view of the application (ie, libxl's caller), > @@ -184,6 +255,13 @@ > #include > #include <_libxl_list.h> > > +/* API compatibility. Only 0x040200 is supported at this time. */ > +#ifdef LIBXL_API_VERSION > +#if LIBXL_API_VERSION != 0x040200 > +#error Unknown LIBXL_API_VERSION > +#endif > +#endif > + > typedef uint8_t libxl_mac[6]; > #define LIBXL_MAC_FMT "%02hhx:%02hhx:%02hhx:%02hhx:%02hhx:%02hhx" > #define LIBXL_MAC_FMTLEN ((2*6)+5) /* 6 hex bytes plus 5 colons */ _______________________________________________ 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 19 18:20:39 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 19 Mar 2012 18:20: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 1S9hC5-0007u7-Fa; Mon, 19 Mar 2012 18:20:33 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9hC4-0007ty-9M for xen-api@lists.xen.org; Mon, 19 Mar 2012 18:20:32 +0000 Received: from [85.158.143.35:60891] by server-1.bemta-4.messagelabs.com id CB/BA-20925-FE8776F4; Mon, 19 Mar 2012 18:20:31 +0000 X-Env-Sender: zhigang.x.wang@oracle.com X-Msg-Ref: server-10.tower-21.messagelabs.com!1332181226!11337171!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDQwOTY4NA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5895 invoked from network); 19 Mar 2012 18:20:27 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Mar 2012 18:20:27 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q2JIKJ35008439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Mar 2012 18:20:20 GMT Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q2JIKHrA003622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Mar 2012 18:20:18 GMT Received: from abhmt114.oracle.com (abhmt114.oracle.com [141.146.116.66]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q2JIKGDU021092; Mon, 19 Mar 2012 13:20:17 -0500 Received: from zhigang.us.oracle.com (/10.149.236.110) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 19 Mar 2012 11:20:16 -0700 Message-ID: <4F6778F9.1080609@oracle.com> Date: Mon, 19 Mar 2012 14:20:41 -0400 From: Zhigang Wang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: Ian Campbell References: <1331732247.23971.438.camel@zakaz.uk.xensource.com> In-Reply-To: X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-CT-RefId: str=0001.0A090204.4F6778E4.00B3,ss=1,re=0.000,fgs=0 Cc: xen-api@lists.xen.org, Jim Fehlig , Bamvor Jian Zhang , Ian Jackson , xen-devel@lists.xen.org Subject: Re: [Xen-API] [PATCH] libxl: Document API and ABI compatibility guarantees X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Any thought on Python/OCaml bindings for this? Thanks, Zhigang On 03/19/2012 11:14 AM, Ian Campbell wrote: > # HG changeset patch > # User Ian Campbell > # Date 1332169579 0 > # Node ID f588c69fd12f17e81d3289653ae1e3b20cd41c11 > # Parent e10c4b937e8fa9159070584113e9378ca175f728 > libxl: Document API and ABI compatibility guarantees. > > Signed-off-by: Ian Campbell > > diff -r e10c4b937e8f -r f588c69fd12f tools/libxl/libxl.h > --- a/tools/libxl/libxl.h Mon Mar 19 14:24:01 2012 +0000 > +++ b/tools/libxl/libxl.h Mon Mar 19 15:06:19 2012 +0000 > @@ -14,6 +14,77 @@ > */ > > /* > + * libxl API compatibility > + * > + * From Xen 4.2 onwards the API of libxl will be maintained in a > + * stable manner. This means that it should be possible to write an > + * application against the API provided by libxl in Xen 4.2 and expect > + * that it will continue to compile against future versions of Xen > + * without source modification. > + * > + * In order to make such compatibility possible it is required that > + * application which want to be exposed to a particular API #define > + * LIBXL_API_VERSION before including libxl.h or any other libxl > + * header. The syntax of the LIBXL_API_VERSION is: > + * 0xVVSSEE > + * where ($(XEN_xxx) from xen/Makefile): > + * VV is the Xen major release number, $(XEN_VERSION) > + * SS is the Xen sub version number, $(XEN_SUBVERSION) > + * EE is the Xen extra version digit, first numeric part of > + * $(XEN_EXTRAVERSION) not including the leading "." > + * For example the first stable API version, supported by Xen 4.2.0, > + * is 0x040200. > + * > + * Lack of LIBXL_API_VERSION means "the latest" which will > + * change. Specifying an unknown LIBXL_API_VERSION will result in a > + * compile time error. > + * > + * Identical versions of the libxl API will represented by the version > + * containing the earliest instance of that API. e.g. if 4.2.0 and > + * 4.3.0 contain an identical libxl API then only LIBXL_API_VERSION > + * 0x040200 will be valid. > + * > + * We will try especially hard to avoid changing the API during a > + * stable series, i.e. it should be unusual for the last byte of > + * LIBXL_API_VERSION to be non-zero. > + * > + * In the event that a change is required which cannot be made > + * backwards compatible in this manner a #define of the form > + * LIBXL_HAVE_ will always be added in order to make it > + * possible to write applciations which build against any version of > + * libxl. Such changes are expected to be exceptional and used as a > + * last resort. The barrier for backporting such a change to a stable > + * branch will be very high. > + * > + * These guarantees apply only to stable releases of Xen. When an > + * incompatible change is made in the unstable tree then > + * LIBXL_API_VERSION will be bumped to the next expected stable > + * release number on the first such change only. Applications which > + * want to support building against Xen unstable are expected to track > + * API changes in that tree until it is released as a stable release. > + * > + * API compatibility will be maintained for all versions of Xen using > + * the same $(XEN_VERSION) (e.g. throughout a major release). > + */ > + > +/* > + * libxl ABI compatibility > + * > + * The only guarantee which libxl makes regarding ABI compatibility > + * across releases is that the SONAME will always be bumped whenever > + * the ABI is changed in an incompatible way. > + * > + * This applies within stable branches as well as > + * development branches. It is possible that a new stable release of > + * Xen may require a rebuild of applications using the > + * library. However per the API compatibility gaurantees such a > + * rebuild should not normally require any source level changes. > + * > + * As with the API compatiblity the SONAME will only be bumped for the > + * first ABI incompatible change in a development branch. > + */ > + > +/* > * libxl memory management > * > * From the point of view of the application (ie, libxl's caller), > @@ -184,6 +255,13 @@ > #include > #include <_libxl_list.h> > > +/* API compatibility. Only 0x040200 is supported at this time. */ > +#ifdef LIBXL_API_VERSION > +#if LIBXL_API_VERSION != 0x040200 > +#error Unknown LIBXL_API_VERSION > +#endif > +#endif > + > typedef uint8_t libxl_mac[6]; > #define LIBXL_MAC_FMT "%02hhx:%02hhx:%02hhx:%02hhx:%02hhx:%02hhx" > #define LIBXL_MAC_FMTLEN ((2*6)+5) /* 6 hex bytes plus 5 colons */ _______________________________________________ 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 20 16:42:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 20 Mar 2012 16:42:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA28a-0000m9-NL; Tue, 20 Mar 2012 16:42:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9oM8-0005dE-7s for xen-api@lists.xen.org; Tue, 20 Mar 2012 01:59:24 +0000 Received: from [85.158.143.35:18436] by server-1.bemta-4.messagelabs.com id BD/A0-20925-B74E76F4; Tue, 20 Mar 2012 01:59:23 +0000 X-Env-Sender: hyacin@archys.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1332208757!6506489!1 X-Originating-IP: [58.121.75.186] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7894 invoked from network); 20 Mar 2012 01:59:20 -0000 Received: from unknown (HELO archys.com) (58.121.75.186) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Mar 2012 01:59:20 -0000 Received: from JPC (external.com [218.236.77.176]) by archys.com (Postfix) with ESMTPA id 425E385D0C; Tue, 20 Mar 2012 10:29:58 +0900 (KST) From: =?ks_c_5601-1987?B?wMzA58ij?= To: Date: Tue, 20 Mar 2012 10:59:15 +0900 Message-ID: <000301cd063d$0df08290$29d187b0$@archys.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac0GODn4bmll7+OBS7Ozj1bdy1rD1g== Content-Language: ko X-Mailman-Approved-At: Tue, 20 Mar 2012 16:42:19 +0000 Subject: [Xen-API] How to use xcp-xapi and python binding on ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6335987075634494193==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multipart message in MIME format. --===============6335987075634494193== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01CD0688.7DE15250" Content-Language: ko This is a multipart message in MIME format. ------=_NextPart_000_0004_01CD0688.7DE15250 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Hello, My name is jaeho Lee and I am from Korea. =20 I want to develop xen-web-management software as using python and = xcp-xapi on ubuntu precise. =20 I have installed xcp-xapi on the ubuntu precise. - I refer to this site =A1=B0http://wiki.xen.org/wiki/Project_Kronos#Using_XCP_- _preparing_the_toolstack=A1=B1. =20 My questions is like below. 1. xapi deamon is xml-rpc server and can I use it through python? - I tried to find related site or documents but I couldn=A1=AFt = know what is right one. (There are too many documents.) - I checked it like this =A1=B0netstat -anp | grep xapi=A1=B1 and = it seem to work as a xml-rpc server. tcp 0 0 127.0.0.1:80 0.0.0.0:* = LISTEN 1362/xapi unix 2 [ ACC ] STREAM LISTENING 2006 1362/xapi /var/lib/xcp/storage unix 2 [ ACC ] STREAM LISTENING 2008 1362/xapi /var/lib/xcp/xapi unix 3 [ ] STREAM CONNECTED 9033 1362/xapi unix 2 [ ] DGRAM 2005 1362/xapi unix 3 [ ] STREAM CONNECTED 1959 1353/xapi unix 2 [ ] DGRAM 1958 1353/xapi =20 2. Is there any default account and password? - I tried to login as =A1=B0pool-admin=A1=B1, but failed. - The error message is like this = =A1=B0SESSION_AUTHENTICATION_FAILED=A1=B1. (Is that because of wrong password or user name? or other problem) =20 If I can get right documents or some hints related to xcp-xapi on ubuntu precise it will be very helpful for me. =20 Please refer to the below things. I tried to test authentication. import sys, time import XenAPI from pprint import pprint =20 if __name__ =3D=3D "__main__": # if len(sys.argv) <> 4: # print "Usage:" # print sys.argv[0], " " # sys.exit(1) url =3D "http://localhost" username =3D "admin" password =3D "" =20 def main(sx): print "main" vms =3D sx.VM.get_all() real_vms =3D [ x for x in vms if not sx.VM.get_is_a_template(x)] pprint ( [sx.VM.get_name_label(x) for x in real_vms] ) =20 if __name__ =3D=3D "__main__": # if len(sys.argv) <> 4: # print "Usage:" # print sys.argv[0], " " # sys.exit(1) url =3D "http://localhost" username =3D "admin" password =3D "" print "List of non-template VMs on %s" %url # First acquire a valid session by logging in: session =3D XenAPI.Session(url) =20 session.xenapi.login_with_password(username, password) =20 session.xenapi.VM.get_all() =20 root@vstb:~/VSTB/test_python# python2.7 test.py List of non-template VMs on http://localhost Traceback (most recent call last): File "test.py", line 40, in session.xenapi.login_with_password(username, password) File "/usr/lib/python2.7/dist-packages/XenAPI.py", line 235, in = __call__ return self.__send(self.__name, args) File "/usr/lib/python2.7/dist-packages/XenAPI.py", line 130, in xenapi_request self._login(methodname, params) File "/usr/lib/python2.7/dist-packages/XenAPI.py", line 154, in _login result =3D _parse_result(getattr(self, 'session.%s' % = method)(*params)) File "/usr/lib/python2.7/dist-packages/XenAPI.py", line 209, in _parse_result raise Failure(result['ErrorDescription']) XenAPI.Failure: ['SESSION_AUTHENTICATION_FAILED', 'admin', = 'Authentication failure'] root@vstb:~/VSTB/test_python# =20 Thank you. ------=_NextPart_000_0004_01CD0688.7DE15250 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable

Hello,

My name is jaeho Lee and I am from = Korea.

 

I want to develop xen-web-management software as using = python and xcp-xapi on ubuntu precise.

 

I have installed xcp-xapi on the = ubuntu precise.

-       = I refer to this = site =A1=B0http://wiki.xen.org/wiki/Project_Kronos#Using_XCP_-_preparing= _the_toolstack=A1=B1.

 

My questions is like = below.

1.     xapi deamon is xml-rpc server and can I use it through = python?

-       = I tried to find = related site or documents but I couldn=A1=AFt know what is right = one.

(There are too many documents.)

-       = I checked it like this = =A1=B0netstat –anp | grep xapi=A1=B1 and it seem to work as a = xml-rpc server.

tcp        = 0      0 = 127.0.0.1:80          &= nbsp; = 0.0.0.0:*          &nbs= p;    LISTEN      = 1362/xapi

unix  2      [ ACC = ]     STREAM     = LISTENING     2006     = 1362/xapi           = /var/lib/xcp/storage

unix  2      [ ACC = ]     STREAM     = LISTENING     2008     = 1362/xapi           = /var/lib/xcp/xapi

unix  3      [ ]  =        STREAM     = CONNECTED     9033     = 1362/xapi

unix  2      [ = ]         = DGRAM           &n= bsp;        = 2005     1362/xapi

unix  = 3      [ = ]         = STREAM     CONNECTED     = 1959     1353/xapi

unix  = 2      [ = ]         = DGRAM           &n= bsp;        = 1958     = 1353/xapi

 

2.     Is there any default account and = password?

-       = I tried to login as = =A1=B0pool-admin=A1=B1, but failed.

-       = The error message is = like this = =A1=B0SESSION_AUTHENTICATION_FAILED=A1=B1.

(Is that because of wrong password or user name? or other = problem)

 

If I can get right documents or some hints related to = xcp-xapi on ubuntu precise it will be very helpful for = me.

 

Please refer to the below things.

I tried to test = authentication.

<The simple code is like = below.>

import sys, time

import = XenAPI

from = pprint import pprint

 

if __name__ =3D=3D = "__main__":

#    if len(sys.argv) <> = 4:

#        print = "Usage:"

#        print = sys.argv[0], " <url> <username> = <password>"

#        = sys.exit(1)

    url =3D = "http://localhost"

    username =3D = "admin"

    password =3D = ""

 

def main(sx):

    print = "main"

    vms =3D = sx.VM.get_all()

    real_vms =3D [ x for x in vms if not = sx.VM.get_is_a_template(x)]

    pprint ( = [sx.VM.get_name_label(x) for x in real_vms] )

 

if __name__ =3D=3D = "__main__":

#    if len(sys.argv) <> = 4:

#        print = "Usage:"

#        print = sys.argv[0], " <url> <username> = <password>"

#        = sys.exit(1)

    url =3D = "http://localhost"

    username =3D = "admin"

    password =3D = ""

    print "List of non-template VMs on = %s" %url

    # First acquire a valid session by = logging in:

    session =3D = XenAPI.Session(url)

 

    = session.xenapi.login_with_password(username, = password)

 

    = session.xenapi.VM.get_all()

 

<The result is like = below>

root@vstb:~/VSTB/test_python# python2.7 = test.py

List of non-template VMs on = http://localhost

Traceback (most recent call last):

 File "test.py", = line 40, in <module>

    = session.xenapi.login_with_password(username, = password)

  File = "/usr/lib/python2.7/dist-packages/XenAPI.py", line 235, in = __call__

    return self.__send(self.__name, = args)

  File = "/usr/lib/python2.7/dist-packages/XenAPI.py", line 130, in = xenapi_request

    self._login(methodname, = params)

  File = "/usr/lib/python2.7/dist-packages/XenAPI.py", line 154, in = _login

    result =3D _parse_result(getattr(self, = 'session.%s' % method)(*params))

  File = "/usr/lib/python2.7/dist-packages/XenAPI.py", line 209, in = _parse_result

    raise = Failure(result['ErrorDescription'])

XenAPI.Failure: = ['SESSION_AUTHENTICATION_FAILED', 'admin', 'Authentication = failure']

root@vstb:~/VSTB/test_python#

 

Thank you.

------=_NextPart_000_0004_01CD0688.7DE15250-- --===============6335987075634494193== 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 --===============6335987075634494193==-- From xen-api-bounces@lists.xen.org Tue Mar 20 16:42:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 20 Mar 2012 16:42:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA28a-0000m9-NL; Tue, 20 Mar 2012 16:42:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1S9oM8-0005dE-7s for xen-api@lists.xen.org; Tue, 20 Mar 2012 01:59:24 +0000 Received: from [85.158.143.35:18436] by server-1.bemta-4.messagelabs.com id BD/A0-20925-B74E76F4; Tue, 20 Mar 2012 01:59:23 +0000 X-Env-Sender: hyacin@archys.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1332208757!6506489!1 X-Originating-IP: [58.121.75.186] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7894 invoked from network); 20 Mar 2012 01:59:20 -0000 Received: from unknown (HELO archys.com) (58.121.75.186) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Mar 2012 01:59:20 -0000 Received: from JPC (external.com [218.236.77.176]) by archys.com (Postfix) with ESMTPA id 425E385D0C; Tue, 20 Mar 2012 10:29:58 +0900 (KST) From: =?ks_c_5601-1987?B?wMzA58ij?= To: Date: Tue, 20 Mar 2012 10:59:15 +0900 Message-ID: <000301cd063d$0df08290$29d187b0$@archys.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac0GODn4bmll7+OBS7Ozj1bdy1rD1g== Content-Language: ko X-Mailman-Approved-At: Tue, 20 Mar 2012 16:42:19 +0000 Subject: [Xen-API] How to use xcp-xapi and python binding on ubuntu X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6335987075634494193==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multipart message in MIME format. --===============6335987075634494193== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01CD0688.7DE15250" Content-Language: ko This is a multipart message in MIME format. ------=_NextPart_000_0004_01CD0688.7DE15250 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Hello, My name is jaeho Lee and I am from Korea. =20 I want to develop xen-web-management software as using python and = xcp-xapi on ubuntu precise. =20 I have installed xcp-xapi on the ubuntu precise. - I refer to this site =A1=B0http://wiki.xen.org/wiki/Project_Kronos#Using_XCP_- _preparing_the_toolstack=A1=B1. =20 My questions is like below. 1. xapi deamon is xml-rpc server and can I use it through python? - I tried to find related site or documents but I couldn=A1=AFt = know what is right one. (There are too many documents.) - I checked it like this =A1=B0netstat -anp | grep xapi=A1=B1 and = it seem to work as a xml-rpc server. tcp 0 0 127.0.0.1:80 0.0.0.0:* = LISTEN 1362/xapi unix 2 [ ACC ] STREAM LISTENING 2006 1362/xapi /var/lib/xcp/storage unix 2 [ ACC ] STREAM LISTENING 2008 1362/xapi /var/lib/xcp/xapi unix 3 [ ] STREAM CONNECTED 9033 1362/xapi unix 2 [ ] DGRAM 2005 1362/xapi unix 3 [ ] STREAM CONNECTED 1959 1353/xapi unix 2 [ ] DGRAM 1958 1353/xapi =20 2. Is there any default account and password? - I tried to login as =A1=B0pool-admin=A1=B1, but failed. - The error message is like this = =A1=B0SESSION_AUTHENTICATION_FAILED=A1=B1. (Is that because of wrong password or user name? or other problem) =20 If I can get right documents or some hints related to xcp-xapi on ubuntu precise it will be very helpful for me. =20 Please refer to the below things. I tried to test authentication. import sys, time import XenAPI from pprint import pprint =20 if __name__ =3D=3D "__main__": # if len(sys.argv) <> 4: # print "Usage:" # print sys.argv[0], " " # sys.exit(1) url =3D "http://localhost" username =3D "admin" password =3D "" =20 def main(sx): print "main" vms =3D sx.VM.get_all() real_vms =3D [ x for x in vms if not sx.VM.get_is_a_template(x)] pprint ( [sx.VM.get_name_label(x) for x in real_vms] ) =20 if __name__ =3D=3D "__main__": # if len(sys.argv) <> 4: # print "Usage:" # print sys.argv[0], " " # sys.exit(1) url =3D "http://localhost" username =3D "admin" password =3D "" print "List of non-template VMs on %s" %url # First acquire a valid session by logging in: session =3D XenAPI.Session(url) =20 session.xenapi.login_with_password(username, password) =20 session.xenapi.VM.get_all() =20 root@vstb:~/VSTB/test_python# python2.7 test.py List of non-template VMs on http://localhost Traceback (most recent call last): File "test.py", line 40, in session.xenapi.login_with_password(username, password) File "/usr/lib/python2.7/dist-packages/XenAPI.py", line 235, in = __call__ return self.__send(self.__name, args) File "/usr/lib/python2.7/dist-packages/XenAPI.py", line 130, in xenapi_request self._login(methodname, params) File "/usr/lib/python2.7/dist-packages/XenAPI.py", line 154, in _login result =3D _parse_result(getattr(self, 'session.%s' % = method)(*params)) File "/usr/lib/python2.7/dist-packages/XenAPI.py", line 209, in _parse_result raise Failure(result['ErrorDescription']) XenAPI.Failure: ['SESSION_AUTHENTICATION_FAILED', 'admin', = 'Authentication failure'] root@vstb:~/VSTB/test_python# =20 Thank you. ------=_NextPart_000_0004_01CD0688.7DE15250 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable

Hello,

My name is jaeho Lee and I am from = Korea.

 

I want to develop xen-web-management software as using = python and xcp-xapi on ubuntu precise.

 

I have installed xcp-xapi on the = ubuntu precise.

-       = I refer to this = site =A1=B0http://wiki.xen.org/wiki/Project_Kronos#Using_XCP_-_preparing= _the_toolstack=A1=B1.

 

My questions is like = below.

1.     xapi deamon is xml-rpc server and can I use it through = python?

-       = I tried to find = related site or documents but I couldn=A1=AFt know what is right = one.

(There are too many documents.)

-       = I checked it like this = =A1=B0netstat –anp | grep xapi=A1=B1 and it seem to work as a = xml-rpc server.

tcp        = 0      0 = 127.0.0.1:80          &= nbsp; = 0.0.0.0:*          &nbs= p;    LISTEN      = 1362/xapi

unix  2      [ ACC = ]     STREAM     = LISTENING     2006     = 1362/xapi           = /var/lib/xcp/storage

unix  2      [ ACC = ]     STREAM     = LISTENING     2008     = 1362/xapi           = /var/lib/xcp/xapi

unix  3      [ ]  =        STREAM     = CONNECTED     9033     = 1362/xapi

unix  2      [ = ]         = DGRAM           &n= bsp;        = 2005     1362/xapi

unix  = 3      [ = ]         = STREAM     CONNECTED     = 1959     1353/xapi

unix  = 2      [ = ]         = DGRAM           &n= bsp;        = 1958     = 1353/xapi

 

2.     Is there any default account and = password?

-       = I tried to login as = =A1=B0pool-admin=A1=B1, but failed.

-       = The error message is = like this = =A1=B0SESSION_AUTHENTICATION_FAILED=A1=B1.

(Is that because of wrong password or user name? or other = problem)

 

If I can get right documents or some hints related to = xcp-xapi on ubuntu precise it will be very helpful for = me.

 

Please refer to the below things.

I tried to test = authentication.

<The simple code is like = below.>

import sys, time

import = XenAPI

from = pprint import pprint

 

if __name__ =3D=3D = "__main__":

#    if len(sys.argv) <> = 4:

#        print = "Usage:"

#        print = sys.argv[0], " <url> <username> = <password>"

#        = sys.exit(1)

    url =3D = "http://localhost"

    username =3D = "admin"

    password =3D = ""

 

def main(sx):

    print = "main"

    vms =3D = sx.VM.get_all()

    real_vms =3D [ x for x in vms if not = sx.VM.get_is_a_template(x)]

    pprint ( = [sx.VM.get_name_label(x) for x in real_vms] )

 

if __name__ =3D=3D = "__main__":

#    if len(sys.argv) <> = 4:

#        print = "Usage:"

#        print = sys.argv[0], " <url> <username> = <password>"

#        = sys.exit(1)

    url =3D = "http://localhost"

    username =3D = "admin"

    password =3D = ""

    print "List of non-template VMs on = %s" %url

    # First acquire a valid session by = logging in:

    session =3D = XenAPI.Session(url)

 

    = session.xenapi.login_with_password(username, = password)

 

    = session.xenapi.VM.get_all()

 

<The result is like = below>

root@vstb:~/VSTB/test_python# python2.7 = test.py

List of non-template VMs on = http://localhost

Traceback (most recent call last):

 File "test.py", = line 40, in <module>

    = session.xenapi.login_with_password(username, = password)

  File = "/usr/lib/python2.7/dist-packages/XenAPI.py", line 235, in = __call__

    return self.__send(self.__name, = args)

  File = "/usr/lib/python2.7/dist-packages/XenAPI.py", line 130, in = xenapi_request

    self._login(methodname, = params)

  File = "/usr/lib/python2.7/dist-packages/XenAPI.py", line 154, in = _login

    result =3D _parse_result(getattr(self, = 'session.%s' % method)(*params))

  File = "/usr/lib/python2.7/dist-packages/XenAPI.py", line 209, in = _parse_result

    raise = Failure(result['ErrorDescription'])

XenAPI.Failure: = ['SESSION_AUTHENTICATION_FAILED', 'admin', 'Authentication = failure']

root@vstb:~/VSTB/test_python#

 

Thank you.

------=_NextPart_000_0004_01CD0688.7DE15250-- --===============6335987075634494193== 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 --===============6335987075634494193==-- From xen-api-bounces@lists.xen.org Tue Mar 20 19:35:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 20 Mar 2012 19:35:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA4py-0000UD-Hi; Tue, 20 Mar 2012 19:35:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA4px-0000U8-BW for xen-api@lists.xen.org; Tue, 20 Mar 2012 19:35:17 +0000 Received: from [193.109.254.147:17346] by server-6.bemta-14.messagelabs.com id 64/67-02047-4FBD86F4; Tue, 20 Mar 2012 19:35:16 +0000 X-Env-Sender: morrison.brendan17@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1332272114!1359808!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=2.0 required=7.0 tests=BODY_RANDOM_LONG, HTML_00_10, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6304 invoked from network); 20 Mar 2012 19:35:15 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Mar 2012 19:35:15 -0000 Received: by iafj26 with SMTP id j26so505554iaf.32 for ; Tue, 20 Mar 2012 12:35:14 -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=1L0h6n1zjsMLKoB7W0aVsKCLFfFqHRQXg04DwVaFnVQ=; b=Peh7nUH/yXXmoruPcF/V+qKVfVEwUouyBJPp2TO2zHT1j2FOkpcLZYvalB+ODtJ0fv 9LROn5hhI1dTOHS0VCI/7WjcU1mrirlYxIgAxdi9xk/GF6QxajeHXY1GBnHaPwpwOO01 +zalhJKqjMh0ijXi+P0CeCi6srnYo/Vn9u3sE+35JfOzRsrS4bPUMb6deyYOzBh3ckBW PMQHtDsaKTrVoS0WqvDttmu67sKn4FKZRbsEnFSv+e8vQPpzsbVhkfHGyXsx7TiR8hde /a9XxcoJbBA29LHnJBa9Xn1EvPWib5s50db6SyjK9hpq1QAX2BjWQiG2+F1FnHUvAk6j f9MA== MIME-Version: 1.0 Received: by 10.50.34.200 with SMTP id b8mr862188igj.50.1332272114237; Tue, 20 Mar 2012 12:35:14 -0700 (PDT) Received: by 10.231.105.196 with HTTP; Tue, 20 Mar 2012 12:35:14 -0700 (PDT) Date: Tue, 20 Mar 2012 15:35:14 -0400 Message-ID: From: Brendan Morrison To: xen-api@lists.xen.org Subject: [Xen-API] capabilities of xen migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7929020365817874623==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7929020365817874623== Content-Type: multipart/alternative; boundary=14dae93409a31d01b704bbb1c688 --14dae93409a31d01b704bbb1c688 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I have recently finished a project researching solutions to perform virtual machine migration across ip subnets while maintaining tcp/ip connections. I am currently looking into continuing this work at a masters level and/ or using it for the google summer of code under either organization debian, or Gentoo. Anyways the current virtualization tecknology used is KVM and it is a limiting factor in our design. As such I am trying to look into other free open source technologies I can use for virtualization. Basically I am wondering the current capabilities of XEN mainly for live migration purposes and more specifically if there is any capability that would allow me to migrate a VM while it is running and upon completion of migration be left with 2 instances of the VM running? I understand that the two machines will obviously not be synchronized .. unless thats possible too? But I am woundering what current built in capabilities are as I would much rather focus on the networking side of the problem and limit the hacking to the current migration technologies to improve the design as this networking is more to where my expertise reside. Thanks in advance brendan --14dae93409a31d01b704bbb1c688 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello all, I have recently finished a project researching solutions to perf= orm virtual machine migration across ip subnets while=A0maintaining=A0tcp/i= p connections. I am currently looking into continuing this work at a master= s level and/ or using it for the google summer of code under either organiz= ation debian, or Gentoo. Anyways the current virtualization tecknology used= is KVM and it is a limiting factor in our design. As such I am trying to l= ook into other free open source=A0technologies=A0I can use for virtualizati= on.=A0

Basically I am=A0wondering=A0the current capabilities of XEN= mainly for live migration purposes and more specifically if there is any c= apability that would=A0allow=A0me to migrate a VM while it is running and u= pon completion of migration be left with 2 instances of the VM running?=A0<= /div>

I understand that the two machines will obviously not b= e synchronized .. unless thats possible too? But I am woundering what curre= nt built in capabilities are as I would much rather focus on the networking= side of the problem and limit the hacking to the current=A0migration=A0tec= hnologies to=A0improve=A0the design as this networking is more to where my = expertise reside.=A0
Thanks in advance=A0
brendan=A0
--14dae93409a31d01b704bbb1c688-- --===============7929020365817874623== 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 --===============7929020365817874623==-- From xen-api-bounces@lists.xen.org Tue Mar 20 19:35:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 20 Mar 2012 19:35:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA4py-0000UD-Hi; Tue, 20 Mar 2012 19:35:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA4px-0000U8-BW for xen-api@lists.xen.org; Tue, 20 Mar 2012 19:35:17 +0000 Received: from [193.109.254.147:17346] by server-6.bemta-14.messagelabs.com id 64/67-02047-4FBD86F4; Tue, 20 Mar 2012 19:35:16 +0000 X-Env-Sender: morrison.brendan17@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1332272114!1359808!1 X-Originating-IP: [209.85.210.173] X-SpamReason: No, hits=2.0 required=7.0 tests=BODY_RANDOM_LONG, HTML_00_10, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6304 invoked from network); 20 Mar 2012 19:35:15 -0000 Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com) (209.85.210.173) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Mar 2012 19:35:15 -0000 Received: by iafj26 with SMTP id j26so505554iaf.32 for ; Tue, 20 Mar 2012 12:35:14 -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=1L0h6n1zjsMLKoB7W0aVsKCLFfFqHRQXg04DwVaFnVQ=; b=Peh7nUH/yXXmoruPcF/V+qKVfVEwUouyBJPp2TO2zHT1j2FOkpcLZYvalB+ODtJ0fv 9LROn5hhI1dTOHS0VCI/7WjcU1mrirlYxIgAxdi9xk/GF6QxajeHXY1GBnHaPwpwOO01 +zalhJKqjMh0ijXi+P0CeCi6srnYo/Vn9u3sE+35JfOzRsrS4bPUMb6deyYOzBh3ckBW PMQHtDsaKTrVoS0WqvDttmu67sKn4FKZRbsEnFSv+e8vQPpzsbVhkfHGyXsx7TiR8hde /a9XxcoJbBA29LHnJBa9Xn1EvPWib5s50db6SyjK9hpq1QAX2BjWQiG2+F1FnHUvAk6j f9MA== MIME-Version: 1.0 Received: by 10.50.34.200 with SMTP id b8mr862188igj.50.1332272114237; Tue, 20 Mar 2012 12:35:14 -0700 (PDT) Received: by 10.231.105.196 with HTTP; Tue, 20 Mar 2012 12:35:14 -0700 (PDT) Date: Tue, 20 Mar 2012 15:35:14 -0400 Message-ID: From: Brendan Morrison To: xen-api@lists.xen.org Subject: [Xen-API] capabilities of xen migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7929020365817874623==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7929020365817874623== Content-Type: multipart/alternative; boundary=14dae93409a31d01b704bbb1c688 --14dae93409a31d01b704bbb1c688 Content-Type: text/plain; charset=ISO-8859-1 Hello all, I have recently finished a project researching solutions to perform virtual machine migration across ip subnets while maintaining tcp/ip connections. I am currently looking into continuing this work at a masters level and/ or using it for the google summer of code under either organization debian, or Gentoo. Anyways the current virtualization tecknology used is KVM and it is a limiting factor in our design. As such I am trying to look into other free open source technologies I can use for virtualization. Basically I am wondering the current capabilities of XEN mainly for live migration purposes and more specifically if there is any capability that would allow me to migrate a VM while it is running and upon completion of migration be left with 2 instances of the VM running? I understand that the two machines will obviously not be synchronized .. unless thats possible too? But I am woundering what current built in capabilities are as I would much rather focus on the networking side of the problem and limit the hacking to the current migration technologies to improve the design as this networking is more to where my expertise reside. Thanks in advance brendan --14dae93409a31d01b704bbb1c688 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello all, I have recently finished a project researching solutions to perf= orm virtual machine migration across ip subnets while=A0maintaining=A0tcp/i= p connections. I am currently looking into continuing this work at a master= s level and/ or using it for the google summer of code under either organiz= ation debian, or Gentoo. Anyways the current virtualization tecknology used= is KVM and it is a limiting factor in our design. As such I am trying to l= ook into other free open source=A0technologies=A0I can use for virtualizati= on.=A0

Basically I am=A0wondering=A0the current capabilities of XEN= mainly for live migration purposes and more specifically if there is any c= apability that would=A0allow=A0me to migrate a VM while it is running and u= pon completion of migration be left with 2 instances of the VM running?=A0<= /div>

I understand that the two machines will obviously not b= e synchronized .. unless thats possible too? But I am woundering what curre= nt built in capabilities are as I would much rather focus on the networking= side of the problem and limit the hacking to the current=A0migration=A0tec= hnologies to=A0improve=A0the design as this networking is more to where my = expertise reside.=A0
Thanks in advance=A0
brendan=A0
--14dae93409a31d01b704bbb1c688-- --===============7929020365817874623== 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 --===============7929020365817874623==-- From xen-api-bounces@lists.xen.org Tue Mar 20 23:05:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 20 Mar 2012 23:05: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 1SA86z-0005OS-Rl; Tue, 20 Mar 2012 23:05:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA86y-0005OI-30 for xen-api@lists.xensource.com; Tue, 20 Mar 2012 23:05:04 +0000 Received: from [85.158.143.35:39605] by server-3.bemta-4.messagelabs.com id 3C/4F-05853-F1D096F4; Tue, 20 Mar 2012 23:05:03 +0000 X-Env-Sender: Ewan.Mellor@eu.citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1332284702!6056018!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDUxMw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1567 invoked from network); 20 Mar 2012 23:05:02 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Mar 2012 23:05:02 -0000 X-IronPort-AV: E=Sophos;i="4.73,621,1325462400"; d="scan'208";a="11427240" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 Mar 2012 23:05:01 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Tue, 20 Mar 2012 23:05:02 +0000 From: Ewan Mellor To: Thomas Goirand , John Garbutt Date: Tue, 20 Mar 2012 23:05:05 +0000 Thread-Topic: [Openstack] [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0F+ieSWmEzma/yTMG8KWlvHwEIyQA8raSw Message-ID: <6005BE083BF501439A84DC3523BAC82DC4BC0BB8F1@LONPMAILBOX01.citrite.net> References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: <4F676BFC.702@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: xen-api , PKG OpenStack , "openstack@lists.launchpad.net" Subject: Re: [Xen-API] [Openstack] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > -----Original Message----- > > > Also, have you tried using DevStack first? It is a good way to get > the hang of how the flags work. > > No it's not! DevStack is for testing with XenServer, and assumes that > you'd be working with Ubuntu. Here, I'm testing the Debian packages > that > we are working on in Debian. Please don't direct me to DevStack, this > wont help. DevStack _will_ help, and that's why we keep telling you to go look there, and I have no idea why you keep refusing. You don't have to run it, but it's up-to-date, and it's working, so it's a nice, clean, self-documenting example of at least one way that someone has managed to make this work. If you have differences between your system and DevStack because of the differences between Debian and Ubuntu or XenServer and XCP, then fine. If you have differences that you don't understand, then you're probably doing it wrong. That's why we tell you, on a weekly basis, to go look at DevStack if you want to see how a flag should be set. You can either do this the easy way, by following other people's working systems, or you can do it the hard way, by deep-diving into every single detail. I'm fine if you want to do it the hard way -- you'll certainly learn a lot, and it's probably very interesting and useful knowledge for the future. Just don't keep complaining that it's all too hard and then refuse to take the easy option. Ewan. _______________________________________________ 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 20 23:05:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 20 Mar 2012 23:05: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 1SA86z-0005OS-Rl; Tue, 20 Mar 2012 23:05:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA86y-0005OI-30 for xen-api@lists.xensource.com; Tue, 20 Mar 2012 23:05:04 +0000 Received: from [85.158.143.35:39605] by server-3.bemta-4.messagelabs.com id 3C/4F-05853-F1D096F4; Tue, 20 Mar 2012 23:05:03 +0000 X-Env-Sender: Ewan.Mellor@eu.citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1332284702!6056018!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDUxMw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1567 invoked from network); 20 Mar 2012 23:05:02 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Mar 2012 23:05:02 -0000 X-IronPort-AV: E=Sophos;i="4.73,621,1325462400"; d="scan'208";a="11427240" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 20 Mar 2012 23:05:01 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Tue, 20 Mar 2012 23:05:02 +0000 From: Ewan Mellor To: Thomas Goirand , John Garbutt Date: Tue, 20 Mar 2012 23:05:05 +0000 Thread-Topic: [Openstack] [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0F+ieSWmEzma/yTMG8KWlvHwEIyQA8raSw Message-ID: <6005BE083BF501439A84DC3523BAC82DC4BC0BB8F1@LONPMAILBOX01.citrite.net> References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: <4F676BFC.702@goirand.fr> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: xen-api , PKG OpenStack , "openstack@lists.launchpad.net" Subject: Re: [Xen-API] [Openstack] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > -----Original Message----- > > > Also, have you tried using DevStack first? It is a good way to get > the hang of how the flags work. > > No it's not! DevStack is for testing with XenServer, and assumes that > you'd be working with Ubuntu. Here, I'm testing the Debian packages > that > we are working on in Debian. Please don't direct me to DevStack, this > wont help. DevStack _will_ help, and that's why we keep telling you to go look there, and I have no idea why you keep refusing. You don't have to run it, but it's up-to-date, and it's working, so it's a nice, clean, self-documenting example of at least one way that someone has managed to make this work. If you have differences between your system and DevStack because of the differences between Debian and Ubuntu or XenServer and XCP, then fine. If you have differences that you don't understand, then you're probably doing it wrong. That's why we tell you, on a weekly basis, to go look at DevStack if you want to see how a flag should be set. You can either do this the easy way, by following other people's working systems, or you can do it the hard way, by deep-diving into every single detail. I'm fine if you want to do it the hard way -- you'll certainly learn a lot, and it's probably very interesting and useful knowledge for the future. Just don't keep complaining that it's all too hard and then refuse to take the easy option. Ewan. _______________________________________________ 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 21 01:43:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 21 Mar 2012 01:43:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAAaK-0002hc-3c; Wed, 21 Mar 2012 01:43:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAAaI-0002hX-Qa for xen-api@lists.xen.org; Wed, 21 Mar 2012 01:43:31 +0000 Received: from [85.158.143.99:4364] by server-2.bemta-4.messagelabs.com id 02/27-17550-142396F4; Wed, 21 Mar 2012 01:43:29 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1332294208!13800118!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1855 invoked from network); 21 Mar 2012 01:43:28 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 01:43:28 -0000 Received: by bkcjg9 with SMTP id jg9so621883bkc.32 for ; Tue, 20 Mar 2012 18:43:27 -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=NFte/W9JfU36GMUJ0u/xhU18PEtvV3+OjDAqrreARU8=; b=K8xx80Lyr6Hx4+vv28yaS4eGPGm3t+ogPRK9qAaudbqpX50NCC/9KImAcVnVf2amEW ChGlL8r58U6NCmd48l+aAITXxtMI4ue/T2lwCRziWx9qCnC1zekpgK8kWbvjRAZN0Crm 7Bw829CVmWzINyhkUxiQBap1pWaEqoCl88zDJbJcGz4SZWNkbxsZZbDLj3U8xe2olNfy ybuyUqGaKg4X6axcGVtRObQE6tQZnk90SfSlBjdHT/VqZ12wIUWV3ThywdbKeg+26AlF WNLHFstGoTfPQyYyq43uV7OLOkzidrZFQwk1y9QaZriZoo2Pwjm3UzL9saZiwMmY9fjN rv8g== Received: by 10.205.122.144 with SMTP id gg16mr818117bkc.12.1332294207748; Tue, 20 Mar 2012 18:43:27 -0700 (PDT) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id jr13sm268722bkb.14.2012.03.20.18.43.25 (version=SSLv3 cipher=OTHER); Tue, 20 Mar 2012 18:43:26 -0700 (PDT) Message-ID: <4F693248.5070009@gmail.com> Date: Wed, 21 Mar 2012 05:43:36 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] capabilities of xen migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8991968558984473407==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8991968558984473407== Content-Type: multipart/alternative; boundary="------------010902010808080006090509" This is a multi-part message in MIME format. --------------010902010808080006090509 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 20.03.2012 23:35, Brendan Morrison wrote: > Hello all, I have recently finished a project researching solutions to > perform virtual machine migration across ip subnets > while maintaining tcp/ip connections. I am currently looking into > continuing this work at a masters level and/ or using it for the > google summer of code under either organization debian, or Gentoo. > Anyways the current virtualization tecknology used is KVM and it is a > limiting factor in our design. As such I am trying to look into other > free open source technologies I can use for virtualization. > > Basically I am wondering the current capabilities of XEN mainly for > live migration purposes and more specifically if there is any > capability that would allow me to migrate a VM while it is running and > upon completion of migration be left with 2 instances of the VM running? > > I understand that the two machines will obviously not be synchronized > .. unless thats possible too? But I am woundering what current built > in capabilities are as I would much rather focus on the networking > side of the problem and limit the hacking to the > current migration technologies to improve the design as this > networking is more to where my expertise reside. > Thanks in advance > brendan > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api I see no specific problem with this. Any migration at the end is just 'create new domain', 'copy', 'destroy old domain'. You can modify xapi sources or xen sources not to wait death of original domain, but just change it uuid to 'technical' to avoid confusion. The main problem is that migration is usually solution to free node for maintenance, so 'leftover' domain will die... I thought about way to do that type of migration, and the simplest way I found (without modifying toolstack or deep changing in guest domain) is just use a /32 networks (IPv4). In that case all packets will be routed via gateway (outside designated network). During migration route will be just replaced with new route table in guest domain and router(s). If you do that, all traffic (except few dropped packets, which is not problem for TCP) will be routed to new designation and accepted by guest. --------------010902010808080006090509 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 20.03.2012 23:35, Brendan Morrison wrote:
Hello all, I have recently finished a project researching solutions to perform virtual machine migration across ip subnets while maintaining tcp/ip connections. I am currently looking into continuing this work at a masters level and/ or using it for the google summer of code under either organization debian, or Gentoo. Anyways the current virtualization tecknology used is KVM and it is a limiting factor in our design. As such I am trying to look into other free open source technologies I can use for virtualization. 

Basically I am wondering the current capabilities of XEN mainly for live migration purposes and more specifically if there is any capability that would allow me to migrate a VM while it is running and upon completion of migration be left with 2 instances of the VM running? 

I understand that the two machines will obviously not be synchronized .. unless thats possible too? But I am woundering what current built in capabilities are as I would much rather focus on the networking side of the problem and limit the hacking to the current migration technologies to improve the design as this networking is more to where my expertise reside. 
Thanks in advance 
brendan 


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

I see no specific problem with this. Any migration at the end is just 'create new domain', 'copy', 'destroy old domain'. You can modify xapi sources or xen sources not to wait death of original domain, but just change it uuid to 'technical' to avoid confusion. The main problem is that migration is usually solution to free node for maintenance, so 'leftover' domain will die...

I thought about way to do that type of migration, and the  simplest way I found (without modifying toolstack or deep changing in guest domain) is just use a /32 networks (IPv4). In that case all packets will be routed via gateway (outside designated network). During migration route will be just replaced with new route table in guest domain and router(s).

If you do that, all traffic (except few dropped packets, which is not problem for TCP) will be routed to new designation and accepted by guest.
--------------010902010808080006090509-- --===============8991968558984473407== 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 --===============8991968558984473407==-- From xen-api-bounces@lists.xen.org Wed Mar 21 01:43:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 21 Mar 2012 01:43:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAAaK-0002hc-3c; Wed, 21 Mar 2012 01:43:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAAaI-0002hX-Qa for xen-api@lists.xen.org; Wed, 21 Mar 2012 01:43:31 +0000 Received: from [85.158.143.99:4364] by server-2.bemta-4.messagelabs.com id 02/27-17550-142396F4; Wed, 21 Mar 2012 01:43:29 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1332294208!13800118!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1855 invoked from network); 21 Mar 2012 01:43:28 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 01:43:28 -0000 Received: by bkcjg9 with SMTP id jg9so621883bkc.32 for ; Tue, 20 Mar 2012 18:43:27 -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=NFte/W9JfU36GMUJ0u/xhU18PEtvV3+OjDAqrreARU8=; b=K8xx80Lyr6Hx4+vv28yaS4eGPGm3t+ogPRK9qAaudbqpX50NCC/9KImAcVnVf2amEW ChGlL8r58U6NCmd48l+aAITXxtMI4ue/T2lwCRziWx9qCnC1zekpgK8kWbvjRAZN0Crm 7Bw829CVmWzINyhkUxiQBap1pWaEqoCl88zDJbJcGz4SZWNkbxsZZbDLj3U8xe2olNfy ybuyUqGaKg4X6axcGVtRObQE6tQZnk90SfSlBjdHT/VqZ12wIUWV3ThywdbKeg+26AlF WNLHFstGoTfPQyYyq43uV7OLOkzidrZFQwk1y9QaZriZoo2Pwjm3UzL9saZiwMmY9fjN rv8g== Received: by 10.205.122.144 with SMTP id gg16mr818117bkc.12.1332294207748; Tue, 20 Mar 2012 18:43:27 -0700 (PDT) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id jr13sm268722bkb.14.2012.03.20.18.43.25 (version=SSLv3 cipher=OTHER); Tue, 20 Mar 2012 18:43:26 -0700 (PDT) Message-ID: <4F693248.5070009@gmail.com> Date: Wed, 21 Mar 2012 05:43:36 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] capabilities of xen migration X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8991968558984473407==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============8991968558984473407== Content-Type: multipart/alternative; boundary="------------010902010808080006090509" This is a multi-part message in MIME format. --------------010902010808080006090509 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 20.03.2012 23:35, Brendan Morrison wrote: > Hello all, I have recently finished a project researching solutions to > perform virtual machine migration across ip subnets > while maintaining tcp/ip connections. I am currently looking into > continuing this work at a masters level and/ or using it for the > google summer of code under either organization debian, or Gentoo. > Anyways the current virtualization tecknology used is KVM and it is a > limiting factor in our design. As such I am trying to look into other > free open source technologies I can use for virtualization. > > Basically I am wondering the current capabilities of XEN mainly for > live migration purposes and more specifically if there is any > capability that would allow me to migrate a VM while it is running and > upon completion of migration be left with 2 instances of the VM running? > > I understand that the two machines will obviously not be synchronized > .. unless thats possible too? But I am woundering what current built > in capabilities are as I would much rather focus on the networking > side of the problem and limit the hacking to the > current migration technologies to improve the design as this > networking is more to where my expertise reside. > Thanks in advance > brendan > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api I see no specific problem with this. Any migration at the end is just 'create new domain', 'copy', 'destroy old domain'. You can modify xapi sources or xen sources not to wait death of original domain, but just change it uuid to 'technical' to avoid confusion. The main problem is that migration is usually solution to free node for maintenance, so 'leftover' domain will die... I thought about way to do that type of migration, and the simplest way I found (without modifying toolstack or deep changing in guest domain) is just use a /32 networks (IPv4). In that case all packets will be routed via gateway (outside designated network). During migration route will be just replaced with new route table in guest domain and router(s). If you do that, all traffic (except few dropped packets, which is not problem for TCP) will be routed to new designation and accepted by guest. --------------010902010808080006090509 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 20.03.2012 23:35, Brendan Morrison wrote:
Hello all, I have recently finished a project researching solutions to perform virtual machine migration across ip subnets while maintaining tcp/ip connections. I am currently looking into continuing this work at a masters level and/ or using it for the google summer of code under either organization debian, or Gentoo. Anyways the current virtualization tecknology used is KVM and it is a limiting factor in our design. As such I am trying to look into other free open source technologies I can use for virtualization. 

Basically I am wondering the current capabilities of XEN mainly for live migration purposes and more specifically if there is any capability that would allow me to migrate a VM while it is running and upon completion of migration be left with 2 instances of the VM running? 

I understand that the two machines will obviously not be synchronized .. unless thats possible too? But I am woundering what current built in capabilities are as I would much rather focus on the networking side of the problem and limit the hacking to the current migration technologies to improve the design as this networking is more to where my expertise reside. 
Thanks in advance 
brendan 


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

I see no specific problem with this. Any migration at the end is just 'create new domain', 'copy', 'destroy old domain'. You can modify xapi sources or xen sources not to wait death of original domain, but just change it uuid to 'technical' to avoid confusion. The main problem is that migration is usually solution to free node for maintenance, so 'leftover' domain will die...

I thought about way to do that type of migration, and the  simplest way I found (without modifying toolstack or deep changing in guest domain) is just use a /32 networks (IPv4). In that case all packets will be routed via gateway (outside designated network). During migration route will be just replaced with new route table in guest domain and router(s).

If you do that, all traffic (except few dropped packets, which is not problem for TCP) will be routed to new designation and accepted by guest.
--------------010902010808080006090509-- --===============8991968558984473407== 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 --===============8991968558984473407==-- From xen-api-bounces@lists.xen.org Wed Mar 21 03:36:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 21 Mar 2012 03:36:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SACLt-0003gH-0F; Wed, 21 Mar 2012 03:36:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SACLq-0003gC-QI for xen-api@lists.xensource.com; Wed, 21 Mar 2012 03:36:43 +0000 Received: from [85.158.138.51:62882] by server-4.bemta-3.messagelabs.com id 3C/8F-16467-9CC496F4; Wed, 21 Mar 2012 03:36:41 +0000 X-Env-Sender: todd.deshane.xen@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1332300999!18420345!1 X-Originating-IP: [209.85.213.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14981 invoked from network); 21 Mar 2012 03:36:41 -0000 Received: from mail-yw0-f43.google.com (HELO mail-yw0-f43.google.com) (209.85.213.43) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 03:36:41 -0000 Received: by yhkk6 with SMTP id k6so799059yhk.30 for ; Tue, 20 Mar 2012 20:36:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=cxxQXXajyQlPZs+phkYAjzzapzA3DiYW/F4jc5pBogs=; b=QruKkcIvJkSXVHUMy63ljqgfl8EWyPFWKzmjVV27CcJTrstrsuA7/+is3D0yZhA87f sh7neHDrznjZP176izDqUrap6O2n5AkJvbWlGdLbwDvdHxvbVBu/vku5JSx6DsKTClpn zXVLHzPKXVJKRVhDWuS1mL8FV5ohe82r7XZ94n4W92AcmGAk15Ve+wFyuSHUgUUxbIXH sqXvq75gso389rQ9hZ4avhDe6yKrHQxfPdd+AlD9jcaCNYK0yEBDp5rqkyRbLJntrdu2 JplCcN7UInx9AFGg/XDZo54a16X9zu6Ktj26EDOwHgAlbR6JCdV/jfmb8QbfzWKpZZLS iDJA== Received: by 10.101.176.22 with SMTP id d22mr752191anp.15.1332300999413; Tue, 20 Mar 2012 20:36:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.60.196 with HTTP; Tue, 20 Mar 2012 20:36:19 -0700 (PDT) In-Reply-To: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> From: Todd Deshane Date: Tue, 20 Mar 2012 23:36:19 -0400 X-Google-Sender-Auth: q7eGX0kMGqgbAOs-ZvfHd2uivmw Message-ID: To: Salvatore Orlando Cc: "openstack@lists.launchpad.net" , xen-api , John Garbutt , Thomas Goirand , PKG OpenStack Subject: Re: [Xen-API] [Openstack] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Tue, Mar 20, 2012 at 8:51 PM, Salvatore Orlando wrote: >updated by nova-network, thus ensuring VMs get the IP address specified by the Looks like the end of this thought got cut off. Was there more? _______________________________________________ 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 21 03:36:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 21 Mar 2012 03:36:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SACLt-0003gH-0F; Wed, 21 Mar 2012 03:36:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SACLq-0003gC-QI for xen-api@lists.xensource.com; Wed, 21 Mar 2012 03:36:43 +0000 Received: from [85.158.138.51:62882] by server-4.bemta-3.messagelabs.com id 3C/8F-16467-9CC496F4; Wed, 21 Mar 2012 03:36:41 +0000 X-Env-Sender: todd.deshane.xen@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1332300999!18420345!1 X-Originating-IP: [209.85.213.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14981 invoked from network); 21 Mar 2012 03:36:41 -0000 Received: from mail-yw0-f43.google.com (HELO mail-yw0-f43.google.com) (209.85.213.43) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 03:36:41 -0000 Received: by yhkk6 with SMTP id k6so799059yhk.30 for ; Tue, 20 Mar 2012 20:36:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=cxxQXXajyQlPZs+phkYAjzzapzA3DiYW/F4jc5pBogs=; b=QruKkcIvJkSXVHUMy63ljqgfl8EWyPFWKzmjVV27CcJTrstrsuA7/+is3D0yZhA87f sh7neHDrznjZP176izDqUrap6O2n5AkJvbWlGdLbwDvdHxvbVBu/vku5JSx6DsKTClpn zXVLHzPKXVJKRVhDWuS1mL8FV5ohe82r7XZ94n4W92AcmGAk15Ve+wFyuSHUgUUxbIXH sqXvq75gso389rQ9hZ4avhDe6yKrHQxfPdd+AlD9jcaCNYK0yEBDp5rqkyRbLJntrdu2 JplCcN7UInx9AFGg/XDZo54a16X9zu6Ktj26EDOwHgAlbR6JCdV/jfmb8QbfzWKpZZLS iDJA== Received: by 10.101.176.22 with SMTP id d22mr752191anp.15.1332300999413; Tue, 20 Mar 2012 20:36:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.236.60.196 with HTTP; Tue, 20 Mar 2012 20:36:19 -0700 (PDT) In-Reply-To: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> From: Todd Deshane Date: Tue, 20 Mar 2012 23:36:19 -0400 X-Google-Sender-Auth: q7eGX0kMGqgbAOs-ZvfHd2uivmw Message-ID: To: Salvatore Orlando Cc: "openstack@lists.launchpad.net" , xen-api , John Garbutt , Thomas Goirand , PKG OpenStack Subject: Re: [Xen-API] [Openstack] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Tue, Mar 20, 2012 at 8:51 PM, Salvatore Orlando wrote: >updated by nova-network, thus ensuring VMs get the IP address specified by the Looks like the end of this thought got cut off. Was there more? _______________________________________________ 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 21 04:42:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 21 Mar 2012 04:42:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SADNk-0006CQ-0z; Wed, 21 Mar 2012 04:42:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SADNi-0006CG-MU for xen-api@lists.xensource.com; Wed, 21 Mar 2012 04:42:43 +0000 Received: from [85.158.139.83:45471] by server-2.bemta-5.messagelabs.com id E0/8D-17016-14C596F4; Wed, 21 Mar 2012 04:42:41 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-2.tower-182.messagelabs.com!1332304959!20276435!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4830 invoked from network); 21 Mar 2012 04:42:40 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-2.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Mar 2012 04:42:40 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 485B8FE48F; Wed, 21 Mar 2012 04:44:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=QDHqzkkuO U68m3/bd23fgiKWHqA=; b=g4g4ejJafnRD49z6Y0bZFrXfxjZHzYCxfupp3mpyu pp2P8yEbEuJ43LgtA63yoaps2QQctaEBihTWG1uvivIXCqMnq2bx+7JKUv9SgFz6 1z1ZJt/xD2Q0Q1BmT4/vThHkoqAtKsQv5bUyS/hoZJGI20EAbyKOimFpbkpEnWSo r4= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=JD0 BkTuxpgjn0SmsoHhBCh1gc56lIXspbYXew8dUcYNO3PmFyvuGiiDnlQYA90dCcFM WjOpfWqRn4chuOdw/Mtf+b7TnlJCrnOhxhQsZ3hgX8SV116FkbTJz4MyTMuP3T8/ iJ9yQeBHBUv52ATmvywMau+JiJDBSfy/4SN4cUxk= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id AE05BFE48D; Wed, 21 Mar 2012 04:44:20 +0000 (UTC) Message-ID: <4F695C39.8090901@goirand.fr> Date: Wed, 21 Mar 2012 12:42:33 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: Ewan Mellor References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> <6005BE083BF501439A84DC3523BAC82DC4BC0BB8F1@LONPMAILBOX01.citrite.net> In-Reply-To: <6005BE083BF501439A84DC3523BAC82DC4BC0BB8F1@LONPMAILBOX01.citrite.net> X-Enigmail-Version: 1.0.1 Cc: "openstack@lists.launchpad.net" , xen-api , Salvatore Orlando , PKG OpenStack , John Garbutt Subject: Re: [Xen-API] [Openstack-devel] [Openstack] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Ewan, Thanks for your answer. On 03/21/2012 07:05 AM, Ewan Mellor wrote: >> -----Original Message----- >> >>> Also, have you tried using DevStack first? It is a good way to get >> the hang of how the flags work. >> >> No it's not! DevStack is for testing with XenServer, and assumes that >> you'd be working with Ubuntu. Here, I'm testing the Debian packages >> that >> we are working on in Debian. Please don't direct me to DevStack, this >> wont help. > > DevStack _will_ help, and that's why we keep telling you to go look > there, and I have no idea why you keep refusing. You are writing the above as if I was being difficult, and refusing to do my homework. That isn't the case. I have read the scripts, and I did understand most of it, but some parts are really not easy to understand without the necessary background knowledge. Namely, the network setup, which is what I am having issue with currently. I'm trying to get the VLAN manager to work, and that mode isn't what Devstack is setting-up: it's setting-up a FlatDHCP. I may try to do a FlatDHCP to check if it works as expected, but that's not really satisfying in production for a public cloud. > You don't have to > run it, but it's up-to-date, and it's working, so it's a nice, clean, > self-documenting example of at least one way that someone has managed > to make this work. I really *don't agree* with the above. It's not self-documenting, it's clearly a big hack (not clean at all) that works only in your specific case (eg: if using CentOS and XenServer 5.6 with Ubuntu Oneiric). As you said it's "one way" to do things only, and it's all but helping to write a user documentation or a successful package. > If you have differences between your system and DevStack because of > the differences between Debian and Ubuntu or XenServer and XCP, then > fine. If you have differences that you don't understand, then you're > probably doing it wrong. That's why we tell you, on a weekly basis, > to go look at DevStack if you want to see how a flag should be set. I don't think that the issue is with flags. > You can either do this the easy way, by following other people's > working systems, or you can do it the hard way, by deep-diving > into every single detail. I'm fine if you want to do it the hard > way -- you'll certainly learn a lot, and it's probably very > interesting and useful knowledge for the future. Just don't keep > complaining that it's all too hard and then refuse to take the > easy option. > > Ewan. I don't "keep complaining that it's too hard", I complain that there's little to zero documentation of what is being done, and that one has to double-guess what is going on in Devstack. You seem to believe that Devstack is enough to replace a real documentation. If that is the case, then you are doing a big mistake here. Remember that I'm a Debian Developer, and that I've been running a hosting business since 2003. I consider myself as an advance user, which understands what a vlan is, how bridge is working, and that with all this, it should be enough knowledge to understand what's going on in a normal product. It's simply not the case with XCP + Openstack which is lacking documentation. Have you, by the way, noticed that there's even a bug that has been filled in Launchpad, about the lack of docs concerning bridging, OVS and networking? In a shorter way: if I'm telling you that Devstack isn't enough to understand what's going on, please trust me! Lucky, John Garbutt, Dave Scott and Salvatore Orlando have understand all this, and are trying to help me. As Salvatore just wrote, I am convince that I'm very close to have the setup working. Salvatore Orlando has written back to me with some very valuable information which I need to take time to understand now. I'll read it carefully today, as I'm sure it will help. Thomas P.S: It well may be that there's a bug in Kronos, because when I do "xe vlan-create", on the screen it's printed "script failing" or something. I'll test it one more time in order to get the exact error message, and probably will work with Mike on debugging this issue, which may be related to the upgrade to the latest version of Open vSwitch (which is 1.4.0 in Debian). _______________________________________________ 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 21 04:42:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 21 Mar 2012 04:42:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SADNk-0006CQ-0z; Wed, 21 Mar 2012 04:42:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SADNi-0006CG-MU for xen-api@lists.xensource.com; Wed, 21 Mar 2012 04:42:43 +0000 Received: from [85.158.139.83:45471] by server-2.bemta-5.messagelabs.com id E0/8D-17016-14C596F4; Wed, 21 Mar 2012 04:42:41 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-2.tower-182.messagelabs.com!1332304959!20276435!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4830 invoked from network); 21 Mar 2012 04:42:40 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-2.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Mar 2012 04:42:40 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id 485B8FE48F; Wed, 21 Mar 2012 04:44:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=postfix; bh=QDHqzkkuO U68m3/bd23fgiKWHqA=; b=g4g4ejJafnRD49z6Y0bZFrXfxjZHzYCxfupp3mpyu pp2P8yEbEuJ43LgtA63yoaps2QQctaEBihTWG1uvivIXCqMnq2bx+7JKUv9SgFz6 1z1ZJt/xD2Q0Q1BmT4/vThHkoqAtKsQv5bUyS/hoZJGI20EAbyKOimFpbkpEnWSo r4= DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=postfix; b=JD0 BkTuxpgjn0SmsoHhBCh1gc56lIXspbYXew8dUcYNO3PmFyvuGiiDnlQYA90dCcFM WjOpfWqRn4chuOdw/Mtf+b7TnlJCrnOhxhQsZ3hgX8SV116FkbTJz4MyTMuP3T8/ iJ9yQeBHBUv52ATmvywMau+JiJDBSfy/4SN4cUxk= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id AE05BFE48D; Wed, 21 Mar 2012 04:44:20 +0000 (UTC) Message-ID: <4F695C39.8090901@goirand.fr> Date: Wed, 21 Mar 2012 12:42:33 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Icedove/3.0.11 MIME-Version: 1.0 To: Ewan Mellor References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> <6005BE083BF501439A84DC3523BAC82DC4BC0BB8F1@LONPMAILBOX01.citrite.net> In-Reply-To: <6005BE083BF501439A84DC3523BAC82DC4BC0BB8F1@LONPMAILBOX01.citrite.net> X-Enigmail-Version: 1.0.1 Cc: "openstack@lists.launchpad.net" , xen-api , Salvatore Orlando , PKG OpenStack , John Garbutt Subject: Re: [Xen-API] [Openstack-devel] [Openstack] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Ewan, Thanks for your answer. On 03/21/2012 07:05 AM, Ewan Mellor wrote: >> -----Original Message----- >> >>> Also, have you tried using DevStack first? It is a good way to get >> the hang of how the flags work. >> >> No it's not! DevStack is for testing with XenServer, and assumes that >> you'd be working with Ubuntu. Here, I'm testing the Debian packages >> that >> we are working on in Debian. Please don't direct me to DevStack, this >> wont help. > > DevStack _will_ help, and that's why we keep telling you to go look > there, and I have no idea why you keep refusing. You are writing the above as if I was being difficult, and refusing to do my homework. That isn't the case. I have read the scripts, and I did understand most of it, but some parts are really not easy to understand without the necessary background knowledge. Namely, the network setup, which is what I am having issue with currently. I'm trying to get the VLAN manager to work, and that mode isn't what Devstack is setting-up: it's setting-up a FlatDHCP. I may try to do a FlatDHCP to check if it works as expected, but that's not really satisfying in production for a public cloud. > You don't have to > run it, but it's up-to-date, and it's working, so it's a nice, clean, > self-documenting example of at least one way that someone has managed > to make this work. I really *don't agree* with the above. It's not self-documenting, it's clearly a big hack (not clean at all) that works only in your specific case (eg: if using CentOS and XenServer 5.6 with Ubuntu Oneiric). As you said it's "one way" to do things only, and it's all but helping to write a user documentation or a successful package. > If you have differences between your system and DevStack because of > the differences between Debian and Ubuntu or XenServer and XCP, then > fine. If you have differences that you don't understand, then you're > probably doing it wrong. That's why we tell you, on a weekly basis, > to go look at DevStack if you want to see how a flag should be set. I don't think that the issue is with flags. > You can either do this the easy way, by following other people's > working systems, or you can do it the hard way, by deep-diving > into every single detail. I'm fine if you want to do it the hard > way -- you'll certainly learn a lot, and it's probably very > interesting and useful knowledge for the future. Just don't keep > complaining that it's all too hard and then refuse to take the > easy option. > > Ewan. I don't "keep complaining that it's too hard", I complain that there's little to zero documentation of what is being done, and that one has to double-guess what is going on in Devstack. You seem to believe that Devstack is enough to replace a real documentation. If that is the case, then you are doing a big mistake here. Remember that I'm a Debian Developer, and that I've been running a hosting business since 2003. I consider myself as an advance user, which understands what a vlan is, how bridge is working, and that with all this, it should be enough knowledge to understand what's going on in a normal product. It's simply not the case with XCP + Openstack which is lacking documentation. Have you, by the way, noticed that there's even a bug that has been filled in Launchpad, about the lack of docs concerning bridging, OVS and networking? In a shorter way: if I'm telling you that Devstack isn't enough to understand what's going on, please trust me! Lucky, John Garbutt, Dave Scott and Salvatore Orlando have understand all this, and are trying to help me. As Salvatore just wrote, I am convince that I'm very close to have the setup working. Salvatore Orlando has written back to me with some very valuable information which I need to take time to understand now. I'll read it carefully today, as I'm sure it will help. Thomas P.S: It well may be that there's a bug in Kronos, because when I do "xe vlan-create", on the screen it's printed "script failing" or something. I'll test it one more time in order to get the exact error message, and probably will work with Mike on debugging this issue, which may be related to the upgrade to the latest version of Open vSwitch (which is 1.4.0 in Debian). _______________________________________________ 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 21 19:00:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 21 Mar 2012 19:00:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAQlO-0002NV-P0; Wed, 21 Mar 2012 19:00:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAQlM-0002LZ-Jh for xen-api@lists.xensource.com; Wed, 21 Mar 2012 19:00:00 +0000 Received: from [85.158.143.99:60701] by server-2.bemta-4.messagelabs.com id 6D/AE-17550-F252A6F4; Wed, 21 Mar 2012 18:59:59 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1332356398!20257463!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDU2MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25516 invoked from network); 21 Mar 2012 18:59:59 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 18:59:59 -0000 X-IronPort-AV: E=Sophos;i="4.73,625,1325462400"; d="scan'208";a="11454749" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Mar 2012 18:59:58 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Wed, 21 Mar 2012 18:59:58 +0000 From: John Garbutt To: Salvatore Orlando , 'Thomas Goirand' Date: Wed, 21 Mar 2012 18:59:57 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0F9UNWekWgfyUaSyS4ijd0Z7gHfQAAlEHgAEAutDAAJlcswA== Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: xen-api , PKG OpenStack , "openstack@lists.launchpad.net" Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 I have tried to throw together some pictures that help describe the guest networking modes with XenServer: http://wiki.openstack.org/XenServer/NetworkingFlags The idea is to complement the existing diagrams currently in the manuals. It would be great if someone can review these diagrams for me. I can then maybe look at polishing them, and getting them into the manuals. Thanks, John > -----Original Message----- > From: Salvatore Orlando > Sent: 21 March 2012 00:51 > To: John Garbutt; 'Thomas Goirand' > Cc: PKG OpenStack; Dave Scott; openstack@lists.launchpad.net; xen-api > Subject: RE: [Xen-API] nova-xcp-network plugin searching for a xapi0 > interface > > Hi Thomas, > > I can probably help you somehow with Openstack networking on XenServer, > as I did some work on it in the past. > I see you are trying to use the VLAN manager, but the behaviour is not the > expected one. > However, since you can spin up instances, and they appear to be attached to > the appropriate bridge, I'd dare to say you're very close! > > In a nutshell, when using the VLAN manager on XenServer: > 1) A PIF identified either by (A) the vlan_interface flag or (B) the > bridge_interface column in the networks db table will be used for creating a > XenServer VLAN network. > The VLAN tag is found in the vlan column, still in the networks table, and > by default the first tag is 100, if my memory does not fail me. > 2) VIF for VM instances within this network will be plugged in this VLAN > network. As you said, you won't see the bridge until a VIF is plugged in it. This > behaviour is the same in XS, XCP, and Kronos. > 3) The 'Openstack domU', i.e. the VM running the nova network node, > instead will not be plugged into this network; since it acts as a gateway for > multiple VLAN networks, it has to be attached on a VLAN trunk. For this > reason it must have an interface on the parent bridge of the VLAN bridge > where VM instances are plugged. I realized this is quite obscure, so to cut a > long story short, if vlan_interface is eth0 it must be plugged in xenbr0, eth1 --> > xenbr1, and so on (on Kronos you might also end up with brwlan0). > 4) Within the Openstack domU, 'ip link' is then used to configure VLAN > interfaces on the 'trunk' port. Each of this vlan interfaces is associated with a > dnsmasq instance, which will distribute IP addresses to instances. The lease > file for dnsmasq is constantly updated by nova-network, thus ensuring VMs > get the IP address specified by the > > With this configuration, VM instances should be able to get the IP address > assigned to them from the appropriate dnsmasq instance, and should be > able to communicate without any problem with other VMs on the same > network and with the their gateway. > The above point (3) probably needs some more explanations. With Open > vSwitch, we don't really have distinct bridges for different VLANs; even if > they appear as distinct bridges to linux and xen server, they are actually the > same OVS instance, which runs a distinct 'fake-bridge' for each VLAN. The > 'real' bridge is the 'parent' of the fake one. You can easily navigate fake and > real bridges with ovs-vsctl. > As you can see I am referring to Openvswitch only. This is for a specific > reason: the fake-parent mechanism automatically imply that ports which are > not on a fake bridge are trunk ports. This does not happen with linux bridge. > A packet forwarded on a VLAN interfaces does not get back in the xenbrX > bridge for ethX. > > So, coming back to your problem I would check that: > 1) The XenServer network whose bridge is xapi0 is configured correctly > (check PIF, VLAN tag) > 2) The Openstack domU is connected to the appropriate bridge according to > the value of vlan_interface (which seems wrong in your conf file) > 3) Open vSwitch is enabled > 4) Check the networks table in your database > > I hope I have been exhaustive enough to not become pedant... At this point > you might wonder why this has not been documented anywhere. > Well, my answer is that it was documented, I am very sure it was. However I > cannot find the wiki page anymore. I have the sources on my laptop, and I > will make sure that VLAN networking and possibly all the other network > managers on xenapi backend are documented; including Quantum. > > Regards, > Salvatore > > > > -----Original Message----- > > From: openstack- > > bounces+salvatore.orlando=eu.citrix.com@lists.launchpad.net > > [mailto:openstack- > > bounces+salvatore.orlando=eu.citrix.com@lists.launchpad.net] On Behalf > > bounces+Of > > John Garbutt > > Sent: 19 March 2012 18:01 > > To: 'Thomas Goirand' > > Cc: PKG OpenStack; Dave Scott; openstack@lists.launchpad.net; xen-api > > Subject: Re: [Openstack] [Xen-API] nova-xcp-network plugin searching > > for a > > xapi0 interface > > > > Hi, > > > > Looks like the network configuration is not quite right. > > > > Have a look at this, for an example of how things could look > > networking wise (when using DevStack and XenServer with two nics): > > http://wiki.openstack.org/XenServer/XenXCPAndXenServer > > > > The manuals have a good description, although it is a little KVM specific: > > http://docs.openstack.org/trunk/openstack- > > compute/admin/content/configuring-flat-dhcp-networking.html > > > > I suggested using DevStack because it is the best "documentation" for > > a working set of flags right now (yes, not ideal, we must fix that > > asap!). Take a > > look: > > https://github.com/openstack-dev/devstack/blob/master/stack.sh#L291 > > Note the defaults in the nova code might work for KVM, but will not > > work for XenServer, so you will need to set those flags with more > appropriate values. > > > > Hope that helps, > > John > > > > -----Original Message----- > > From: Thomas Goirand [mailto:thomas@goirand.fr] > > Sent: 19 March 2012 5:25 > > To: John Garbutt > > Cc: Dave Scott; xen-api; PKG OpenStack; openstack@lists.launchpad.net > > Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 > > interface > > > > On 03/20/2012 12:05 AM, John Garbutt wrote: > > > This sounds a lot like a configuration issue with your guest network bridge. > > Are you OK to supply your nova.conf file? > > > > Sure! Here it is: > > > > --sql_connection=mysql://nova:admin@127.0.0.1/nova > > --novncproxy_base_url=http://:6080/vnc_auto.html > > --rabbit_host= > > --glance_api_servers=:9292 > > --network_manager=nova.network.manager.VlanManager > > --vlan_interface=br100 > > --dhcpbridge=/usr/bin/nova-dhcpbridge > > --firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver > > --connection_type=xenapi > > --xenapi_connection_url=https:// > > --xenapi_connection_username=root > > --xenapi_connection_password=XXXXXXX > > --reboot_timeout=600 > > --rescue_timeout=86400 > > --resize_confirm_window=86400 > > --auth_strategy=keystone > > --allow_admin_api > > --allow_resize_to_same_host > > --logdir=/var/log/nova > > --state_path=/var/lib/nova > > --lock_path=/var/lock/nova > > --vncserver_listen=0.0.0.0 > > --force_dhcp_release > > --use_deprecated_auth > > --use_project_ca > > --verbose > > > > Note that since I restarted xcp-xapi, it seems that the xapi0 bridge > > is created each time I create a VM, which is what I was expecting. So > > that parts seems to work now, but the issue is that now, I have no > > networking at all (eg: I can't reach the instance from the Openstack domU). > > > > Here's what "xe network-list" returns on my dom0: > > > > uuid ( RO) : > > name-label ( RW): br100 > > name-description ( RW): network for nova bridge br100 > > bridge ( RO): xapi0 > > > > So it really is nova who created this. But shouldn't it be linked to > > my > > xenbr0 as well? What is the normal networking setup that should be done? > > > > There's absolutely zero documentation which I could find about this. > > Of course, I'll write one directly in our Debian packages as soon as this > works. > > > > > Also, have you tried using DevStack first? It is a good way to get > > > the hang of > > how the flags work. > > > > No it's not! DevStack is for testing with XenServer, and assumes that > > you'd be working with Ubuntu. Here, I'm testing the Debian packages > > that we are working on in Debian. Please don't direct me to DevStack, this > wont help. > > > > > I'm not familiar with the design of the Nova plugins but my guess is > > > that > > they're trying to use the "Host internal management network" -- a > > network from which VMs can access the XenAPI (i.e. talk to xapi in domain > 0). > > > > > > On recent XCP versions the default bridge name changed to "xenapi" > > > to > > make it easier to distinguish from a firewall rules PoV. > > > > As per Mike on IRC, (from Citrix, upstream for XCP, XenServer and > > Kronos), each time there's a new network being created, XCP create a > > xapiX bridge automatically. I shouldn't have even try to bring the > > xapi0 bridge myself, XCP does it (if it doesn't, then there's an issue). > > > > > Note that the actual linux bridge (or openvswitch) is created on > > > demand so > > you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. > > > > > > Try changing "xapi0" to "xenapi" in the plugins and see if they work better? > > > > Nop, that wont help, xapi0 is really what to expect. My only issue now > > is to have it connected to the br100 of Openstack in my domU. > > > > Thanks for the help already, > > Cheers, > > > > Thomas > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp _______________________________________________ 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 21 19:00:10 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 21 Mar 2012 19:00:10 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAQlO-0002NV-P0; Wed, 21 Mar 2012 19:00:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAQlM-0002LZ-Jh for xen-api@lists.xensource.com; Wed, 21 Mar 2012 19:00:00 +0000 Received: from [85.158.143.99:60701] by server-2.bemta-4.messagelabs.com id 6D/AE-17550-F252A6F4; Wed, 21 Mar 2012 18:59:59 +0000 X-Env-Sender: John.Garbutt@citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1332356398!20257463!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDU2MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25516 invoked from network); 21 Mar 2012 18:59:59 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 18:59:59 -0000 X-IronPort-AV: E=Sophos;i="4.73,625,1325462400"; d="scan'208";a="11454749" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Mar 2012 18:59:58 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Wed, 21 Mar 2012 18:59:58 +0000 From: John Garbutt To: Salvatore Orlando , 'Thomas Goirand' Date: Wed, 21 Mar 2012 18:59:57 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0F9UNWekWgfyUaSyS4ijd0Z7gHfQAAlEHgAEAutDAAJlcswA== Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: xen-api , PKG OpenStack , "openstack@lists.launchpad.net" Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 I have tried to throw together some pictures that help describe the guest networking modes with XenServer: http://wiki.openstack.org/XenServer/NetworkingFlags The idea is to complement the existing diagrams currently in the manuals. It would be great if someone can review these diagrams for me. I can then maybe look at polishing them, and getting them into the manuals. Thanks, John > -----Original Message----- > From: Salvatore Orlando > Sent: 21 March 2012 00:51 > To: John Garbutt; 'Thomas Goirand' > Cc: PKG OpenStack; Dave Scott; openstack@lists.launchpad.net; xen-api > Subject: RE: [Xen-API] nova-xcp-network plugin searching for a xapi0 > interface > > Hi Thomas, > > I can probably help you somehow with Openstack networking on XenServer, > as I did some work on it in the past. > I see you are trying to use the VLAN manager, but the behaviour is not the > expected one. > However, since you can spin up instances, and they appear to be attached to > the appropriate bridge, I'd dare to say you're very close! > > In a nutshell, when using the VLAN manager on XenServer: > 1) A PIF identified either by (A) the vlan_interface flag or (B) the > bridge_interface column in the networks db table will be used for creating a > XenServer VLAN network. > The VLAN tag is found in the vlan column, still in the networks table, and > by default the first tag is 100, if my memory does not fail me. > 2) VIF for VM instances within this network will be plugged in this VLAN > network. As you said, you won't see the bridge until a VIF is plugged in it. This > behaviour is the same in XS, XCP, and Kronos. > 3) The 'Openstack domU', i.e. the VM running the nova network node, > instead will not be plugged into this network; since it acts as a gateway for > multiple VLAN networks, it has to be attached on a VLAN trunk. For this > reason it must have an interface on the parent bridge of the VLAN bridge > where VM instances are plugged. I realized this is quite obscure, so to cut a > long story short, if vlan_interface is eth0 it must be plugged in xenbr0, eth1 --> > xenbr1, and so on (on Kronos you might also end up with brwlan0). > 4) Within the Openstack domU, 'ip link' is then used to configure VLAN > interfaces on the 'trunk' port. Each of this vlan interfaces is associated with a > dnsmasq instance, which will distribute IP addresses to instances. The lease > file for dnsmasq is constantly updated by nova-network, thus ensuring VMs > get the IP address specified by the > > With this configuration, VM instances should be able to get the IP address > assigned to them from the appropriate dnsmasq instance, and should be > able to communicate without any problem with other VMs on the same > network and with the their gateway. > The above point (3) probably needs some more explanations. With Open > vSwitch, we don't really have distinct bridges for different VLANs; even if > they appear as distinct bridges to linux and xen server, they are actually the > same OVS instance, which runs a distinct 'fake-bridge' for each VLAN. The > 'real' bridge is the 'parent' of the fake one. You can easily navigate fake and > real bridges with ovs-vsctl. > As you can see I am referring to Openvswitch only. This is for a specific > reason: the fake-parent mechanism automatically imply that ports which are > not on a fake bridge are trunk ports. This does not happen with linux bridge. > A packet forwarded on a VLAN interfaces does not get back in the xenbrX > bridge for ethX. > > So, coming back to your problem I would check that: > 1) The XenServer network whose bridge is xapi0 is configured correctly > (check PIF, VLAN tag) > 2) The Openstack domU is connected to the appropriate bridge according to > the value of vlan_interface (which seems wrong in your conf file) > 3) Open vSwitch is enabled > 4) Check the networks table in your database > > I hope I have been exhaustive enough to not become pedant... At this point > you might wonder why this has not been documented anywhere. > Well, my answer is that it was documented, I am very sure it was. However I > cannot find the wiki page anymore. I have the sources on my laptop, and I > will make sure that VLAN networking and possibly all the other network > managers on xenapi backend are documented; including Quantum. > > Regards, > Salvatore > > > > -----Original Message----- > > From: openstack- > > bounces+salvatore.orlando=eu.citrix.com@lists.launchpad.net > > [mailto:openstack- > > bounces+salvatore.orlando=eu.citrix.com@lists.launchpad.net] On Behalf > > bounces+Of > > John Garbutt > > Sent: 19 March 2012 18:01 > > To: 'Thomas Goirand' > > Cc: PKG OpenStack; Dave Scott; openstack@lists.launchpad.net; xen-api > > Subject: Re: [Openstack] [Xen-API] nova-xcp-network plugin searching > > for a > > xapi0 interface > > > > Hi, > > > > Looks like the network configuration is not quite right. > > > > Have a look at this, for an example of how things could look > > networking wise (when using DevStack and XenServer with two nics): > > http://wiki.openstack.org/XenServer/XenXCPAndXenServer > > > > The manuals have a good description, although it is a little KVM specific: > > http://docs.openstack.org/trunk/openstack- > > compute/admin/content/configuring-flat-dhcp-networking.html > > > > I suggested using DevStack because it is the best "documentation" for > > a working set of flags right now (yes, not ideal, we must fix that > > asap!). Take a > > look: > > https://github.com/openstack-dev/devstack/blob/master/stack.sh#L291 > > Note the defaults in the nova code might work for KVM, but will not > > work for XenServer, so you will need to set those flags with more > appropriate values. > > > > Hope that helps, > > John > > > > -----Original Message----- > > From: Thomas Goirand [mailto:thomas@goirand.fr] > > Sent: 19 March 2012 5:25 > > To: John Garbutt > > Cc: Dave Scott; xen-api; PKG OpenStack; openstack@lists.launchpad.net > > Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 > > interface > > > > On 03/20/2012 12:05 AM, John Garbutt wrote: > > > This sounds a lot like a configuration issue with your guest network bridge. > > Are you OK to supply your nova.conf file? > > > > Sure! Here it is: > > > > --sql_connection=mysql://nova:admin@127.0.0.1/nova > > --novncproxy_base_url=http://:6080/vnc_auto.html > > --rabbit_host= > > --glance_api_servers=:9292 > > --network_manager=nova.network.manager.VlanManager > > --vlan_interface=br100 > > --dhcpbridge=/usr/bin/nova-dhcpbridge > > --firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver > > --connection_type=xenapi > > --xenapi_connection_url=https:// > > --xenapi_connection_username=root > > --xenapi_connection_password=XXXXXXX > > --reboot_timeout=600 > > --rescue_timeout=86400 > > --resize_confirm_window=86400 > > --auth_strategy=keystone > > --allow_admin_api > > --allow_resize_to_same_host > > --logdir=/var/log/nova > > --state_path=/var/lib/nova > > --lock_path=/var/lock/nova > > --vncserver_listen=0.0.0.0 > > --force_dhcp_release > > --use_deprecated_auth > > --use_project_ca > > --verbose > > > > Note that since I restarted xcp-xapi, it seems that the xapi0 bridge > > is created each time I create a VM, which is what I was expecting. So > > that parts seems to work now, but the issue is that now, I have no > > networking at all (eg: I can't reach the instance from the Openstack domU). > > > > Here's what "xe network-list" returns on my dom0: > > > > uuid ( RO) : > > name-label ( RW): br100 > > name-description ( RW): network for nova bridge br100 > > bridge ( RO): xapi0 > > > > So it really is nova who created this. But shouldn't it be linked to > > my > > xenbr0 as well? What is the normal networking setup that should be done? > > > > There's absolutely zero documentation which I could find about this. > > Of course, I'll write one directly in our Debian packages as soon as this > works. > > > > > Also, have you tried using DevStack first? It is a good way to get > > > the hang of > > how the flags work. > > > > No it's not! DevStack is for testing with XenServer, and assumes that > > you'd be working with Ubuntu. Here, I'm testing the Debian packages > > that we are working on in Debian. Please don't direct me to DevStack, this > wont help. > > > > > I'm not familiar with the design of the Nova plugins but my guess is > > > that > > they're trying to use the "Host internal management network" -- a > > network from which VMs can access the XenAPI (i.e. talk to xapi in domain > 0). > > > > > > On recent XCP versions the default bridge name changed to "xenapi" > > > to > > make it easier to distinguish from a firewall rules PoV. > > > > As per Mike on IRC, (from Citrix, upstream for XCP, XenServer and > > Kronos), each time there's a new network being created, XCP create a > > xapiX bridge automatically. I shouldn't have even try to bring the > > xapi0 bridge myself, XCP does it (if it doesn't, then there's an issue). > > > > > Note that the actual linux bridge (or openvswitch) is created on > > > demand so > > you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. > > > > > > Try changing "xapi0" to "xenapi" in the plugins and see if they work better? > > > > Nop, that wont help, xapi0 is really what to expect. My only issue now > > is to have it connected to the br100 of Openstack in my domU. > > > > Thanks for the help already, > > Cheers, > > > > Thomas > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~openstack > > More help : https://help.launchpad.net/ListHelp _______________________________________________ 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 22 13:13:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 22 Mar 2012 13:13:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAhpZ-0002d8-Fi; Thu, 22 Mar 2012 13:13:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAHXo-0002rt-RO for xen-api@lists.xensource.com; Wed, 21 Mar 2012 09:09:25 +0000 Received: from [85.158.143.99:59365] by server-2.bemta-4.messagelabs.com id 69/7C-17550-4CA996F4; Wed, 21 Mar 2012 09:09:24 +0000 X-Env-Sender: Salvatore.Orlando@eu.citrix.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1332320962!19591991!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDU2MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26019 invoked from network); 21 Mar 2012 09:09:22 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 09:09:22 -0000 X-IronPort-AV: E=Sophos;i="4.73,623,1325462400"; d="scan'208";a="11431681" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Mar 2012 09:09:22 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Wed, 21 Mar 2012 09:09:22 +0000 From: Salvatore Orlando To: Todd Deshane Date: Wed, 21 Mar 2012 09:09:21 +0000 Thread-Topic: [Openstack] [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0HE9TE8m00CCfqTaS/MZ7eIYIeNwALj12A Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 22 Mar 2012 13:13:27 +0000 Cc: "openstack@lists.launchpad.net" , xen-api , John Garbutt , Thomas Goirand , PKG OpenStack Subject: Re: [Xen-API] [Openstack] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 "The lease file for dnsmasq is constantly updated by nova-network, thus ensuring VMs get the IP address specified by the layer3 network driver (nova IPAM or Melange)." Sorry about that :) > -----Original Message----- > From: todd.deshane.xen@gmail.com [mailto:todd.deshane.xen@gmail.com] > On Behalf Of Todd Deshane > Sent: 21 March 2012 03:36 > To: Salvatore Orlando > Cc: John Garbutt; Thomas Goirand; xen-api; PKG OpenStack; Dave Scott; > openstack@lists.launchpad.net > Subject: Re: [Openstack] [Xen-API] nova-xcp-network plugin searching for a > xapi0 interface > > On Tue, Mar 20, 2012 at 8:51 PM, Salvatore Orlando > wrote: > > >updated by nova-network, thus ensuring VMs get the IP address specified > >by the > > Looks like the end of this thought got cut off. Was there more? _______________________________________________ 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 22 13:13:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 22 Mar 2012 13:13:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAhpZ-0002d8-Fi; Thu, 22 Mar 2012 13:13:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAHXo-0002rt-RO for xen-api@lists.xensource.com; Wed, 21 Mar 2012 09:09:25 +0000 Received: from [85.158.143.99:59365] by server-2.bemta-4.messagelabs.com id 69/7C-17550-4CA996F4; Wed, 21 Mar 2012 09:09:24 +0000 X-Env-Sender: Salvatore.Orlando@eu.citrix.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1332320962!19591991!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDU2MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26019 invoked from network); 21 Mar 2012 09:09:22 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 09:09:22 -0000 X-IronPort-AV: E=Sophos;i="4.73,623,1325462400"; d="scan'208";a="11431681" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Mar 2012 09:09:22 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Wed, 21 Mar 2012 09:09:22 +0000 From: Salvatore Orlando To: Todd Deshane Date: Wed, 21 Mar 2012 09:09:21 +0000 Thread-Topic: [Openstack] [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0HE9TE8m00CCfqTaS/MZ7eIYIeNwALj12A Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 22 Mar 2012 13:13:27 +0000 Cc: "openstack@lists.launchpad.net" , xen-api , John Garbutt , Thomas Goirand , PKG OpenStack Subject: Re: [Xen-API] [Openstack] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 "The lease file for dnsmasq is constantly updated by nova-network, thus ensuring VMs get the IP address specified by the layer3 network driver (nova IPAM or Melange)." Sorry about that :) > -----Original Message----- > From: todd.deshane.xen@gmail.com [mailto:todd.deshane.xen@gmail.com] > On Behalf Of Todd Deshane > Sent: 21 March 2012 03:36 > To: Salvatore Orlando > Cc: John Garbutt; Thomas Goirand; xen-api; PKG OpenStack; Dave Scott; > openstack@lists.launchpad.net > Subject: Re: [Openstack] [Xen-API] nova-xcp-network plugin searching for a > xapi0 interface > > On Tue, Mar 20, 2012 at 8:51 PM, Salvatore Orlando > wrote: > > >updated by nova-network, thus ensuring VMs get the IP address specified > >by the > > Looks like the end of this thought got cut off. Was there more? _______________________________________________ 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 22 13:13:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 22 Mar 2012 13:13:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAhpZ-0002cy-Ba; Thu, 22 Mar 2012 13:13:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA9lu-0007Bm-1q for xen-api@lists.xensource.com; Wed, 21 Mar 2012 00:51:26 +0000 Received: from [193.109.254.147:18549] by server-6.bemta-14.messagelabs.com id 2E/95-02047-D06296F4; Wed, 21 Mar 2012 00:51:25 +0000 X-Env-Sender: Salvatore.Orlando@eu.citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1332291084!1365630!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDUxMw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20190 invoked from network); 21 Mar 2012 00:51:24 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 00:51:24 -0000 X-IronPort-AV: E=Sophos;i="4.73,621,1325462400"; d="scan'208";a="11427830" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Mar 2012 00:51:24 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Wed, 21 Mar 2012 00:51:24 +0000 From: Salvatore Orlando To: John Garbutt , 'Thomas Goirand' Date: Wed, 21 Mar 2012 00:51:22 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0F9UNWekWgfyUaSyS4ijd0Z7gHfQAAlEHgAEAutDA= Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 22 Mar 2012 13:13:27 +0000 Cc: xen-api , PKG OpenStack , "openstack@lists.launchpad.net" Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Thomas, I can probably help you somehow with Openstack networking on XenServer, as I did some work on it in the past. I see you are trying to use the VLAN manager, but the behaviour is not the expected one. However, since you can spin up instances, and they appear to be attached to the appropriate bridge, I'd dare to say you're very close! In a nutshell, when using the VLAN manager on XenServer: 1) A PIF identified either by (A) the vlan_interface flag or (B) the bridge_interface column in the networks db table will be used for creating a XenServer VLAN network. The VLAN tag is found in the vlan column, still in the networks table, and by default the first tag is 100, if my memory does not fail me. 2) VIF for VM instances within this network will be plugged in this VLAN network. As you said, you won't see the bridge until a VIF is plugged in it. This behaviour is the same in XS, XCP, and Kronos. 3) The 'Openstack domU', i.e. the VM running the nova network node, instead will not be plugged into this network; since it acts as a gateway for multiple VLAN networks, it has to be attached on a VLAN trunk. For this reason it must have an interface on the parent bridge of the VLAN bridge where VM instances are plugged. I realized this is quite obscure, so to cut a long story short, if vlan_interface is eth0 it must be plugged in xenbr0, eth1 --> xenbr1, and so on (on Kronos you might also end up with brwlan0). 4) Within the Openstack domU, 'ip link' is then used to configure VLAN interfaces on the 'trunk' port. Each of this vlan interfaces is associated with a dnsmasq instance, which will distribute IP addresses to instances. The lease file for dnsmasq is constantly updated by nova-network, thus ensuring VMs get the IP address specified by the With this configuration, VM instances should be able to get the IP address assigned to them from the appropriate dnsmasq instance, and should be able to communicate without any problem with other VMs on the same network and with the their gateway. The above point (3) probably needs some more explanations. With Open vSwitch, we don't really have distinct bridges for different VLANs; even if they appear as distinct bridges to linux and xen server, they are actually the same OVS instance, which runs a distinct 'fake-bridge' for each VLAN. The 'real' bridge is the 'parent' of the fake one. You can easily navigate fake and real bridges with ovs-vsctl. As you can see I am referring to Openvswitch only. This is for a specific reason: the fake-parent mechanism automatically imply that ports which are not on a fake bridge are trunk ports. This does not happen with linux bridge. A packet forwarded on a VLAN interfaces does not get back in the xenbrX bridge for ethX. So, coming back to your problem I would check that: 1) The XenServer network whose bridge is xapi0 is configured correctly (check PIF, VLAN tag) 2) The Openstack domU is connected to the appropriate bridge according to the value of vlan_interface (which seems wrong in your conf file) 3) Open vSwitch is enabled 4) Check the networks table in your database I hope I have been exhaustive enough to not become pedant... At this point you might wonder why this has not been documented anywhere. Well, my answer is that it was documented, I am very sure it was. However I cannot find the wiki page anymore. I have the sources on my laptop, and I will make sure that VLAN networking and possibly all the other network managers on xenapi backend are documented; including Quantum. Regards, Salvatore > -----Original Message----- > From: openstack- > bounces+salvatore.orlando=eu.citrix.com@lists.launchpad.net > [mailto:openstack- > bounces+salvatore.orlando=eu.citrix.com@lists.launchpad.net] On Behalf Of > John Garbutt > Sent: 19 March 2012 18:01 > To: 'Thomas Goirand' > Cc: PKG OpenStack; Dave Scott; openstack@lists.launchpad.net; xen-api > Subject: Re: [Openstack] [Xen-API] nova-xcp-network plugin searching for a > xapi0 interface > > Hi, > > Looks like the network configuration is not quite right. > > Have a look at this, for an example of how things could look networking wise > (when using DevStack and XenServer with two nics): > http://wiki.openstack.org/XenServer/XenXCPAndXenServer > > The manuals have a good description, although it is a little KVM specific: > http://docs.openstack.org/trunk/openstack- > compute/admin/content/configuring-flat-dhcp-networking.html > > I suggested using DevStack because it is the best "documentation" for a > working set of flags right now (yes, not ideal, we must fix that asap!). Take a > look: > https://github.com/openstack-dev/devstack/blob/master/stack.sh#L291 > Note the defaults in the nova code might work for KVM, but will not work for > XenServer, so you will need to set those flags with more appropriate values. > > Hope that helps, > John > > -----Original Message----- > From: Thomas Goirand [mailto:thomas@goirand.fr] > Sent: 19 March 2012 5:25 > To: John Garbutt > Cc: Dave Scott; xen-api; PKG OpenStack; openstack@lists.launchpad.net > Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 > interface > > On 03/20/2012 12:05 AM, John Garbutt wrote: > > This sounds a lot like a configuration issue with your guest network bridge. > Are you OK to supply your nova.conf file? > > Sure! Here it is: > > --sql_connection=mysql://nova:admin@127.0.0.1/nova > --novncproxy_base_url=http://:6080/vnc_auto.html > --rabbit_host= > --glance_api_servers=:9292 > --network_manager=nova.network.manager.VlanManager > --vlan_interface=br100 > --dhcpbridge=/usr/bin/nova-dhcpbridge > --firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver > --connection_type=xenapi > --xenapi_connection_url=https:// > --xenapi_connection_username=root > --xenapi_connection_password=XXXXXXX > --reboot_timeout=600 > --rescue_timeout=86400 > --resize_confirm_window=86400 > --auth_strategy=keystone > --allow_admin_api > --allow_resize_to_same_host > --logdir=/var/log/nova > --state_path=/var/lib/nova > --lock_path=/var/lock/nova > --vncserver_listen=0.0.0.0 > --force_dhcp_release > --use_deprecated_auth > --use_project_ca > --verbose > > Note that since I restarted xcp-xapi, it seems that the xapi0 bridge is created > each time I create a VM, which is what I was expecting. So that parts seems > to work now, but the issue is that now, I have no networking at all (eg: I can't > reach the instance from the Openstack domU). > > Here's what "xe network-list" returns on my dom0: > > uuid ( RO) : > name-label ( RW): br100 > name-description ( RW): network for nova bridge br100 > bridge ( RO): xapi0 > > So it really is nova who created this. But shouldn't it be linked to my > xenbr0 as well? What is the normal networking setup that should be done? > > There's absolutely zero documentation which I could find about this. Of > course, I'll write one directly in our Debian packages as soon as this works. > > > Also, have you tried using DevStack first? It is a good way to get the hang of > how the flags work. > > No it's not! DevStack is for testing with XenServer, and assumes that you'd > be working with Ubuntu. Here, I'm testing the Debian packages that we are > working on in Debian. Please don't direct me to DevStack, this wont help. > > > I'm not familiar with the design of the Nova plugins but my guess is that > they're trying to use the "Host internal management network" -- a network > from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). > > > > On recent XCP versions the default bridge name changed to "xenapi" to > make it easier to distinguish from a firewall rules PoV. > > As per Mike on IRC, (from Citrix, upstream for XCP, XenServer and Kronos), > each time there's a new network being created, XCP create a xapiX bridge > automatically. I shouldn't have even try to bring the xapi0 bridge myself, XCP > does it (if it doesn't, then there's an issue). > > > Note that the actual linux bridge (or openvswitch) is created on demand so > you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. > > > > Try changing "xapi0" to "xenapi" in the plugins and see if they work better? > > Nop, that wont help, xapi0 is really what to expect. My only issue now is to > have it connected to the br100 of Openstack in my domU. > > Thanks for the help already, > Cheers, > > Thomas > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ 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 22 13:13:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 22 Mar 2012 13:13:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SAhpZ-0002cy-Ba; Thu, 22 Mar 2012 13:13:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SA9lu-0007Bm-1q for xen-api@lists.xensource.com; Wed, 21 Mar 2012 00:51:26 +0000 Received: from [193.109.254.147:18549] by server-6.bemta-14.messagelabs.com id 2E/95-02047-D06296F4; Wed, 21 Mar 2012 00:51:25 +0000 X-Env-Sender: Salvatore.Orlando@eu.citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1332291084!1365630!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MDUxMw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20190 invoked from network); 21 Mar 2012 00:51:24 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Mar 2012 00:51:24 -0000 X-IronPort-AV: E=Sophos;i="4.73,621,1325462400"; d="scan'208";a="11427830" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 21 Mar 2012 00:51:24 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Wed, 21 Mar 2012 00:51:24 +0000 From: Salvatore Orlando To: John Garbutt , 'Thomas Goirand' Date: Wed, 21 Mar 2012 00:51:22 +0000 Thread-Topic: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Thread-Index: Ac0F9UNWekWgfyUaSyS4ijd0Z7gHfQAAlEHgAEAutDA= Message-ID: References: <4F64B311.8060709@goirand.fr> <81A73678E76EA642801C8F2E4823AD21D7724CFA44@LONPMAILBOX01.citrite.net> <4F676BFC.702@goirand.fr> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 22 Mar 2012 13:13:27 +0000 Cc: xen-api , PKG OpenStack , "openstack@lists.launchpad.net" Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Thomas, I can probably help you somehow with Openstack networking on XenServer, as I did some work on it in the past. I see you are trying to use the VLAN manager, but the behaviour is not the expected one. However, since you can spin up instances, and they appear to be attached to the appropriate bridge, I'd dare to say you're very close! In a nutshell, when using the VLAN manager on XenServer: 1) A PIF identified either by (A) the vlan_interface flag or (B) the bridge_interface column in the networks db table will be used for creating a XenServer VLAN network. The VLAN tag is found in the vlan column, still in the networks table, and by default the first tag is 100, if my memory does not fail me. 2) VIF for VM instances within this network will be plugged in this VLAN network. As you said, you won't see the bridge until a VIF is plugged in it. This behaviour is the same in XS, XCP, and Kronos. 3) The 'Openstack domU', i.e. the VM running the nova network node, instead will not be plugged into this network; since it acts as a gateway for multiple VLAN networks, it has to be attached on a VLAN trunk. For this reason it must have an interface on the parent bridge of the VLAN bridge where VM instances are plugged. I realized this is quite obscure, so to cut a long story short, if vlan_interface is eth0 it must be plugged in xenbr0, eth1 --> xenbr1, and so on (on Kronos you might also end up with brwlan0). 4) Within the Openstack domU, 'ip link' is then used to configure VLAN interfaces on the 'trunk' port. Each of this vlan interfaces is associated with a dnsmasq instance, which will distribute IP addresses to instances. The lease file for dnsmasq is constantly updated by nova-network, thus ensuring VMs get the IP address specified by the With this configuration, VM instances should be able to get the IP address assigned to them from the appropriate dnsmasq instance, and should be able to communicate without any problem with other VMs on the same network and with the their gateway. The above point (3) probably needs some more explanations. With Open vSwitch, we don't really have distinct bridges for different VLANs; even if they appear as distinct bridges to linux and xen server, they are actually the same OVS instance, which runs a distinct 'fake-bridge' for each VLAN. The 'real' bridge is the 'parent' of the fake one. You can easily navigate fake and real bridges with ovs-vsctl. As you can see I am referring to Openvswitch only. This is for a specific reason: the fake-parent mechanism automatically imply that ports which are not on a fake bridge are trunk ports. This does not happen with linux bridge. A packet forwarded on a VLAN interfaces does not get back in the xenbrX bridge for ethX. So, coming back to your problem I would check that: 1) The XenServer network whose bridge is xapi0 is configured correctly (check PIF, VLAN tag) 2) The Openstack domU is connected to the appropriate bridge according to the value of vlan_interface (which seems wrong in your conf file) 3) Open vSwitch is enabled 4) Check the networks table in your database I hope I have been exhaustive enough to not become pedant... At this point you might wonder why this has not been documented anywhere. Well, my answer is that it was documented, I am very sure it was. However I cannot find the wiki page anymore. I have the sources on my laptop, and I will make sure that VLAN networking and possibly all the other network managers on xenapi backend are documented; including Quantum. Regards, Salvatore > -----Original Message----- > From: openstack- > bounces+salvatore.orlando=eu.citrix.com@lists.launchpad.net > [mailto:openstack- > bounces+salvatore.orlando=eu.citrix.com@lists.launchpad.net] On Behalf Of > John Garbutt > Sent: 19 March 2012 18:01 > To: 'Thomas Goirand' > Cc: PKG OpenStack; Dave Scott; openstack@lists.launchpad.net; xen-api > Subject: Re: [Openstack] [Xen-API] nova-xcp-network plugin searching for a > xapi0 interface > > Hi, > > Looks like the network configuration is not quite right. > > Have a look at this, for an example of how things could look networking wise > (when using DevStack and XenServer with two nics): > http://wiki.openstack.org/XenServer/XenXCPAndXenServer > > The manuals have a good description, although it is a little KVM specific: > http://docs.openstack.org/trunk/openstack- > compute/admin/content/configuring-flat-dhcp-networking.html > > I suggested using DevStack because it is the best "documentation" for a > working set of flags right now (yes, not ideal, we must fix that asap!). Take a > look: > https://github.com/openstack-dev/devstack/blob/master/stack.sh#L291 > Note the defaults in the nova code might work for KVM, but will not work for > XenServer, so you will need to set those flags with more appropriate values. > > Hope that helps, > John > > -----Original Message----- > From: Thomas Goirand [mailto:thomas@goirand.fr] > Sent: 19 March 2012 5:25 > To: John Garbutt > Cc: Dave Scott; xen-api; PKG OpenStack; openstack@lists.launchpad.net > Subject: Re: [Xen-API] nova-xcp-network plugin searching for a xapi0 > interface > > On 03/20/2012 12:05 AM, John Garbutt wrote: > > This sounds a lot like a configuration issue with your guest network bridge. > Are you OK to supply your nova.conf file? > > Sure! Here it is: > > --sql_connection=mysql://nova:admin@127.0.0.1/nova > --novncproxy_base_url=http://:6080/vnc_auto.html > --rabbit_host= > --glance_api_servers=:9292 > --network_manager=nova.network.manager.VlanManager > --vlan_interface=br100 > --dhcpbridge=/usr/bin/nova-dhcpbridge > --firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver > --connection_type=xenapi > --xenapi_connection_url=https:// > --xenapi_connection_username=root > --xenapi_connection_password=XXXXXXX > --reboot_timeout=600 > --rescue_timeout=86400 > --resize_confirm_window=86400 > --auth_strategy=keystone > --allow_admin_api > --allow_resize_to_same_host > --logdir=/var/log/nova > --state_path=/var/lib/nova > --lock_path=/var/lock/nova > --vncserver_listen=0.0.0.0 > --force_dhcp_release > --use_deprecated_auth > --use_project_ca > --verbose > > Note that since I restarted xcp-xapi, it seems that the xapi0 bridge is created > each time I create a VM, which is what I was expecting. So that parts seems > to work now, but the issue is that now, I have no networking at all (eg: I can't > reach the instance from the Openstack domU). > > Here's what "xe network-list" returns on my dom0: > > uuid ( RO) : > name-label ( RW): br100 > name-description ( RW): network for nova bridge br100 > bridge ( RO): xapi0 > > So it really is nova who created this. But shouldn't it be linked to my > xenbr0 as well? What is the normal networking setup that should be done? > > There's absolutely zero documentation which I could find about this. Of > course, I'll write one directly in our Debian packages as soon as this works. > > > Also, have you tried using DevStack first? It is a good way to get the hang of > how the flags work. > > No it's not! DevStack is for testing with XenServer, and assumes that you'd > be working with Ubuntu. Here, I'm testing the Debian packages that we are > working on in Debian. Please don't direct me to DevStack, this wont help. > > > I'm not familiar with the design of the Nova plugins but my guess is that > they're trying to use the "Host internal management network" -- a network > from which VMs can access the XenAPI (i.e. talk to xapi in domain 0). > > > > On recent XCP versions the default bridge name changed to "xenapi" to > make it easier to distinguish from a firewall rules PoV. > > As per Mike on IRC, (from Citrix, upstream for XCP, XenServer and Kronos), > each time there's a new network being created, XCP create a xapiX bridge > automatically. I shouldn't have even try to bring the xapi0 bridge myself, XCP > does it (if it doesn't, then there's an issue). > > > Note that the actual linux bridge (or openvswitch) is created on demand so > you won't see it in "brctl show" or "ovs-vsctl show" until it's being used. > > > > Try changing "xapi0" to "xenapi" in the plugins and see if they work better? > > Nop, that wont help, xapi0 is really what to expect. My only issue now is to > have it connected to the br100 of Openstack in my domU. > > Thanks for the help already, > Cheers, > > Thomas > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ 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 23 14:21:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 14:21: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 1SB5Mh-0001Cq-13; Fri, 23 Mar 2012 14:21:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB5Me-0001CT-UN for xen-api@lists.xen.org; Fri, 23 Mar 2012 14:21:13 +0000 Received: from [85.158.143.99:23396] by server-2.bemta-4.messagelabs.com id C1/C0-17550-8D68C6F4; Fri, 23 Mar 2012 14:21:12 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1332512471!14247019!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31685 invoked from network); 23 Mar 2012 14:21:11 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 23 Mar 2012 14:21:11 -0000 Received: by eeit10 with SMTP id t10so1063219eei.32 for ; Fri, 23 Mar 2012 07:21:10 -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=afcjGe9y7z8Yj/czPEBbpjpGeuBcJ5SJuzUrP351rFM=; b=vulxlzPdxh5rRDDwfePjhf8rFPvcJuvEFgfx2QibCjuXlcFrSt4nJVrU8/tU/yrAHH omjop8GDjolU2qYVLMxszdD8zijcNQ1xqaa12jMtoEnzA0tZvwCKw/xQ1dSKNVH/BqwI Zy1syG9D77mDbzOUY8PBJElp4L3vcWKKucGBfYrDhe+ZvqeoA/qQZG9iXHvhHpssgskj IO9srbIGoojF1CNMQuarQQrm1QdzS9GhjcZEJecwpTbGV0VO8Gp0GNMl822fhpsTTfPa TZ7QOq92YvYTSrww1Jw4PguppgRBVeqc+FJP1a5Qvh8CG4biAYj3puxCr0VTKc1vlz3A tdkA== Received: by 10.14.123.202 with SMTP id v50mr1680513eeh.95.1332512470722; Fri, 23 Mar 2012 07:21:10 -0700 (PDT) Received: from [172.16.25.10] ([176.251.82.166]) by mx.google.com with ESMTPS id n56sm28666419eeb.4.2012.03.23.07.21.08 (version=SSLv3 cipher=OTHER); Fri, 23 Mar 2012 07:21:09 -0700 (PDT) Message-ID: <4F6C86D3.1040908@xen.org> Date: Fri, 23 Mar 2012 14:21:07 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-API] Xen Documentation Day: March 26th X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, everybody. A quick reminder that the next Xen Document Day is happening = next Monday. For more detail see = http://blog.xen.org/index.php/2012/03/22/xen-documentation-day-march-26th/ = or below ... Hope to see you on IRC! Feel free to add stuff to the TODO list = (http://wiki.xen.org/wiki/Xen_Document_Days#TODO) or put your name = besides an item if you intend to work on it. Best Regards Lars ************************************* * Xen Documentation Day: March 26th * ************************************* We have another Xen document day come up next Monday. Xen Document Days = are for people who care about Xen Documentation and want to improve it. = We introduced Documentation Days, because working on documentation in = parallel with like minded-people, is just more fun than working alone! = Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained = TODO list (http://wiki.xen.org/wiki/Xen_Document_Days#TODO). Of course, = you can work on anything you like: the list just provides suggestions. How do I participate? =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - Join us on IRC: freenode channel #xendocday - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! Interesting items on the TODO list =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D I just went through our community maintained Docs Day TODO list and = thought I=92d highlight some items: - A feature status document that shows which features work in which Xen = release! That would be something for our developers to create! - Admin docs covering topics such as =93Setting boot order for domUs (PV = and HVM)=94, =93Chaining pypxeboot and pygrub=94, etc. Any proficient Xen user can help = put these together! - Reviewing Wiki main page categories such as Beginners could really = benefit from YOUR input. It would help to see whether the documents in a category are = useful to YOU and which ones should be highlighted in a trail. - There is also some easy Wiki maintenance work that needs doing: some = of it is as easy as formatting. Anybody who knows could do this! Personally, I will be working on: - A new =93Why Xen=94 and maybe =93Which Xen=94 document, to help people de= cide = whether Xen is for them and what flavour of Xen is best - I will also be working on content for the new xen.org website I am looking forward to the day and hopefully documentation days will = become a regular Xen event. See you on IRC! _______________________________________________ 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 23 14:21:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 14:21: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 1SB5Mh-0001Cq-13; Fri, 23 Mar 2012 14:21:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB5Me-0001CT-UN for xen-api@lists.xen.org; Fri, 23 Mar 2012 14:21:13 +0000 Received: from [85.158.143.99:23396] by server-2.bemta-4.messagelabs.com id C1/C0-17550-8D68C6F4; Fri, 23 Mar 2012 14:21:12 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-216.messagelabs.com!1332512471!14247019!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31685 invoked from network); 23 Mar 2012 14:21:11 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-14.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 23 Mar 2012 14:21:11 -0000 Received: by eeit10 with SMTP id t10so1063219eei.32 for ; Fri, 23 Mar 2012 07:21:10 -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=afcjGe9y7z8Yj/czPEBbpjpGeuBcJ5SJuzUrP351rFM=; b=vulxlzPdxh5rRDDwfePjhf8rFPvcJuvEFgfx2QibCjuXlcFrSt4nJVrU8/tU/yrAHH omjop8GDjolU2qYVLMxszdD8zijcNQ1xqaa12jMtoEnzA0tZvwCKw/xQ1dSKNVH/BqwI Zy1syG9D77mDbzOUY8PBJElp4L3vcWKKucGBfYrDhe+ZvqeoA/qQZG9iXHvhHpssgskj IO9srbIGoojF1CNMQuarQQrm1QdzS9GhjcZEJecwpTbGV0VO8Gp0GNMl822fhpsTTfPa TZ7QOq92YvYTSrww1Jw4PguppgRBVeqc+FJP1a5Qvh8CG4biAYj3puxCr0VTKc1vlz3A tdkA== Received: by 10.14.123.202 with SMTP id v50mr1680513eeh.95.1332512470722; Fri, 23 Mar 2012 07:21:10 -0700 (PDT) Received: from [172.16.25.10] ([176.251.82.166]) by mx.google.com with ESMTPS id n56sm28666419eeb.4.2012.03.23.07.21.08 (version=SSLv3 cipher=OTHER); Fri, 23 Mar 2012 07:21:09 -0700 (PDT) Message-ID: <4F6C86D3.1040908@xen.org> Date: Fri, 23 Mar 2012 14:21:07 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org, xen-users@lists.xen.org Subject: [Xen-API] Xen Documentation Day: March 26th X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi, everybody. A quick reminder that the next Xen Document Day is happening = next Monday. For more detail see = http://blog.xen.org/index.php/2012/03/22/xen-documentation-day-march-26th/ = or below ... Hope to see you on IRC! Feel free to add stuff to the TODO list = (http://wiki.xen.org/wiki/Xen_Document_Days#TODO) or put your name = besides an item if you intend to work on it. Best Regards Lars ************************************* * Xen Documentation Day: March 26th * ************************************* We have another Xen document day come up next Monday. Xen Document Days = are for people who care about Xen Documentation and want to improve it. = We introduced Documentation Days, because working on documentation in = parallel with like minded-people, is just more fun than working alone! = Everybody who can contribute is welcome to join! For a list of items that need work, check out the community maintained = TODO list (http://wiki.xen.org/wiki/Xen_Document_Days#TODO). Of course, = you can work on anything you like: the list just provides suggestions. How do I participate? =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - Join us on IRC: freenode channel #xendocday - Tell people what you intend to work on (to avoid doing something somebody else is already working on) - Fix some documentation - Help others - And above all: have fun! Interesting items on the TODO list =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D I just went through our community maintained Docs Day TODO list and = thought I=92d highlight some items: - A feature status document that shows which features work in which Xen = release! That would be something for our developers to create! - Admin docs covering topics such as =93Setting boot order for domUs (PV = and HVM)=94, =93Chaining pypxeboot and pygrub=94, etc. Any proficient Xen user can help = put these together! - Reviewing Wiki main page categories such as Beginners could really = benefit from YOUR input. It would help to see whether the documents in a category are = useful to YOU and which ones should be highlighted in a trail. - There is also some easy Wiki maintenance work that needs doing: some = of it is as easy as formatting. Anybody who knows could do this! Personally, I will be working on: - A new =93Why Xen=94 and maybe =93Which Xen=94 document, to help people de= cide = whether Xen is for them and what flavour of Xen is best - I will also be working on content for the new xen.org website I am looking forward to the day and hopefully documentation days will = become a regular Xen event. See you on IRC! _______________________________________________ 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 23 14:22:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 14:22: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 1SB5Nn-0001Kf-9j; Fri, 23 Mar 2012 14:22:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB49E-0008NI-8I for xen-api@lists.xensource.com; Fri, 23 Mar 2012 13:03:16 +0000 Received: from [85.158.139.83:13412] by server-7.bemta-5.messagelabs.com id 9E/30-16195-3947C6F4; Fri, 23 Mar 2012 13:03:15 +0000 X-Env-Sender: isha.tarte@esds.co.in X-Msg-Ref: server-15.tower-182.messagelabs.com!1332507789!20612713!1 X-Originating-IP: [115.124.104.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8771 invoked from network); 23 Mar 2012 13:03:14 -0000 Received: from server.esds.co.in (HELO server.esds.co.in) (115.124.104.10) by server-15.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Mar 2012 13:03:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=esds.co.in; h=Received:MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To:Subject:Message-ID:X-Sender:User-Agent; b=Y2Vg7av/0qm6bLbzKIPvJBhvQWXqgTo5mkwJogcxtRtLxCDLDg30gPgYYM7s+4fiV3JEnJ7hhnt/ibF6Sl/jtpJW37jg+Zr00gZNlLjk00gAXeCVL3whmjM1zeCYC0yM; Received: from localhost.localdomain ([127.0.0.1]:49313 helo=mail.esds.co.in) by server.esds.co.in with esmtpa (Exim 4.69) (envelope-from ) id 1SB491-0000pp-39 for xen-api@lists.xensource.com; Fri, 23 Mar 2012 18:33:03 +0530 MIME-Version: 1.0 Date: Fri, 23 Mar 2012 18:33:02 +0530 From: isha.tarte@esds.co.in To: Message-ID: X-Sender: isha.tarte@esds.co.in User-Agent: Roundcube Webmail/0.6 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server.esds.co.in X-AntiAbuse: Original Domain - lists.xensource.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - esds.co.in X-Mailman-Approved-At: Fri, 23 Mar 2012 14:22:21 +0000 Subject: [Xen-API] Architecture of XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Hello, Will you please provide me the generalized architecture of hypervisor (XEN) including its communication protocol. Thanks & regards, Isha _______________________________________________ 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 23 14:22:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 14:22: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 1SB5Nn-0001Kf-9j; Fri, 23 Mar 2012 14:22:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB49E-0008NI-8I for xen-api@lists.xensource.com; Fri, 23 Mar 2012 13:03:16 +0000 Received: from [85.158.139.83:13412] by server-7.bemta-5.messagelabs.com id 9E/30-16195-3947C6F4; Fri, 23 Mar 2012 13:03:15 +0000 X-Env-Sender: isha.tarte@esds.co.in X-Msg-Ref: server-15.tower-182.messagelabs.com!1332507789!20612713!1 X-Originating-IP: [115.124.104.10] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8771 invoked from network); 23 Mar 2012 13:03:14 -0000 Received: from server.esds.co.in (HELO server.esds.co.in) (115.124.104.10) by server-15.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Mar 2012 13:03:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=esds.co.in; h=Received:MIME-Version:Content-Type:Content-Transfer-Encoding:Date:From:To:Subject:Message-ID:X-Sender:User-Agent; b=Y2Vg7av/0qm6bLbzKIPvJBhvQWXqgTo5mkwJogcxtRtLxCDLDg30gPgYYM7s+4fiV3JEnJ7hhnt/ibF6Sl/jtpJW37jg+Zr00gZNlLjk00gAXeCVL3whmjM1zeCYC0yM; Received: from localhost.localdomain ([127.0.0.1]:49313 helo=mail.esds.co.in) by server.esds.co.in with esmtpa (Exim 4.69) (envelope-from ) id 1SB491-0000pp-39 for xen-api@lists.xensource.com; Fri, 23 Mar 2012 18:33:03 +0530 MIME-Version: 1.0 Date: Fri, 23 Mar 2012 18:33:02 +0530 From: isha.tarte@esds.co.in To: Message-ID: X-Sender: isha.tarte@esds.co.in User-Agent: Roundcube Webmail/0.6 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server.esds.co.in X-AntiAbuse: Original Domain - lists.xensource.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - esds.co.in X-Mailman-Approved-At: Fri, 23 Mar 2012 14:22:21 +0000 Subject: [Xen-API] Architecture of XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Hello, Will you please provide me the generalized architecture of hypervisor (XEN) including its communication protocol. Thanks & regards, Isha _______________________________________________ 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 23 17:01:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 17:01:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB7rQ-0004NO-IX; Fri, 23 Mar 2012 17:01:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB7rP-0004NJ-6p for xen-api@lists.xen.org; Fri, 23 Mar 2012 17:01:07 +0000 Received: from [85.158.138.51:46504] by server-1.bemta-3.messagelabs.com id 41/7D-04539-25CAC6F4; Fri, 23 Mar 2012 17:01:06 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1332522065!8030559!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3815 invoked from network); 23 Mar 2012 17:01:05 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 23 Mar 2012 17:01:05 -0000 Received: by eeit10 with SMTP id t10so1109799eei.32 for ; Fri, 23 Mar 2012 10:01:05 -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=LxJeFVjk+SqRFp+dbiHx7VqUGqqP51Tz6go2AdE5XWE=; b=MdHi6++rggMmJrJ/zn60FQRHL+c0zqn9dlnAcQrykmk++MyOUxZecXMpQhQv5N5PDa 1w7BbM47UHh9Cr+jWyWdlukWOHDuoaep2hZAXF6Ea1wcL1ITo05VssNd3iw4MlgK1whJ RftS0VI8byxsfDbi2+Xd/IJNRkaqDCkuaR2d5t+Tz6R5JnEgST+Y6y6JtSpiI8GqzPdW bViwlp/rImRxUXewh/j1mSfTCZtfLOKZk3Cz8AiP/lAA1AtNWN6AMrjpLCKcmCnLE1m9 Fjjkvv0ghRYOcIkuJWIAfk64KvrRmiEqjlWUm3UBChG+xoDZN1yxx3GVWY//SiDN+3dX WLCA== Received: by 10.213.29.5 with SMTP id o5mr901327ebc.279.1332522065306; Fri, 23 Mar 2012 10:01:05 -0700 (PDT) Received: from [172.16.25.10] ([176.251.82.166]) by mx.google.com with ESMTPS id m55sm29342246eei.1.2012.03.23.10.00.58 (version=SSLv3 cipher=OTHER); Fri, 23 Mar 2012 10:01:02 -0700 (PDT) Message-ID: <4F6CAC49.7030300@xen.org> Date: Fri, 23 Mar 2012 17:00:57 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-devel@lists.xen.org, David Nalley , mark.hinkle@citrix.com, xen-api@lists.xen.org, xen-arm@lists.xen.org Subject: [Xen-API] GSOC 2012 Feedback on Xen.org X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Discussion of API issues surrounding Xen 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 Guys, we just got off the call regarding GSOC 2012 feedback. As you know, we did not make it this year. Fundamentally a number of things are going on: a) Google is mixing up mentoring orgs a little to give new organizations a chance b) Some organizations which had good applications and ideas pages got caught out by this This was actually not the case for us: - Positive feedback on outcome in 2011 - Good application - Bad ideas page !!! In a nutshell, Google chooses a returning mentoring org basically on the quality and content of the ideas page. This means a) General information for students b) Clarity, expectation setting, process, etc. c) Quantity of ideas (relative to size of community) d) Quality of ideas (detail, how clear, are mentors assigned, etc.) Specific feedback we got was that our ideas were not well enough formed or described and that we did not make it because of this. Also that there was generally too little guidance for students on it. This means that next year, we will need to have ideas well formulated, vetted, mentors assigned and everything presented nicely by the time we apply as mentoring organization for GSoC. I guess we got away with not doing this in 2011, because we were still considered a new mentoring org. So in a nutshell, because we succeeded two times in a row the bar has been raised and we were not aware of it. In a nutshell: - We need to start the process of collating ideas straight in the new year (or even before XMas) - We need to decide how to run the program and publish this on the ideas page before we apply - Use February to decide which ideas to put forward, identify mentors, tidy the ideas, etc. - Clean everything up and make it presentable and look nice - We will also need to show a degree of maturity on the ideas page*) Basically, we will need to do signifcant work for GSoC before we get accepted on the assumption that we will. Do let me know if you have any questions. Best Regards Lars ----- *) Aka process and information to help set expectations. We need to include all information for students and mentors when we apply for GSoC. We actually had a lot of this from 2011, but I took it out out because we were going to make significant changes which we had not yet agreed. Obviously that was a mistake. _______________________________________________ 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 23 17:01:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 17:01:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB7rQ-0004NO-IX; Fri, 23 Mar 2012 17:01:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB7rP-0004NJ-6p for xen-api@lists.xen.org; Fri, 23 Mar 2012 17:01:07 +0000 Received: from [85.158.138.51:46504] by server-1.bemta-3.messagelabs.com id 41/7D-04539-25CAC6F4; Fri, 23 Mar 2012 17:01:06 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-174.messagelabs.com!1332522065!8030559!1 X-Originating-IP: [74.125.83.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3815 invoked from network); 23 Mar 2012 17:01:05 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-13.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 23 Mar 2012 17:01:05 -0000 Received: by eeit10 with SMTP id t10so1109799eei.32 for ; Fri, 23 Mar 2012 10:01:05 -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=LxJeFVjk+SqRFp+dbiHx7VqUGqqP51Tz6go2AdE5XWE=; b=MdHi6++rggMmJrJ/zn60FQRHL+c0zqn9dlnAcQrykmk++MyOUxZecXMpQhQv5N5PDa 1w7BbM47UHh9Cr+jWyWdlukWOHDuoaep2hZAXF6Ea1wcL1ITo05VssNd3iw4MlgK1whJ RftS0VI8byxsfDbi2+Xd/IJNRkaqDCkuaR2d5t+Tz6R5JnEgST+Y6y6JtSpiI8GqzPdW bViwlp/rImRxUXewh/j1mSfTCZtfLOKZk3Cz8AiP/lAA1AtNWN6AMrjpLCKcmCnLE1m9 Fjjkvv0ghRYOcIkuJWIAfk64KvrRmiEqjlWUm3UBChG+xoDZN1yxx3GVWY//SiDN+3dX WLCA== Received: by 10.213.29.5 with SMTP id o5mr901327ebc.279.1332522065306; Fri, 23 Mar 2012 10:01:05 -0700 (PDT) Received: from [172.16.25.10] ([176.251.82.166]) by mx.google.com with ESMTPS id m55sm29342246eei.1.2012.03.23.10.00.58 (version=SSLv3 cipher=OTHER); Fri, 23 Mar 2012 10:01:02 -0700 (PDT) Message-ID: <4F6CAC49.7030300@xen.org> Date: Fri, 23 Mar 2012 17:00:57 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-devel@lists.xen.org, David Nalley , mark.hinkle@citrix.com, xen-api@lists.xen.org, xen-arm@lists.xen.org Subject: [Xen-API] GSOC 2012 Feedback on Xen.org X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Discussion of API issues surrounding Xen 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 Guys, we just got off the call regarding GSOC 2012 feedback. As you know, we did not make it this year. Fundamentally a number of things are going on: a) Google is mixing up mentoring orgs a little to give new organizations a chance b) Some organizations which had good applications and ideas pages got caught out by this This was actually not the case for us: - Positive feedback on outcome in 2011 - Good application - Bad ideas page !!! In a nutshell, Google chooses a returning mentoring org basically on the quality and content of the ideas page. This means a) General information for students b) Clarity, expectation setting, process, etc. c) Quantity of ideas (relative to size of community) d) Quality of ideas (detail, how clear, are mentors assigned, etc.) Specific feedback we got was that our ideas were not well enough formed or described and that we did not make it because of this. Also that there was generally too little guidance for students on it. This means that next year, we will need to have ideas well formulated, vetted, mentors assigned and everything presented nicely by the time we apply as mentoring organization for GSoC. I guess we got away with not doing this in 2011, because we were still considered a new mentoring org. So in a nutshell, because we succeeded two times in a row the bar has been raised and we were not aware of it. In a nutshell: - We need to start the process of collating ideas straight in the new year (or even before XMas) - We need to decide how to run the program and publish this on the ideas page before we apply - Use February to decide which ideas to put forward, identify mentors, tidy the ideas, etc. - Clean everything up and make it presentable and look nice - We will also need to show a degree of maturity on the ideas page*) Basically, we will need to do signifcant work for GSoC before we get accepted on the assumption that we will. Do let me know if you have any questions. Best Regards Lars ----- *) Aka process and information to help set expectations. We need to include all information for students and mentors when we apply for GSoC. We actually had a lot of this from 2011, but I took it out out because we were going to make significant changes which we had not yet agreed. Obviously that was a mistake. _______________________________________________ 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 23 18:20:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 18:20:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB95a-0005XU-L7; Fri, 23 Mar 2012 18:19:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB95Z-0005XE-Mi for xen-api@lists.xensource.com; Fri, 23 Mar 2012 18:19:49 +0000 Received: from [85.158.139.83:49332] by server-12.bemta-5.messagelabs.com id F5/CF-05587-4CEBC6F4; Fri, 23 Mar 2012 18:19:48 +0000 X-Env-Sender: todd.deshane.xen@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1332526786!19839417!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10520 invoked from network); 23 Mar 2012 18:19:47 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 23 Mar 2012 18:19:47 -0000 Received: by iadj38 with SMTP id j38so6195687iad.30 for ; Fri, 23 Mar 2012 11:19:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=MRFPVefFfYwj2iZFQ2M08vbRNfPl215kTiiL9QApO/M=; b=w8ALNVQ7Qnc5Ya8dVuvRsdwNtvZ98gIC+4KCDPP2hYAWapaMPvsBZKyr4/PuiaBIt3 +D5TEbjQu4FntztJKLu/BlcEXnU5cJ8p7jj2lLA9cbQ5qDokn10DChHrLcSW2tivF72U xpGFCKTgaHFx8okMJn30yCLcLCIhT5xP9S+gpN5tvR/1mvaRKwqiGYG3+ZuStMihPNPE 4CA8YaJEL1ULjlzmruY3chvvs5YmlDHHNuOpMD9utBkdflLqB++rFzzNv13WRlUsdVM9 65RDLY3uHorf/OoMyLhynJmYD2EpKSR8p6W4NZk1GTH90D4scylvEb8gAuWrvJA0Ro4M EkTg== Received: by 10.50.149.167 with SMTP id ub7mr2833917igb.43.1332526785595; Fri, 23 Mar 2012 11:19:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.234.206 with HTTP; Fri, 23 Mar 2012 11:19:25 -0700 (PDT) In-Reply-To: References: From: Todd Deshane Date: Fri, 23 Mar 2012 14:19:25 -0400 X-Google-Sender-Auth: LHTE0k5LGCepgtI4KdhcssJBYqo Message-ID: To: isha.tarte@esds.co.in Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Architecture of XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Fri, Mar 23, 2012 at 9:03 AM, wrote: > Hello, > > Will you please provide me the generalized =A0architecture of hypervisor = (XEN) > including its communication protocol. > There is a lot of developer documentation here: http://wiki.xensource.com/wiki/XAPI_Developer_Guide For some more general XCP information see: http://www.slideshare.net/cloudstack/vbacd-xen-cloud-computing http://vimeo.com/38636349 Hope that helps. You may want to ask more specific questions. That way we can give you more specific answers. Thanks, Todd -- = Todd Deshane http://www.linkedin.com/in/deshantm http://blog.xen.org/ http://wiki.xen.org/ _______________________________________________ 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 23 18:20:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 23 Mar 2012 18:20:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB95a-0005XU-L7; Fri, 23 Mar 2012 18:19:50 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SB95Z-0005XE-Mi for xen-api@lists.xensource.com; Fri, 23 Mar 2012 18:19:49 +0000 Received: from [85.158.139.83:49332] by server-12.bemta-5.messagelabs.com id F5/CF-05587-4CEBC6F4; Fri, 23 Mar 2012 18:19:48 +0000 X-Env-Sender: todd.deshane.xen@gmail.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1332526786!19839417!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10520 invoked from network); 23 Mar 2012 18:19:47 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 23 Mar 2012 18:19:47 -0000 Received: by iadj38 with SMTP id j38so6195687iad.30 for ; Fri, 23 Mar 2012 11:19:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=MRFPVefFfYwj2iZFQ2M08vbRNfPl215kTiiL9QApO/M=; b=w8ALNVQ7Qnc5Ya8dVuvRsdwNtvZ98gIC+4KCDPP2hYAWapaMPvsBZKyr4/PuiaBIt3 +D5TEbjQu4FntztJKLu/BlcEXnU5cJ8p7jj2lLA9cbQ5qDokn10DChHrLcSW2tivF72U xpGFCKTgaHFx8okMJn30yCLcLCIhT5xP9S+gpN5tvR/1mvaRKwqiGYG3+ZuStMihPNPE 4CA8YaJEL1ULjlzmruY3chvvs5YmlDHHNuOpMD9utBkdflLqB++rFzzNv13WRlUsdVM9 65RDLY3uHorf/OoMyLhynJmYD2EpKSR8p6W4NZk1GTH90D4scylvEb8gAuWrvJA0Ro4M EkTg== Received: by 10.50.149.167 with SMTP id ub7mr2833917igb.43.1332526785595; Fri, 23 Mar 2012 11:19:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.234.206 with HTTP; Fri, 23 Mar 2012 11:19:25 -0700 (PDT) In-Reply-To: References: From: Todd Deshane Date: Fri, 23 Mar 2012 14:19:25 -0400 X-Google-Sender-Auth: LHTE0k5LGCepgtI4KdhcssJBYqo Message-ID: To: isha.tarte@esds.co.in Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Architecture of XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On Fri, Mar 23, 2012 at 9:03 AM, wrote: > Hello, > > Will you please provide me the generalized =A0architecture of hypervisor = (XEN) > including its communication protocol. > There is a lot of developer documentation here: http://wiki.xensource.com/wiki/XAPI_Developer_Guide For some more general XCP information see: http://www.slideshare.net/cloudstack/vbacd-xen-cloud-computing http://vimeo.com/38636349 Hope that helps. You may want to ask more specific questions. That way we can give you more specific answers. Thanks, Todd -- = Todd Deshane http://www.linkedin.com/in/deshantm http://blog.xen.org/ http://wiki.xen.org/ _______________________________________________ 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 24 13:06:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 24 Mar 2012 13:06: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 1SBQfU-0003bt-Aa; Sat, 24 Mar 2012 13:06:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SBQfS-0003bf-SZ for xen-api@lists.xensource.com; Sat, 24 Mar 2012 13:06:03 +0000 Received: from [193.109.254.147:25035] by server-7.bemta-14.messagelabs.com id 4D/11-01627-AB6CD6F4; Sat, 24 Mar 2012 13:06:02 +0000 X-Env-Sender: torushikeshj@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1332594361!1887188!1 X-Originating-IP: [209.85.215.171] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15705 invoked from network); 24 Mar 2012 13:06:01 -0000 Received: from mail-ey0-f171.google.com (HELO mail-ey0-f171.google.com) (209.85.215.171) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Mar 2012 13:06:01 -0000 Received: by eaal11 with SMTP id l11so1714053eaa.30 for ; Sat, 24 Mar 2012 06:06:01 -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=ifg3aIGOK/Lhe9YitNDyikd9Btr+3POPz52YiZ5AD8M=; b=p6MvgF7jNQgwYbYuPqi8q5DoRof7rphNT0awOUlHxanAPAKpj+bilHockBp9+eQV9x fly6sDAplMO67rQmXqa4FQ3tsFEeyNilji4mfO5itIZ+nnrRNevBCcUJAM78JYqrStAr /3iBbTaHiFgJA9iNQ29KJYQrt5FrBk475+z/q6JnG+jxAtSeo2hWAZ+g4HUfa0Wkt+8K azemIqbQX8ntbyRk5Sqay0ubEseq4gIHhVG/7WcMAC/Bcl90/ytB/w7KQlSYEhA+QE9N ZW4k3i41u7s7qsdfZy3ysvTwb277ngXc7QzLuz7jy6UQMnPqsRlZSStHkfWniYbCGdXB 2mvg== MIME-Version: 1.0 Received: by 10.14.183.194 with SMTP id q42mr2050405eem.130.1332594360976; Sat, 24 Mar 2012 06:06:00 -0700 (PDT) Received: by 10.14.184.7 with HTTP; Sat, 24 Mar 2012 06:06:00 -0700 (PDT) Date: Sat, 24 Mar 2012 18:36:00 +0530 Message-ID: From: R J To: xen-api@lists.xensource.com, xen-devel@lists.xensource.com Subject: [Xen-API] CentOS 6.X balloon issue [ XCP 1.5 / CentOS6 Bug ] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8051199474314288988==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8051199474314288988== Content-Type: multipart/alternative; boundary=047d7b3a800484055e04bbfccdbb --047d7b3a800484055e04bbfccdbb Content-Type: text/plain; charset=ISO-8859-1 Hello List, On XCP1.5 ballooning of CentOS6.X does not work correctly. The DomU can be ballooned up only till its start_target_mem and seems to disobey the static max. For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyond 4GB though it has static max as 16GB. I can confirm same issue on XCP1.1, so it might be something only with CentOS6. - RJ --047d7b3a800484055e04bbfccdbb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello List,

On XCP1.5 ballooning of CentOS6.X does not work correctl= y.
The DomU can be ballooned up only till its start_target_mem and seems= to disobey the static max.

For e.g If I start a CentOS6 DomU with 4= GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyon= d 4GB though it has static max as 16GB.

I can confirm same issue on XCP1.1, so it might be something only with = CentOS6.

- RJ
--047d7b3a800484055e04bbfccdbb-- --===============8051199474314288988== 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 --===============8051199474314288988==-- From xen-api-bounces@lists.xen.org Sat Mar 24 13:06:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 24 Mar 2012 13:06: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 1SBQfU-0003bt-Aa; Sat, 24 Mar 2012 13:06:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SBQfS-0003bf-SZ for xen-api@lists.xensource.com; Sat, 24 Mar 2012 13:06:03 +0000 Received: from [193.109.254.147:25035] by server-7.bemta-14.messagelabs.com id 4D/11-01627-AB6CD6F4; Sat, 24 Mar 2012 13:06:02 +0000 X-Env-Sender: torushikeshj@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1332594361!1887188!1 X-Originating-IP: [209.85.215.171] X-SpamReason: No, hits=1.5 required=7.0 tests=HTML_00_10,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15705 invoked from network); 24 Mar 2012 13:06:01 -0000 Received: from mail-ey0-f171.google.com (HELO mail-ey0-f171.google.com) (209.85.215.171) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 24 Mar 2012 13:06:01 -0000 Received: by eaal11 with SMTP id l11so1714053eaa.30 for ; Sat, 24 Mar 2012 06:06:01 -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=ifg3aIGOK/Lhe9YitNDyikd9Btr+3POPz52YiZ5AD8M=; b=p6MvgF7jNQgwYbYuPqi8q5DoRof7rphNT0awOUlHxanAPAKpj+bilHockBp9+eQV9x fly6sDAplMO67rQmXqa4FQ3tsFEeyNilji4mfO5itIZ+nnrRNevBCcUJAM78JYqrStAr /3iBbTaHiFgJA9iNQ29KJYQrt5FrBk475+z/q6JnG+jxAtSeo2hWAZ+g4HUfa0Wkt+8K azemIqbQX8ntbyRk5Sqay0ubEseq4gIHhVG/7WcMAC/Bcl90/ytB/w7KQlSYEhA+QE9N ZW4k3i41u7s7qsdfZy3ysvTwb277ngXc7QzLuz7jy6UQMnPqsRlZSStHkfWniYbCGdXB 2mvg== MIME-Version: 1.0 Received: by 10.14.183.194 with SMTP id q42mr2050405eem.130.1332594360976; Sat, 24 Mar 2012 06:06:00 -0700 (PDT) Received: by 10.14.184.7 with HTTP; Sat, 24 Mar 2012 06:06:00 -0700 (PDT) Date: Sat, 24 Mar 2012 18:36:00 +0530 Message-ID: From: R J To: xen-api@lists.xensource.com, xen-devel@lists.xensource.com Subject: [Xen-API] CentOS 6.X balloon issue [ XCP 1.5 / CentOS6 Bug ] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8051199474314288988==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8051199474314288988== Content-Type: multipart/alternative; boundary=047d7b3a800484055e04bbfccdbb --047d7b3a800484055e04bbfccdbb Content-Type: text/plain; charset=ISO-8859-1 Hello List, On XCP1.5 ballooning of CentOS6.X does not work correctly. The DomU can be ballooned up only till its start_target_mem and seems to disobey the static max. For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyond 4GB though it has static max as 16GB. I can confirm same issue on XCP1.1, so it might be something only with CentOS6. - RJ --047d7b3a800484055e04bbfccdbb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello List,

On XCP1.5 ballooning of CentOS6.X does not work correctl= y.
The DomU can be ballooned up only till its start_target_mem and seems= to disobey the static max.

For e.g If I start a CentOS6 DomU with 4= GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyon= d 4GB though it has static max as 16GB.

I can confirm same issue on XCP1.1, so it might be something only with = CentOS6.

- RJ
--047d7b3a800484055e04bbfccdbb-- --===============8051199474314288988== 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 --===============8051199474314288988==-- From xen-api-bounces@lists.xen.org Sun Mar 25 12:05:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 25 Mar 2012 12:05:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SBmBp-0006e7-Tv; Sun, 25 Mar 2012 12:04:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SBmBn-0006e1-VV for xen-api@lists.xen.org; Sun, 25 Mar 2012 12:04:52 +0000 Received: from [193.109.254.147:51269] by server-9.bemta-14.messagelabs.com id 12/EA-05787-3E90F6F4; Sun, 25 Mar 2012 12:04:51 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1332677090!1953741!1 X-Originating-IP: [209.85.214.45] 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-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5017 invoked from network); 25 Mar 2012 12:04:50 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 25 Mar 2012 12:04:50 -0000 Received: by bkcjg9 with SMTP id jg9so4194490bkc.32 for ; Sun, 25 Mar 2012 05:04:49 -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=4a3yUyAVSE6tMGk3WLIruunVRIxzF+PK3DqjUdWO154=; b=c3DVx/ndzTZrNL9LfxxYxBXvZ7xc1e73wyCRJd5e4ToB01gGX96HkuJ+tecWPd2lie jMUSDgw63I6opV78WlZCHttNl3f6DyZjANM+4mL9Z0Ov5kUwVojCM2GF5Wy5cD/K6iaY TuQLgNNjRWMhmwKFDyfP30SrUxz0q945CkD9Mg07utW4QLrtQQxjVbUXq6OTFwBddT2j x6md/s457w/s4R9BL0zo87UQZTrca3V7L9/ttazEb3zci6W0Hk+hJSESYGmbwbjFnOCy DiPHeIEV7Nq4OyR7VRDJWkJlayzbT29Z1Vv6Gb3hf1gSedrO3BKf3WqmMEd8ofqV9fu4 Brcw== Received: by 10.204.154.194 with SMTP id p2mr3994572bkw.80.1332677089627; Sun, 25 Mar 2012 05:04:49 -0700 (PDT) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id r14sm26225524bkv.11.2012.03.25.05.04.47 (version=SSLv3 cipher=OTHER); Sun, 25 Mar 2012 05:04:48 -0700 (PDT) Message-ID: <4F6F09FE.7080506@gmail.com> Date: Sun, 25 Mar 2012 16:05:18 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] CentOS 6.X balloon issue [ XCP 1.5 / CentOS6 Bug ] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3814957540060690692==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3814957540060690692== Content-Type: multipart/alternative; boundary="------------080000010303040200040303" This is a multi-part message in MIME format. --------------080000010303040200040303 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Heh, I've reported that stuff many times, until it was fixed in recent kernels (about 3.1 or 3.2). No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen and so on). On 24.03.2012 17:06, R J wrote: > Hello List, > > On XCP1.5 ballooning of CentOS6.X does not work correctly. > The DomU can be ballooned up only till its start_target_mem and seems > to disobey the static max. > > For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works > fine between 256MB to 4GB but it cant go beyond 4GB though it has > static max as 16GB. > > I can confirm same issue on XCP1.1, so it might be something only with > CentOS6. > > - RJ > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------080000010303040200040303 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Heh, I've reported that stuff many times, until it was fixed in recent kernels (about 3.1 or 3.2).

No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen  and so on).



On 24.03.2012 17:06, R J wrote:
Hello List,

On XCP1.5 ballooning of CentOS6.X does not work correctly.
The DomU can be ballooned up only till its start_target_mem and seems to disobey the static max.

For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyond 4GB though it has static max as 16GB.

I can confirm same issue on XCP1.1, so it might be something only with CentOS6.

- RJ


_______________________________________________
xen-api mailing list
xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------080000010303040200040303-- --===============3814957540060690692== 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 --===============3814957540060690692==-- From xen-api-bounces@lists.xen.org Sun Mar 25 12:05:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 25 Mar 2012 12:05:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SBmBp-0006e7-Tv; Sun, 25 Mar 2012 12:04:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SBmBn-0006e1-VV for xen-api@lists.xen.org; Sun, 25 Mar 2012 12:04:52 +0000 Received: from [193.109.254.147:51269] by server-9.bemta-14.messagelabs.com id 12/EA-05787-3E90F6F4; Sun, 25 Mar 2012 12:04:51 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1332677090!1953741!1 X-Originating-IP: [209.85.214.45] 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-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5017 invoked from network); 25 Mar 2012 12:04:50 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 25 Mar 2012 12:04:50 -0000 Received: by bkcjg9 with SMTP id jg9so4194490bkc.32 for ; Sun, 25 Mar 2012 05:04:49 -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=4a3yUyAVSE6tMGk3WLIruunVRIxzF+PK3DqjUdWO154=; b=c3DVx/ndzTZrNL9LfxxYxBXvZ7xc1e73wyCRJd5e4ToB01gGX96HkuJ+tecWPd2lie jMUSDgw63I6opV78WlZCHttNl3f6DyZjANM+4mL9Z0Ov5kUwVojCM2GF5Wy5cD/K6iaY TuQLgNNjRWMhmwKFDyfP30SrUxz0q945CkD9Mg07utW4QLrtQQxjVbUXq6OTFwBddT2j x6md/s457w/s4R9BL0zo87UQZTrca3V7L9/ttazEb3zci6W0Hk+hJSESYGmbwbjFnOCy DiPHeIEV7Nq4OyR7VRDJWkJlayzbT29Z1Vv6Gb3hf1gSedrO3BKf3WqmMEd8ofqV9fu4 Brcw== Received: by 10.204.154.194 with SMTP id p2mr3994572bkw.80.1332677089627; Sun, 25 Mar 2012 05:04:49 -0700 (PDT) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id r14sm26225524bkv.11.2012.03.25.05.04.47 (version=SSLv3 cipher=OTHER); Sun, 25 Mar 2012 05:04:48 -0700 (PDT) Message-ID: <4F6F09FE.7080506@gmail.com> Date: Sun, 25 Mar 2012 16:05:18 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] CentOS 6.X balloon issue [ XCP 1.5 / CentOS6 Bug ] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3814957540060690692==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3814957540060690692== Content-Type: multipart/alternative; boundary="------------080000010303040200040303" This is a multi-part message in MIME format. --------------080000010303040200040303 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Heh, I've reported that stuff many times, until it was fixed in recent kernels (about 3.1 or 3.2). No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen and so on). On 24.03.2012 17:06, R J wrote: > Hello List, > > On XCP1.5 ballooning of CentOS6.X does not work correctly. > The DomU can be ballooned up only till its start_target_mem and seems > to disobey the static max. > > For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works > fine between 256MB to 4GB but it cant go beyond 4GB though it has > static max as 16GB. > > I can confirm same issue on XCP1.1, so it might be something only with > CentOS6. > > - RJ > > > _______________________________________________ > xen-api mailing list > xen-api@lists.xen.org > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------080000010303040200040303 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Heh, I've reported that stuff many times, until it was fixed in recent kernels (about 3.1 or 3.2).

No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen  and so on).



On 24.03.2012 17:06, R J wrote:
Hello List,

On XCP1.5 ballooning of CentOS6.X does not work correctly.
The DomU can be ballooned up only till its start_target_mem and seems to disobey the static max.

For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyond 4GB though it has static max as 16GB.

I can confirm same issue on XCP1.1, so it might be something only with CentOS6.

- RJ


_______________________________________________
xen-api mailing list
xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
--------------080000010303040200040303-- --===============3814957540060690692== 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 --===============3814957540060690692==-- From xen-api-bounces@lists.xen.org Mon Mar 26 06:56:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 06:56: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 1SC3qd-0008WS-8R; Mon, 26 Mar 2012 06:56:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC3qc-0008WL-1g for xen-api@lists.xen.org; Mon, 26 Mar 2012 06:56:10 +0000 Received: from [85.158.139.83:46103] by server-12.bemta-5.messagelabs.com id 86/90-05587-903107F4; Mon, 26 Mar 2012 06:56:09 +0000 X-Env-Sender: torushikeshj@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1332744962!17020513!1 X-Originating-IP: [74.125.83.45] 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-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1307 invoked from network); 26 Mar 2012 06:56:02 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 06:56:02 -0000 Received: by eeit10 with SMTP id t10so1465376eei.32 for ; Sun, 25 Mar 2012 23:56:02 -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=dVXwui85+Dv4H5EZqEMWHvzljp15rm4JD1PoUHZIkt8=; b=NvaniBflVLU8/L5v8/FQDsMV1OaiL+K+d9D8ONEo+Sh/P25v5+A2XDy51wIL/KYTL+ bScyfdK0pftlhKp14FzbYaRx0ey7tLuplp8WcvfmZUs3qRpo0tSeZgPxvsEqtTfe5ALR oqnfJsbgDpCt2PfsFv3XBJFxVdmpDDVRaaq7NYKqo5gnEIh1lkbf4wGAgUvlOaSHq9Yy EG2DDUdnYfgxDsdn3vbuo+WhjWHhsvi3NgLQwFy+SZVeelZYc3DSBIW0KVFET4k7sGjs b4kd0Vf79eSVu2+Dm0c4lcBQOFoKF1EhpQL83yZ8LtfEpOQnotk0ZHUGAhWXbiw5Pyqg +y4g== MIME-Version: 1.0 Received: by 10.14.28.132 with SMTP id g4mr2721112eea.96.1332744961968; Sun, 25 Mar 2012 23:56:01 -0700 (PDT) Received: by 10.14.184.7 with HTTP; Sun, 25 Mar 2012 23:56:01 -0700 (PDT) In-Reply-To: <4F6F09FE.7080506@gmail.com> References: <4F6F09FE.7080506@gmail.com> Date: Mon, 26 Mar 2012 12:26:01 +0530 Message-ID: From: R J To: George Shuklin Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] CentOS 6.X balloon issue [ XCP 1.5 / CentOS6 Bug ] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2032883644609279915==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2032883644609279915== Content-Type: multipart/alternative; boundary=bcaec52be65f08cb2404bc1fde3a --bcaec52be65f08cb2404bc1fde3a Content-Type: text/plain; charset=ISO-8859-1 On Sun, Mar 25, 2012 at 5:35 PM, George Shuklin wrote: > Heh, I've reported that stuff many times, until it was fixed in recent > kernels (about 3.1 or 3.2). > > No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP > toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse > f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen and so on). > > > Oh ! Do you have any URL so that I can track for this bug update ? And till the time this BUG gets resolved, how do I obtain a 2.6.32-xen ? I'm little familiar with Kernel Compilations but not too much. I would appreciate if you can guide me. > > On 24.03.2012 17:06, R J wrote: > > Hello List, > > On XCP1.5 ballooning of CentOS6.X does not work correctly. > The DomU can be ballooned up only till its start_target_mem and seems to > disobey the static max. > > For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine > between 256MB to 4GB but it cant go beyond 4GB though it has static max as > 16GB. > > I can confirm same issue on XCP1.1, so it might be something only with > CentOS6. > > - RJ > > > _______________________________________________ > 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 > > --bcaec52be65f08cb2404bc1fde3a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sun, Mar 25, 2012 at 5:35 PM, George = Shuklin <g= eorge.shuklin@gmail.com> wrote:
=20 =20 =20
Heh, I've reported that stuff many times, until it was fixed in recent kernels (about 3.1 or 3.2).

No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen=A0 and so on).



Oh ! Do you have any URL so= that I can track for this bug update ?
And till the time this BUG gets = resolved, how do I obtain a 2.6.32-xen ?

I'm little familiar wit= h Kernel Compilations but not too much. I would appreciate if you can guide= me.



On 24.03.2012 17:06, R J wrote:
Hello List= ,

On XCP1.5 ballooning of CentOS6.X does not work correctly.
The DomU can be ballooned up only till its start_target_mem and seems to disobey the static max.

For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyond 4GB though it has static max as 16GB.

I can confirm same issue on XCP1.1, so it might be something only with CentOS6.

- RJ


_______________________________________________
xen-api mailing list
xen-api@lists.xe=
n.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


--bcaec52be65f08cb2404bc1fde3a-- --===============2032883644609279915== 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 --===============2032883644609279915==-- From xen-api-bounces@lists.xen.org Mon Mar 26 06:56:19 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 06:56: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 1SC3qd-0008WS-8R; Mon, 26 Mar 2012 06:56:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC3qc-0008WL-1g for xen-api@lists.xen.org; Mon, 26 Mar 2012 06:56:10 +0000 Received: from [85.158.139.83:46103] by server-12.bemta-5.messagelabs.com id 86/90-05587-903107F4; Mon, 26 Mar 2012 06:56:09 +0000 X-Env-Sender: torushikeshj@gmail.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1332744962!17020513!1 X-Originating-IP: [74.125.83.45] 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-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1307 invoked from network); 26 Mar 2012 06:56:02 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-7.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 06:56:02 -0000 Received: by eeit10 with SMTP id t10so1465376eei.32 for ; Sun, 25 Mar 2012 23:56:02 -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=dVXwui85+Dv4H5EZqEMWHvzljp15rm4JD1PoUHZIkt8=; b=NvaniBflVLU8/L5v8/FQDsMV1OaiL+K+d9D8ONEo+Sh/P25v5+A2XDy51wIL/KYTL+ bScyfdK0pftlhKp14FzbYaRx0ey7tLuplp8WcvfmZUs3qRpo0tSeZgPxvsEqtTfe5ALR oqnfJsbgDpCt2PfsFv3XBJFxVdmpDDVRaaq7NYKqo5gnEIh1lkbf4wGAgUvlOaSHq9Yy EG2DDUdnYfgxDsdn3vbuo+WhjWHhsvi3NgLQwFy+SZVeelZYc3DSBIW0KVFET4k7sGjs b4kd0Vf79eSVu2+Dm0c4lcBQOFoKF1EhpQL83yZ8LtfEpOQnotk0ZHUGAhWXbiw5Pyqg +y4g== MIME-Version: 1.0 Received: by 10.14.28.132 with SMTP id g4mr2721112eea.96.1332744961968; Sun, 25 Mar 2012 23:56:01 -0700 (PDT) Received: by 10.14.184.7 with HTTP; Sun, 25 Mar 2012 23:56:01 -0700 (PDT) In-Reply-To: <4F6F09FE.7080506@gmail.com> References: <4F6F09FE.7080506@gmail.com> Date: Mon, 26 Mar 2012 12:26:01 +0530 Message-ID: From: R J To: George Shuklin Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] CentOS 6.X balloon issue [ XCP 1.5 / CentOS6 Bug ] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2032883644609279915==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2032883644609279915== Content-Type: multipart/alternative; boundary=bcaec52be65f08cb2404bc1fde3a --bcaec52be65f08cb2404bc1fde3a Content-Type: text/plain; charset=ISO-8859-1 On Sun, Mar 25, 2012 at 5:35 PM, George Shuklin wrote: > Heh, I've reported that stuff many times, until it was fixed in recent > kernels (about 3.1 or 3.2). > > No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP > toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse > f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen and so on). > > > Oh ! Do you have any URL so that I can track for this bug update ? And till the time this BUG gets resolved, how do I obtain a 2.6.32-xen ? I'm little familiar with Kernel Compilations but not too much. I would appreciate if you can guide me. > > On 24.03.2012 17:06, R J wrote: > > Hello List, > > On XCP1.5 ballooning of CentOS6.X does not work correctly. > The DomU can be ballooned up only till its start_target_mem and seems to > disobey the static max. > > For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine > between 256MB to 4GB but it cant go beyond 4GB though it has static max as > 16GB. > > I can confirm same issue on XCP1.1, so it might be something only with > CentOS6. > > - RJ > > > _______________________________________________ > 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 > > --bcaec52be65f08cb2404bc1fde3a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Sun, Mar 25, 2012 at 5:35 PM, George = Shuklin <g= eorge.shuklin@gmail.com> wrote:
=20 =20 =20
Heh, I've reported that stuff many times, until it was fixed in recent kernels (about 3.1 or 3.2).

No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen=A0 and so on).



Oh ! Do you have any URL so= that I can track for this bug update ?
And till the time this BUG gets = resolved, how do I obtain a 2.6.32-xen ?

I'm little familiar wit= h Kernel Compilations but not too much. I would appreciate if you can guide= me.



On 24.03.2012 17:06, R J wrote:
Hello List= ,

On XCP1.5 ballooning of CentOS6.X does not work correctly.
The DomU can be ballooned up only till its start_target_mem and seems to disobey the static max.

For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyond 4GB though it has static max as 16GB.

I can confirm same issue on XCP1.1, so it might be something only with CentOS6.

- RJ


_______________________________________________
xen-api mailing list
xen-api@lists.xe=
n.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


--bcaec52be65f08cb2404bc1fde3a-- --===============2032883644609279915== 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 --===============2032883644609279915==-- From xen-api-bounces@lists.xen.org Mon Mar 26 09:10:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 09:10:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC5ws-0003mm-Az; Mon, 26 Mar 2012 09:10:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC5wr-0003mV-0w for xen-api@lists.xen.org; Mon, 26 Mar 2012 09:10:45 +0000 Received: from [85.158.138.51:22957] by server-4.bemta-3.messagelabs.com id 52/06-16467-492307F4; Mon, 26 Mar 2012 09:10:44 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1332753043!19332042!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10553 invoked from network); 26 Mar 2012 09:10:43 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 09:10:43 -0000 Received: by bkcjg9 with SMTP id jg9so4696646bkc.32 for ; Mon, 26 Mar 2012 02:10:42 -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=QEOEmzsc6S316AF3dn6kNN7U4YnyR3oGQwIJykdtQKM=; b=Z0Qylq63gNNxmRWRE8IhWO1bzZlR8dt2kgF6nNuLhYzqGX0fWrz5EqU7yveRaBtii2 oT1Jpx6b9s4JWok/8EfchaBL8WWfp41BR3Ze8yVMya3DIrvfcE9gajtRT8bzHTyXYbPv 52y264RiofuVzuowM9r603LfhU+jH7rwynjlPvRn6P96g6SURouOFTGU4q0Z7yZCFMNt saXKb9jdhoccvk4QSbiXCW9VfNiMO/xa7pwq2sNoekjyZmoCspQZj2xrqq+FQ0Z4hE4G NUhbKITsDX5aPflrhngjcbpoGVXbBfmdrzCOb6kv48GtSAaUvNuxYTKViAIoxr3LcuRw a2+w== Received: by 10.204.152.27 with SMTP id e27mr7991700bkw.55.1332753042790; Mon, 26 Mar 2012 02:10:42 -0700 (PDT) Received: from [172.16.25.10] ([176.251.82.166]) by mx.google.com with ESMTPS id z17sm22404005bkw.12.2012.03.26.02.10.40 (version=SSLv3 cipher=OTHER); Mon, 26 Mar 2012 02:10:41 -0700 (PDT) Message-ID: <4F70328E.3090601@xen.org> Date: Mon, 26 Mar 2012 10:10:38 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-devel@devel.xen.org, xen-arm@lists.xen.org, xen-api@lists.xen.org Subject: [Xen-API] Xen Document Day Today : IRC #xendocday X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Discussion of API issues surrounding Xen 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 For more info, see http://wiki.xen.org/wiki/Xen_Document_Days _______________________________________________ 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 26 09:10:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 09:10:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC5ws-0003mm-Az; Mon, 26 Mar 2012 09:10:46 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC5wr-0003mV-0w for xen-api@lists.xen.org; Mon, 26 Mar 2012 09:10:45 +0000 Received: from [85.158.138.51:22957] by server-4.bemta-3.messagelabs.com id 52/06-16467-492307F4; Mon, 26 Mar 2012 09:10:44 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1332753043!19332042!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10553 invoked from network); 26 Mar 2012 09:10:43 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 09:10:43 -0000 Received: by bkcjg9 with SMTP id jg9so4696646bkc.32 for ; Mon, 26 Mar 2012 02:10:42 -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=QEOEmzsc6S316AF3dn6kNN7U4YnyR3oGQwIJykdtQKM=; b=Z0Qylq63gNNxmRWRE8IhWO1bzZlR8dt2kgF6nNuLhYzqGX0fWrz5EqU7yveRaBtii2 oT1Jpx6b9s4JWok/8EfchaBL8WWfp41BR3Ze8yVMya3DIrvfcE9gajtRT8bzHTyXYbPv 52y264RiofuVzuowM9r603LfhU+jH7rwynjlPvRn6P96g6SURouOFTGU4q0Z7yZCFMNt saXKb9jdhoccvk4QSbiXCW9VfNiMO/xa7pwq2sNoekjyZmoCspQZj2xrqq+FQ0Z4hE4G NUhbKITsDX5aPflrhngjcbpoGVXbBfmdrzCOb6kv48GtSAaUvNuxYTKViAIoxr3LcuRw a2+w== Received: by 10.204.152.27 with SMTP id e27mr7991700bkw.55.1332753042790; Mon, 26 Mar 2012 02:10:42 -0700 (PDT) Received: from [172.16.25.10] ([176.251.82.166]) by mx.google.com with ESMTPS id z17sm22404005bkw.12.2012.03.26.02.10.40 (version=SSLv3 cipher=OTHER); Mon, 26 Mar 2012 02:10:41 -0700 (PDT) Message-ID: <4F70328E.3090601@xen.org> Date: Mon, 26 Mar 2012 10:10:38 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-devel@devel.xen.org, xen-arm@lists.xen.org, xen-api@lists.xen.org Subject: [Xen-API] Xen Document Day Today : IRC #xendocday X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Discussion of API issues surrounding Xen 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 For more info, see http://wiki.xen.org/wiki/Xen_Document_Days _______________________________________________ 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 26 11:17:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 11:17:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC7v8-00075O-Er; Mon, 26 Mar 2012 11:17:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC7v6-00075J-2a for xen-api@lists.xen.org; Mon, 26 Mar 2012 11:17:04 +0000 Received: from [85.158.138.51:13901] by server-11.bemta-3.messagelabs.com id 2A/B4-12049-F20507F4; Mon, 26 Mar 2012 11:17:03 +0000 X-Env-Sender: taglio@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1332760619!19356739!1 X-Originating-IP: [209.85.161.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiBicC5ibG9 nc3BvdC5jb20p\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28366 invoked from network); 26 Mar 2012 11:17:00 -0000 Received: from mail-gx0-f173.google.com (HELO mail-gx0-f173.google.com) (209.85.161.173) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 11:17:00 -0000 Received: by ggnp2 with SMTP id p2so241353ggn.32 for ; Mon, 26 Mar 2012 04:16:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=TrxGjHIgVxV5fbGwq64JKoK47QfiycdyDJTM6AsMQZw=; b=N/XWXavovgE3Er9TrbAQ9zgB3MKfyD/Z586MkGVNxoPTD8H6z+NUSbnpBGOsc9qTmm aaHV3QrwJzB1smgxeV3Iemkpb1JdQd1VPMhKKTa2aBgCSrq1DoVKNcYvjUM86GaV29NG UhHBGFHAhfD7Vc9wyG+gUcrO7WdTePK+Cv/b9ZstJT3RRaqcvoRDi0gPhWz/fhPOuMVL J4A6cnckZGQKlFcKhcnugN0AYns2WiQgvsTuMiK2n25nUMLv5Jd+DouUBBIh4t64hKGa folRdTOsAUY+Zmz3UFN3uj/Ku5aVhbD7JfnRTNr9CThkVgx81Kbq7S6c1/+EfRNVnBk+ 16QA== Received: by 10.236.170.193 with SMTP id p41mr13376580yhl.15.1332760618939; Mon, 26 Mar 2012 04:16:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.131.1 with HTTP; Mon, 26 Mar 2012 04:16:17 -0700 (PDT) From: Riccardo Giuntoli Date: Mon, 26 Mar 2012 13:16:17 +0200 Message-ID: To: xen-api@lists.xen.org Content-Type: multipart/mixed; boundary=20cf305e21b14336e804bc238309 Subject: [Xen-API] XCP advanced networking X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --20cf305e21b14336e804bc238309 Content-Type: multipart/alternative; boundary=20cf305e21b14336e404bc238307 --20cf305e21b14336e404bc238307 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello there i'm Riccardo Giuntoli writing from Spain, i'm setting up a Precise Pangoline dom0 machine, using the directives of Project Kronos like i've found on http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution. All went ok and with simple networking i've created and started correctly a domU ubuntu 10.04 LTS machine. Now i've set up this network configuration: http://4.bp.blogspot.com/-PYpCkbfX40g/TzWWxcSd8SI/AAAAAAAAASw/iUIaK74Tlm8/s= 1600/Linux+vSwitch+Configuration.png All the configuration is done at "debian level" using /etc/network/interfaces as you can see in the attachment. Now when i try to start my lucid lynx VM that was attached to xenbr0 i've got this error: "Cannot plug VIF". This seems to be good cause i don't add any pif (can i add bridges like pif or only ethernet physical devices?). I've tried to add my new interfaces BUT i cannot do it. Please tell me, is possible do this???? Can i manage networking with debian scripts and then use the interfaces with xe ????? Best Regards, --=20 Name: Riccardo Giuntoli Email: taglio@gmail.com Location: Canyelles, BCN, Espa=C3=B1a PGP Key: 0x67123739 PGP Fingerprint: CE75 16B5 D855 842FAB54 FB5C DDC6 4640 6712 3739 Key server: hkp://wwwkeys.eu.pgp.net --20cf305e21b14336e404bc238307 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello there i'm Riccardo Giuntoli writing from Spain,

i'm se= tting up a Precise Pangoline dom0 machine, using the directives of Project = Kronos like i've found on http://wiki.xen.org/wiki/XCP_toolstack= _on_a_Debian-based_distribution.

All went ok and with simple networking i've created and started cor= rectly a domU ubuntu 10.04 LTS machine.

Now i've set up this ne= twork configuration:

http://4.bp.blogspot.com/-PYpCkbfX40g/TzWWxcSd8SI/AAAAAAAAASw/iUIaK74Tlm= 8/s1600/Linux+vSwitch+Configuration.png

All the configuration is done at "debian level" using /etc/ne= twork/interfaces as you can see in the attachment.

Now when i try t= o start my lucid lynx VM that was attached to xenbr0 i've got this erro= r: "Cannot plug VIF".

This seems to be good cause i don't add any pif (can i add bridges = like pif or only ethernet physical devices?).

I've tried to add = my new interfaces BUT i cannot do it.

Please tell me, is possible do= this???? Can i manage networking with debian scripts and then use the inte= rfaces with xe ?????

Best Regards,


--
Name: Riccardo Giuntoli
Email: taglio@gmail.com
Lo= cation: Canyelles, BCN, Espa=C3=B1a
PGP Key: 0x67123739
PGP Fingerpri= nt: CE75 16B5 D855 842FAB54 FB5C DDC6 4640 6712 3739
Key server: hkp://w= wwkeys.eu.pgp.net
--20cf305e21b14336e404bc238307-- --20cf305e21b14336e804bc238309 Content-Type: application/octet-stream; name=interfaces Content-Disposition: attachment; filename=interfaces Content-Transfer-Encoding: base64 X-Attachment-Id: f_h09f06s60 YXV0byBsbwppZmFjZSBsbyBpbmV0IGxvb3BiYWNrCgphdXRvIGV0aDAKaWZhY2UgZXRoMCBpbmV0 IG1hbnVhbAoJcHJlLXVwIGlmY29uZmlnICRJRkFDRSB1cAoJcG9zdC1kb3duIGlmY29uZmlnICRJ RkFDRSBkb3duCgphdXRvIGV0aDEKaWZhY2UgZXRoMSBpbmV0IG1hbnVhbAoJcHJlLXVwIGlmY29u ZmlnICRJRkFDRSB1cAoJcG9zdC1kb3duIGlmY29uZmlnICRJRkFDRSBkb3duCgphdXRvIGJvbmQw CmlmYWNlIGJvbmQwIGluZXQgbWFudWFsCglwcmUtdXAgbW9kcHJvYmUgYm9uZGluZyBtb2RlPTQg bWlpbW9uPTEwMCB4bWl0X2hhc2hfcG9saWN5PTIgbGFjcF9yYXRlPTAKCXByZS11cCBpZmNvbmZp ZyAkSUZBQ0UgdXAKCXBvc3QtdXAgaWZlbnNsYXZlIGJvbmQwIGV0aDAgZXRoMQoJcHJlLWRvd24g aWZlbnNsYXZlIC1kIGJvbmQwIGV0aDAgZXRoMQoJcG9zdC1kb3duIGlmY29uZmlnICRJRkFDRSBk b3duCgphdXRvIGJvbmQwLjEwCmlmYWNlIGJvbmQwLjEwIGluZXQgbWFudWFsCgl2bGFuX3Jhd19k ZXZpY2UgYm9uZDAKCXByZS11cCBpZmNvbmZpZyAkSUZBQ0UgdXAKCXBvc3QtZG93biBpZmNvbmZp ZyAkSUZBQ0UgZG93bgoKYXV0byBib25kMC4yMDAKaWZhY2UgYm9uZDAuMjAwIGluZXQgbWFudWFs CiAgICAgICAgdmxhbl9yYXdfZGV2aWNlIGJvbmQwCiAgICAgICAgcHJlLXVwIGlmY29uZmlnICRJ RkFDRSB1cAoJcG9zdC1kb3duIGlmY29uZmlnICRJRkFDRSBkb3duCgphdXRvIGJvbmQwLjIwMQpp ZmFjZSBib25kMC4yMDEgaW5ldCBtYW51YWwKCXZsYW5fcmF3X2RldmljZSBib25kMAogICAgICAg IHByZS11cCBpZmNvbmZpZyAkSUZBQ0UgdXAKCXBvc3QtZG93biBpZmNvbmZpZyAkSUZBQ0UgZG93 bgoKYXV0byB4ZW5icjAKaWZhY2UgeGVuYnIwIGluZXQgc3RhdGljCglhZGRyZXNzIDE5Mi4xNjgu MTAuMjAwCgluZXRtYXNrIDI1NS4yNTUuMjU1LjAKCWdhdGV3YXkgMTkyLjE2OC4xMC4xCglkbnMt bmFtZXNlcnZlcnMgMTkyLjE2OC4xMC4xCglkbnMtZG9tYWluIHJlZHl0ZWwubmV0CgkjcHJlLXVw IGJyY3RsIGFkZGJyIHhlbmJyMAoJcHJlLXVwIGJyY3RsIGFkZGlmIHhlbmJyMCBib25kMC4xMAoJ cG9zdC1kb3duIGJyY3RsIGRlbGlmIHhlbmJyMCBib25kMC4xMAoJcG9zdC1kb3duIGlmY29uZmln IHhlbmJyMCBkb3duCglwb3N0LWRvd24gYnJjdGwgZGVsYnIgeGVuYnIwCgphdXRvIHhlbmJyLVNS VgppZmFjZSB4ZW5ici1TUlYgaW5ldCBtYW51YWwKCXByZS11cCBicmN0bCBhZGRiciB4ZW5ici1T UlYKICAgICAgICBwcmUtdXAgYnJjdGwgYWRkaWYgeGVuYnItU1JWIGJvbmQwLjIwMAoJcHJlLXVw IGlmY29uZmlnICRJRkFDRSB1cAogICAgICAgIHBvc3QtZG93biBicmN0bCBkZWxpZiB4ZW5ici1T UlYgYm9uZDAuMjAwCiAgICAgICAgcG9zdC1kb3duIGlmY29uZmlnIHhlbmJyLVNSViBkb3duCiAg ICAgICAgcG9zdC1kb3duIGJyY3RsIGRlbGJyIHhlbmJyLVNSVgoJcG9zdC1kb3duIGlmY29uZmln ICRJRkFDRSBkb3duCgphdXRvIHhlbmJyLURNWgppZmFjZSB4ZW5ici1ETVogaW5ldCBtYW51YWwK CXByZS11cCBicmN0bCBhZGRiciB4ZW5ici1ETVoKICAgICAgICBwcmUtdXAgYnJjdGwgYWRkaWYg eGVuYnItRE1aIGJvbmQwLjIwMQoJcHJlLXVwIGlmY29uZmlnICRJRkFDRSB1cAogICAgICAgIHBv c3QtZG93biBicmN0bCBkZWxpZiB4ZW5ici1ETVogYm9uZDAuMjAxCiAgICAgICAgcG9zdC1kb3du IGlmY29uZmlnIHhlbmJyLURNWiBkb3duCiAgICAgICAgcG9zdC1kb3duIGJyY3RsIGRlbGJyIHhl bmJyLURNWgoJcG9zdC1kb3duIGlmY29uZmlnICRJRkFDRSBkb3duCgo= --20cf305e21b14336e804bc238309 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 --20cf305e21b14336e804bc238309-- From xen-api-bounces@lists.xen.org Mon Mar 26 11:17:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 11:17:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC7v8-00075O-Er; Mon, 26 Mar 2012 11:17:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC7v6-00075J-2a for xen-api@lists.xen.org; Mon, 26 Mar 2012 11:17:04 +0000 Received: from [85.158.138.51:13901] by server-11.bemta-3.messagelabs.com id 2A/B4-12049-F20507F4; Mon, 26 Mar 2012 11:17:03 +0000 X-Env-Sender: taglio@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1332760619!19356739!1 X-Originating-IP: [209.85.161.173] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiBicC5ibG9 nc3BvdC5jb20p\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28366 invoked from network); 26 Mar 2012 11:17:00 -0000 Received: from mail-gx0-f173.google.com (HELO mail-gx0-f173.google.com) (209.85.161.173) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 11:17:00 -0000 Received: by ggnp2 with SMTP id p2so241353ggn.32 for ; Mon, 26 Mar 2012 04:16:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=TrxGjHIgVxV5fbGwq64JKoK47QfiycdyDJTM6AsMQZw=; b=N/XWXavovgE3Er9TrbAQ9zgB3MKfyD/Z586MkGVNxoPTD8H6z+NUSbnpBGOsc9qTmm aaHV3QrwJzB1smgxeV3Iemkpb1JdQd1VPMhKKTa2aBgCSrq1DoVKNcYvjUM86GaV29NG UhHBGFHAhfD7Vc9wyG+gUcrO7WdTePK+Cv/b9ZstJT3RRaqcvoRDi0gPhWz/fhPOuMVL J4A6cnckZGQKlFcKhcnugN0AYns2WiQgvsTuMiK2n25nUMLv5Jd+DouUBBIh4t64hKGa folRdTOsAUY+Zmz3UFN3uj/Ku5aVhbD7JfnRTNr9CThkVgx81Kbq7S6c1/+EfRNVnBk+ 16QA== Received: by 10.236.170.193 with SMTP id p41mr13376580yhl.15.1332760618939; Mon, 26 Mar 2012 04:16:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.131.1 with HTTP; Mon, 26 Mar 2012 04:16:17 -0700 (PDT) From: Riccardo Giuntoli Date: Mon, 26 Mar 2012 13:16:17 +0200 Message-ID: To: xen-api@lists.xen.org Content-Type: multipart/mixed; boundary=20cf305e21b14336e804bc238309 Subject: [Xen-API] XCP advanced networking X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --20cf305e21b14336e804bc238309 Content-Type: multipart/alternative; boundary=20cf305e21b14336e404bc238307 --20cf305e21b14336e404bc238307 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello there i'm Riccardo Giuntoli writing from Spain, i'm setting up a Precise Pangoline dom0 machine, using the directives of Project Kronos like i've found on http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution. All went ok and with simple networking i've created and started correctly a domU ubuntu 10.04 LTS machine. Now i've set up this network configuration: http://4.bp.blogspot.com/-PYpCkbfX40g/TzWWxcSd8SI/AAAAAAAAASw/iUIaK74Tlm8/s= 1600/Linux+vSwitch+Configuration.png All the configuration is done at "debian level" using /etc/network/interfaces as you can see in the attachment. Now when i try to start my lucid lynx VM that was attached to xenbr0 i've got this error: "Cannot plug VIF". This seems to be good cause i don't add any pif (can i add bridges like pif or only ethernet physical devices?). I've tried to add my new interfaces BUT i cannot do it. Please tell me, is possible do this???? Can i manage networking with debian scripts and then use the interfaces with xe ????? Best Regards, --=20 Name: Riccardo Giuntoli Email: taglio@gmail.com Location: Canyelles, BCN, Espa=C3=B1a PGP Key: 0x67123739 PGP Fingerprint: CE75 16B5 D855 842FAB54 FB5C DDC6 4640 6712 3739 Key server: hkp://wwwkeys.eu.pgp.net --20cf305e21b14336e404bc238307 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello there i'm Riccardo Giuntoli writing from Spain,

i'm se= tting up a Precise Pangoline dom0 machine, using the directives of Project = Kronos like i've found on http://wiki.xen.org/wiki/XCP_toolstack= _on_a_Debian-based_distribution.

All went ok and with simple networking i've created and started cor= rectly a domU ubuntu 10.04 LTS machine.

Now i've set up this ne= twork configuration:

http://4.bp.blogspot.com/-PYpCkbfX40g/TzWWxcSd8SI/AAAAAAAAASw/iUIaK74Tlm= 8/s1600/Linux+vSwitch+Configuration.png

All the configuration is done at "debian level" using /etc/ne= twork/interfaces as you can see in the attachment.

Now when i try t= o start my lucid lynx VM that was attached to xenbr0 i've got this erro= r: "Cannot plug VIF".

This seems to be good cause i don't add any pif (can i add bridges = like pif or only ethernet physical devices?).

I've tried to add = my new interfaces BUT i cannot do it.

Please tell me, is possible do= this???? Can i manage networking with debian scripts and then use the inte= rfaces with xe ?????

Best Regards,


--
Name: Riccardo Giuntoli
Email: taglio@gmail.com
Lo= cation: Canyelles, BCN, Espa=C3=B1a
PGP Key: 0x67123739
PGP Fingerpri= nt: CE75 16B5 D855 842FAB54 FB5C DDC6 4640 6712 3739
Key server: hkp://w= wwkeys.eu.pgp.net
--20cf305e21b14336e404bc238307-- --20cf305e21b14336e804bc238309 Content-Type: application/octet-stream; name=interfaces Content-Disposition: attachment; filename=interfaces Content-Transfer-Encoding: base64 X-Attachment-Id: f_h09f06s60 YXV0byBsbwppZmFjZSBsbyBpbmV0IGxvb3BiYWNrCgphdXRvIGV0aDAKaWZhY2UgZXRoMCBpbmV0 IG1hbnVhbAoJcHJlLXVwIGlmY29uZmlnICRJRkFDRSB1cAoJcG9zdC1kb3duIGlmY29uZmlnICRJ RkFDRSBkb3duCgphdXRvIGV0aDEKaWZhY2UgZXRoMSBpbmV0IG1hbnVhbAoJcHJlLXVwIGlmY29u ZmlnICRJRkFDRSB1cAoJcG9zdC1kb3duIGlmY29uZmlnICRJRkFDRSBkb3duCgphdXRvIGJvbmQw CmlmYWNlIGJvbmQwIGluZXQgbWFudWFsCglwcmUtdXAgbW9kcHJvYmUgYm9uZGluZyBtb2RlPTQg bWlpbW9uPTEwMCB4bWl0X2hhc2hfcG9saWN5PTIgbGFjcF9yYXRlPTAKCXByZS11cCBpZmNvbmZp ZyAkSUZBQ0UgdXAKCXBvc3QtdXAgaWZlbnNsYXZlIGJvbmQwIGV0aDAgZXRoMQoJcHJlLWRvd24g aWZlbnNsYXZlIC1kIGJvbmQwIGV0aDAgZXRoMQoJcG9zdC1kb3duIGlmY29uZmlnICRJRkFDRSBk b3duCgphdXRvIGJvbmQwLjEwCmlmYWNlIGJvbmQwLjEwIGluZXQgbWFudWFsCgl2bGFuX3Jhd19k ZXZpY2UgYm9uZDAKCXByZS11cCBpZmNvbmZpZyAkSUZBQ0UgdXAKCXBvc3QtZG93biBpZmNvbmZp ZyAkSUZBQ0UgZG93bgoKYXV0byBib25kMC4yMDAKaWZhY2UgYm9uZDAuMjAwIGluZXQgbWFudWFs CiAgICAgICAgdmxhbl9yYXdfZGV2aWNlIGJvbmQwCiAgICAgICAgcHJlLXVwIGlmY29uZmlnICRJ RkFDRSB1cAoJcG9zdC1kb3duIGlmY29uZmlnICRJRkFDRSBkb3duCgphdXRvIGJvbmQwLjIwMQpp ZmFjZSBib25kMC4yMDEgaW5ldCBtYW51YWwKCXZsYW5fcmF3X2RldmljZSBib25kMAogICAgICAg IHByZS11cCBpZmNvbmZpZyAkSUZBQ0UgdXAKCXBvc3QtZG93biBpZmNvbmZpZyAkSUZBQ0UgZG93 bgoKYXV0byB4ZW5icjAKaWZhY2UgeGVuYnIwIGluZXQgc3RhdGljCglhZGRyZXNzIDE5Mi4xNjgu MTAuMjAwCgluZXRtYXNrIDI1NS4yNTUuMjU1LjAKCWdhdGV3YXkgMTkyLjE2OC4xMC4xCglkbnMt bmFtZXNlcnZlcnMgMTkyLjE2OC4xMC4xCglkbnMtZG9tYWluIHJlZHl0ZWwubmV0CgkjcHJlLXVw IGJyY3RsIGFkZGJyIHhlbmJyMAoJcHJlLXVwIGJyY3RsIGFkZGlmIHhlbmJyMCBib25kMC4xMAoJ cG9zdC1kb3duIGJyY3RsIGRlbGlmIHhlbmJyMCBib25kMC4xMAoJcG9zdC1kb3duIGlmY29uZmln IHhlbmJyMCBkb3duCglwb3N0LWRvd24gYnJjdGwgZGVsYnIgeGVuYnIwCgphdXRvIHhlbmJyLVNS VgppZmFjZSB4ZW5ici1TUlYgaW5ldCBtYW51YWwKCXByZS11cCBicmN0bCBhZGRiciB4ZW5ici1T UlYKICAgICAgICBwcmUtdXAgYnJjdGwgYWRkaWYgeGVuYnItU1JWIGJvbmQwLjIwMAoJcHJlLXVw IGlmY29uZmlnICRJRkFDRSB1cAogICAgICAgIHBvc3QtZG93biBicmN0bCBkZWxpZiB4ZW5ici1T UlYgYm9uZDAuMjAwCiAgICAgICAgcG9zdC1kb3duIGlmY29uZmlnIHhlbmJyLVNSViBkb3duCiAg ICAgICAgcG9zdC1kb3duIGJyY3RsIGRlbGJyIHhlbmJyLVNSVgoJcG9zdC1kb3duIGlmY29uZmln ICRJRkFDRSBkb3duCgphdXRvIHhlbmJyLURNWgppZmFjZSB4ZW5ici1ETVogaW5ldCBtYW51YWwK CXByZS11cCBicmN0bCBhZGRiciB4ZW5ici1ETVoKICAgICAgICBwcmUtdXAgYnJjdGwgYWRkaWYg eGVuYnItRE1aIGJvbmQwLjIwMQoJcHJlLXVwIGlmY29uZmlnICRJRkFDRSB1cAogICAgICAgIHBv c3QtZG93biBicmN0bCBkZWxpZiB4ZW5ici1ETVogYm9uZDAuMjAxCiAgICAgICAgcG9zdC1kb3du IGlmY29uZmlnIHhlbmJyLURNWiBkb3duCiAgICAgICAgcG9zdC1kb3duIGJyY3RsIGRlbGJyIHhl bmJyLURNWgoJcG9zdC1kb3duIGlmY29uZmlnICRJRkFDRSBkb3duCgo= --20cf305e21b14336e804bc238309 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 --20cf305e21b14336e804bc238309-- From xen-api-bounces@lists.xen.org Mon Mar 26 12:28:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 12:28:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC928-0001C5-TV; Mon, 26 Mar 2012 12:28:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC927-0001Bz-88 for xen-api@lists.xen.org; Mon, 26 Mar 2012 12:28:23 +0000 Received: from [193.109.254.147:4720] by server-7.bemta-14.messagelabs.com id ED/4C-01627-6E0607F4; Mon, 26 Mar 2012 12:28:22 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1332764901!2081030!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24769 invoked from network); 26 Mar 2012 12:28:21 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 12:28:21 -0000 Received: by lahe6 with SMTP id e6so4713138lah.32 for ; Mon, 26 Mar 2012 05:28:20 -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:cc:subject :references:in-reply-to:content-type; bh=ymqpi9qnsfESDoavG2CfnLNVfH5WYyK9OVOG+ss/HnU=; b=uMnzBc/IEeo9YPPt1osxWNtwtRP1MJm5vkCG/feolauAUMCr+b0RBLzGg/SFIXlBND r/lxE9FSIim/l0C6OFn1j6oxJwQT3AqTu4+OhnsiYdXEWyvZgO2XXpNeP8hRB2NCb9pQ D1mokJf71+U5vn8L+N3hRyN5erzNgueom+qVnrkfh1oPleuqbS3GmR122Qhadl4U14WX OYsxDM76M7JYWz08DMi2rjj5CbLqYJl6kVmr73dLy0PDiyrUeO5BL7SjuCTKvyGjMYC5 HyM+xIo2lzZjK0bS8K/R3KwSg8XrvHneoSgflCrFINFStrrk1AutA2FsjmsBYncOCglJ jQ7Q== Received: by 10.112.86.229 with SMTP id s5mr7919086lbz.0.1332764900734; Mon, 26 Mar 2012 05:28:20 -0700 (PDT) Received: from [192.168.40.44] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id gw17sm17024085lab.11.2012.03.26.05.28.16 (version=SSLv3 cipher=OTHER); Mon, 26 Mar 2012 05:28:19 -0700 (PDT) Message-ID: <4F7060DE.9080406@gmail.com> Date: Mon, 26 Mar 2012 16:28:14 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120309 Thunderbird/11.0 MIME-Version: 1.0 To: R J References: <4F6F09FE.7080506@gmail.com> In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] CentOS 6.X balloon issue [ XCP 1.5 / CentOS6 Bug ] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0331245581250024486==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0331245581250024486== Content-Type: multipart/alternative; boundary="------------090200070009040603020105" This is a multi-part message in MIME format. --------------090200070009040603020105 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 1) commit d7587810a40aee32ec6bdfc2d4bce7ba9fd03c3e in linux tree. 2) I don't think it's good idea to change kernel of CentOS: it contains lot of changes compare to vanilla 3) Actually, this is reason why we don't provide customers CentOS 6 in cloud. All other operating systems (including centos 5) works with -xen kernels or have it in distribution. 26.03.2012 10:56, R J wrote: > > > On Sun, Mar 25, 2012 at 5:35 PM, George Shuklin > > wrote: > > Heh, I've reported that stuff many times, until it was fixed in > recent kernels (about 3.1 or 3.2). > > No luck for 2.6.32. All older pv_ops kernels do have that issue > with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward > ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen and so on). > > > > Oh ! Do you have any URL so that I can track for this bug update ? > And till the time this BUG gets resolved, how do I obtain a 2.6.32-xen ? > > I'm little familiar with Kernel Compilations but not too much. I would > appreciate if you can guide me. > > > > On 24.03.2012 17:06, R J wrote: >> Hello List, >> >> On XCP1.5 ballooning of CentOS6.X does not work correctly. >> The DomU can be ballooned up only till its start_target_mem and >> seems to disobey the static max. >> >> For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning >> works fine between 256MB to 4GB but it cant go beyond 4GB though >> it has static max as 16GB. >> >> I can confirm same issue on XCP1.1, so it might be something only >> with CentOS6. >> >> - RJ >> >> >> _______________________________________________ >> 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 > > --------------090200070009040603020105 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 1) commit d7587810a40aee32ec6bdfc2d4bce7ba9fd03c3e in linux tree.
2) I don't think  it's good idea to change kernel of CentOS: it contains lot of changes compare to vanilla
3) Actually, this is reason why we don't provide customers CentOS 6 in cloud. All other operating systems (including centos 5) works with -xen kernels or have it in distribution.


26.03.2012 10:56, R J wrote:


On Sun, Mar 25, 2012 at 5:35 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Heh, I've reported that stuff many times, until it was fixed in recent kernels (about 3.1 or 3.2).

No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen  and so on).



Oh ! Do you have any URL so that I can track for this bug update ?
And till the time this BUG gets resolved, how do I obtain a 2.6.32-xen ?

I'm little familiar with Kernel Compilations but not too much. I would appreciate if you can guide me.



On 24.03.2012 17:06, R J wrote:
Hello List,

On XCP1.5 ballooning of CentOS6.X does not work correctly.
The DomU can be ballooned up only till its start_target_mem and seems to disobey the static max.

For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyond 4GB though it has static max as 16GB.

I can confirm same issue on XCP1.1, so it might be something only with CentOS6.

- RJ


_______________________________________________
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



--------------090200070009040603020105-- --===============0331245581250024486== 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 --===============0331245581250024486==-- From xen-api-bounces@lists.xen.org Mon Mar 26 12:28:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 12:28:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC928-0001C5-TV; Mon, 26 Mar 2012 12:28:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SC927-0001Bz-88 for xen-api@lists.xen.org; Mon, 26 Mar 2012 12:28:23 +0000 Received: from [193.109.254.147:4720] by server-7.bemta-14.messagelabs.com id ED/4C-01627-6E0607F4; Mon, 26 Mar 2012 12:28:22 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1332764901!2081030!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24769 invoked from network); 26 Mar 2012 12:28:21 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 12:28:21 -0000 Received: by lahe6 with SMTP id e6so4713138lah.32 for ; Mon, 26 Mar 2012 05:28:20 -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:cc:subject :references:in-reply-to:content-type; bh=ymqpi9qnsfESDoavG2CfnLNVfH5WYyK9OVOG+ss/HnU=; b=uMnzBc/IEeo9YPPt1osxWNtwtRP1MJm5vkCG/feolauAUMCr+b0RBLzGg/SFIXlBND r/lxE9FSIim/l0C6OFn1j6oxJwQT3AqTu4+OhnsiYdXEWyvZgO2XXpNeP8hRB2NCb9pQ D1mokJf71+U5vn8L+N3hRyN5erzNgueom+qVnrkfh1oPleuqbS3GmR122Qhadl4U14WX OYsxDM76M7JYWz08DMi2rjj5CbLqYJl6kVmr73dLy0PDiyrUeO5BL7SjuCTKvyGjMYC5 HyM+xIo2lzZjK0bS8K/R3KwSg8XrvHneoSgflCrFINFStrrk1AutA2FsjmsBYncOCglJ jQ7Q== Received: by 10.112.86.229 with SMTP id s5mr7919086lbz.0.1332764900734; Mon, 26 Mar 2012 05:28:20 -0700 (PDT) Received: from [192.168.40.44] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id gw17sm17024085lab.11.2012.03.26.05.28.16 (version=SSLv3 cipher=OTHER); Mon, 26 Mar 2012 05:28:19 -0700 (PDT) Message-ID: <4F7060DE.9080406@gmail.com> Date: Mon, 26 Mar 2012 16:28:14 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120309 Thunderbird/11.0 MIME-Version: 1.0 To: R J References: <4F6F09FE.7080506@gmail.com> In-Reply-To: Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] CentOS 6.X balloon issue [ XCP 1.5 / CentOS6 Bug ] X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0331245581250024486==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============0331245581250024486== Content-Type: multipart/alternative; boundary="------------090200070009040603020105" This is a multi-part message in MIME format. --------------090200070009040603020105 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 1) commit d7587810a40aee32ec6bdfc2d4bce7ba9fd03c3e in linux tree. 2) I don't think it's good idea to change kernel of CentOS: it contains lot of changes compare to vanilla 3) Actually, this is reason why we don't provide customers CentOS 6 in cloud. All other operating systems (including centos 5) works with -xen kernels or have it in distribution. 26.03.2012 10:56, R J wrote: > > > On Sun, Mar 25, 2012 at 5:35 PM, George Shuklin > > wrote: > > Heh, I've reported that stuff many times, until it was fixed in > recent kernels (about 3.1 or 3.2). > > No luck for 2.6.32. All older pv_ops kernels do have that issue > with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward > ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen and so on). > > > > Oh ! Do you have any URL so that I can track for this bug update ? > And till the time this BUG gets resolved, how do I obtain a 2.6.32-xen ? > > I'm little familiar with Kernel Compilations but not too much. I would > appreciate if you can guide me. > > > > On 24.03.2012 17:06, R J wrote: >> Hello List, >> >> On XCP1.5 ballooning of CentOS6.X does not work correctly. >> The DomU can be ballooned up only till its start_target_mem and >> seems to disobey the static max. >> >> For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning >> works fine between 256MB to 4GB but it cant go beyond 4GB though >> it has static max as 16GB. >> >> I can confirm same issue on XCP1.1, so it might be something only >> with CentOS6. >> >> - RJ >> >> >> _______________________________________________ >> 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 > > --------------090200070009040603020105 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 1) commit d7587810a40aee32ec6bdfc2d4bce7ba9fd03c3e in linux tree.
2) I don't think  it's good idea to change kernel of CentOS: it contains lot of changes compare to vanilla
3) Actually, this is reason why we don't provide customers CentOS 6 in cloud. All other operating systems (including centos 5) works with -xen kernels or have it in distribution.


26.03.2012 10:56, R J wrote:


On Sun, Mar 25, 2012 at 5:35 PM, George Shuklin <george.shuklin@gmail.com> wrote:
Heh, I've reported that stuff many times, until it was fixed in recent kernels (about 3.1 or 3.2).

No luck for 2.6.32. All older pv_ops kernels do have that issue with XCP toolstack. Use -xen kernels (like 2.6.18-xen, or forward ported from suse f.e. 2.6.34-xen, 2.6.37-xen, 3.1-xen  and so on).



Oh ! Do you have any URL so that I can track for this bug update ?
And till the time this BUG gets resolved, how do I obtain a 2.6.32-xen ?

I'm little familiar with Kernel Compilations but not too much. I would appreciate if you can guide me.



On 24.03.2012 17:06, R J wrote:
Hello List,

On XCP1.5 ballooning of CentOS6.X does not work correctly.
The DomU can be ballooned up only till its start_target_mem and seems to disobey the static max.

For e.g If I start a CentOS6 DomU with 4GB RAM then ballooning works fine between 256MB to 4GB but it cant go beyond 4GB though it has static max as 16GB.

I can confirm same issue on XCP1.1, so it might be something only with CentOS6.

- RJ


_______________________________________________
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



--------------090200070009040603020105-- --===============0331245581250024486== 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 --===============0331245581250024486==-- From xen-api-bounces@lists.xen.org Mon Mar 26 14:59:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 14:59:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCBOA-0005YO-8T; Mon, 26 Mar 2012 14:59:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCBO8-0005YJ-Kx for xen-api@lists.xensource.com; Mon, 26 Mar 2012 14:59:16 +0000 Received: from [85.158.138.51:60561] by server-3.bemta-3.messagelabs.com id 68/89-10665-344807F4; Mon, 26 Mar 2012 14:59:15 +0000 X-Env-Sender: todd.deshane.xen@gmail.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1332773953!19328103!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_10, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28498 invoked from network); 26 Mar 2012 14:59:15 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-3.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 14:59:15 -0000 Received: by iadj38 with SMTP id j38so10487973iad.30 for ; Mon, 26 Mar 2012 07:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=aUblKiBCVm4HpRE6yglRBO6kxku7DfAO4pnlYhPLAYo=; b=JNbbFFIjHikoqgJMfnPG1mJpVWl6H8SMH9uhdnv04oMpT9KTn40IiK/fmyqnvz2eiN WTV7L4gItN2QJROQf2IH3Flm+M0wCdKrlbmG2JIp0xA1HtXprjfscbLdGH4VH8vOZhB+ z+sQ9rlPh/r9LQ7norqR1EN6+nElGay/3sj0755AtIA9P6YhGW8zoG3ttosLOLePjI7G MUrkqk9/vI76C7igK/+qMYDuAiPDOOHs8q9QljlafnbvkZASSHf+PF91WgGGXmI/FNmE 2TEN8WifLIy7GSHoW57ol5GGf7hJe6UAQdS4Hdq++q8UeWAwYVYeq3+uGCWa/glcqNOJ UdAw== Received: by 10.50.197.132 with SMTP id iu4mr6863685igc.74.1332773953241; Mon, 26 Mar 2012 07:59:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.190.205 with HTTP; Mon, 26 Mar 2012 07:58:52 -0700 (PDT) In-Reply-To: References: From: Todd Deshane Date: Mon, 26 Mar 2012 10:58:52 -0400 X-Google-Sender-Auth: YIEDIbzneDfcuq2JkPSoaL6dtUw Message-ID: To: isha.tarte@esds.co.in Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Architecture of XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 adding back the list On Mon, Mar 26, 2012 at 10:34 AM, wrote: > Hello Todd, > > Thank you for taking time out to answer my queries. Information which you > gave was very useful. > I again have come up with some doubts which are: > > =A0Can you tell me when we (DOM 0) creates a VM what files it append into > it(VM). With XAPI, VMs are created from templates and the settings can be seen with the command xe vm-param-list. There are various xe commands that can be used to change these settings and add virtual devices, etc. http://docs.vmd.citrix.com/XenServer/4.0.1/reference/ch05.html > =A0Does each VM has XAPI in it? No. In current XCP/XenServer, XAPI runs as a service in dom0, but work is in progress to allow XAPI to run in a service domain. http://wiki.xen.org/wiki/Xenopsd > =A0XAPI & xapi are two different things? If yes can you please elaborate. > No. You may see XAPI talked about as a toolstack and also as a service, but its the same XAPI. Hope that helps. Cheers, Todd -- = Todd Deshane http://www.linkedin.com/in/deshantm http://blog.xen.org/ http://wiki.xen.org/ _______________________________________________ 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 26 14:59:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 26 Mar 2012 14:59:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCBOA-0005YO-8T; Mon, 26 Mar 2012 14:59:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCBO8-0005YJ-Kx for xen-api@lists.xensource.com; Mon, 26 Mar 2012 14:59:16 +0000 Received: from [85.158.138.51:60561] by server-3.bemta-3.messagelabs.com id 68/89-10665-344807F4; Mon, 26 Mar 2012 14:59:15 +0000 X-Env-Sender: todd.deshane.xen@gmail.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1332773953!19328103!1 X-Originating-IP: [209.85.210.171] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_10, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28498 invoked from network); 26 Mar 2012 14:59:15 -0000 Received: from mail-iy0-f171.google.com (HELO mail-iy0-f171.google.com) (209.85.210.171) by server-3.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 26 Mar 2012 14:59:15 -0000 Received: by iadj38 with SMTP id j38so10487973iad.30 for ; Mon, 26 Mar 2012 07:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=aUblKiBCVm4HpRE6yglRBO6kxku7DfAO4pnlYhPLAYo=; b=JNbbFFIjHikoqgJMfnPG1mJpVWl6H8SMH9uhdnv04oMpT9KTn40IiK/fmyqnvz2eiN WTV7L4gItN2QJROQf2IH3Flm+M0wCdKrlbmG2JIp0xA1HtXprjfscbLdGH4VH8vOZhB+ z+sQ9rlPh/r9LQ7norqR1EN6+nElGay/3sj0755AtIA9P6YhGW8zoG3ttosLOLePjI7G MUrkqk9/vI76C7igK/+qMYDuAiPDOOHs8q9QljlafnbvkZASSHf+PF91WgGGXmI/FNmE 2TEN8WifLIy7GSHoW57ol5GGf7hJe6UAQdS4Hdq++q8UeWAwYVYeq3+uGCWa/glcqNOJ UdAw== Received: by 10.50.197.132 with SMTP id iu4mr6863685igc.74.1332773953241; Mon, 26 Mar 2012 07:59:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.190.205 with HTTP; Mon, 26 Mar 2012 07:58:52 -0700 (PDT) In-Reply-To: References: From: Todd Deshane Date: Mon, 26 Mar 2012 10:58:52 -0400 X-Google-Sender-Auth: YIEDIbzneDfcuq2JkPSoaL6dtUw Message-ID: To: isha.tarte@esds.co.in Cc: xen-api@lists.xensource.com Subject: Re: [Xen-API] Architecture of XCP X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 adding back the list On Mon, Mar 26, 2012 at 10:34 AM, wrote: > Hello Todd, > > Thank you for taking time out to answer my queries. Information which you > gave was very useful. > I again have come up with some doubts which are: > > =A0Can you tell me when we (DOM 0) creates a VM what files it append into > it(VM). With XAPI, VMs are created from templates and the settings can be seen with the command xe vm-param-list. There are various xe commands that can be used to change these settings and add virtual devices, etc. http://docs.vmd.citrix.com/XenServer/4.0.1/reference/ch05.html > =A0Does each VM has XAPI in it? No. In current XCP/XenServer, XAPI runs as a service in dom0, but work is in progress to allow XAPI to run in a service domain. http://wiki.xen.org/wiki/Xenopsd > =A0XAPI & xapi are two different things? If yes can you please elaborate. > No. You may see XAPI talked about as a toolstack and also as a service, but its the same XAPI. Hope that helps. Cheers, Todd -- = Todd Deshane http://www.linkedin.com/in/deshantm http://blog.xen.org/ http://wiki.xen.org/ _______________________________________________ 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 27 13:09:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 27 Mar 2012 13:09:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCW9M-0003XA-JF; Tue, 27 Mar 2012 13:09:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCW9L-0003X4-Sc for xen-api@lists.xen.org; Tue, 27 Mar 2012 13:09:24 +0000 Received: from [193.109.254.147:37392] by server-7.bemta-14.messagelabs.com id 88/3D-01627-30CB17F4; Tue, 27 Mar 2012 13:09:23 +0000 X-Env-Sender: the.kazak@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1332853761!2246509!1 X-Originating-IP: [209.85.214.45] 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-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29785 invoked from network); 27 Mar 2012 13:09:21 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2012 13:09:21 -0000 Received: by bkcjg9 with SMTP id jg9so6004530bkc.32 for ; Tue, 27 Mar 2012 06:09:21 -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 :content-type; bh=7OY8ignA5P8Tn+gRNXAx5BhrELrTdk8ZRHhMNmui0FY=; b=ROhmnzLuwy60ta03x5ghgORc0ST97o+4bOhZb0+hZ3v/jtFjPkpxqTa/oviFFzZoKe fNzLMXJlGaI5t5kcNGmnfzHAvvdjZ7/X4slhXz9HGDF4nRF8l/eqHopQWkNjzqSAPcbV szlCaiLDZZyaSHt1oVaeOdAPxV9qilTMoD+um9nZjuSZntV/pW7UPriQ/2cLc5C3WGYj 7/gFAQ8njv0ZgkD738Q/Rq34i1vZADINUxRwLWHb7pxRWmbxQ4YW8EBgbMdfG4mS7G3g cDiBCAle4khQCKEC8OiC3+DfeCU3UJ7sEM+axsfvIsPDuLUWwQmeMm0OC0LTyvgIuhZ3 oWyw== Received: by 10.204.133.196 with SMTP id g4mr10345465bkt.0.1332853761101; Tue, 27 Mar 2012 06:09:21 -0700 (PDT) Received: from [212.50.0.54] (purple.varna.spnet.net. [212.50.0.54]) by mx.google.com with ESMTPS id u14sm39112966bkp.2.2012.03.27.06.09.19 (version=SSLv3 cipher=OTHER); Tue, 27 Mar 2012 06:09:20 -0700 (PDT) Message-ID: <4F71BB8F.6090504@gmail.com> Date: Tue, 27 Mar 2012 16:07:27 +0300 From: Dimitar Kazakov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.28) Gecko/20120313 Thunderbird/3.1.20 MIME-Version: 1.0 To: xen-api@lists.xen.org Content-Type: multipart/mixed; boundary="------------080506070801040706070409" Subject: [Xen-API] VDI.create failure on ext local SR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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. --------------080506070801040706070409 Content-Type: multipart/alternative; boundary="------------090902070600030208010108" --------------090902070600030208010108 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, Have problem with creating VDI on local SR type=ext xe vdi-create sr-uuid=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab name-label=test sharable=false type=user virtual-size=100MiB Error code: SR_BACKEND_FAILURE_78 Error parameters: , VDI Creation failed [opterr=error 127], xapi: [20120325T14:50:58.472Z| info|hyperion|60835 UNIX /var/lib/xcp/xapi|VDI.create R:e2cdeb6b186d|audit] ('trackid=51bd7a4a8b299b312f6f958f5d370a1c' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ]' 'API' 'VDI.create' (('name_label' 'test' '' '') ('name_description' '' '' '') ('SR' 'Local storage' 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab' 'OpaqueRef:676707ab-b93a-6e91-8824-dce326928452'))) There is no such problem when create VDI on Local SR type=lvhd. Both tests are made with sr created on the same physical partition xe sr-create host-uuid=5fbdc200-4165-f850-3e7a-2ab1d00a2221 content-type=user type=ext device-config:device=/dev/sda3 shared=false name-label="Local storage" name-description="Local storage" sm-config:allocation=thin and xe sr-create host-uuid=5fbdc200-4165-f850-3e7a-2ab1d00a2221 content-type=user type=lvhd device-config:device=/dev/sda3 shared=false name-label="Local storage" name-description="Local storage" sm-config:allocation=thin There is no problem creating VDI on lvhd local SR, but when try same operation on ext local SR it always failed. Ext partition is mounted properly and accessible RW through /run/sr-mount/{sr uuid} mount point. Xen version 4.1.2 (Debian 4.1.2-2.1) XCP-XAPI toolstack 1.3.2-4 (Kronos) Anyone managed to work around this problem ? Regards, Dimitar Kazakov --------------090902070600030208010108 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 
Hi,
Have problem with creating VDI on local SR type=ext
xe vdi-create sr-uuid=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab name-label=test sharable=false type=user virtual-size=100MiB
Error code: SR_BACKEND_FAILURE_78
Error parameters: , VDI Creation failed [opterr=error 127],

xapi: [20120325T14:50:58.472Z| info|hyperion|60835 UNIX /var/lib/xcp/xapi|VDI.create R:e2cdeb6b186d|audit] ('trackid=51bd7a4a8b299b312f6f958f5d370a1c' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127];  ]' 'API' 'VDI.create' (('name_label' 'test' '' '') ('name_description' '<value/>' '' '') ('SR' 'Local storage' 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab' 'OpaqueRef:676707ab-b93a-6e91-8824-dce326928452')))

There is no such problem when create VDI on Local SR type=lvhd. Both tests are made with sr created on the same physical partition
xe sr-create host-uuid=5fbdc200-4165-f850-3e7a-2ab1d00a2221 content-type=user type=ext device-config:device=/dev/sda3 shared=false name-label="Local storage" name-description="Local storage" sm-config:allocation=thin
and
xe sr-create host-uuid=5fbdc200-4165-f850-3e7a-2ab1d00a2221 content-type=user type=lvhd device-config:device=/dev/sda3 shared=false name-label="Local storage" name-description="Local storage" sm-config:allocation=thin

There is no problem creating VDI on lvhd local SR, but when try same operation on ext local SR it always failed.  Ext partition is mounted properly and accessible RW through /run/sr-mount/{sr uuid} mount point. 

Xen version 4.1.2 (Debian 4.1.2-2.1)
XCP-XAPI toolstack 1.3.2-4 (Kronos)

Anyone managed to work around this problem ?

Regards,
Dimitar Kazakov
--------------090902070600030208010108-- --------------080506070801040706070409 Content-Type: text/x-vcard; charset=utf-8; name="the_kazak.vcf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="the_kazak.vcf" YmVnaW46dmNhcmQNCmZuOkRpbWl0YXIgS2F6YWtvdiAoa0B6QGspDQpuOkthemFrb3Y7RGlt aXRhcg0Kb3JnOldlYlRvQ2xvdWQNCmFkcjo7OztWYXJuYTs7OTAwMDtCdWxnYXJpYQ0KZW1h aWw7aW50ZXJuZXQ6dGhlLmthemFrQGdtYWlsLmNvbQ0KdGVsO2hvbWU6KzM1OSAoNTIpIDkx MTExOQ0KdGVsO2NlbGw6KzM1OSAoODgpIDg1NTk5MDkNCngtbW96aWxsYS1odG1sOkZBTFNF DQp2ZXJzaW9uOjIuMQ0KZW5kOnZjYXJkDQoNCg== --------------080506070801040706070409 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 --------------080506070801040706070409-- From xen-api-bounces@lists.xen.org Tue Mar 27 13:09:33 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 27 Mar 2012 13:09:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCW9M-0003XA-JF; Tue, 27 Mar 2012 13:09:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCW9L-0003X4-Sc for xen-api@lists.xen.org; Tue, 27 Mar 2012 13:09:24 +0000 Received: from [193.109.254.147:37392] by server-7.bemta-14.messagelabs.com id 88/3D-01627-30CB17F4; Tue, 27 Mar 2012 13:09:23 +0000 X-Env-Sender: the.kazak@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1332853761!2246509!1 X-Originating-IP: [209.85.214.45] 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-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29785 invoked from network); 27 Mar 2012 13:09:21 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Mar 2012 13:09:21 -0000 Received: by bkcjg9 with SMTP id jg9so6004530bkc.32 for ; Tue, 27 Mar 2012 06:09:21 -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 :content-type; bh=7OY8ignA5P8Tn+gRNXAx5BhrELrTdk8ZRHhMNmui0FY=; b=ROhmnzLuwy60ta03x5ghgORc0ST97o+4bOhZb0+hZ3v/jtFjPkpxqTa/oviFFzZoKe fNzLMXJlGaI5t5kcNGmnfzHAvvdjZ7/X4slhXz9HGDF4nRF8l/eqHopQWkNjzqSAPcbV szlCaiLDZZyaSHt1oVaeOdAPxV9qilTMoD+um9nZjuSZntV/pW7UPriQ/2cLc5C3WGYj 7/gFAQ8njv0ZgkD738Q/Rq34i1vZADINUxRwLWHb7pxRWmbxQ4YW8EBgbMdfG4mS7G3g cDiBCAle4khQCKEC8OiC3+DfeCU3UJ7sEM+axsfvIsPDuLUWwQmeMm0OC0LTyvgIuhZ3 oWyw== Received: by 10.204.133.196 with SMTP id g4mr10345465bkt.0.1332853761101; Tue, 27 Mar 2012 06:09:21 -0700 (PDT) Received: from [212.50.0.54] (purple.varna.spnet.net. [212.50.0.54]) by mx.google.com with ESMTPS id u14sm39112966bkp.2.2012.03.27.06.09.19 (version=SSLv3 cipher=OTHER); Tue, 27 Mar 2012 06:09:20 -0700 (PDT) Message-ID: <4F71BB8F.6090504@gmail.com> Date: Tue, 27 Mar 2012 16:07:27 +0300 From: Dimitar Kazakov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.28) Gecko/20120313 Thunderbird/3.1.20 MIME-Version: 1.0 To: xen-api@lists.xen.org Content-Type: multipart/mixed; boundary="------------080506070801040706070409" Subject: [Xen-API] VDI.create failure on ext local SR X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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. --------------080506070801040706070409 Content-Type: multipart/alternative; boundary="------------090902070600030208010108" --------------090902070600030208010108 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, Have problem with creating VDI on local SR type=ext xe vdi-create sr-uuid=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab name-label=test sharable=false type=user virtual-size=100MiB Error code: SR_BACKEND_FAILURE_78 Error parameters: , VDI Creation failed [opterr=error 127], xapi: [20120325T14:50:58.472Z| info|hyperion|60835 UNIX /var/lib/xcp/xapi|VDI.create R:e2cdeb6b186d|audit] ('trackid=51bd7a4a8b299b312f6f958f5d370a1c' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ]' 'API' 'VDI.create' (('name_label' 'test' '' '') ('name_description' '' '' '') ('SR' 'Local storage' 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab' 'OpaqueRef:676707ab-b93a-6e91-8824-dce326928452'))) There is no such problem when create VDI on Local SR type=lvhd. Both tests are made with sr created on the same physical partition xe sr-create host-uuid=5fbdc200-4165-f850-3e7a-2ab1d00a2221 content-type=user type=ext device-config:device=/dev/sda3 shared=false name-label="Local storage" name-description="Local storage" sm-config:allocation=thin and xe sr-create host-uuid=5fbdc200-4165-f850-3e7a-2ab1d00a2221 content-type=user type=lvhd device-config:device=/dev/sda3 shared=false name-label="Local storage" name-description="Local storage" sm-config:allocation=thin There is no problem creating VDI on lvhd local SR, but when try same operation on ext local SR it always failed. Ext partition is mounted properly and accessible RW through /run/sr-mount/{sr uuid} mount point. Xen version 4.1.2 (Debian 4.1.2-2.1) XCP-XAPI toolstack 1.3.2-4 (Kronos) Anyone managed to work around this problem ? Regards, Dimitar Kazakov --------------090902070600030208010108 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 
Hi,
Have problem with creating VDI on local SR type=ext
xe vdi-create sr-uuid=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab name-label=test sharable=false type=user virtual-size=100MiB
Error code: SR_BACKEND_FAILURE_78
Error parameters: , VDI Creation failed [opterr=error 127],

xapi: [20120325T14:50:58.472Z| info|hyperion|60835 UNIX /var/lib/xcp/xapi|VDI.create R:e2cdeb6b186d|audit] ('trackid=51bd7a4a8b299b312f6f958f5d370a1c' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'ERROR:SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127];  ]' 'API' 'VDI.create' (('name_label' 'test' '' '') ('name_description' '<value/>' '' '') ('SR' 'Local storage' 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab' 'OpaqueRef:676707ab-b93a-6e91-8824-dce326928452')))

There is no such problem when create VDI on Local SR type=lvhd. Both tests are made with sr created on the same physical partition
xe sr-create host-uuid=5fbdc200-4165-f850-3e7a-2ab1d00a2221 content-type=user type=ext device-config:device=/dev/sda3 shared=false name-label="Local storage" name-description="Local storage" sm-config:allocation=thin
and
xe sr-create host-uuid=5fbdc200-4165-f850-3e7a-2ab1d00a2221 content-type=user type=lvhd device-config:device=/dev/sda3 shared=false name-label="Local storage" name-description="Local storage" sm-config:allocation=thin

There is no problem creating VDI on lvhd local SR, but when try same operation on ext local SR it always failed.  Ext partition is mounted properly and accessible RW through /run/sr-mount/{sr uuid} mount point. 

Xen version 4.1.2 (Debian 4.1.2-2.1)
XCP-XAPI toolstack 1.3.2-4 (Kronos)

Anyone managed to work around this problem ?

Regards,
Dimitar Kazakov
--------------090902070600030208010108-- --------------080506070801040706070409 Content-Type: text/x-vcard; charset=utf-8; name="the_kazak.vcf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="the_kazak.vcf" YmVnaW46dmNhcmQNCmZuOkRpbWl0YXIgS2F6YWtvdiAoa0B6QGspDQpuOkthemFrb3Y7RGlt aXRhcg0Kb3JnOldlYlRvQ2xvdWQNCmFkcjo7OztWYXJuYTs7OTAwMDtCdWxnYXJpYQ0KZW1h aWw7aW50ZXJuZXQ6dGhlLmthemFrQGdtYWlsLmNvbQ0KdGVsO2hvbWU6KzM1OSAoNTIpIDkx MTExOQ0KdGVsO2NlbGw6KzM1OSAoODgpIDg1NTk5MDkNCngtbW96aWxsYS1odG1sOkZBTFNF DQp2ZXJzaW9uOjIuMQ0KZW5kOnZjYXJkDQoNCg== --------------080506070801040706070409 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 --------------080506070801040706070409-- From xen-api-bounces@lists.xen.org Tue Mar 27 15:36:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 27 Mar 2012 15:36:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCYRo-000472-92; Tue, 27 Mar 2012 15:36:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCYRm-00046x-9S for xen-api@lists.xen.org; Tue, 27 Mar 2012 15:36:34 +0000 Received: from [85.158.143.99:49849] by server-3.bemta-4.messagelabs.com id 9C/B4-05853-18ED17F4; Tue, 27 Mar 2012 15:36:33 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-7.tower-216.messagelabs.com!1332862592!17705860!1 X-Originating-IP: [80.12.242.124] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2955 invoked from network); 27 Mar 2012 15:36:32 -0000 Received: from smtp02.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.124) by server-7.tower-216.messagelabs.com with SMTP; 27 Mar 2012 15:36:32 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d55 with ME id qfcX1i00R3zjds103fcXmy; Tue, 27 Mar 2012 17:36:32 +0200 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A37EA74529; Tue, 27 Mar 2012 17:36:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PdeXTpn7OQbp; Tue, 27 Mar 2012 17:36:31 +0200 (CEST) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 121887450E; Tue, 27 Mar 2012 17:36:31 +0200 (CEST) Message-ID: <4F71DE7E.5090704@tranquil-it-systems.fr> Date: Tue, 27 Mar 2012 17:36:30 +0200 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] coalescing and oomkiller X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi every one, I think I am experiencing the bug reference in CTX131673 = (http://support.citrix.com/article/CTX131673 oomkiller because of memory = leaks in vhd-util when coalescing). The servers experiencing the issue = are xcp 1.0.0-42052. Those servers are pool members with shared iscsi = storage. The advisory specify it applies to Xenserver 6. Can it be that it also = apply to XCP 1.0? The patch seems to come as source code. Can it be = compiled and applied to XCP as well? Thanks, Denis -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 27 15:36:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 27 Mar 2012 15:36:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCYRo-000472-92; Tue, 27 Mar 2012 15:36:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SCYRm-00046x-9S for xen-api@lists.xen.org; Tue, 27 Mar 2012 15:36:34 +0000 Received: from [85.158.143.99:49849] by server-3.bemta-4.messagelabs.com id 9C/B4-05853-18ED17F4; Tue, 27 Mar 2012 15:36:33 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-7.tower-216.messagelabs.com!1332862592!17705860!1 X-Originating-IP: [80.12.242.124] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2955 invoked from network); 27 Mar 2012 15:36:32 -0000 Received: from smtp02.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.124) by server-7.tower-216.messagelabs.com with SMTP; 27 Mar 2012 15:36:32 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d55 with ME id qfcX1i00R3zjds103fcXmy; Tue, 27 Mar 2012 17:36:32 +0200 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id A37EA74529; Tue, 27 Mar 2012 17:36:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at tranquilit.local Received: from srvzimbra.tranquilit.local ([127.0.0.1]) by localhost (srvzimbra.tranquilit.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PdeXTpn7OQbp; Tue, 27 Mar 2012 17:36:31 +0200 (CEST) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 121887450E; Tue, 27 Mar 2012 17:36:31 +0200 (CEST) Message-ID: <4F71DE7E.5090704@tranquil-it-systems.fr> Date: Tue, 27 Mar 2012 17:36:30 +0200 From: Denis Cardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] coalescing and oomkiller X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org Hi every one, I think I am experiencing the bug reference in CTX131673 = (http://support.citrix.com/article/CTX131673 oomkiller because of memory = leaks in vhd-util when coalescing). The servers experiencing the issue = are xcp 1.0.0-42052. Those servers are pool members with shared iscsi = storage. The advisory specify it applies to Xenserver 6. Can it be that it also = apply to XCP 1.0? The patch seems to come as source code. Can it be = compiled and applied to XCP as well? Thanks, Denis -- = Denis Cardon Tranquil IT Systems 44 bvd des pas enchant=E9s 44230 Saint S=E9bastien sur Loire tel : +33 (0) 2.40.97.57.57 http://www.tranquil-it-systems.fr _______________________________________________ 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 29 19:32:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 29 Mar 2012 19:32:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDL4h-0004Dx-IL; Thu, 29 Mar 2012 19:31:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDL4f-0004Ds-MC for xen-api@lists.xen.org; Thu, 29 Mar 2012 19:31:58 +0000 Received: from [193.109.254.147:37303] by server-6.bemta-14.messagelabs.com id 6F/E6-02047-CA8B47F4; Thu, 29 Mar 2012 19:31:56 +0000 X-Env-Sender: vase@selfip.ru X-Msg-Ref: server-16.tower-27.messagelabs.com!1333049515!2631746!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_TEST_2, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22436 invoked from network); 29 Mar 2012 19:31:56 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Mar 2012 19:31:56 -0000 Received: by lahe6 with SMTP id e6so3736660lah.32 for ; Thu, 29 Mar 2012 12:31:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfip.ru; s=google; h=mime-version:sender:x-originating-ip:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=YHAKANq46m6YHUdhgM7ApvSXjX1A01XWf6v7T2HNRZI=; b=a4OKj9Ph4OumGXPVmQmVglWwqheawxrbY2fHjAAXcUTjAOINax1CFyCV9K0R4wX+sc COdhyGifNXWHzDACDNfZTQIAmYSrrMFhOUPYW+3MCxtkkT1KKsLAIcOpCqvCQT7dbdBi FYxJbWLf8guwb4c6CuRs0wlBopVHOO6pyCRA8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:from:date:x-google-sender-auth :message-id:subject:to:content-type:x-gm-message-state; bh=YHAKANq46m6YHUdhgM7ApvSXjX1A01XWf6v7T2HNRZI=; b=N9+WZ1xUslm/HKmVHRWwWLkifjWHeCpvRJd4XdEACYkdWAHPTiwQIgj20SpbZcUhxz o7nhrMpt1o5lMoWSkOTrkJ3VkGwqU4H+8FpbsaN1Q1FUw2z/J1GWLv1HEqsmYhEW23MA uoJhQtfLg8+DLCQx1mzzxm4JOzTjfIWH9SYbGomcppuJ7TOd9/bAiMmtIJcXhXSAD6nO fNnYqiJZm5EdFlIwijrb/pJQHcFg15ahVaMgprQVz8OWybVjxlKm/8Ep36U2GOJjQGEY hB2A+oyHK0TY/1488XurMLsAOc1Fms2bgK3asP3aBjkum98/aCpM3d7AvRW9+kfvA1Ec 8HcQ== Received: by 10.152.128.38 with SMTP id nl6mr28958592lab.15.1333049515549; Thu, 29 Mar 2012 12:31:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.37.195 with HTTP; Thu, 29 Mar 2012 12:31:40 -0700 (PDT) X-Originating-IP: [178.70.155.148] From: Vasiliy Tolstov Date: Thu, 29 Mar 2012 23:31:40 +0400 X-Google-Sender-Auth: _4QmYyaUXfs-jiZxp6Ln-I0YMKo Message-ID: To: xen-api@lists.xen.org X-Gm-Message-State: ALoCoQmhzvcODZwp6U3OCfXjC1HjLdVJTuamLFf8RHHubKJtn9e/MGUOmdFJ3ghs2dsehDv65fDn Subject: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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. I'm try to switch from gplpv windows xen drivers to citrix. And found, that my implementation of xenstore client does not work with citrix drivers (but works fine with gplpv). Where i can obtain sources for windows software placed on xs-tools.iso and distibuted with windows drivers? -- Vasiliy Tolstov, Clodo.ru e-mail: v.tolstov@selfip.ru jabber: vase@selfip.ru _______________________________________________ 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 29 19:32:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 29 Mar 2012 19:32:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDL4h-0004Dx-IL; Thu, 29 Mar 2012 19:31:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDL4f-0004Ds-MC for xen-api@lists.xen.org; Thu, 29 Mar 2012 19:31:58 +0000 Received: from [193.109.254.147:37303] by server-6.bemta-14.messagelabs.com id 6F/E6-02047-CA8B47F4; Thu, 29 Mar 2012 19:31:56 +0000 X-Env-Sender: vase@selfip.ru X-Msg-Ref: server-16.tower-27.messagelabs.com!1333049515!2631746!1 X-Originating-IP: [209.85.215.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_TEST_2, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22436 invoked from network); 29 Mar 2012 19:31:56 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Mar 2012 19:31:56 -0000 Received: by lahe6 with SMTP id e6so3736660lah.32 for ; Thu, 29 Mar 2012 12:31:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfip.ru; s=google; h=mime-version:sender:x-originating-ip:from:date:x-google-sender-auth :message-id:subject:to:content-type; bh=YHAKANq46m6YHUdhgM7ApvSXjX1A01XWf6v7T2HNRZI=; b=a4OKj9Ph4OumGXPVmQmVglWwqheawxrbY2fHjAAXcUTjAOINax1CFyCV9K0R4wX+sc COdhyGifNXWHzDACDNfZTQIAmYSrrMFhOUPYW+3MCxtkkT1KKsLAIcOpCqvCQT7dbdBi FYxJbWLf8guwb4c6CuRs0wlBopVHOO6pyCRA8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:from:date:x-google-sender-auth :message-id:subject:to:content-type:x-gm-message-state; bh=YHAKANq46m6YHUdhgM7ApvSXjX1A01XWf6v7T2HNRZI=; b=N9+WZ1xUslm/HKmVHRWwWLkifjWHeCpvRJd4XdEACYkdWAHPTiwQIgj20SpbZcUhxz o7nhrMpt1o5lMoWSkOTrkJ3VkGwqU4H+8FpbsaN1Q1FUw2z/J1GWLv1HEqsmYhEW23MA uoJhQtfLg8+DLCQx1mzzxm4JOzTjfIWH9SYbGomcppuJ7TOd9/bAiMmtIJcXhXSAD6nO fNnYqiJZm5EdFlIwijrb/pJQHcFg15ahVaMgprQVz8OWybVjxlKm/8Ep36U2GOJjQGEY hB2A+oyHK0TY/1488XurMLsAOc1Fms2bgK3asP3aBjkum98/aCpM3d7AvRW9+kfvA1Ec 8HcQ== Received: by 10.152.128.38 with SMTP id nl6mr28958592lab.15.1333049515549; Thu, 29 Mar 2012 12:31:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.37.195 with HTTP; Thu, 29 Mar 2012 12:31:40 -0700 (PDT) X-Originating-IP: [178.70.155.148] From: Vasiliy Tolstov Date: Thu, 29 Mar 2012 23:31:40 +0400 X-Google-Sender-Auth: _4QmYyaUXfs-jiZxp6Ln-I0YMKo Message-ID: To: xen-api@lists.xen.org X-Gm-Message-State: ALoCoQmhzvcODZwp6U3OCfXjC1HjLdVJTuamLFf8RHHubKJtn9e/MGUOmdFJ3ghs2dsehDv65fDn Subject: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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. I'm try to switch from gplpv windows xen drivers to citrix. And found, that my implementation of xenstore client does not work with citrix drivers (but works fine with gplpv). Where i can obtain sources for windows software placed on xs-tools.iso and distibuted with windows drivers? -- Vasiliy Tolstov, Clodo.ru e-mail: v.tolstov@selfip.ru jabber: vase@selfip.ru _______________________________________________ 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 30 08:13:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 08:13:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDWxb-0006IZ-9w; Fri, 30 Mar 2012 08:13:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDWxZ-0006IU-Up for xen-api@lists.xen.org; Fri, 30 Mar 2012 08:13:26 +0000 Received: from [85.158.139.83:39403] by server-12.bemta-5.messagelabs.com id 41/F1-05587-52B657F4; Fri, 30 Mar 2012 08:13:25 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1333095204!17415361!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MjE0Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3466 invoked from network); 30 Mar 2012 08:13:24 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 30 Mar 2012 08:13:24 -0000 X-IronPort-AV: E=Sophos;i="4.75,342,1330905600"; d="scan'208";a="11662594" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 30 Mar 2012 08:13:24 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Fri, 30 Mar 2012 09:13:24 +0100 From: Paul Durrant To: Vasiliy Tolstov , "xen-api@lists.xen.org" Date: Fri, 30 Mar 2012 09:13:23 +0100 Thread-Topic: [Xen-API] where find sources for windows software on xs-tools.iso? Thread-Index: Ac0N4t3yXGbX1f06QNyleuRlAGTt3wAC0ijQ Message-ID: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Vasily, This is not entirely surprising since the user API to access xenstore are completely private to the PV driver implementation you happen to be using. We do, however, have a WMI API that we *may* be willing to disclose (modulo agreement from lawyers etc., so I can't promise). As for source, you'd need to get a license from Citrix for that. Paul > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Vasiliy Tolstov > Sent: 29 March 2012 20:32 > To: xen-api@lists.xen.org > Subject: [Xen-API] where find sources for windows software on xs-tools.iso? > > Hello. I'm try to switch from gplpv windows xen drivers to citrix. And found, > that my implementation of xenstore client does not work with citrix drivers > (but works fine with gplpv). > Where i can obtain sources for windows software placed on xs-tools.iso and > distibuted with windows drivers? > > -- > Vasiliy Tolstov, > Clodo.ru > e-mail: v.tolstov@selfip.ru > jabber: vase@selfip.ru > > _______________________________________________ > 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 Fri Mar 30 08:13:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 08:13:35 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDWxb-0006IZ-9w; Fri, 30 Mar 2012 08:13:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDWxZ-0006IU-Up for xen-api@lists.xen.org; Fri, 30 Mar 2012 08:13:26 +0000 Received: from [85.158.139.83:39403] by server-12.bemta-5.messagelabs.com id 41/F1-05587-52B657F4; Fri, 30 Mar 2012 08:13:25 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-14.tower-182.messagelabs.com!1333095204!17415361!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MjE0Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3466 invoked from network); 30 Mar 2012 08:13:24 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 30 Mar 2012 08:13:24 -0000 X-IronPort-AV: E=Sophos;i="4.75,342,1330905600"; d="scan'208";a="11662594" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 30 Mar 2012 08:13:24 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Fri, 30 Mar 2012 09:13:24 +0100 From: Paul Durrant To: Vasiliy Tolstov , "xen-api@lists.xen.org" Date: Fri, 30 Mar 2012 09:13:23 +0100 Thread-Topic: [Xen-API] where find sources for windows software on xs-tools.iso? Thread-Index: Ac0N4t3yXGbX1f06QNyleuRlAGTt3wAC0ijQ Message-ID: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Vasily, This is not entirely surprising since the user API to access xenstore are completely private to the PV driver implementation you happen to be using. We do, however, have a WMI API that we *may* be willing to disclose (modulo agreement from lawyers etc., so I can't promise). As for source, you'd need to get a license from Citrix for that. Paul > -----Original Message----- > From: xen-api-bounces@lists.xen.org [mailto:xen-api- > bounces@lists.xen.org] On Behalf Of Vasiliy Tolstov > Sent: 29 March 2012 20:32 > To: xen-api@lists.xen.org > Subject: [Xen-API] where find sources for windows software on xs-tools.iso? > > Hello. I'm try to switch from gplpv windows xen drivers to citrix. And found, > that my implementation of xenstore client does not work with citrix drivers > (but works fine with gplpv). > Where i can obtain sources for windows software placed on xs-tools.iso and > distibuted with windows drivers? > > -- > Vasiliy Tolstov, > Clodo.ru > e-mail: v.tolstov@selfip.ru > jabber: vase@selfip.ru > > _______________________________________________ > 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 Fri Mar 30 08:45:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 08:45: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 1SDXSH-0001im-7R; Fri, 30 Mar 2012 08:45:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXSF-0001if-Hi for xen-api@lists.xen.org; Fri, 30 Mar 2012 08:45:07 +0000 Received: from [85.158.139.83:61341] by server-12.bemta-5.messagelabs.com id 4D/DD-05587-292757F4; Fri, 30 Mar 2012 08:45:06 +0000 X-Env-Sender: joseph.glanville@orionvm.com.au X-Msg-Ref: server-5.tower-182.messagelabs.com!1333097103!21705531!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_TEST_2, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23562 invoked from network); 30 Mar 2012 08:45:05 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 30 Mar 2012 08:45:05 -0000 Received: by obbwd20 with SMTP id wd20so841363obb.32 for ; Fri, 30 Mar 2012 01:45:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:x-gm-message-state:content-type :content-transfer-encoding; bh=p4xQkGW7hFnNApp7g3Jf2YezGw0rhesIJYIZfkQXqGQ=; b=CO+sDeiqX+QdqlVMI+WJC8hE0t5K9DXnT2hC+ScoAYRZWBfUQWm4kvxHL11Tee1CHL lDGbSuTul7b71xufXKQUEJ10VchHTralaiQUqLNOh7wtcq78OFA7rAjrai/dpP+zsh8k Obmk1dcQJPs0lmLVC+6+plaxXphGWPeLwBgvg+PnNWiDOXjfjLyq4Ej/F53ZqSwnAIp4 XBoocvQtML3bjqTaUi6nkuiv/OEoBgUkQTrs6Zib5vWuICgVwXi7P5+8vp+w9Y/EPQVk 37mOWXp618s8/zt0cZzN0hSM62DLSUcDJ/3JlImxrELgiqa79oBNW6UkJ7UH/5KJxihE 1esw== MIME-Version: 1.0 Received: by 10.182.222.74 with SMTP id qk10mr1434965obc.75.1333097103229; Fri, 30 Mar 2012 01:45:03 -0700 (PDT) Received: by 10.182.47.167 with HTTP; Fri, 30 Mar 2012 01:45:03 -0700 (PDT) X-Originating-IP: [59.167.234.130] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> Date: Fri, 30 Mar 2012 19:45:03 +1100 Message-ID: From: Joseph Glanville To: Paul Durrant X-Gm-Message-State: ALoCoQm+4t5FUM+3f7Y80y0Y43lX1u0Pi0e5x+Q9kGxawmaK4lHyJ2Y71d/wWkgdi3/x4pbvZP7D Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Hi Paul, What are the major differences between the Citrix drivers and GPLPV? Can one use the Citrix drivers on Xen.org 4.1.2? I remember playing with them a while ago but had an issue where the Citrix shutdown monitor was polling a xenstore address that didn't exist ( I think this was on 4.0 and the drivers were for Boston.. which AFAIK is 4.1-testing based) I would like to put this documentation up on the wiki so people know which drivers work with which Xen release (XenServer, XCP, Xen.org) Thanks! Joseph. On 30 March 2012 19:13, Paul Durrant wrote: > Vasily, > > =A0This is not entirely surprising since the user API to access xenstore = are completely private to the PV driver implementation you happen to be usi= ng. We do, however, have a WMI API that we *may* be willing to disclose (mo= dulo agreement from lawyers etc., so I can't promise). As for source, you'd= need to get a license from Citrix for that. > > =A0Paul > >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >> bounces@lists.xen.org] On Behalf Of Vasiliy Tolstov >> Sent: 29 March 2012 20:32 >> To: xen-api@lists.xen.org >> Subject: [Xen-API] where find sources for windows software on xs-tools.i= so? >> >> Hello. I'm try to switch from gplpv windows xen drivers to citrix. And f= ound, >> that my implementation of xenstore client does not work with citrix driv= ers >> (but works fine with gplpv). >> Where i can obtain sources for windows software placed on xs-tools.iso a= nd >> distibuted with windows drivers? >> >> -- >> Vasiliy Tolstov, >> Clodo.ru >> e-mail: v.tolstov@selfip.ru >> jabber: vase@selfip.ru >> >> _______________________________________________ >> 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 -- = Founder | Director | VP Research Orion Virtualisation Solutions=A0|=A0www.orionvm.com.au=A0| Phone: 1300 56 99 52 | Mobile: 0428 754 846 _______________________________________________ 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 30 08:45:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 08:45: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 1SDXSH-0001im-7R; Fri, 30 Mar 2012 08:45:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXSF-0001if-Hi for xen-api@lists.xen.org; Fri, 30 Mar 2012 08:45:07 +0000 Received: from [85.158.139.83:61341] by server-12.bemta-5.messagelabs.com id 4D/DD-05587-292757F4; Fri, 30 Mar 2012 08:45:06 +0000 X-Env-Sender: joseph.glanville@orionvm.com.au X-Msg-Ref: server-5.tower-182.messagelabs.com!1333097103!21705531!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_TEST_2, RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23562 invoked from network); 30 Mar 2012 08:45:05 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 30 Mar 2012 08:45:05 -0000 Received: by obbwd20 with SMTP id wd20so841363obb.32 for ; Fri, 30 Mar 2012 01:45:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:x-gm-message-state:content-type :content-transfer-encoding; bh=p4xQkGW7hFnNApp7g3Jf2YezGw0rhesIJYIZfkQXqGQ=; b=CO+sDeiqX+QdqlVMI+WJC8hE0t5K9DXnT2hC+ScoAYRZWBfUQWm4kvxHL11Tee1CHL lDGbSuTul7b71xufXKQUEJ10VchHTralaiQUqLNOh7wtcq78OFA7rAjrai/dpP+zsh8k Obmk1dcQJPs0lmLVC+6+plaxXphGWPeLwBgvg+PnNWiDOXjfjLyq4Ej/F53ZqSwnAIp4 XBoocvQtML3bjqTaUi6nkuiv/OEoBgUkQTrs6Zib5vWuICgVwXi7P5+8vp+w9Y/EPQVk 37mOWXp618s8/zt0cZzN0hSM62DLSUcDJ/3JlImxrELgiqa79oBNW6UkJ7UH/5KJxihE 1esw== MIME-Version: 1.0 Received: by 10.182.222.74 with SMTP id qk10mr1434965obc.75.1333097103229; Fri, 30 Mar 2012 01:45:03 -0700 (PDT) Received: by 10.182.47.167 with HTTP; Fri, 30 Mar 2012 01:45:03 -0700 (PDT) X-Originating-IP: [59.167.234.130] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> Date: Fri, 30 Mar 2012 19:45:03 +1100 Message-ID: From: Joseph Glanville To: Paul Durrant X-Gm-Message-State: ALoCoQm+4t5FUM+3f7Y80y0Y43lX1u0Pi0e5x+Q9kGxawmaK4lHyJ2Y71d/wWkgdi3/x4pbvZP7D Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 Hi Paul, What are the major differences between the Citrix drivers and GPLPV? Can one use the Citrix drivers on Xen.org 4.1.2? I remember playing with them a while ago but had an issue where the Citrix shutdown monitor was polling a xenstore address that didn't exist ( I think this was on 4.0 and the drivers were for Boston.. which AFAIK is 4.1-testing based) I would like to put this documentation up on the wiki so people know which drivers work with which Xen release (XenServer, XCP, Xen.org) Thanks! Joseph. On 30 March 2012 19:13, Paul Durrant wrote: > Vasily, > > =A0This is not entirely surprising since the user API to access xenstore = are completely private to the PV driver implementation you happen to be usi= ng. We do, however, have a WMI API that we *may* be willing to disclose (mo= dulo agreement from lawyers etc., so I can't promise). As for source, you'd= need to get a license from Citrix for that. > > =A0Paul > >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >> bounces@lists.xen.org] On Behalf Of Vasiliy Tolstov >> Sent: 29 March 2012 20:32 >> To: xen-api@lists.xen.org >> Subject: [Xen-API] where find sources for windows software on xs-tools.i= so? >> >> Hello. I'm try to switch from gplpv windows xen drivers to citrix. And f= ound, >> that my implementation of xenstore client does not work with citrix driv= ers >> (but works fine with gplpv). >> Where i can obtain sources for windows software placed on xs-tools.iso a= nd >> distibuted with windows drivers? >> >> -- >> Vasiliy Tolstov, >> Clodo.ru >> e-mail: v.tolstov@selfip.ru >> jabber: vase@selfip.ru >> >> _______________________________________________ >> 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 -- = Founder | Director | VP Research Orion Virtualisation Solutions=A0|=A0www.orionvm.com.au=A0| Phone: 1300 56 99 52 | Mobile: 0428 754 846 _______________________________________________ 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 30 08:57:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 08:57: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 1SDXec-000239-RP; Fri, 30 Mar 2012 08:57:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXec-000232-3D for xen-api@lists.xen.org; Fri, 30 Mar 2012 08:57:54 +0000 Received: from [85.158.138.51:24115] by server-6.bemta-3.messagelabs.com id 6A/1C-08206-195757F4; Fri, 30 Mar 2012 08:57:53 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1333097872!20042748!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MjE0Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25679 invoked from network); 30 Mar 2012 08:57:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 30 Mar 2012 08:57:52 -0000 X-IronPort-AV: E=Sophos;i="4.75,343,1330905600"; d="scan'208";a="11664881" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 30 Mar 2012 08:57:52 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Fri, 30 Mar 2012 09:57:52 +0100 From: Paul Durrant To: Joseph Glanville Date: Fri, 30 Mar 2012 09:58:09 +0100 Thread-Topic: [Xen-API] where find sources for windows software on xs-tools.iso? Thread-Index: Ac0OUWjdtIhMGQPXR9GYI7Ly5ZTaEgAAPSoA Message-ID: <291EDFCB1E9E224A99088639C4762022C812021A9F@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > -----Original Message----- > From: Joseph Glanville [mailto:joseph.glanville@orionvm.com.au] > Sent: 30 March 2012 09:45 > To: Paul Durrant > Cc: Vasiliy Tolstov; xen-api@lists.xen.org > Subject: Re: [Xen-API] where find sources for windows software on xs- > tools.iso? > > Hi Paul, > > What are the major differences between the Citrix drivers and GPLPV? Joseph, How about 'the entire codebase' as an answer ;-) There's no connection between the two and not being familiar with the current state of GPLPV I can't really compare and contrast at a functional level. > Can one use the Citrix drivers on Xen.org 4.1.2? > Yes. The EULA allows them to be used on open source Xen. I've had them working myself on a private build of xen-unstable and a PVops dom0 kernel. > I remember playing with them a while ago but had an issue where the Citrix > shutdown monitor was polling a xenstore address that didn't exist ( I think > this was on 4.0 and the drivers were for Boston.. > which AFAIK is 4.1-testing based) > You may well get issues with older guest agents dying and re-spawning because of xenstore keys it expects to find and doesn't. I suggest using the package from the recent Sanibel hotfix, XS602E002. The drivers and guest agent therein should be fine on open source Xen and a PVops kernel although I have not tried them myself. Paul _______________________________________________ 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 30 08:57:59 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 08:57: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 1SDXec-000239-RP; Fri, 30 Mar 2012 08:57:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXec-000232-3D for xen-api@lists.xen.org; Fri, 30 Mar 2012 08:57:54 +0000 Received: from [85.158.138.51:24115] by server-6.bemta-3.messagelabs.com id 6A/1C-08206-195757F4; Fri, 30 Mar 2012 08:57:53 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1333097872!20042748!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MjE0Mw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25679 invoked from network); 30 Mar 2012 08:57:52 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-9.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 30 Mar 2012 08:57:52 -0000 X-IronPort-AV: E=Sophos;i="4.75,343,1330905600"; d="scan'208";a="11664881" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 30 Mar 2012 08:57:52 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Fri, 30 Mar 2012 09:57:52 +0100 From: Paul Durrant To: Joseph Glanville Date: Fri, 30 Mar 2012 09:58:09 +0100 Thread-Topic: [Xen-API] where find sources for windows software on xs-tools.iso? Thread-Index: Ac0OUWjdtIhMGQPXR9GYI7Ly5ZTaEgAAPSoA Message-ID: <291EDFCB1E9E224A99088639C4762022C812021A9F@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 > -----Original Message----- > From: Joseph Glanville [mailto:joseph.glanville@orionvm.com.au] > Sent: 30 March 2012 09:45 > To: Paul Durrant > Cc: Vasiliy Tolstov; xen-api@lists.xen.org > Subject: Re: [Xen-API] where find sources for windows software on xs- > tools.iso? > > Hi Paul, > > What are the major differences between the Citrix drivers and GPLPV? Joseph, How about 'the entire codebase' as an answer ;-) There's no connection between the two and not being familiar with the current state of GPLPV I can't really compare and contrast at a functional level. > Can one use the Citrix drivers on Xen.org 4.1.2? > Yes. The EULA allows them to be used on open source Xen. I've had them working myself on a private build of xen-unstable and a PVops dom0 kernel. > I remember playing with them a while ago but had an issue where the Citrix > shutdown monitor was polling a xenstore address that didn't exist ( I think > this was on 4.0 and the drivers were for Boston.. > which AFAIK is 4.1-testing based) > You may well get issues with older guest agents dying and re-spawning because of xenstore keys it expects to find and doesn't. I suggest using the package from the recent Sanibel hotfix, XS602E002. The drivers and guest agent therein should be fine on open source Xen and a PVops kernel although I have not tried them myself. Paul _______________________________________________ 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 30 09:06:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 09:06:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXmd-0002M4-CE; Fri, 30 Mar 2012 09:06:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXmb-0002Lu-7F for xen-api@lists.xen.org; Fri, 30 Mar 2012 09:06:09 +0000 Received: from [85.158.143.99:4895] by server-2.bemta-4.messagelabs.com id 36/89-17550-087757F4; Fri, 30 Mar 2012 09:06:08 +0000 X-Env-Sender: joseph.glanville@orionvm.com.au X-Msg-Ref: server-3.tower-216.messagelabs.com!1333098365!20984185!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32312 invoked from network); 30 Mar 2012 09:06:07 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 30 Mar 2012 09:06:07 -0000 Received: by obbwd20 with SMTP id wd20so871773obb.32 for ; Fri, 30 Mar 2012 02:06:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:x-gm-message-state:content-type :content-transfer-encoding; bh=equ5S0CueKg0t0bX87n1xgNhTgh3EEuAbHEOy5f71/o=; b=PEgF/f3j05y41U/S9zs6cu1u0UHPmQJpjER9rghma1ueOjOaxPMC4DFM5GQneNJKhE t0Gi13LS1IQACtlj1Kk4tMTGHVdVhHhJKJ7mvhHzfLydIMzaWR2fL4AtZCaALLRzCzWn vhEU9N9scnL/QOoghv7CWyMWL2rB3GJpPt6KEwBb4kugwUNzMtCDgohHzNnpCVz2Re9I n1+GUK8PRnA50wShqIMdKrFawAOvJpaLY4GpSw+3JfMtPhG18dVDVRH9E2ajRaWFdZez 7g/G6JGHV0xWPix+g+LyfVu8InzahHdBClSMT0Pf+zy9Wiq/hR2N7Rr4Z4vCyl4xlHi5 4ujg== MIME-Version: 1.0 Received: by 10.60.172.231 with SMTP id bf7mr1553343oec.45.1333098364821; Fri, 30 Mar 2012 02:06:04 -0700 (PDT) Received: by 10.182.47.167 with HTTP; Fri, 30 Mar 2012 02:06:04 -0700 (PDT) X-Originating-IP: [59.167.234.130] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021A9F@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C812021A9F@LONPMAILBOX01.citrite.net> Date: Fri, 30 Mar 2012 20:06:04 +1100 Message-ID: From: Joseph Glanville To: Paul Durrant X-Gm-Message-State: ALoCoQkDWvfhWV1yVntF+ODDhJegOFGyj+fkNor9KWwn5K6r7jUpW7diAqPSMrpJ/Y0X+adKWdWI Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On 30 March 2012 19:58, Paul Durrant wrote: >> -----Original Message----- >> From: Joseph Glanville [mailto:joseph.glanville@orionvm.com.au] >> Sent: 30 March 2012 09:45 >> To: Paul Durrant >> Cc: Vasiliy Tolstov; xen-api@lists.xen.org >> Subject: Re: [Xen-API] where find sources for windows software on xs- >> tools.iso? >> >> Hi Paul, >> >> What are the major differences between the Citrix drivers and GPLPV? > > Joseph, > > =A0How about 'the entire codebase' as an answer ;-) There's no connection= between the two and not being familiar with the current state of GPLPV I c= an't really compare and contrast at a functional level. Hehe fair enough. :P > >> Can one use the Citrix drivers on Xen.org 4.1.2? >> > > =A0Yes. The EULA allows them to be used on open source Xen. I've had them= working myself on a private build of xen-unstable and a PVops dom0 kernel. > >> I remember playing with them a while ago but had an issue where the Citr= ix >> shutdown monitor was polling a xenstore address that didn't exist ( I th= ink >> this was on 4.0 and the drivers were for Boston.. >> which AFAIK is 4.1-testing based) >> > > You may well get issues with older guest agents dying and re-spawning bec= ause of xenstore keys it expects to find and doesn't. I suggest using the p= ackage from the recent Sanibel hotfix, XS602E002. The drivers and guest age= nt therein should be fine on open source Xen and a PVops kernel although I = have not tried them myself. > > =A0Paul Thanks Paul, that should be plenty to get me started. :) Joseph. -- = Founder | Director | VP Research Orion Virtualisation Solutions=A0|=A0www.orionvm.com.au=A0| Phone: 1300 56 99 52 | Mobile: 0428 754 846 _______________________________________________ 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 30 09:06:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 30 Mar 2012 09:06:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXmd-0002M4-CE; Fri, 30 Mar 2012 09:06:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDXmb-0002Lu-7F for xen-api@lists.xen.org; Fri, 30 Mar 2012 09:06:09 +0000 Received: from [85.158.143.99:4895] by server-2.bemta-4.messagelabs.com id 36/89-17550-087757F4; Fri, 30 Mar 2012 09:06:08 +0000 X-Env-Sender: joseph.glanville@orionvm.com.au X-Msg-Ref: server-3.tower-216.messagelabs.com!1333098365!20984185!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32312 invoked from network); 30 Mar 2012 09:06:07 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 30 Mar 2012 09:06:07 -0000 Received: by obbwd20 with SMTP id wd20so871773obb.32 for ; Fri, 30 Mar 2012 02:06:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:x-gm-message-state:content-type :content-transfer-encoding; bh=equ5S0CueKg0t0bX87n1xgNhTgh3EEuAbHEOy5f71/o=; b=PEgF/f3j05y41U/S9zs6cu1u0UHPmQJpjER9rghma1ueOjOaxPMC4DFM5GQneNJKhE t0Gi13LS1IQACtlj1Kk4tMTGHVdVhHhJKJ7mvhHzfLydIMzaWR2fL4AtZCaALLRzCzWn vhEU9N9scnL/QOoghv7CWyMWL2rB3GJpPt6KEwBb4kugwUNzMtCDgohHzNnpCVz2Re9I n1+GUK8PRnA50wShqIMdKrFawAOvJpaLY4GpSw+3JfMtPhG18dVDVRH9E2ajRaWFdZez 7g/G6JGHV0xWPix+g+LyfVu8InzahHdBClSMT0Pf+zy9Wiq/hR2N7Rr4Z4vCyl4xlHi5 4ujg== MIME-Version: 1.0 Received: by 10.60.172.231 with SMTP id bf7mr1553343oec.45.1333098364821; Fri, 30 Mar 2012 02:06:04 -0700 (PDT) Received: by 10.182.47.167 with HTTP; Fri, 30 Mar 2012 02:06:04 -0700 (PDT) X-Originating-IP: [59.167.234.130] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021A9F@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C812021A9F@LONPMAILBOX01.citrite.net> Date: Fri, 30 Mar 2012 20:06:04 +1100 Message-ID: From: Joseph Glanville To: Paul Durrant X-Gm-Message-State: ALoCoQkDWvfhWV1yVntF+ODDhJegOFGyj+fkNor9KWwn5K6r7jUpW7diAqPSMrpJ/Y0X+adKWdWI Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 On 30 March 2012 19:58, Paul Durrant wrote: >> -----Original Message----- >> From: Joseph Glanville [mailto:joseph.glanville@orionvm.com.au] >> Sent: 30 March 2012 09:45 >> To: Paul Durrant >> Cc: Vasiliy Tolstov; xen-api@lists.xen.org >> Subject: Re: [Xen-API] where find sources for windows software on xs- >> tools.iso? >> >> Hi Paul, >> >> What are the major differences between the Citrix drivers and GPLPV? > > Joseph, > > =A0How about 'the entire codebase' as an answer ;-) There's no connection= between the two and not being familiar with the current state of GPLPV I c= an't really compare and contrast at a functional level. Hehe fair enough. :P > >> Can one use the Citrix drivers on Xen.org 4.1.2? >> > > =A0Yes. The EULA allows them to be used on open source Xen. I've had them= working myself on a private build of xen-unstable and a PVops dom0 kernel. > >> I remember playing with them a while ago but had an issue where the Citr= ix >> shutdown monitor was polling a xenstore address that didn't exist ( I th= ink >> this was on 4.0 and the drivers were for Boston.. >> which AFAIK is 4.1-testing based) >> > > You may well get issues with older guest agents dying and re-spawning bec= ause of xenstore keys it expects to find and doesn't. I suggest using the p= ackage from the recent Sanibel hotfix, XS602E002. The drivers and guest age= nt therein should be fine on open source Xen and a PVops kernel although I = have not tried them myself. > > =A0Paul Thanks Paul, that should be plenty to get me started. :) Joseph. -- = Founder | Director | VP Research Orion Virtualisation Solutions=A0|=A0www.orionvm.com.au=A0| Phone: 1300 56 99 52 | Mobile: 0428 754 846 _______________________________________________ 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 31 13:46:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 31 Mar 2012 13:46:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDydG-0007Oq-SX; Sat, 31 Mar 2012 13:46:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDydF-0007Ol-Ja for xen-api@lists.xen.org; Sat, 31 Mar 2012 13:46:17 +0000 Received: from [85.158.143.35:16955] by server-3.bemta-4.messagelabs.com id 1E/02-05853-8AA077F4; Sat, 31 Mar 2012 13:46:16 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1333201574!14331462!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_TEST_2,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4837 invoked from network); 31 Mar 2012 13:46:15 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 31 Mar 2012 13:46:15 -0000 Received: by bkcjg9 with SMTP id jg9so1427632bkc.32 for ; Sat, 31 Mar 2012 06:46:14 -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=YppbyOodsO8UWQCpxh/ItWgUZqGiXn1CwdhEvD++7GM=; b=X5tp1JD6O9qEGABvOdHhrFYTbUYEvyY6HybkSGsGoCNjLRVLUpZLvbSd/F4WglZkXD u1tDGcoNktaHRAtO8brxgqQvjIBgQ5iH7r7WLZTohGvbB38KhyJwLbfZCHay9/3sUvom hK2e1Pb4PfYHdFwyFU0C3o/FuvljEeAcHKaBKWeNY1WpDflExgLzKGOeWs0KEhxib2o9 Z5PbMufxgy1eiT1LM5CDcvMyLM+C294t6JY4Y7e5XgiMoJ6FKjnx1A8hTyZRTomATKGl k9Rmb6l3DAlzGfJCTJ558xv01KSL9UhlrAb+1ubcDD+663hAGldQCo6x3lXPo/+Wc1oM KcmA== Received: by 10.204.155.73 with SMTP id r9mr851532bkw.22.1333201574470; Sat, 31 Mar 2012 06:46:14 -0700 (PDT) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id z14sm23733606bky.15.2012.03.31.06.46.12 (version=SSLv3 cipher=OTHER); Sat, 31 Mar 2012 06:46:12 -0700 (PDT) Message-ID: <4F770ADD.2070708@gmail.com> Date: Sat, 31 Mar 2012 17:47:09 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 I don't know Citrix intentions during XenServer -> XCP opensoursing, bu if XCP is opensource, so every component shall be open, isn't it? And xs-tools.iso is included to opensource distribution of XCP. On 30.03.2012 12:13, Paul Durrant wrote: > Vasily, > > This is not entirely surprising since the user API to access xenstore are completely private to the PV driver implementation you happen to be using. We do, however, have a WMI API that we *may* be willing to disclose (modulo agreement from lawyers etc., so I can't promise). As for source, you'd need to get a license from Citrix for that. > > Paul > >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >> bounces@lists.xen.org] On Behalf Of Vasiliy Tolstov >> Sent: 29 March 2012 20:32 >> To: xen-api@lists.xen.org >> Subject: [Xen-API] where find sources for windows software on xs-tools.iso? >> >> Hello. I'm try to switch from gplpv windows xen drivers to citrix. And found, >> that my implementation of xenstore client does not work with citrix drivers >> (but works fine with gplpv). >> Where i can obtain sources for windows software placed on xs-tools.iso and >> distibuted with windows drivers? >> >> -- >> Vasiliy Tolstov, >> Clodo.ru >> e-mail: v.tolstov@selfip.ru >> jabber: vase@selfip.ru >> >> _______________________________________________ >> 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 Sat Mar 31 13:46:27 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 31 Mar 2012 13:46:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDydG-0007Oq-SX; Sat, 31 Mar 2012 13:46:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SDydF-0007Ol-Ja for xen-api@lists.xen.org; Sat, 31 Mar 2012 13:46:17 +0000 Received: from [85.158.143.35:16955] by server-3.bemta-4.messagelabs.com id 1E/02-05853-8AA077F4; Sat, 31 Mar 2012 13:46:16 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1333201574!14331462!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_TEST_2,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4837 invoked from network); 31 Mar 2012 13:46:15 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 31 Mar 2012 13:46:15 -0000 Received: by bkcjg9 with SMTP id jg9so1427632bkc.32 for ; Sat, 31 Mar 2012 06:46:14 -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=YppbyOodsO8UWQCpxh/ItWgUZqGiXn1CwdhEvD++7GM=; b=X5tp1JD6O9qEGABvOdHhrFYTbUYEvyY6HybkSGsGoCNjLRVLUpZLvbSd/F4WglZkXD u1tDGcoNktaHRAtO8brxgqQvjIBgQ5iH7r7WLZTohGvbB38KhyJwLbfZCHay9/3sUvom hK2e1Pb4PfYHdFwyFU0C3o/FuvljEeAcHKaBKWeNY1WpDflExgLzKGOeWs0KEhxib2o9 Z5PbMufxgy1eiT1LM5CDcvMyLM+C294t6JY4Y7e5XgiMoJ6FKjnx1A8hTyZRTomATKGl k9Rmb6l3DAlzGfJCTJ558xv01KSL9UhlrAb+1ubcDD+663hAGldQCo6x3lXPo/+Wc1oM KcmA== Received: by 10.204.155.73 with SMTP id r9mr851532bkw.22.1333201574470; Sat, 31 Mar 2012 06:46:14 -0700 (PDT) Received: from home.desunote.ru (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id z14sm23733606bky.15.2012.03.31.06.46.12 (version=SSLv3 cipher=OTHER); Sat, 31 Mar 2012 06:46:12 -0700 (PDT) Message-ID: <4F770ADD.2070708@gmail.com> Date: Sat, 31 Mar 2012 17:47:09 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> Subject: Re: [Xen-API] where find sources for windows software on xs-tools.iso? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of API issues surrounding Xen 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 I don't know Citrix intentions during XenServer -> XCP opensoursing, bu if XCP is opensource, so every component shall be open, isn't it? And xs-tools.iso is included to opensource distribution of XCP. On 30.03.2012 12:13, Paul Durrant wrote: > Vasily, > > This is not entirely surprising since the user API to access xenstore are completely private to the PV driver implementation you happen to be using. We do, however, have a WMI API that we *may* be willing to disclose (modulo agreement from lawyers etc., so I can't promise). As for source, you'd need to get a license from Citrix for that. > > Paul > >> -----Original Message----- >> From: xen-api-bounces@lists.xen.org [mailto:xen-api- >> bounces@lists.xen.org] On Behalf Of Vasiliy Tolstov >> Sent: 29 March 2012 20:32 >> To: xen-api@lists.xen.org >> Subject: [Xen-API] where find sources for windows software on xs-tools.iso? >> >> Hello. I'm try to switch from gplpv windows xen drivers to citrix. And found, >> that my implementation of xenstore client does not work with citrix drivers >> (but works fine with gplpv). >> Where i can obtain sources for windows software placed on xs-tools.iso and >> distibuted with windows drivers? >> >> -- >> Vasiliy Tolstov, >> Clodo.ru >> e-mail: v.tolstov@selfip.ru >> jabber: vase@selfip.ru >> >> _______________________________________________ >> 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