From xen-api-bounces@lists.xen.org Mon Apr 02 06:59:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 02 Apr 2012 06:59: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 1SEbEe-0000F2-Ke; Mon, 02 Apr 2012 06:59:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SEbEd-0000Ex-1S for xen-api@lists.xen.org; Mon, 02 Apr 2012 06:59:27 +0000 Received: from [85.158.143.35:18569] by server-1.bemta-4.messagelabs.com id 48/E7-20925-E4E497F4; Mon, 02 Apr 2012 06:59:26 +0000 X-Env-Sender: vase@selfip.ru X-Msg-Ref: server-4.tower-21.messagelabs.com!1333349964!5161617!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 1083 invoked from network); 2 Apr 2012 06:59:25 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2012 06:59:25 -0000 Received: by lahe6 with SMTP id e6so3645541lah.32 for ; Sun, 01 Apr 2012 23:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfip.ru; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type; bh=r6iWa7Q28KTlgndccVhpBscWHMQpCY+AG3VzLkqPCtM=; b=SzB4J9OmwRUUYpngNunvOfmkRHDqz6ACiaEHzFf3rGHLUE5kK203/7jMs5aZiDbKHR d0ZbV6CAhm6r1ac27x8jQ9+BAY0mlV6Q1R2Uu17jSs/Ferk4woXSXnpm8zjED/vCfVjw xA+ZigZkYRMMVOC1lUtmsk7kbaj6eA8T7QNhg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=r6iWa7Q28KTlgndccVhpBscWHMQpCY+AG3VzLkqPCtM=; b=TQSZsyjv5/ihqrcPqrOHzkB/vGXN4/VyFuPe0UpE+NiOw2oMbfUldw/3aCLh9Cl/u2 vgK2abFg5ysSdpFro2jMDIK/QtvoCx5hexuJ80jTifEP3SGfG257t3g/pRtVWTeq+8w8 rJpkG/AZAThDOqt/PbJSKcvETWCWN6AFW0pxFYnJY8o2Lrrs+pi7B7sigmAgGdv3GQbA mYJkl1JHKdby2/KSEMggw7Sxsm1vcT4PL1fd/EXAalO4Et0/gzV8jimYnX/BVKWEy0C3 t2zFwmDWR5+aCZiHW2XrgpNC6PzsS+mYGjndTi2h7Xep+mttJrDWylqyYAh5osoiXsNS wvCw== Received: by 10.152.102.228 with SMTP id fr4mr8267783lab.23.1333349964356; Sun, 01 Apr 2012 23:59:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.37.234 with HTTP; Sun, 1 Apr 2012 23:59:00 -0700 (PDT) X-Originating-IP: [85.143.161.18] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> From: Vasiliy Tolstov Date: Mon, 2 Apr 2012 10:59:00 +0400 X-Google-Sender-Auth: zs2U5ydJCK3wNQK633nW0poUa5U Message-ID: To: Paul Durrant X-Gm-Message-State: ALoCoQk33d+pDC2dcJg8AioossLEkGt7HixicfgiAJ5WicD8HgF2AbkmJx6EInUpKX/Yjf7qXUry 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 2012/3/30 Paul Durrant : > I to access xenstore are completely private to the PV driver implementation you happen to be using. Why? I'm not understand what neededing to reinvent the wheel? If i want to write some tool, that works under all windows xen drivers, that i need to do? > 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. Where i can find WPI API references or some docs? -- 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 Mon Apr 02 06:59:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 02 Apr 2012 06:59: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 1SEbEe-0000F2-Ke; Mon, 02 Apr 2012 06:59:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SEbEd-0000Ex-1S for xen-api@lists.xen.org; Mon, 02 Apr 2012 06:59:27 +0000 Received: from [85.158.143.35:18569] by server-1.bemta-4.messagelabs.com id 48/E7-20925-E4E497F4; Mon, 02 Apr 2012 06:59:26 +0000 X-Env-Sender: vase@selfip.ru X-Msg-Ref: server-4.tower-21.messagelabs.com!1333349964!5161617!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 1083 invoked from network); 2 Apr 2012 06:59:25 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2012 06:59:25 -0000 Received: by lahe6 with SMTP id e6so3645541lah.32 for ; Sun, 01 Apr 2012 23:59:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfip.ru; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type; bh=r6iWa7Q28KTlgndccVhpBscWHMQpCY+AG3VzLkqPCtM=; b=SzB4J9OmwRUUYpngNunvOfmkRHDqz6ACiaEHzFf3rGHLUE5kK203/7jMs5aZiDbKHR d0ZbV6CAhm6r1ac27x8jQ9+BAY0mlV6Q1R2Uu17jSs/Ferk4woXSXnpm8zjED/vCfVjw xA+ZigZkYRMMVOC1lUtmsk7kbaj6eA8T7QNhg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=r6iWa7Q28KTlgndccVhpBscWHMQpCY+AG3VzLkqPCtM=; b=TQSZsyjv5/ihqrcPqrOHzkB/vGXN4/VyFuPe0UpE+NiOw2oMbfUldw/3aCLh9Cl/u2 vgK2abFg5ysSdpFro2jMDIK/QtvoCx5hexuJ80jTifEP3SGfG257t3g/pRtVWTeq+8w8 rJpkG/AZAThDOqt/PbJSKcvETWCWN6AFW0pxFYnJY8o2Lrrs+pi7B7sigmAgGdv3GQbA mYJkl1JHKdby2/KSEMggw7Sxsm1vcT4PL1fd/EXAalO4Et0/gzV8jimYnX/BVKWEy0C3 t2zFwmDWR5+aCZiHW2XrgpNC6PzsS+mYGjndTi2h7Xep+mttJrDWylqyYAh5osoiXsNS wvCw== Received: by 10.152.102.228 with SMTP id fr4mr8267783lab.23.1333349964356; Sun, 01 Apr 2012 23:59:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.37.234 with HTTP; Sun, 1 Apr 2012 23:59:00 -0700 (PDT) X-Originating-IP: [85.143.161.18] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> From: Vasiliy Tolstov Date: Mon, 2 Apr 2012 10:59:00 +0400 X-Google-Sender-Auth: zs2U5ydJCK3wNQK633nW0poUa5U Message-ID: To: Paul Durrant X-Gm-Message-State: ALoCoQk33d+pDC2dcJg8AioossLEkGt7HixicfgiAJ5WicD8HgF2AbkmJx6EInUpKX/Yjf7qXUry 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 2012/3/30 Paul Durrant : > I to access xenstore are completely private to the PV driver implementation you happen to be using. Why? I'm not understand what neededing to reinvent the wheel? If i want to write some tool, that works under all windows xen drivers, that i need to do? > 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. Where i can find WPI API references or some docs? -- 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 Mon Apr 02 08:16:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 02 Apr 2012 08:16: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 1SEcRD-0001PS-Ih; Mon, 02 Apr 2012 08:16:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SEcRC-0001PN-4H for xen-api@lists.xen.org; Mon, 02 Apr 2012 08:16:30 +0000 Received: from [193.109.254.147:7859] by server-12.bemta-14.messagelabs.com id 5D/15-05847-D50697F4; Mon, 02 Apr 2012 08:16:29 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1333354588!2996880!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MjYwOQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16658 invoked from network); 2 Apr 2012 08:16:28 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2012 08:16:28 -0000 X-IronPort-AV: E=Sophos;i="4.75,355,1330905600"; d="scan'208";a="11714709" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Apr 2012 08:16:27 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 2 Apr 2012 09:16:27 +0100 From: Paul Durrant To: Vasiliy Tolstov Date: Mon, 2 Apr 2012 09:16:48 +0100 Thread-Topic: [Xen-API] where find sources for windows software on xs-tools.iso? Thread-Index: Ac0QnixZW8fzIq/GSxKtumUk8S7yWwAClesA Message-ID: <291EDFCB1E9E224A99088639C4762022C812021BA9@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: vase@selfip.ru [mailto:vase@selfip.ru] On Behalf Of Vasiliy Tolstov > Sent: 02 April 2012 07:59 > To: Paul Durrant > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] where find sources for windows software on xs- > tools.iso? > > 2012/3/30 Paul Durrant : > > I to access xenstore are completely private to the PV driver > implementation you happen to be using. > > Why? Vasiliy, There is no 'standard' in this respect for PV drivers. It would be good if there was one, but there isn't, so each different set of PV drivers will expose a different API for accessing xenstore. > I'm not understand what neededing to reinvent the wheel? If i want to > write some tool, that works under all windows xen drivers, that i need to > do? > > > 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. > > Where i can find WPI API references or some docs? > As I said, the WMI API is not published as yet. I'll see what I can do about getting approval to do this. 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 Mon Apr 02 08:16:45 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 02 Apr 2012 08:16: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 1SEcRD-0001PS-Ih; Mon, 02 Apr 2012 08:16:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SEcRC-0001PN-4H for xen-api@lists.xen.org; Mon, 02 Apr 2012 08:16:30 +0000 Received: from [193.109.254.147:7859] by server-12.bemta-14.messagelabs.com id 5D/15-05847-D50697F4; Mon, 02 Apr 2012 08:16:29 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1333354588!2996880!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MjYwOQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16658 invoked from network); 2 Apr 2012 08:16:28 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Apr 2012 08:16:28 -0000 X-IronPort-AV: E=Sophos;i="4.75,355,1330905600"; d="scan'208";a="11714709" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 02 Apr 2012 08:16:27 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 2 Apr 2012 09:16:27 +0100 From: Paul Durrant To: Vasiliy Tolstov Date: Mon, 2 Apr 2012 09:16:48 +0100 Thread-Topic: [Xen-API] where find sources for windows software on xs-tools.iso? Thread-Index: Ac0QnixZW8fzIq/GSxKtumUk8S7yWwAClesA Message-ID: <291EDFCB1E9E224A99088639C4762022C812021BA9@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: vase@selfip.ru [mailto:vase@selfip.ru] On Behalf Of Vasiliy Tolstov > Sent: 02 April 2012 07:59 > To: Paul Durrant > Cc: xen-api@lists.xen.org > Subject: Re: [Xen-API] where find sources for windows software on xs- > tools.iso? > > 2012/3/30 Paul Durrant : > > I to access xenstore are completely private to the PV driver > implementation you happen to be using. > > Why? Vasiliy, There is no 'standard' in this respect for PV drivers. It would be good if there was one, but there isn't, so each different set of PV drivers will expose a different API for accessing xenstore. > I'm not understand what neededing to reinvent the wheel? If i want to > write some tool, that works under all windows xen drivers, that i need to > do? > > > 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. > > Where i can find WPI API references or some docs? > As I said, the WMI API is not published as yet. I'll see what I can do about getting approval to do this. 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 Tue Apr 03 14:32:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 03 Apr 2012 14:32: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 1SF4mh-0005I4-7h; Tue, 03 Apr 2012 14:32:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SF4mg-0005Hp-9p for xen-api@lists.xen.org; Tue, 03 Apr 2012 14:32:34 +0000 Received: from [85.158.143.35:20377] by server-2.bemta-4.messagelabs.com id D9/43-17550-10A0B7F4; Tue, 03 Apr 2012 14:32:33 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1333463549!17004866!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MjU1MA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19884 invoked from network); 3 Apr 2012 14:32:32 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Apr 2012 14:32:32 -0000 X-IronPort-AV: E=Sophos;i="4.75,363,1330905600"; d="scan'208";a="11748473" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Apr 2012 14:32:28 +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; Tue, 3 Apr 2012 15:32:28 +0100 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 1SF4ma-0005LN-AS; Tue, 03 Apr 2012 14:32:28 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1SF4ma-0004d2-7f; Tue, 03 Apr 2012 15:32:28 +0100 From: Ian Jackson MIME-Version: 1.0 Message-ID: <20347.2553.796551.427623@mariner.uk.xensource.com> Date: Tue, 3 Apr 2012 15:32:25 +0100 To: Ian Campbell Newsgroups: chiark.mail.xen.devel In-Reply-To: References: <1331732247.23971.438.camel@zakaz.uk.xensource.com> X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu) Cc: xen-api@lists.xen.org, Bamvor Jian Zhang , Jim Fehlig , xen-devel@lists.xen.org Subject: Re: [Xen-API] [Xen-devel] [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 Ian Campbell writes ("[Xen-devel] [PATCH] libxl: Document API and ABI compatibility guarantees"): > libxl: Document API and ABI compatibility guarantees. > > Signed-off-by: Ian Campbell Committed-by: Ian Jackson _______________________________________________ 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 Apr 03 14:32:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 03 Apr 2012 14:32: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 1SF4mh-0005I4-7h; Tue, 03 Apr 2012 14:32:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SF4mg-0005Hp-9p for xen-api@lists.xen.org; Tue, 03 Apr 2012 14:32:34 +0000 Received: from [85.158.143.35:20377] by server-2.bemta-4.messagelabs.com id D9/43-17550-10A0B7F4; Tue, 03 Apr 2012 14:32:33 +0000 X-Env-Sender: Ian.Jackson@eu.citrix.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1333463549!17004866!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MjU1MA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19884 invoked from network); 3 Apr 2012 14:32:32 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Apr 2012 14:32:32 -0000 X-IronPort-AV: E=Sophos;i="4.75,363,1330905600"; d="scan'208";a="11748473" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 03 Apr 2012 14:32:28 +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; Tue, 3 Apr 2012 15:32:28 +0100 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 1SF4ma-0005LN-AS; Tue, 03 Apr 2012 14:32:28 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.72) (envelope-from ) id 1SF4ma-0004d2-7f; Tue, 03 Apr 2012 15:32:28 +0100 From: Ian Jackson MIME-Version: 1.0 Message-ID: <20347.2553.796551.427623@mariner.uk.xensource.com> Date: Tue, 3 Apr 2012 15:32:25 +0100 To: Ian Campbell Newsgroups: chiark.mail.xen.devel In-Reply-To: References: <1331732247.23971.438.camel@zakaz.uk.xensource.com> X-Mailer: VM 8.1.0 under 23.2.1 (i486-pc-linux-gnu) Cc: xen-api@lists.xen.org, Bamvor Jian Zhang , Jim Fehlig , xen-devel@lists.xen.org Subject: Re: [Xen-API] [Xen-devel] [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 Ian Campbell writes ("[Xen-devel] [PATCH] libxl: Document API and ABI compatibility guarantees"): > libxl: Document API and ABI compatibility guarantees. > > Signed-off-by: Ian Campbell Committed-by: Ian Jackson _______________________________________________ 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 Apr 04 09:30:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 09:30: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 1SFMXp-0004PO-MW; Wed, 04 Apr 2012 09:30:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFMXo-0004PJ-9S for xen-api@lists.xensource.com; Wed, 04 Apr 2012 09:30:24 +0000 Received: from [85.158.139.83:25540] by server-3.bemta-5.messagelabs.com id 3D/F7-25237-FA41C7F4; Wed, 04 Apr 2012 09:30:23 +0000 X-Env-Sender: medhavini1991@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1333531822!22428647!1 X-Originating-IP: [209.85.215.171] 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 19136 invoked from network); 4 Apr 2012 09:30:22 -0000 Received: from mail-ey0-f171.google.com (HELO mail-ey0-f171.google.com) (209.85.215.171) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2012 09:30:22 -0000 Received: by eaal11 with SMTP id l11so29230eaa.30 for ; Wed, 04 Apr 2012 02:30:22 -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=zd8wfGBuJtmXDcGLXMjpIBttBgdQTzEIsB5bLqbEa4E=; b=VyQMFX9pV6ZdLwNPLIrvMQYxxPiRn51Qb57smXgfTDmIl8TqoeMZzNXjED8N7ZKQ3q MdiOHfKfXWWpFLarlVVsUbdq9ykwyjhqtXgWsoS+UiMUURN6ZCrHuwlsPzSHrVUN2Y8w usJM/GjIRsOD/0Fk3O0f7pCq6QhoswvchJ+0T8SwqNDHYcBtvjgJPtyNe549kLsDDDmH hgoVyp+a72POjFk9uCr/Hz9gVawIblVYhxqTmZXC9CzoU+zHWA3PXSBcDxj/iu74F1x3 NvnXbL5TZSx/1vDFT9kkO1X4ipq4FiQKeUtNXA4+QlWjQ1aGSsW/zuH3Xtr7exgsjxw7 CG5g== MIME-Version: 1.0 Received: by 10.213.27.24 with SMTP id g24mr1549205ebc.113.1333531821016; Wed, 04 Apr 2012 02:30:21 -0700 (PDT) Received: by 10.213.27.133 with HTTP; Wed, 4 Apr 2012 02:30:20 -0700 (PDT) Date: Wed, 4 Apr 2012 15:00:20 +0530 Message-ID: From: Medhavini Buchade To: xen-api Subject: [Xen-API] Unable to view squeeze graphical console 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 everyone, I have created a Debian Squeeze 32 bit VM. I can see the text console. I have edited the gdm.conf file and added the required lines in server section to configure VNC as per xen server virtual machine installation documentation. However I am unable to get a graphical console.(that button in xencenter is still disabled) Can anyone please help!! Thank you in advance. _______________________________________________ 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 Apr 04 09:30:35 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 09:30: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 1SFMXp-0004PO-MW; Wed, 04 Apr 2012 09:30:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFMXo-0004PJ-9S for xen-api@lists.xensource.com; Wed, 04 Apr 2012 09:30:24 +0000 Received: from [85.158.139.83:25540] by server-3.bemta-5.messagelabs.com id 3D/F7-25237-FA41C7F4; Wed, 04 Apr 2012 09:30:23 +0000 X-Env-Sender: medhavini1991@gmail.com X-Msg-Ref: server-2.tower-182.messagelabs.com!1333531822!22428647!1 X-Originating-IP: [209.85.215.171] 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 19136 invoked from network); 4 Apr 2012 09:30:22 -0000 Received: from mail-ey0-f171.google.com (HELO mail-ey0-f171.google.com) (209.85.215.171) by server-2.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2012 09:30:22 -0000 Received: by eaal11 with SMTP id l11so29230eaa.30 for ; Wed, 04 Apr 2012 02:30:22 -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=zd8wfGBuJtmXDcGLXMjpIBttBgdQTzEIsB5bLqbEa4E=; b=VyQMFX9pV6ZdLwNPLIrvMQYxxPiRn51Qb57smXgfTDmIl8TqoeMZzNXjED8N7ZKQ3q MdiOHfKfXWWpFLarlVVsUbdq9ykwyjhqtXgWsoS+UiMUURN6ZCrHuwlsPzSHrVUN2Y8w usJM/GjIRsOD/0Fk3O0f7pCq6QhoswvchJ+0T8SwqNDHYcBtvjgJPtyNe549kLsDDDmH hgoVyp+a72POjFk9uCr/Hz9gVawIblVYhxqTmZXC9CzoU+zHWA3PXSBcDxj/iu74F1x3 NvnXbL5TZSx/1vDFT9kkO1X4ipq4FiQKeUtNXA4+QlWjQ1aGSsW/zuH3Xtr7exgsjxw7 CG5g== MIME-Version: 1.0 Received: by 10.213.27.24 with SMTP id g24mr1549205ebc.113.1333531821016; Wed, 04 Apr 2012 02:30:21 -0700 (PDT) Received: by 10.213.27.133 with HTTP; Wed, 4 Apr 2012 02:30:20 -0700 (PDT) Date: Wed, 4 Apr 2012 15:00:20 +0530 Message-ID: From: Medhavini Buchade To: xen-api Subject: [Xen-API] Unable to view squeeze graphical console 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 everyone, I have created a Debian Squeeze 32 bit VM. I can see the text console. I have edited the gdm.conf file and added the required lines in server section to configure VNC as per xen server virtual machine installation documentation. However I am unable to get a graphical console.(that button in xencenter is still disabled) Can anyone please help!! Thank you in advance. _______________________________________________ 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 Apr 04 10:11:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 10:11: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 1SFNBa-0005dc-II; Wed, 04 Apr 2012 10:11:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFNBZ-0005dW-VK for xen-api@lists.xen.org; Wed, 04 Apr 2012 10:11:30 +0000 Received: from [85.158.143.99:30647] by server-1.bemta-4.messagelabs.com id EC/5F-20925-05E1C7F4; Wed, 04 Apr 2012 10:11:28 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1333534281!21752642!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 31053 invoked from network); 4 Apr 2012 10:11:27 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2012 10:11:27 -0000 Received: by bkcjg9 with SMTP id jg9so106860bkc.32 for ; Wed, 04 Apr 2012 03:11: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:references :in-reply-to:content-type:content-transfer-encoding; bh=LcChy6HDz/CG0fbnFMNLCgBwEosTRlmhq8ySyERbCm0=; b=JzKBMba976/sSCpsFCJlwqQMFobZ5XrfB+s/QGrM2dtiZn8g3zbolQZQjI+rkPHw2k 2Sqq0Dd2hHE+aPzhRd/vL0dEASr/6/+VabspHnkhgJLqzLCdg4qSjVLx9Uuy4yJIagGn O6w18VsL8K0DO0X7wkexqOsGDl/ybEvMDJy7zkrfKRgi36IOe/YD2F7TLlFhFRB+r7Ul PnSCYJg2HaLm7BrIF/VVbqQh953Ltp/XuZ7y1WlP0B0zF5h/BFiOHiScZSV6l8pNn+as Y4ExA2eJslhfRCeZgmtPpTSfxN3to7885NqaQag86r0uWkSXq635CuRJaurlausUSzDH 4U4Q== Received: by 10.204.133.205 with SMTP id g13mr1900361bkt.94.1333534281543; Wed, 04 Apr 2012 03:11:21 -0700 (PDT) Received: from [192.168.10.37] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id z14sm554222bky.15.2012.04.04.03.11.19 (version=SSLv3 cipher=OTHER); Wed, 04 Apr 2012 03:11:20 -0700 (PDT) Message-ID: <4F7C1E46.9000108@gmail.com> Date: Wed, 04 Apr 2012 14:11:18 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120402 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] Unable to view squeeze graphical console 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 If you talking about XCP, see: http://wiki.xensource.com/wiki/Xen_Cloud_Platform:_Access_to_VM_console On 04.04.2012 13:30, Medhavini Buchade wrote: > Hello everyone, > > I have created a Debian Squeeze 32 bit VM. I can see the text console. > I have edited the gdm.conf file and added the required lines in > server section to configure VNC as per xen server virtual machine > installation documentation. > However I am unable to get a graphical console.(that button in > xencenter is still disabled) > > Can anyone please help!! > > Thank you in advance. > > _______________________________________________ > 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 Apr 04 10:11:38 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 10:11: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 1SFNBa-0005dc-II; Wed, 04 Apr 2012 10:11:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFNBZ-0005dW-VK for xen-api@lists.xen.org; Wed, 04 Apr 2012 10:11:30 +0000 Received: from [85.158.143.99:30647] by server-1.bemta-4.messagelabs.com id EC/5F-20925-05E1C7F4; Wed, 04 Apr 2012 10:11:28 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1333534281!21752642!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 31053 invoked from network); 4 Apr 2012 10:11:27 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-11.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2012 10:11:27 -0000 Received: by bkcjg9 with SMTP id jg9so106860bkc.32 for ; Wed, 04 Apr 2012 03:11: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:references :in-reply-to:content-type:content-transfer-encoding; bh=LcChy6HDz/CG0fbnFMNLCgBwEosTRlmhq8ySyERbCm0=; b=JzKBMba976/sSCpsFCJlwqQMFobZ5XrfB+s/QGrM2dtiZn8g3zbolQZQjI+rkPHw2k 2Sqq0Dd2hHE+aPzhRd/vL0dEASr/6/+VabspHnkhgJLqzLCdg4qSjVLx9Uuy4yJIagGn O6w18VsL8K0DO0X7wkexqOsGDl/ybEvMDJy7zkrfKRgi36IOe/YD2F7TLlFhFRB+r7Ul PnSCYJg2HaLm7BrIF/VVbqQh953Ltp/XuZ7y1WlP0B0zF5h/BFiOHiScZSV6l8pNn+as Y4ExA2eJslhfRCeZgmtPpTSfxN3to7885NqaQag86r0uWkSXq635CuRJaurlausUSzDH 4U4Q== Received: by 10.204.133.205 with SMTP id g13mr1900361bkt.94.1333534281543; Wed, 04 Apr 2012 03:11:21 -0700 (PDT) Received: from [192.168.10.37] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id z14sm554222bky.15.2012.04.04.03.11.19 (version=SSLv3 cipher=OTHER); Wed, 04 Apr 2012 03:11:20 -0700 (PDT) Message-ID: <4F7C1E46.9000108@gmail.com> Date: Wed, 04 Apr 2012 14:11:18 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120402 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: In-Reply-To: Subject: Re: [Xen-API] Unable to view squeeze graphical console 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 If you talking about XCP, see: http://wiki.xensource.com/wiki/Xen_Cloud_Platform:_Access_to_VM_console On 04.04.2012 13:30, Medhavini Buchade wrote: > Hello everyone, > > I have created a Debian Squeeze 32 bit VM. I can see the text console. > I have edited the gdm.conf file and added the required lines in > server section to configure VNC as per xen server virtual machine > installation documentation. > However I am unable to get a graphical console.(that button in > xencenter is still disabled) > > Can anyone please help!! > > Thank you in advance. > > _______________________________________________ > 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 Apr 04 12:18:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 12:18:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFPAW-00079p-Ue; Wed, 04 Apr 2012 12:18:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFPAV-00079k-GA for xen-api@lists.xensource.com; Wed, 04 Apr 2012 12:18:31 +0000 Received: from [85.158.143.99:23261] by server-1.bemta-4.messagelabs.com id CC/46-20925-61C3C7F4; Wed, 04 Apr 2012 12:18:30 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-6.tower-216.messagelabs.com!1333541910!22269331!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11103 invoked from network); 4 Apr 2012 12:18:30 -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; 4 Apr 2012 12:18:30 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id toJV1i0093zjds103oJVH8; Wed, 04 Apr 2012 14:18:30 +0200 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id D478A74537; Wed, 4 Apr 2012 14:18:28 +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 GROMw48ojEiG; Wed, 4 Apr 2012 14:18:28 +0200 (CEST) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 4511574001; Wed, 4 Apr 2012 14:18:28 +0200 (CEST) Message-ID: <4F7C3C14.7020502@tranquil-it-systems.fr> Date: Wed, 04 Apr 2012 14:18:28 +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: Medhavini Buchade References: In-Reply-To: Cc: xen-api Subject: Re: [Xen-API] Unable to view squeeze graphical console 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 Medhavini, > I have created a Debian Squeeze 32 bit VM. I can see the text console. > I have edited the gdm.conf file and added the required lines in > server section to configure VNC as per xen server virtual machine > installation documentation. > However I am unable to get a graphical console.(that button in > xencenter is still disabled) > > Can anyone please help!! did you install the vm through the debian template or with the cdrom on = a full virt template? Stock Debian template gives you paravirtual VM, with no emulated graphic = card, so no graphic output in xencenter. However, you can still install vnc/nx/x2go/xrdp server and have a = graphical access to your VM through the network. Cheers, Denis > > Thank you in advance. > > _______________________________________________ > 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 Wed Apr 04 12:18:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 12:18:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFPAW-00079p-Ue; Wed, 04 Apr 2012 12:18:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFPAV-00079k-GA for xen-api@lists.xensource.com; Wed, 04 Apr 2012 12:18:31 +0000 Received: from [85.158.143.99:23261] by server-1.bemta-4.messagelabs.com id CC/46-20925-61C3C7F4; Wed, 04 Apr 2012 12:18:30 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-6.tower-216.messagelabs.com!1333541910!22269331!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11103 invoked from network); 4 Apr 2012 12:18:30 -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; 4 Apr 2012 12:18:30 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id toJV1i0093zjds103oJVH8; Wed, 04 Apr 2012 14:18:30 +0200 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id D478A74537; Wed, 4 Apr 2012 14:18:28 +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 GROMw48ojEiG; Wed, 4 Apr 2012 14:18:28 +0200 (CEST) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id 4511574001; Wed, 4 Apr 2012 14:18:28 +0200 (CEST) Message-ID: <4F7C3C14.7020502@tranquil-it-systems.fr> Date: Wed, 04 Apr 2012 14:18:28 +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: Medhavini Buchade References: In-Reply-To: Cc: xen-api Subject: Re: [Xen-API] Unable to view squeeze graphical console 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 Medhavini, > I have created a Debian Squeeze 32 bit VM. I can see the text console. > I have edited the gdm.conf file and added the required lines in > server section to configure VNC as per xen server virtual machine > installation documentation. > However I am unable to get a graphical console.(that button in > xencenter is still disabled) > > Can anyone please help!! did you install the vm through the debian template or with the cdrom on = a full virt template? Stock Debian template gives you paravirtual VM, with no emulated graphic = card, so no graphic output in xencenter. However, you can still install vnc/nx/x2go/xrdp server and have a = graphical access to your VM through the network. Cheers, Denis > > Thank you in advance. > > _______________________________________________ > 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 Wed Apr 04 13:47:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 13:47: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 1SFQYM-0008Nw-7m; Wed, 04 Apr 2012 13:47:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFQYK-0008Nr-GZ for xen-api@lists.xensource.com; Wed, 04 Apr 2012 13:47:12 +0000 Received: from [85.158.143.35:29167] by server-3.bemta-4.messagelabs.com id 83/E2-05853-FD05C7F4; Wed, 04 Apr 2012 13:47:11 +0000 X-Env-Sender: medhavini1991@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1333547230!11017115!1 X-Originating-IP: [74.125.83.43] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_10_20, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24654 invoked from network); 4 Apr 2012 13:47:11 -0000 Received: from mail-ee0-f43.google.com (HELO mail-ee0-f43.google.com) (74.125.83.43) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2012 13:47:11 -0000 Received: by eekc13 with SMTP id c13so140706eek.30 for ; Wed, 04 Apr 2012 06:47:10 -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=U/YFRY/fY77ye+h0rZ/QRj/cYEtnohf1Eb91Tm37/O4=; b=y9Xn8HIYPkaRD8T6zL8QOSlHXq+jJgOeWPuhMG2scvXmEJYbkqrUkZHuPFLL7iNsPJ bzzAVF9m0ddm/NQNC6QwfaA9KYZ0/oywIzImV7Vbqdfg9/5UCVDZ/EcwzxJae63salAe 2msDMSdfv6W487tZv76zm2LbmilzQWho73XZDoxNuf9m01K8zQT7iDiJ27m5QmS/QVI/ DPDcmVCYcNUaHDHygt9Cj6dETbSVSvZwiv88GHH5pBWcboHs6e+6gfplyk1XAnHMRoww gKn2wK8U+IzWjG1ibpk1gKLB+tE/4YIU0K7xvA3lPJBShSzm/M9NZYKhuEdG1aE/j9ME DY5g== MIME-Version: 1.0 Received: by 10.14.98.75 with SMTP id u51mr3139954eef.35.1333547230458; Wed, 04 Apr 2012 06:47:10 -0700 (PDT) Received: by 10.213.27.133 with HTTP; Wed, 4 Apr 2012 06:47:10 -0700 (PDT) Date: Wed, 4 Apr 2012 19:17:10 +0530 Message-ID: From: Medhavini Buchade To: xen-api Subject: Re: [Xen-API] Unable to view squeeze graphical console 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="===============8016297527938658705==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8016297527938658705== Content-Type: multipart/alternative; boundary=bcaec517a722f6758004bcdaa8bd --bcaec517a722f6758004bcdaa8bd Content-Type: text/plain; charset=ISO-8859-1 Hello thank you for replying Denis. I have installed Debian Squeeze using the template given by XCP and then using network repository mirror. Actually I had initially installed Debian Lenny using the same procedure. I was also able to get the graphical console for it using steps given in documentation (editing gdm.config, etc). But when I wanted to create a VM of Lenny again I found that its removed from the repository. So I tried to follow the same steps for Squeeze. But I was unable to get graphical console. Also one more weird thing that I observed is I couldn't find menu.lst in my Squeeze. Is this normal (as I am doing this first time I really don't know much) ?? I did not get any error during installation. Thank you. --bcaec517a722f6758004bcdaa8bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello=A0
thank you for replying Denis.

I have = installed Debian Squeeze using the template given by XCP and then using net= work repository mirror.
Actually I had initially installed Debian= Lenny using the same procedure. I was also able to get the graphical conso= le for it using steps given in documentation (editing gdm.config, etc). But= when I wanted to create a VM of Lenny again I found that its removed from = the repository. So I tried to follow the same steps for Squeeze. But I was = unable to get graphical console.=A0
Also one more weird thing that I observed is I couldn't find menu.= lst in my Squeeze. Is this normal (as I am doing this first time I really d= on't know much) ?? I did not get any error during installation.

Thank you.
--bcaec517a722f6758004bcdaa8bd-- --===============8016297527938658705== 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 --===============8016297527938658705==-- From xen-api-bounces@lists.xen.org Wed Apr 04 13:47:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 13:47: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 1SFQYM-0008Nw-7m; Wed, 04 Apr 2012 13:47:14 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFQYK-0008Nr-GZ for xen-api@lists.xensource.com; Wed, 04 Apr 2012 13:47:12 +0000 Received: from [85.158.143.35:29167] by server-3.bemta-4.messagelabs.com id 83/E2-05853-FD05C7F4; Wed, 04 Apr 2012 13:47:11 +0000 X-Env-Sender: medhavini1991@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1333547230!11017115!1 X-Originating-IP: [74.125.83.43] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_10_20, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24654 invoked from network); 4 Apr 2012 13:47:11 -0000 Received: from mail-ee0-f43.google.com (HELO mail-ee0-f43.google.com) (74.125.83.43) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Apr 2012 13:47:11 -0000 Received: by eekc13 with SMTP id c13so140706eek.30 for ; Wed, 04 Apr 2012 06:47:10 -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=U/YFRY/fY77ye+h0rZ/QRj/cYEtnohf1Eb91Tm37/O4=; b=y9Xn8HIYPkaRD8T6zL8QOSlHXq+jJgOeWPuhMG2scvXmEJYbkqrUkZHuPFLL7iNsPJ bzzAVF9m0ddm/NQNC6QwfaA9KYZ0/oywIzImV7Vbqdfg9/5UCVDZ/EcwzxJae63salAe 2msDMSdfv6W487tZv76zm2LbmilzQWho73XZDoxNuf9m01K8zQT7iDiJ27m5QmS/QVI/ DPDcmVCYcNUaHDHygt9Cj6dETbSVSvZwiv88GHH5pBWcboHs6e+6gfplyk1XAnHMRoww gKn2wK8U+IzWjG1ibpk1gKLB+tE/4YIU0K7xvA3lPJBShSzm/M9NZYKhuEdG1aE/j9ME DY5g== MIME-Version: 1.0 Received: by 10.14.98.75 with SMTP id u51mr3139954eef.35.1333547230458; Wed, 04 Apr 2012 06:47:10 -0700 (PDT) Received: by 10.213.27.133 with HTTP; Wed, 4 Apr 2012 06:47:10 -0700 (PDT) Date: Wed, 4 Apr 2012 19:17:10 +0530 Message-ID: From: Medhavini Buchade To: xen-api Subject: Re: [Xen-API] Unable to view squeeze graphical console 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="===============8016297527938658705==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8016297527938658705== Content-Type: multipart/alternative; boundary=bcaec517a722f6758004bcdaa8bd --bcaec517a722f6758004bcdaa8bd Content-Type: text/plain; charset=ISO-8859-1 Hello thank you for replying Denis. I have installed Debian Squeeze using the template given by XCP and then using network repository mirror. Actually I had initially installed Debian Lenny using the same procedure. I was also able to get the graphical console for it using steps given in documentation (editing gdm.config, etc). But when I wanted to create a VM of Lenny again I found that its removed from the repository. So I tried to follow the same steps for Squeeze. But I was unable to get graphical console. Also one more weird thing that I observed is I couldn't find menu.lst in my Squeeze. Is this normal (as I am doing this first time I really don't know much) ?? I did not get any error during installation. Thank you. --bcaec517a722f6758004bcdaa8bd Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello=A0
thank you for replying Denis.

I have = installed Debian Squeeze using the template given by XCP and then using net= work repository mirror.
Actually I had initially installed Debian= Lenny using the same procedure. I was also able to get the graphical conso= le for it using steps given in documentation (editing gdm.config, etc). But= when I wanted to create a VM of Lenny again I found that its removed from = the repository. So I tried to follow the same steps for Squeeze. But I was = unable to get graphical console.=A0
Also one more weird thing that I observed is I couldn't find menu.= lst in my Squeeze. Is this normal (as I am doing this first time I really d= on't know much) ?? I did not get any error during installation.

Thank you.
--bcaec517a722f6758004bcdaa8bd-- --===============8016297527938658705== 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 --===============8016297527938658705==-- From xen-api-bounces@lists.xen.org Wed Apr 04 14:03:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 14:03:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFQnd-00009k-Rx; Wed, 04 Apr 2012 14:03:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFQnc-00009Y-2n for xen-api@lists.xen.org; Wed, 04 Apr 2012 14:03:00 +0000 Received: from [85.158.138.51:58898] by server-5.bemta-3.messagelabs.com id 4F/11-24278-3945C7F4; Wed, 04 Apr 2012 14:02:59 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-10.tower-174.messagelabs.com!1333548177!20810906!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14299 invoked from network); 4 Apr 2012 14:02:58 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-10.tower-174.messagelabs.com with SMTP; 4 Apr 2012 14:02:58 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id tq2x1i0053zjds103q2xsL; Wed, 04 Apr 2012 16:02:57 +0200 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id F104D74537 for ; Wed, 4 Apr 2012 16:02:56 +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 i99hmsjkYTRd; Wed, 4 Apr 2012 16:02:55 +0200 (CEST) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CDFAC74001; Wed, 4 Apr 2012 16:02:55 +0200 (CEST) Message-ID: <4F7C548F.6060102@tranquil-it-systems.fr> Date: Wed, 04 Apr 2012 16:02:55 +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 References: <4F71DE7E.5090704@tranquil-it-systems.fr> In-Reply-To: <4F71DE7E.5090704@tranquil-it-systems.fr> Subject: Re: [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, > 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? since that vhd chain meltdown, I've exported all vms, format the SR, do = a fresh xcp 1.1 install on the 3 nodes and re-imported all vms. The SAN = has been very busy overnight, but everything is back to normal. For the time being I'll try to avoid snapshotting in order to avoid = coalescing and wait for XCP 1.5. By the way, I was puzzled by the timeline for this issue : the hotfix = for this bug went out on march 10th 2012, while it was checked in in = github on december 9th, and the hotfix source code itself is dated on = december 6th... Thanks, Denis > > 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 Wed Apr 04 14:03:11 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 14:03:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFQnd-00009k-Rx; Wed, 04 Apr 2012 14:03:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFQnc-00009Y-2n for xen-api@lists.xen.org; Wed, 04 Apr 2012 14:03:00 +0000 Received: from [85.158.138.51:58898] by server-5.bemta-3.messagelabs.com id 4F/11-24278-3945C7F4; Wed, 04 Apr 2012 14:02:59 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-10.tower-174.messagelabs.com!1333548177!20810906!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14299 invoked from network); 4 Apr 2012 14:02:58 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-10.tower-174.messagelabs.com with SMTP; 4 Apr 2012 14:02:58 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id tq2x1i0053zjds103q2xsL; Wed, 04 Apr 2012 16:02:57 +0200 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id F104D74537 for ; Wed, 4 Apr 2012 16:02:56 +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 i99hmsjkYTRd; Wed, 4 Apr 2012 16:02:55 +0200 (CEST) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CDFAC74001; Wed, 4 Apr 2012 16:02:55 +0200 (CEST) Message-ID: <4F7C548F.6060102@tranquil-it-systems.fr> Date: Wed, 04 Apr 2012 16:02:55 +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 References: <4F71DE7E.5090704@tranquil-it-systems.fr> In-Reply-To: <4F71DE7E.5090704@tranquil-it-systems.fr> Subject: Re: [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, > 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? since that vhd chain meltdown, I've exported all vms, format the SR, do = a fresh xcp 1.1 install on the 3 nodes and re-imported all vms. The SAN = has been very busy overnight, but everything is back to normal. For the time being I'll try to avoid snapshotting in order to avoid = coalescing and wait for XCP 1.5. By the way, I was puzzled by the timeline for this issue : the hotfix = for this bug went out on march 10th 2012, while it was checked in in = github on december 9th, and the hotfix source code itself is dated on = december 6th... Thanks, Denis > > 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 Wed Apr 04 14:17:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 14:17: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 1SFR1i-0000LU-0K; Wed, 04 Apr 2012 14:17:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFR1g-0000LP-Pk for xen-api@lists.xensource.com; Wed, 04 Apr 2012 14:17:33 +0000 Received: from [85.158.138.51:6289] by server-10.bemta-3.messagelabs.com id F0/18-15637-CF75C7F4; Wed, 04 Apr 2012 14:17:32 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-15.tower-174.messagelabs.com!1333549051!18971910!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6230 invoked from network); 4 Apr 2012 14:17:31 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-15.tower-174.messagelabs.com with SMTP; 4 Apr 2012 14:17:31 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id tqHX1i0023zjds103qHXkU; Wed, 04 Apr 2012 16:17:31 +0200 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id DF55C7453A; Wed, 4 Apr 2012 16:17:30 +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 AMLLgb6VhWe2; Wed, 4 Apr 2012 16:17:30 +0200 (CEST) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CF53674537; Wed, 4 Apr 2012 16:17:29 +0200 (CEST) Message-ID: <4F7C57F9.1010605@tranquil-it-systems.fr> Date: Wed, 04 Apr 2012 16:17:29 +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: Medhavini Buchade References: In-Reply-To: Cc: xen-api Subject: Re: [Xen-API] Unable to view squeeze graphical console 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 Medhavini, > thank you for replying Denis. you are welcome :-) > I have installed Debian Squeeze using the template given by XCP and then > using network repository mirror. so that is a pv install. > Actually I had initially installed Debian Lenny using the same > procedure. I was also able to get the graphical console for it using > steps given in documentation (editing gdm.config, etc). But when I > wanted to create a VM of Lenny again I found that its removed from the > repository. So I tried to follow the same steps for Squeeze. But I was > unable to get graphical console. if you still have the lenny vm around and urging for a graphical frame = buffer, you can export/import it on your new server. The citrix template list is quite restrictive, but I guess it is the = template list with commercial support from citrix. You can install many = other non listed os without much hassle actually. For the squeeze PV vm, you can convert it to HVM so you have a graphical = frame buffer. I think the following line should do it (you may also have = to set your hard drive to "bootable") : xe vm-param-set HVM-boot-policy=3D"BIOS order" uuid=3D xe vm-param-set PV-args=3D"" uuid=3D xe vm-param-set PV-bootloader-args=3D"" uuid=3D > Also one more weird thing that I observed is I couldn't find menu.lst in > my Squeeze. Is this normal (as I am doing this first time I really don't > know much) ?? I did not get any error during installation. Grub 2? Cheers, Denis > > Thank you. > > > 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 Wed Apr 04 14:17:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 04 Apr 2012 14:17: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 1SFR1i-0000LU-0K; Wed, 04 Apr 2012 14:17:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFR1g-0000LP-Pk for xen-api@lists.xensource.com; Wed, 04 Apr 2012 14:17:33 +0000 Received: from [85.158.138.51:6289] by server-10.bemta-3.messagelabs.com id F0/18-15637-CF75C7F4; Wed, 04 Apr 2012 14:17:32 +0000 X-Env-Sender: denis.cardon@tranquil-it-systems.fr X-Msg-Ref: server-15.tower-174.messagelabs.com!1333549051!18971910!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6230 invoked from network); 4 Apr 2012 14:17:31 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-15.tower-174.messagelabs.com with SMTP; 4 Apr 2012 14:17:31 -0000 Received: from srvzimbra.tranquilit.local ([193.252.46.185]) by mwinf5d59 with ME id tqHX1i0023zjds103qHXkU; Wed, 04 Apr 2012 16:17:31 +0200 Received: from localhost (localhost [127.0.0.1]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id DF55C7453A; Wed, 4 Apr 2012 16:17:30 +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 AMLLgb6VhWe2; Wed, 4 Apr 2012 16:17:30 +0200 (CEST) Received: from srvlts1.tranquilit.local (srvlts1.tranquilit.local [192.168.149.14]) by srvzimbra.tranquilit.local (Postfix) with ESMTP id CF53674537; Wed, 4 Apr 2012 16:17:29 +0200 (CEST) Message-ID: <4F7C57F9.1010605@tranquil-it-systems.fr> Date: Wed, 04 Apr 2012 16:17:29 +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: Medhavini Buchade References: In-Reply-To: Cc: xen-api Subject: Re: [Xen-API] Unable to view squeeze graphical console 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 Medhavini, > thank you for replying Denis. you are welcome :-) > I have installed Debian Squeeze using the template given by XCP and then > using network repository mirror. so that is a pv install. > Actually I had initially installed Debian Lenny using the same > procedure. I was also able to get the graphical console for it using > steps given in documentation (editing gdm.config, etc). But when I > wanted to create a VM of Lenny again I found that its removed from the > repository. So I tried to follow the same steps for Squeeze. But I was > unable to get graphical console. if you still have the lenny vm around and urging for a graphical frame = buffer, you can export/import it on your new server. The citrix template list is quite restrictive, but I guess it is the = template list with commercial support from citrix. You can install many = other non listed os without much hassle actually. For the squeeze PV vm, you can convert it to HVM so you have a graphical = frame buffer. I think the following line should do it (you may also have = to set your hard drive to "bootable") : xe vm-param-set HVM-boot-policy=3D"BIOS order" uuid=3D xe vm-param-set PV-args=3D"" uuid=3D xe vm-param-set PV-bootloader-args=3D"" uuid=3D > Also one more weird thing that I observed is I couldn't find menu.lst in > my Squeeze. Is this normal (as I am doing this first time I really don't > know much) ?? I did not get any error during installation. Grub 2? Cheers, Denis > > Thank you. > > > 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 Thu Apr 05 09:23:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 05 Apr 2012 09:23: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 1SFiuZ-0003qQ-Uh; Thu, 05 Apr 2012 09:23:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFiuX-0003qG-CU for xen-api@lists.xen.org; Thu, 05 Apr 2012 09:23:21 +0000 Received: from [85.158.143.99:53325] by server-3.bemta-4.messagelabs.com id 5D/49-05853-8846D7F4; Thu, 05 Apr 2012 09:23:20 +0000 X-Env-Sender: the.kazak@gmail.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1333617799!22470462!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 15545 invoked from network); 5 Apr 2012 09:23:19 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Apr 2012 09:23:19 -0000 Received: by bkcjg9 with SMTP id jg9so1293998bkc.32 for ; Thu, 05 Apr 2012 02:23:19 -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=ozNx+xdKj3m499f6n8WzLq2OO5t/ksFWdX6wb9GLSY8=; b=uitzRoyc0qjJ4mzMX36YdX767JhCj8MTYIKaIbt6s3b/xXnSd/33edSmmDGxlLTMXE VXc2rbeFToJMifeJIWZxLXd6gfqguOkuhLWjWiVVV/5XlMQbPzl8Eitp3LPzvvWUV2lq 1F7VWrWottXU65BzqAFiZsDJQIZyCJb7srDDZ4bktJIFX/FvgwozwSV3Txr3l+XwBpO3 Jcj2uT9ctkn88k965x4OKuMrlR5W/6QDmV5BYsr0kg4QROGt6GXZqQvMKrIGxG9nx1JS FpYBtcATaRludKxbo/0mln4lZ4ChzkBV5pGYkxBLk/xHIZqmIOxB4r0VLhKEotvvudKR 7lWg== Received: by 10.204.128.201 with SMTP id l9mr786292bks.90.1333617798871; Thu, 05 Apr 2012 02:23:18 -0700 (PDT) Received: from [212.50.0.54] (purple.varna.spnet.net. [212.50.0.54]) by mx.google.com with ESMTPS id f5sm7372018bke.9.2012.04.05.02.23.17 (version=SSLv3 cipher=OTHER); Thu, 05 Apr 2012 02:23:18 -0700 (PDT) Message-ID: <4F7D6480.6040704@gmail.com> Date: Thu, 05 Apr 2012 12:23:12 +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, xen-devel@lists.xen.org Content-Type: multipart/mixed; boundary="------------000503040804060600000300" Subject: [Xen-API] xe vdi-create failure ot local SR type=file and type=ext 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. --------------000503040804060600000300 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, have permanent failure when try to create VDI on local SR type=file or type=ext. On both types it failed with the same error: SR_BACKEND_FAILURE_78 VDI Creation failed [opterr=error 127] I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) Is it a bug, or am I missing something? Anybody managed to workaround this problem? Here is a short extract from xcp-xapi.log id=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab type=user name-label=test virtual-size=1GiB username=root password=null [20120403T07:57:53.973Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] Session.create trackid=1ef3448b63e70822073569022044e96b pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120403T07:57:53.974Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] Attempting to open /var/lib/xcp/xapi [20120403T07:57:53.975Z|debug|hyperion|547 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:4cab7e7aa9ae created by task D:93575fa7333c [20120403T07:57:53.982Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|audit] VDI.create: SR = 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab (Local storage)'; name label = 'test' [20120403T07:57:53.983Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Marking SR for VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) [20120403T07:57:53.984Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|storage_impl] VDI.create task:OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a sr:ba4e9e1a-bc42-0dc9-af0e-5db2905666ab vdi_info:{"vdi": "", "name_label": "test", "name_description": "", "ty": "user", "metadata_of_pool": "", "is_a_snapshot": false, "snapshot_time": "19700101T00:00:00Z", "snapshot_of": "", "read_only": false, "virtual_size": 1073741824, "physical_utilisation": 0} params: [20120403T07:57:53.984Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dummytaskhelper] task VDI.create D:db9f2e113fee created by task R:efdfb350d7ac [20120403T07:57:53.986Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.create trackid=654ed4437d52fe9cdd8e5d98a5955526 pool=false uname= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120403T07:57:53.987Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Attempting to open /var/lib/xcp/xapi [20120403T07:57:53.987Z|debug|hyperion|548 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:3829e36dbb97 created by task D:6ec167aaa83d [20120403T07:57:54.066Z|debug|hyperion|549 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:host.get_other_config D:c813aaba73c4 created by task D:db9f2e113fee [20120403T07:57:54.071Z|debug|hyperion|549 UNIX /var/lib/xcp/xapi||http_critical] Premature termination of connection! [20120403T07:57:54.109Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at sm_exec.ml:220.7-69 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.109Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.destroy trackid=654ed4437d52fe9cdd8e5d98a5955526 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at pervasiveext.ml:26.22-25 -> server_helpers.ml:76.11-23 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Server_helpers.exec exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at pervasiveext.ml:26.22-25 -> sm.ml:132.25-98 -> storage_access.ml:259.36-331 -> storage_access.ml:257.28-492 -> server_helpers.ml:76.11-23 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] Server_helpers.exec exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at storage_access.ml:449.8-47 -> message_forwarding.ml:233.25-44 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Unmarking SR after VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) [20120403T07:57:54.111Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at pervasiveext.ml:26.22-25 -> server.ml:24034.78-280 -> rbac.ml:229.16-23 [20120403T07:57:54.112Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at rbac.ml:238.10-15 -> server_helpers.ml:79.11-41 [20120403T07:57:54.112Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] Server_helpers.exec exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] [20120403T07:57:54.112Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.112Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.114Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|backtrace] Raised at pervasiveext.ml:26.22-25 -> server_helpers.ml:153.10-106 -> server.ml:24035.19-190 -> server_helpers.ml:119.4-7 [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||xapi] Raised at client.ml:6.37-75 -> client.ml:9043.48-106 -> cli_operations.ml:1082.11-187 -> xapi_cli.ml:112.18-56 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.117Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|session.logout D:2d486a4a5b26|xapi] Session.destroy trackid=1ef3448b63e70822073569022044e96b [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||backtrace] Raised at pervasiveext.ml:26.22-25 -> xapi_cli.ml:111.2-138 -> xapi_cli.ml:205.7-44 -> xapi_cli.ml:257.4-23 [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] Xapi_cli.exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 Thanks, Dimitar Kazkov --------------000503040804060600000300 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== --------------000503040804060600000300 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 --------------000503040804060600000300-- From xen-api-bounces@lists.xen.org Thu Apr 05 09:23:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 05 Apr 2012 09:23: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 1SFiuZ-0003qQ-Uh; Thu, 05 Apr 2012 09:23:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFiuX-0003qG-CU for xen-api@lists.xen.org; Thu, 05 Apr 2012 09:23:21 +0000 Received: from [85.158.143.99:53325] by server-3.bemta-4.messagelabs.com id 5D/49-05853-8846D7F4; Thu, 05 Apr 2012 09:23:20 +0000 X-Env-Sender: the.kazak@gmail.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1333617799!22470462!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 15545 invoked from network); 5 Apr 2012 09:23:19 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-9.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 5 Apr 2012 09:23:19 -0000 Received: by bkcjg9 with SMTP id jg9so1293998bkc.32 for ; Thu, 05 Apr 2012 02:23:19 -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=ozNx+xdKj3m499f6n8WzLq2OO5t/ksFWdX6wb9GLSY8=; b=uitzRoyc0qjJ4mzMX36YdX767JhCj8MTYIKaIbt6s3b/xXnSd/33edSmmDGxlLTMXE VXc2rbeFToJMifeJIWZxLXd6gfqguOkuhLWjWiVVV/5XlMQbPzl8Eitp3LPzvvWUV2lq 1F7VWrWottXU65BzqAFiZsDJQIZyCJb7srDDZ4bktJIFX/FvgwozwSV3Txr3l+XwBpO3 Jcj2uT9ctkn88k965x4OKuMrlR5W/6QDmV5BYsr0kg4QROGt6GXZqQvMKrIGxG9nx1JS FpYBtcATaRludKxbo/0mln4lZ4ChzkBV5pGYkxBLk/xHIZqmIOxB4r0VLhKEotvvudKR 7lWg== Received: by 10.204.128.201 with SMTP id l9mr786292bks.90.1333617798871; Thu, 05 Apr 2012 02:23:18 -0700 (PDT) Received: from [212.50.0.54] (purple.varna.spnet.net. [212.50.0.54]) by mx.google.com with ESMTPS id f5sm7372018bke.9.2012.04.05.02.23.17 (version=SSLv3 cipher=OTHER); Thu, 05 Apr 2012 02:23:18 -0700 (PDT) Message-ID: <4F7D6480.6040704@gmail.com> Date: Thu, 05 Apr 2012 12:23:12 +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, xen-devel@lists.xen.org Content-Type: multipart/mixed; boundary="------------000503040804060600000300" Subject: [Xen-API] xe vdi-create failure ot local SR type=file and type=ext 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. --------------000503040804060600000300 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, have permanent failure when try to create VDI on local SR type=file or type=ext. On both types it failed with the same error: SR_BACKEND_FAILURE_78 VDI Creation failed [opterr=error 127] I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) Is it a bug, or am I missing something? Anybody managed to workaround this problem? Here is a short extract from xcp-xapi.log id=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab type=user name-label=test virtual-size=1GiB username=root password=null [20120403T07:57:53.973Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] Session.create trackid=1ef3448b63e70822073569022044e96b pool=false uname=root is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120403T07:57:53.974Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] Attempting to open /var/lib/xcp/xapi [20120403T07:57:53.975Z|debug|hyperion|547 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:4cab7e7aa9ae created by task D:93575fa7333c [20120403T07:57:53.982Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|audit] VDI.create: SR = 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab (Local storage)'; name label = 'test' [20120403T07:57:53.983Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Marking SR for VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) [20120403T07:57:53.984Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|storage_impl] VDI.create task:OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a sr:ba4e9e1a-bc42-0dc9-af0e-5db2905666ab vdi_info:{"vdi": "", "name_label": "test", "name_description": "", "ty": "user", "metadata_of_pool": "", "is_a_snapshot": false, "snapshot_time": "19700101T00:00:00Z", "snapshot_of": "", "read_only": false, "virtual_size": 1073741824, "physical_utilisation": 0} params: [20120403T07:57:53.984Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dummytaskhelper] task VDI.create D:db9f2e113fee created by task R:efdfb350d7ac [20120403T07:57:53.986Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.create trackid=654ed4437d52fe9cdd8e5d98a5955526 pool=false uname= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 [20120403T07:57:53.987Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Attempting to open /var/lib/xcp/xapi [20120403T07:57:53.987Z|debug|hyperion|548 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid D:3829e36dbb97 created by task D:6ec167aaa83d [20120403T07:57:54.066Z|debug|hyperion|549 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:host.get_other_config D:c813aaba73c4 created by task D:db9f2e113fee [20120403T07:57:54.071Z|debug|hyperion|549 UNIX /var/lib/xcp/xapi||http_critical] Premature termination of connection! [20120403T07:57:54.109Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at sm_exec.ml:220.7-69 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.109Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.destroy trackid=654ed4437d52fe9cdd8e5d98a5955526 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at pervasiveext.ml:26.22-25 -> server_helpers.ml:76.11-23 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Server_helpers.exec exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at pervasiveext.ml:26.22-25 -> sm.ml:132.25-98 -> storage_access.ml:259.36-331 -> storage_access.ml:257.28-492 -> server_helpers.ml:76.11-23 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] Server_helpers.exec exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at storage_access.ml:449.8-47 -> message_forwarding.ml:233.25-44 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.110Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Unmarking SR after VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) [20120403T07:57:54.111Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at pervasiveext.ml:26.22-25 -> server.ml:24034.78-280 -> rbac.ml:229.16-23 [20120403T07:57:54.112Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at rbac.ml:238.10-15 -> server_helpers.ml:79.11-41 [20120403T07:57:54.112Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] Server_helpers.exec exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] [20120403T07:57:54.112Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.112Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120403T07:57:54.114Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|backtrace] Raised at pervasiveext.ml:26.22-25 -> server_helpers.ml:153.10-106 -> server.ml:24035.19-190 -> server_helpers.ml:119.4-7 [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||xapi] Raised at client.ml:6.37-75 -> client.ml:9043.48-106 -> cli_operations.ml:1082.11-187 -> xapi_cli.ml:112.18-56 -> pervasiveext.ml:22.2-9 [20120403T07:57:54.117Z| info|hyperion|546 UNIX /var/lib/xcp/xapi|session.logout D:2d486a4a5b26|xapi] Session.destroy trackid=1ef3448b63e70822073569022044e96b [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||backtrace] Raised at pervasiveext.ml:26.22-25 -> xapi_cli.ml:111.2-138 -> xapi_cli.ml:205.7-44 -> xapi_cli.ml:257.4-23 [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] Xapi_cli.exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 Thanks, Dimitar Kazkov --------------000503040804060600000300 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== --------------000503040804060600000300 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 --------------000503040804060600000300-- From xen-api-bounces@lists.xen.org Thu Apr 05 10:08:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 05 Apr 2012 10:08:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFjbz-00057r-J0; Thu, 05 Apr 2012 10:08:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFjbx-00057i-IZ for xen-api@lists.xen.org; Thu, 05 Apr 2012 10:08:13 +0000 Received: from [85.158.143.35:10600] by server-1.bemta-4.messagelabs.com id BE/99-20925-C0F6D7F4; Thu, 05 Apr 2012 10:08:12 +0000 X-Env-Sender: Jonathan.Ludlam@eu.citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1333620490!7570595!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MzE0NA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27477 invoked from network); 5 Apr 2012 10:08:11 -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; 5 Apr 2012 10:08:11 -0000 X-IronPort-AV: E=Sophos;i="4.75,375,1330905600"; d="scan'208";a="11789319" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Apr 2012 10:08:10 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 5 Apr 2012 11:08:10 +0100 From: Jonathan Ludlam To: Dimitar Kazakov Date: Thu, 5 Apr 2012 11:08:08 +0100 Thread-Topic: [Xen-API] xe vdi-create failure ot local SR type=file and type=ext Thread-Index: Ac0TFABqcTeHZXqNSuqhLzKIJ11u8A== Message-ID: <7549B613-6EB9-4DD8-9741-C0D8556D0176@eu.citrix.com> References: <4F7D6480.6040704@gmail.com> In-Reply-To: <4F7D6480.6040704@gmail.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-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe vdi-create failure ot local SR type=file and type=ext 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 log snippet doesn't have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. Jon On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > Hi, > have permanent failure when try to create VDI on local SR type=file or > type=ext. On both types it failed with the same error: > SR_BACKEND_FAILURE_78 > VDI Creation failed [opterr=error 127] > > I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian > 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) > > Is it a bug, or am I missing something? Anybody managed to workaround > this problem? > > > Here is a short extract from xcp-xapi.log > > id=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab type=user name-label=test > virtual-size=1GiB username=root password=null > [20120403T07:57:53.973Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] > Session.create trackid=1ef3448b63e70822073569022044e96b pool=false > uname=root is_local_superuser=true auth_user_sid= > parent=trackid=9834f5af41c964e225f24279aefe4e49 > [20120403T07:57:53.974Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] > Attempting to open /var/lib/xcp/xapi > [20120403T07:57:53.975Z|debug|hyperion|547 UNIX > /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid > D:4cab7e7aa9ae created by task D:93575fa7333c > [20120403T07:57:53.982Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|audit] VDI.create: SR = > 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab (Local storage)'; name label = 'test' > [20120403T07:57:53.983Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Marking SR for > VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) > [20120403T07:57:53.984Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|storage_impl] VDI.create > task:OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a > sr:ba4e9e1a-bc42-0dc9-af0e-5db2905666ab vdi_info:{"vdi": "", > "name_label": "test", "name_description": "", "ty": "user", > "metadata_of_pool": "", "is_a_snapshot": false, "snapshot_time": > "19700101T00:00:00Z", "snapshot_of": "", "read_only": false, > "virtual_size": 1073741824, "physical_utilisation": 0} params: > [20120403T07:57:53.984Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dummytaskhelper] task > VDI.create D:db9f2e113fee created by task R:efdfb350d7ac > [20120403T07:57:53.986Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.create > trackid=654ed4437d52fe9cdd8e5d98a5955526 pool=false uname= > is_local_superuser=true auth_user_sid= > parent=trackid=9834f5af41c964e225f24279aefe4e49 > [20120403T07:57:53.987Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Attempting to open > /var/lib/xcp/xapi > [20120403T07:57:53.987Z|debug|hyperion|548 UNIX > /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid > D:3829e36dbb97 created by task D:6ec167aaa83d > [20120403T07:57:54.066Z|debug|hyperion|549 UNIX > /var/lib/xcp/xapi||dummytaskhelper] task dispatch:host.get_other_config > D:c813aaba73c4 created by task D:db9f2e113fee > [20120403T07:57:54.071Z|debug|hyperion|549 UNIX > /var/lib/xcp/xapi||http_critical] Premature termination of connection! > [20120403T07:57:54.109Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at > sm_exec.ml:220.7-69 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.109Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.destroy > trackid=654ed4437d52fe9cdd8e5d98a5955526 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at > pervasiveext.ml:26.22-25 -> server_helpers.ml:76.11-23 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Server_helpers.exec > exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation > failed [opterr=error 127]; ] > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at > server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at > pervasiveext.ml:26.22-25 -> sm.ml:132.25-98 -> > storage_access.ml:259.36-331 -> storage_access.ml:257.28-492 -> > server_helpers.ml:76.11-23 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] > Server_helpers.exec exception_handler: Got exception > SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at > server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at > storage_access.ml:449.8-47 -> message_forwarding.ml:233.25-44 -> > pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Unmarking SR after > VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) > [20120403T07:57:54.111Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at > pervasiveext.ml:26.22-25 -> server.ml:24034.78-280 -> rbac.ml:229.16-23 > [20120403T07:57:54.112Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at > rbac.ml:238.10-15 -> server_helpers.ml:79.11-41 > [20120403T07:57:54.112Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] > Server_helpers.exec exception_handler: Got exception > SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] > [20120403T07:57:54.112Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.112Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.114Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at > server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.115Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.115Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.115Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|backtrace] Raised > at pervasiveext.ml:26.22-25 -> server_helpers.ml:153.10-106 -> > server.ml:24035.19-190 -> server_helpers.ml:119.4-7 > [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||xapi] > Raised at client.ml:6.37-75 -> client.ml:9043.48-106 -> > cli_operations.ml:1082.11-187 -> xapi_cli.ml:112.18-56 -> > pervasiveext.ml:22.2-9 > [20120403T07:57:54.117Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|session.logout D:2d486a4a5b26|xapi] Session.destroy > trackid=1ef3448b63e70822073569022044e96b > [20120403T07:57:54.118Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi||backtrace] Raised at pervasiveext.ml:26.22-25 -> > xapi_cli.ml:111.2-138 -> xapi_cli.ml:205.7-44 -> xapi_cli.ml:257.4-23 > [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] > Xapi_cli.exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI > Creation failed [opterr=error 127]; ] > [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] > Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 > > Thanks, > Dimitar Kazkov > _______________________________________________ > 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 Apr 05 10:08:23 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 05 Apr 2012 10:08:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFjbz-00057r-J0; Thu, 05 Apr 2012 10:08:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFjbx-00057i-IZ for xen-api@lists.xen.org; Thu, 05 Apr 2012 10:08:13 +0000 Received: from [85.158.143.35:10600] by server-1.bemta-4.messagelabs.com id BE/99-20925-C0F6D7F4; Thu, 05 Apr 2012 10:08:12 +0000 X-Env-Sender: Jonathan.Ludlam@eu.citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1333620490!7570595!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MzE0NA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27477 invoked from network); 5 Apr 2012 10:08:11 -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; 5 Apr 2012 10:08:11 -0000 X-IronPort-AV: E=Sophos;i="4.75,375,1330905600"; d="scan'208";a="11789319" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 05 Apr 2012 10:08:10 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 5 Apr 2012 11:08:10 +0100 From: Jonathan Ludlam To: Dimitar Kazakov Date: Thu, 5 Apr 2012 11:08:08 +0100 Thread-Topic: [Xen-API] xe vdi-create failure ot local SR type=file and type=ext Thread-Index: Ac0TFABqcTeHZXqNSuqhLzKIJ11u8A== Message-ID: <7549B613-6EB9-4DD8-9741-C0D8556D0176@eu.citrix.com> References: <4F7D6480.6040704@gmail.com> In-Reply-To: <4F7D6480.6040704@gmail.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-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] xe vdi-create failure ot local SR type=file and type=ext 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 log snippet doesn't have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. Jon On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > Hi, > have permanent failure when try to create VDI on local SR type=file or > type=ext. On both types it failed with the same error: > SR_BACKEND_FAILURE_78 > VDI Creation failed [opterr=error 127] > > I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian > 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) > > Is it a bug, or am I missing something? Anybody managed to workaround > this problem? > > > Here is a short extract from xcp-xapi.log > > id=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab type=user name-label=test > virtual-size=1GiB username=root password=null > [20120403T07:57:53.973Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] > Session.create trackid=1ef3448b63e70822073569022044e96b pool=false > uname=root is_local_superuser=true auth_user_sid= > parent=trackid=9834f5af41c964e225f24279aefe4e49 > [20120403T07:57:53.974Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] > Attempting to open /var/lib/xcp/xapi > [20120403T07:57:53.975Z|debug|hyperion|547 UNIX > /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid > D:4cab7e7aa9ae created by task D:93575fa7333c > [20120403T07:57:53.982Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|audit] VDI.create: SR = > 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab (Local storage)'; name label = 'test' > [20120403T07:57:53.983Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Marking SR for > VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) > [20120403T07:57:53.984Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|storage_impl] VDI.create > task:OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a > sr:ba4e9e1a-bc42-0dc9-af0e-5db2905666ab vdi_info:{"vdi": "", > "name_label": "test", "name_description": "", "ty": "user", > "metadata_of_pool": "", "is_a_snapshot": false, "snapshot_time": > "19700101T00:00:00Z", "snapshot_of": "", "read_only": false, > "virtual_size": 1073741824, "physical_utilisation": 0} params: > [20120403T07:57:53.984Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dummytaskhelper] task > VDI.create D:db9f2e113fee created by task R:efdfb350d7ac > [20120403T07:57:53.986Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.create > trackid=654ed4437d52fe9cdd8e5d98a5955526 pool=false uname= > is_local_superuser=true auth_user_sid= > parent=trackid=9834f5af41c964e225f24279aefe4e49 > [20120403T07:57:53.987Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Attempting to open > /var/lib/xcp/xapi > [20120403T07:57:53.987Z|debug|hyperion|548 UNIX > /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid > D:3829e36dbb97 created by task D:6ec167aaa83d > [20120403T07:57:54.066Z|debug|hyperion|549 UNIX > /var/lib/xcp/xapi||dummytaskhelper] task dispatch:host.get_other_config > D:c813aaba73c4 created by task D:db9f2e113fee > [20120403T07:57:54.071Z|debug|hyperion|549 UNIX > /var/lib/xcp/xapi||http_critical] Premature termination of connection! > [20120403T07:57:54.109Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at > sm_exec.ml:220.7-69 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.109Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.destroy > trackid=654ed4437d52fe9cdd8e5d98a5955526 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at > pervasiveext.ml:26.22-25 -> server_helpers.ml:76.11-23 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Server_helpers.exec > exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation > failed [opterr=error 127]; ] > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at > server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at > pervasiveext.ml:26.22-25 -> sm.ml:132.25-98 -> > storage_access.ml:259.36-331 -> storage_access.ml:257.28-492 -> > server_helpers.ml:76.11-23 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] > Server_helpers.exec exception_handler: Got exception > SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at > server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at > storage_access.ml:449.8-47 -> message_forwarding.ml:233.25-44 -> > pervasiveext.ml:22.2-9 > [20120403T07:57:54.110Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Unmarking SR after > VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) > [20120403T07:57:54.111Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at > pervasiveext.ml:26.22-25 -> server.ml:24034.78-280 -> rbac.ml:229.16-23 > [20120403T07:57:54.112Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at > rbac.ml:238.10-15 -> server_helpers.ml:79.11-41 > [20120403T07:57:54.112Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] > Server_helpers.exec exception_handler: Got exception > SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] > [20120403T07:57:54.112Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.112Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at > string.ml:150.25-34 -> stringext.ml:108.13-29 > [20120403T07:57:54.114Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at > server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.115Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.115Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|xapi] Raised at > pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 > [20120403T07:57:54.115Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|backtrace] Raised > at pervasiveext.ml:26.22-25 -> server_helpers.ml:153.10-106 -> > server.ml:24035.19-190 -> server_helpers.ml:119.4-7 > [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||xapi] > Raised at client.ml:6.37-75 -> client.ml:9043.48-106 -> > cli_operations.ml:1082.11-187 -> xapi_cli.ml:112.18-56 -> > pervasiveext.ml:22.2-9 > [20120403T07:57:54.117Z| info|hyperion|546 UNIX > /var/lib/xcp/xapi|session.logout D:2d486a4a5b26|xapi] Session.destroy > trackid=1ef3448b63e70822073569022044e96b > [20120403T07:57:54.118Z|debug|hyperion|546 UNIX > /var/lib/xcp/xapi||backtrace] Raised at pervasiveext.ml:26.22-25 -> > xapi_cli.ml:111.2-138 -> xapi_cli.ml:205.7-44 -> xapi_cli.ml:257.4-23 > [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] > Xapi_cli.exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI > Creation failed [opterr=error 127]; ] > [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] > Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 > > Thanks, > Dimitar Kazkov > _______________________________________________ > 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 Apr 05 12:23:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 05 Apr 2012 12:23: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 1SFliJ-0001Wf-PL; Thu, 05 Apr 2012 12:22:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFliI-0001WW-Hg for xen-api@lists.xen.org; Thu, 05 Apr 2012 12:22:54 +0000 Received: from [85.158.143.35:57557] by server-3.bemta-4.messagelabs.com id A5/E0-05853-D9E8D7F4; Thu, 05 Apr 2012 12:22:53 +0000 X-Env-Sender: the.kazak@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1333628570!14867578!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 27095 invoked from network); 5 Apr 2012 12:22:51 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Apr 2012 12:22:51 -0000 Received: by bkcjg9 with SMTP id jg9so1460407bkc.32 for ; Thu, 05 Apr 2012 05:22:50 -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=SroVNrVSLh/KUYGlpxkXsltsootHYK8/avmxzWEiGHM=; b=M5vvB+Z4gy13KHCST6Zfy+ONzCcp9j8tkl8qDW/RFs9g7/nPK7nwMh38MFbr+qXiP+ 78xSXyBK2gg0Ucl4+3/JrAAHkCTg+88WrG6IYYcqPzcmVH5skD1H3ngEMLFZnVLPlL0p mk9PRcD+oyQUGJJVfMC/T/Z+pvKKs5wTL1xb7xWohrfr9pAloXuWJdbnTkn6z71WmAkH en/oGmw/OyUZWoECHtH7290T9GMVixLS2DQjPQJgBWEbaUol3CO9+EEDzbPVOgMV9Bcu zD0Ih3OzMAVLqpXKspQikhEVKwG/TJmUM7O5PwE5g8WVS1J2tmhx3a839rHS4cuuHWpP igDg== Received: by 10.204.132.72 with SMTP id a8mr1070276bkt.42.1333628569998; Thu, 05 Apr 2012 05:22:49 -0700 (PDT) Received: from [212.50.0.54] (purple.varna.spnet.net. [212.50.0.54]) by mx.google.com with ESMTPS id zx16sm8484731bkb.13.2012.04.05.05.22.47 (version=SSLv3 cipher=OTHER); Thu, 05 Apr 2012 05:22:48 -0700 (PDT) Message-ID: <4F7D8E96.1040808@gmail.com> Date: Thu, 05 Apr 2012 15:22:46 +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, xen-devel@lists.xen.org References: <4F7D6480.6040704@gmail.com> <7549B613-6EB9-4DD8-9741-C0D8556D0176@eu.citrix.com> In-Reply-To: <7549B613-6EB9-4DD8-9741-C0D8556D0176@eu.citrix.com> Content-Type: multipart/mixed; boundary="------------050905020305040603080804" Subject: Re: [Xen-API] (solved) xe vdi-create failure ot local SR type=file and type=ext 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. --------------050905020305040603080804 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks! I found the problem in SMlog. /usr/sbin/td-util create vhd 1024 /var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd /usr/sbin/td-util: error while loading shared libraries: libxenctrl.so.4.0: cannot open shared object file: No such file or directory td-util from blktap-utils 2.0.90-3 (testing) is looking for libxenctrl.so.4.0, but the package libxen-4.1 4.1.2-2.1 (testing) offers only libxenctrl-4.1.so in /usr/lib. Makeing a link libxenctrl.so.4.0 to libxenctrl-4.1.so in /usr/lib solves the problem. SMlog snippet: [22578] 2012-04-05 14:00:27.322636 ['uuidgen', '-r'] [22578] 2012-04-05 14:00:27.329600 SUCCESS [22578] 2012-04-05 14:00:27.336360 lock: acquired /var/lock/sm/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/sr [22578] 2012-04-05 14:00:27.336677 vdi_create {'sr_uuid': '4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2', 'subtask_of': 'DummyRef:|7d48c27e-b70e-59eb-6197-51518053c92e|VDI.create', 'vdi_type': 'user', 'args': ['1073741824', 'test', '', '', 'false', '19700101T00:00:00Z', '', 'false'], 'host_ref': 'OpaqueRef:e5783245-3c2c-df70-80c3-244d77ebc59f', 'session_ref': 'OpaqueRef:0c7299c1-981a-c1b5-f5b7-17a1a467518f', 'device_config': {'device': '/dev/sdb1', 'SRmaster': 'true'}, 'command': 'vdi_create', 'sr_ref': 'OpaqueRef:ed43ec0a-3570-7535-cac9-d4a086f69d18', 'vdi_sm_config': {}} [22578] 2012-04-05 14:00:27.337019 ['/usr/sbin/td-util', 'create', 'vhd', '1024', '/var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd'] [22578] 2012-04-05 14:00:27.342837 FAILED: (rc 127) stdout: '', stderr: '/usr/sbin/td-util: error while loading shared libraries: libxenctrl.so.4.0: cannot open shared object file: No such file or directory ' [22578] 2012-04-05 14:00:27.361494 Raising exception [78, VDI Creation failed [opterr=error 127]] [22578] 2012-04-05 14:00:27.361842 lock: released /var/lock/sm/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/sr [22578] 2012-04-05 14:00:27.362757 ***** vdi_create: EXCEPTION , VDI Creation failed [opterr=error 127] File "/usr/lib/xcp/sm/SRCommand.py", line 94, in run return self._run_locked(sr) File "/usr/lib/xcp/sm/SRCommand.py", line 131, in _run_locked return self._run(sr, target) File "/usr/lib/xcp/sm/SRCommand.py", line 159, in _run return target.create(self.params['sr_uuid'], self.vdi_uuid, long(self.params['args'][0])) File "/usr/lib/xcp/sm/FileSR.py", line 464, in create opterr='error %d' % inst.code) File "/usr/lib/xcp/sm/xs_errors.py", line 49, in __init__ raise SR.SROSError(errorcode, errormessage) [22578] 2012-04-05 14:00:27.363242 lock: closed /var/lock/sm/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/sr On 04/05/2012 01:08 PM, Jonathan Ludlam wrote: > The log snippet doesn't have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. > > Jon > > On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > >> Hi, >> have permanent failure when try to create VDI on local SR type=file or >> type=ext. On both types it failed with the same error: >> SR_BACKEND_FAILURE_78 >> VDI Creation failed [opterr=error 127] >> >> I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian >> 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) >> >> Is it a bug, or am I missing something? Anybody managed to workaround >> this problem? >> >> >> Here is a short extract from xcp-xapi.log >> >> id=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab type=user name-label=test >> virtual-size=1GiB username=root password=null >> [20120403T07:57:53.973Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] >> Session.create trackid=1ef3448b63e70822073569022044e96b pool=false >> uname=root is_local_superuser=true auth_user_sid= >> parent=trackid=9834f5af41c964e225f24279aefe4e49 >> [20120403T07:57:53.974Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] >> Attempting to open /var/lib/xcp/xapi >> [20120403T07:57:53.975Z|debug|hyperion|547 UNIX >> /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid >> D:4cab7e7aa9ae created by task D:93575fa7333c >> [20120403T07:57:53.982Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|audit] VDI.create: SR = >> 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab (Local storage)'; name label = 'test' >> [20120403T07:57:53.983Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Marking SR for >> VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) >> [20120403T07:57:53.984Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|storage_impl] VDI.create >> task:OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a >> sr:ba4e9e1a-bc42-0dc9-af0e-5db2905666ab vdi_info:{"vdi": "", >> "name_label": "test", "name_description": "", "ty": "user", >> "metadata_of_pool": "", "is_a_snapshot": false, "snapshot_time": >> "19700101T00:00:00Z", "snapshot_of": "", "read_only": false, >> "virtual_size": 1073741824, "physical_utilisation": 0} params: >> [20120403T07:57:53.984Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dummytaskhelper] task >> VDI.create D:db9f2e113fee created by task R:efdfb350d7ac >> [20120403T07:57:53.986Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.create >> trackid=654ed4437d52fe9cdd8e5d98a5955526 pool=false uname= >> is_local_superuser=true auth_user_sid= >> parent=trackid=9834f5af41c964e225f24279aefe4e49 >> [20120403T07:57:53.987Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Attempting to open >> /var/lib/xcp/xapi >> [20120403T07:57:53.987Z|debug|hyperion|548 UNIX >> /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid >> D:3829e36dbb97 created by task D:6ec167aaa83d >> [20120403T07:57:54.066Z|debug|hyperion|549 UNIX >> /var/lib/xcp/xapi||dummytaskhelper] task dispatch:host.get_other_config >> D:c813aaba73c4 created by task D:db9f2e113fee >> [20120403T07:57:54.071Z|debug|hyperion|549 UNIX >> /var/lib/xcp/xapi||http_critical] Premature termination of connection! >> [20120403T07:57:54.109Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at >> sm_exec.ml:220.7-69 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.109Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.destroy >> trackid=654ed4437d52fe9cdd8e5d98a5955526 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at >> pervasiveext.ml:26.22-25 -> server_helpers.ml:76.11-23 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Server_helpers.exec >> exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation >> failed [opterr=error 127]; ] >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at >> server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at >> pervasiveext.ml:26.22-25 -> sm.ml:132.25-98 -> >> storage_access.ml:259.36-331 -> storage_access.ml:257.28-492 -> >> server_helpers.ml:76.11-23 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] >> Server_helpers.exec exception_handler: Got exception >> SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at >> server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at >> storage_access.ml:449.8-47 -> message_forwarding.ml:233.25-44 -> >> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Unmarking SR after >> VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) >> [20120403T07:57:54.111Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at >> pervasiveext.ml:26.22-25 -> server.ml:24034.78-280 -> rbac.ml:229.16-23 >> [20120403T07:57:54.112Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at >> rbac.ml:238.10-15 -> server_helpers.ml:79.11-41 >> [20120403T07:57:54.112Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] >> Server_helpers.exec exception_handler: Got exception >> SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] >> [20120403T07:57:54.112Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.112Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.114Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at >> server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.115Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.115Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.115Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|backtrace] Raised >> at pervasiveext.ml:26.22-25 -> server_helpers.ml:153.10-106 -> >> server.ml:24035.19-190 -> server_helpers.ml:119.4-7 >> [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||xapi] >> Raised at client.ml:6.37-75 -> client.ml:9043.48-106 -> >> cli_operations.ml:1082.11-187 -> xapi_cli.ml:112.18-56 -> >> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.117Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|session.logout D:2d486a4a5b26|xapi] Session.destroy >> trackid=1ef3448b63e70822073569022044e96b >> [20120403T07:57:54.118Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi||backtrace] Raised at pervasiveext.ml:26.22-25 -> >> xapi_cli.ml:111.2-138 -> xapi_cli.ml:205.7-44 -> xapi_cli.ml:257.4-23 >> [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] >> Xapi_cli.exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI >> Creation failed [opterr=error 127]; ] >> [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] >> Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 >> >> Thanks, >> Dimitar Kazkov >> _______________________________________________ >> xen-api mailing list >> xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------050905020305040603080804 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== --------------050905020305040603080804 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 --------------050905020305040603080804-- From xen-api-bounces@lists.xen.org Thu Apr 05 12:23:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 05 Apr 2012 12:23: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 1SFliJ-0001Wf-PL; Thu, 05 Apr 2012 12:22:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFliI-0001WW-Hg for xen-api@lists.xen.org; Thu, 05 Apr 2012 12:22:54 +0000 Received: from [85.158.143.35:57557] by server-3.bemta-4.messagelabs.com id A5/E0-05853-D9E8D7F4; Thu, 05 Apr 2012 12:22:53 +0000 X-Env-Sender: the.kazak@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1333628570!14867578!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 27095 invoked from network); 5 Apr 2012 12:22:51 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Apr 2012 12:22:51 -0000 Received: by bkcjg9 with SMTP id jg9so1460407bkc.32 for ; Thu, 05 Apr 2012 05:22:50 -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=SroVNrVSLh/KUYGlpxkXsltsootHYK8/avmxzWEiGHM=; b=M5vvB+Z4gy13KHCST6Zfy+ONzCcp9j8tkl8qDW/RFs9g7/nPK7nwMh38MFbr+qXiP+ 78xSXyBK2gg0Ucl4+3/JrAAHkCTg+88WrG6IYYcqPzcmVH5skD1H3ngEMLFZnVLPlL0p mk9PRcD+oyQUGJJVfMC/T/Z+pvKKs5wTL1xb7xWohrfr9pAloXuWJdbnTkn6z71WmAkH en/oGmw/OyUZWoECHtH7290T9GMVixLS2DQjPQJgBWEbaUol3CO9+EEDzbPVOgMV9Bcu zD0Ih3OzMAVLqpXKspQikhEVKwG/TJmUM7O5PwE5g8WVS1J2tmhx3a839rHS4cuuHWpP igDg== Received: by 10.204.132.72 with SMTP id a8mr1070276bkt.42.1333628569998; Thu, 05 Apr 2012 05:22:49 -0700 (PDT) Received: from [212.50.0.54] (purple.varna.spnet.net. [212.50.0.54]) by mx.google.com with ESMTPS id zx16sm8484731bkb.13.2012.04.05.05.22.47 (version=SSLv3 cipher=OTHER); Thu, 05 Apr 2012 05:22:48 -0700 (PDT) Message-ID: <4F7D8E96.1040808@gmail.com> Date: Thu, 05 Apr 2012 15:22:46 +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, xen-devel@lists.xen.org References: <4F7D6480.6040704@gmail.com> <7549B613-6EB9-4DD8-9741-C0D8556D0176@eu.citrix.com> In-Reply-To: <7549B613-6EB9-4DD8-9741-C0D8556D0176@eu.citrix.com> Content-Type: multipart/mixed; boundary="------------050905020305040603080804" Subject: Re: [Xen-API] (solved) xe vdi-create failure ot local SR type=file and type=ext 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. --------------050905020305040603080804 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Thanks! I found the problem in SMlog. /usr/sbin/td-util create vhd 1024 /var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd /usr/sbin/td-util: error while loading shared libraries: libxenctrl.so.4.0: cannot open shared object file: No such file or directory td-util from blktap-utils 2.0.90-3 (testing) is looking for libxenctrl.so.4.0, but the package libxen-4.1 4.1.2-2.1 (testing) offers only libxenctrl-4.1.so in /usr/lib. Makeing a link libxenctrl.so.4.0 to libxenctrl-4.1.so in /usr/lib solves the problem. SMlog snippet: [22578] 2012-04-05 14:00:27.322636 ['uuidgen', '-r'] [22578] 2012-04-05 14:00:27.329600 SUCCESS [22578] 2012-04-05 14:00:27.336360 lock: acquired /var/lock/sm/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/sr [22578] 2012-04-05 14:00:27.336677 vdi_create {'sr_uuid': '4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2', 'subtask_of': 'DummyRef:|7d48c27e-b70e-59eb-6197-51518053c92e|VDI.create', 'vdi_type': 'user', 'args': ['1073741824', 'test', '', '', 'false', '19700101T00:00:00Z', '', 'false'], 'host_ref': 'OpaqueRef:e5783245-3c2c-df70-80c3-244d77ebc59f', 'session_ref': 'OpaqueRef:0c7299c1-981a-c1b5-f5b7-17a1a467518f', 'device_config': {'device': '/dev/sdb1', 'SRmaster': 'true'}, 'command': 'vdi_create', 'sr_ref': 'OpaqueRef:ed43ec0a-3570-7535-cac9-d4a086f69d18', 'vdi_sm_config': {}} [22578] 2012-04-05 14:00:27.337019 ['/usr/sbin/td-util', 'create', 'vhd', '1024', '/var/run/sr-mount/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/247b64e4-6b7f-4b2f-bd73-50e848c78d71.vhd'] [22578] 2012-04-05 14:00:27.342837 FAILED: (rc 127) stdout: '', stderr: '/usr/sbin/td-util: error while loading shared libraries: libxenctrl.so.4.0: cannot open shared object file: No such file or directory ' [22578] 2012-04-05 14:00:27.361494 Raising exception [78, VDI Creation failed [opterr=error 127]] [22578] 2012-04-05 14:00:27.361842 lock: released /var/lock/sm/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/sr [22578] 2012-04-05 14:00:27.362757 ***** vdi_create: EXCEPTION , VDI Creation failed [opterr=error 127] File "/usr/lib/xcp/sm/SRCommand.py", line 94, in run return self._run_locked(sr) File "/usr/lib/xcp/sm/SRCommand.py", line 131, in _run_locked return self._run(sr, target) File "/usr/lib/xcp/sm/SRCommand.py", line 159, in _run return target.create(self.params['sr_uuid'], self.vdi_uuid, long(self.params['args'][0])) File "/usr/lib/xcp/sm/FileSR.py", line 464, in create opterr='error %d' % inst.code) File "/usr/lib/xcp/sm/xs_errors.py", line 49, in __init__ raise SR.SROSError(errorcode, errormessage) [22578] 2012-04-05 14:00:27.363242 lock: closed /var/lock/sm/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/sr On 04/05/2012 01:08 PM, Jonathan Ludlam wrote: > The log snippet doesn't have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. > > Jon > > On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > >> Hi, >> have permanent failure when try to create VDI on local SR type=file or >> type=ext. On both types it failed with the same error: >> SR_BACKEND_FAILURE_78 >> VDI Creation failed [opterr=error 127] >> >> I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian >> 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) >> >> Is it a bug, or am I missing something? Anybody managed to workaround >> this problem? >> >> >> Here is a short extract from xcp-xapi.log >> >> id=ba4e9e1a-bc42-0dc9-af0e-5db2905666ab type=user name-label=test >> virtual-size=1GiB username=root password=null >> [20120403T07:57:53.973Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] >> Session.create trackid=1ef3448b63e70822073569022044e96b pool=false >> uname=root is_local_superuser=true auth_user_sid= >> parent=trackid=9834f5af41c964e225f24279aefe4e49 >> [20120403T07:57:53.974Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|session.login_with_password D:93575fa7333c|xapi] >> Attempting to open /var/lib/xcp/xapi >> [20120403T07:57:53.975Z|debug|hyperion|547 UNIX >> /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid >> D:4cab7e7aa9ae created by task D:93575fa7333c >> [20120403T07:57:53.982Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|audit] VDI.create: SR = >> 'ba4e9e1a-bc42-0dc9-af0e-5db2905666ab (Local storage)'; name label = 'test' >> [20120403T07:57:53.983Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Marking SR for >> VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) >> [20120403T07:57:53.984Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|storage_impl] VDI.create >> task:OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a >> sr:ba4e9e1a-bc42-0dc9-af0e-5db2905666ab vdi_info:{"vdi": "", >> "name_label": "test", "name_description": "", "ty": "user", >> "metadata_of_pool": "", "is_a_snapshot": false, "snapshot_time": >> "19700101T00:00:00Z", "snapshot_of": "", "read_only": false, >> "virtual_size": 1073741824, "physical_utilisation": 0} params: >> [20120403T07:57:53.984Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dummytaskhelper] task >> VDI.create D:db9f2e113fee created by task R:efdfb350d7ac >> [20120403T07:57:53.986Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.create >> trackid=654ed4437d52fe9cdd8e5d98a5955526 pool=false uname= >> is_local_superuser=true auth_user_sid= >> parent=trackid=9834f5af41c964e225f24279aefe4e49 >> [20120403T07:57:53.987Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Attempting to open >> /var/lib/xcp/xapi >> [20120403T07:57:53.987Z|debug|hyperion|548 UNIX >> /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.get_uuid >> D:3829e36dbb97 created by task D:6ec167aaa83d >> [20120403T07:57:54.066Z|debug|hyperion|549 UNIX >> /var/lib/xcp/xapi||dummytaskhelper] task dispatch:host.get_other_config >> D:c813aaba73c4 created by task D:db9f2e113fee >> [20120403T07:57:54.071Z|debug|hyperion|549 UNIX >> /var/lib/xcp/xapi||http_critical] Premature termination of connection! >> [20120403T07:57:54.109Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at >> sm_exec.ml:220.7-69 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.109Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Session.destroy >> trackid=654ed4437d52fe9cdd8e5d98a5955526 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at >> pervasiveext.ml:26.22-25 -> server_helpers.ml:76.11-23 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Server_helpers.exec >> exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI Creation >> failed [opterr=error 127]; ] >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|dispatcher] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|backtrace] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at >> server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|sm_exec D:6ec167aaa83d|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at >> pervasiveext.ml:26.22-25 -> sm.ml:132.25-98 -> >> storage_access.ml:259.36-331 -> storage_access.ml:257.28-492 -> >> server_helpers.ml:76.11-23 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] >> Server_helpers.exec exception_handler: Got exception >> SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|dispatcher] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|backtrace] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at >> server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create D:db9f2e113fee|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at >> storage_access.ml:449.8-47 -> message_forwarding.ml:233.25-44 -> >> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.110Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Unmarking SR after >> VDI.create (task=OpaqueRef:efdfb350-d7ac-c3e3-3a69-9c8e4d560f2a) >> [20120403T07:57:54.111Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at >> pervasiveext.ml:26.22-25 -> server.ml:24034.78-280 -> rbac.ml:229.16-23 >> [20120403T07:57:54.112Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at >> rbac.ml:238.10-15 -> server_helpers.ml:79.11-41 >> [20120403T07:57:54.112Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] >> Server_helpers.exec exception_handler: Got exception >> SR_BACKEND_FAILURE_78: [ ; VDI Creation failed [opterr=error 127]; ] >> [20120403T07:57:54.112Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|dispatcher] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.112Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|backtrace] Raised at >> string.ml:150.25-34 -> stringext.ml:108.13-29 >> [20120403T07:57:54.114Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at >> server_helpers.ml:94.14-15 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.115Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|VDI.create R:efdfb350d7ac|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.115Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|xapi] Raised at >> pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.115Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi|dispatch:VDI.create D:f979b7f99455|backtrace] Raised >> at pervasiveext.ml:26.22-25 -> server_helpers.ml:153.10-106 -> >> server.ml:24035.19-190 -> server_helpers.ml:119.4-7 >> [20120403T07:57:54.115Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||xapi] >> Raised at client.ml:6.37-75 -> client.ml:9043.48-106 -> >> cli_operations.ml:1082.11-187 -> xapi_cli.ml:112.18-56 -> >> pervasiveext.ml:22.2-9 >> [20120403T07:57:54.117Z| info|hyperion|546 UNIX >> /var/lib/xcp/xapi|session.logout D:2d486a4a5b26|xapi] Session.destroy >> trackid=1ef3448b63e70822073569022044e96b >> [20120403T07:57:54.118Z|debug|hyperion|546 UNIX >> /var/lib/xcp/xapi||backtrace] Raised at pervasiveext.ml:26.22-25 -> >> xapi_cli.ml:111.2-138 -> xapi_cli.ml:205.7-44 -> xapi_cli.ml:257.4-23 >> [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] >> Xapi_cli.exception_handler: Got exception SR_BACKEND_FAILURE_78: [ ; VDI >> Creation failed [opterr=error 127]; ] >> [20120403T07:57:54.118Z|debug|hyperion|546 UNIX /var/lib/xcp/xapi||cli] >> Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 >> >> Thanks, >> Dimitar Kazkov >> _______________________________________________ >> xen-api mailing list >> xen-api@lists.xen.org >> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api --------------050905020305040603080804 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== --------------050905020305040603080804 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 --------------050905020305040603080804-- From xen-api-bounces@lists.xen.org Fri Apr 06 03:00:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 06 Apr 2012 03:00:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFzPp-00059X-V0; Fri, 06 Apr 2012 03:00:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFzPo-00059S-Eo for xen-api@lists.xensource.com; Fri, 06 Apr 2012 03:00:44 +0000 Received: from [85.158.143.35:35908] by server-3.bemta-4.messagelabs.com id F1/90-05853-B5C5E7F4; Fri, 06 Apr 2012 03:00:43 +0000 X-Env-Sender: pankaj.kumarbiswas@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1333681237!12112752!1 X-Originating-IP: [203.166.19.134] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjE2Ni4xOS4xMzQgPT4gNDM0Mjg=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10134 invoked from network); 6 Apr 2012 03:00:40 -0000 Received: from smtp.citrix.com.au (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Apr 2012 03:00:40 -0000 X-IronPort-AV: E=Sophos;i="4.75,380,1330905600"; d="scan'208,217";a="11021919" Received: from banpmailmx01.citrite.net ([10.103.128.73]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 06 Apr 2012 03:00:35 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.71]) by BANPMAILMX01.citrite.net ([10.103.128.73]) with mapi; Fri, 6 Apr 2012 08:30:34 +0530 From: Pankaj Kumar Biswas To: "xen-api@lists.xensource.com" Date: Fri, 6 Apr 2012 08:30:31 +0530 Thread-Topic: how to remove 1 thread (posted by myself) Thread-Index: Ac0ToW3MBifBe254QeOHh9km3FxSRQ== Message-ID: <64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6@BANPMAILBOX01.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: [Xen-API] how to remove 1 thread (posted by myself) 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="===============1307402510394500024==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1307402510394500024== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6BANPMAILBOX01_" --_000_64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6BANPMAILBOX01_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Team, Can you please help me in the process of removing 1 thread which I have pos= ted myself. Thanks & Regards, PANKAJ KUMAR BISWAS --_000_64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6BANPMAILBOX01_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Team,

 

Can y= ou please help me in the process of removing 1 thread which I have posted m= yself.

 

Thanks & Rega= rds,

PANKAJ KUMAR BISWAS

 = ;

= --_000_64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6BANPMAILBOX01_-- --===============1307402510394500024== 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 --===============1307402510394500024==-- From xen-api-bounces@lists.xen.org Fri Apr 06 03:00:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 06 Apr 2012 03:00:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFzPp-00059X-V0; Fri, 06 Apr 2012 03:00:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SFzPo-00059S-Eo for xen-api@lists.xensource.com; Fri, 06 Apr 2012 03:00:44 +0000 Received: from [85.158.143.35:35908] by server-3.bemta-4.messagelabs.com id F1/90-05853-B5C5E7F4; Fri, 06 Apr 2012 03:00:43 +0000 X-Env-Sender: pankaj.kumarbiswas@citrix.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1333681237!12112752!1 X-Originating-IP: [203.166.19.134] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjE2Ni4xOS4xMzQgPT4gNDM0Mjg=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10134 invoked from network); 6 Apr 2012 03:00:40 -0000 Received: from smtp.citrix.com.au (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Apr 2012 03:00:40 -0000 X-IronPort-AV: E=Sophos;i="4.75,380,1330905600"; d="scan'208,217";a="11021919" Received: from banpmailmx01.citrite.net ([10.103.128.73]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 06 Apr 2012 03:00:35 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.71]) by BANPMAILMX01.citrite.net ([10.103.128.73]) with mapi; Fri, 6 Apr 2012 08:30:34 +0530 From: Pankaj Kumar Biswas To: "xen-api@lists.xensource.com" Date: Fri, 6 Apr 2012 08:30:31 +0530 Thread-Topic: how to remove 1 thread (posted by myself) Thread-Index: Ac0ToW3MBifBe254QeOHh9km3FxSRQ== Message-ID: <64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6@BANPMAILBOX01.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: [Xen-API] how to remove 1 thread (posted by myself) 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="===============1307402510394500024==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1307402510394500024== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6BANPMAILBOX01_" --_000_64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6BANPMAILBOX01_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Team, Can you please help me in the process of removing 1 thread which I have pos= ted myself. Thanks & Regards, PANKAJ KUMAR BISWAS --_000_64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6BANPMAILBOX01_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Team,

 

Can y= ou please help me in the process of removing 1 thread which I have posted m= yself.

 

Thanks & Rega= rds,

PANKAJ KUMAR BISWAS

 = ;

= --_000_64FB1554ABC9B44FAA773FBD6CB889C2F915435DC6BANPMAILBOX01_-- --===============1307402510394500024== 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 --===============1307402510394500024==-- From xen-api-bounces@lists.xen.org Fri Apr 06 10:33:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 06 Apr 2012 10:33: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 1SG6Ts-0000Ge-77; Fri, 06 Apr 2012 10:33:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SG6Tq-0000GX-KI for xen-api@lists.xen.org; Fri, 06 Apr 2012 10:33:22 +0000 Received: from [85.158.143.99:63890] by server-1.bemta-4.messagelabs.com id B6/D3-20925-176CE7F4; Fri, 06 Apr 2012 10:33:21 +0000 X-Env-Sender: vase@selfip.ru X-Msg-Ref: server-10.tower-216.messagelabs.com!1333708400!16242283!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 6245 invoked from network); 6 Apr 2012 10:33:21 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Apr 2012 10:33:21 -0000 Received: by lahe6 with SMTP id e6so2802226lah.32 for ; Fri, 06 Apr 2012 03:33:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfip.ru; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=gjRAByGSEof45KbW6+DIpI6kR5Fag/akmw8nZQey/dE=; b=JQhUErUeqD9VJdDOrGm7aTycsTJdugkWmOr3HLst5QwzkR1/XdUnUxGOtdl7pvdurD FTfCIreptPQX2yxn+PigkaFAsBvepoo87/XdeO4jeez3h/fhyqTxhhliwJ9InTOxHb3g G0b46IKpAVMCJNajV+oHHBb3sX/LA4kz67PtI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip: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=gjRAByGSEof45KbW6+DIpI6kR5Fag/akmw8nZQey/dE=; b=gSlq7Qjdsf2kE82ktenNUGSzDj3AezKsY1/1MqJu3rZL+AahMN4fVp3mnP0tDdeN29 pzX9C9SnmPv0oB1trILN0dgJM+z80+NkA/e8hDJF/mPnpukv6wrGHIaEk/0s3m00WIRH FdTiDZJjM2WejqnNiPuakANxEL4AkZpvh3Ob6aPsuss919mb/HtJx9ZX5GeLLYGk8QAc 49VhZf0Fy2OGZnTG9m+Cg9eMLN9ZYQEePnUjLrwFxQXAhb4aRJSxiQuOlHyBk44QlaFO ENadkCaSeb4PHD+FNpRCZ4rdjbEaTdN8WLWCyGavWa3sK6SDfHDquKXSmWgLdCi8qFjP Hqcw== Received: by 10.152.125.41 with SMTP id mn9mr7931213lab.30.1333708399853; Fri, 06 Apr 2012 03:33:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.37.234 with HTTP; Fri, 6 Apr 2012 03:33:04 -0700 (PDT) X-Originating-IP: [85.143.161.18] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021BA9@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C812021BA9@LONPMAILBOX01.citrite.net> From: Vasiliy Tolstov Date: Fri, 6 Apr 2012 14:33:04 +0400 X-Google-Sender-Auth: xLh0lDgSa2sXJqwWwR7IdojxZxQ Message-ID: To: Paul Durrant X-Gm-Message-State: ALoCoQkDHwKl3tf0Je+c1CihhQiDBz9lxRD6L78NSviAPBhVOXatEQwe8Do6wCv+toYB2D2pAaiM 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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MjAxMi80LzIgUGF1bCBEdXJyYW50IDxQYXVsLkR1cnJhbnRAY2l0cml4LmNvbT46Cj4gwqBBcyBJ IHNhaWQsIHRoZSBXTUkgQVBJIGlzIG5vdCBwdWJsaXNoZWQgYXMgeWV0LiBJJ2xsIHNlZSB3aGF0 IEkgY2FuIGRvIGFib3V0IGdldHRpbmcgYXBwcm92YWwgdG8gZG8gdGhpcy4KCkhlbGxvLCBkbyB5 b3UgaGF2ZSBhbnkgcHJvZ3Jlc3M/CgoKLS0gClZhc2lsaXkgVG9sc3RvdiwKQ2xvZG8ucnUKZS1t YWlsOiB2LnRvbHN0b3ZAc2VsZmlwLnJ1CmphYmJlcjogdmFzZUBzZWxmaXAucnUKCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnhlbi1hcGkgbWFpbGluZyBs aXN0Cnhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21h aWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Fri Apr 06 10:33:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 06 Apr 2012 10:33: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 1SG6Ts-0000Ge-77; Fri, 06 Apr 2012 10:33:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SG6Tq-0000GX-KI for xen-api@lists.xen.org; Fri, 06 Apr 2012 10:33:22 +0000 Received: from [85.158.143.99:63890] by server-1.bemta-4.messagelabs.com id B6/D3-20925-176CE7F4; Fri, 06 Apr 2012 10:33:21 +0000 X-Env-Sender: vase@selfip.ru X-Msg-Ref: server-10.tower-216.messagelabs.com!1333708400!16242283!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 6245 invoked from network); 6 Apr 2012 10:33:21 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 6 Apr 2012 10:33:21 -0000 Received: by lahe6 with SMTP id e6so2802226lah.32 for ; Fri, 06 Apr 2012 03:33:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfip.ru; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=gjRAByGSEof45KbW6+DIpI6kR5Fag/akmw8nZQey/dE=; b=JQhUErUeqD9VJdDOrGm7aTycsTJdugkWmOr3HLst5QwzkR1/XdUnUxGOtdl7pvdurD FTfCIreptPQX2yxn+PigkaFAsBvepoo87/XdeO4jeez3h/fhyqTxhhliwJ9InTOxHb3g G0b46IKpAVMCJNajV+oHHBb3sX/LA4kz67PtI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip: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=gjRAByGSEof45KbW6+DIpI6kR5Fag/akmw8nZQey/dE=; b=gSlq7Qjdsf2kE82ktenNUGSzDj3AezKsY1/1MqJu3rZL+AahMN4fVp3mnP0tDdeN29 pzX9C9SnmPv0oB1trILN0dgJM+z80+NkA/e8hDJF/mPnpukv6wrGHIaEk/0s3m00WIRH FdTiDZJjM2WejqnNiPuakANxEL4AkZpvh3Ob6aPsuss919mb/HtJx9ZX5GeLLYGk8QAc 49VhZf0Fy2OGZnTG9m+Cg9eMLN9ZYQEePnUjLrwFxQXAhb4aRJSxiQuOlHyBk44QlaFO ENadkCaSeb4PHD+FNpRCZ4rdjbEaTdN8WLWCyGavWa3sK6SDfHDquKXSmWgLdCi8qFjP Hqcw== Received: by 10.152.125.41 with SMTP id mn9mr7931213lab.30.1333708399853; Fri, 06 Apr 2012 03:33:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.37.234 with HTTP; Fri, 6 Apr 2012 03:33:04 -0700 (PDT) X-Originating-IP: [85.143.161.18] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C812021BA9@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C812021BA9@LONPMAILBOX01.citrite.net> From: Vasiliy Tolstov Date: Fri, 6 Apr 2012 14:33:04 +0400 X-Google-Sender-Auth: xLh0lDgSa2sXJqwWwR7IdojxZxQ Message-ID: To: Paul Durrant X-Gm-Message-State: ALoCoQkDHwKl3tf0Je+c1CihhQiDBz9lxRD6L78NSviAPBhVOXatEQwe8Do6wCv+toYB2D2pAaiM 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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MjAxMi80LzIgUGF1bCBEdXJyYW50IDxQYXVsLkR1cnJhbnRAY2l0cml4LmNvbT46Cj4gwqBBcyBJ IHNhaWQsIHRoZSBXTUkgQVBJIGlzIG5vdCBwdWJsaXNoZWQgYXMgeWV0LiBJJ2xsIHNlZSB3aGF0 IEkgY2FuIGRvIGFib3V0IGdldHRpbmcgYXBwcm92YWwgdG8gZG8gdGhpcy4KCkhlbGxvLCBkbyB5 b3UgaGF2ZSBhbnkgcHJvZ3Jlc3M/CgoKLS0gClZhc2lsaXkgVG9sc3RvdiwKQ2xvZG8ucnUKZS1t YWlsOiB2LnRvbHN0b3ZAc2VsZmlwLnJ1CmphYmJlcjogdmFzZUBzZWxmaXAucnUKCl9fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnhlbi1hcGkgbWFpbGluZyBs aXN0Cnhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21h aWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Sat Apr 07 07:42:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 07 Apr 2012 07:42: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 1SGQHt-0000tH-J1; Sat, 07 Apr 2012 07:42:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SGQHs-0000t8-BH for xen-api@lists.xen.org; Sat, 07 Apr 2012 07:42:20 +0000 Received: from [85.158.143.99:60881] by server-2.bemta-4.messagelabs.com id 5F/30-17550-BDFEF7F4; Sat, 07 Apr 2012 07:42:19 +0000 X-Env-Sender: egoitz@ramattack.net X-Msg-Ref: server-7.tower-216.messagelabs.com!1333784538!19306145!1 X-Originating-IP: [194.30.0.207] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk0LjMwLjAuMjA3ID0+IDIwMjE4\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3193 invoked from network); 7 Apr 2012 07:42:19 -0000 Received: from proxypop03.sare.net (HELO proxypop03.sare.net) (194.30.0.207) by server-7.tower-216.messagelabs.com with SMTP; 7 Apr 2012 07:42:19 -0000 Received: from [192.168.12.225] (unknown [212.81.198.13]) by proxypop03.sare.net (Postfix) with ESMTPSA id 74D669DC41D for ; Sat, 7 Apr 2012 09:42:18 +0200 (CEST) From: Egoitz Aurrekoetxea To: xen-api@lists.xen.org Organization: etxea Date: Sat, 07 Apr 2012 09:42:17 +0200 Message-ID: <1333784537.3868.8.camel@mactoo> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 Subject: [Xen-API] XenCloud, Xapi and FreeBSD X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: egoitz@ramattack.net 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 Good morning, I would like to make a suggestion from this mailing list. I'm working at an ISP environment and we're running Xen Cloud as virtualization infrastructure. For a large number of years we have been running FreeBSD (an nowadays... we run it too...).. although FreeBSD seems to run pretty nice under XenCloud (with XENHVM kernel) the interacion with xapi and XenServerTools are not supported for this (IMHO) nice operating system. It gives so much possibilities to experienced sysadmins that I think that other OS like Centos (for example) are totally in clear disadvantage with this BSD Os (for some several reasons which I could debate in other moment). So I would to suggest from here to add support for FreeBSD at XenServerTools and to be able to take advantage of this fine api with this fine OS. Is it planned to give FreeBSD support to xapi?. If not, I could try to take some time for trying to write it. Thank you very much for you're time. Best regards, _______________________________________________ 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 Apr 07 07:42:31 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 07 Apr 2012 07:42: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 1SGQHt-0000tH-J1; Sat, 07 Apr 2012 07:42:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SGQHs-0000t8-BH for xen-api@lists.xen.org; Sat, 07 Apr 2012 07:42:20 +0000 Received: from [85.158.143.99:60881] by server-2.bemta-4.messagelabs.com id 5F/30-17550-BDFEF7F4; Sat, 07 Apr 2012 07:42:19 +0000 X-Env-Sender: egoitz@ramattack.net X-Msg-Ref: server-7.tower-216.messagelabs.com!1333784538!19306145!1 X-Originating-IP: [194.30.0.207] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk0LjMwLjAuMjA3ID0+IDIwMjE4\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3193 invoked from network); 7 Apr 2012 07:42:19 -0000 Received: from proxypop03.sare.net (HELO proxypop03.sare.net) (194.30.0.207) by server-7.tower-216.messagelabs.com with SMTP; 7 Apr 2012 07:42:19 -0000 Received: from [192.168.12.225] (unknown [212.81.198.13]) by proxypop03.sare.net (Postfix) with ESMTPSA id 74D669DC41D for ; Sat, 7 Apr 2012 09:42:18 +0200 (CEST) From: Egoitz Aurrekoetxea To: xen-api@lists.xen.org Organization: etxea Date: Sat, 07 Apr 2012 09:42:17 +0200 Message-ID: <1333784537.3868.8.camel@mactoo> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 Subject: [Xen-API] XenCloud, Xapi and FreeBSD X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: egoitz@ramattack.net 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 Good morning, I would like to make a suggestion from this mailing list. I'm working at an ISP environment and we're running Xen Cloud as virtualization infrastructure. For a large number of years we have been running FreeBSD (an nowadays... we run it too...).. although FreeBSD seems to run pretty nice under XenCloud (with XENHVM kernel) the interacion with xapi and XenServerTools are not supported for this (IMHO) nice operating system. It gives so much possibilities to experienced sysadmins that I think that other OS like Centos (for example) are totally in clear disadvantage with this BSD Os (for some several reasons which I could debate in other moment). So I would to suggest from here to add support for FreeBSD at XenServerTools and to be able to take advantage of this fine api with this fine OS. Is it planned to give FreeBSD support to xapi?. If not, I could try to take some time for trying to write it. Thank you very much for you're time. Best regards, _______________________________________________ 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 Apr 07 08:12:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 07 Apr 2012 08:12: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 1SGQkv-0001gS-UZ; Sat, 07 Apr 2012 08:12:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SGQku-0001gJ-84 for xen-api@lists.xen.org; Sat, 07 Apr 2012 08:12:20 +0000 Received: from [85.158.139.83:14636] by server-5.bemta-5.messagelabs.com id 68/81-13566-3E6FF7F4; Sat, 07 Apr 2012 08:12:19 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1333786338!22847132!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MzI3OQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31340 invoked from network); 7 Apr 2012 08:12:18 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2012 08:12:18 -0000 X-IronPort-AV: E=Sophos;i="4.75,385,1330905600"; d="scan'208";a="11818789" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Apr 2012 08:12:17 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Sat, 7 Apr 2012 09:12:17 +0100 From: Dave Scott To: "egoitz@ramattack.net" Date: Sat, 7 Apr 2012 09:12:16 +0100 Thread-Topic: [Xen-API] XenCloud, Xapi and FreeBSD Thread-Index: Ac0UliVTVL2TL4xaSM618UrSLpenmA== Message-ID: References: <1333784537.3868.8.camel@mactoo> In-Reply-To: <1333784537.3868.8.camel@mactoo> 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] XenCloud, Xapi and FreeBSD 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, I'm not aware of anyone trying to port the tools to FreeBSD. However, it should be quite simple because the tools are just a couple of shell scripts which write to xenstore (using "xenstore-write") So I think you would need to: 1. Make sure the "xenstore-*" commands work (you might need to set an environment variable first, to allow them to find the right kernel device) 2. Customize the Linux shell scripts -- they need to know how to get the VM's IP addresses etc (replace eth0 with xn0?) 3. Make sure the scripts start up as a system service 4. Contribute your work o the FreeBSD ports tree? HTH, Dave -- Dave Scott XenServer System Architect On Apr 7, 2012, at 8:43 AM, "Egoitz Aurrekoetxea" wrote: > Good morning, > > I would like to make a suggestion from this mailing list. > > I'm working at an ISP environment and we're running Xen Cloud as > virtualization infrastructure. For a large number of years we have been > running FreeBSD (an nowadays... we run it too...).. although FreeBSD > seems to run pretty nice under XenCloud (with XENHVM kernel) the > interacion with xapi and XenServerTools are not supported for this > (IMHO) nice operating system. It gives so much possibilities to > experienced sysadmins that I think that other OS like Centos (for > example) are totally in clear disadvantage with this BSD Os (for some > several reasons which I could debate in other moment). So I would to > suggest from here to add support for FreeBSD at XenServerTools and to be > able to take advantage of this fine api with this fine OS. > > Is it planned to give FreeBSD support to xapi?. If not, I could try to > take some time for trying to write it. > > Thank you very much for you're time. > Best regards, > > > _______________________________________________ > 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 Apr 07 08:12:30 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 07 Apr 2012 08:12: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 1SGQkv-0001gS-UZ; Sat, 07 Apr 2012 08:12:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SGQku-0001gJ-84 for xen-api@lists.xen.org; Sat, 07 Apr 2012 08:12:20 +0000 Received: from [85.158.139.83:14636] by server-5.bemta-5.messagelabs.com id 68/81-13566-3E6FF7F4; Sat, 07 Apr 2012 08:12:19 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1333786338!22847132!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MzI3OQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31340 invoked from network); 7 Apr 2012 08:12:18 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 7 Apr 2012 08:12:18 -0000 X-IronPort-AV: E=Sophos;i="4.75,385,1330905600"; d="scan'208";a="11818789" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 07 Apr 2012 08:12:17 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Sat, 7 Apr 2012 09:12:17 +0100 From: Dave Scott To: "egoitz@ramattack.net" Date: Sat, 7 Apr 2012 09:12:16 +0100 Thread-Topic: [Xen-API] XenCloud, Xapi and FreeBSD Thread-Index: Ac0UliVTVL2TL4xaSM618UrSLpenmA== Message-ID: References: <1333784537.3868.8.camel@mactoo> In-Reply-To: <1333784537.3868.8.camel@mactoo> 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] XenCloud, Xapi and FreeBSD 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, I'm not aware of anyone trying to port the tools to FreeBSD. However, it should be quite simple because the tools are just a couple of shell scripts which write to xenstore (using "xenstore-write") So I think you would need to: 1. Make sure the "xenstore-*" commands work (you might need to set an environment variable first, to allow them to find the right kernel device) 2. Customize the Linux shell scripts -- they need to know how to get the VM's IP addresses etc (replace eth0 with xn0?) 3. Make sure the scripts start up as a system service 4. Contribute your work o the FreeBSD ports tree? HTH, Dave -- Dave Scott XenServer System Architect On Apr 7, 2012, at 8:43 AM, "Egoitz Aurrekoetxea" wrote: > Good morning, > > I would like to make a suggestion from this mailing list. > > I'm working at an ISP environment and we're running Xen Cloud as > virtualization infrastructure. For a large number of years we have been > running FreeBSD (an nowadays... we run it too...).. although FreeBSD > seems to run pretty nice under XenCloud (with XENHVM kernel) the > interacion with xapi and XenServerTools are not supported for this > (IMHO) nice operating system. It gives so much possibilities to > experienced sysadmins that I think that other OS like Centos (for > example) are totally in clear disadvantage with this BSD Os (for some > several reasons which I could debate in other moment). So I would to > suggest from here to add support for FreeBSD at XenServerTools and to be > able to take advantage of this fine api with this fine OS. > > Is it planned to give FreeBSD support to xapi?. If not, I could try to > take some time for trying to write it. > > Thank you very much for you're time. > Best regards, > > > _______________________________________________ > 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 Apr 07 08:17:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 07 Apr 2012 08:17: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 1SGQpi-0001nh-DW; Sat, 07 Apr 2012 08:17:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SGQpg-0001nc-Jh for xen-api@lists.xen.org; Sat, 07 Apr 2012 08:17:16 +0000 Received: from [85.158.143.99:46765] by server-3.bemta-4.messagelabs.com id BD/EA-05853-B08FF7F4; Sat, 07 Apr 2012 08:17:15 +0000 X-Env-Sender: egoitz@ramattack.net X-Msg-Ref: server-6.tower-216.messagelabs.com!1333786635!22640292!1 X-Originating-IP: [194.30.0.65] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk0LjMwLjAuNjUgPT4gODk0MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8609 invoked from network); 7 Apr 2012 08:17:15 -0000 Received: from proxypop04.sare.net (HELO proxypop04.sare.net) (194.30.0.65) by server-6.tower-216.messagelabs.com with SMTP; 7 Apr 2012 08:17:15 -0000 Received: from [192.168.12.225] (unknown [212.81.198.13]) by proxypop04.sare.net (Postfix) with ESMTPSA id 4220A9DC417; Sat, 7 Apr 2012 10:17:14 +0200 (CEST) From: Egoitz Aurrekoetxea To: Dave Scott In-Reply-To: References: <1333784537.3868.8.camel@mactoo> Organization: etxea Date: Sat, 07 Apr 2012 10:17:13 +0200 Message-ID: <1333786633.3868.12.camel@mactoo> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XenCloud, Xapi and FreeBSD X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: egoitz@ramattack.net 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 Including for stoping the virtual machine, sleeping, moving to another host and so Dave?. Xentools port is available for FreeBSD so I assume this could be. On Sat, 2012-04-07 at 09:12 +0100, Dave Scott wrote: > Hi, > > I'm not aware of anyone trying to port the tools to FreeBSD. However, it should be quite simple because the tools are just a couple of shell scripts which write to xenstore (using "xenstore-write") > > So I think you would need to: > > 1. Make sure the "xenstore-*" commands work (you might need to set an environment variable first, to allow them to find the right kernel device) > Any kind of test I could do?? Till the moment FreeBSD is running quite nice at the XCP apart of the fact is not having XenServerTools installed... but yes Xentools and XENHVM kernel. > 2. Customize the Linux shell scripts -- they need to know how to get the VM's IP addresses etc (replace eth0 with xn0?) > There's no problem on that.... > 3. Make sure the scripts start up as a system service > No problem too.... > 4. Contribute your work o the FreeBSD ports tree? > Of course!!! this is important for those who love FreeBSD for they're servers!! It's not the same working mode as don't know Debian for example... or Centos... and some people manages much more better with FreeBSD... so just shell scripts you say?? > HTH, > 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 Sat Apr 07 08:17:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 07 Apr 2012 08:17: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 1SGQpi-0001nh-DW; Sat, 07 Apr 2012 08:17:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SGQpg-0001nc-Jh for xen-api@lists.xen.org; Sat, 07 Apr 2012 08:17:16 +0000 Received: from [85.158.143.99:46765] by server-3.bemta-4.messagelabs.com id BD/EA-05853-B08FF7F4; Sat, 07 Apr 2012 08:17:15 +0000 X-Env-Sender: egoitz@ramattack.net X-Msg-Ref: server-6.tower-216.messagelabs.com!1333786635!22640292!1 X-Originating-IP: [194.30.0.65] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk0LjMwLjAuNjUgPT4gODk0MQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8609 invoked from network); 7 Apr 2012 08:17:15 -0000 Received: from proxypop04.sare.net (HELO proxypop04.sare.net) (194.30.0.65) by server-6.tower-216.messagelabs.com with SMTP; 7 Apr 2012 08:17:15 -0000 Received: from [192.168.12.225] (unknown [212.81.198.13]) by proxypop04.sare.net (Postfix) with ESMTPSA id 4220A9DC417; Sat, 7 Apr 2012 10:17:14 +0200 (CEST) From: Egoitz Aurrekoetxea To: Dave Scott In-Reply-To: References: <1333784537.3868.8.camel@mactoo> Organization: etxea Date: Sat, 07 Apr 2012 10:17:13 +0200 Message-ID: <1333786633.3868.12.camel@mactoo> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] XenCloud, Xapi and FreeBSD X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: egoitz@ramattack.net 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 Including for stoping the virtual machine, sleeping, moving to another host and so Dave?. Xentools port is available for FreeBSD so I assume this could be. On Sat, 2012-04-07 at 09:12 +0100, Dave Scott wrote: > Hi, > > I'm not aware of anyone trying to port the tools to FreeBSD. However, it should be quite simple because the tools are just a couple of shell scripts which write to xenstore (using "xenstore-write") > > So I think you would need to: > > 1. Make sure the "xenstore-*" commands work (you might need to set an environment variable first, to allow them to find the right kernel device) > Any kind of test I could do?? Till the moment FreeBSD is running quite nice at the XCP apart of the fact is not having XenServerTools installed... but yes Xentools and XENHVM kernel. > 2. Customize the Linux shell scripts -- they need to know how to get the VM's IP addresses etc (replace eth0 with xn0?) > There's no problem on that.... > 3. Make sure the scripts start up as a system service > No problem too.... > 4. Contribute your work o the FreeBSD ports tree? > Of course!!! this is important for those who love FreeBSD for they're servers!! It's not the same working mode as don't know Debian for example... or Centos... and some people manages much more better with FreeBSD... so just shell scripts you say?? > HTH, > 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 Sun Apr 08 00:41:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 08 Apr 2012 00:41: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 1SGgBb-0001Fo-Q0; Sun, 08 Apr 2012 00:40:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SGgBa-0001Fj-Aq for xen-api@lists.xensource.com; Sun, 08 Apr 2012 00:40:54 +0000 Received: from [193.109.254.147:27871] by server-9.bemta-14.messagelabs.com id 8D/F8-05787-59ED08F4; Sun, 08 Apr 2012 00:40:53 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1333845652!541333!1 X-Originating-IP: [209.85.214.43] 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 25884 invoked from network); 8 Apr 2012 00:40:53 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Apr 2012 00:40:53 -0000 Received: by bkwj5 with SMTP id j5so2948776bkw.30 for ; Sat, 07 Apr 2012 17:40:52 -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:content-transfer-encoding; bh=B0czJxrn5OuoukTqrCuMZ5OA7DQvN920mDwcKXeknaU=; b=hG9LlTTfXsMG71Elu/RVqBn1S7WKpJ385iCuKxImfzzknwdMCKyMvaumJa9gFOnx5A 985YXidlU1/xBuf2JFW6KLGxl/YhcsOB7z7KeMVJFeawsCSmXNNuxpW/vPZX+uyNr/y5 IeQQENX5L2xLyZAyWP1aerUYMxiQ2rAGkAkumtRJWMGu9v44YxObfCKAnbzXZM8Eiw2L rZ6ME8p+sK2fSKxg4uTVMYOpplQor1/klpLhYwwC+fjyNg16DmUYz1ZXV/IPSolW6URh FYY0isb43X1Re+yMIhaBo7o7JlPHmkfYVVvwh9+MpDN8i0jFU6ftm2QyO3abr4jYDSuP BT+A== Received: by 10.204.154.66 with SMTP id n2mr1216499bkw.77.1333845652434; Sat, 07 Apr 2012 17:40:52 -0700 (PDT) Received: from [10.13.77.220] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id zx16sm21929418bkb.13.2012.04.07.17.40.50 (version=SSLv3 cipher=OTHER); Sat, 07 Apr 2012 17:40:51 -0700 (PDT) Message-ID: <4F80DE91.2070105@gmail.com> Date: Sun, 08 Apr 2012 04:40:49 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120402 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" Subject: [Xen-API] [XCP] [BUG] [SM] wrong filter in lvm.conf with multipath-enabled SR (LVMoISCSI) 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. Summary: filter statement in lvm.conf does not prevent LVM to use wrong PV for iscsi/multipath LVM SR's. Configuration: SR (LVMoISCSI), enabled multipath. Hosts do have options "multipathing: true; multipathhandle: dmp;" in other-config. multipath -ll shows normally operating MP disk. But one of the host shows in pvdisplay output that PV is on '/dev/sdc', not on /dev/mapper/long-mutlipath-id. I looked to /etc/lvm/lvm.conf and found it has filter option like this: filter = [ "r|/dev/xvd.|", "r|/dev/VG_Xen.*/LV.*|" ] (no /dev/sd*) I think there is some chance this cause lvm tools make /dev/sd* device PV for LVM, not multipathed one. This happens only on one host in whole pool, so it looks be very rare situation (but it is repeatable, every pbd-plug). I done some adhoc fix with filtering out all /dev/sd* devices, but for normal fix this shall be coded somewhere in SM, because by fix turn off all normal LVMoISCSI and local LVM SR's... _______________________________________________ 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 Sun Apr 08 00:41:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 08 Apr 2012 00:41: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 1SGgBb-0001Fo-Q0; Sun, 08 Apr 2012 00:40:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SGgBa-0001Fj-Aq for xen-api@lists.xensource.com; Sun, 08 Apr 2012 00:40:54 +0000 Received: from [193.109.254.147:27871] by server-9.bemta-14.messagelabs.com id 8D/F8-05787-59ED08F4; Sun, 08 Apr 2012 00:40:53 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1333845652!541333!1 X-Originating-IP: [209.85.214.43] 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 25884 invoked from network); 8 Apr 2012 00:40:53 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Apr 2012 00:40:53 -0000 Received: by bkwj5 with SMTP id j5so2948776bkw.30 for ; Sat, 07 Apr 2012 17:40:52 -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:content-transfer-encoding; bh=B0czJxrn5OuoukTqrCuMZ5OA7DQvN920mDwcKXeknaU=; b=hG9LlTTfXsMG71Elu/RVqBn1S7WKpJ385iCuKxImfzzknwdMCKyMvaumJa9gFOnx5A 985YXidlU1/xBuf2JFW6KLGxl/YhcsOB7z7KeMVJFeawsCSmXNNuxpW/vPZX+uyNr/y5 IeQQENX5L2xLyZAyWP1aerUYMxiQ2rAGkAkumtRJWMGu9v44YxObfCKAnbzXZM8Eiw2L rZ6ME8p+sK2fSKxg4uTVMYOpplQor1/klpLhYwwC+fjyNg16DmUYz1ZXV/IPSolW6URh FYY0isb43X1Re+yMIhaBo7o7JlPHmkfYVVvwh9+MpDN8i0jFU6ftm2QyO3abr4jYDSuP BT+A== Received: by 10.204.154.66 with SMTP id n2mr1216499bkw.77.1333845652434; Sat, 07 Apr 2012 17:40:52 -0700 (PDT) Received: from [10.13.77.220] (desunote.ru. [95.161.2.76]) by mx.google.com with ESMTPS id zx16sm21929418bkb.13.2012.04.07.17.40.50 (version=SSLv3 cipher=OTHER); Sat, 07 Apr 2012 17:40:51 -0700 (PDT) Message-ID: <4F80DE91.2070105@gmail.com> Date: Sun, 08 Apr 2012 04:40:49 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120402 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" Subject: [Xen-API] [XCP] [BUG] [SM] wrong filter in lvm.conf with multipath-enabled SR (LVMoISCSI) 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. Summary: filter statement in lvm.conf does not prevent LVM to use wrong PV for iscsi/multipath LVM SR's. Configuration: SR (LVMoISCSI), enabled multipath. Hosts do have options "multipathing: true; multipathhandle: dmp;" in other-config. multipath -ll shows normally operating MP disk. But one of the host shows in pvdisplay output that PV is on '/dev/sdc', not on /dev/mapper/long-mutlipath-id. I looked to /etc/lvm/lvm.conf and found it has filter option like this: filter = [ "r|/dev/xvd.|", "r|/dev/VG_Xen.*/LV.*|" ] (no /dev/sd*) I think there is some chance this cause lvm tools make /dev/sd* device PV for LVM, not multipathed one. This happens only on one host in whole pool, so it looks be very rare situation (but it is repeatable, every pbd-plug). I done some adhoc fix with filtering out all /dev/sd* devices, but for normal fix this shall be coded somewhere in SM, because by fix turn off all normal LVMoISCSI and local LVM SR's... _______________________________________________ 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 Apr 10 08:43:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 10 Apr 2012 08:43:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SHWfn-0000qS-NJ; Tue, 10 Apr 2012 08:43:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SHWfm-0000qN-6N for xen-api@lists.xen.org; Tue, 10 Apr 2012 08:43:34 +0000 Received: from [193.109.254.147:56014] by server-9.bemta-14.messagelabs.com id 09/64-05787-5B2F38F4; Tue, 10 Apr 2012 08:43:33 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1334047412!3890849!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MzMxNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5495 invoked from network); 10 Apr 2012 08:43:33 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2012 08:43:33 -0000 X-IronPort-AV: E=Sophos;i="4.75,398,1330905600"; d="scan'208";a="11844449" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Apr 2012 08:43:32 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Tue, 10 Apr 2012 09:43:32 +0100 From: Paul Durrant To: Vasiliy Tolstov Date: Tue, 10 Apr 2012 09:44:01 +0100 Thread-Topic: [Xen-API] where find sources for windows software on xs-tools.iso? Thread-Index: Ac0T4LGkhym9h8D9Tui4BXJ4BiidtQDFTSGw Message-ID: <291EDFCB1E9E224A99088639C4762022C8235B7024@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C812021BA9@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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VmFzaWxpeSwNCg0KICBBbGFzLCBubyBJIGhhdmVuJ3QuIEkndmUgYXNrZWQgbXkgbWFuYWdlbWVu dCBmb3IgYXBwcm92YWwgdG8gcHVibGlzaCBidXQgaGVhcmQgbm90aGluZyBiYWNrLiBJJ2xsIHBp bmcgdGhlbSBhZ2Fpbi4NCg0KICBQYXVsDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N Cj4gRnJvbTogdmFzZUBzZWxmaXAucnUgW21haWx0bzp2YXNlQHNlbGZpcC5ydV0gT24gQmVoYWxm IE9mIFZhc2lsaXkgVG9sc3Rvdg0KPiBTZW50OiAwNiBBcHJpbCAyMDEyIDExOjMzDQo+IFRvOiBQ YXVsIER1cnJhbnQNCj4gQ2M6IHhlbi1hcGlAbGlzdHMueGVuLm9yZw0KPiBTdWJqZWN0OiBSZTog W1hlbi1BUEldIHdoZXJlIGZpbmQgc291cmNlcyBmb3Igd2luZG93cyBzb2Z0d2FyZSBvbiB4cy0N Cj4gdG9vbHMuaXNvPw0KPiANCj4gMjAxMi80LzIgUGF1bCBEdXJyYW50IDxQYXVsLkR1cnJhbnRA Y2l0cml4LmNvbT46DQo+ID4gwqBBcyBJIHNhaWQsIHRoZSBXTUkgQVBJIGlzIG5vdCBwdWJsaXNo ZWQgYXMgeWV0LiBJJ2xsIHNlZSB3aGF0IEkgY2FuIGRvIGFib3V0DQo+IGdldHRpbmcgYXBwcm92 YWwgdG8gZG8gdGhpcy4NCj4gDQo+IEhlbGxvLCBkbyB5b3UgaGF2ZSBhbnkgcHJvZ3Jlc3M/DQo+ IA0KPiANCj4gLS0NCj4gVmFzaWxpeSBUb2xzdG92LA0KPiBDbG9kby5ydQ0KPiBlLW1haWw6IHYu dG9sc3RvdkBzZWxmaXAucnUNCj4gamFiYmVyOiB2YXNlQHNlbGZpcC5ydQ0KX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KeGVuLWFwaSBtYWlsaW5nIGxpc3QK eGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1h bi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Tue Apr 10 08:43:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 10 Apr 2012 08:43:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SHWfn-0000qS-NJ; Tue, 10 Apr 2012 08:43:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SHWfm-0000qN-6N for xen-api@lists.xen.org; Tue, 10 Apr 2012 08:43:34 +0000 Received: from [193.109.254.147:56014] by server-9.bemta-14.messagelabs.com id 09/64-05787-5B2F38F4; Tue, 10 Apr 2012 08:43:33 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1334047412!3890849!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5MzMxNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5495 invoked from network); 10 Apr 2012 08:43:33 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2012 08:43:33 -0000 X-IronPort-AV: E=Sophos;i="4.75,398,1330905600"; d="scan'208";a="11844449" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 10 Apr 2012 08:43:32 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Tue, 10 Apr 2012 09:43:32 +0100 From: Paul Durrant To: Vasiliy Tolstov Date: Tue, 10 Apr 2012 09:44:01 +0100 Thread-Topic: [Xen-API] where find sources for windows software on xs-tools.iso? Thread-Index: Ac0T4LGkhym9h8D9Tui4BXJ4BiidtQDFTSGw Message-ID: <291EDFCB1E9E224A99088639C4762022C8235B7024@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C812021BA9@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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VmFzaWxpeSwNCg0KICBBbGFzLCBubyBJIGhhdmVuJ3QuIEkndmUgYXNrZWQgbXkgbWFuYWdlbWVu dCBmb3IgYXBwcm92YWwgdG8gcHVibGlzaCBidXQgaGVhcmQgbm90aGluZyBiYWNrLiBJJ2xsIHBp bmcgdGhlbSBhZ2Fpbi4NCg0KICBQYXVsDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N Cj4gRnJvbTogdmFzZUBzZWxmaXAucnUgW21haWx0bzp2YXNlQHNlbGZpcC5ydV0gT24gQmVoYWxm IE9mIFZhc2lsaXkgVG9sc3Rvdg0KPiBTZW50OiAwNiBBcHJpbCAyMDEyIDExOjMzDQo+IFRvOiBQ YXVsIER1cnJhbnQNCj4gQ2M6IHhlbi1hcGlAbGlzdHMueGVuLm9yZw0KPiBTdWJqZWN0OiBSZTog W1hlbi1BUEldIHdoZXJlIGZpbmQgc291cmNlcyBmb3Igd2luZG93cyBzb2Z0d2FyZSBvbiB4cy0N Cj4gdG9vbHMuaXNvPw0KPiANCj4gMjAxMi80LzIgUGF1bCBEdXJyYW50IDxQYXVsLkR1cnJhbnRA Y2l0cml4LmNvbT46DQo+ID4gwqBBcyBJIHNhaWQsIHRoZSBXTUkgQVBJIGlzIG5vdCBwdWJsaXNo ZWQgYXMgeWV0LiBJJ2xsIHNlZSB3aGF0IEkgY2FuIGRvIGFib3V0DQo+IGdldHRpbmcgYXBwcm92 YWwgdG8gZG8gdGhpcy4NCj4gDQo+IEhlbGxvLCBkbyB5b3UgaGF2ZSBhbnkgcHJvZ3Jlc3M/DQo+ IA0KPiANCj4gLS0NCj4gVmFzaWxpeSBUb2xzdG92LA0KPiBDbG9kby5ydQ0KPiBlLW1haWw6IHYu dG9sc3RvdkBzZWxmaXAucnUNCj4gamFiYmVyOiB2YXNlQHNlbGZpcC5ydQ0KX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KeGVuLWFwaSBtYWlsaW5nIGxpc3QK eGVuLWFwaUBsaXN0cy54ZW4ub3JnCmh0dHA6Ly9saXN0cy54ZW4ub3JnL2NnaS1iaW4vbWFpbG1h bi9saXN0aW5mby94ZW4tYXBpCg== From xen-api-bounces@lists.xen.org Tue Apr 10 09:17:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 10 Apr 2012 09:17:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SHXCk-0001Nb-6r; Tue, 10 Apr 2012 09:17:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SHXCh-0001NJ-HU for xen-api@lists.xen.org; Tue, 10 Apr 2012 09:17:36 +0000 Received: from [193.109.254.147:41102] by server-5.bemta-14.messagelabs.com id 19/70-30733-EAAF38F4; Tue, 10 Apr 2012 09:17:34 +0000 X-Env-Sender: vase@selfip.ru X-Msg-Ref: server-8.tower-27.messagelabs.com!1334049453!3898982!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 13996 invoked from network); 10 Apr 2012 09:17:33 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2012 09:17:33 -0000 Received: by lahe6 with SMTP id e6so4990599lah.32 for ; Tue, 10 Apr 2012 02:17:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfip.ru; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=r8+8nd6hvYEc9Mb5zQc5L2PlEFwwJxwLTud1slEgLsU=; b=UnmciPtGiAprdbkdlRu9AoFs6mZBdzJg6ZXrgRTCB5djP2J925/Mk2j3pcrGPIqSR3 YYFHQMP8VGSr8a6bf4A2LUVhK759imjC7/TLlkAAu95ecGNs316dW1X5fQWw9tdPnD42 07LrR5K3wdHrx0XJLVqUlzk9RZysiePTMTJJc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip: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=r8+8nd6hvYEc9Mb5zQc5L2PlEFwwJxwLTud1slEgLsU=; b=J4qbwM8Z14H+MDhiDFwRgfW0ch1bb8rr6kS54HJHwC8yChybIxhyFX0kSNXRZaLmwn OIEj+JC+PoTBaAKqRWQTVIAUYdYNA00f3gR+RNjliR8/I9dnQSA9GTiLcQcMFmrx+MX1 WiP9rEMHAIDN004YciTP9N0+SP5ksw2FP9bVU+OojkeYOD50nysmIi9xbt4S/4GT4wAg o4u3k8d1YYx9c0HKh2Gdp4IaewI0oU+M8zsmYS5r4zhRvUA72LYDUY0WZGZqRbNS04Q5 9QGe8eQXepVcsOgGEfFidBPCQ6FWXEb1D6l1cjH0xup7ekL1D7BF2det/VAOBx7nXjaw VRuw== Received: by 10.112.10.41 with SMTP id f9mr969405lbb.46.1334049452966; Tue, 10 Apr 2012 02:17:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.37.234 with HTTP; Tue, 10 Apr 2012 02:17:17 -0700 (PDT) X-Originating-IP: [85.143.161.18] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C8235B7024@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C812021BA9@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C8235B7024@LONPMAILBOX01.citrite.net> From: Vasiliy Tolstov Date: Tue, 10 Apr 2012 13:17:17 +0400 X-Google-Sender-Auth: HRHHpEcbJG-ZDvnYsbqbB3waX3g Message-ID: To: Paul Durrant X-Gm-Message-State: ALoCoQlEAG0A90LDWrrrjx3VF/75uSHvMUlI+JkIAdssmQ7dfdDlRrOwdl8ESrwFe51B1HQXNBxl 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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MjAxMi80LzEwIFBhdWwgRHVycmFudCA8UGF1bC5EdXJyYW50QGNpdHJpeC5jb20+Ogo+IFZhc2ls aXksCj4KPiDCoEFsYXMsIG5vIEkgaGF2ZW4ndC4gSSd2ZSBhc2tlZCBteSBtYW5hZ2VtZW50IGZv ciBhcHByb3ZhbCB0byBwdWJsaXNoIGJ1dCBoZWFyZCBub3RoaW5nIGJhY2suIEknbGwgcGluZyB0 aGVtIGFnYWluLgo+Cj4gwqBQYXVsCj4KClRoYW5rcyEKCi0tIApWYXNpbGl5IFRvbHN0b3YsCkNs b2RvLnJ1CmUtbWFpbDogdi50b2xzdG92QHNlbGZpcC5ydQpqYWJiZXI6IHZhc2VAc2VsZmlwLnJ1 CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwp4ZW4tYXBp IG1haWxpbmcgbGlzdAp4ZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Tue Apr 10 09:17:46 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 10 Apr 2012 09:17:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SHXCk-0001Nb-6r; Tue, 10 Apr 2012 09:17:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SHXCh-0001NJ-HU for xen-api@lists.xen.org; Tue, 10 Apr 2012 09:17:36 +0000 Received: from [193.109.254.147:41102] by server-5.bemta-14.messagelabs.com id 19/70-30733-EAAF38F4; Tue, 10 Apr 2012 09:17:34 +0000 X-Env-Sender: vase@selfip.ru X-Msg-Ref: server-8.tower-27.messagelabs.com!1334049453!3898982!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 13996 invoked from network); 10 Apr 2012 09:17:33 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Apr 2012 09:17:33 -0000 Received: by lahe6 with SMTP id e6so4990599lah.32 for ; Tue, 10 Apr 2012 02:17:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfip.ru; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=r8+8nd6hvYEc9Mb5zQc5L2PlEFwwJxwLTud1slEgLsU=; b=UnmciPtGiAprdbkdlRu9AoFs6mZBdzJg6ZXrgRTCB5djP2J925/Mk2j3pcrGPIqSR3 YYFHQMP8VGSr8a6bf4A2LUVhK759imjC7/TLlkAAu95ecGNs316dW1X5fQWw9tdPnD42 07LrR5K3wdHrx0XJLVqUlzk9RZysiePTMTJJc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip: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=r8+8nd6hvYEc9Mb5zQc5L2PlEFwwJxwLTud1slEgLsU=; b=J4qbwM8Z14H+MDhiDFwRgfW0ch1bb8rr6kS54HJHwC8yChybIxhyFX0kSNXRZaLmwn OIEj+JC+PoTBaAKqRWQTVIAUYdYNA00f3gR+RNjliR8/I9dnQSA9GTiLcQcMFmrx+MX1 WiP9rEMHAIDN004YciTP9N0+SP5ksw2FP9bVU+OojkeYOD50nysmIi9xbt4S/4GT4wAg o4u3k8d1YYx9c0HKh2Gdp4IaewI0oU+M8zsmYS5r4zhRvUA72LYDUY0WZGZqRbNS04Q5 9QGe8eQXepVcsOgGEfFidBPCQ6FWXEb1D6l1cjH0xup7ekL1D7BF2det/VAOBx7nXjaw VRuw== Received: by 10.112.10.41 with SMTP id f9mr969405lbb.46.1334049452966; Tue, 10 Apr 2012 02:17:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.37.234 with HTTP; Tue, 10 Apr 2012 02:17:17 -0700 (PDT) X-Originating-IP: [85.143.161.18] In-Reply-To: <291EDFCB1E9E224A99088639C4762022C8235B7024@LONPMAILBOX01.citrite.net> References: <291EDFCB1E9E224A99088639C4762022C812021A78@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C812021BA9@LONPMAILBOX01.citrite.net> <291EDFCB1E9E224A99088639C4762022C8235B7024@LONPMAILBOX01.citrite.net> From: Vasiliy Tolstov Date: Tue, 10 Apr 2012 13:17:17 +0400 X-Google-Sender-Auth: HRHHpEcbJG-ZDvnYsbqbB3waX3g Message-ID: To: Paul Durrant X-Gm-Message-State: ALoCoQlEAG0A90LDWrrrjx3VF/75uSHvMUlI+JkIAdssmQ7dfdDlRrOwdl8ESrwFe51B1HQXNBxl 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="utf-8" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org MjAxMi80LzEwIFBhdWwgRHVycmFudCA8UGF1bC5EdXJyYW50QGNpdHJpeC5jb20+Ogo+IFZhc2ls aXksCj4KPiDCoEFsYXMsIG5vIEkgaGF2ZW4ndC4gSSd2ZSBhc2tlZCBteSBtYW5hZ2VtZW50IGZv ciBhcHByb3ZhbCB0byBwdWJsaXNoIGJ1dCBoZWFyZCBub3RoaW5nIGJhY2suIEknbGwgcGluZyB0 aGVtIGFnYWluLgo+Cj4gwqBQYXVsCj4KClRoYW5rcyEKCi0tIApWYXNpbGl5IFRvbHN0b3YsCkNs b2RvLnJ1CmUtbWFpbDogdi50b2xzdG92QHNlbGZpcC5ydQpqYWJiZXI6IHZhc2VAc2VsZmlwLnJ1 CgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwp4ZW4tYXBp IG1haWxpbmcgbGlzdAp4ZW4tYXBpQGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcv Y2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Fri Apr 13 03:01:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 13 Apr 2012 03:01: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 1SIWlC-0006yU-Bw; Fri, 13 Apr 2012 03:01:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SG57J-0007la-FX for xen-api@lists.xen.org; Fri, 06 Apr 2012 09:06:01 +0000 Received: from [193.109.254.147:32330] by server-3.bemta-14.messagelabs.com id 4C/87-23274-8F1BE7F4; Fri, 06 Apr 2012 09:06:00 +0000 X-Env-Sender: suixiufeng@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1333703158!3490895!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, 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 21301 invoked from network); 6 Apr 2012 09:05:59 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Apr 2012 09:05:59 -0000 Received: by obbup19 with SMTP id up19so1882543obb.32 for ; Fri, 06 Apr 2012 02:05:58 -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 :content-type; bh=JfSH+KT6pijzKjRtsUyRFYK6XBY5Z+r2Naz3oTyGXjs=; b=ylSo7upI3nSLLPLZB3WfeDSkp4i9GTYLxPVi2pCzpCxn3m2MGdS1uK+vBK4NJxRA3v U8VorHkx+a/wLJmrxjU6w4K8DjbnDsQxKfXZl1gcNUdMR+kP9VZ1BsZzyvcCI2IjbiuW xUMLH1GBlc/CzvxwSsudzKywTHOvYMMq3mZR0zjK0bUZB8Dlnu6GX70/Sn/8bgZmlEC/ fn6soKQf3JFLhEEL//aMNpoDoCAO/p9oeNRdExWYmXfacLaW9c4q5fPe203yX3EqKorr mgRswjsXc5A0Pp2QAUoWXU48IJPLpI09E6wT4e10TBP1BGyzgBxjWAyoJVHkpLFEUM5U 1+zA== MIME-Version: 1.0 Received: by 10.182.108.3 with SMTP id hg3mr8106445obb.29.1333703158050; Fri, 06 Apr 2012 02:05:58 -0700 (PDT) Received: by 10.182.213.41 with HTTP; Fri, 6 Apr 2012 02:05:58 -0700 (PDT) In-Reply-To: References: Date: Fri, 6 Apr 2012 17:05:58 +0800 Message-ID: From: suixiufeng To: xen-api@lists.xen.org X-Mailman-Approved-At: Fri, 13 Apr 2012 03:01:17 +0000 Subject: [Xen-API] Fwd: Xenoprof 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: multipart/mixed; boundary="===============2517065071891363951==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2517065071891363951== Content-Type: multipart/alternative; boundary=f46d0447854ff8ae4404bcfef681 --f46d0447854ff8ae4404bcfef681 Content-Type: text/plain; charset=ISO-8859-1 ---------- Forwarded message ---------- From: suixiufeng Date: 2012/4/6 Subject: Xenoprof on XCP To: xen-devel@lists.xensource.com Hi, I am trying to use xenoprof to monitor the performance of benchmarks running on a XCP based systems. I have installed the xenoprof tools on both XCP_Dom0 and a debian VM. But when I run the following command on debian VM, opcontrol --start-daemon --event=CPU_CLK_UNHALTED:1000000:1:1:1 --xen=/boot/xen-syms-3.4.2 --vmlinux=/usr/src/linux-source-2.6.32/vmlinux I get the error message: You cannot specify any performance counter events because OProfile is in timer mode. I am not sure how to use event based profile on debian VM running on top of XCP. Does this message mean that the VCPU virtualized by XCP can't be recognized by xenoprof? Thank you! --f46d0447854ff8ae4404bcfef681 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ----------<= br>From: suixiufeng <= ;suixiufeng@gmail.com>
Date: 2012/4/6
Subject: Xenoprof on XCP
To: xen-devel@lists.xensource.com


Hi,=A0 =A0I am trying to use xenoprof to monitor the performance of benchmar= ks running on a XCP based systems. I have installed the xenoprof tools on b= oth XCP_Dom0 and a debian VM. But when I run the following command on debia= n VM,
=A0 =A0
=A0 =A0opcontrol --start-daemon --event=3DCPU_CLK_UN= HALTED:1000000:1:1:1 --xen=3D/boot/xen-syms-3.4.2 --vmlinux=3D/usr/src/linu= x-source-2.6.32/vmlinux

=A0 =A0I get the error mes= sage:=A0
=A0 =A0
=A0 =A0You cannot specify any performance counter events<= /div>
=A0 =A0because OProfile is in timer mode.

=A0 =A0I am not sure how to use event based profile on debian VM running = on top of XCP. Does this message mean that the VCPU virtualized by XCP can&= #39;t be recognized by xenoprof? Thank you!

=A0 =A0

--f46d0447854ff8ae4404bcfef681-- --===============2517065071891363951== 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 --===============2517065071891363951==-- From xen-api-bounces@lists.xen.org Fri Apr 13 03:01:26 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 13 Apr 2012 03:01: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 1SIWlC-0006yU-Bw; Fri, 13 Apr 2012 03:01:18 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SG57J-0007la-FX for xen-api@lists.xen.org; Fri, 06 Apr 2012 09:06:01 +0000 Received: from [193.109.254.147:32330] by server-3.bemta-14.messagelabs.com id 4C/87-23274-8F1BE7F4; Fri, 06 Apr 2012 09:06:00 +0000 X-Env-Sender: suixiufeng@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1333703158!3490895!1 X-Originating-IP: [209.85.214.173] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, 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 21301 invoked from network); 6 Apr 2012 09:05:59 -0000 Received: from mail-ob0-f173.google.com (HELO mail-ob0-f173.google.com) (209.85.214.173) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Apr 2012 09:05:59 -0000 Received: by obbup19 with SMTP id up19so1882543obb.32 for ; Fri, 06 Apr 2012 02:05:58 -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 :content-type; bh=JfSH+KT6pijzKjRtsUyRFYK6XBY5Z+r2Naz3oTyGXjs=; b=ylSo7upI3nSLLPLZB3WfeDSkp4i9GTYLxPVi2pCzpCxn3m2MGdS1uK+vBK4NJxRA3v U8VorHkx+a/wLJmrxjU6w4K8DjbnDsQxKfXZl1gcNUdMR+kP9VZ1BsZzyvcCI2IjbiuW xUMLH1GBlc/CzvxwSsudzKywTHOvYMMq3mZR0zjK0bUZB8Dlnu6GX70/Sn/8bgZmlEC/ fn6soKQf3JFLhEEL//aMNpoDoCAO/p9oeNRdExWYmXfacLaW9c4q5fPe203yX3EqKorr mgRswjsXc5A0Pp2QAUoWXU48IJPLpI09E6wT4e10TBP1BGyzgBxjWAyoJVHkpLFEUM5U 1+zA== MIME-Version: 1.0 Received: by 10.182.108.3 with SMTP id hg3mr8106445obb.29.1333703158050; Fri, 06 Apr 2012 02:05:58 -0700 (PDT) Received: by 10.182.213.41 with HTTP; Fri, 6 Apr 2012 02:05:58 -0700 (PDT) In-Reply-To: References: Date: Fri, 6 Apr 2012 17:05:58 +0800 Message-ID: From: suixiufeng To: xen-api@lists.xen.org X-Mailman-Approved-At: Fri, 13 Apr 2012 03:01:17 +0000 Subject: [Xen-API] Fwd: Xenoprof 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: multipart/mixed; boundary="===============2517065071891363951==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============2517065071891363951== Content-Type: multipart/alternative; boundary=f46d0447854ff8ae4404bcfef681 --f46d0447854ff8ae4404bcfef681 Content-Type: text/plain; charset=ISO-8859-1 ---------- Forwarded message ---------- From: suixiufeng Date: 2012/4/6 Subject: Xenoprof on XCP To: xen-devel@lists.xensource.com Hi, I am trying to use xenoprof to monitor the performance of benchmarks running on a XCP based systems. I have installed the xenoprof tools on both XCP_Dom0 and a debian VM. But when I run the following command on debian VM, opcontrol --start-daemon --event=CPU_CLK_UNHALTED:1000000:1:1:1 --xen=/boot/xen-syms-3.4.2 --vmlinux=/usr/src/linux-source-2.6.32/vmlinux I get the error message: You cannot specify any performance counter events because OProfile is in timer mode. I am not sure how to use event based profile on debian VM running on top of XCP. Does this message mean that the VCPU virtualized by XCP can't be recognized by xenoprof? Thank you! --f46d0447854ff8ae4404bcfef681 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ----------<= br>From: suixiufeng <= ;suixiufeng@gmail.com>
Date: 2012/4/6
Subject: Xenoprof on XCP
To: xen-devel@lists.xensource.com


Hi,=A0 =A0I am trying to use xenoprof to monitor the performance of benchmar= ks running on a XCP based systems. I have installed the xenoprof tools on b= oth XCP_Dom0 and a debian VM. But when I run the following command on debia= n VM,
=A0 =A0
=A0 =A0opcontrol --start-daemon --event=3DCPU_CLK_UN= HALTED:1000000:1:1:1 --xen=3D/boot/xen-syms-3.4.2 --vmlinux=3D/usr/src/linu= x-source-2.6.32/vmlinux

=A0 =A0I get the error mes= sage:=A0
=A0 =A0
=A0 =A0You cannot specify any performance counter events<= /div>
=A0 =A0because OProfile is in timer mode.

=A0 =A0I am not sure how to use event based profile on debian VM running = on top of XCP. Does this message mean that the VCPU virtualized by XCP can&= #39;t be recognized by xenoprof? Thank you!

=A0 =A0

--f46d0447854ff8ae4404bcfef681-- --===============2517065071891363951== 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 --===============2517065071891363951==-- From xen-api-bounces@lists.xen.org Fri Apr 13 10:27:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 13 Apr 2012 10:27:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SIdj1-0006Wo-Sf; Fri, 13 Apr 2012 10:27:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SIdj0-0006Wj-Mi for xen-api@lists.xen.org; Fri, 13 Apr 2012 10:27:30 +0000 Received: from [85.158.143.99:44792] by server-1.bemta-4.messagelabs.com id AF/4D-20925-09FF78F4; Fri, 13 Apr 2012 10:27:28 +0000 X-Env-Sender: Marcus.Granado@eu.citrix.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1334312845!23450903!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NDEzNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16299 invoked from network); 13 Apr 2012 10:27:26 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Apr 2012 10:27:26 -0000 X-IronPort-AV: E=Sophos;i="4.75,416,1330905600"; d="scan'208,217";a="11922125" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Apr 2012 10:27:24 +0000 Received: from [10.80.3.59] (10.80.3.59) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 13 Apr 2012 11:27:24 +0100 Message-ID: <4F87FF88.6050000@citrix.com> Date: Fri, 13 Apr 2012 11:27:20 +0100 From: Marcus Granado User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120313 Thunderbird/11.0 MIME-Version: 1.0 To: suixiufeng References: In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Fwd: Xenoprof 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: multipart/mixed; boundary="===============8694784461327317395==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8694784461327317395== Content-Type: multipart/alternative; boundary="------------000300040000030209080601" --------------000300040000030209080601 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 06/04/12 10:05, suixiufeng wrote: > > Hi, > I am trying to use xenoprof to monitor the performance of > benchmarks running on a XCP based systems. I have installed the > xenoprof tools on both XCP_Dom0 and a debian VM. But when I run the > following command on debian VM, > opcontrol --start-daemon --event=CPU_CLK_UNHALTED:1000000:1:1:1 > --xen=/boot/xen-syms-3.4.2 --vmlinux=/usr/src/linux-source-2.6.32/vmlinux > > I get the error message: > You cannot specify any performance counter events > because OProfile is in timer mode. > > I am not sure how to use event based profile on debian VM running > on top of XCP. Does this message mean that the VCPU virtualized by XCP > can't be recognized by xenoprof? Thank you! > > xenoprof should be started on both dom0 (with the --active-domains= param ) and the pv debian vm. The following links have step-by-step instructions: http://fedoraproject.org/wiki/Tools/XenoprofGuide http://xenoprof.sourceforge.net/xenoprof_2.0.txt cheers, Marcus --------------000300040000030209080601 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 06/04/12 10:05, suixiufeng wrote:

Hi,
   I am trying to use xenoprof to monitor the performance of benchmarks running on a XCP based systems. I have installed the xenoprof tools on both XCP_Dom0 and a debian VM. But when I run the following command on debian VM,
   
   opcontrol --start-daemon --event=CPU_CLK_UNHALTED:1000000:1:1:1 --xen=/boot/xen-syms-3.4.2 --vmlinux=/usr/src/linux-source-2.6.32/vmlinux

   I get the error message: 
   
   You cannot specify any performance counter events
   because OProfile is in timer mode.

   I am not sure how to use event based profile on debian VM running on top of XCP. Does this message mean that the VCPU virtualized by XCP can't be recognized by xenoprof? Thank you!

  

xenoprof should be started on both dom0 (with the --active-domains=<pv-debian-vm-id>  param ) and the pv debian vm.
The following links have step-by-step instructions:
http://fedoraproject.org/wiki/Tools/XenoprofGuide
http://xenoprof.sourceforge.net/xenoprof_2.0.txt

cheers,
Marcus

--------------000300040000030209080601-- --===============8694784461327317395== 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 --===============8694784461327317395==-- From xen-api-bounces@lists.xen.org Fri Apr 13 10:27:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 13 Apr 2012 10:27:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SIdj1-0006Wo-Sf; Fri, 13 Apr 2012 10:27:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SIdj0-0006Wj-Mi for xen-api@lists.xen.org; Fri, 13 Apr 2012 10:27:30 +0000 Received: from [85.158.143.99:44792] by server-1.bemta-4.messagelabs.com id AF/4D-20925-09FF78F4; Fri, 13 Apr 2012 10:27:28 +0000 X-Env-Sender: Marcus.Granado@eu.citrix.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1334312845!23450903!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NDEzNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16299 invoked from network); 13 Apr 2012 10:27:26 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 13 Apr 2012 10:27:26 -0000 X-IronPort-AV: E=Sophos;i="4.75,416,1330905600"; d="scan'208,217";a="11922125" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 13 Apr 2012 10:27:24 +0000 Received: from [10.80.3.59] (10.80.3.59) by LONPMAILMX01.citrite.net (10.30.203.162) with Microsoft SMTP Server id 8.3.213.0; Fri, 13 Apr 2012 11:27:24 +0100 Message-ID: <4F87FF88.6050000@citrix.com> Date: Fri, 13 Apr 2012 11:27:20 +0100 From: Marcus Granado User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120313 Thunderbird/11.0 MIME-Version: 1.0 To: suixiufeng References: In-Reply-To: Cc: "xen-api@lists.xen.org" Subject: Re: [Xen-API] Fwd: Xenoprof 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: multipart/mixed; boundary="===============8694784461327317395==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============8694784461327317395== Content-Type: multipart/alternative; boundary="------------000300040000030209080601" --------------000300040000030209080601 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 06/04/12 10:05, suixiufeng wrote: > > Hi, > I am trying to use xenoprof to monitor the performance of > benchmarks running on a XCP based systems. I have installed the > xenoprof tools on both XCP_Dom0 and a debian VM. But when I run the > following command on debian VM, > opcontrol --start-daemon --event=CPU_CLK_UNHALTED:1000000:1:1:1 > --xen=/boot/xen-syms-3.4.2 --vmlinux=/usr/src/linux-source-2.6.32/vmlinux > > I get the error message: > You cannot specify any performance counter events > because OProfile is in timer mode. > > I am not sure how to use event based profile on debian VM running > on top of XCP. Does this message mean that the VCPU virtualized by XCP > can't be recognized by xenoprof? Thank you! > > xenoprof should be started on both dom0 (with the --active-domains= param ) and the pv debian vm. The following links have step-by-step instructions: http://fedoraproject.org/wiki/Tools/XenoprofGuide http://xenoprof.sourceforge.net/xenoprof_2.0.txt cheers, Marcus --------------000300040000030209080601 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 06/04/12 10:05, suixiufeng wrote:

Hi,
   I am trying to use xenoprof to monitor the performance of benchmarks running on a XCP based systems. I have installed the xenoprof tools on both XCP_Dom0 and a debian VM. But when I run the following command on debian VM,
   
   opcontrol --start-daemon --event=CPU_CLK_UNHALTED:1000000:1:1:1 --xen=/boot/xen-syms-3.4.2 --vmlinux=/usr/src/linux-source-2.6.32/vmlinux

   I get the error message: 
   
   You cannot specify any performance counter events
   because OProfile is in timer mode.

   I am not sure how to use event based profile on debian VM running on top of XCP. Does this message mean that the VCPU virtualized by XCP can't be recognized by xenoprof? Thank you!

  

xenoprof should be started on both dom0 (with the --active-domains=<pv-debian-vm-id>  param ) and the pv debian vm.
The following links have step-by-step instructions:
http://fedoraproject.org/wiki/Tools/XenoprofGuide
http://xenoprof.sourceforge.net/xenoprof_2.0.txt

cheers,
Marcus

--------------000300040000030209080601-- --===============8694784461327317395== 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 --===============8694784461327317395==-- From xen-api-bounces@lists.xen.org Mon Apr 16 08:47:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 16 Apr 2012 08:47:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJhaU-0007fr-DV; Mon, 16 Apr 2012 08:47:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJhaS-0007fm-IG for xen-api@lists.xen.org; Mon, 16 Apr 2012 08:47:04 +0000 Received: from [85.158.138.51:10708] by server-1.bemta-3.messagelabs.com id 6A/C2-11491-78CDB8F4; Mon, 16 Apr 2012 08:47:03 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-11.tower-174.messagelabs.com!1334566022!22255508!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29648 invoked from network); 16 Apr 2012 08:47:03 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-11.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Apr 2012 08:47:03 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id C838EFE118; Mon, 16 Apr 2012 08:47: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 :content-transfer-encoding; s=postfix; bh=OxUadrW8KqWP+CdQiIAqoz Z69Po=; b=W3Uo13N5gGj0d2PR9+IJT1Wx6AXftib4F6WCg6OhtFwOxKS+y8f9TN ovEullSqqw9nMtpiXdF50i3jmeErpss86dZeYGNUhEfl0mlFQtrkh43cF41366nw KY4XAGEHHeqQLe39ci4ZvqRKMpjhGKSxj/vqgnaBh1p604H2C+/PE= 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=xrodFh2vkg99G/35 ZSzQkw/72clC0EqFkJcfXRwlJh9S3o/mMqPi29FxTk+XQlFfyuFgxXZVfBch8NsZ Nb/VSiS9jcbqtZh9xKHMa+yA4Sa9wW819SnSuvo++aXjkJMLZAip0Ts4K23fBgLj aOqvPHDWWJBezUBJEW8hM+ckEmI= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id A4DA6FE068; Mon, 16 Apr 2012 08:47:44 +0000 (UTC) Message-ID: <4F8BDC82.1090000@goirand.fr> Date: Mon, 16 Apr 2012 16:46:58 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120317 Icedove/3.0.11 MIME-Version: 1.0 To: Jon Ludlam , Mike McClurg , "xen-api@lists.xen.org" X-Enigmail-Version: 1.0.1 Subject: [Xen-API] New Debian release of xen-api and VLAN creation errors 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 RGVhciBKb24gYW5kIE1pa2UsCgpTaW5jZSB3ZSBhZGRlZCBhIG5ldyBkZWJjb25mIHF1ZXN0aW9u IHRvIHNlbGVjdCBvcGVudnN3aXRjaCBvciBiaXJkZ2luZywKdGhlIGRlYmlhbi9jb250cm9sIHBh Y2thZ2UgZGVzY3JpcHRpb25zIGFuZApkZWJpYW4veGNwLW5ldHdvcmtkLnRlbXBsYXRlcyBoYXMg YmVlbiByZXZpZXdlZCBieSB0aGUKZGViaWFuLWwxMG4tZW5nbGlzaCB0ZWFtLCBhbmQgdHJhbnNs YXRlZCB0byBtYW55IGxhbmd1YWdlczoKCiAgKiBEZWJjb25mIHRlbXBsYXRlcyBhbmQgZGViaWFu L2NvbnRyb2wgcmV2aWV3ZWQgYnkgdGhlIGRlYmlhbi1sMTBuLQogICAgZW5nbGlzaCB0ZWFtIGFz IHBhcnQgb2YgdGhlIFNtaXRoIHJldmlldyBwcm9qZWN0LiBDbG9zZXM6ICM2NjM0NzMKICAqIFtE ZWJjb25mIHRyYW5zbGF0aW9uIHVwZGF0ZXNdCiAgKiBQb2xpc2ggKE1pY2hhxYIgS3XFgmFjaCku ICBDbG9zZXM6ICM2NjU5NzcKICAqIFJ1c3NpYW4gKFl1cmkgS296bG92KS4gIENsb3NlczogIzY2 NTk5NAogICogRGFuaXNoIChKb2UgSGFuc2VuKS4gIENsb3NlczogIzY2NjUxOAogICogQ3plY2gg KE1pY2hhbCBTaW11bmVrKS4gIENsb3NlczogIzY2NjU1MQogICogRnJlbmNoIChUaG9tYXMgVmlu Y2VudCkuICBDbG9zZXM6ICM2Njc1NDkKICAqIEJyYXppbGlhbiBQb3J0dWd1ZXNlIChBZHJpYW5v IFJhZmFlbCBHb21lcykuICBDbG9zZXM6ICM2NjgwOTAKICAqIEl0YWxpYW4gKEJlYXRyaWNlIFRv cnJhY2NhKS4gIENsb3NlczogIzY2ODE2MgogICogU3BhbmlzaDsgKENhbWFsZcOzbikuICBDbG9z ZXM6ICM2NjgxODMKICAqIEdlcm1hbiAoQ2hyaXMgTGVpY2spLiAgQ2xvc2VzOiAjNjY2NzEyCiAg KiBTd2VkaXNoIChNYXJ0aW4gQmFnZ2UgLyBicm90aGVyKS4gIENsb3NlczogIzY2ODI5MAogICog UG9ydHVndWVzZSAoTWlndWVsIEZpZ3VlaXJlZG8pLiAgQ2xvc2VzOiAjNjY4MzEwCiAgKiBEdXRj aDsgKEplcm9lbiBTY2hvdCkuICBDbG9zZXM6ICM2Njg1MjcKICAqIFNpbXBsaWZpZWQgQ2hpbmVz ZSAoQ2FvIFdlaSAvIOabueeOrikuCgpUaGF0IGxhc3Qgb25lIGhhcyBiZWVuIHRyYW5zbGF0ZWQg dG8gQ2hpbmVzZSBieSBteSB3aWZlISA6KQoKU28gSSB3b3VsZCBzdWdnZXN0IHlvdSB0byBwdWxs IGZyb20gdGhlIGRlYmlhbi1zaWQgYnJhbmNoIG9uIEFsaW90aCwgc28KeW91IGdldCB0aGUgdHJh bnNsYXRpb25zLiBJIHdvdWxkIGFsc28gc3VnZ2VzdCB0aGF0IFVidW50dSBnZXRzIHRoZQp0cmFu c2xhdGlvbiBiZWZvcmUgdGhlIG5leHQgTFRTIGlzIHJlbGVhc2VkLiBKb24sIHNpbmNlIE1pa2Ug aXMgb24KaG9saWRheXMsIG1heWJlIHlvdSBjYW4gcHVzaCB0aGUgYWJvdmUgdG8gdGhlIHhlbm9y ZyBnaXRodWIgcmVwb3NpdG9yeT8KCkFsc28sIEknbSBoYXZpbmcgaXNzdWVzIHdpdGggdGhlIHZs YW4tY3JlYXRlIGNvbW1hbmQgdXNpbmcgdGhlIGN1cnJlbnRseQpyZWxlYXNlZCBwYWNrYWdlOgoK cm9vdEBub2RlNDQwNzp+IyB4ZSB2bGFuLWNyZWF0ZSBwaWYtdXVpZD0ke0VUSDBfUElGfSB2bGFu PTIKbmV0d29yay11dWlkPSRuZXQKQW4gdW5rbm93biBlcnJvciBvY2N1cnJlZCB3aGlsZSBhdHRl bXB0aW5nIHRvIGNvbmZpZ3VyZSBhbiBpbnRlcmZhY2UuClBJRjogZjZlZWIwNDgtMzIzMC00YmI0 LTFhMjItNDAxOTQwZTZiNGZhCm1zZzogU0NSSVBUX0VSUk9SIFtzY3JpcHQgPSAvc2Jpbi9pcCwg YXJncyA9IGxpbmsgc2V0IHhhcGk2IHVwLCBjb2RlID0KMSwgc3Rkb3V0ID0gLCBzdGRlcnIgPSBD YW5ub3QgZmluZCBkZXZpY2UgInhhcGk2IgpdCgpNeSBiZWxpZWYgaXMgdGhhdCB4YXBpNiBzaG91 bGQgYmUgYXV0b21hdGljYWxseSBjcmVhdGVkLiBEbyB5b3Uga25vdwp3aGF0J3MgZ29pbmcgb24/ ICh0aGF0J3Mgd2hlbiB1c2luZyBvcGVudnN3aXRjaCBvZiBjb3Vyc2UuLi4pCgpDaGVlcnMsCgpU aG9tYXMgR29pcmFuZAoKUC5TOiBNeSBJT0FUIGlzc3VlIGhhcyBiZWVuIGZpeGVkIGluIHRoZSBE ZWJpYW4ga2VybmVsIHBhY2thZ2UsIGFuZCBpbgp1cHN0cmVhbSBsaW51eCwgYWZ0ZXIgYSBsb25n IHJlcG9ydGluZyBhbmQgdGVzdGluZyBwZXJpb2Q6Clt4ODZdIGlvYXQ6IGZpeCBzaXplIG9mICdj b21wbGV0aW9uJyBmb3IgWGVuIChDbG9zZXM6ICM2NjA1NTQpCgpfX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXwp4ZW4tYXBpIG1haWxpbmcgbGlzdAp4ZW4tYXBp QGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Mon Apr 16 08:47:13 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 16 Apr 2012 08:47:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJhaU-0007fr-DV; Mon, 16 Apr 2012 08:47:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJhaS-0007fm-IG for xen-api@lists.xen.org; Mon, 16 Apr 2012 08:47:04 +0000 Received: from [85.158.138.51:10708] by server-1.bemta-3.messagelabs.com id 6A/C2-11491-78CDB8F4; Mon, 16 Apr 2012 08:47:03 +0000 X-Env-Sender: thomas@goirand.fr X-Msg-Ref: server-11.tower-174.messagelabs.com!1334566022!22255508!1 X-Originating-IP: [117.121.247.104] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29648 invoked from network); 16 Apr 2012 08:47:03 -0000 Received: from mx.atlanta.gplhost.com (HELO mx.atlanta.gplhost.com) (117.121.247.104) by server-11.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Apr 2012 08:47:03 -0000 Received: from mx.atlanta.gplhost.com (localhost.localdomain [127.0.0.1]) by mx.atlanta.gplhost.com (Postfix) with ESMTP id C838EFE118; Mon, 16 Apr 2012 08:47: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 :content-transfer-encoding; s=postfix; bh=OxUadrW8KqWP+CdQiIAqoz Z69Po=; b=W3Uo13N5gGj0d2PR9+IJT1Wx6AXftib4F6WCg6OhtFwOxKS+y8f9TN ovEullSqqw9nMtpiXdF50i3jmeErpss86dZeYGNUhEfl0mlFQtrkh43cF41366nw KY4XAGEHHeqQLe39ci4ZvqRKMpjhGKSxj/vqgnaBh1p604H2C+/PE= 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=xrodFh2vkg99G/35 ZSzQkw/72clC0EqFkJcfXRwlJh9S3o/mMqPi29FxTk+XQlFfyuFgxXZVfBch8NsZ Nb/VSiS9jcbqtZh9xKHMa+yA4Sa9wW819SnSuvo++aXjkJMLZAip0Ts4K23fBgLj aOqvPHDWWJBezUBJEW8hM+ckEmI= Received: from [127.0.0.1] (atl.apt-proxy.gplhost.com [117.121.247.20]) by mx.atlanta.gplhost.com (Postfix) with ESMTPA id A4DA6FE068; Mon, 16 Apr 2012 08:47:44 +0000 (UTC) Message-ID: <4F8BDC82.1090000@goirand.fr> Date: Mon, 16 Apr 2012 16:46:58 +0800 From: Thomas Goirand Organization: GPLHost User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120317 Icedove/3.0.11 MIME-Version: 1.0 To: Jon Ludlam , Mike McClurg , "xen-api@lists.xen.org" X-Enigmail-Version: 1.0.1 Subject: [Xen-API] New Debian release of xen-api and VLAN creation errors 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 RGVhciBKb24gYW5kIE1pa2UsCgpTaW5jZSB3ZSBhZGRlZCBhIG5ldyBkZWJjb25mIHF1ZXN0aW9u IHRvIHNlbGVjdCBvcGVudnN3aXRjaCBvciBiaXJkZ2luZywKdGhlIGRlYmlhbi9jb250cm9sIHBh Y2thZ2UgZGVzY3JpcHRpb25zIGFuZApkZWJpYW4veGNwLW5ldHdvcmtkLnRlbXBsYXRlcyBoYXMg YmVlbiByZXZpZXdlZCBieSB0aGUKZGViaWFuLWwxMG4tZW5nbGlzaCB0ZWFtLCBhbmQgdHJhbnNs YXRlZCB0byBtYW55IGxhbmd1YWdlczoKCiAgKiBEZWJjb25mIHRlbXBsYXRlcyBhbmQgZGViaWFu L2NvbnRyb2wgcmV2aWV3ZWQgYnkgdGhlIGRlYmlhbi1sMTBuLQogICAgZW5nbGlzaCB0ZWFtIGFz IHBhcnQgb2YgdGhlIFNtaXRoIHJldmlldyBwcm9qZWN0LiBDbG9zZXM6ICM2NjM0NzMKICAqIFtE ZWJjb25mIHRyYW5zbGF0aW9uIHVwZGF0ZXNdCiAgKiBQb2xpc2ggKE1pY2hhxYIgS3XFgmFjaCku ICBDbG9zZXM6ICM2NjU5NzcKICAqIFJ1c3NpYW4gKFl1cmkgS296bG92KS4gIENsb3NlczogIzY2 NTk5NAogICogRGFuaXNoIChKb2UgSGFuc2VuKS4gIENsb3NlczogIzY2NjUxOAogICogQ3plY2gg KE1pY2hhbCBTaW11bmVrKS4gIENsb3NlczogIzY2NjU1MQogICogRnJlbmNoIChUaG9tYXMgVmlu Y2VudCkuICBDbG9zZXM6ICM2Njc1NDkKICAqIEJyYXppbGlhbiBQb3J0dWd1ZXNlIChBZHJpYW5v IFJhZmFlbCBHb21lcykuICBDbG9zZXM6ICM2NjgwOTAKICAqIEl0YWxpYW4gKEJlYXRyaWNlIFRv cnJhY2NhKS4gIENsb3NlczogIzY2ODE2MgogICogU3BhbmlzaDsgKENhbWFsZcOzbikuICBDbG9z ZXM6ICM2NjgxODMKICAqIEdlcm1hbiAoQ2hyaXMgTGVpY2spLiAgQ2xvc2VzOiAjNjY2NzEyCiAg KiBTd2VkaXNoIChNYXJ0aW4gQmFnZ2UgLyBicm90aGVyKS4gIENsb3NlczogIzY2ODI5MAogICog UG9ydHVndWVzZSAoTWlndWVsIEZpZ3VlaXJlZG8pLiAgQ2xvc2VzOiAjNjY4MzEwCiAgKiBEdXRj aDsgKEplcm9lbiBTY2hvdCkuICBDbG9zZXM6ICM2Njg1MjcKICAqIFNpbXBsaWZpZWQgQ2hpbmVz ZSAoQ2FvIFdlaSAvIOabueeOrikuCgpUaGF0IGxhc3Qgb25lIGhhcyBiZWVuIHRyYW5zbGF0ZWQg dG8gQ2hpbmVzZSBieSBteSB3aWZlISA6KQoKU28gSSB3b3VsZCBzdWdnZXN0IHlvdSB0byBwdWxs IGZyb20gdGhlIGRlYmlhbi1zaWQgYnJhbmNoIG9uIEFsaW90aCwgc28KeW91IGdldCB0aGUgdHJh bnNsYXRpb25zLiBJIHdvdWxkIGFsc28gc3VnZ2VzdCB0aGF0IFVidW50dSBnZXRzIHRoZQp0cmFu c2xhdGlvbiBiZWZvcmUgdGhlIG5leHQgTFRTIGlzIHJlbGVhc2VkLiBKb24sIHNpbmNlIE1pa2Ug aXMgb24KaG9saWRheXMsIG1heWJlIHlvdSBjYW4gcHVzaCB0aGUgYWJvdmUgdG8gdGhlIHhlbm9y ZyBnaXRodWIgcmVwb3NpdG9yeT8KCkFsc28sIEknbSBoYXZpbmcgaXNzdWVzIHdpdGggdGhlIHZs YW4tY3JlYXRlIGNvbW1hbmQgdXNpbmcgdGhlIGN1cnJlbnRseQpyZWxlYXNlZCBwYWNrYWdlOgoK cm9vdEBub2RlNDQwNzp+IyB4ZSB2bGFuLWNyZWF0ZSBwaWYtdXVpZD0ke0VUSDBfUElGfSB2bGFu PTIKbmV0d29yay11dWlkPSRuZXQKQW4gdW5rbm93biBlcnJvciBvY2N1cnJlZCB3aGlsZSBhdHRl bXB0aW5nIHRvIGNvbmZpZ3VyZSBhbiBpbnRlcmZhY2UuClBJRjogZjZlZWIwNDgtMzIzMC00YmI0 LTFhMjItNDAxOTQwZTZiNGZhCm1zZzogU0NSSVBUX0VSUk9SIFtzY3JpcHQgPSAvc2Jpbi9pcCwg YXJncyA9IGxpbmsgc2V0IHhhcGk2IHVwLCBjb2RlID0KMSwgc3Rkb3V0ID0gLCBzdGRlcnIgPSBD YW5ub3QgZmluZCBkZXZpY2UgInhhcGk2IgpdCgpNeSBiZWxpZWYgaXMgdGhhdCB4YXBpNiBzaG91 bGQgYmUgYXV0b21hdGljYWxseSBjcmVhdGVkLiBEbyB5b3Uga25vdwp3aGF0J3MgZ29pbmcgb24/ ICh0aGF0J3Mgd2hlbiB1c2luZyBvcGVudnN3aXRjaCBvZiBjb3Vyc2UuLi4pCgpDaGVlcnMsCgpU aG9tYXMgR29pcmFuZAoKUC5TOiBNeSBJT0FUIGlzc3VlIGhhcyBiZWVuIGZpeGVkIGluIHRoZSBE ZWJpYW4ga2VybmVsIHBhY2thZ2UsIGFuZCBpbgp1cHN0cmVhbSBsaW51eCwgYWZ0ZXIgYSBsb25n IHJlcG9ydGluZyBhbmQgdGVzdGluZyBwZXJpb2Q6Clt4ODZdIGlvYXQ6IGZpeCBzaXplIG9mICdj b21wbGV0aW9uJyBmb3IgWGVuIChDbG9zZXM6ICM2NjA1NTQpCgpfX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXwp4ZW4tYXBpIG1haWxpbmcgbGlzdAp4ZW4tYXBp QGxpc3RzLnhlbi5vcmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Mon Apr 16 10:21:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 16 Apr 2012 10:21:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJj40-0001IL-2S; Mon, 16 Apr 2012 10:21:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJj3y-0001IF-66 for xen-api@lists.xensource.com; Mon, 16 Apr 2012 10:21:38 +0000 Received: from [193.109.254.147:35073] by server-10.bemta-14.messagelabs.com id BE/13-05847-1B2FB8F4; Mon, 16 Apr 2012 10:21:37 +0000 X-Env-Sender: chris.percol@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1334571693!4748700!1 X-Originating-IP: [209.85.214.43] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3362 invoked from network); 16 Apr 2012 10:21:34 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Apr 2012 10:21:34 -0000 Received: by bkwj5 with SMTP id j5so4215364bkw.30 for ; Mon, 16 Apr 2012 03:21:33 -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=4PTkTlE2zwF0oNNlG2r4wutcqSdt0GA2OrnI8/jE+YE=; b=ozFIXjxCL6zB/SBdbOwX+t5HviK7oB+ouf0j+IwuFDfFstq3bYeMYyZqk99cVxV7QY q9QQLz/osTGI0cevrRVMEWNyVuUzp4bVxuUmKLXyA204eEuI5MZDGbPd2Bpz6g843a2j hpqgwYnV0BH+H3/f+MbN7rBCUXjcQ0AsgUSZa1FhXOQqLMV6DzvfxEKFgKaoFzkH9ytd h+Jp4J/Svs4AH+GmJK7+Hhb9hol6nK4QIxgTj9rQQF6JxaqXTvioqbac5gG6w1m6QcVb y45fdMqEvnTBqO7oqAMtJEIET51wTvuSWabguuQ98+JagsVmlewxl1rYwgVaCR8f7nHy 5Ipw== MIME-Version: 1.0 Received: by 10.204.152.18 with SMTP id e18mr3468198bkw.83.1334571693398; Mon, 16 Apr 2012 03:21:33 -0700 (PDT) Received: by 10.205.33.203 with HTTP; Mon, 16 Apr 2012 03:21:33 -0700 (PDT) Date: Mon, 16 Apr 2012 11:21:33 +0100 Message-ID: From: Chris Percol To: xen-api@lists.xensource.com Subject: [Xen-API] Network Failure on XCP 5.6.199-42052c Host 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, I was hoping for help troubleshooting an issue we had on one of our hosts, XCP 5.6.199-42052c. Supermicro H7DGU with 2x8 Opteron CPUs and 96Gb RAM, last night. Although the network interfaces seemed up on the host we lost connectivity to our firewall which resulted in loss of connectivity to about 30 VMs to the outside world. We have several other hosts so I can confirm the issue was a network failure on this specific host. I tried to resolve the issue but ended up doing a restart and this resolved the problem. The host is using a storage repository on one of VMs using NFS. I noticed in the logs that this VM had issues and I wonder if that somehow brought networking down on the host or maybe this was just a symptom of another issue? Any input would be appreciated. Apr 15 18:21:16 x5 kernel: nfs: server 10.10.0.45 not responding, still trying Apr 15 18:21:17 x5 kernel: INFO: task ovs-vswitchd:5974 blocked for more than 120 seconds. Apr 15 18:21:17 x5 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 15 18:21:17 x5 kernel: ovs-vswitchd D e5722780 0 5974 5973 0x00000004 Apr 15 18:21:17 x5 kernel: db5719dc 00200282 f0973354 e5722780 ee6d9d08 ee6d9e2c ce1c7e44 eab137c0 Apr 15 18:21:17 x5 kernel: 45a4cc39 0028e1e1 edc801d4 edc800c4 edc80030 edc801d4 c16bbf00 00000000 Apr 15 18:21:17 x5 kernel: ede21580 0028e1af c04c1780 00001c9a 00000000 db5719d4 c0147f96 66907e06 Apr 15 18:21:17 x5 kernel: Call Trace: [20120415T19:18:28.958Z|debug|x5|13950 unix-RPC||dummytaskhelper] task dispatch:session.get_uuid D:f2213f2e0c70 created by task D:837c21561a6a [20120415T19:18:28.963Z|debug|x5|13951 unix-RPC||dummytaskhelper] task dispatch:SR.scan D:f1bd29c3d938 created by task D:e02a05d4e0de [20120415T19:18:28.966Z| info|x5|13951 unix-RPC|dispatch:SR.scan D:f1bd29c3d938|taskhelper] task SR.scan R:b45f2439f7e6 (uuid:141c1a50-8da7-a8bb-17f4-1a8d5b337e74) created (trackid=b8f3decedd8451914a904e71cb8d48ad) by task D:e02a05d4e0de [20120415T19:18:28.966Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] SR.scan: SR = '481b5ca8-7a8f-0288-3ec3-43f82a48d454 (NFS ISO library)' [20120415T19:18:28.967Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Marking SR for SR.scan (task=OpaqueRef:b45f2439-f7e6-1ecb-a443-6e844a111348) [20120415T19:18:28.968Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Raised at message_forwarding.ml:322.15-87 -> message_forwarding.ml:2522.13-75 -> pervasiveext.ml:22.2-9 [20120415T19:18:28.968Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Unmarking SR after SR.scan (task=OpaqueRef:b45f2439-f7e6-1ecb-a443-6e844a111348) [20120415T19:18:28.969Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|backtrace] Raised at pervasiveext.ml:26.22-25 -> rbac.ml:230.16-23 [20120415T19:18:28.969Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|backtrace] Raised at rbac.ml:239.10-15 -> server_helpers.ml:77.11-41 [20120415T19:18:28.969Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|dispatcher] Server_helpers.exec exception_handler: Got exception SR_HAS_NO_PBDS: [ OpaqueRef:ca3da3f2-8a8f-4429-1bed-3622ca267ea3 ] [20120415T19:18:28.969Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120415T19:18:28.970Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120415T19:18:28.970Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Raised at server_helpers.ml:92.14-15 -> pervasiveext.ml:22.2-9 [20120415T19:18:28.971Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120415T19:18:28.971Z|debug|x5|13951 unix-RPC|dispatch:SR.scan D:f1bd29c3d938|backtrace] Raised at pervasiveext.ml:26.22-25 -> server_helpers.ml:152.10-106 -> server.ml:23092.19-167 -> server_helpers.ml:118.4-7 [20120415T19:18:28.971Z|debug|x5|13948|scan one D:e02a05d4e0de|backtrace] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120415T19:18:28.971Z|debug|x5|13948|scan one D:e02a05d4e0de|helpers] Ignoring exception: SR_HAS_NO_PBDS: [ OpaqueRef:ca3da3f2-8a8f-4429-1bed-3622ca267ea3 ] while scanning SR OpaqueRef:ca3da3f2-8a8f-4429-1bed-3622ca267ea3 [20120415T19:18:28.973Z|debug|x5|13952 unix-RPC||dummytaskhelper] task dispatch:session.logout D:e962a3b6f080 created by task D:e02a05d4e0de [20120415T19:18:28.975Z| info|x5|13952 unix-RPC|session.logout D:5c78f51f578d|xapi] Session.destroy trackid=b8f3decedd8451914a904e71cb8d48ad [20120415T19:18:58.990Z|debug|x5|723 sr_scan|SR scanner D:4f5c02e4e89b|xapi] Automatically scanning SRs = [ OpaqueRef:ca3da3f2-8a8f-4429-1bed-3622ca267ea3 ] [20120415T19:18:58.991Z|debug|x5|13955||dummytaskhelper] task scan one D:8f644b854713 created by task D:4f5c02e4e89b [20120415T19:18:58.994Z|debug|x5|13956 unix-RPC||dummytaskhelper] task dispatch:session.slave_login D:64dafa62bc40 created by task D:8f644b854713 [20120415T19:18:58.997Z| info|x5|13956 unix-RPC|session.slave_login D:4cdc58a7de1a|xapi] Session.create trackid=81957e954b40fc1946be2d57e76db174 pool=true uname= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 Many thanks, Chris _______________________________________________ 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 Apr 16 10:21:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 16 Apr 2012 10:21:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJj40-0001IL-2S; Mon, 16 Apr 2012 10:21:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJj3y-0001IF-66 for xen-api@lists.xensource.com; Mon, 16 Apr 2012 10:21:38 +0000 Received: from [193.109.254.147:35073] by server-10.bemta-14.messagelabs.com id BE/13-05847-1B2FB8F4; Mon, 16 Apr 2012 10:21:37 +0000 X-Env-Sender: chris.percol@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1334571693!4748700!1 X-Originating-IP: [209.85.214.43] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3362 invoked from network); 16 Apr 2012 10:21:34 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Apr 2012 10:21:34 -0000 Received: by bkwj5 with SMTP id j5so4215364bkw.30 for ; Mon, 16 Apr 2012 03:21:33 -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=4PTkTlE2zwF0oNNlG2r4wutcqSdt0GA2OrnI8/jE+YE=; b=ozFIXjxCL6zB/SBdbOwX+t5HviK7oB+ouf0j+IwuFDfFstq3bYeMYyZqk99cVxV7QY q9QQLz/osTGI0cevrRVMEWNyVuUzp4bVxuUmKLXyA204eEuI5MZDGbPd2Bpz6g843a2j hpqgwYnV0BH+H3/f+MbN7rBCUXjcQ0AsgUSZa1FhXOQqLMV6DzvfxEKFgKaoFzkH9ytd h+Jp4J/Svs4AH+GmJK7+Hhb9hol6nK4QIxgTj9rQQF6JxaqXTvioqbac5gG6w1m6QcVb y45fdMqEvnTBqO7oqAMtJEIET51wTvuSWabguuQ98+JagsVmlewxl1rYwgVaCR8f7nHy 5Ipw== MIME-Version: 1.0 Received: by 10.204.152.18 with SMTP id e18mr3468198bkw.83.1334571693398; Mon, 16 Apr 2012 03:21:33 -0700 (PDT) Received: by 10.205.33.203 with HTTP; Mon, 16 Apr 2012 03:21:33 -0700 (PDT) Date: Mon, 16 Apr 2012 11:21:33 +0100 Message-ID: From: Chris Percol To: xen-api@lists.xensource.com Subject: [Xen-API] Network Failure on XCP 5.6.199-42052c Host 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, I was hoping for help troubleshooting an issue we had on one of our hosts, XCP 5.6.199-42052c. Supermicro H7DGU with 2x8 Opteron CPUs and 96Gb RAM, last night. Although the network interfaces seemed up on the host we lost connectivity to our firewall which resulted in loss of connectivity to about 30 VMs to the outside world. We have several other hosts so I can confirm the issue was a network failure on this specific host. I tried to resolve the issue but ended up doing a restart and this resolved the problem. The host is using a storage repository on one of VMs using NFS. I noticed in the logs that this VM had issues and I wonder if that somehow brought networking down on the host or maybe this was just a symptom of another issue? Any input would be appreciated. Apr 15 18:21:16 x5 kernel: nfs: server 10.10.0.45 not responding, still trying Apr 15 18:21:17 x5 kernel: INFO: task ovs-vswitchd:5974 blocked for more than 120 seconds. Apr 15 18:21:17 x5 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 15 18:21:17 x5 kernel: ovs-vswitchd D e5722780 0 5974 5973 0x00000004 Apr 15 18:21:17 x5 kernel: db5719dc 00200282 f0973354 e5722780 ee6d9d08 ee6d9e2c ce1c7e44 eab137c0 Apr 15 18:21:17 x5 kernel: 45a4cc39 0028e1e1 edc801d4 edc800c4 edc80030 edc801d4 c16bbf00 00000000 Apr 15 18:21:17 x5 kernel: ede21580 0028e1af c04c1780 00001c9a 00000000 db5719d4 c0147f96 66907e06 Apr 15 18:21:17 x5 kernel: Call Trace: [20120415T19:18:28.958Z|debug|x5|13950 unix-RPC||dummytaskhelper] task dispatch:session.get_uuid D:f2213f2e0c70 created by task D:837c21561a6a [20120415T19:18:28.963Z|debug|x5|13951 unix-RPC||dummytaskhelper] task dispatch:SR.scan D:f1bd29c3d938 created by task D:e02a05d4e0de [20120415T19:18:28.966Z| info|x5|13951 unix-RPC|dispatch:SR.scan D:f1bd29c3d938|taskhelper] task SR.scan R:b45f2439f7e6 (uuid:141c1a50-8da7-a8bb-17f4-1a8d5b337e74) created (trackid=b8f3decedd8451914a904e71cb8d48ad) by task D:e02a05d4e0de [20120415T19:18:28.966Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] SR.scan: SR = '481b5ca8-7a8f-0288-3ec3-43f82a48d454 (NFS ISO library)' [20120415T19:18:28.967Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Marking SR for SR.scan (task=OpaqueRef:b45f2439-f7e6-1ecb-a443-6e844a111348) [20120415T19:18:28.968Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Raised at message_forwarding.ml:322.15-87 -> message_forwarding.ml:2522.13-75 -> pervasiveext.ml:22.2-9 [20120415T19:18:28.968Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Unmarking SR after SR.scan (task=OpaqueRef:b45f2439-f7e6-1ecb-a443-6e844a111348) [20120415T19:18:28.969Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|backtrace] Raised at pervasiveext.ml:26.22-25 -> rbac.ml:230.16-23 [20120415T19:18:28.969Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|backtrace] Raised at rbac.ml:239.10-15 -> server_helpers.ml:77.11-41 [20120415T19:18:28.969Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|dispatcher] Server_helpers.exec exception_handler: Got exception SR_HAS_NO_PBDS: [ OpaqueRef:ca3da3f2-8a8f-4429-1bed-3622ca267ea3 ] [20120415T19:18:28.969Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|dispatcher] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120415T19:18:28.970Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|backtrace] Raised at string.ml:150.25-34 -> stringext.ml:108.13-29 [20120415T19:18:28.970Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Raised at server_helpers.ml:92.14-15 -> pervasiveext.ml:22.2-9 [20120415T19:18:28.971Z|debug|x5|13951 unix-RPC|SR.scan R:b45f2439f7e6|xapi] Raised at pervasiveext.ml:26.22-25 -> pervasiveext.ml:22.2-9 [20120415T19:18:28.971Z|debug|x5|13951 unix-RPC|dispatch:SR.scan D:f1bd29c3d938|backtrace] Raised at pervasiveext.ml:26.22-25 -> server_helpers.ml:152.10-106 -> server.ml:23092.19-167 -> server_helpers.ml:118.4-7 [20120415T19:18:28.971Z|debug|x5|13948|scan one D:e02a05d4e0de|backtrace] Raised at hashtbl.ml:93.19-28 -> debug.ml:100.36-65 [20120415T19:18:28.971Z|debug|x5|13948|scan one D:e02a05d4e0de|helpers] Ignoring exception: SR_HAS_NO_PBDS: [ OpaqueRef:ca3da3f2-8a8f-4429-1bed-3622ca267ea3 ] while scanning SR OpaqueRef:ca3da3f2-8a8f-4429-1bed-3622ca267ea3 [20120415T19:18:28.973Z|debug|x5|13952 unix-RPC||dummytaskhelper] task dispatch:session.logout D:e962a3b6f080 created by task D:e02a05d4e0de [20120415T19:18:28.975Z| info|x5|13952 unix-RPC|session.logout D:5c78f51f578d|xapi] Session.destroy trackid=b8f3decedd8451914a904e71cb8d48ad [20120415T19:18:58.990Z|debug|x5|723 sr_scan|SR scanner D:4f5c02e4e89b|xapi] Automatically scanning SRs = [ OpaqueRef:ca3da3f2-8a8f-4429-1bed-3622ca267ea3 ] [20120415T19:18:58.991Z|debug|x5|13955||dummytaskhelper] task scan one D:8f644b854713 created by task D:4f5c02e4e89b [20120415T19:18:58.994Z|debug|x5|13956 unix-RPC||dummytaskhelper] task dispatch:session.slave_login D:64dafa62bc40 created by task D:8f644b854713 [20120415T19:18:58.997Z| info|x5|13956 unix-RPC|session.slave_login D:4cdc58a7de1a|xapi] Session.create trackid=81957e954b40fc1946be2d57e76db174 pool=true uname= is_local_superuser=true auth_user_sid= parent=trackid=9834f5af41c964e225f24279aefe4e49 Many thanks, Chris _______________________________________________ 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 Apr 16 13:44:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 16 Apr 2012 13:44: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 1SJmDn-0006Te-2F; Mon, 16 Apr 2012 13:43:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJmDk-0006TS-W6 for xen-api@lists.xen.org; Mon, 16 Apr 2012 13:43:57 +0000 Received: from [85.158.143.35:3041] by server-2.bemta-4.messagelabs.com id A1/3C-17550-C122C8F4; Mon, 16 Apr 2012 13:43:56 +0000 X-Env-Sender: fubinzhang@ict.ac.cn X-Msg-Ref: server-14.tower-21.messagelabs.com!1334583833!16342228!1 X-Originating-IP: [159.226.251.23] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6148 invoked from network); 16 Apr 2012 13:43:55 -0000 Received: from smtp23.cstnet.cn (HELO cstnet.cn) (159.226.251.23) by server-14.tower-21.messagelabs.com with SMTP; 16 Apr 2012 13:43:55 -0000 Received: from [10.30.0.243] (unknown [159.226.43.35]) by app3 (Coremail) with SMTP id SQCowJBLaAcXIoxPQEIPAA--.49451S2; Mon, 16 Apr 2012 21:43:51 +0800 (CST) Message-ID: <4F8C2217.6050407@ict.ac.cn> Date: Mon, 16 Apr 2012 21:43:51 +0800 From: Fu Bin-zhang User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: xen-api@lists.xen.org X-CM-TRANSID: SQCowJBLaAcXIoxPQEIPAA--.49451S2 X-Coremail-Antispam: 1UD129KBjvdXoWrtFWDJF1xZFykZFWDJF1kXwb_yoWxuwb_GF yqv3WkXryjyF4Igr17Cr4YqrWrKa1DWr1jy34rtFsrK347trsrXF9IgrsYv34Ivw4UGrn8 AFyrXa1akry2kjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUjXAYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k042IE 4asKkaVY67AtM7k0a2IF6F4UM7kC6x804xWl14x267AKxVWUJVW8JwAFc2x0x2IEx4CE42 xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2z4x0Y4vE2Ix0cI8IcVAFwI0_ Xr0_Ar1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxV W0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_GcCE3s1ln4vEbcI7uVAqrcv_JFW8Xr15 M2kK64xIx7IE04vEw4CY0x0E548m6r1fGryUXwAqjxCEc2xF0cIa020Ex4CE44I27wAqx4 xG64xvF2IEw4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_JF0_Jw1lYx0Ex4A2jsIE14v2 6F4UJVW0owACjcxG0xvEwIxGrwCYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI7VAKI4 8JMxCIbVAxMI8E67AF67kF1VAFwI0_Jr0_JrylIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E 3sUvcSsGvfC2KfnxnUUI43ZEXa7IUeG0PDUUUUU== X-CM-SenderInfo: pixex0x2kd0wg6lf3hldfou0/ Subject: [Xen-API] XCP 1.5 BETA 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: 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, I am trying to install xcp-1.5 beta, however i got an error about partition table. I am sure that the disk is correctly installed because i have successfully installed XCP-1.0 on the same machine. Any hint is appreciated. Thanks in advance. The output is: ---------------------------------------- An unrecoverable error has occured. The error was: The new partition table could not be written: sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sda: unrecognized partition table type sfdisk: 1: no such partition Reversion also failed: sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sda: unrecognized partition table type Best Regards, Fu, Binzhang _______________________________________________ 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 Apr 16 13:44:06 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 16 Apr 2012 13:44: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 1SJmDn-0006Te-2F; Mon, 16 Apr 2012 13:43:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJmDk-0006TS-W6 for xen-api@lists.xen.org; Mon, 16 Apr 2012 13:43:57 +0000 Received: from [85.158.143.35:3041] by server-2.bemta-4.messagelabs.com id A1/3C-17550-C122C8F4; Mon, 16 Apr 2012 13:43:56 +0000 X-Env-Sender: fubinzhang@ict.ac.cn X-Msg-Ref: server-14.tower-21.messagelabs.com!1334583833!16342228!1 X-Originating-IP: [159.226.251.23] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6148 invoked from network); 16 Apr 2012 13:43:55 -0000 Received: from smtp23.cstnet.cn (HELO cstnet.cn) (159.226.251.23) by server-14.tower-21.messagelabs.com with SMTP; 16 Apr 2012 13:43:55 -0000 Received: from [10.30.0.243] (unknown [159.226.43.35]) by app3 (Coremail) with SMTP id SQCowJBLaAcXIoxPQEIPAA--.49451S2; Mon, 16 Apr 2012 21:43:51 +0800 (CST) Message-ID: <4F8C2217.6050407@ict.ac.cn> Date: Mon, 16 Apr 2012 21:43:51 +0800 From: Fu Bin-zhang User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; zh-CN; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: xen-api@lists.xen.org X-CM-TRANSID: SQCowJBLaAcXIoxPQEIPAA--.49451S2 X-Coremail-Antispam: 1UD129KBjvdXoWrtFWDJF1xZFykZFWDJF1kXwb_yoWxuwb_GF yqv3WkXryjyF4Igr17Cr4YqrWrKa1DWr1jy34rtFsrK347trsrXF9IgrsYv34Ivw4UGrn8 AFyrXa1akry2kjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUjXAYjxAI6xkYrwAYjxAI6xCIbckI1I0E57IF64kEYxAxM7k042IE 4asKkaVY67AtM7k0a2IF6F4UM7kC6x804xWl14x267AKxVWUJVW8JwAFc2x0x2IEx4CE42 xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2z4x0Y4vE2Ix0cI8IcVAFwI0_ Xr0_Ar1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_Cr1l84ACjcxK6I8E87Iv67AKxV W0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_GcCE3s1ln4vEbcI7uVAqrcv_JFW8Xr15 M2kK64xIx7IE04vEw4CY0x0E548m6r1fGryUXwAqjxCEc2xF0cIa020Ex4CE44I27wAqx4 xG64xvF2IEw4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_JF0_Jw1lYx0Ex4A2jsIE14v2 6F4UJVW0owACjcxG0xvEwIxGrwCYjI0SjxkI62AI1cAE67vIY487MxAIw28IcxkI7VAKI4 8JMxCIbVAxMI8E67AF67kF1VAFwI0_Jr0_JrylIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E 3sUvcSsGvfC2KfnxnUUI43ZEXa7IUeG0PDUUUUU== X-CM-SenderInfo: pixex0x2kd0wg6lf3hldfou0/ Subject: [Xen-API] XCP 1.5 BETA 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: 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, I am trying to install xcp-1.5 beta, however i got an error about partition table. I am sure that the disk is correctly installed because i have successfully installed XCP-1.0 on the same machine. Any hint is appreciated. Thanks in advance. The output is: ---------------------------------------- An unrecoverable error has occured. The error was: The new partition table could not be written: sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sda: unrecognized partition table type sfdisk: 1: no such partition Reversion also failed: sfdisk: ERROR: sector 0 does not have an msdos signature /dev/sda: unrecognized partition table type Best Regards, Fu, Binzhang _______________________________________________ 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 Apr 16 13:56:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 16 Apr 2012 13:56: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 1SJmQ8-0006zW-5i; Mon, 16 Apr 2012 13:56:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJmQ6-0006zK-GP for xen-api@lists.xen.org; Mon, 16 Apr 2012 13:56:42 +0000 Received: from [193.109.254.147:60279] by server-5.bemta-14.messagelabs.com id 3E/D6-30733-9152C8F4; Mon, 16 Apr 2012 13:56:41 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1334584600!4833307!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6192 invoked from network); 16 Apr 2012 13:56:41 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Apr 2012 13:56:41 -0000 Received: by lahe6 with SMTP id e6so4638484lah.32 for ; Mon, 16 Apr 2012 06:56:40 -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=zVBFqIKJfT/uFeElqlAOLT41FAkTQenVKw/XWnMkFho=; b=YJ7Wg4vYe/NGd4LuWCO+AdwxXKPUbzPd30Tzj3rkZVFRl6lnrpxi2VqwQlF7WIFj6o iMQUd3rfycpi109St8gqd/e7bcbE3VujXpWCqDeZCDx21hOjFwCtpvM4pEmj4MvUafgx DfyMJbgpITHWfpKwMh6zAU7erzpiqPA4+YG40RGSDMby5XuoC0+J5tOf440dOIDF8xGu gHCNuY4NtlwOENIAcoEwUFBEGZjMq6oaWdfzFa541zgdRZaLKSfKI5jeJOC7LE54M7VH ppHAPZFm0HyqnUx8/ort3m00qQOUbakeJISYPld9yX19iZwQAXUTYTKG7Uc2Tuu1zLeC +0Qg== Received: by 10.152.146.67 with SMTP id ta3mr10375202lab.25.1334584600493; Mon, 16 Apr 2012 06:56:40 -0700 (PDT) Received: from [192.168.40.44] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id pb13sm19476586lab.16.2012.04.16.06.56.31 (version=SSLv3 cipher=OTHER); Mon, 16 Apr 2012 06:56:32 -0700 (PDT) Message-ID: <4F8C250E.1040709@gmail.com> Date: Mon, 16 Apr 2012 17:56:30 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F8C2217.6050407@ict.ac.cn> In-Reply-To: <4F8C2217.6050407@ict.ac.cn> Subject: Re: [Xen-API] XCP 1.5 BETA 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 16.04.2012 17:43, Fu Bin-zhang wrote: > I am trying to install xcp-1.5 beta, however i got an error > about partition table. I am sure that the disk is correctly installed > because i have successfully installed XCP-1.0 on the same machine. > Any hint is appreciated. Thanks in advance. > > The output is: > ---------------------------------------- > An unrecoverable error has occured. The error was: > > The new partition table could not be written: > sfdisk: ERROR: sector 0 does not have an msdos signature > /dev/sda: unrecognized partition table type > > sfdisk: 1: no such partition > > Reversion also failed: > sfdisk: ERROR: sector 0 does not have an msdos signature > /dev/sda: unrecognized partition table type > Seems like XCP (sfdisk) does not like hard drives without MBR. Try to boot to any Linux system and run fdisk /dev/sda, say 'w' (write) and 'q' (quit). Sector0 contains two pieces of information: MBR (initial bootloader) and patition table. You need (seem like this) to have correct MBR before installing XCP. _______________________________________________ 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 Apr 16 13:56:49 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 16 Apr 2012 13:56: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 1SJmQ8-0006zW-5i; Mon, 16 Apr 2012 13:56:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SJmQ6-0006zK-GP for xen-api@lists.xen.org; Mon, 16 Apr 2012 13:56:42 +0000 Received: from [193.109.254.147:60279] by server-5.bemta-14.messagelabs.com id 3E/D6-30733-9152C8F4; Mon, 16 Apr 2012 13:56:41 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1334584600!4833307!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6192 invoked from network); 16 Apr 2012 13:56:41 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 16 Apr 2012 13:56:41 -0000 Received: by lahe6 with SMTP id e6so4638484lah.32 for ; Mon, 16 Apr 2012 06:56:40 -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=zVBFqIKJfT/uFeElqlAOLT41FAkTQenVKw/XWnMkFho=; b=YJ7Wg4vYe/NGd4LuWCO+AdwxXKPUbzPd30Tzj3rkZVFRl6lnrpxi2VqwQlF7WIFj6o iMQUd3rfycpi109St8gqd/e7bcbE3VujXpWCqDeZCDx21hOjFwCtpvM4pEmj4MvUafgx DfyMJbgpITHWfpKwMh6zAU7erzpiqPA4+YG40RGSDMby5XuoC0+J5tOf440dOIDF8xGu gHCNuY4NtlwOENIAcoEwUFBEGZjMq6oaWdfzFa541zgdRZaLKSfKI5jeJOC7LE54M7VH ppHAPZFm0HyqnUx8/ort3m00qQOUbakeJISYPld9yX19iZwQAXUTYTKG7Uc2Tuu1zLeC +0Qg== Received: by 10.152.146.67 with SMTP id ta3mr10375202lab.25.1334584600493; Mon, 16 Apr 2012 06:56:40 -0700 (PDT) Received: from [192.168.40.44] (officecvt.selectel.ru. [188.93.16.50]) by mx.google.com with ESMTPS id pb13sm19476586lab.16.2012.04.16.06.56.31 (version=SSLv3 cipher=OTHER); Mon, 16 Apr 2012 06:56:32 -0700 (PDT) Message-ID: <4F8C250E.1040709@gmail.com> Date: Mon, 16 Apr 2012 17:56:30 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F8C2217.6050407@ict.ac.cn> In-Reply-To: <4F8C2217.6050407@ict.ac.cn> Subject: Re: [Xen-API] XCP 1.5 BETA 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-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 16.04.2012 17:43, Fu Bin-zhang wrote: > I am trying to install xcp-1.5 beta, however i got an error > about partition table. I am sure that the disk is correctly installed > because i have successfully installed XCP-1.0 on the same machine. > Any hint is appreciated. Thanks in advance. > > The output is: > ---------------------------------------- > An unrecoverable error has occured. The error was: > > The new partition table could not be written: > sfdisk: ERROR: sector 0 does not have an msdos signature > /dev/sda: unrecognized partition table type > > sfdisk: 1: no such partition > > Reversion also failed: > sfdisk: ERROR: sector 0 does not have an msdos signature > /dev/sda: unrecognized partition table type > Seems like XCP (sfdisk) does not like hard drives without MBR. Try to boot to any Linux system and run fdisk /dev/sda, say 'w' (write) and 'q' (quit). Sector0 contains two pieces of information: MBR (initial bootloader) and patition table. You need (seem like this) to have correct MBR before installing XCP. _______________________________________________ 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 Apr 19 09:03:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 19 Apr 2012 09:03: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 1SKnGW-0007vR-Vd; Thu, 19 Apr 2012 09:03:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKnGV-0007vM-CJ for xen-api@lists.xen.org; Thu, 19 Apr 2012 09:02:59 +0000 Received: from [85.158.138.51:24220] by server-12.bemta-3.messagelabs.com id 7B/63-29760-2C4DF8F4; Thu, 19 Apr 2012 09:02:58 +0000 X-Env-Sender: Abhinandan.Prateek@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1334826173!22830499!1 X-Originating-IP: [203.166.19.134] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjE2Ni4xOS4xMzQgPT4gNDQzOTY=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14232 invoked from network); 19 Apr 2012 09:02:57 -0000 Received: from smtp.citrix.com.au (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2012 09:02:57 -0000 X-IronPort-AV: E=Sophos;i="4.75,445,1330905600"; d="scan'208";a="11156443" Received: from banpmailmx02.citrite.net ([10.103.128.74]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 19 Apr 2012 09:02:51 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.71]) by BANPMAILMX02.citrite.net ([10.103.128.74]) with mapi; Thu, 19 Apr 2012 14:32:51 +0530 From: Abhinandan Prateek To: "xen-api@lists.xen.org" , Bob Ball , Andrew Halley Date: Thu, 19 Apr 2012 14:32:49 +0530 Thread-Topic: XCP 1.5 beta api Thread-Index: Ac0eAUIgbCXpb7jtSASB4XbFaGmYrw== Message-ID: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCDA9@BANPMAILBOX01.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 Cc: Ram Chinta , Kevin Kluge Subject: [Xen-API] XCP 1.5 beta api 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 We are testing support for XCP 1.5 beta in the cloudstack software. While testing we saw that the method get_mtime is omitted from /opt/xensource/sm/util.py. This method is present in XCP 1.1. The sr dir timestamp is used by cloudstack to check if the sr has changed. Is there a reason to do that ? Will it be possible to add it back. Thanks and Regards, Abhinandan Prateek _______________________________________________ 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 Apr 19 09:03:09 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 19 Apr 2012 09:03: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 1SKnGW-0007vR-Vd; Thu, 19 Apr 2012 09:03:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKnGV-0007vM-CJ for xen-api@lists.xen.org; Thu, 19 Apr 2012 09:02:59 +0000 Received: from [85.158.138.51:24220] by server-12.bemta-3.messagelabs.com id 7B/63-29760-2C4DF8F4; Thu, 19 Apr 2012 09:02:58 +0000 X-Env-Sender: Abhinandan.Prateek@citrix.com X-Msg-Ref: server-2.tower-174.messagelabs.com!1334826173!22830499!1 X-Originating-IP: [203.166.19.134] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjE2Ni4xOS4xMzQgPT4gNDQzOTY=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14232 invoked from network); 19 Apr 2012 09:02:57 -0000 Received: from smtp.citrix.com.au (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by server-2.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2012 09:02:57 -0000 X-IronPort-AV: E=Sophos;i="4.75,445,1330905600"; d="scan'208";a="11156443" Received: from banpmailmx02.citrite.net ([10.103.128.74]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 19 Apr 2012 09:02:51 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.71]) by BANPMAILMX02.citrite.net ([10.103.128.74]) with mapi; Thu, 19 Apr 2012 14:32:51 +0530 From: Abhinandan Prateek To: "xen-api@lists.xen.org" , Bob Ball , Andrew Halley Date: Thu, 19 Apr 2012 14:32:49 +0530 Thread-Topic: XCP 1.5 beta api Thread-Index: Ac0eAUIgbCXpb7jtSASB4XbFaGmYrw== Message-ID: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCDA9@BANPMAILBOX01.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 Cc: Ram Chinta , Kevin Kluge Subject: [Xen-API] XCP 1.5 beta api 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 We are testing support for XCP 1.5 beta in the cloudstack software. While testing we saw that the method get_mtime is omitted from /opt/xensource/sm/util.py. This method is present in XCP 1.1. The sr dir timestamp is used by cloudstack to check if the sr has changed. Is there a reason to do that ? Will it be possible to add it back. Thanks and Regards, Abhinandan Prateek _______________________________________________ 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 Apr 19 13:40:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 19 Apr 2012 13:40:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKrbH-0005F8-T5; Thu, 19 Apr 2012 13:40:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKrbG-0005F3-43 for xen-api@lists.xen.org; Thu, 19 Apr 2012 13:40:42 +0000 Received: from [85.158.143.99:51167] by server-1.bemta-4.messagelabs.com id F6/33-20925-9D5109F4; Thu, 19 Apr 2012 13:40:41 +0000 X-Env-Sender: Jonathan.Ludlam@eu.citrix.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1334842831!23462530!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NTEwNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28197 invoked from network); 19 Apr 2012 13:40:40 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2012 13:40:40 -0000 X-IronPort-AV: E=Sophos;i="4.75,447,1330905600"; d="scan'208";a="12028363" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Apr 2012 13:40:31 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 19 Apr 2012 14:40:31 +0100 From: Jonathan Ludlam To: Abhinandan Prateek Date: Thu, 19 Apr 2012 14:40:30 +0100 Thread-Topic: [Xen-API] XCP 1.5 beta api Thread-Index: Ac0eMfzo+71OCs48R2+hcycqlWRTHg== Message-ID: References: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCDA9@BANPMAILBOX01.citrite.net> In-Reply-To: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCDA9@BANPMAILBOX01.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 Cc: Andrew Halley , Bob Ball , Kevin Kluge , Ram Chinta , "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.5 beta api 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 Hiya, We don't use it any more (clearly!) but it was an extremely small function - you could probably just implement it elsewhere: def get_mtime(path): st = ioretry_stat(lambda: os.stat(path)) return st[stat.ST_MTIME] Also, this isn't specific to XCP - the same code is in XS 6.0. Does that not affect you too? Jon On 19 Apr 2012, at 10:02, Abhinandan Prateek wrote: > > We are testing support for XCP 1.5 beta in the cloudstack software. While testing we saw that the method get_mtime is omitted from /opt/xensource/sm/util.py. This method is present in XCP 1.1. The sr dir timestamp is used by cloudstack to check if the sr has changed. > > Is there a reason to do that ? Will it be possible to add it back. > > Thanks and Regards, > Abhinandan Prateek > > _______________________________________________ > 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 Apr 19 13:40:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 19 Apr 2012 13:40:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKrbH-0005F8-T5; Thu, 19 Apr 2012 13:40:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKrbG-0005F3-43 for xen-api@lists.xen.org; Thu, 19 Apr 2012 13:40:42 +0000 Received: from [85.158.143.99:51167] by server-1.bemta-4.messagelabs.com id F6/33-20925-9D5109F4; Thu, 19 Apr 2012 13:40:41 +0000 X-Env-Sender: Jonathan.Ludlam@eu.citrix.com X-Msg-Ref: server-13.tower-216.messagelabs.com!1334842831!23462530!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NTEwNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28197 invoked from network); 19 Apr 2012 13:40:40 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-13.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2012 13:40:40 -0000 X-IronPort-AV: E=Sophos;i="4.75,447,1330905600"; d="scan'208";a="12028363" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Apr 2012 13:40:31 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 19 Apr 2012 14:40:31 +0100 From: Jonathan Ludlam To: Abhinandan Prateek Date: Thu, 19 Apr 2012 14:40:30 +0100 Thread-Topic: [Xen-API] XCP 1.5 beta api Thread-Index: Ac0eMfzo+71OCs48R2+hcycqlWRTHg== Message-ID: References: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCDA9@BANPMAILBOX01.citrite.net> In-Reply-To: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCDA9@BANPMAILBOX01.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 Cc: Andrew Halley , Bob Ball , Kevin Kluge , Ram Chinta , "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.5 beta api 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 Hiya, We don't use it any more (clearly!) but it was an extremely small function - you could probably just implement it elsewhere: def get_mtime(path): st = ioretry_stat(lambda: os.stat(path)) return st[stat.ST_MTIME] Also, this isn't specific to XCP - the same code is in XS 6.0. Does that not affect you too? Jon On 19 Apr 2012, at 10:02, Abhinandan Prateek wrote: > > We are testing support for XCP 1.5 beta in the cloudstack software. While testing we saw that the method get_mtime is omitted from /opt/xensource/sm/util.py. This method is present in XCP 1.1. The sr dir timestamp is used by cloudstack to check if the sr has changed. > > Is there a reason to do that ? Will it be possible to add it back. > > Thanks and Regards, > Abhinandan Prateek > > _______________________________________________ > 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 Apr 19 14:02:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 19 Apr 2012 14:02: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 1SKrwL-0005hB-DV; Thu, 19 Apr 2012 14:02:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKrwK-0005h6-9J for xen-api@lists.xen.org; Thu, 19 Apr 2012 14:02:28 +0000 Received: from [85.158.139.83:27435] by server-10.bemta-5.messagelabs.com id B0/9B-08260-3FA109F4; Thu, 19 Apr 2012 14:02:27 +0000 X-Env-Sender: Abhinandan.Prateek@citrix.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1334844142!17224312!1 X-Originating-IP: [203.166.19.134] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjE2Ni4xOS4xMzQgPT4gNDQzOTY=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31296 invoked from network); 19 Apr 2012 14:02:26 -0000 Received: from smtp.citrix.com.au (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2012 14:02:26 -0000 X-IronPort-AV: E=Sophos;i="4.75,447,1330905600"; d="scan'208";a="11158588" Received: from banpmailmx02.citrite.net ([10.103.128.74]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 19 Apr 2012 14:02:21 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.71]) by BANPMAILMX02.citrite.net ([10.103.128.74]) with mapi; Thu, 19 Apr 2012 19:32:20 +0530 From: Abhinandan Prateek To: Jonathan Ludlam Date: Thu, 19 Apr 2012 19:32:17 +0530 Thread-Topic: [Xen-API] XCP 1.5 beta api Thread-Index: Ac0eMfzo+71OCs48R2+hcycqlWRTHgAAozgw Message-ID: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCE4B@BANPMAILBOX01.citrite.net> References: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCDA9@BANPMAILBOX01.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: Ram Chinta , Chiradeep Vittal , Anthony Xu , Alex Huang , Andrew Halley , Bob Ball , Kevin Kluge , "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.5 beta api 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 Jon, Thanks for quick update. If it has been removed as part of cleanup we will make appropriate changes in our codebase for XCP. As I can see things are happening bit differently for XS 6.0 in cloudstack and there we do not use that particular method. -Abhi -----Original Message----- From: Jonathan Ludlam Sent: Thursday, April 19, 2012 7:11 PM To: Abhinandan Prateek Cc: xen-api@lists.xen.org; Bob Ball; Andrew Halley; Ram Chinta; Kevin Kluge Subject: Re: [Xen-API] XCP 1.5 beta api Hiya, We don't use it any more (clearly!) but it was an extremely small function - you could probably just implement it elsewhere: def get_mtime(path): st = ioretry_stat(lambda: os.stat(path)) return st[stat.ST_MTIME] Also, this isn't specific to XCP - the same code is in XS 6.0. Does that not affect you too? Jon On 19 Apr 2012, at 10:02, Abhinandan Prateek wrote: > > We are testing support for XCP 1.5 beta in the cloudstack software. While testing we saw that the method get_mtime is omitted from /opt/xensource/sm/util.py. This method is present in XCP 1.1. The sr dir timestamp is used by cloudstack to check if the sr has changed. > > Is there a reason to do that ? Will it be possible to add it back. > > Thanks and Regards, > Abhinandan Prateek > > _______________________________________________ > 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 Apr 19 14:02:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 19 Apr 2012 14:02: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 1SKrwL-0005hB-DV; Thu, 19 Apr 2012 14:02:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKrwK-0005h6-9J for xen-api@lists.xen.org; Thu, 19 Apr 2012 14:02:28 +0000 Received: from [85.158.139.83:27435] by server-10.bemta-5.messagelabs.com id B0/9B-08260-3FA109F4; Thu, 19 Apr 2012 14:02:27 +0000 X-Env-Sender: Abhinandan.Prateek@citrix.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1334844142!17224312!1 X-Originating-IP: [203.166.19.134] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjAzLjE2Ni4xOS4xMzQgPT4gNDQzOTY=\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31296 invoked from network); 19 Apr 2012 14:02:26 -0000 Received: from smtp.citrix.com.au (HELO SMTP.CITRIX.COM.AU) (203.166.19.134) by server-16.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2012 14:02:26 -0000 X-IronPort-AV: E=Sophos;i="4.75,447,1330905600"; d="scan'208";a="11158588" Received: from banpmailmx02.citrite.net ([10.103.128.74]) by SYDPIPO01.CITRIX.COM.AU with ESMTP/TLS/RC4-MD5; 19 Apr 2012 14:02:21 +0000 Received: from BANPMAILBOX01.citrite.net ([10.103.128.71]) by BANPMAILMX02.citrite.net ([10.103.128.74]) with mapi; Thu, 19 Apr 2012 19:32:20 +0530 From: Abhinandan Prateek To: Jonathan Ludlam Date: Thu, 19 Apr 2012 19:32:17 +0530 Thread-Topic: [Xen-API] XCP 1.5 beta api Thread-Index: Ac0eMfzo+71OCs48R2+hcycqlWRTHgAAozgw Message-ID: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCE4B@BANPMAILBOX01.citrite.net> References: <64FB1554ABC9B44FAA773FBD6CB889C2F9155BCDA9@BANPMAILBOX01.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: Ram Chinta , Chiradeep Vittal , Anthony Xu , Alex Huang , Andrew Halley , Bob Ball , Kevin Kluge , "xen-api@lists.xen.org" Subject: Re: [Xen-API] XCP 1.5 beta api 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 Jon, Thanks for quick update. If it has been removed as part of cleanup we will make appropriate changes in our codebase for XCP. As I can see things are happening bit differently for XS 6.0 in cloudstack and there we do not use that particular method. -Abhi -----Original Message----- From: Jonathan Ludlam Sent: Thursday, April 19, 2012 7:11 PM To: Abhinandan Prateek Cc: xen-api@lists.xen.org; Bob Ball; Andrew Halley; Ram Chinta; Kevin Kluge Subject: Re: [Xen-API] XCP 1.5 beta api Hiya, We don't use it any more (clearly!) but it was an extremely small function - you could probably just implement it elsewhere: def get_mtime(path): st = ioretry_stat(lambda: os.stat(path)) return st[stat.ST_MTIME] Also, this isn't specific to XCP - the same code is in XS 6.0. Does that not affect you too? Jon On 19 Apr 2012, at 10:02, Abhinandan Prateek wrote: > > We are testing support for XCP 1.5 beta in the cloudstack software. While testing we saw that the method get_mtime is omitted from /opt/xensource/sm/util.py. This method is present in XCP 1.1. The sr dir timestamp is used by cloudstack to check if the sr has changed. > > Is there a reason to do that ? Will it be possible to add it back. > > Thanks and Regards, > Abhinandan Prateek > > _______________________________________________ > 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 Apr 20 09:40:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 20 Apr 2012 09:40: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 1SLAKb-0006gQ-A1; Fri, 20 Apr 2012 09:40:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SLAKZ-0006g0-2G for xen-api@lists.xen.org; Fri, 20 Apr 2012 09:40:43 +0000 Received: from [85.158.139.83:11155] by server-10.bemta-5.messagelabs.com id A1/50-08260-A1F219F4; Fri, 20 Apr 2012 09:40:42 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1334914841!24734334!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 20807 invoked from network); 20 Apr 2012 09:40:41 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Apr 2012 09:40:41 -0000 Received: by bkcji1 with SMTP id ji1so1261570bkc.32 for ; Fri, 20 Apr 2012 02:40:41 -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=/cScVXuptoXHbnQzOKjCbFUCs3h9gNA7mUmf/MdYUS8=; b=zWFm6ZJ/foPh1GXnXZ4dxnLwFKUEHXK5ArNGxicuqAMnU5E6gzUoStk14RSq8+1264 Os52MGeHgssFm/h1xIsmp5BogkP3kBjJXn8WzgvPysNc37ceeWR26apozN3Pw7WRAZiB i4qkCvtJe9BfdFCipIf+9hLhoey2xUu/yJwR/Gquh1A8yIxdw3R3KxffoVFW8JhWm2Yl 2mWRiHUFv7yFModMgFblyl5Zw2qeECaGRXjPBioeFR20f6Wk+V9axup3D1lpyrf/RfwK jR4O4/0MZVRnXKylQFrXCxOF2xvxysHYey7wf102F8dpQoY2/Mno7FRLu0CSIHZZgPhC BqZQ== Received: by 10.204.154.209 with SMTP id p17mr1739196bkw.6.1334914840956; Fri, 20 Apr 2012 02:40:40 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id im9sm4885668bkc.5.2012.04.20.02.40.38 (version=SSLv3 cipher=OTHER); Fri, 20 Apr 2012 02:40:39 -0700 (PDT) Message-ID: <4F912F15.2030202@xen.org> Date: Fri, 20 Apr 2012 10:40:37 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-arm@lists.xen.org, xen-users@lists.xen.org, xen-api@lists.xen.org Subject: [Xen-API] Xen Documentation Day : April 23rd 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 Hi everybody, we have another Xen Documentation Day come up next Monday, April 23. More information - http://wiki.xen.org/wiki/Xen_Document_Days - http://wiki.xen.org/wiki/Xen_Document_Days/TODO For a list of items that need work, check out the community maintained TODO and wishlist. Of course, you can work on anything you like: the list just provides suggestions. How do I participate? - 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! See you on IRC! Lars _______________________________________________ xen-api mailing list xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Apr 20 09:40:53 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 20 Apr 2012 09:40: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 1SLAKb-0006gQ-A1; Fri, 20 Apr 2012 09:40:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SLAKZ-0006g0-2G for xen-api@lists.xen.org; Fri, 20 Apr 2012 09:40:43 +0000 Received: from [85.158.139.83:11155] by server-10.bemta-5.messagelabs.com id A1/50-08260-A1F219F4; Fri, 20 Apr 2012 09:40:42 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-5.tower-182.messagelabs.com!1334914841!24734334!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 20807 invoked from network); 20 Apr 2012 09:40:41 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-5.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 20 Apr 2012 09:40:41 -0000 Received: by bkcji1 with SMTP id ji1so1261570bkc.32 for ; Fri, 20 Apr 2012 02:40:41 -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=/cScVXuptoXHbnQzOKjCbFUCs3h9gNA7mUmf/MdYUS8=; b=zWFm6ZJ/foPh1GXnXZ4dxnLwFKUEHXK5ArNGxicuqAMnU5E6gzUoStk14RSq8+1264 Os52MGeHgssFm/h1xIsmp5BogkP3kBjJXn8WzgvPysNc37ceeWR26apozN3Pw7WRAZiB i4qkCvtJe9BfdFCipIf+9hLhoey2xUu/yJwR/Gquh1A8yIxdw3R3KxffoVFW8JhWm2Yl 2mWRiHUFv7yFModMgFblyl5Zw2qeECaGRXjPBioeFR20f6Wk+V9axup3D1lpyrf/RfwK jR4O4/0MZVRnXKylQFrXCxOF2xvxysHYey7wf102F8dpQoY2/Mno7FRLu0CSIHZZgPhC BqZQ== Received: by 10.204.154.209 with SMTP id p17mr1739196bkw.6.1334914840956; Fri, 20 Apr 2012 02:40:40 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id im9sm4885668bkc.5.2012.04.20.02.40.38 (version=SSLv3 cipher=OTHER); Fri, 20 Apr 2012 02:40:39 -0700 (PDT) Message-ID: <4F912F15.2030202@xen.org> Date: Fri, 20 Apr 2012 10:40:37 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-arm@lists.xen.org, xen-users@lists.xen.org, xen-api@lists.xen.org Subject: [Xen-API] Xen Documentation Day : April 23rd 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 Hi everybody, we have another Xen Documentation Day come up next Monday, April 23. More information - http://wiki.xen.org/wiki/Xen_Document_Days - http://wiki.xen.org/wiki/Xen_Document_Days/TODO For a list of items that need work, check out the community maintained TODO and wishlist. Of course, you can work on anything you like: the list just provides suggestions. How do I participate? - 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! See you on IRC! Lars _______________________________________________ xen-api mailing list xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Fri Apr 20 17:16:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 20 Apr 2012 17:16: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 1SLHRd-0008D5-Sm; Fri, 20 Apr 2012 17:16:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SLHRc-0008Cn-Br for xen-api@lists.xen.org; Fri, 20 Apr 2012 17:16:28 +0000 Received: from [193.109.254.147:63154] by server-4.bemta-14.messagelabs.com id CF/D6-11570-BE9919F4; Fri, 20 Apr 2012 17:16:27 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1334942186!5579012!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 28691 invoked from network); 20 Apr 2012 17:16:27 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Apr 2012 17:16:27 -0000 Received: by eeit10 with SMTP id t10so2719079eei.32 for ; Fri, 20 Apr 2012 10:16:26 -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=YoOTErKoULE6DyteZ528o3Ip/skRLLdixA0OBftrtms=; b=dssaMbANR+e1HjmFv5UIxt2zuWHVgD9csC3Bhin6B//mwgkFjEUTarszRtH/I/RMdK dXceNqKh41qRcDIk1/Tmdqosh2d+MJYb4SWm7ZgiH7KzgZnyChcYRV7ulR/4VSNmiG6X ia30Fe58v+pGwiTZDHcgj3l6zfCX4EHscOisLPS3AGe2vWiABqeuwY9oEGmoLfrct8et sKLLBY5T8SaZ73pWGEbHHvw8AtArT+XFb0d0tdmYuT5ujVXbCicF7rAK08V67KVRHN3U ybOzgbYzdOdbjWgUUJwH2y8CNCyJPHQOPn4IhIA1a09mt27HYMJiTo5hJ2ORcwh3wr5G 1aZg== Received: by 10.14.96.203 with SMTP id r51mr1233813eef.24.1334942186515; Fri, 20 Apr 2012 10:16:26 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id e56sm29068809eea.11.2012.04.20.10.16.24 (version=SSLv3 cipher=OTHER); Fri, 20 Apr 2012 10:16:25 -0700 (PDT) Message-ID: <4F9199E5.5080409@xen.org> Date: Fri, 20 Apr 2012 18:16:21 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-arm@lists.xen.org, xen-api@lists.xen.org Subject: [Xen-API] IMPORTANT: Changes to XenSummit Format : Please vote! 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 Hi everybody, I have been talking to a number of the key contributors to the project regarding XenSummit and got feedback on the format of XenSummit. Please read, if you are active in the community and DO VOTE! Cheers Lars Change of date in CFP! ====================== First I wanted to annouce that we are extending the CFP from May 1st to 15th of June. Key community members felt that May 1 is too early. In particular because we have closed the CFP 5-6 weeks before the event in the past. Due to contractual issues June 15th is the last day we can do though. Proposal! PLEASE READ! ====================== A number of vendors felt we should change the format of XenSummit to be more like the Linux Kernel Summit. I.e. a) An invite only event for the top 20-30 developers of the project b) The main focus would be around finding technical solutions and making decisions I can see the merit of this, but it is too late to do this for all of XenSummit due to event contracts that havce been signed. However we have a number of options, moving towards this: 1) Start half a day early and have an invite only XenDev Event event on Sunday afteroon 2) Cut XenSummit short by 1/2 day and append the XenDev event. This may incur some financial penalties for Xen.org and the overall ticket cost may have to be higher than in the past. 3) Do the invite only meeting in parallel with XenSummit. I have an additional large room on TUE the 27th, which we could use for this and I also have two break-out rooms and can allocate one of them to the XenDev event (these were intended for people sitting together and hacking on stuff and/or BoFs). There are several options: hold the XenDev event on 3.1) 26th afternoon 3.2) 27th morning 3.3) 27th afternoon In my view option 1) and 3.1) have the advantage that we can report back to XenSummit, that nobody will miss key talks and that people can sit together in the break-out rooms. Vote ==== Please vote by providing. Vote closes by the 27th. Vote by replying to this mail with ... -1: none of the above (i.e. I dont want a XenDev event) +1 for a DevMeeting on sunday (aka for proposal 1) +1 for cutting XenSummit short (aka for proposal 2) +1 for parallel 26th PM (aka proposal 3.1) +1 for parallel 27th AM (aka proposal 3.2) +1 for parallel 27th PM (aka proposal 3.3) _______________________________________________ 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 Apr 20 17:16:37 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 20 Apr 2012 17:16: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 1SLHRd-0008D5-Sm; Fri, 20 Apr 2012 17:16:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SLHRc-0008Cn-Br for xen-api@lists.xen.org; Fri, 20 Apr 2012 17:16:28 +0000 Received: from [193.109.254.147:63154] by server-4.bemta-14.messagelabs.com id CF/D6-11570-BE9919F4; Fri, 20 Apr 2012 17:16:27 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1334942186!5579012!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 28691 invoked from network); 20 Apr 2012 17:16:27 -0000 Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com) (74.125.83.45) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Apr 2012 17:16:27 -0000 Received: by eeit10 with SMTP id t10so2719079eei.32 for ; Fri, 20 Apr 2012 10:16:26 -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=YoOTErKoULE6DyteZ528o3Ip/skRLLdixA0OBftrtms=; b=dssaMbANR+e1HjmFv5UIxt2zuWHVgD9csC3Bhin6B//mwgkFjEUTarszRtH/I/RMdK dXceNqKh41qRcDIk1/Tmdqosh2d+MJYb4SWm7ZgiH7KzgZnyChcYRV7ulR/4VSNmiG6X ia30Fe58v+pGwiTZDHcgj3l6zfCX4EHscOisLPS3AGe2vWiABqeuwY9oEGmoLfrct8et sKLLBY5T8SaZ73pWGEbHHvw8AtArT+XFb0d0tdmYuT5ujVXbCicF7rAK08V67KVRHN3U ybOzgbYzdOdbjWgUUJwH2y8CNCyJPHQOPn4IhIA1a09mt27HYMJiTo5hJ2ORcwh3wr5G 1aZg== Received: by 10.14.96.203 with SMTP id r51mr1233813eef.24.1334942186515; Fri, 20 Apr 2012 10:16:26 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id e56sm29068809eea.11.2012.04.20.10.16.24 (version=SSLv3 cipher=OTHER); Fri, 20 Apr 2012 10:16:25 -0700 (PDT) Message-ID: <4F9199E5.5080409@xen.org> Date: Fri, 20 Apr 2012 18:16:21 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-arm@lists.xen.org, xen-api@lists.xen.org Subject: [Xen-API] IMPORTANT: Changes to XenSummit Format : Please vote! 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 Hi everybody, I have been talking to a number of the key contributors to the project regarding XenSummit and got feedback on the format of XenSummit. Please read, if you are active in the community and DO VOTE! Cheers Lars Change of date in CFP! ====================== First I wanted to annouce that we are extending the CFP from May 1st to 15th of June. Key community members felt that May 1 is too early. In particular because we have closed the CFP 5-6 weeks before the event in the past. Due to contractual issues June 15th is the last day we can do though. Proposal! PLEASE READ! ====================== A number of vendors felt we should change the format of XenSummit to be more like the Linux Kernel Summit. I.e. a) An invite only event for the top 20-30 developers of the project b) The main focus would be around finding technical solutions and making decisions I can see the merit of this, but it is too late to do this for all of XenSummit due to event contracts that havce been signed. However we have a number of options, moving towards this: 1) Start half a day early and have an invite only XenDev Event event on Sunday afteroon 2) Cut XenSummit short by 1/2 day and append the XenDev event. This may incur some financial penalties for Xen.org and the overall ticket cost may have to be higher than in the past. 3) Do the invite only meeting in parallel with XenSummit. I have an additional large room on TUE the 27th, which we could use for this and I also have two break-out rooms and can allocate one of them to the XenDev event (these were intended for people sitting together and hacking on stuff and/or BoFs). There are several options: hold the XenDev event on 3.1) 26th afternoon 3.2) 27th morning 3.3) 27th afternoon In my view option 1) and 3.1) have the advantage that we can report back to XenSummit, that nobody will miss key talks and that people can sit together in the break-out rooms. Vote ==== Please vote by providing. Vote closes by the 27th. Vote by replying to this mail with ... -1: none of the above (i.e. I dont want a XenDev event) +1 for a DevMeeting on sunday (aka for proposal 1) +1 for cutting XenSummit short (aka for proposal 2) +1 for parallel 26th PM (aka proposal 3.1) +1 for parallel 27th AM (aka proposal 3.2) +1 for parallel 27th PM (aka proposal 3.3) _______________________________________________ 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 Apr 21 21:51:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 21 Apr 2012 21:51: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 1SLiCw-0001lX-EQ; Sat, 21 Apr 2012 21:51:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKrFp-0003Zc-9m for xen-api@lists.xen.org; Thu, 19 Apr 2012 13:18:33 +0000 Received: from [85.158.138.51:19206] by server-12.bemta-3.messagelabs.com id 67/AD-29760-8A0109F4; Thu, 19 Apr 2012 13:18:32 +0000 X-Env-Sender: andrew.halley@citrix.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1334841511!22834247!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NTEwNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25426 invoked from network); 19 Apr 2012 13:18:31 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2012 13:18:31 -0000 X-IronPort-AV: E=Sophos;i="4.75,447,1330905600"; d="scan'208,217";a="12027573" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Apr 2012 13:18:30 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 19 Apr 2012 14:18:30 +0100 From: Andrew Halley To: Abhinandan Prateek , "xen-api@lists.xen.org" , Bob Ball , Andrew Halley Date: Thu, 19 Apr 2012 14:18:29 +0100 Thread-Topic: XCP 1.5 beta api Thread-Index: Ac0eAUIgbCXpb7jtSASB4XbFaGmYrwALadZy Message-ID: <101tr2brgdfgluqwf88y4gda.1334841462919@email.android.com> 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: Sat, 21 Apr 2012 21:51:05 +0000 Cc: Ram Chinta , Kevin Kluge Subject: Re: [Xen-API] XCP 1.5 beta api 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="===============1431025073952577317==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1431025073952577317== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_101tr2brgdfgluqwf88y4gda1334841462919emailandroidcom_" --_000_101tr2brgdfgluqwf88y4gda1334841462919emailandroidcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Checking. Sent from my Mobile device - apologies for typos and brevity -------- Original message -------- Subject: XCP 1.5 beta api From: Abhinandan Prateek To: "xen-api@lists.xen.org" ,Bob Ball ,Andrew Halley CC: Kevin Kluge ,Ram Chinta We are testing support for XCP 1.5 beta in the cloudstack software. While t= esting we saw that the method get_mtime is omitted from /opt/xensource/sm/u= til.py. This method is present in XCP 1.1. The sr dir timestamp is used b= y cloudstack to check if the sr has changed. Is there a reason to do that ? Will it be possible to add it back. Thanks and Regards, Abhinandan Prateek --_000_101tr2brgdfgluqwf88y4gda1334841462919emailandroidcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Checking.


Sent from my Mobil= e device - apologies for typos and brevity


-------- Orig= inal message --------
Subject: XCP 1.5 beta api
From: Abhinandan Pra= teek <Abhinandan.Prateek@citrix.com>
To: "xen-api@lists.xen.= org" <xen-api@lists.xen.org>,Bob Ball <bob.ball@citrix.com>= ;,Andrew Halley <andrew.halley@citrix.com>
CC: Kevin Kluge <Ke= vin.Kluge@citrix.com>,Ram Chinta <ram.chinta@citrix.com>

<= br>

We are testing support for XCP 1.5 beta in the cloudstack software. While t= esting we saw that the method get_mtime is omitted from /opt/xensource/sm/u= til.py.  This method is present in XCP 1.1.  The sr dir timestamp= is used by cloudstack to check if the sr has changed.

Is there a reason to do that ? Will it be possible to add it back.

Thanks and Regards,
Abhinandan Prateek
 --_000_101tr2brgdfgluqwf88y4gda1334841462919emailandroidcom_-- --===============1431025073952577317== 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 --===============1431025073952577317==-- From xen-api-bounces@lists.xen.org Sat Apr 21 21:51:15 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sat, 21 Apr 2012 21:51: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 1SLiCw-0001lX-EQ; Sat, 21 Apr 2012 21:51:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SKrFp-0003Zc-9m for xen-api@lists.xen.org; Thu, 19 Apr 2012 13:18:33 +0000 Received: from [85.158.138.51:19206] by server-12.bemta-3.messagelabs.com id 67/AD-29760-8A0109F4; Thu, 19 Apr 2012 13:18:32 +0000 X-Env-Sender: andrew.halley@citrix.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1334841511!22834247!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NTEwNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25426 invoked from network); 19 Apr 2012 13:18:31 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 19 Apr 2012 13:18:31 -0000 X-IronPort-AV: E=Sophos;i="4.75,447,1330905600"; d="scan'208,217";a="12027573" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 19 Apr 2012 13:18:30 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.161]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Thu, 19 Apr 2012 14:18:30 +0100 From: Andrew Halley To: Abhinandan Prateek , "xen-api@lists.xen.org" , Bob Ball , Andrew Halley Date: Thu, 19 Apr 2012 14:18:29 +0100 Thread-Topic: XCP 1.5 beta api Thread-Index: Ac0eAUIgbCXpb7jtSASB4XbFaGmYrwALadZy Message-ID: <101tr2brgdfgluqwf88y4gda.1334841462919@email.android.com> 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: Sat, 21 Apr 2012 21:51:05 +0000 Cc: Ram Chinta , Kevin Kluge Subject: Re: [Xen-API] XCP 1.5 beta api 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="===============1431025073952577317==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============1431025073952577317== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_101tr2brgdfgluqwf88y4gda1334841462919emailandroidcom_" --_000_101tr2brgdfgluqwf88y4gda1334841462919emailandroidcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Checking. Sent from my Mobile device - apologies for typos and brevity -------- Original message -------- Subject: XCP 1.5 beta api From: Abhinandan Prateek To: "xen-api@lists.xen.org" ,Bob Ball ,Andrew Halley CC: Kevin Kluge ,Ram Chinta We are testing support for XCP 1.5 beta in the cloudstack software. While t= esting we saw that the method get_mtime is omitted from /opt/xensource/sm/u= til.py. This method is present in XCP 1.1. The sr dir timestamp is used b= y cloudstack to check if the sr has changed. Is there a reason to do that ? Will it be possible to add it back. Thanks and Regards, Abhinandan Prateek --_000_101tr2brgdfgluqwf88y4gda1334841462919emailandroidcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Checking.


Sent from my Mobil= e device - apologies for typos and brevity


-------- Orig= inal message --------
Subject: XCP 1.5 beta api
From: Abhinandan Pra= teek <Abhinandan.Prateek@citrix.com>
To: "xen-api@lists.xen.= org" <xen-api@lists.xen.org>,Bob Ball <bob.ball@citrix.com>= ;,Andrew Halley <andrew.halley@citrix.com>
CC: Kevin Kluge <Ke= vin.Kluge@citrix.com>,Ram Chinta <ram.chinta@citrix.com>

<= br>

We are testing support for XCP 1.5 beta in the cloudstack software. While t= esting we saw that the method get_mtime is omitted from /opt/xensource/sm/u= til.py.  This method is present in XCP 1.1.  The sr dir timestamp= is used by cloudstack to check if the sr has changed.

Is there a reason to do that ? Will it be possible to add it back.

Thanks and Regards,
Abhinandan Prateek
 --_000_101tr2brgdfgluqwf88y4gda1334841462919emailandroidcom_-- --===============1431025073952577317== 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 --===============1431025073952577317==-- From xen-api-bounces@lists.xen.org Mon Apr 23 07:46:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 23 Apr 2012 07:46:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMDyh-0005vt-Sg; Mon, 23 Apr 2012 07:46:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMDyh-0005vS-1o for xen-api@lists.xen.org; Mon, 23 Apr 2012 07:46:31 +0000 Received: from [85.158.143.99:2646] by server-3.bemta-4.messagelabs.com id 1D/90-05853-6D8059F4; Mon, 23 Apr 2012 07:46:30 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1335167189!24751520!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15327 invoked from network); 23 Apr 2012 07:46:29 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2012 07:46:29 -0000 Received: by bkty15 with SMTP id y15so131683bkt.32 for ; Mon, 23 Apr 2012 00:46:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=SFrW8gz0/9UghL1ZyBowlr0bL+R2IO/sBvPU6tRHl+o=; b=DOrn5F7cFH5aIBmLdF00B5Cf59fddhn/BkaeEvJdtp6xk+W4rCZoq7P07LHD6kn/MC 0f7+2AEe7veB0+i+WHLVOBh2hnD7vtJxzPBhwlSkT9vWBfo6BIwkUbYuPyq3vJoHE7hF M9q/PIRuqucXGKxUG1GExOvYQIza/42rQ3gfo7G0IAzJjsjngp+tf7XVFNEPMNDSbHNT AHXl8f6NandJGq/K5ZQ67rUa6YVsEQo3xgeeMIpvL9m/TVPLP3OmXCpgaHlhrUF3SDwZ 7eszn9oEzdot2xJDkoEpGQNQsKW567Mjnd5kXpkIdSp0E/KkIckW8r8N+aNsa0QkV3Eh wj7w== Received: by 10.204.149.210 with SMTP id u18mr3828191bkv.34.1335167188788; Mon, 23 Apr 2012 00:46:28 -0700 (PDT) Received: from [172.16.26.11] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id s16sm22870013bkt.3.2012.04.23.00.46.21 (version=SSLv3 cipher=OTHER); Mon, 23 Apr 2012 00:46:25 -0700 (PDT) Message-ID: <4F9508CA.7040709@xen.org> Date: Mon, 23 Apr 2012 08:46:18 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-users@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org Subject: [Xen-API] Xen Document Day Today 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-Type: multipart/mixed; boundary="===============7571097226164389577==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7571097226164389577== Content-Type: multipart/alternative; boundary="------------000500090705090002080306" This is a multi-part message in MIME format. --------------000500090705090002080306 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Good Morning, it is Xen Document Day today! Join us on IRC: freenode channel *#xendocday* More info: wiki.xen.org/wiki/Xen_Document_Day TODO List: wiki.xen.org/wiki/Xen_Document_Days/TODO Lars --------------000500090705090002080306 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Good Morning,
it is Xen Document Day today!
Join us on IRC: freenode channel #xendocday
More info: wiki.xen.org/wiki/Xen_Document_Day
TODO List: wiki.xen.org/wiki/Xen_Document_Days/TODO
Lars
--------------000500090705090002080306-- --===============7571097226164389577== 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 --===============7571097226164389577==-- From xen-api-bounces@lists.xen.org Mon Apr 23 07:46:40 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 23 Apr 2012 07:46:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMDyh-0005vt-Sg; Mon, 23 Apr 2012 07:46:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMDyh-0005vS-1o for xen-api@lists.xen.org; Mon, 23 Apr 2012 07:46:31 +0000 Received: from [85.158.143.99:2646] by server-3.bemta-4.messagelabs.com id 1D/90-05853-6D8059F4; Mon, 23 Apr 2012 07:46:30 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1335167189!24751520!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15327 invoked from network); 23 Apr 2012 07:46:29 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-6.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2012 07:46:29 -0000 Received: by bkty15 with SMTP id y15so131683bkt.32 for ; Mon, 23 Apr 2012 00:46:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=SFrW8gz0/9UghL1ZyBowlr0bL+R2IO/sBvPU6tRHl+o=; b=DOrn5F7cFH5aIBmLdF00B5Cf59fddhn/BkaeEvJdtp6xk+W4rCZoq7P07LHD6kn/MC 0f7+2AEe7veB0+i+WHLVOBh2hnD7vtJxzPBhwlSkT9vWBfo6BIwkUbYuPyq3vJoHE7hF M9q/PIRuqucXGKxUG1GExOvYQIza/42rQ3gfo7G0IAzJjsjngp+tf7XVFNEPMNDSbHNT AHXl8f6NandJGq/K5ZQ67rUa6YVsEQo3xgeeMIpvL9m/TVPLP3OmXCpgaHlhrUF3SDwZ 7eszn9oEzdot2xJDkoEpGQNQsKW567Mjnd5kXpkIdSp0E/KkIckW8r8N+aNsa0QkV3Eh wj7w== Received: by 10.204.149.210 with SMTP id u18mr3828191bkv.34.1335167188788; Mon, 23 Apr 2012 00:46:28 -0700 (PDT) Received: from [172.16.26.11] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id s16sm22870013bkt.3.2012.04.23.00.46.21 (version=SSLv3 cipher=OTHER); Mon, 23 Apr 2012 00:46:25 -0700 (PDT) Message-ID: <4F9508CA.7040709@xen.org> Date: Mon, 23 Apr 2012 08:46:18 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-users@lists.xen.org, xen-api@lists.xen.org, xen-arm@lists.xen.org Subject: [Xen-API] Xen Document Day Today 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-Type: multipart/mixed; boundary="===============7571097226164389577==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============7571097226164389577== Content-Type: multipart/alternative; boundary="------------000500090705090002080306" This is a multi-part message in MIME format. --------------000500090705090002080306 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Good Morning, it is Xen Document Day today! Join us on IRC: freenode channel *#xendocday* More info: wiki.xen.org/wiki/Xen_Document_Day TODO List: wiki.xen.org/wiki/Xen_Document_Days/TODO Lars --------------000500090705090002080306 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Good Morning,
it is Xen Document Day today!
Join us on IRC: freenode channel #xendocday
More info: wiki.xen.org/wiki/Xen_Document_Day
TODO List: wiki.xen.org/wiki/Xen_Document_Days/TODO
Lars
--------------000500090705090002080306-- --===============7571097226164389577== 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 --===============7571097226164389577==-- From xen-api-bounces@lists.xen.org Mon Apr 23 08:20:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 23 Apr 2012 08:20: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 1SMEVh-0008F4-GT; Mon, 23 Apr 2012 08:20:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMEVg-0008Ej-7v for xen-api@lists.xen.org; Mon, 23 Apr 2012 08:20:36 +0000 Received: from [85.158.143.35:5008] by server-2.bemta-4.messagelabs.com id D9/E6-17550-3D0159F4; Mon, 23 Apr 2012 08:20:35 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1335169234!10044061!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NDQ1MA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15563 invoked from network); 23 Apr 2012 08:20:35 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2012 08:20:35 -0000 X-IronPort-AV: E=Sophos;i="4.75,465,1330905600"; d="scan'208";a="12071322" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 23 Apr 2012 08:20:34 +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, 23 Apr 2012 09:20:32 +0100 Message-ID: <1335169230.30700.0.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Mon, 23 Apr 2012 09:20:30 +0100 In-Reply-To: <4F9508CA.7040709@xen.org> References: <4F9508CA.7040709@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [XenARM] Xen Document Day Today 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-04-23 at 08:46 +0100, Lars Kurth wrote: > Good Morning, > it is Xen Document Day today! > Join us on IRC: freenode channel #xendocday > More info: wiki.xen.org/wiki/Xen_Document_Day NB, the above should actually be: http://wiki.xen.org/wiki/Xen_Document_Days (extra "s" on the end) > TODO List: wiki.xen.org/wiki/Xen_Document_Days/TODO > Lars _______________________________________________ xen-api mailing list xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Apr 23 08:20:44 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 23 Apr 2012 08:20: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 1SMEVh-0008F4-GT; Mon, 23 Apr 2012 08:20:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMEVg-0008Ej-7v for xen-api@lists.xen.org; Mon, 23 Apr 2012 08:20:36 +0000 Received: from [85.158.143.35:5008] by server-2.bemta-4.messagelabs.com id D9/E6-17550-3D0159F4; Mon, 23 Apr 2012 08:20:35 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1335169234!10044061!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NDQ1MA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15563 invoked from network); 23 Apr 2012 08:20:35 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2012 08:20:35 -0000 X-IronPort-AV: E=Sophos;i="4.75,465,1330905600"; d="scan'208";a="12071322" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 23 Apr 2012 08:20:34 +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, 23 Apr 2012 09:20:32 +0100 Message-ID: <1335169230.30700.0.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Mon, 23 Apr 2012 09:20:30 +0100 In-Reply-To: <4F9508CA.7040709@xen.org> References: <4F9508CA.7040709@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-users@lists.xen.org" , "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [XenARM] Xen Document Day Today 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-04-23 at 08:46 +0100, Lars Kurth wrote: > Good Morning, > it is Xen Document Day today! > Join us on IRC: freenode channel #xendocday > More info: wiki.xen.org/wiki/Xen_Document_Day NB, the above should actually be: http://wiki.xen.org/wiki/Xen_Document_Days (extra "s" on the end) > TODO List: wiki.xen.org/wiki/Xen_Document_Days/TODO > Lars _______________________________________________ xen-api mailing list xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Apr 23 08:54:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 23 Apr 2012 08:54: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 1SMF21-0001jj-5u; Mon, 23 Apr 2012 08:54:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMF1z-0001jW-PF for xen-api@lists.xen.org; Mon, 23 Apr 2012 08:54:00 +0000 Received: from [85.158.139.83:50092] by server-11.bemta-5.messagelabs.com id CA/D6-12959-6A8159F4; Mon, 23 Apr 2012 08:53:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1335171238!21148582!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NTY4MA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7568 invoked from network); 23 Apr 2012 08:53:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2012 08:53:58 -0000 X-IronPort-AV: E=Sophos;i="4.75,465,1330905600"; d="scan'208";a="12072215" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 23 Apr 2012 08:53:58 +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, 23 Apr 2012 09:53:57 +0100 Message-ID: <1335171236.30700.14.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Mon, 23 Apr 2012 09:53:56 +0100 In-Reply-To: <4F9199E5.5080409@xen.org> References: <4F9199E5.5080409@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [XenARM] IMPORTANT: Changes to XenSummit Format : Please vote! 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, 2012-04-20 at 18:16 +0100, Lars Kurth wrote: > Hi everybody, > > I have been talking to a number of the key contributors to the project > regarding XenSummit and got feedback on the format of XenSummit. Please > read, if you are active in the community and DO VOTE! > > Cheers > Lars > > Change of date in CFP! > ====================== > First I wanted to annouce that we are extending the CFP from May 1st to > 15th of June. Key community members felt that May 1 is too early. In > particular because we have closed the CFP 5-6 weeks before the event in > the past. Due to contractual issues June 15th is the last day we can do > though. > > Proposal! PLEASE READ! > ====================== > A number of vendors felt we should change the format of XenSummit to be > more like the Linux Kernel Summit. I.e. > a) An invite only event for the top 20-30 developers of the project > b) The main focus would be around finding technical solutions and making > decisions IMHO this sort of event would make a great addition to the XenSummit program rather than a replacement for it. i.e. a single day before the main event (which remains two days). > I can see the merit of this, but it is too late to do this for all of > XenSummit due to event contracts that havce been signed. > > However we have a number of options, moving towards this: > 1) Start half a day early and have an invite only XenDev Event event on > Sunday afteroon > 2) Cut XenSummit short by 1/2 day and append the XenDev event. This may > incur some financial penalties for Xen.org and the overall ticket cost > may have to be higher than in the past. > 3) Do the invite only meeting in parallel with XenSummit. I have an > additional large room on TUE the 27th, which we could use for this and I > also have two break-out rooms and can allocate one of them to the XenDev > event (these were intended for people sitting together and hacking on > stuff and/or BoFs). There are several options: hold the XenDev event on > 3.1) 26th afternoon > 3.2) 27th morning > 3.3) 27th afternoon > > In my view option 1) and 3.1) have the advantage that we can report back > to XenSummit, that nobody will miss key talks and that people can sit > together in the break-out rooms. > > Vote > ==== > Please vote by providing. Vote closes by the 27th. Vote by replying to > this mail with ... > -1: none of the above (i.e. I dont want a XenDev event) > +1 for a DevMeeting on sunday (aka for proposal 1) > +1 for cutting XenSummit short (aka for proposal 2) > +1 for parallel 26th PM (aka proposal 3.1) > +1 for parallel 27th AM (aka proposal 3.2) > +1 for parallel 27th PM (aka proposal 3.3) Family commitments prevent me attending this year so I'll abstain on the specifics of the date this time around and vote on the general principal: +1 for a XenDev event to precede each XenSummit Sorry for making up my own tick box ;-) 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 Apr 23 08:54:07 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 23 Apr 2012 08:54: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 1SMF21-0001jj-5u; Mon, 23 Apr 2012 08:54:01 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMF1z-0001jW-PF for xen-api@lists.xen.org; Mon, 23 Apr 2012 08:54:00 +0000 Received: from [85.158.139.83:50092] by server-11.bemta-5.messagelabs.com id CA/D6-12959-6A8159F4; Mon, 23 Apr 2012 08:53:58 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1335171238!21148582!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NTY4MA==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7568 invoked from network); 23 Apr 2012 08:53:58 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 23 Apr 2012 08:53:58 -0000 X-IronPort-AV: E=Sophos;i="4.75,465,1330905600"; d="scan'208";a="12072215" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 23 Apr 2012 08:53:58 +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, 23 Apr 2012 09:53:57 +0100 Message-ID: <1335171236.30700.14.camel@zakaz.uk.xensource.com> From: Ian Campbell To: "lars.kurth@xen.org" Date: Mon, 23 Apr 2012 09:53:56 +0100 In-Reply-To: <4F9199E5.5080409@xen.org> References: <4F9199E5.5080409@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.2.2-1 MIME-Version: 1.0 Cc: "xen-arm@lists.xen.org" , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" Subject: Re: [Xen-API] [XenARM] IMPORTANT: Changes to XenSummit Format : Please vote! 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, 2012-04-20 at 18:16 +0100, Lars Kurth wrote: > Hi everybody, > > I have been talking to a number of the key contributors to the project > regarding XenSummit and got feedback on the format of XenSummit. Please > read, if you are active in the community and DO VOTE! > > Cheers > Lars > > Change of date in CFP! > ====================== > First I wanted to annouce that we are extending the CFP from May 1st to > 15th of June. Key community members felt that May 1 is too early. In > particular because we have closed the CFP 5-6 weeks before the event in > the past. Due to contractual issues June 15th is the last day we can do > though. > > Proposal! PLEASE READ! > ====================== > A number of vendors felt we should change the format of XenSummit to be > more like the Linux Kernel Summit. I.e. > a) An invite only event for the top 20-30 developers of the project > b) The main focus would be around finding technical solutions and making > decisions IMHO this sort of event would make a great addition to the XenSummit program rather than a replacement for it. i.e. a single day before the main event (which remains two days). > I can see the merit of this, but it is too late to do this for all of > XenSummit due to event contracts that havce been signed. > > However we have a number of options, moving towards this: > 1) Start half a day early and have an invite only XenDev Event event on > Sunday afteroon > 2) Cut XenSummit short by 1/2 day and append the XenDev event. This may > incur some financial penalties for Xen.org and the overall ticket cost > may have to be higher than in the past. > 3) Do the invite only meeting in parallel with XenSummit. I have an > additional large room on TUE the 27th, which we could use for this and I > also have two break-out rooms and can allocate one of them to the XenDev > event (these were intended for people sitting together and hacking on > stuff and/or BoFs). There are several options: hold the XenDev event on > 3.1) 26th afternoon > 3.2) 27th morning > 3.3) 27th afternoon > > In my view option 1) and 3.1) have the advantage that we can report back > to XenSummit, that nobody will miss key talks and that people can sit > together in the break-out rooms. > > Vote > ==== > Please vote by providing. Vote closes by the 27th. Vote by replying to > this mail with ... > -1: none of the above (i.e. I dont want a XenDev event) > +1 for a DevMeeting on sunday (aka for proposal 1) > +1 for cutting XenSummit short (aka for proposal 2) > +1 for parallel 26th PM (aka proposal 3.1) > +1 for parallel 27th AM (aka proposal 3.2) > +1 for parallel 27th PM (aka proposal 3.3) Family commitments prevent me attending this year so I'll abstain on the specifics of the date this time around and vote on the general principal: +1 for a XenDev event to precede each XenSummit Sorry for making up my own tick box ;-) 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 Apr 23 17:16:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 23 Apr 2012 17:16:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMMs7-0006P6-9a; Mon, 23 Apr 2012 17:16:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMMs5-0006Os-G3 for xen-api@lists.xen.org; Mon, 23 Apr 2012 17:16:17 +0000 Received: from [85.158.138.51:45023] by server-10.bemta-3.messagelabs.com id 2D/32-29478-06E859F4; Mon, 23 Apr 2012 17:16:16 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1335201374!23379647!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDQ4ODE2Nw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18013 invoked from network); 23 Apr 2012 17:16:16 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-11.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Apr 2012 17:16:16 -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 q3NHGAJp032111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 23 Apr 2012 17:16:11 GMT Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q3NHG9MD006646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Apr 2012 17:16:10 GMT Received: from abhmt104.oracle.com (abhmt104.oracle.com [141.146.116.56]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q3NHGAwh014409; Mon, 23 Apr 2012 12:16:10 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 23 Apr 2012 10:16:09 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id EA11A4032D; Mon, 23 Apr 2012 13:11:04 -0400 (EDT) Date: Mon, 23 Apr 2012 13:11:04 -0400 From: Konrad Rzeszutek Wilk To: Ian Campbell Message-ID: <20120423171104.GA24378@phenom.dumpdata.com> References: <4F9199E5.5080409@xen.org> <1335171236.30700.14.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1335171236.30700.14.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: "xen-arm@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [XenARM] IMPORTANT: Changes to XenSummit Format : Please vote! 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, Apr 23, 2012 at 09:53:56AM +0100, Ian Campbell wrote: > On Fri, 2012-04-20 at 18:16 +0100, Lars Kurth wrote: > > Hi everybody, > > > > I have been talking to a number of the key contributors to the project > > regarding XenSummit and got feedback on the format of XenSummit. Please > > read, if you are active in the community and DO VOTE! > > > > Cheers > > Lars > > > > Change of date in CFP! > > ====================== > > First I wanted to annouce that we are extending the CFP from May 1st to > > 15th of June. Key community members felt that May 1 is too early. In > > particular because we have closed the CFP 5-6 weeks before the event in > > the past. Due to contractual issues June 15th is the last day we can do > > though. > > > > Proposal! PLEASE READ! > > ====================== > > A number of vendors felt we should change the format of XenSummit to be > > more like the Linux Kernel Summit. I.e. > > a) An invite only event for the top 20-30 developers of the project > > b) The main focus would be around finding technical solutions and making > > decisions > > IMHO this sort of event would make a great addition to the XenSummit > program rather than a replacement for it. i.e. a single day before the > main event (which remains two days). > > > I can see the merit of this, but it is too late to do this for all of > > XenSummit due to event contracts that havce been signed. > > > > However we have a number of options, moving towards this: > > 1) Start half a day early and have an invite only XenDev Event event on > > Sunday afteroon > > 2) Cut XenSummit short by 1/2 day and append the XenDev event. This may > > incur some financial penalties for Xen.org and the overall ticket cost > > may have to be higher than in the past. > > 3) Do the invite only meeting in parallel with XenSummit. I have an > > additional large room on TUE the 27th, which we could use for this and I > > also have two break-out rooms and can allocate one of them to the XenDev > > event (these were intended for people sitting together and hacking on > > stuff and/or BoFs). There are several options: hold the XenDev event on > > 3.1) 26th afternoon > > 3.2) 27th morning > > 3.3) 27th afternoon > > > > In my view option 1) and 3.1) have the advantage that we can report back > > to XenSummit, that nobody will miss key talks and that people can sit > > together in the break-out rooms. > > > > Vote > > ==== > > Please vote by providing. Vote closes by the 27th. Vote by replying to > > this mail with ... > > -1: none of the above (i.e. I dont want a XenDev event) > > +1 for a DevMeeting on sunday (aka for proposal 1) > > +1 for cutting XenSummit short (aka for proposal 2) > > +1 for parallel 26th PM (aka proposal 3.1) > > +1 for parallel 27th AM (aka proposal 3.2) > > +1 for parallel 27th PM (aka proposal 3.3) > > Family commitments prevent me attending this year so I'll abstain on the > specifics of the date this time around and vote on the general > principal: > +1 for a XenDev event to precede each XenSummit +1 for that. Even if it means just hitting the local if the crowd is small. _______________________________________________ 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 Apr 23 17:16:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 23 Apr 2012 17:16:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMMs7-0006P6-9a; Mon, 23 Apr 2012 17:16:19 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMMs5-0006Os-G3 for xen-api@lists.xen.org; Mon, 23 Apr 2012 17:16:17 +0000 Received: from [85.158.138.51:45023] by server-10.bemta-3.messagelabs.com id 2D/32-29478-06E859F4; Mon, 23 Apr 2012 17:16:16 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-11.tower-174.messagelabs.com!1335201374!23379647!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDQ4ODE2Nw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18013 invoked from network); 23 Apr 2012 17:16:16 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-11.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Apr 2012 17:16:16 -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 q3NHGAJp032111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 23 Apr 2012 17:16:11 GMT Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q3NHG9MD006646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Apr 2012 17:16:10 GMT Received: from abhmt104.oracle.com (abhmt104.oracle.com [141.146.116.56]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q3NHGAwh014409; Mon, 23 Apr 2012 12:16:10 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 23 Apr 2012 10:16:09 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id EA11A4032D; Mon, 23 Apr 2012 13:11:04 -0400 (EDT) Date: Mon, 23 Apr 2012 13:11:04 -0400 From: Konrad Rzeszutek Wilk To: Ian Campbell Message-ID: <20120423171104.GA24378@phenom.dumpdata.com> References: <4F9199E5.5080409@xen.org> <1335171236.30700.14.camel@zakaz.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1335171236.30700.14.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: "xen-arm@lists.xen.org" , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" Subject: Re: [Xen-API] [XenARM] IMPORTANT: Changes to XenSummit Format : Please vote! 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, Apr 23, 2012 at 09:53:56AM +0100, Ian Campbell wrote: > On Fri, 2012-04-20 at 18:16 +0100, Lars Kurth wrote: > > Hi everybody, > > > > I have been talking to a number of the key contributors to the project > > regarding XenSummit and got feedback on the format of XenSummit. Please > > read, if you are active in the community and DO VOTE! > > > > Cheers > > Lars > > > > Change of date in CFP! > > ====================== > > First I wanted to annouce that we are extending the CFP from May 1st to > > 15th of June. Key community members felt that May 1 is too early. In > > particular because we have closed the CFP 5-6 weeks before the event in > > the past. Due to contractual issues June 15th is the last day we can do > > though. > > > > Proposal! PLEASE READ! > > ====================== > > A number of vendors felt we should change the format of XenSummit to be > > more like the Linux Kernel Summit. I.e. > > a) An invite only event for the top 20-30 developers of the project > > b) The main focus would be around finding technical solutions and making > > decisions > > IMHO this sort of event would make a great addition to the XenSummit > program rather than a replacement for it. i.e. a single day before the > main event (which remains two days). > > > I can see the merit of this, but it is too late to do this for all of > > XenSummit due to event contracts that havce been signed. > > > > However we have a number of options, moving towards this: > > 1) Start half a day early and have an invite only XenDev Event event on > > Sunday afteroon > > 2) Cut XenSummit short by 1/2 day and append the XenDev event. This may > > incur some financial penalties for Xen.org and the overall ticket cost > > may have to be higher than in the past. > > 3) Do the invite only meeting in parallel with XenSummit. I have an > > additional large room on TUE the 27th, which we could use for this and I > > also have two break-out rooms and can allocate one of them to the XenDev > > event (these were intended for people sitting together and hacking on > > stuff and/or BoFs). There are several options: hold the XenDev event on > > 3.1) 26th afternoon > > 3.2) 27th morning > > 3.3) 27th afternoon > > > > In my view option 1) and 3.1) have the advantage that we can report back > > to XenSummit, that nobody will miss key talks and that people can sit > > together in the break-out rooms. > > > > Vote > > ==== > > Please vote by providing. Vote closes by the 27th. Vote by replying to > > this mail with ... > > -1: none of the above (i.e. I dont want a XenDev event) > > +1 for a DevMeeting on sunday (aka for proposal 1) > > +1 for cutting XenSummit short (aka for proposal 2) > > +1 for parallel 26th PM (aka proposal 3.1) > > +1 for parallel 27th AM (aka proposal 3.2) > > +1 for parallel 27th PM (aka proposal 3.3) > > Family commitments prevent me attending this year so I'll abstain on the > specifics of the date this time around and vote on the general > principal: > +1 for a XenDev event to precede each XenSummit +1 for that. Even if it means just hitting the local if the crowd is small. _______________________________________________ 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 Apr 24 10:32:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 24 Apr 2012 10:32: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 1SMd2y-00005N-BI; Tue, 24 Apr 2012 10:32:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMd2w-00004v-Q0 for xen-api@lists.xen.org; Tue, 24 Apr 2012 10:32:35 +0000 Received: from [85.158.138.51:22509] by server-6.bemta-3.messagelabs.com id 92/FE-05145-141869F4; Tue, 24 Apr 2012 10:32:33 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1335263552!14584964!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 25920 invoked from network); 24 Apr 2012 10:32:33 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2012 10:32:33 -0000 Received: by bkty15 with SMTP id y15so464586bkt.32 for ; Tue, 24 Apr 2012 03:32:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PUQgzotWf9ALMoEzuDJ+ob5k+5xgz7EmAI2Vd7R4+8k=; b=mQ2zQKXSJKjPq+0CHiF8svsJB/hCCWcefvUHLe6goGx4ambhmF6xeP6p3rcBTYQ5Hj GTsqFBYsVguXSsdBOT+rVvin15BEUqqPO+3zu+H61j/1eac13CWSbl/DfCcxD+gDGnKw 8wvGYXDROO0cpKpm+Daq/4jGORWFx0ko01FA+Tlslwy1GyR295SvNZq66S0PfNEXiQvj IwRixzq9+zerwdtUyoScMXluBVDgUCUFhbgzf2Wmp60um4sHQQRGOUQN1XSsX5u3ayf/ oki74Jkd0LGKtpq8Xmoo/j9u+mYC5pVndJtDEUW07uK8w9mN+foVo5Pmag6IxtIgwLj6 jxJw== Received: by 10.204.149.210 with SMTP id u18mr965382bkv.34.1335263552144; Tue, 24 Apr 2012 03:32:32 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id zx16sm30843660bkb.13.2012.04.24.03.32.29 (version=SSLv3 cipher=OTHER); Tue, 24 Apr 2012 03:32:30 -0700 (PDT) Message-ID: <4F96813C.6030108@xen.org> Date: Tue, 24 Apr 2012 11:32:28 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-arm@lists.xen.org, xen-api@lists.xen.org References: <4F9199E5.5080409@xen.org> In-Reply-To: <4F9199E5.5080409@xen.org> Subject: Re: [Xen-API] IMPORTANT: Changes to XenSummit Format : Please vote! 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 I got a number of votes so far: votes are still open until Friday let me summarize votes so far: - 5 votes for sunday (option 1) - 2 votes for a parallel session on the 26th PM (option 3.1) - 1 vote for cutting XenSummit short (option 2) Regards Lars On 20/04/2012 18:16, Lars Kurth wrote: > Hi everybody, > > I have been talking to a number of the key contributors to the project > regarding XenSummit and got feedback on the format of XenSummit. > Please read, if you are active in the community and DO VOTE! > > Cheers > Lars > > Change of date in CFP! > ====================== > First I wanted to annouce that we are extending the CFP from May 1st > to 15th of June. Key community members felt that May 1 is too early. > In particular because we have closed the CFP 5-6 weeks before the > event in the past. Due to contractual issues June 15th is the last day > we can do though. > > Proposal! PLEASE READ! > ====================== > A number of vendors felt we should change the format of XenSummit to > be more like the Linux Kernel Summit. I.e. > a) An invite only event for the top 20-30 developers of the project > b) The main focus would be around finding technical solutions and > making decisions > I can see the merit of this, but it is too late to do this for all of > XenSummit due to event contracts that havce been signed. > > However we have a number of options, moving towards this: > 1) Start half a day early and have an invite only XenDev Event event > on Sunday afteroon > 2) Cut XenSummit short by 1/2 day and append the XenDev event. This > may incur some financial penalties for Xen.org and the overall ticket > cost may have to be higher than in the past. > 3) Do the invite only meeting in parallel with XenSummit. I have an > additional large room on TUE the 27th, which we could use for this and > I also have two break-out rooms and can allocate one of them to the > XenDev event (these were intended for people sitting together and > hacking on stuff and/or BoFs). There are several options: hold the > XenDev event on > 3.1) 26th afternoon > 3.2) 27th morning > 3.3) 27th afternoon > > In my view option 1) and 3.1) have the advantage that we can report > back to XenSummit, that nobody will miss key talks and that people can > sit together in the break-out rooms. > > Vote > ==== > Please vote by providing. Vote closes by the 27th. Vote by replying to > this mail with ... > -1: none of the above (i.e. I dont want a XenDev event) > +1 for a DevMeeting on sunday (aka for proposal 1) > +1 for cutting XenSummit short (aka for proposal 2) > +1 for parallel 26th PM (aka proposal 3.1) > +1 for parallel 27th AM (aka proposal 3.2) > +1 for parallel 27th PM (aka proposal 3.3) > _______________________________________________ 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 Apr 24 10:32:43 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 24 Apr 2012 10:32: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 1SMd2y-00005N-BI; Tue, 24 Apr 2012 10:32:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMd2w-00004v-Q0 for xen-api@lists.xen.org; Tue, 24 Apr 2012 10:32:35 +0000 Received: from [85.158.138.51:22509] by server-6.bemta-3.messagelabs.com id 92/FE-05145-141869F4; Tue, 24 Apr 2012 10:32:33 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-174.messagelabs.com!1335263552!14584964!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 25920 invoked from network); 24 Apr 2012 10:32:33 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-7.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2012 10:32:33 -0000 Received: by bkty15 with SMTP id y15so464586bkt.32 for ; Tue, 24 Apr 2012 03:32:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PUQgzotWf9ALMoEzuDJ+ob5k+5xgz7EmAI2Vd7R4+8k=; b=mQ2zQKXSJKjPq+0CHiF8svsJB/hCCWcefvUHLe6goGx4ambhmF6xeP6p3rcBTYQ5Hj GTsqFBYsVguXSsdBOT+rVvin15BEUqqPO+3zu+H61j/1eac13CWSbl/DfCcxD+gDGnKw 8wvGYXDROO0cpKpm+Daq/4jGORWFx0ko01FA+Tlslwy1GyR295SvNZq66S0PfNEXiQvj IwRixzq9+zerwdtUyoScMXluBVDgUCUFhbgzf2Wmp60um4sHQQRGOUQN1XSsX5u3ayf/ oki74Jkd0LGKtpq8Xmoo/j9u+mYC5pVndJtDEUW07uK8w9mN+foVo5Pmag6IxtIgwLj6 jxJw== Received: by 10.204.149.210 with SMTP id u18mr965382bkv.34.1335263552144; Tue, 24 Apr 2012 03:32:32 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id zx16sm30843660bkb.13.2012.04.24.03.32.29 (version=SSLv3 cipher=OTHER); Tue, 24 Apr 2012 03:32:30 -0700 (PDT) Message-ID: <4F96813C.6030108@xen.org> Date: Tue, 24 Apr 2012 11:32:28 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-devel@lists.xen.org, xen-arm@lists.xen.org, xen-api@lists.xen.org References: <4F9199E5.5080409@xen.org> In-Reply-To: <4F9199E5.5080409@xen.org> Subject: Re: [Xen-API] IMPORTANT: Changes to XenSummit Format : Please vote! 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 I got a number of votes so far: votes are still open until Friday let me summarize votes so far: - 5 votes for sunday (option 1) - 2 votes for a parallel session on the 26th PM (option 3.1) - 1 vote for cutting XenSummit short (option 2) Regards Lars On 20/04/2012 18:16, Lars Kurth wrote: > Hi everybody, > > I have been talking to a number of the key contributors to the project > regarding XenSummit and got feedback on the format of XenSummit. > Please read, if you are active in the community and DO VOTE! > > Cheers > Lars > > Change of date in CFP! > ====================== > First I wanted to annouce that we are extending the CFP from May 1st > to 15th of June. Key community members felt that May 1 is too early. > In particular because we have closed the CFP 5-6 weeks before the > event in the past. Due to contractual issues June 15th is the last day > we can do though. > > Proposal! PLEASE READ! > ====================== > A number of vendors felt we should change the format of XenSummit to > be more like the Linux Kernel Summit. I.e. > a) An invite only event for the top 20-30 developers of the project > b) The main focus would be around finding technical solutions and > making decisions > I can see the merit of this, but it is too late to do this for all of > XenSummit due to event contracts that havce been signed. > > However we have a number of options, moving towards this: > 1) Start half a day early and have an invite only XenDev Event event > on Sunday afteroon > 2) Cut XenSummit short by 1/2 day and append the XenDev event. This > may incur some financial penalties for Xen.org and the overall ticket > cost may have to be higher than in the past. > 3) Do the invite only meeting in parallel with XenSummit. I have an > additional large room on TUE the 27th, which we could use for this and > I also have two break-out rooms and can allocate one of them to the > XenDev event (these were intended for people sitting together and > hacking on stuff and/or BoFs). There are several options: hold the > XenDev event on > 3.1) 26th afternoon > 3.2) 27th morning > 3.3) 27th afternoon > > In my view option 1) and 3.1) have the advantage that we can report > back to XenSummit, that nobody will miss key talks and that people can > sit together in the break-out rooms. > > Vote > ==== > Please vote by providing. Vote closes by the 27th. Vote by replying to > this mail with ... > -1: none of the above (i.e. I dont want a XenDev event) > +1 for a DevMeeting on sunday (aka for proposal 1) > +1 for cutting XenSummit short (aka for proposal 2) > +1 for parallel 26th PM (aka proposal 3.1) > +1 for parallel 27th AM (aka proposal 3.2) > +1 for parallel 27th PM (aka proposal 3.3) > _______________________________________________ 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 Apr 24 14:54:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 24 Apr 2012 14:54:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMh8I-0005iE-J4; Tue, 24 Apr 2012 14:54:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMh8H-0005hm-9r for xen-api@lists.xensource.com; Tue, 24 Apr 2012 14:54:21 +0000 Received: from [85.158.138.51:56632] by server-3.bemta-3.messagelabs.com id 26/48-04048-C9EB69F4; Tue, 24 Apr 2012 14:54:20 +0000 X-Env-Sender: chris.percol@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1335279259!23570315!1 X-Originating-IP: [209.85.214.43] 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 4158 invoked from network); 24 Apr 2012 14:54:19 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2012 14:54:19 -0000 Received: by bkwj5 with SMTP id j5so732007bkw.30 for ; Tue, 24 Apr 2012 07:54:19 -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=0DwbOxKPABuPDUxuCfCjiJmpD1huikTI4zbyCjV9vVI=; b=BIvlYejflDpu1wl0q/SmqplDdDR3QWoLTcqLvWbrrxMhZD3HLRstubSvyszsbdGyk+ dDfLluN1mVbJ0flZ8lyKyC/9+pBaq1fwsy3ri9sWVmlDe3WNc1wIQemigI+iYMeiVtXU BIydoUyS2JsrahG/+MrWqWkUsUEiErBLqO09KH23CzJhzkDO8BReMpVLjA4clYKSBuNI tYlrF24Us1OSS4g86LjXgraGQC7aYx6vY+C3A8Ri7u+t78HoUn5T2Vht/RNw2t55N6Sr ufbK/mogvcHOMbdKtYJmu5D2V67EdfIxtuf82obPhAKxFXgG2UUJsLHeATB0lCDOoPWd HRRQ== MIME-Version: 1.0 Received: by 10.204.154.10 with SMTP id m10mr6106239bkw.13.1335279258825; Tue, 24 Apr 2012 07:54:18 -0700 (PDT) Received: by 10.205.129.19 with HTTP; Tue, 24 Apr 2012 07:54:18 -0700 (PDT) Date: Tue, 24 Apr 2012 15:54:18 +0100 Message-ID: From: Chris Percol To: xen-api@lists.xensource.com Subject: [Xen-API] vhd_complete errors and disk corruption 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, We're encountering the following error intermittently on XCP 1.0. It seems to be restricted to particular VMs. We've had 2 out of around 30 affected by this issue, which seems to end up causing disk corruption. Apr 24 12:55:25 x5 tapdisk[5051]: ERROR: errno -5 at vhd_complete: /dev/mapper/VG_XenStorage--86d18095--7819--25b5--e4d4--fff89212bd56-VHD--248ac421--1683--4ab2--b5c6--49fb62849cb6: op: 3, lsec: 15908864, secs: 1, nbytes: 512, blk: 3884, blk_offset: 1576183 I'd appreciate any suggestions on how to debug this further. Thanks, Chris _______________________________________________ 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 Apr 24 14:54:32 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Tue, 24 Apr 2012 14:54:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMh8I-0005iE-J4; Tue, 24 Apr 2012 14:54:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMh8H-0005hm-9r for xen-api@lists.xensource.com; Tue, 24 Apr 2012 14:54:21 +0000 Received: from [85.158.138.51:56632] by server-3.bemta-3.messagelabs.com id 26/48-04048-C9EB69F4; Tue, 24 Apr 2012 14:54:20 +0000 X-Env-Sender: chris.percol@gmail.com X-Msg-Ref: server-4.tower-174.messagelabs.com!1335279259!23570315!1 X-Originating-IP: [209.85.214.43] 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 4158 invoked from network); 24 Apr 2012 14:54:19 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-4.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 24 Apr 2012 14:54:19 -0000 Received: by bkwj5 with SMTP id j5so732007bkw.30 for ; Tue, 24 Apr 2012 07:54:19 -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=0DwbOxKPABuPDUxuCfCjiJmpD1huikTI4zbyCjV9vVI=; b=BIvlYejflDpu1wl0q/SmqplDdDR3QWoLTcqLvWbrrxMhZD3HLRstubSvyszsbdGyk+ dDfLluN1mVbJ0flZ8lyKyC/9+pBaq1fwsy3ri9sWVmlDe3WNc1wIQemigI+iYMeiVtXU BIydoUyS2JsrahG/+MrWqWkUsUEiErBLqO09KH23CzJhzkDO8BReMpVLjA4clYKSBuNI tYlrF24Us1OSS4g86LjXgraGQC7aYx6vY+C3A8Ri7u+t78HoUn5T2Vht/RNw2t55N6Sr ufbK/mogvcHOMbdKtYJmu5D2V67EdfIxtuf82obPhAKxFXgG2UUJsLHeATB0lCDOoPWd HRRQ== MIME-Version: 1.0 Received: by 10.204.154.10 with SMTP id m10mr6106239bkw.13.1335279258825; Tue, 24 Apr 2012 07:54:18 -0700 (PDT) Received: by 10.205.129.19 with HTTP; Tue, 24 Apr 2012 07:54:18 -0700 (PDT) Date: Tue, 24 Apr 2012 15:54:18 +0100 Message-ID: From: Chris Percol To: xen-api@lists.xensource.com Subject: [Xen-API] vhd_complete errors and disk corruption 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, We're encountering the following error intermittently on XCP 1.0. It seems to be restricted to particular VMs. We've had 2 out of around 30 affected by this issue, which seems to end up causing disk corruption. Apr 24 12:55:25 x5 tapdisk[5051]: ERROR: errno -5 at vhd_complete: /dev/mapper/VG_XenStorage--86d18095--7819--25b5--e4d4--fff89212bd56-VHD--248ac421--1683--4ab2--b5c6--49fb62849cb6: op: 3, lsec: 15908864, secs: 1, nbytes: 512, blk: 3884, blk_offset: 1576183 I'd appreciate any suggestions on how to debug this further. Thanks, Chris _______________________________________________ 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 Apr 25 07:31:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 25 Apr 2012 07:31:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMwh7-00046R-ED; Wed, 25 Apr 2012 07:31:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMwh6-00046M-G1 for xen-api@lists.xensource.com; Wed, 25 Apr 2012 07:31:20 +0000 Received: from [193.109.254.147:54919] by server-1.bemta-14.messagelabs.com id A5/E1-29372-748A79F4; Wed, 25 Apr 2012 07:31:19 +0000 X-Env-Sender: jordan.tomkinson@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1335339073!6169314!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6988 invoked from network); 25 Apr 2012 07:31:15 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 25 Apr 2012 07:31:15 -0000 Received: by obbtb18 with SMTP id tb18so2628021obb.30 for ; Wed, 25 Apr 2012 00:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=w1ObcfxM6JiJkB5ihgWeMShRAOEq92E0hUE0W3EHo4w=; b=QZZ+Jyeb7hvWySmOM/T+jBj677/lBmQSYmTQgRZHkKhWa+lROOi+mYMkF8ZYzTc/v/ diWKO11nv5LJFTBVAwmaWyTZE67TLVNS/wB5/WDGWNZKmBL0p2JfvJzK8fHecA0PDyJw yYmp0jjyADMk1NDZdjhSJ/k7WCH8pmYyiEAS5fMpWr8Ck4K6u7Dh/o7BCaYW350vNPC7 o6aP+UQX3vBb84p/z5BszfmK56hEJ9ld+ATYxUuVBvreuzT9IlP5qLfxDd3IcMW0sFPx QffAD8vBkPbnLfSB4gm1SiuwKb617XvFuNJmoo0aRbC8lUGU1SJ1H/xDaTamd+QzVKjk t6aw== MIME-Version: 1.0 Received: by 10.60.169.165 with SMTP id af5mr1696758oec.72.1335339073435; Wed, 25 Apr 2012 00:31:13 -0700 (PDT) Received: by 10.182.118.38 with HTTP; Wed, 25 Apr 2012 00:31:13 -0700 (PDT) Date: Wed, 25 Apr 2012 15:31:13 +0800 X-Google-Sender-Auth: O2dZjVo0W_Ho-YhXni3aB2vcPBY Message-ID: From: Jordan Tomkinson To: xen-api@lists.xensource.com Subject: [Xen-API] xenblkfront i/o errors corrupting domU 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="===============0144464831740983778==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0144464831740983778== Content-Type: multipart/alternative; boundary=bcaec54a3df420776204be7bdb8e --bcaec54a3df420776204be7bdb8e Content-Type: text/plain; charset=ISO-8859-1 Hi list, I am seeing all the problems described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/824089 with XCP 1.5 beta (1.4.99) I am using barrier=0 in my fstab mount options on all ubuntu 12.04 guests both hvm and pv and still seeing corrupted ext3 and ext4 partitions resulting in loss of data from the guest and even completely unbootable guests Towards the end of the ubuntu bug report Malcolm Scott indicates that this bug is known by Citrix and needs to be fixed on the dom0 Will this patch be available for XCP as well as XenServer ? When can we expect it ? --bcaec54a3df420776204be7bdb8e Content-Type: text/html; charset=ISO-8859-1 Hi list,

I am seeing all the problems described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/824089 with XCP 1.5 beta (1.4.99)
I am using barrier=0 in my fstab mount options on all ubuntu 12.04 guests both hvm and pv and still seeing corrupted ext3 and ext4
partitions resulting in loss of data from the guest and even completely unbootable guests

Towards the end of the ubuntu bug report Malcolm Scott indicates that this bug is known by Citrix and needs to be fixed on the dom0

Will this patch be available for XCP as well as XenServer ?
When can we expect it ?

--bcaec54a3df420776204be7bdb8e-- --===============0144464831740983778== 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 --===============0144464831740983778==-- From xen-api-bounces@lists.xen.org Wed Apr 25 07:31:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 25 Apr 2012 07:31:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMwh7-00046R-ED; Wed, 25 Apr 2012 07:31:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMwh6-00046M-G1 for xen-api@lists.xensource.com; Wed, 25 Apr 2012 07:31:20 +0000 Received: from [193.109.254.147:54919] by server-1.bemta-14.messagelabs.com id A5/E1-29372-748A79F4; Wed, 25 Apr 2012 07:31:19 +0000 X-Env-Sender: jordan.tomkinson@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1335339073!6169314!1 X-Originating-IP: [209.85.214.171] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6988 invoked from network); 25 Apr 2012 07:31:15 -0000 Received: from mail-ob0-f171.google.com (HELO mail-ob0-f171.google.com) (209.85.214.171) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 25 Apr 2012 07:31:15 -0000 Received: by obbtb18 with SMTP id tb18so2628021obb.30 for ; Wed, 25 Apr 2012 00:31:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=w1ObcfxM6JiJkB5ihgWeMShRAOEq92E0hUE0W3EHo4w=; b=QZZ+Jyeb7hvWySmOM/T+jBj677/lBmQSYmTQgRZHkKhWa+lROOi+mYMkF8ZYzTc/v/ diWKO11nv5LJFTBVAwmaWyTZE67TLVNS/wB5/WDGWNZKmBL0p2JfvJzK8fHecA0PDyJw yYmp0jjyADMk1NDZdjhSJ/k7WCH8pmYyiEAS5fMpWr8Ck4K6u7Dh/o7BCaYW350vNPC7 o6aP+UQX3vBb84p/z5BszfmK56hEJ9ld+ATYxUuVBvreuzT9IlP5qLfxDd3IcMW0sFPx QffAD8vBkPbnLfSB4gm1SiuwKb617XvFuNJmoo0aRbC8lUGU1SJ1H/xDaTamd+QzVKjk t6aw== MIME-Version: 1.0 Received: by 10.60.169.165 with SMTP id af5mr1696758oec.72.1335339073435; Wed, 25 Apr 2012 00:31:13 -0700 (PDT) Received: by 10.182.118.38 with HTTP; Wed, 25 Apr 2012 00:31:13 -0700 (PDT) Date: Wed, 25 Apr 2012 15:31:13 +0800 X-Google-Sender-Auth: O2dZjVo0W_Ho-YhXni3aB2vcPBY Message-ID: From: Jordan Tomkinson To: xen-api@lists.xensource.com Subject: [Xen-API] xenblkfront i/o errors corrupting domU 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="===============0144464831740983778==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0144464831740983778== Content-Type: multipart/alternative; boundary=bcaec54a3df420776204be7bdb8e --bcaec54a3df420776204be7bdb8e Content-Type: text/plain; charset=ISO-8859-1 Hi list, I am seeing all the problems described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/824089 with XCP 1.5 beta (1.4.99) I am using barrier=0 in my fstab mount options on all ubuntu 12.04 guests both hvm and pv and still seeing corrupted ext3 and ext4 partitions resulting in loss of data from the guest and even completely unbootable guests Towards the end of the ubuntu bug report Malcolm Scott indicates that this bug is known by Citrix and needs to be fixed on the dom0 Will this patch be available for XCP as well as XenServer ? When can we expect it ? --bcaec54a3df420776204be7bdb8e Content-Type: text/html; charset=ISO-8859-1 Hi list,

I am seeing all the problems described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/824089 with XCP 1.5 beta (1.4.99)
I am using barrier=0 in my fstab mount options on all ubuntu 12.04 guests both hvm and pv and still seeing corrupted ext3 and ext4
partitions resulting in loss of data from the guest and even completely unbootable guests

Towards the end of the ubuntu bug report Malcolm Scott indicates that this bug is known by Citrix and needs to be fixed on the dom0

Will this patch be available for XCP as well as XenServer ?
When can we expect it ?

--bcaec54a3df420776204be7bdb8e-- --===============0144464831740983778== 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 --===============0144464831740983778==-- From xen-api-bounces@lists.xen.org Wed Apr 25 08:12:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 25 Apr 2012 08:12: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 1SMxKe-0005Rz-0t; Wed, 25 Apr 2012 08:12:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMxKa-0005Rh-RO for xen-api@lists.xensource.com; Wed, 25 Apr 2012 08:12:10 +0000 Received: from [85.158.138.51:39786] by server-9.bemta-3.messagelabs.com id 1B/80-26691-8D1B79F4; Wed, 25 Apr 2012 08:12:08 +0000 X-Env-Sender: chris.percol@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1335341525!23538585!1 X-Originating-IP: [209.85.214.43] 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 30483 invoked from network); 25 Apr 2012 08:12:05 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Apr 2012 08:12:05 -0000 Received: by bkwj5 with SMTP id j5so1434312bkw.30 for ; Wed, 25 Apr 2012 01:12:04 -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 :content-type:content-transfer-encoding; bh=uAID8lCTkulpLQV8zeGQsrSfsBC8+aDdcnWrpf9or/Q=; b=oDMqBDGhew4Jl9hX2TwkXhQHDJk/0yPh2Vi46lhgn04GAw/upYk5Dnrf9SewKtnDOy SvYxXYgSO5RCLe26ab1Xm9xQlnlJl11E7lMaVgEHqzKRglIsK9473LcEf6GEw7rcg1PH 28KOr1MGvr4i77za64Cqledg1ffnq0Na8rAUA/gnObL/spRNUJE++TazV4W6v3DrELOO Wha7QbCcHuggotoUWhauoylo4FkjWcsL4YRVICs8+bR206FQN3Yw83tSyCVSk4RQsZ26 M/iwmAWeZP9VseFrqCOVOebYZ79NpA4r+j8taXNb/7EHUhcKvWCKc4wDIk7/3dwftPTC oi2A== MIME-Version: 1.0 Received: by 10.204.155.147 with SMTP id s19mr516240bkw.140.1335341524771; Wed, 25 Apr 2012 01:12:04 -0700 (PDT) Received: by 10.205.129.19 with HTTP; Wed, 25 Apr 2012 01:12:04 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 Apr 2012 09:12:04 +0100 Message-ID: From: Chris Percol To: xen-api@lists.xensource.com Subject: Re: [Xen-API] vhd_complete errors and disk corruption 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 - Has anyone had any thoughts on this, or can anyone suggest a better place for me to ask such questions? Thanks, Chris On Tue, Apr 24, 2012 at 3:54 PM, Chris Percol wrot= e: > Hi, > We're encountering the following error intermittently on XCP 1.0. =A0It > seems to be restricted to particular VMs. =A0We've had 2 out of around > 30 affected by this issue, which seems to end up causing disk > corruption. > > > Apr 24 12:55:25 x5 tapdisk[5051]: ERROR: errno -5 at vhd_complete: > /dev/mapper/VG_XenStorage--86d18095--7819--25b5--e4d4--fff89212bd56-VHD--= 248ac421--1683--4ab2--b5c6--49fb62849cb6: > op: 3, lsec: 15908864, secs: 1, nbytes: 512, blk: 3884, blk_offset: > 1576183 > > I'd appreciate any suggestions on how to debug this further. > > Thanks, > Chris _______________________________________________ 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 Apr 25 08:12:18 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 25 Apr 2012 08:12: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 1SMxKe-0005Rz-0t; Wed, 25 Apr 2012 08:12:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SMxKa-0005Rh-RO for xen-api@lists.xensource.com; Wed, 25 Apr 2012 08:12:10 +0000 Received: from [85.158.138.51:39786] by server-9.bemta-3.messagelabs.com id 1B/80-26691-8D1B79F4; Wed, 25 Apr 2012 08:12:08 +0000 X-Env-Sender: chris.percol@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1335341525!23538585!1 X-Originating-IP: [209.85.214.43] 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 30483 invoked from network); 25 Apr 2012 08:12:05 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 25 Apr 2012 08:12:05 -0000 Received: by bkwj5 with SMTP id j5so1434312bkw.30 for ; Wed, 25 Apr 2012 01:12:04 -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 :content-type:content-transfer-encoding; bh=uAID8lCTkulpLQV8zeGQsrSfsBC8+aDdcnWrpf9or/Q=; b=oDMqBDGhew4Jl9hX2TwkXhQHDJk/0yPh2Vi46lhgn04GAw/upYk5Dnrf9SewKtnDOy SvYxXYgSO5RCLe26ab1Xm9xQlnlJl11E7lMaVgEHqzKRglIsK9473LcEf6GEw7rcg1PH 28KOr1MGvr4i77za64Cqledg1ffnq0Na8rAUA/gnObL/spRNUJE++TazV4W6v3DrELOO Wha7QbCcHuggotoUWhauoylo4FkjWcsL4YRVICs8+bR206FQN3Yw83tSyCVSk4RQsZ26 M/iwmAWeZP9VseFrqCOVOebYZ79NpA4r+j8taXNb/7EHUhcKvWCKc4wDIk7/3dwftPTC oi2A== MIME-Version: 1.0 Received: by 10.204.155.147 with SMTP id s19mr516240bkw.140.1335341524771; Wed, 25 Apr 2012 01:12:04 -0700 (PDT) Received: by 10.205.129.19 with HTTP; Wed, 25 Apr 2012 01:12:04 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 Apr 2012 09:12:04 +0100 Message-ID: From: Chris Percol To: xen-api@lists.xensource.com Subject: Re: [Xen-API] vhd_complete errors and disk corruption 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 - Has anyone had any thoughts on this, or can anyone suggest a better place for me to ask such questions? Thanks, Chris On Tue, Apr 24, 2012 at 3:54 PM, Chris Percol wrot= e: > Hi, > We're encountering the following error intermittently on XCP 1.0. =A0It > seems to be restricted to particular VMs. =A0We've had 2 out of around > 30 affected by this issue, which seems to end up causing disk > corruption. > > > Apr 24 12:55:25 x5 tapdisk[5051]: ERROR: errno -5 at vhd_complete: > /dev/mapper/VG_XenStorage--86d18095--7819--25b5--e4d4--fff89212bd56-VHD--= 248ac421--1683--4ab2--b5c6--49fb62849cb6: > op: 3, lsec: 15908864, secs: 1, nbytes: 512, blk: 3884, blk_offset: > 1576183 > > I'd appreciate any suggestions on how to debug this further. > > Thanks, > Chris _______________________________________________ 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 Apr 25 18:12:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 25 Apr 2012 18:12:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SN6hN-00067k-9j; Wed, 25 Apr 2012 18:12:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SN6hL-00067d-MG for xen-api@lists.xen.org; Wed, 25 Apr 2012 18:12:15 +0000 Received: from [85.158.139.83:46245] by server-5.bemta-5.messagelabs.com id 3C/F9-13566-E7E389F4; Wed, 25 Apr 2012 18:12:14 +0000 X-Env-Sender: dbhout@sequenciainc.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1335377533!18142081!1 X-Originating-IP: [206.188.198.66] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA2LjE4OC4xOTguNjYgPT4gMTI3MTY4\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24586 invoked from network); 25 Apr 2012 18:12:14 -0000 Received: from omr1pod1.networksolutionsemail.com (HELO omr1pod1.networksolutionsemail.com) (206.188.198.66) by server-16.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Apr 2012 18:12:14 -0000 Received: from mail.networksolutionsemail.com (mailpod1.networksolutionsemail.com [206.188.198.65]) by omr1pod1.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q3PICC4N011784 for ; Wed, 25 Apr 2012 14:12:13 -0400 X-Authenticated-IP: 206.188.198.65 Received: from [206.188.198.65] ([206.188.198.65:47064] helo=oxapp3pod1.mgt.hosting.qts.netsol.com) by cm-omr3pod1 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTP id 28/B0-00981-C7E389F4; Wed, 25 Apr 2012 14:12:12 -0400 Date: Wed, 25 Apr 2012 14:12:12 -0400 (EDT) From: David Hout To: xen-api@lists.xen.org Message-ID: <644653400.127753.1335377532834.JavaMail.vpopmail@mail.sequenciainc.com> MIME-Version: 1.0 X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v6.20.1-Rev8 Subject: [Xen-API] empty template list X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: David Hout List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7407320820736528782==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7407320820736528782== Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Hi,

 

I've been working to get a Kronos XCP installation running on Debian SID.  I started out using the instructions here (http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution) and then once I got down the road far enough I used the instructions in /usr/share/doc/xcp-xapi/README.Debian.gz on the server itself.

 

I think I'm very close but my issue at the moment is I can't see any templates.

 

xe template-list returns nothing whatsoever.

 

I went back through the archives and saw a similar problem posted on December 19 but didn't see any resolution.

 

Can anybody help?

 

Thanks,

 

Dave

 

 

--===============7407320820736528782== 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 --===============7407320820736528782==-- From xen-api-bounces@lists.xen.org Wed Apr 25 18:12:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Wed, 25 Apr 2012 18:12:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SN6hN-00067k-9j; Wed, 25 Apr 2012 18:12:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SN6hL-00067d-MG for xen-api@lists.xen.org; Wed, 25 Apr 2012 18:12:15 +0000 Received: from [85.158.139.83:46245] by server-5.bemta-5.messagelabs.com id 3C/F9-13566-E7E389F4; Wed, 25 Apr 2012 18:12:14 +0000 X-Env-Sender: dbhout@sequenciainc.com X-Msg-Ref: server-16.tower-182.messagelabs.com!1335377533!18142081!1 X-Originating-IP: [206.188.198.66] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjA2LjE4OC4xOTguNjYgPT4gMTI3MTY4\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24586 invoked from network); 25 Apr 2012 18:12:14 -0000 Received: from omr1pod1.networksolutionsemail.com (HELO omr1pod1.networksolutionsemail.com) (206.188.198.66) by server-16.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Apr 2012 18:12:14 -0000 Received: from mail.networksolutionsemail.com (mailpod1.networksolutionsemail.com [206.188.198.65]) by omr1pod1.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q3PICC4N011784 for ; Wed, 25 Apr 2012 14:12:13 -0400 X-Authenticated-IP: 206.188.198.65 Received: from [206.188.198.65] ([206.188.198.65:47064] helo=oxapp3pod1.mgt.hosting.qts.netsol.com) by cm-omr3pod1 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTP id 28/B0-00981-C7E389F4; Wed, 25 Apr 2012 14:12:12 -0400 Date: Wed, 25 Apr 2012 14:12:12 -0400 (EDT) From: David Hout To: xen-api@lists.xen.org Message-ID: <644653400.127753.1335377532834.JavaMail.vpopmail@mail.sequenciainc.com> MIME-Version: 1.0 X-Priority: 3 Importance: Medium X-Mailer: Open-Xchange Mailer v6.20.1-Rev8 Subject: [Xen-API] empty template list X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: David Hout List-Id: Discussion of API issues surrounding Xen List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7407320820736528782==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============7407320820736528782== Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Hi,

 

I've been working to get a Kronos XCP installation running on Debian SID.  I started out using the instructions here (http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution) and then once I got down the road far enough I used the instructions in /usr/share/doc/xcp-xapi/README.Debian.gz on the server itself.

 

I think I'm very close but my issue at the moment is I can't see any templates.

 

xe template-list returns nothing whatsoever.

 

I went back through the archives and saw a similar problem posted on December 19 but didn't see any resolution.

 

Can anybody help?

 

Thanks,

 

Dave

 

 

--===============7407320820736528782== 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 --===============7407320820736528782==-- From xen-api-bounces@lists.xen.org Thu Apr 26 12:45:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 26 Apr 2012 12:45: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 1SNO44-0007o8-0E; Thu, 26 Apr 2012 12:44:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNO42-0007nm-0q for xen-api@lists.xen.org; Thu, 26 Apr 2012 12:44:50 +0000 Received: from [85.158.138.51:49913] by server-9.bemta-3.messagelabs.com id 73/A0-26691-143499F4; Thu, 26 Apr 2012 12:44:49 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1335444287!23952648!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21440 invoked from network); 26 Apr 2012 12:44:48 -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 Apr 2012 12:44:48 -0000 Received: by bkty15 with SMTP id y15so1113706bkt.32 for ; Thu, 26 Apr 2012 05:44:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=fIFltkWYN4/1trFXAlyENA0h3Ynqpt38Tkp0GsyVpiQ=; b=jMR1ltFF6jC4FJwIDB7hpjSZIVbEf+/9cJaZEECJyYIgP5LP0cOAuA9pTtX8sgATtp 3HV1s6Ux3ZaNZpKtnDL9hZp6wX4+4nwDcPKrEMi1lt3WhUFtTQgLthLyoWHmPU3463rR div1PssSI9mVTP+4WpNe2yc0Kpbqk1vqWZtiu7h7bGja8I73xtmos4By0XAJLPt0omK2 K/pp36eXBN0oQkJAA8Gq2hu3gBLwX2Or+8JNs5Tzu3x/Daioe7zal9x67ucrYh2vYxeJ jA5zZlvWPJKrEViuFqDM4Q0JZer83O9cjn+ubNNUmwnAoqZ1UrdHIW8jh32AhVYwigFU WHFQ== Received: by 10.205.133.11 with SMTP id hw11mr2292503bkc.12.1335444287556; Thu, 26 Apr 2012 05:44:47 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id e20sm5453244bkv.10.2012.04.26.05.44.45 (version=SSLv3 cipher=OTHER); Thu, 26 Apr 2012 05:44:46 -0700 (PDT) Message-ID: <4F99433C.8040505@xen.org> Date: Thu, 26 Apr 2012 13:44:44 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 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] Changes to mailing lists (i.e. archiving of old lists) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Development and user list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3352025008965793947==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3352025008965793947== Content-Type: multipart/alternative; boundary="------------010406080209060802050908" This is a multi-part message in MIME format. --------------010406080209060802050908 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi everybody, I have archived a number of mailing lists that have been inactive, because a) they have fulfilled their purpose (i.e. the project for which they were created was completed or archived) b) they have been inactive for a year c) the discussion related to these are now happening elsewhere (e.g. on xen-devel) What does archiving mean: * I moved the list to the Archived section of http://lists.xen.org/ * I moved the list into emergency moderation (every post will be moderated) and new user * I removed the list from http://lists.xen.org/cgi-bin/mailman/listinfo The lists that were archived are: xen-bugs, xen-cim, xen-introspect, xen-tools, xen-ia64-devel, xen-research, xen-japanese. I have hidden a numer of other lists, hidden is like archived except that I have not listed them on http://lists.xen.org/ - in other words, the lists are still there, but they are not referenced. These were: ova-devel, xen-merge, xm-test-changelog, xm-test-devel & xen-community This should make finding the right xen list much easier and be less confusing to newcomers. Please let me know, if there are any objections. Regards Lars --------------010406080209060802050908 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi everybody,

I have archived a number of mailing lists that have been inactive, because
a) they have fulfilled their purpose (i.e. the project for which they were created was completed or archived)
b) they have been inactive for a year
c) the discussion related to these are now happening elsewhere (e.g. on xen-devel)

What does archiving mean:

The lists that were archived are: xen-bugs, xen-cim, xen-introspect, xen-tools, xen-ia64-devel, xen-research, xen-japanese.

I have hidden a numer of other lists, hidden is like archived except that I have not listed them on http://lists.xen.org/ - in other words, the lists are still there, but they are not referenced. These were: ova-devel, xen-merge, xm-test-changelog, xm-test-devel & xen-community

This should make finding the right xen list much easier and be less confusing to newcomers. Please let me know, if there are any objections.

Regards
Lars
--------------010406080209060802050908-- --===============3352025008965793947== 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 --===============3352025008965793947==-- From xen-api-bounces@lists.xen.org Thu Apr 26 12:45:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Thu, 26 Apr 2012 12:45: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 1SNO44-0007o8-0E; Thu, 26 Apr 2012 12:44:52 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNO42-0007nm-0q for xen-api@lists.xen.org; Thu, 26 Apr 2012 12:44:50 +0000 Received: from [85.158.138.51:49913] by server-9.bemta-3.messagelabs.com id 73/A0-26691-143499F4; Thu, 26 Apr 2012 12:44:49 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-174.messagelabs.com!1335444287!23952648!1 X-Originating-IP: [209.85.214.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21440 invoked from network); 26 Apr 2012 12:44:48 -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 Apr 2012 12:44:48 -0000 Received: by bkty15 with SMTP id y15so1113706bkt.32 for ; Thu, 26 Apr 2012 05:44:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=fIFltkWYN4/1trFXAlyENA0h3Ynqpt38Tkp0GsyVpiQ=; b=jMR1ltFF6jC4FJwIDB7hpjSZIVbEf+/9cJaZEECJyYIgP5LP0cOAuA9pTtX8sgATtp 3HV1s6Ux3ZaNZpKtnDL9hZp6wX4+4nwDcPKrEMi1lt3WhUFtTQgLthLyoWHmPU3463rR div1PssSI9mVTP+4WpNe2yc0Kpbqk1vqWZtiu7h7bGja8I73xtmos4By0XAJLPt0omK2 K/pp36eXBN0oQkJAA8Gq2hu3gBLwX2Or+8JNs5Tzu3x/Daioe7zal9x67ucrYh2vYxeJ jA5zZlvWPJKrEViuFqDM4Q0JZer83O9cjn+ubNNUmwnAoqZ1UrdHIW8jh32AhVYwigFU WHFQ== Received: by 10.205.133.11 with SMTP id hw11mr2292503bkc.12.1335444287556; Thu, 26 Apr 2012 05:44:47 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id e20sm5453244bkv.10.2012.04.26.05.44.45 (version=SSLv3 cipher=OTHER); Thu, 26 Apr 2012 05:44:46 -0700 (PDT) Message-ID: <4F99433C.8040505@xen.org> Date: Thu, 26 Apr 2012 13:44:44 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 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] Changes to mailing lists (i.e. archiving of old lists) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Development and user list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3352025008965793947==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============3352025008965793947== Content-Type: multipart/alternative; boundary="------------010406080209060802050908" This is a multi-part message in MIME format. --------------010406080209060802050908 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi everybody, I have archived a number of mailing lists that have been inactive, because a) they have fulfilled their purpose (i.e. the project for which they were created was completed or archived) b) they have been inactive for a year c) the discussion related to these are now happening elsewhere (e.g. on xen-devel) What does archiving mean: * I moved the list to the Archived section of http://lists.xen.org/ * I moved the list into emergency moderation (every post will be moderated) and new user * I removed the list from http://lists.xen.org/cgi-bin/mailman/listinfo The lists that were archived are: xen-bugs, xen-cim, xen-introspect, xen-tools, xen-ia64-devel, xen-research, xen-japanese. I have hidden a numer of other lists, hidden is like archived except that I have not listed them on http://lists.xen.org/ - in other words, the lists are still there, but they are not referenced. These were: ova-devel, xen-merge, xm-test-changelog, xm-test-devel & xen-community This should make finding the right xen list much easier and be less confusing to newcomers. Please let me know, if there are any objections. Regards Lars --------------010406080209060802050908 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi everybody,

I have archived a number of mailing lists that have been inactive, because
a) they have fulfilled their purpose (i.e. the project for which they were created was completed or archived)
b) they have been inactive for a year
c) the discussion related to these are now happening elsewhere (e.g. on xen-devel)

What does archiving mean:

The lists that were archived are: xen-bugs, xen-cim, xen-introspect, xen-tools, xen-ia64-devel, xen-research, xen-japanese.

I have hidden a numer of other lists, hidden is like archived except that I have not listed them on http://lists.xen.org/ - in other words, the lists are still there, but they are not referenced. These were: ova-devel, xen-merge, xm-test-changelog, xm-test-devel & xen-community

This should make finding the right xen list much easier and be less confusing to newcomers. Please let me know, if there are any objections.

Regards
Lars
--------------010406080209060802050908-- --===============3352025008965793947== 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 --===============3352025008965793947==-- From xen-api-bounces@lists.xen.org Fri Apr 27 12:48:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 27 Apr 2012 12:48: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 1SNkbA-0008VJ-1n; Fri, 27 Apr 2012 12:48:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNkb8-0008V8-Ko for xen-api@lists.xensource.com; Fri, 27 Apr 2012 12:48:30 +0000 Received: from [85.158.138.51:60574] by server-3.bemta-3.messagelabs.com id 67/27-04048-D959A9F4; Fri, 27 Apr 2012 12:48:29 +0000 X-Env-Sender: todd.deshane.xen@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1335530907!23993591!1 X-Originating-IP: [209.85.160.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 21009 invoked from network); 27 Apr 2012 12:48:29 -0000 Received: from mail-gy0-f171.google.com (HELO mail-gy0-f171.google.com) (209.85.160.171) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2012 12:48:29 -0000 Received: by ghbz17 with SMTP id z17so385166ghb.30 for ; Fri, 27 Apr 2012 05:48:27 -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=0xTP8riZSZ/UMIN+Nm0Hdg80aUGjF3zvD69WqlkEwUM=; b=e6G6+R8mJ3bFmXGLjyjisLVDnpiE6vzDt4BlQasG4fxUx9u/plu43+yO/XZTeNgV4U LbG9hcUPjr4iNo+dkhrnyd6f9TFkOwT90nwBRlkVPrNJM8qF7mpK6SHSB0hwMbm/y9iw bcOG2WW2an9TZewoatBPvJBhaWMaAaBriJn1+aYVH79cs1KXddWmejmDT/yivTMP6NJF AJH7z5N5rInaldavwBe1sORnKks/bj0eFRQ5KhhKAYoUBsFJbDHBDCY0+wXTnhuehhPd ufJW1NZnKAlFyADwjfGw0F6Z6wtyKVSFVL24c06w6+NJkvonwbyCIbqZcD2cEv2Kfimu 3BOQ== Received: by 10.50.76.136 with SMTP id k8mr2256147igw.2.1335530907381; Fri, 27 Apr 2012 05:48:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.20.66 with HTTP; Fri, 27 Apr 2012 05:48:07 -0700 (PDT) In-Reply-To: <557004149BCB6446BE48D5BA5F8C9D68DF918FE4FF@MAIL.corp.cht.com.tw> References: <557004149BCB6446BE48D5BA5F8C9D68DF918FE4FF@MAIL.corp.cht.com.tw> From: Todd Deshane Date: Fri, 27 Apr 2012 08:48:07 -0400 X-Google-Sender-Auth: W_9JWDBrAcl2UhfhQt6Sd5A3Ey0 Message-ID: To: =?Big5?B?tsDEbb33?= Cc: "xen-users@lists.xen.org" , xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] What's the different between XAPI and Xenopsd ? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VGhpcyBpcyBhIGJldHRlciBxdWVzdGlvbiBmb3IgdGhlIHhlbi1hcGkgbWFpbGluZyBsaXN0LiBB ZGRpbmcgdG8gdGhlIENDLgoKT24gVGh1LCBBcHIgMjYsIDIwMTIgYXQgMTA6NTggQU0sILbAxG29 9yA8dHVyaW5nQGNodC5jb20udHc+IHdyb3RlOgo+IEhpIGV2ZXJ5b25lLAo+Cj4KPgo+IEkgaGF2 ZSBzb21lIHF1ZXN0aW9uIGFib3V0IHRoZSBYZW5vcHNkLgo+Cj4gSaGmdmUgcmVhZCB0aGUgd2lr aSBkb2N1bWVudCBidXQgY2Fubm90IHVuZGVyc3RhbmQgd2hlcmUgdG8gdXNlIGl0LAo+Cj4gSXMg dGhpcyBkaWZmZXJlbnQgd2l0aCBYQVBJID8gV2hhdKGmcyB0aGUgbWFpbiB3b3JrIGZvcj8KPgo+ Cj4KPiBDYW4gYW55b25lIGRlc2NyaWJlIGl0IG1vcmUgY2xlYXJseSBhYm91dCBpdD8KPgo+IFRo YW5rcyBhIGxvdCEhCj4KPgo+Cj4KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwo+IFhlbi11c2VycyBtYWlsaW5nIGxpc3QKPiBYZW4tdXNlcnNAbGlzdHMu eGVuLm9yZwo+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2VycwoKCgotLSAKVG9kZCBEZXNo YW5lCmh0dHA6Ly93d3cubGlua2VkaW4uY29tL2luL2Rlc2hhbnRtCmh0dHA6Ly9ibG9nLnhlbi5v cmcvCmh0dHA6Ly93aWtpLnhlbi5vcmcvCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5v cmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Fri Apr 27 12:48:41 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 27 Apr 2012 12:48: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 1SNkbA-0008VJ-1n; Fri, 27 Apr 2012 12:48:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNkb8-0008V8-Ko for xen-api@lists.xensource.com; Fri, 27 Apr 2012 12:48:30 +0000 Received: from [85.158.138.51:60574] by server-3.bemta-3.messagelabs.com id 67/27-04048-D959A9F4; Fri, 27 Apr 2012 12:48:29 +0000 X-Env-Sender: todd.deshane.xen@gmail.com X-Msg-Ref: server-16.tower-174.messagelabs.com!1335530907!23993591!1 X-Originating-IP: [209.85.160.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 21009 invoked from network); 27 Apr 2012 12:48:29 -0000 Received: from mail-gy0-f171.google.com (HELO mail-gy0-f171.google.com) (209.85.160.171) by server-16.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2012 12:48:29 -0000 Received: by ghbz17 with SMTP id z17so385166ghb.30 for ; Fri, 27 Apr 2012 05:48:27 -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=0xTP8riZSZ/UMIN+Nm0Hdg80aUGjF3zvD69WqlkEwUM=; b=e6G6+R8mJ3bFmXGLjyjisLVDnpiE6vzDt4BlQasG4fxUx9u/plu43+yO/XZTeNgV4U LbG9hcUPjr4iNo+dkhrnyd6f9TFkOwT90nwBRlkVPrNJM8qF7mpK6SHSB0hwMbm/y9iw bcOG2WW2an9TZewoatBPvJBhaWMaAaBriJn1+aYVH79cs1KXddWmejmDT/yivTMP6NJF AJH7z5N5rInaldavwBe1sORnKks/bj0eFRQ5KhhKAYoUBsFJbDHBDCY0+wXTnhuehhPd ufJW1NZnKAlFyADwjfGw0F6Z6wtyKVSFVL24c06w6+NJkvonwbyCIbqZcD2cEv2Kfimu 3BOQ== Received: by 10.50.76.136 with SMTP id k8mr2256147igw.2.1335530907381; Fri, 27 Apr 2012 05:48:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.20.66 with HTTP; Fri, 27 Apr 2012 05:48:07 -0700 (PDT) In-Reply-To: <557004149BCB6446BE48D5BA5F8C9D68DF918FE4FF@MAIL.corp.cht.com.tw> References: <557004149BCB6446BE48D5BA5F8C9D68DF918FE4FF@MAIL.corp.cht.com.tw> From: Todd Deshane Date: Fri, 27 Apr 2012 08:48:07 -0400 X-Google-Sender-Auth: W_9JWDBrAcl2UhfhQt6Sd5A3Ey0 Message-ID: To: =?Big5?B?tsDEbb33?= Cc: "xen-users@lists.xen.org" , xen-api@lists.xensource.com Subject: Re: [Xen-API] [Xen-users] What's the different between XAPI and Xenopsd ? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: base64 Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org VGhpcyBpcyBhIGJldHRlciBxdWVzdGlvbiBmb3IgdGhlIHhlbi1hcGkgbWFpbGluZyBsaXN0LiBB ZGRpbmcgdG8gdGhlIENDLgoKT24gVGh1LCBBcHIgMjYsIDIwMTIgYXQgMTA6NTggQU0sILbAxG29 9yA8dHVyaW5nQGNodC5jb20udHc+IHdyb3RlOgo+IEhpIGV2ZXJ5b25lLAo+Cj4KPgo+IEkgaGF2 ZSBzb21lIHF1ZXN0aW9uIGFib3V0IHRoZSBYZW5vcHNkLgo+Cj4gSaGmdmUgcmVhZCB0aGUgd2lr aSBkb2N1bWVudCBidXQgY2Fubm90IHVuZGVyc3RhbmQgd2hlcmUgdG8gdXNlIGl0LAo+Cj4gSXMg dGhpcyBkaWZmZXJlbnQgd2l0aCBYQVBJID8gV2hhdKGmcyB0aGUgbWFpbiB3b3JrIGZvcj8KPgo+ Cj4KPiBDYW4gYW55b25lIGRlc2NyaWJlIGl0IG1vcmUgY2xlYXJseSBhYm91dCBpdD8KPgo+IFRo YW5rcyBhIGxvdCEhCj4KPgo+Cj4KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwo+IFhlbi11c2VycyBtYWlsaW5nIGxpc3QKPiBYZW4tdXNlcnNAbGlzdHMu eGVuLm9yZwo+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hlbi11c2VycwoKCgotLSAKVG9kZCBEZXNo YW5lCmh0dHA6Ly93d3cubGlua2VkaW4uY29tL2luL2Rlc2hhbnRtCmh0dHA6Ly9ibG9nLnhlbi5v cmcvCmh0dHA6Ly93aWtpLnhlbi5vcmcvCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpYZW4tYXBpIG1haWxpbmcgbGlzdApYZW4tYXBpQGxpc3RzLnhlbi5v cmcKaHR0cDovL2xpc3RzLnhlbi5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3hlbi1hcGkK From xen-api-bounces@lists.xen.org Fri Apr 27 13:47:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 27 Apr 2012 13:47: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 1SNlVd-00017H-B8; Fri, 27 Apr 2012 13:46:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNlVb-00017C-Sw for xen-api@lists.xen.org; Fri, 27 Apr 2012 13:46:52 +0000 Received: from [85.158.139.83:42784] by server-5.bemta-5.messagelabs.com id FE/D7-13566-A43AA9F4; Fri, 27 Apr 2012 13:46:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1335534410!21934119!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 32390 invoked from network); 27 Apr 2012 13:46:50 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2012 13:46:50 -0000 Received: by bkty15 with SMTP id y15so626148bkt.32 for ; Fri, 27 Apr 2012 06:46:49 -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=kx63W0u5AJVLnLGTgGqV30GR9lP27qFyH22wNDMDRjo=; b=AFudVJURbfq7ec3se9r6wah/8vlYw2a8gI5TuO38DLK4mB0UJAe08sdfTdIQ0iZ0N9 FF7r+iLQGWzGRtpuTYIvi82NPynW+Eh+QWDoeTZyi10tglOnbGwo9ieWVdSyGtv1tnn7 CKoiNOhdASOXKP1dll1/GpHORcamm6/fdgDMSqAc0LsRvrW5biq++9X/cuI4Y0OsdiNg oztsSf7l4KeFUDKJQmp9Xd/pfqu0H01wlV3PsMMiKR8xKanCLzGVtcdOkfpkveWnqH5o h6wU4zq4GRo746mRcrG88bCcI/4WjljdKkY9bVd8WyZN2xRO7C6/gnMTUp2/pjrq4P6t xMuA== Received: by 10.205.124.9 with SMTP id gm9mr1217034bkc.29.1335534409806; Fri, 27 Apr 2012 06:46:49 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id c4sm11843910bkh.0.2012.04.27.06.46.45 (version=SSLv3 cipher=OTHER); Fri, 27 Apr 2012 06:46:48 -0700 (PDT) Message-ID: <4F9AA344.8080706@xen.org> Date: Fri, 27 Apr 2012 14:46:44 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] XCP Toolstack Improvements @ Ubuntu Developer Summit on 2012-05-07 16:15-17:00 in Grand Ballroom B X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Development list for XCP and Xen API 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 See http://summit.ubuntu.com/uds-q/meeting/20367/servercloud-q-xcp/ _______________________________________________ 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 Apr 27 13:47:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 27 Apr 2012 13:47: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 1SNlVd-00017H-B8; Fri, 27 Apr 2012 13:46:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNlVb-00017C-Sw for xen-api@lists.xen.org; Fri, 27 Apr 2012 13:46:52 +0000 Received: from [85.158.139.83:42784] by server-5.bemta-5.messagelabs.com id FE/D7-13566-A43AA9F4; Fri, 27 Apr 2012 13:46:50 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-182.messagelabs.com!1335534410!21934119!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 32390 invoked from network); 27 Apr 2012 13:46:50 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-6.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2012 13:46:50 -0000 Received: by bkty15 with SMTP id y15so626148bkt.32 for ; Fri, 27 Apr 2012 06:46:49 -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=kx63W0u5AJVLnLGTgGqV30GR9lP27qFyH22wNDMDRjo=; b=AFudVJURbfq7ec3se9r6wah/8vlYw2a8gI5TuO38DLK4mB0UJAe08sdfTdIQ0iZ0N9 FF7r+iLQGWzGRtpuTYIvi82NPynW+Eh+QWDoeTZyi10tglOnbGwo9ieWVdSyGtv1tnn7 CKoiNOhdASOXKP1dll1/GpHORcamm6/fdgDMSqAc0LsRvrW5biq++9X/cuI4Y0OsdiNg oztsSf7l4KeFUDKJQmp9Xd/pfqu0H01wlV3PsMMiKR8xKanCLzGVtcdOkfpkveWnqH5o h6wU4zq4GRo746mRcrG88bCcI/4WjljdKkY9bVd8WyZN2xRO7C6/gnMTUp2/pjrq4P6t xMuA== Received: by 10.205.124.9 with SMTP id gm9mr1217034bkc.29.1335534409806; Fri, 27 Apr 2012 06:46:49 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id c4sm11843910bkh.0.2012.04.27.06.46.45 (version=SSLv3 cipher=OTHER); Fri, 27 Apr 2012 06:46:48 -0700 (PDT) Message-ID: <4F9AA344.8080706@xen.org> Date: Fri, 27 Apr 2012 14:46:44 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] XCP Toolstack Improvements @ Ubuntu Developer Summit on 2012-05-07 16:15-17:00 in Grand Ballroom B X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Development list for XCP and Xen API 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 See http://summit.ubuntu.com/uds-q/meeting/20367/servercloud-q-xcp/ _______________________________________________ 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 Apr 27 14:08:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 27 Apr 2012 14:08: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 1SNlq1-0001Or-B0; Fri, 27 Apr 2012 14:07:57 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNlpz-0001Ol-RH for xen-api@lists.xensource.com; Fri, 27 Apr 2012 14:07:56 +0000 Received: from [193.109.254.147:5056] by server-12.bemta-14.messagelabs.com id 59/43-05898-B38AA9F4; Fri, 27 Apr 2012 14:07:55 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1335535673!6670529!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5Njc0OQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24304 invoked from network); 27 Apr 2012 14:07:54 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2012 14:07:54 -0000 X-IronPort-AV: E=Sophos;i="4.75,491,1330905600"; d="scan'208";a="12179732" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 27 Apr 2012 14:07:40 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Fri, 27 Apr 2012 15:07:40 +0100 From: Dave Scott To: 'Todd Deshane' , =?gb2312?B?/FOrSd14?= Date: Fri, 27 Apr 2012 15:07:39 +0100 Thread-Topic: [Xen-users] What's the different between XAPI and Xenopsd ? Thread-Index: Ac0kdAugTQr7phpJTaCEd7vYXRDzTwABpXfw Message-ID: <81A73678E76EA642801C8F2E4823AD21DA9E1FD5BE@LONPMAILBOX01.citrite.net> References: <557004149BCB6446BE48D5BA5F8C9D68DF918FE4FF@MAIL.corp.cht.com.tw> 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-users@lists.xen.org" , "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [Xen-users] What's the different between XAPI and Xenopsd ? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0901057613359734920==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0901057613359734920== Content-Language: en-US Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksDQoNCkF0IHRoZSBtb21lbnQgeGFwaSBpcyBxdWl0ZSBtb25vbGl0aGljIGFuZCB3ZSB3YW50 ZWQgdG8gbWFrZSBpdCBlYXNpZXIgdG8gbWFpbnRhaW4gYnkgc3BsaXR0aW5nIGl0IHVwIGludG8g c2V2ZXJhbCBzbWFsbGVyIHNlcnZpY2VzLg0KDQpUaGUgbmV3IHhlbm9wc2QgaXMgdGhlICJkb21h aW4gbWFuYWdlciIgcGFydCBvZiB4YXBpLiBUaGlzIGlzIG5vdyB3aGF0IGhhcHBlbnMgd2hlbiBh IHVzZXIgc3RhcnRzIGEgVk06DQoNCjEuIGNsaWVudCBzZW5kcyB0aGUgWGVuQVBJIFZNLnN0YXJ0 IGNhbGwgdG8geGFwaQ0KMi4geGFwaSBkZWNpZGVzIHdoaWNoIGhvc3QgdG8gc3RhcnQgdGhlIFZN IG9uDQozLiB4YXBpIGZvcndhcmRzIHRoZSBjYWxsIHRvIHRoZSB4YXBpIG9uIHRoZSAic2xhdmUi DQo0LiB0aGUgc2xhdmUgeGFwaSBnaXZlcyB0aGUgVk0gY29uZmlndXJhdGlvbiB0byB4ZW5vcHNk DQo1LiB0aGUgc2xhdmUgeGFwaSB0ZWxscyB4ZW5vcHNkIHRvIHN0YXJ0IHRoZSBWTSBhbmQgbG9v ayBhZnRlciBpdC4NCg0KTGF0ZXIgaWYgdGhlIHVzZXIgcmVib290cyB0aGUgVk06DQoNCjEuIHhl bm9wc2Qgbm90aWNlcyB0aGUgZG9tYWluIG5lZWRzIHRvIGJlIHJlc3RhcnRlZA0KMi4geGVub3Bz ZCByZXN0YXJ0cyB0aGUgVk0NCjMuIHhhcGkgcmVjZWl2ZXMgYW4gZXZlbnQgZnJvbSB4ZW5vcHNk IHRlbGxpbmcgaXQgdGhhdCB0aGUgVk0gaGFzIGNoYW5nZWQNCjQuIHhhcGkgYXNrcyB4ZW5vcHNk IGZvciB0aGUgY3VycmVudCBWTSBzdGF0ZQ0KNS4geGFwaSB1cGRhdGVzIHRoZSBwb29sIGRhdGFi YXNlDQoNClNvIHhlbm9wc2QgaXMgcmVhbGx5IGFuIGludGVybmFsIHNlcnZpY2UuDQoNCkFwYXJ0 IGZyb20gYmVpbmcgZWFzaWVyIHRvIG1haW50YWluIGl0Og0KDQoxLiB3aWxsIGJlIGVhc2llciB0 byBpbnRlZ3JhdGUgd2l0aCBsaWJ4bCBiZWNhdXNlIGFsbCB0aGUgbG93LWxldmVsIHhlbiBzdHVm ZiBpcyBjb250YWluZWQgd2l0aGluIGEgImJhY2tlbmQiIHBsdWdpbg0KDQoyLiBpbmNsdWRlcyBh ICJtb2NrIiBiYWNrZW5kIHdoaWNoIGNhbiBiZSB1c2VkIHRvIHNpbXVsYXRlIGEgaG9zdCwgdXNl ZnVsIGZvciB0ZXN0aW5nDQoNCjMuIGl0IGlzIGF3YXJlIG9mIGRyaXZlciBkb21haW5zIGkuZS4g dGhhdCBiYWNrZW5kcyBjYW4gYmUgaW4gZG9tYWlucyBvdGhlciB0aGFuIGRvbWFpbiB6ZXJvDQoN CjQuIGlzIG11Y2ggbW9yZSBjbGVhbmx5IG11bHRpdGhyZWFkZWQgKGFuZCB3aWxsIGhvcGVmdWxs eSBiZSBjb252ZXJ0ZWQgdG8gdXNlIHRoZSAibHd0IiBtb25hZGljIGNvbmN1cnJlbmN5IGxpYnJh cnkgaW4gdGhlIGZ1dHVyZSkNCg0KSFRILA0KRGF2ZQ0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn ZS0tLS0tDQo+IEZyb206IHRvZGQuZGVzaGFuZS54ZW5AZ21haWwuY29tIFttYWlsdG86dG9kZC5k ZXNoYW5lLnhlbkBnbWFpbC5jb21dIE9uDQo+IEJlaGFsZiBPZiBUb2RkIERlc2hhbmUNCj4gU2Vu dDogMjcgQXByaWwgMjAxMiAxMzo0OA0KPiBUbzog/FOrSd14DQo+IENjOiB4ZW4tdXNlcnNAbGlz dHMueGVuLm9yZzsgeGVuLWFwaUBsaXN0cy54ZW5zb3VyY2UuY29tOyBEYXZlIFNjb3R0DQo+IFN1 YmplY3Q6IFJlOiBbWGVuLXVzZXJzXSBXaGF0J3MgdGhlIGRpZmZlcmVudCBiZXR3ZWVuIFhBUEkg YW5kIFhlbm9wc2QgPw0KPiANCj4gVGhpcyBpcyBhIGJldHRlciBxdWVzdGlvbiBmb3IgdGhlIHhl bi1hcGkgbWFpbGluZyBsaXN0LiBBZGRpbmcgdG8gdGhlDQo+IENDLg0KPiANCj4gT24gVGh1LCBB cHIgMjYsIDIwMTIgYXQgMTA6NTggQU0sIPxTq0ndeCA8dHVyaW5nQGNodC5jb20udHc+IHdyb3Rl Og0KPiA+IEhpIGV2ZXJ5b25lLA0KPiA+DQo+ID4NCj4gPg0KPiA+IEkgaGF2ZSBzb21lIHF1ZXN0 aW9uIGFib3V0IHRoZSBYZW5vcHNkLg0KPiA+DQo+ID4gSaGvdmUgcmVhZCB0aGUgd2lraSBkb2N1 bWVudCBidXQgY2Fubm90IHVuZGVyc3RhbmQgd2hlcmUgdG8gdXNlIGl0LA0KPiA+DQo+ID4gSXMg dGhpcyBkaWZmZXJlbnQgd2l0aCBYQVBJID8gV2hhdKGvcyB0aGUgbWFpbiB3b3JrIGZvcj8NCj4g Pg0KPiA+DQo+ID4NCj4gPiBDYW4gYW55b25lIGRlc2NyaWJlIGl0IG1vcmUgY2xlYXJseSBhYm91 dCBpdD8NCj4gPg0KPiA+IFRoYW5rcyBhIGxvdCEhDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPiBf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IFhlbi11 c2VycyBtYWlsaW5nIGxpc3QNCj4gPiBYZW4tdXNlcnNAbGlzdHMueGVuLm9yZw0KPiA+IGh0dHA6 Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw0KPiANCj4gDQo+IA0KPiAtLQ0KPiBUb2RkIERlc2hh bmUNCj4gaHR0cDovL3d3dy5saW5rZWRpbi5jb20vaW4vZGVzaGFudG0NCj4gaHR0cDovL2Jsb2cu eGVuLm9yZy8NCj4gaHR0cDovL3dpa2kueGVuLm9yZy8NCg== --===============0901057613359734920== 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 --===============0901057613359734920==-- From xen-api-bounces@lists.xen.org Fri Apr 27 14:08:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 27 Apr 2012 14:08: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 1SNlq1-0001Or-B0; Fri, 27 Apr 2012 14:07:57 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNlpz-0001Ol-RH for xen-api@lists.xensource.com; Fri, 27 Apr 2012 14:07:56 +0000 Received: from [193.109.254.147:5056] by server-12.bemta-14.messagelabs.com id 59/43-05898-B38AA9F4; Fri, 27 Apr 2012 14:07:55 +0000 X-Env-Sender: Dave.Scott@eu.citrix.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1335535673!6670529!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5Njc0OQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24304 invoked from network); 27 Apr 2012 14:07:54 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (62.200.22.115) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2012 14:07:54 -0000 X-IronPort-AV: E=Sophos;i="4.75,491,1330905600"; d="scan'208";a="12179732" Received: from lonpmailmx02.citrite.net ([10.30.203.163]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 27 Apr 2012 14:07:40 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX02.citrite.net ([10.30.203.163]) with mapi; Fri, 27 Apr 2012 15:07:40 +0100 From: Dave Scott To: 'Todd Deshane' , =?gb2312?B?/FOrSd14?= Date: Fri, 27 Apr 2012 15:07:39 +0100 Thread-Topic: [Xen-users] What's the different between XAPI and Xenopsd ? Thread-Index: Ac0kdAugTQr7phpJTaCEd7vYXRDzTwABpXfw Message-ID: <81A73678E76EA642801C8F2E4823AD21DA9E1FD5BE@LONPMAILBOX01.citrite.net> References: <557004149BCB6446BE48D5BA5F8C9D68DF918FE4FF@MAIL.corp.cht.com.tw> 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-users@lists.xen.org" , "xen-api@lists.xensource.com" Subject: Re: [Xen-API] [Xen-users] What's the different between XAPI and Xenopsd ? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0901057613359734920==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org --===============0901057613359734920== Content-Language: en-US Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksDQoNCkF0IHRoZSBtb21lbnQgeGFwaSBpcyBxdWl0ZSBtb25vbGl0aGljIGFuZCB3ZSB3YW50 ZWQgdG8gbWFrZSBpdCBlYXNpZXIgdG8gbWFpbnRhaW4gYnkgc3BsaXR0aW5nIGl0IHVwIGludG8g c2V2ZXJhbCBzbWFsbGVyIHNlcnZpY2VzLg0KDQpUaGUgbmV3IHhlbm9wc2QgaXMgdGhlICJkb21h aW4gbWFuYWdlciIgcGFydCBvZiB4YXBpLiBUaGlzIGlzIG5vdyB3aGF0IGhhcHBlbnMgd2hlbiBh IHVzZXIgc3RhcnRzIGEgVk06DQoNCjEuIGNsaWVudCBzZW5kcyB0aGUgWGVuQVBJIFZNLnN0YXJ0 IGNhbGwgdG8geGFwaQ0KMi4geGFwaSBkZWNpZGVzIHdoaWNoIGhvc3QgdG8gc3RhcnQgdGhlIFZN IG9uDQozLiB4YXBpIGZvcndhcmRzIHRoZSBjYWxsIHRvIHRoZSB4YXBpIG9uIHRoZSAic2xhdmUi DQo0LiB0aGUgc2xhdmUgeGFwaSBnaXZlcyB0aGUgVk0gY29uZmlndXJhdGlvbiB0byB4ZW5vcHNk DQo1LiB0aGUgc2xhdmUgeGFwaSB0ZWxscyB4ZW5vcHNkIHRvIHN0YXJ0IHRoZSBWTSBhbmQgbG9v ayBhZnRlciBpdC4NCg0KTGF0ZXIgaWYgdGhlIHVzZXIgcmVib290cyB0aGUgVk06DQoNCjEuIHhl bm9wc2Qgbm90aWNlcyB0aGUgZG9tYWluIG5lZWRzIHRvIGJlIHJlc3RhcnRlZA0KMi4geGVub3Bz ZCByZXN0YXJ0cyB0aGUgVk0NCjMuIHhhcGkgcmVjZWl2ZXMgYW4gZXZlbnQgZnJvbSB4ZW5vcHNk IHRlbGxpbmcgaXQgdGhhdCB0aGUgVk0gaGFzIGNoYW5nZWQNCjQuIHhhcGkgYXNrcyB4ZW5vcHNk IGZvciB0aGUgY3VycmVudCBWTSBzdGF0ZQ0KNS4geGFwaSB1cGRhdGVzIHRoZSBwb29sIGRhdGFi YXNlDQoNClNvIHhlbm9wc2QgaXMgcmVhbGx5IGFuIGludGVybmFsIHNlcnZpY2UuDQoNCkFwYXJ0 IGZyb20gYmVpbmcgZWFzaWVyIHRvIG1haW50YWluIGl0Og0KDQoxLiB3aWxsIGJlIGVhc2llciB0 byBpbnRlZ3JhdGUgd2l0aCBsaWJ4bCBiZWNhdXNlIGFsbCB0aGUgbG93LWxldmVsIHhlbiBzdHVm ZiBpcyBjb250YWluZWQgd2l0aGluIGEgImJhY2tlbmQiIHBsdWdpbg0KDQoyLiBpbmNsdWRlcyBh ICJtb2NrIiBiYWNrZW5kIHdoaWNoIGNhbiBiZSB1c2VkIHRvIHNpbXVsYXRlIGEgaG9zdCwgdXNl ZnVsIGZvciB0ZXN0aW5nDQoNCjMuIGl0IGlzIGF3YXJlIG9mIGRyaXZlciBkb21haW5zIGkuZS4g dGhhdCBiYWNrZW5kcyBjYW4gYmUgaW4gZG9tYWlucyBvdGhlciB0aGFuIGRvbWFpbiB6ZXJvDQoN CjQuIGlzIG11Y2ggbW9yZSBjbGVhbmx5IG11bHRpdGhyZWFkZWQgKGFuZCB3aWxsIGhvcGVmdWxs eSBiZSBjb252ZXJ0ZWQgdG8gdXNlIHRoZSAibHd0IiBtb25hZGljIGNvbmN1cnJlbmN5IGxpYnJh cnkgaW4gdGhlIGZ1dHVyZSkNCg0KSFRILA0KRGF2ZQ0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn ZS0tLS0tDQo+IEZyb206IHRvZGQuZGVzaGFuZS54ZW5AZ21haWwuY29tIFttYWlsdG86dG9kZC5k ZXNoYW5lLnhlbkBnbWFpbC5jb21dIE9uDQo+IEJlaGFsZiBPZiBUb2RkIERlc2hhbmUNCj4gU2Vu dDogMjcgQXByaWwgMjAxMiAxMzo0OA0KPiBUbzog/FOrSd14DQo+IENjOiB4ZW4tdXNlcnNAbGlz dHMueGVuLm9yZzsgeGVuLWFwaUBsaXN0cy54ZW5zb3VyY2UuY29tOyBEYXZlIFNjb3R0DQo+IFN1 YmplY3Q6IFJlOiBbWGVuLXVzZXJzXSBXaGF0J3MgdGhlIGRpZmZlcmVudCBiZXR3ZWVuIFhBUEkg YW5kIFhlbm9wc2QgPw0KPiANCj4gVGhpcyBpcyBhIGJldHRlciBxdWVzdGlvbiBmb3IgdGhlIHhl bi1hcGkgbWFpbGluZyBsaXN0LiBBZGRpbmcgdG8gdGhlDQo+IENDLg0KPiANCj4gT24gVGh1LCBB cHIgMjYsIDIwMTIgYXQgMTA6NTggQU0sIPxTq0ndeCA8dHVyaW5nQGNodC5jb20udHc+IHdyb3Rl Og0KPiA+IEhpIGV2ZXJ5b25lLA0KPiA+DQo+ID4NCj4gPg0KPiA+IEkgaGF2ZSBzb21lIHF1ZXN0 aW9uIGFib3V0IHRoZSBYZW5vcHNkLg0KPiA+DQo+ID4gSaGvdmUgcmVhZCB0aGUgd2lraSBkb2N1 bWVudCBidXQgY2Fubm90IHVuZGVyc3RhbmQgd2hlcmUgdG8gdXNlIGl0LA0KPiA+DQo+ID4gSXMg dGhpcyBkaWZmZXJlbnQgd2l0aCBYQVBJID8gV2hhdKGvcyB0aGUgbWFpbiB3b3JrIGZvcj8NCj4g Pg0KPiA+DQo+ID4NCj4gPiBDYW4gYW55b25lIGRlc2NyaWJlIGl0IG1vcmUgY2xlYXJseSBhYm91 dCBpdD8NCj4gPg0KPiA+IFRoYW5rcyBhIGxvdCEhDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPiBf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+IFhlbi11 c2VycyBtYWlsaW5nIGxpc3QNCj4gPiBYZW4tdXNlcnNAbGlzdHMueGVuLm9yZw0KPiA+IGh0dHA6 Ly9saXN0cy54ZW4ub3JnL3hlbi11c2Vycw0KPiANCj4gDQo+IA0KPiAtLQ0KPiBUb2RkIERlc2hh bmUNCj4gaHR0cDovL3d3dy5saW5rZWRpbi5jb20vaW4vZGVzaGFudG0NCj4gaHR0cDovL2Jsb2cu eGVuLm9yZy8NCj4gaHR0cDovL3dpa2kueGVuLm9yZy8NCg== --===============0901057613359734920== 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 --===============0901057613359734920==-- From xen-api-bounces@lists.xen.org Fri Apr 27 21:41:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 27 Apr 2012 21:41:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNsuv-0000OR-A9; Fri, 27 Apr 2012 21:41:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNsuu-0000OL-Ax for xen-api@lists.xen.org; Fri, 27 Apr 2012 21:41:28 +0000 Received: from [85.158.143.99:60210] by server-1.bemta-4.messagelabs.com id 85/AB-20925-6821B9F4; Fri, 27 Apr 2012 21:41:26 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1335562884!25054825!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28892 invoked from network); 27 Apr 2012 21:41:24 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2012 21:41:24 -0000 Received: by wibhq7 with SMTP id hq7so844822wib.14 for ; Fri, 27 Apr 2012 14:41:23 -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=j+7nyrJBHo2v5TTe0Y3SMSfb6AT18gzwdiNNne3JFgs=; b=WxzTwSLdMi6/0uAbLby909BLL5DktvrK93KoVj/Uge0etBbMQbsShAkPTObIctshN4 9MKJDFt5EGgoHfxu9uRRblA11zQrUE7hZLQ2CggOYZuw0CJ26lck01RHn+Qcc2m69UWA DslMkBhDxAsRYQtS626LA6BQWzsrdgUGe9JEiCWwxT2L63uvX/K7l5S1QDRU4kjaMtWk JyHXhiFLmXiUGbgAV4SRF9PddFR/oz3yQRsCjewFZ6Bton4sXWvEfPnFyduDanQGqzvi W0ubXXLcnaOF9422AToxeIkY0gJWhKxr79ppNeW1V+HAdwKbRUaTXNfx6iP3JkqDCO/5 9HjA== Received: by 10.180.76.240 with SMTP id n16mr2261444wiw.10.1335562883531; Fri, 27 Apr 2012 14:41:23 -0700 (PDT) Received: from [192.168.1.234] (101-55-112-92.pool.ukrtel.net. [92.112.55.101]) by mx.google.com with ESMTPS id n20sm11906199wiw.5.2012.04.27.14.41.20 (version=SSLv3 cipher=OTHER); Fri, 27 Apr 2012 14:41:22 -0700 (PDT) Message-ID: <4F9B127B.1020307@gmail.com> Date: Sat, 28 Apr 2012 01:41:15 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <557004149BCB6446BE48D5BA5F8C9D68DF918FE4FF@MAIL.corp.cht.com.tw> <81A73678E76EA642801C8F2E4823AD21DA9E1FD5BE@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21DA9E1FD5BE@LONPMAILBOX01.citrite.net> Subject: Re: [Xen-API] [Xen-users] What's the different between XAPI and Xenopsd ? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2272756272518541670==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2272756272518541670== Content-Type: multipart/alternative; boundary="------------030906040405060900000906" This is a multi-part message in MIME format. --------------030906040405060900000906 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Wow, cool news. I've all time have troubles with xapi been 'low-level domain manager' as high-level same time (f.e. if xapi have issues with space in dom0 due excessive logging, all operations stops, including domain reboot). If you did not already implement everything, would you like to add some way to get those notifications to be available to external subscriptors? I know about xapi events subscription, but xapi requirer master to be online and sometimes getting information directly is much more preferable. I know it all about hacking around xapi, but why not? On 27.04.2012 18:07, Dave Scott wrote: > Hi, > > At the moment xapi is quite monolithic and we wanted to make it easier to maintain by splitting it up into several smaller services. > > The new xenopsd is the "domain manager" part of xapi. This is now what happens when a user starts a VM: > > 1. client sends the XenAPI VM.start call to xapi > 2. xapi decides which host to start the VM on > 3. xapi forwards the call to the xapi on the "slave" > 4. the slave xapi gives the VM configuration to xenopsd > 5. the slave xapi tells xenopsd to start the VM and look after it. > > Later if the user reboots the VM: > > 1. xenopsd notices the domain needs to be restarted > 2. xenopsd restarts the VM > 3. xapi receives an event from xenopsd telling it that the VM has changed > 4. xapi asks xenopsd for the current VM state > 5. xapi updates the pool database > > So xenopsd is really an internal service. > > Apart from being easier to maintain it: > > 1. will be easier to integrate with libxl because all the low-level xen stuff is contained within a "backend" plugin > > 2. includes a "mock" backend which can be used to simulate a host, useful for testing > > 3. it is aware of driver domains i.e. that backends can be in domains other than domain zero > > 4. is much more cleanly multithreaded (and will hopefully be converted to use the "lwt" monadic concurrency library in the future) > > HTH, > Dave > >> -----Original Message----- >> From: todd.deshane.xen@gmail.com [mailto:todd.deshane.xen@gmail.com] On >> Behalf Of Todd Deshane >> Sent: 27 April 2012 13:48 >> To: ??? >> Cc: xen-users@lists.xen.org; xen-api@lists.xensource.com; Dave Scott >> Subject: Re: [Xen-users] What's the different between XAPI and Xenopsd ? >> >> This is a better question for the xen-api mailing list. Adding to the >> CC. >> >> On Thu, Apr 26, 2012 at 10:58 AM, ??? wrote: >>> Hi everyone, >>> >>> >>> >>> I have some question about the Xenopsd. >>> >>> I've read the wiki document but cannot understand where to use it, >>> >>> Is this different with XAPI ? What's the main work for? >>> >>> >>> >>> Can anyone describe it more clearly about it? >>> >>> Thanks a lot!! >>> >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >> >> >> -- >> 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 --------------030906040405060900000906 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Wow, cool news. I've all time have troubles with xapi been 'low-level domain manager' as high-level same time (f.e. if xapi have issues with space in dom0 due excessive logging, all operations stops, including domain reboot).

If you did not already implement everything, would you like to add some way to get those notifications to be available to external subscriptors? I know about xapi events subscription, but xapi requirer master to be online and sometimes getting information directly is much more preferable. I know it all about hacking around xapi, but why not?


On 27.04.2012 18:07, Dave Scott wrote: 
Hi,

At the moment xapi is quite monolithic and we wanted to make it easier to maintain by splitting it up into several smaller services.

The new xenopsd is the "domain manager" part of xapi. This is now what happens when a user starts a VM:

1. client sends the XenAPI VM.start call to xapi
2. xapi decides which host to start the VM on
3. xapi forwards the call to the xapi on the "slave"
4. the slave xapi gives the VM configuration to xenopsd
5. the slave xapi tells xenopsd to start the VM and look after it.

Later if the user reboots the VM:

1. xenopsd notices the domain needs to be restarted
2. xenopsd restarts the VM
3. xapi receives an event from xenopsd telling it that the VM has changed
4. xapi asks xenopsd for the current VM state
5. xapi updates the pool database

So xenopsd is really an internal service.

Apart from being easier to maintain it:

1. will be easier to integrate with libxl because all the low-level xen stuff is contained within a "backend" plugin

2. includes a "mock" backend which can be used to simulate a host, useful for testing

3. it is aware of driver domains i.e. that backends can be in domains other than domain zero

4. is much more cleanly multithreaded (and will hopefully be converted to use the "lwt" monadic concurrency library in the future)

HTH,
Dave


-----Original Message-----
From: todd.deshane.xen@gmail.com [mailto:todd.deshane.xen@gmail.com] On
Behalf Of Todd Deshane
Sent: 27 April 2012 13:48
To: 黃獻輝
Cc: xen-users@lists.xen.org; xen-api@lists.xensource.com; Dave Scott
Subject: Re: [Xen-users] What's the different between XAPI and Xenopsd ?

This is a better question for the xen-api mailing list. Adding to the
CC.

On Thu, Apr 26, 2012 at 10:58 AM, 黃獻輝 <turing@cht.com.tw> wrote:

Hi everyone,



I have some question about the Xenopsd.

I’ve read the wiki document but cannot understand where to use it,

Is this different with XAPI ? What’s the main work for?



Can anyone describe it more clearly about it?

Thanks a lot!!




_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users



--
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

--------------030906040405060900000906-- --===============2272756272518541670== 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 --===============2272756272518541670==-- From xen-api-bounces@lists.xen.org Fri Apr 27 21:41:36 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Fri, 27 Apr 2012 21:41:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNsuv-0000OR-A9; Fri, 27 Apr 2012 21:41:29 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SNsuu-0000OL-Ax for xen-api@lists.xen.org; Fri, 27 Apr 2012 21:41:28 +0000 Received: from [85.158.143.99:60210] by server-1.bemta-4.messagelabs.com id 85/AB-20925-6821B9F4; Fri, 27 Apr 2012 21:41:26 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-3.tower-216.messagelabs.com!1335562884!25054825!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28892 invoked from network); 27 Apr 2012 21:41:24 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-3.tower-216.messagelabs.com with RC4-SHA encrypted SMTP; 27 Apr 2012 21:41:24 -0000 Received: by wibhq7 with SMTP id hq7so844822wib.14 for ; Fri, 27 Apr 2012 14:41:23 -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=j+7nyrJBHo2v5TTe0Y3SMSfb6AT18gzwdiNNne3JFgs=; b=WxzTwSLdMi6/0uAbLby909BLL5DktvrK93KoVj/Uge0etBbMQbsShAkPTObIctshN4 9MKJDFt5EGgoHfxu9uRRblA11zQrUE7hZLQ2CggOYZuw0CJ26lck01RHn+Qcc2m69UWA DslMkBhDxAsRYQtS626LA6BQWzsrdgUGe9JEiCWwxT2L63uvX/K7l5S1QDRU4kjaMtWk JyHXhiFLmXiUGbgAV4SRF9PddFR/oz3yQRsCjewFZ6Bton4sXWvEfPnFyduDanQGqzvi W0ubXXLcnaOF9422AToxeIkY0gJWhKxr79ppNeW1V+HAdwKbRUaTXNfx6iP3JkqDCO/5 9HjA== Received: by 10.180.76.240 with SMTP id n16mr2261444wiw.10.1335562883531; Fri, 27 Apr 2012 14:41:23 -0700 (PDT) Received: from [192.168.1.234] (101-55-112-92.pool.ukrtel.net. [92.112.55.101]) by mx.google.com with ESMTPS id n20sm11906199wiw.5.2012.04.27.14.41.20 (version=SSLv3 cipher=OTHER); Fri, 27 Apr 2012 14:41:22 -0700 (PDT) Message-ID: <4F9B127B.1020307@gmail.com> Date: Sat, 28 Apr 2012 01:41:15 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <557004149BCB6446BE48D5BA5F8C9D68DF918FE4FF@MAIL.corp.cht.com.tw> <81A73678E76EA642801C8F2E4823AD21DA9E1FD5BE@LONPMAILBOX01.citrite.net> In-Reply-To: <81A73678E76EA642801C8F2E4823AD21DA9E1FD5BE@LONPMAILBOX01.citrite.net> Subject: Re: [Xen-API] [Xen-users] What's the different between XAPI and Xenopsd ? X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2272756272518541670==" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org This is a multi-part message in MIME format. --===============2272756272518541670== Content-Type: multipart/alternative; boundary="------------030906040405060900000906" This is a multi-part message in MIME format. --------------030906040405060900000906 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Wow, cool news. I've all time have troubles with xapi been 'low-level domain manager' as high-level same time (f.e. if xapi have issues with space in dom0 due excessive logging, all operations stops, including domain reboot). If you did not already implement everything, would you like to add some way to get those notifications to be available to external subscriptors? I know about xapi events subscription, but xapi requirer master to be online and sometimes getting information directly is much more preferable. I know it all about hacking around xapi, but why not? On 27.04.2012 18:07, Dave Scott wrote: > Hi, > > At the moment xapi is quite monolithic and we wanted to make it easier to maintain by splitting it up into several smaller services. > > The new xenopsd is the "domain manager" part of xapi. This is now what happens when a user starts a VM: > > 1. client sends the XenAPI VM.start call to xapi > 2. xapi decides which host to start the VM on > 3. xapi forwards the call to the xapi on the "slave" > 4. the slave xapi gives the VM configuration to xenopsd > 5. the slave xapi tells xenopsd to start the VM and look after it. > > Later if the user reboots the VM: > > 1. xenopsd notices the domain needs to be restarted > 2. xenopsd restarts the VM > 3. xapi receives an event from xenopsd telling it that the VM has changed > 4. xapi asks xenopsd for the current VM state > 5. xapi updates the pool database > > So xenopsd is really an internal service. > > Apart from being easier to maintain it: > > 1. will be easier to integrate with libxl because all the low-level xen stuff is contained within a "backend" plugin > > 2. includes a "mock" backend which can be used to simulate a host, useful for testing > > 3. it is aware of driver domains i.e. that backends can be in domains other than domain zero > > 4. is much more cleanly multithreaded (and will hopefully be converted to use the "lwt" monadic concurrency library in the future) > > HTH, > Dave > >> -----Original Message----- >> From: todd.deshane.xen@gmail.com [mailto:todd.deshane.xen@gmail.com] On >> Behalf Of Todd Deshane >> Sent: 27 April 2012 13:48 >> To: ??? >> Cc: xen-users@lists.xen.org; xen-api@lists.xensource.com; Dave Scott >> Subject: Re: [Xen-users] What's the different between XAPI and Xenopsd ? >> >> This is a better question for the xen-api mailing list. Adding to the >> CC. >> >> On Thu, Apr 26, 2012 at 10:58 AM, ??? wrote: >>> Hi everyone, >>> >>> >>> >>> I have some question about the Xenopsd. >>> >>> I've read the wiki document but cannot understand where to use it, >>> >>> Is this different with XAPI ? What's the main work for? >>> >>> >>> >>> Can anyone describe it more clearly about it? >>> >>> Thanks a lot!! >>> >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >> >> >> -- >> 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 --------------030906040405060900000906 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Wow, cool news. I've all time have troubles with xapi been 'low-level domain manager' as high-level same time (f.e. if xapi have issues with space in dom0 due excessive logging, all operations stops, including domain reboot).

If you did not already implement everything, would you like to add some way to get those notifications to be available to external subscriptors? I know about xapi events subscription, but xapi requirer master to be online and sometimes getting information directly is much more preferable. I know it all about hacking around xapi, but why not?


On 27.04.2012 18:07, Dave Scott wrote: 
Hi,

At the moment xapi is quite monolithic and we wanted to make it easier to maintain by splitting it up into several smaller services.

The new xenopsd is the "domain manager" part of xapi. This is now what happens when a user starts a VM:

1. client sends the XenAPI VM.start call to xapi
2. xapi decides which host to start the VM on
3. xapi forwards the call to the xapi on the "slave"
4. the slave xapi gives the VM configuration to xenopsd
5. the slave xapi tells xenopsd to start the VM and look after it.

Later if the user reboots the VM:

1. xenopsd notices the domain needs to be restarted
2. xenopsd restarts the VM
3. xapi receives an event from xenopsd telling it that the VM has changed
4. xapi asks xenopsd for the current VM state
5. xapi updates the pool database

So xenopsd is really an internal service.

Apart from being easier to maintain it:

1. will be easier to integrate with libxl because all the low-level xen stuff is contained within a "backend" plugin

2. includes a "mock" backend which can be used to simulate a host, useful for testing

3. it is aware of driver domains i.e. that backends can be in domains other than domain zero

4. is much more cleanly multithreaded (and will hopefully be converted to use the "lwt" monadic concurrency library in the future)

HTH,
Dave


-----Original Message-----
From: todd.deshane.xen@gmail.com [mailto:todd.deshane.xen@gmail.com] On
Behalf Of Todd Deshane
Sent: 27 April 2012 13:48
To: 黃獻輝
Cc: xen-users@lists.xen.org; xen-api@lists.xensource.com; Dave Scott
Subject: Re: [Xen-users] What's the different between XAPI and Xenopsd ?

This is a better question for the xen-api mailing list. Adding to the
CC.

On Thu, Apr 26, 2012 at 10:58 AM, 黃獻輝 <turing@cht.com.tw> wrote:

Hi everyone,



I have some question about the Xenopsd.

I’ve read the wiki document but cannot understand where to use it,

Is this different with XAPI ? What’s the main work for?



Can anyone describe it more clearly about it?

Thanks a lot!!




_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users



--
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

--------------030906040405060900000906-- --===============2272756272518541670== 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 --===============2272756272518541670==-- From xen-api-bounces@lists.xen.org Sun Apr 29 02:06:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 02:06:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOJX7-0002D8-TC; Sun, 29 Apr 2012 02:06:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOJX5-0002D3-Ou for xen-api@lists.xen.org; Sun, 29 Apr 2012 02:06:39 +0000 Received: from [85.158.143.99:34024] by server-2.bemta-4.messagelabs.com id 6A/97-17550-F22AC9F4; Sun, 29 Apr 2012 02:06:39 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1335665196!19332979!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30127 invoked from network); 29 Apr 2012 02:06:37 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-10.tower-216.messagelabs.com with SMTP; 29 Apr 2012 02:06:37 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Sat, 28 Apr 2012 19:06:34 -0700 Message-ID: <4F9CA228.3040307@holgerdanske.com> Date: Sat, 28 Apr 2012 19:06:32 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 xen-api: Thread moved from debian-user. I'm attempting to follow along with the xcp-xapi README.Debian on Wheezy per: http://www.debian.org/News/2012/20120425 Note that I installed Debian testing amd64 for the initial (dom0?) operating system. When I installed xcp-api, I found out that README.Debian recommends i386. When I attempt to create a storage group, the "xe" command-line interface generates an error: # xe sr-create type=ext name-label=node0sr0 device-config:device=/dev/mapper/vg_xcp-lv_xcp Error: Connection refused (calling connect ) If I try to get help with "xe", I get the same error: # xe help Error: Connection refused (calling connect ) Any suggestions? TIA, David p.s. Is there a better mailing list to get support for xcp-xapi? _______________________________________________ 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 Sun Apr 29 02:06:55 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 02:06:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOJX7-0002D8-TC; Sun, 29 Apr 2012 02:06:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOJX5-0002D3-Ou for xen-api@lists.xen.org; Sun, 29 Apr 2012 02:06:39 +0000 Received: from [85.158.143.99:34024] by server-2.bemta-4.messagelabs.com id 6A/97-17550-F22AC9F4; Sun, 29 Apr 2012 02:06:39 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-10.tower-216.messagelabs.com!1335665196!19332979!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30127 invoked from network); 29 Apr 2012 02:06:37 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-10.tower-216.messagelabs.com with SMTP; 29 Apr 2012 02:06:37 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Sat, 28 Apr 2012 19:06:34 -0700 Message-ID: <4F9CA228.3040307@holgerdanske.com> Date: Sat, 28 Apr 2012 19:06:32 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 xen-api: Thread moved from debian-user. I'm attempting to follow along with the xcp-xapi README.Debian on Wheezy per: http://www.debian.org/News/2012/20120425 Note that I installed Debian testing amd64 for the initial (dom0?) operating system. When I installed xcp-api, I found out that README.Debian recommends i386. When I attempt to create a storage group, the "xe" command-line interface generates an error: # xe sr-create type=ext name-label=node0sr0 device-config:device=/dev/mapper/vg_xcp-lv_xcp Error: Connection refused (calling connect ) If I try to get help with "xe", I get the same error: # xe help Error: Connection refused (calling connect ) Any suggestions? TIA, David p.s. Is there a better mailing list to get support for xcp-xapi? _______________________________________________ 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 Sun Apr 29 09:09:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 09:09: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 1SOQ7i-0004Wa-2W; Sun, 29 Apr 2012 09:08:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOQ7e-0004WV-AD for xen-api@lists.xen.org; Sun, 29 Apr 2012 09:08:51 +0000 Received: from [85.158.139.83:23023] by server-6.bemta-5.messagelabs.com id 0E/99-13222-DA00D9F4; Sun, 29 Apr 2012 08:49:49 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1335689388!23259787!1 X-Originating-IP: [74.125.82.51] 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 7914 invoked from network); 29 Apr 2012 08:49:48 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2012 08:49:48 -0000 Received: by wgbed3 with SMTP id ed3so294767wgb.32 for ; Sun, 29 Apr 2012 01:49:48 -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=dSe7D65wm0WsXy9C3eGHDFoFwtsCozWBi36iZceUsVU=; b=DvrQNrCRm8q1SU3xeJZqUEVJoHZ1rpJRh6khvoZDJkOoWfrewwePWs9XCgxq+syCkd 992AZOWuzYwksYAigYlGYRSTghw50dkNaeDtF9pCiuklEUkwSyRc6t5Kt9yMZ+T5eAlS 3KuYh9cNTdJZR5IpVyUNFnP8x4f/KWSJDQ3tnARDOEdtvF8AMQ43AKQyCAHsHAzbAUok ZLROL1OwRlEeaKUwNENaPPEagXixKxlu9fYhzlGE8nXR7r6TwM4e/h9fd31c50T09pAu rgMXbJrftshuRI7NCCtFWEt3LNMMXcAzyNkcR1CsD3bdmISKvFmZnZCCxDM58YARhVPA A1rA== Received: by 10.180.78.164 with SMTP id c4mr5121717wix.10.1335689388679; Sun, 29 Apr 2012 01:49:48 -0700 (PDT) Received: from [10.1.126.128] ([195.162.88.230]) by mx.google.com with ESMTPS id e6sm19050869wix.8.2012.04.29.01.49.41 (version=SSLv3 cipher=OTHER); Sun, 29 Apr 2012 01:49:47 -0700 (PDT) Message-ID: <4F9D009C.9070307@gmail.com> Date: Sun, 29 Apr 2012 12:49:32 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F9CA228.3040307@holgerdanske.com> In-Reply-To: <4F9CA228.3040307@holgerdanske.com> Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 about debian specific yet, but 'connection refused' means xapi service is not running. Check it and it log (xensource.log). On 29.04.2012 06:06, David Christensen wrote: > xen-api: > > Thread moved from debian-user. > > > I'm attempting to follow along with the xcp-xapi README.Debian on > Wheezy per: > > http://www.debian.org/News/2012/20120425 > > > Note that I installed Debian testing amd64 for the initial (dom0?) > operating system. When I installed xcp-api, I found out that > README.Debian recommends i386. > > > When I attempt to create a storage group, the "xe" command-line > interface generates an error: > > # xe sr-create type=ext name-label=node0sr0 > device-config:device=/dev/mapper/vg_xcp-lv_xcp > Error: Connection refused (calling connect ) > > > If I try to get help with "xe", I get the same error: > > # xe help > Error: Connection refused (calling connect ) > > > Any suggestions? > > > TIA, > > David > > p.s. Is there a better mailing list to get support for xcp-xapi? > > _______________________________________________ > 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 Sun Apr 29 09:09:17 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 09:09: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 1SOQ7i-0004Wa-2W; Sun, 29 Apr 2012 09:08:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOQ7e-0004WV-AD for xen-api@lists.xen.org; Sun, 29 Apr 2012 09:08:51 +0000 Received: from [85.158.139.83:23023] by server-6.bemta-5.messagelabs.com id 0E/99-13222-DA00D9F4; Sun, 29 Apr 2012 08:49:49 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1335689388!23259787!1 X-Originating-IP: [74.125.82.51] 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 7914 invoked from network); 29 Apr 2012 08:49:48 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-4.tower-182.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2012 08:49:48 -0000 Received: by wgbed3 with SMTP id ed3so294767wgb.32 for ; Sun, 29 Apr 2012 01:49:48 -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=dSe7D65wm0WsXy9C3eGHDFoFwtsCozWBi36iZceUsVU=; b=DvrQNrCRm8q1SU3xeJZqUEVJoHZ1rpJRh6khvoZDJkOoWfrewwePWs9XCgxq+syCkd 992AZOWuzYwksYAigYlGYRSTghw50dkNaeDtF9pCiuklEUkwSyRc6t5Kt9yMZ+T5eAlS 3KuYh9cNTdJZR5IpVyUNFnP8x4f/KWSJDQ3tnARDOEdtvF8AMQ43AKQyCAHsHAzbAUok ZLROL1OwRlEeaKUwNENaPPEagXixKxlu9fYhzlGE8nXR7r6TwM4e/h9fd31c50T09pAu rgMXbJrftshuRI7NCCtFWEt3LNMMXcAzyNkcR1CsD3bdmISKvFmZnZCCxDM58YARhVPA A1rA== Received: by 10.180.78.164 with SMTP id c4mr5121717wix.10.1335689388679; Sun, 29 Apr 2012 01:49:48 -0700 (PDT) Received: from [10.1.126.128] ([195.162.88.230]) by mx.google.com with ESMTPS id e6sm19050869wix.8.2012.04.29.01.49.41 (version=SSLv3 cipher=OTHER); Sun, 29 Apr 2012 01:49:47 -0700 (PDT) Message-ID: <4F9D009C.9070307@gmail.com> Date: Sun, 29 Apr 2012 12:49:32 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F9CA228.3040307@holgerdanske.com> In-Reply-To: <4F9CA228.3040307@holgerdanske.com> Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 about debian specific yet, but 'connection refused' means xapi service is not running. Check it and it log (xensource.log). On 29.04.2012 06:06, David Christensen wrote: > xen-api: > > Thread moved from debian-user. > > > I'm attempting to follow along with the xcp-xapi README.Debian on > Wheezy per: > > http://www.debian.org/News/2012/20120425 > > > Note that I installed Debian testing amd64 for the initial (dom0?) > operating system. When I installed xcp-api, I found out that > README.Debian recommends i386. > > > When I attempt to create a storage group, the "xe" command-line > interface generates an error: > > # xe sr-create type=ext name-label=node0sr0 > device-config:device=/dev/mapper/vg_xcp-lv_xcp > Error: Connection refused (calling connect ) > > > If I try to get help with "xe", I get the same error: > > # xe help > Error: Connection refused (calling connect ) > > > Any suggestions? > > > TIA, > > David > > p.s. Is there a better mailing list to get support for xcp-xapi? > > _______________________________________________ > 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 Sun Apr 29 11:23:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 11:23: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 1SOSE9-0004ys-Qz; Sun, 29 Apr 2012 11:23:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOSE9-0004yn-Bm for xen-api@lists.xensource.com; Sun, 29 Apr 2012 11:23:41 +0000 Received: from [193.109.254.147:2593] by server-3.bemta-14.messagelabs.com id 5C/26-23274-CB42D9F4; Sun, 29 Apr 2012 11:23:40 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1335698619!6852947!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10706 invoked from network); 29 Apr 2012 11:23:40 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-8.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 11:23:40 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TBNcT5012240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Apr 2012 13:23:39 +0200 Message-ID: <4F9D24B9.8010508@swisscenter.com> Date: Sun, 29 Apr 2012 13:23:37 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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, I'm currently playing with XCP 1.5 beta on a Dell Blade infrastructure = that is linked to redundent filers with 10gbits NICs. The redundent 10gigs interfaces are not managed by xapi (i've told xapi = to forget them) and are configured like on any normal linux box. They are connected to the same 10gig switch where the filers are = connected to. Interfaces on the filers: 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe Interfaces on the blades: 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe The problem is that after some testing with iperf i get to this conclusion: 1) Between the filers the speed is 9.9Gbit/s. 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is quite poor 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is quite = poor (so that's not a new 1.5 bug) 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. Do you have any ideas what could be the problem ? knowing that between = the filers the speed is good and it's passing through the same switch. Is there a DDK VM available for XCP 1.5 beta? I would like to try to = build the latest Broadcom drivers for these nics (bnx2x) for the kernel = used on xcp 1.5... In the meantime I will try to install a debian on another blade to check = if the speed are correct with the filers. Thanks, S=E9bastien _______________________________________________ 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 Sun Apr 29 11:23:52 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 11:23: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 1SOSE9-0004ys-Qz; Sun, 29 Apr 2012 11:23:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOSE9-0004yn-Bm for xen-api@lists.xensource.com; Sun, 29 Apr 2012 11:23:41 +0000 Received: from [193.109.254.147:2593] by server-3.bemta-14.messagelabs.com id 5C/26-23274-CB42D9F4; Sun, 29 Apr 2012 11:23:40 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1335698619!6852947!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10706 invoked from network); 29 Apr 2012 11:23:40 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-8.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 11:23:40 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TBNcT5012240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Apr 2012 13:23:39 +0200 Message-ID: <4F9D24B9.8010508@swisscenter.com> Date: Sun, 29 Apr 2012 13:23:37 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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, I'm currently playing with XCP 1.5 beta on a Dell Blade infrastructure = that is linked to redundent filers with 10gbits NICs. The redundent 10gigs interfaces are not managed by xapi (i've told xapi = to forget them) and are configured like on any normal linux box. They are connected to the same 10gig switch where the filers are = connected to. Interfaces on the filers: 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe Interfaces on the blades: 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 = 10-Gigabit PCIe The problem is that after some testing with iperf i get to this conclusion: 1) Between the filers the speed is 9.9Gbit/s. 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is quite poor 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is quite = poor (so that's not a new 1.5 bug) 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. Do you have any ideas what could be the problem ? knowing that between = the filers the speed is good and it's passing through the same switch. Is there a DDK VM available for XCP 1.5 beta? I would like to try to = build the latest Broadcom drivers for these nics (bnx2x) for the kernel = used on xcp 1.5... In the meantime I will try to install a debian on another blade to check = if the speed are correct with the filers. Thanks, S=E9bastien _______________________________________________ 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 Sun Apr 29 12:23:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 12:23:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOT9w-0005KT-7n; Sun, 29 Apr 2012 12:23:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOT9u-0005KO-8P for xen-api@lists.xensource.com; Sun, 29 Apr 2012 12:23:22 +0000 Received: from [193.109.254.147:44960] by server-5.bemta-14.messagelabs.com id 77/06-30733-9B23D9F4; Sun, 29 Apr 2012 12:23:21 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1335702200!6820183!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12701 invoked from network); 29 Apr 2012 12:23:20 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 12:23:20 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TCNGKH018344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Apr 2012 14:23:17 +0200 Message-ID: <4F9D32B3.6010501@swisscenter.com> Date: Sun, 29 Apr 2012 14:23:15 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> In-Reply-To: <4F9D24B9.8010508@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 again, So I did my test with a debian 6 on the same hardware than I'm using to = try the xcp 1.5. Speed to the filer via the 10gig nic: [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec I would tend to conclude that there is something wrong with the = XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). (Note that our Dell hardware is certified as supported by XenServer, so = it seems not so true :/) modinfo for bnx2x on debian 6 filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko firmware: bnx2x-e1h-5.0.21.0.fw firmware: bnx2x-e1-5.0.21.0.fw version: 1.52.1 license: GPL description: Broadcom NetXtreme II BCM57710/57711/57711E Driver author: Eliezer Tamir srcversion: 050FF749F80E43CB5873BC9 alias: pci:v000014E4d00001650sv*sd*bc*sc*i* alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* depends: mdio,libcrc32c vermagic: 2.6.32-5-amd64 SMP mod_unload modversions parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = (default)) (int) parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 = (default is half number of CPUs) (int) parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 = (default is half number of CPUs) (int) parm: disable_tpa: Disable the TPA (LRO) feature (int) parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) parm: dropless_fc: Pause on exhausted host ring (int) parm: poll: Use polling (for debug) (int) parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) parm: debug: Default debug msglevel (int) modinfo for bnx2x on xcp 1.5 [root@xen-blade13 ~]# modinfo bnx2x filename: = /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net/bnx2= x.ko version: 1.62.17 license: GPL description: Broadcom NetXtreme II BCM57710/57711/57711E/57712/57712E = Driver author: Eliezer Tamir srcversion: 13EA885EBE061121BAEC28D alias: pci:v000014E4d00001663sv*sd*bc*sc*i* alias: pci:v000014E4d00001662sv*sd*bc*sc*i* alias: pci:v000014E4d00001650sv*sd*bc*sc*i* alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* depends: mdio vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP mod_unload = modversions Xen 686 parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) parm: pri_map: Priority to HW queue mapping (int) parm: qs_per_cos: Number of queues per HW queue (int) parm: cos_min_rate: Weight for RR between HW queues (int) parm: num_queues: Number of queues for multi_mode=3D1 (default = is as a number of CPUs) (int) parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) parm: disable_tpa: Disable the TPA (LRO) feature (int) parm: int_mode: Force interrupt mode other than MSI-X (1 = INT#x; 2 MSI) (int) parm: dropless_fc: Pause on exhausted host ring (int) parm: poll: Use polling (for debug) (int) parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) parm: debug: Default debug msglevel (int) Seems that the xcp 1.5 got a more recent version of the module. So that = might not be the problem. Maybe another problem in the kernel ? Any ideas how I could debug this ? Cheers, S=E9bastien On 29.04.2012 13:23, S=E9bastien Riccio wrote: > Hi, > > I'm currently playing with XCP 1.5 beta on a Dell Blade infrastructure = > that is linked to redundent filers with 10gbits NICs. > > The redundent 10gigs interfaces are not managed by xapi (i've told = > xapi to forget them) and are configured like on any normal linux box. > > They are connected to the same 10gig switch where the filers are = > connected to. > > Interfaces on the filers: > 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > > Interfaces on the blades: > 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > > The problem is that after some testing with iperf i get to this = > conclusion: > > 1) Between the filers the speed is 9.9Gbit/s. > 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is quite = > poor > 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is = > quite poor (so that's not a new 1.5 bug) > 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. > > Do you have any ideas what could be the problem ? knowing that between = > the filers the speed is good and it's passing through the same switch. > > Is there a DDK VM available for XCP 1.5 beta? I would like to try to = > build the latest Broadcom drivers for these nics (bnx2x) for the = > kernel used on xcp 1.5... > > In the meantime I will try to install a debian on another blade to = > check if the speed are correct with the filers. > > Thanks, > S=E9bastien > > > _______________________________________________ > 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 Sun Apr 29 12:23:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 12:23:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOT9w-0005KT-7n; Sun, 29 Apr 2012 12:23:24 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOT9u-0005KO-8P for xen-api@lists.xensource.com; Sun, 29 Apr 2012 12:23:22 +0000 Received: from [193.109.254.147:44960] by server-5.bemta-14.messagelabs.com id 77/06-30733-9B23D9F4; Sun, 29 Apr 2012 12:23:21 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1335702200!6820183!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12701 invoked from network); 29 Apr 2012 12:23:20 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 12:23:20 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TCNGKH018344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Apr 2012 14:23:17 +0200 Message-ID: <4F9D32B3.6010501@swisscenter.com> Date: Sun, 29 Apr 2012 14:23:15 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> In-Reply-To: <4F9D24B9.8010508@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 again, So I did my test with a debian 6 on the same hardware than I'm using to = try the xcp 1.5. Speed to the filer via the 10gig nic: [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec I would tend to conclude that there is something wrong with the = XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). (Note that our Dell hardware is certified as supported by XenServer, so = it seems not so true :/) modinfo for bnx2x on debian 6 filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko firmware: bnx2x-e1h-5.0.21.0.fw firmware: bnx2x-e1-5.0.21.0.fw version: 1.52.1 license: GPL description: Broadcom NetXtreme II BCM57710/57711/57711E Driver author: Eliezer Tamir srcversion: 050FF749F80E43CB5873BC9 alias: pci:v000014E4d00001650sv*sd*bc*sc*i* alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* depends: mdio,libcrc32c vermagic: 2.6.32-5-amd64 SMP mod_unload modversions parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = (default)) (int) parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 = (default is half number of CPUs) (int) parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 = (default is half number of CPUs) (int) parm: disable_tpa: Disable the TPA (LRO) feature (int) parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) parm: dropless_fc: Pause on exhausted host ring (int) parm: poll: Use polling (for debug) (int) parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) parm: debug: Default debug msglevel (int) modinfo for bnx2x on xcp 1.5 [root@xen-blade13 ~]# modinfo bnx2x filename: = /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net/bnx2= x.ko version: 1.62.17 license: GPL description: Broadcom NetXtreme II BCM57710/57711/57711E/57712/57712E = Driver author: Eliezer Tamir srcversion: 13EA885EBE061121BAEC28D alias: pci:v000014E4d00001663sv*sd*bc*sc*i* alias: pci:v000014E4d00001662sv*sd*bc*sc*i* alias: pci:v000014E4d00001650sv*sd*bc*sc*i* alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* depends: mdio vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP mod_unload = modversions Xen 686 parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) parm: pri_map: Priority to HW queue mapping (int) parm: qs_per_cos: Number of queues per HW queue (int) parm: cos_min_rate: Weight for RR between HW queues (int) parm: num_queues: Number of queues for multi_mode=3D1 (default = is as a number of CPUs) (int) parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) parm: disable_tpa: Disable the TPA (LRO) feature (int) parm: int_mode: Force interrupt mode other than MSI-X (1 = INT#x; 2 MSI) (int) parm: dropless_fc: Pause on exhausted host ring (int) parm: poll: Use polling (for debug) (int) parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) parm: debug: Default debug msglevel (int) Seems that the xcp 1.5 got a more recent version of the module. So that = might not be the problem. Maybe another problem in the kernel ? Any ideas how I could debug this ? Cheers, S=E9bastien On 29.04.2012 13:23, S=E9bastien Riccio wrote: > Hi, > > I'm currently playing with XCP 1.5 beta on a Dell Blade infrastructure = > that is linked to redundent filers with 10gbits NICs. > > The redundent 10gigs interfaces are not managed by xapi (i've told = > xapi to forget them) and are configured like on any normal linux box. > > They are connected to the same 10gig switch where the filers are = > connected to. > > Interfaces on the filers: > 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > > Interfaces on the blades: > 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = > BCM57711 10-Gigabit PCIe > > The problem is that after some testing with iperf i get to this = > conclusion: > > 1) Between the filers the speed is 9.9Gbit/s. > 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is quite = > poor > 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is = > quite poor (so that's not a new 1.5 bug) > 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. > > Do you have any ideas what could be the problem ? knowing that between = > the filers the speed is good and it's passing through the same switch. > > Is there a DDK VM available for XCP 1.5 beta? I would like to try to = > build the latest Broadcom drivers for these nics (bnx2x) for the = > kernel used on xcp 1.5... > > In the meantime I will try to install a debian on another blade to = > check if the speed are correct with the filers. > > Thanks, > S=E9bastien > > > _______________________________________________ > 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 Sun Apr 29 12:44:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 12:44: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 1SOTU4-0005RL-U0; Sun, 29 Apr 2012 12:44:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOTU3-0005RG-Gz for xen-api@lists.xensource.com; Sun, 29 Apr 2012 12:44:11 +0000 Received: from [193.109.254.147:48847] by server-12.bemta-14.messagelabs.com id FF/1F-05898-A973D9F4; Sun, 29 Apr 2012 12:44:10 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1335703449!6834663!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 389 invoked from network); 29 Apr 2012 12:44:09 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 12:44:09 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TCi8eq020525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Apr 2012 14:44:09 +0200 Message-ID: <4F9D3797.5050406@swisscenter.com> Date: Sun, 29 Apr 2012 14:44:07 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> In-Reply-To: <4F9D32B3.6010501@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 again, again :) Something strange : If i issue parallel threads with iperf (8 in this example, the 10Gbit/s = speed is reached) [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? It's really not efficient as we connect the iscsi storage to the filer = from dom0, so it will always be a single thread, so no possibility to = get the full 10Gbit bw for our storage. Is there a way to get rid of that (bug?) limitation ? Cheers, S=E9bastien On 29.04.2012 14:23, S=E9bastien Riccio wrote: > Hi again, > > So I did my test with a debian 6 on the same hardware than I'm using = > to try the xcp 1.5. > > Speed to the filer via the 10gig nic: > > [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec > > I would tend to conclude that there is something wrong with the = > XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). > > (Note that our Dell hardware is certified as supported by XenServer, = > so it seems not so true :/) > > modinfo for bnx2x on debian 6 > > filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko > firmware: bnx2x-e1h-5.0.21.0.fw > firmware: bnx2x-e1-5.0.21.0.fw > version: 1.52.1 > license: GPL > description: Broadcom NetXtreme II BCM57710/57711/57711E Driver > author: Eliezer Tamir > srcversion: 050FF749F80E43CB5873BC9 > alias: pci:v000014E4d00001650sv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* > depends: mdio,libcrc32c > vermagic: 2.6.32-5-amd64 SMP mod_unload modversions > parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = > (default)) (int) > parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 = > (default is half number of CPUs) (int) > parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 = > (default is half number of CPUs) (int) > parm: disable_tpa: Disable the TPA (LRO) feature (int) > parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) > parm: dropless_fc: Pause on exhausted host ring (int) > parm: poll: Use polling (for debug) (int) > parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) > parm: debug: Default debug msglevel (int) > > modinfo for bnx2x on xcp 1.5 > > [root@xen-blade13 ~]# modinfo bnx2x > filename: = > /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net/bn= x2x.ko > version: 1.62.17 > license: GPL > description: Broadcom NetXtreme II = > BCM57710/57711/57711E/57712/57712E Driver > author: Eliezer Tamir > srcversion: 13EA885EBE061121BAEC28D > alias: pci:v000014E4d00001663sv*sd*bc*sc*i* > alias: pci:v000014E4d00001662sv*sd*bc*sc*i* > alias: pci:v000014E4d00001650sv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* > depends: mdio > vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP mod_unload = > modversions Xen 686 > parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = > (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) > parm: pri_map: Priority to HW queue mapping (int) > parm: qs_per_cos: Number of queues per HW queue (int) > parm: cos_min_rate: Weight for RR between HW queues (int) > parm: num_queues: Number of queues for multi_mode=3D1 (default = > is as a number of CPUs) (int) > parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) > parm: disable_tpa: Disable the TPA (LRO) feature (int) > parm: int_mode: Force interrupt mode other than MSI-X (1 = > INT#x; 2 MSI) (int) > parm: dropless_fc: Pause on exhausted host ring (int) > parm: poll: Use polling (for debug) (int) > parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) > parm: debug: Default debug msglevel (int) > > Seems that the xcp 1.5 got a more recent version of the module. So = > that might not be the problem. > Maybe another problem in the kernel ? > > Any ideas how I could debug this ? > > Cheers, > S=E9bastien > > > On 29.04.2012 13:23, S=E9bastien Riccio wrote: >> Hi, >> >> I'm currently playing with XCP 1.5 beta on a Dell Blade = >> infrastructure that is linked to redundent filers with 10gbits NICs. >> >> The redundent 10gigs interfaces are not managed by xapi (i've told = >> xapi to forget them) and are configured like on any normal linux box. >> >> They are connected to the same 10gig switch where the filers are = >> connected to. >> >> Interfaces on the filers: >> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> >> Interfaces on the blades: >> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> >> The problem is that after some testing with iperf i get to this = >> conclusion: >> >> 1) Between the filers the speed is 9.9Gbit/s. >> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is quite = >> poor >> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is = >> quite poor (so that's not a new 1.5 bug) >> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >> >> Do you have any ideas what could be the problem ? knowing that = >> between the filers the speed is good and it's passing through the = >> same switch. >> >> Is there a DDK VM available for XCP 1.5 beta? I would like to try to = >> build the latest Broadcom drivers for these nics (bnx2x) for the = >> kernel used on xcp 1.5... >> >> In the meantime I will try to install a debian on another blade to = >> check if the speed are correct with the filers. >> >> Thanks, >> S=E9bastien >> >> >> _______________________________________________ >> 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 Sun Apr 29 12:44:22 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 12:44: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 1SOTU4-0005RL-U0; Sun, 29 Apr 2012 12:44:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOTU3-0005RG-Gz for xen-api@lists.xensource.com; Sun, 29 Apr 2012 12:44:11 +0000 Received: from [193.109.254.147:48847] by server-12.bemta-14.messagelabs.com id FF/1F-05898-A973D9F4; Sun, 29 Apr 2012 12:44:10 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1335703449!6834663!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 389 invoked from network); 29 Apr 2012 12:44:09 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 12:44:09 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TCi8eq020525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Apr 2012 14:44:09 +0200 Message-ID: <4F9D3797.5050406@swisscenter.com> Date: Sun, 29 Apr 2012 14:44:07 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> In-Reply-To: <4F9D32B3.6010501@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 again, again :) Something strange : If i issue parallel threads with iperf (8 in this example, the 10Gbit/s = speed is reached) [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? It's really not efficient as we connect the iscsi storage to the filer = from dom0, so it will always be a single thread, so no possibility to = get the full 10Gbit bw for our storage. Is there a way to get rid of that (bug?) limitation ? Cheers, S=E9bastien On 29.04.2012 14:23, S=E9bastien Riccio wrote: > Hi again, > > So I did my test with a debian 6 on the same hardware than I'm using = > to try the xcp 1.5. > > Speed to the filer via the 10gig nic: > > [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec > > I would tend to conclude that there is something wrong with the = > XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). > > (Note that our Dell hardware is certified as supported by XenServer, = > so it seems not so true :/) > > modinfo for bnx2x on debian 6 > > filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko > firmware: bnx2x-e1h-5.0.21.0.fw > firmware: bnx2x-e1-5.0.21.0.fw > version: 1.52.1 > license: GPL > description: Broadcom NetXtreme II BCM57710/57711/57711E Driver > author: Eliezer Tamir > srcversion: 050FF749F80E43CB5873BC9 > alias: pci:v000014E4d00001650sv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* > depends: mdio,libcrc32c > vermagic: 2.6.32-5-amd64 SMP mod_unload modversions > parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = > (default)) (int) > parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 = > (default is half number of CPUs) (int) > parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 = > (default is half number of CPUs) (int) > parm: disable_tpa: Disable the TPA (LRO) feature (int) > parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) > parm: dropless_fc: Pause on exhausted host ring (int) > parm: poll: Use polling (for debug) (int) > parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) > parm: debug: Default debug msglevel (int) > > modinfo for bnx2x on xcp 1.5 > > [root@xen-blade13 ~]# modinfo bnx2x > filename: = > /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net/bn= x2x.ko > version: 1.62.17 > license: GPL > description: Broadcom NetXtreme II = > BCM57710/57711/57711E/57712/57712E Driver > author: Eliezer Tamir > srcversion: 13EA885EBE061121BAEC28D > alias: pci:v000014E4d00001663sv*sd*bc*sc*i* > alias: pci:v000014E4d00001662sv*sd*bc*sc*i* > alias: pci:v000014E4d00001650sv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* > alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* > depends: mdio > vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP mod_unload = > modversions Xen 686 > parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = > (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) > parm: pri_map: Priority to HW queue mapping (int) > parm: qs_per_cos: Number of queues per HW queue (int) > parm: cos_min_rate: Weight for RR between HW queues (int) > parm: num_queues: Number of queues for multi_mode=3D1 (default = > is as a number of CPUs) (int) > parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) > parm: disable_tpa: Disable the TPA (LRO) feature (int) > parm: int_mode: Force interrupt mode other than MSI-X (1 = > INT#x; 2 MSI) (int) > parm: dropless_fc: Pause on exhausted host ring (int) > parm: poll: Use polling (for debug) (int) > parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) > parm: debug: Default debug msglevel (int) > > Seems that the xcp 1.5 got a more recent version of the module. So = > that might not be the problem. > Maybe another problem in the kernel ? > > Any ideas how I could debug this ? > > Cheers, > S=E9bastien > > > On 29.04.2012 13:23, S=E9bastien Riccio wrote: >> Hi, >> >> I'm currently playing with XCP 1.5 beta on a Dell Blade = >> infrastructure that is linked to redundent filers with 10gbits NICs. >> >> The redundent 10gigs interfaces are not managed by xapi (i've told = >> xapi to forget them) and are configured like on any normal linux box. >> >> They are connected to the same 10gig switch where the filers are = >> connected to. >> >> Interfaces on the filers: >> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> >> Interfaces on the blades: >> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >> BCM57711 10-Gigabit PCIe >> >> The problem is that after some testing with iperf i get to this = >> conclusion: >> >> 1) Between the filers the speed is 9.9Gbit/s. >> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is quite = >> poor >> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is = >> quite poor (so that's not a new 1.5 bug) >> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >> >> Do you have any ideas what could be the problem ? knowing that = >> between the filers the speed is good and it's passing through the = >> same switch. >> >> Is there a DDK VM available for XCP 1.5 beta? I would like to try to = >> build the latest Broadcom drivers for these nics (bnx2x) for the = >> kernel used on xcp 1.5... >> >> In the meantime I will try to install a debian on another blade to = >> check if the speed are correct with the filers. >> >> Thanks, >> S=E9bastien >> >> >> _______________________________________________ >> 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 Sun Apr 29 15:29:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 15:29: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 1SOW3S-0007Co-DZ; Sun, 29 Apr 2012 15:28:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOW3Q-0007Ci-V7 for xen-api@lists.xensource.com; Sun, 29 Apr 2012 15:28:53 +0000 Received: from [85.158.139.83:46702] by server-9.bemta-5.messagelabs.com id 52/6D-09826-43E5D9F4; Sun, 29 Apr 2012 15:28:52 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1335713330!25989248!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10847 invoked from network); 29 Apr 2012 15:28:50 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-3.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 15:28:50 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TFSmUU004978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Apr 2012 17:28:49 +0200 Message-ID: <4F9D5E2F.2090906@swisscenter.com> Date: Sun, 29 Apr 2012 17:28:47 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> In-Reply-To: <4F9D3797.5050406@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Me again (sorry), Still trying to sort things out to understand why it's slow under xcp, = I've installed xcp on debian (project kronos), and did an iperf from dom0 [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec It's not getting to the 10gibt/s so it looks that it's related to the = xen hypervisor. But it still 2x better than with xcp/xenserver. Any ideas how to improve this? Cheers, S=E9bastien On 29.04.2012 14:44, S=E9bastien Riccio wrote: > Hi again, again :) > > Something strange : > > If i issue parallel threads with iperf (8 in this example, the = > 10Gbit/s speed is reached) > > [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec > [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec > [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec > [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec > [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec > [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec > [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec > [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec > [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec > > So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? > It's really not efficient as we connect the iscsi storage to the filer = > from dom0, so it will always be a single thread, so no possibility to = > get the full 10Gbit bw for our storage. > > Is there a way to get rid of that (bug?) limitation ? > > Cheers, > S=E9bastien > > > > > On 29.04.2012 14:23, S=E9bastien Riccio wrote: >> Hi again, >> >> So I did my test with a debian 6 on the same hardware than I'm using = >> to try the xcp 1.5. >> >> Speed to the filer via the 10gig nic: >> >> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >> >> I would tend to conclude that there is something wrong with the = >> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >> >> (Note that our Dell hardware is certified as supported by XenServer, = >> so it seems not so true :/) >> >> modinfo for bnx2x on debian 6 >> >> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko >> firmware: bnx2x-e1h-5.0.21.0.fw >> firmware: bnx2x-e1-5.0.21.0.fw >> version: 1.52.1 >> license: GPL >> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >> author: Eliezer Tamir >> srcversion: 050FF749F80E43CB5873BC9 >> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >> depends: mdio,libcrc32c >> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = >> (default)) (int) >> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 = >> (default is half number of CPUs) (int) >> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 = >> (default is half number of CPUs) (int) >> parm: disable_tpa: Disable the TPA (LRO) feature (int) >> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >> parm: dropless_fc: Pause on exhausted host ring (int) >> parm: poll: Use polling (for debug) (int) >> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >> parm: debug: Default debug msglevel (int) >> >> modinfo for bnx2x on xcp 1.5 >> >> [root@xen-blade13 ~]# modinfo bnx2x >> filename: = >> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net/b= nx2x.ko >> version: 1.62.17 >> license: GPL >> description: Broadcom NetXtreme II = >> BCM57710/57711/57711E/57712/57712E Driver >> author: Eliezer Tamir >> srcversion: 13EA885EBE061121BAEC28D >> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >> depends: mdio >> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP mod_unload = >> modversions Xen 686 >> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = >> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >> parm: pri_map: Priority to HW queue mapping (int) >> parm: qs_per_cos: Number of queues per HW queue (int) >> parm: cos_min_rate: Weight for RR between HW queues (int) >> parm: num_queues: Number of queues for multi_mode=3D1 = >> (default is as a number of CPUs) (int) >> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >> parm: disable_tpa: Disable the TPA (LRO) feature (int) >> parm: int_mode: Force interrupt mode other than MSI-X (1 = >> INT#x; 2 MSI) (int) >> parm: dropless_fc: Pause on exhausted host ring (int) >> parm: poll: Use polling (for debug) (int) >> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >> parm: debug: Default debug msglevel (int) >> >> Seems that the xcp 1.5 got a more recent version of the module. So = >> that might not be the problem. >> Maybe another problem in the kernel ? >> >> Any ideas how I could debug this ? >> >> Cheers, >> S=E9bastien >> >> >> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>> Hi, >>> >>> I'm currently playing with XCP 1.5 beta on a Dell Blade = >>> infrastructure that is linked to redundent filers with 10gbits NICs. >>> >>> The redundent 10gigs interfaces are not managed by xapi (i've told = >>> xapi to forget them) and are configured like on any normal linux box. >>> >>> They are connected to the same 10gig switch where the filers are = >>> connected to. >>> >>> Interfaces on the filers: >>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> >>> Interfaces on the blades: >>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> >>> The problem is that after some testing with iperf i get to this = >>> conclusion: >>> >>> 1) Between the filers the speed is 9.9Gbit/s. >>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is = >>> quite poor >>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is = >>> quite poor (so that's not a new 1.5 bug) >>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>> >>> Do you have any ideas what could be the problem ? knowing that = >>> between the filers the speed is good and it's passing through the = >>> same switch. >>> >>> Is there a DDK VM available for XCP 1.5 beta? I would like to try to = >>> build the latest Broadcom drivers for these nics (bnx2x) for the = >>> kernel used on xcp 1.5... >>> >>> In the meantime I will try to install a debian on another blade to = >>> check if the speed are correct with the filers. >>> >>> Thanks, >>> S=E9bastien >>> >>> >>> _______________________________________________ >>> 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 > _______________________________________________ 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 Sun Apr 29 15:29:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 15:29: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 1SOW3S-0007Co-DZ; Sun, 29 Apr 2012 15:28:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOW3Q-0007Ci-V7 for xen-api@lists.xensource.com; Sun, 29 Apr 2012 15:28:53 +0000 Received: from [85.158.139.83:46702] by server-9.bemta-5.messagelabs.com id 52/6D-09826-43E5D9F4; Sun, 29 Apr 2012 15:28:52 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-3.tower-182.messagelabs.com!1335713330!25989248!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10847 invoked from network); 29 Apr 2012 15:28:50 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-3.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 15:28:50 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TFSmUU004978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Apr 2012 17:28:49 +0200 Message-ID: <4F9D5E2F.2090906@swisscenter.com> Date: Sun, 29 Apr 2012 17:28:47 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> In-Reply-To: <4F9D3797.5050406@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Me again (sorry), Still trying to sort things out to understand why it's slow under xcp, = I've installed xcp on debian (project kronos), and did an iperf from dom0 [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec It's not getting to the 10gibt/s so it looks that it's related to the = xen hypervisor. But it still 2x better than with xcp/xenserver. Any ideas how to improve this? Cheers, S=E9bastien On 29.04.2012 14:44, S=E9bastien Riccio wrote: > Hi again, again :) > > Something strange : > > If i issue parallel threads with iperf (8 in this example, the = > 10Gbit/s speed is reached) > > [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec > [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec > [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec > [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec > [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec > [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec > [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec > [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec > [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec > > So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? > It's really not efficient as we connect the iscsi storage to the filer = > from dom0, so it will always be a single thread, so no possibility to = > get the full 10Gbit bw for our storage. > > Is there a way to get rid of that (bug?) limitation ? > > Cheers, > S=E9bastien > > > > > On 29.04.2012 14:23, S=E9bastien Riccio wrote: >> Hi again, >> >> So I did my test with a debian 6 on the same hardware than I'm using = >> to try the xcp 1.5. >> >> Speed to the filer via the 10gig nic: >> >> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >> >> I would tend to conclude that there is something wrong with the = >> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >> >> (Note that our Dell hardware is certified as supported by XenServer, = >> so it seems not so true :/) >> >> modinfo for bnx2x on debian 6 >> >> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko >> firmware: bnx2x-e1h-5.0.21.0.fw >> firmware: bnx2x-e1-5.0.21.0.fw >> version: 1.52.1 >> license: GPL >> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >> author: Eliezer Tamir >> srcversion: 050FF749F80E43CB5873BC9 >> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >> depends: mdio,libcrc32c >> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = >> (default)) (int) >> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 = >> (default is half number of CPUs) (int) >> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 = >> (default is half number of CPUs) (int) >> parm: disable_tpa: Disable the TPA (LRO) feature (int) >> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >> parm: dropless_fc: Pause on exhausted host ring (int) >> parm: poll: Use polling (for debug) (int) >> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >> parm: debug: Default debug msglevel (int) >> >> modinfo for bnx2x on xcp 1.5 >> >> [root@xen-blade13 ~]# modinfo bnx2x >> filename: = >> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net/b= nx2x.ko >> version: 1.62.17 >> license: GPL >> description: Broadcom NetXtreme II = >> BCM57710/57711/57711E/57712/57712E Driver >> author: Eliezer Tamir >> srcversion: 13EA885EBE061121BAEC28D >> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >> depends: mdio >> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP mod_unload = >> modversions Xen 686 >> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = >> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >> parm: pri_map: Priority to HW queue mapping (int) >> parm: qs_per_cos: Number of queues per HW queue (int) >> parm: cos_min_rate: Weight for RR between HW queues (int) >> parm: num_queues: Number of queues for multi_mode=3D1 = >> (default is as a number of CPUs) (int) >> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >> parm: disable_tpa: Disable the TPA (LRO) feature (int) >> parm: int_mode: Force interrupt mode other than MSI-X (1 = >> INT#x; 2 MSI) (int) >> parm: dropless_fc: Pause on exhausted host ring (int) >> parm: poll: Use polling (for debug) (int) >> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >> parm: debug: Default debug msglevel (int) >> >> Seems that the xcp 1.5 got a more recent version of the module. So = >> that might not be the problem. >> Maybe another problem in the kernel ? >> >> Any ideas how I could debug this ? >> >> Cheers, >> S=E9bastien >> >> >> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>> Hi, >>> >>> I'm currently playing with XCP 1.5 beta on a Dell Blade = >>> infrastructure that is linked to redundent filers with 10gbits NICs. >>> >>> The redundent 10gigs interfaces are not managed by xapi (i've told = >>> xapi to forget them) and are configured like on any normal linux box. >>> >>> They are connected to the same 10gig switch where the filers are = >>> connected to. >>> >>> Interfaces on the filers: >>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> >>> Interfaces on the blades: >>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>> BCM57711 10-Gigabit PCIe >>> >>> The problem is that after some testing with iperf i get to this = >>> conclusion: >>> >>> 1) Between the filers the speed is 9.9Gbit/s. >>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is = >>> quite poor >>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is = >>> quite poor (so that's not a new 1.5 bug) >>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>> >>> Do you have any ideas what could be the problem ? knowing that = >>> between the filers the speed is good and it's passing through the = >>> same switch. >>> >>> Is there a DDK VM available for XCP 1.5 beta? I would like to try to = >>> build the latest Broadcom drivers for these nics (bnx2x) for the = >>> kernel used on xcp 1.5... >>> >>> In the meantime I will try to install a debian on another blade to = >>> check if the speed are correct with the filers. >>> >>> Thanks, >>> S=E9bastien >>> >>> >>> _______________________________________________ >>> 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 > _______________________________________________ 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 Sun Apr 29 17:23:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 17:23:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOXqY-0008G1-PW; Sun, 29 Apr 2012 17:23:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOXqX-0008Fw-4E for xen-api@lists.xensource.com; Sun, 29 Apr 2012 17:23:41 +0000 Received: from [85.158.143.35:16663] by server-2.bemta-4.messagelabs.com id 27/29-17550-C197D9F4; Sun, 29 Apr 2012 17:23:40 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1335720218!9167653!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11560 invoked from network); 29 Apr 2012 17:23:39 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 17:23:39 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3THNbWW015066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Apr 2012 19:23:38 +0200 Message-ID: <4F9D7917.8060804@swisscenter.com> Date: Sun, 29 Apr 2012 19:23:35 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com> In-Reply-To: <4F9D5E2F.2090906@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Another discovery: On XCP 1.5 iperf on dom0 to localhost (loopback) Client connecting to localhost, TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 38278 connected with 127.0.0.1 port 5001 ^C[ 3] 0.0- 5.2 sec 1.79 GBytes 2.97 Gbits/sec Limited to 3gbit on xapi/debian root@kronos:~# iperf -c 10.50.50.111 ------------------------------------------------------------ Client connecting to 10.50.50.111, TCP port 5001 TCP window size: 167 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 41137 connected with 127.0.0.1 port 5001 [ ID] Interval Transfer Bandwidth[ 3] 0.0- 5.6 sec 13.1 = GBytes 20.0 Gbits/sec clearly not a nic issue.... Cheers, S=E9bastien On 29.04.2012 17:28, S=E9bastien Riccio wrote: > Me again (sorry), > > Still trying to sort things out to understand why it's slow under xcp, = > I've installed xcp on debian (project kronos), and did an iperf from dom0 > > [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec > [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec > [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec > [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec > [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec > [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec > [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec > > It's not getting to the 10gibt/s so it looks that it's related to the = > xen hypervisor. > But it still 2x better than with xcp/xenserver. > > Any ideas how to improve this? > > Cheers, > S=E9bastien > > On 29.04.2012 14:44, S=E9bastien Riccio wrote: >> Hi again, again :) >> >> Something strange : >> >> If i issue parallel threads with iperf (8 in this example, the = >> 10Gbit/s speed is reached) >> >> [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec >> [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >> [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec >> [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec >> [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec >> [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec >> [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >> [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec >> [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec >> >> So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? >> It's really not efficient as we connect the iscsi storage to the = >> filer from dom0, so it will always be a single thread, so no = >> possibility to get the full 10Gbit bw for our storage. >> >> Is there a way to get rid of that (bug?) limitation ? >> >> Cheers, >> S=E9bastien >> >> >> >> >> On 29.04.2012 14:23, S=E9bastien Riccio wrote: >>> Hi again, >>> >>> So I did my test with a debian 6 on the same hardware than I'm using = >>> to try the xcp 1.5. >>> >>> Speed to the filer via the 10gig nic: >>> >>> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >>> >>> I would tend to conclude that there is something wrong with the = >>> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >>> >>> (Note that our Dell hardware is certified as supported by XenServer, = >>> so it seems not so true :/) >>> >>> modinfo for bnx2x on debian 6 >>> >>> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko >>> firmware: bnx2x-e1h-5.0.21.0.fw >>> firmware: bnx2x-e1-5.0.21.0.fw >>> version: 1.52.1 >>> license: GPL >>> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >>> author: Eliezer Tamir >>> srcversion: 050FF749F80E43CB5873BC9 >>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>> depends: mdio,libcrc32c >>> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = >>> (default)) (int) >>> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 = >>> (default is half number of CPUs) (int) >>> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 = >>> (default is half number of CPUs) (int) >>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >>> parm: dropless_fc: Pause on exhausted host ring (int) >>> parm: poll: Use polling (for debug) (int) >>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>> parm: debug: Default debug msglevel (int) >>> >>> modinfo for bnx2x on xcp 1.5 >>> >>> [root@xen-blade13 ~]# modinfo bnx2x >>> filename: = >>> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net/= bnx2x.ko >>> version: 1.62.17 >>> license: GPL >>> description: Broadcom NetXtreme II = >>> BCM57710/57711/57711E/57712/57712E Driver >>> author: Eliezer Tamir >>> srcversion: 13EA885EBE061121BAEC28D >>> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >>> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>> depends: mdio >>> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP = >>> mod_unload modversions Xen 686 >>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = >>> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >>> parm: pri_map: Priority to HW queue mapping (int) >>> parm: qs_per_cos: Number of queues per HW queue (int) >>> parm: cos_min_rate: Weight for RR between HW queues (int) >>> parm: num_queues: Number of queues for multi_mode=3D1 = >>> (default is as a number of CPUs) (int) >>> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>> parm: int_mode: Force interrupt mode other than MSI-X (1 = >>> INT#x; 2 MSI) (int) >>> parm: dropless_fc: Pause on exhausted host ring (int) >>> parm: poll: Use polling (for debug) (int) >>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>> parm: debug: Default debug msglevel (int) >>> >>> Seems that the xcp 1.5 got a more recent version of the module. So = >>> that might not be the problem. >>> Maybe another problem in the kernel ? >>> >>> Any ideas how I could debug this ? >>> >>> Cheers, >>> S=E9bastien >>> >>> >>> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>>> Hi, >>>> >>>> I'm currently playing with XCP 1.5 beta on a Dell Blade = >>>> infrastructure that is linked to redundent filers with 10gbits NICs. >>>> >>>> The redundent 10gigs interfaces are not managed by xapi (i've told = >>>> xapi to forget them) and are configured like on any normal linux box. >>>> >>>> They are connected to the same 10gig switch where the filers are = >>>> connected to. >>>> >>>> Interfaces on the filers: >>>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> >>>> Interfaces on the blades: >>>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> >>>> The problem is that after some testing with iperf i get to this = >>>> conclusion: >>>> >>>> 1) Between the filers the speed is 9.9Gbit/s. >>>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is = >>>> quite poor >>>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is = >>>> quite poor (so that's not a new 1.5 bug) >>>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>>> >>>> Do you have any ideas what could be the problem ? knowing that = >>>> between the filers the speed is good and it's passing through the = >>>> same switch. >>>> >>>> Is there a DDK VM available for XCP 1.5 beta? I would like to try = >>>> to build the latest Broadcom drivers for these nics (bnx2x) for the = >>>> kernel used on xcp 1.5... >>>> >>>> In the meantime I will try to install a debian on another blade to = >>>> check if the speed are correct with the filers. >>>> >>>> Thanks, >>>> S=E9bastien >>>> >>>> >>>> _______________________________________________ >>>> 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 >> > > > _______________________________________________ > 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 Sun Apr 29 17:23:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 17:23:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOXqY-0008G1-PW; Sun, 29 Apr 2012 17:23:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOXqX-0008Fw-4E for xen-api@lists.xensource.com; Sun, 29 Apr 2012 17:23:41 +0000 Received: from [85.158.143.35:16663] by server-2.bemta-4.messagelabs.com id 27/29-17550-C197D9F4; Sun, 29 Apr 2012 17:23:40 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1335720218!9167653!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11560 invoked from network); 29 Apr 2012 17:23:39 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 17:23:39 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3THNbWW015066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 29 Apr 2012 19:23:38 +0200 Message-ID: <4F9D7917.8060804@swisscenter.com> Date: Sun, 29 Apr 2012 19:23:35 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com> In-Reply-To: <4F9D5E2F.2090906@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Another discovery: On XCP 1.5 iperf on dom0 to localhost (loopback) Client connecting to localhost, TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 38278 connected with 127.0.0.1 port 5001 ^C[ 3] 0.0- 5.2 sec 1.79 GBytes 2.97 Gbits/sec Limited to 3gbit on xapi/debian root@kronos:~# iperf -c 10.50.50.111 ------------------------------------------------------------ Client connecting to 10.50.50.111, TCP port 5001 TCP window size: 167 KByte (default) ------------------------------------------------------------ [ 3] local 127.0.0.1 port 41137 connected with 127.0.0.1 port 5001 [ ID] Interval Transfer Bandwidth[ 3] 0.0- 5.6 sec 13.1 = GBytes 20.0 Gbits/sec clearly not a nic issue.... Cheers, S=E9bastien On 29.04.2012 17:28, S=E9bastien Riccio wrote: > Me again (sorry), > > Still trying to sort things out to understand why it's slow under xcp, = > I've installed xcp on debian (project kronos), and did an iperf from dom0 > > [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec > [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec > [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec > [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec > [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec > [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec > [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec > > It's not getting to the 10gibt/s so it looks that it's related to the = > xen hypervisor. > But it still 2x better than with xcp/xenserver. > > Any ideas how to improve this? > > Cheers, > S=E9bastien > > On 29.04.2012 14:44, S=E9bastien Riccio wrote: >> Hi again, again :) >> >> Something strange : >> >> If i issue parallel threads with iperf (8 in this example, the = >> 10Gbit/s speed is reached) >> >> [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec >> [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >> [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec >> [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec >> [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec >> [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec >> [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >> [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec >> [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec >> >> So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? >> It's really not efficient as we connect the iscsi storage to the = >> filer from dom0, so it will always be a single thread, so no = >> possibility to get the full 10Gbit bw for our storage. >> >> Is there a way to get rid of that (bug?) limitation ? >> >> Cheers, >> S=E9bastien >> >> >> >> >> On 29.04.2012 14:23, S=E9bastien Riccio wrote: >>> Hi again, >>> >>> So I did my test with a debian 6 on the same hardware than I'm using = >>> to try the xcp 1.5. >>> >>> Speed to the filer via the 10gig nic: >>> >>> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >>> >>> I would tend to conclude that there is something wrong with the = >>> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >>> >>> (Note that our Dell hardware is certified as supported by XenServer, = >>> so it seems not so true :/) >>> >>> modinfo for bnx2x on debian 6 >>> >>> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko >>> firmware: bnx2x-e1h-5.0.21.0.fw >>> firmware: bnx2x-e1-5.0.21.0.fw >>> version: 1.52.1 >>> license: GPL >>> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >>> author: Eliezer Tamir >>> srcversion: 050FF749F80E43CB5873BC9 >>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>> depends: mdio,libcrc32c >>> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = >>> (default)) (int) >>> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 = >>> (default is half number of CPUs) (int) >>> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 = >>> (default is half number of CPUs) (int) >>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >>> parm: dropless_fc: Pause on exhausted host ring (int) >>> parm: poll: Use polling (for debug) (int) >>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>> parm: debug: Default debug msglevel (int) >>> >>> modinfo for bnx2x on xcp 1.5 >>> >>> [root@xen-blade13 ~]# modinfo bnx2x >>> filename: = >>> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net/= bnx2x.ko >>> version: 1.62.17 >>> license: GPL >>> description: Broadcom NetXtreme II = >>> BCM57710/57711/57711E/57712/57712E Driver >>> author: Eliezer Tamir >>> srcversion: 13EA885EBE061121BAEC28D >>> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >>> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>> depends: mdio >>> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP = >>> mod_unload modversions Xen 686 >>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable = >>> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >>> parm: pri_map: Priority to HW queue mapping (int) >>> parm: qs_per_cos: Number of queues per HW queue (int) >>> parm: cos_min_rate: Weight for RR between HW queues (int) >>> parm: num_queues: Number of queues for multi_mode=3D1 = >>> (default is as a number of CPUs) (int) >>> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>> parm: int_mode: Force interrupt mode other than MSI-X (1 = >>> INT#x; 2 MSI) (int) >>> parm: dropless_fc: Pause on exhausted host ring (int) >>> parm: poll: Use polling (for debug) (int) >>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>> parm: debug: Default debug msglevel (int) >>> >>> Seems that the xcp 1.5 got a more recent version of the module. So = >>> that might not be the problem. >>> Maybe another problem in the kernel ? >>> >>> Any ideas how I could debug this ? >>> >>> Cheers, >>> S=E9bastien >>> >>> >>> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>>> Hi, >>>> >>>> I'm currently playing with XCP 1.5 beta on a Dell Blade = >>>> infrastructure that is linked to redundent filers with 10gbits NICs. >>>> >>>> The redundent 10gigs interfaces are not managed by xapi (i've told = >>>> xapi to forget them) and are configured like on any normal linux box. >>>> >>>> They are connected to the same 10gig switch where the filers are = >>>> connected to. >>>> >>>> Interfaces on the filers: >>>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> >>>> Interfaces on the blades: >>>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II = >>>> BCM57711 10-Gigabit PCIe >>>> >>>> The problem is that after some testing with iperf i get to this = >>>> conclusion: >>>> >>>> 1) Between the filers the speed is 9.9Gbit/s. >>>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is = >>>> quite poor >>>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is = >>>> quite poor (so that's not a new 1.5 bug) >>>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>>> >>>> Do you have any ideas what could be the problem ? knowing that = >>>> between the filers the speed is good and it's passing through the = >>>> same switch. >>>> >>>> Is there a DDK VM available for XCP 1.5 beta? I would like to try = >>>> to build the latest Broadcom drivers for these nics (bnx2x) for the = >>>> kernel used on xcp 1.5... >>>> >>>> In the meantime I will try to install a debian on another blade to = >>>> check if the speed are correct with the filers. >>>> >>>> Thanks, >>>> S=E9bastien >>>> >>>> >>>> _______________________________________________ >>>> 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 >> > > > _______________________________________________ > 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 Sun Apr 29 18:10:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 18:10:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOYa8-0000BH-Rh; Sun, 29 Apr 2012 18:10:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOYa8-0000BB-26 for xen-api@lists.xen.org; Sun, 29 Apr 2012 18:10:48 +0000 Received: from [85.158.143.99:56491] by server-2.bemta-4.messagelabs.com id 6C/E2-17550-7248D9F4; Sun, 29 Apr 2012 18:10:47 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1335723044!18235047!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25587 invoked from network); 29 Apr 2012 18:10:45 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-11.tower-216.messagelabs.com with SMTP; 29 Apr 2012 18:10:45 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Sun, 29 Apr 2012 10:59:32 -0700 Message-ID: <4F9D8184.5010509@holgerdanske.com> Date: Sun, 29 Apr 2012 10:59:32 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> In-Reply-To: <4F9D009C.9070307@gmail.com> Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 04/29/2012 01:49 AM, George Shuklin wrote: > I don't know about debian specific yet, but 'connection refused' means > xapi service is not running. Check it and it log (xensource.log). Thanks for the reply. :-) See console session, below. I don't see a 'xapi' service. I can't locate a 'xensource.log' file. Rummaging around yesterday, I recall seeing a message to the effect that xe/xapi won't work when xend is running; but, I don't recall where. David -- 2012-04-29 10:49:27 root@i72600s ~ # ps -A | egrep '(xen|xcp)' 40 ? 00:00:00 xenwatch 41 ? 00:00:00 xenbus 2195 ? 00:00:00 xcp-fe 2236 ? 00:00:00 xenstored 2246 ? 00:00:00 xenconsoled 2384 ? 00:00:00 xend 2385 ? 00:00:01 xend 2012-04-29 10:49:29 root@i72600s ~ # ll /var/log/x* -rw------- 1 root root 1231 Apr 29 10:16 /var/log/xcp-squeezed.log -rw------- 1 root root 728 Apr 29 10:16 /var/log/xcp-v6d.log /var/log/xen: total 100 drwxr-s--- 2 root adm 4096 Apr 27 23:09 ./ drwxr-xr-x 14 root root 45056 Apr 29 10:21 ../ -rw-r--r-- 1 root adm 17160 Apr 29 10:16 xend-debug.log -rw-r--r-- 1 root adm 17506 Apr 29 10:16 xend.log 2012-04-29 10:49:34 root@i72600s ~ # cat /var/log/xcp-squeezed.log [20120428T04:42:22.895Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T05:02:42.248Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T06:09:11.335Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T06:09:11.339Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 [20120428T19:09:29.414Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T19:09:29.417Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 [20120428T22:23:48.016Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T22:23:48.019Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 [20120428T22:39:57.607Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T22:39:57.610Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 [20120429T17:16:47.161Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120429T17:16:47.164Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 2012-04-29 10:49:39 root@i72600s ~ # cat /var/log/xcp-v6d.log [20120428T04:42:22.977Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T05:02:42.231Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T06:09:09.027Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T19:09:27.022Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T22:23:45.627Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T22:39:55.203Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120429T17:16:44.742Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 2012-04-29 10:49:46 root@i72600s ~ # tail -n 51 /var/log/xen/xend-debug.log Xend started at Sun Apr 29 10:16:45 2012. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory cat: /sys/bus/scsi/devices/host3/model: No such file or directory cat: /sys/bus/scsi/devices/host3/type: No such file or directory cat: /sys/bus/scsi/devices/host3/rev: No such file or directory cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory cat: /sys/bus/scsi/devices/host4/model: No such file or directory cat: /sys/bus/scsi/devices/host4/type: No such file or directory cat: /sys/bus/scsi/devices/host4/rev: No such file or directory cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory cat: /sys/bus/scsi/devices/host5/model: No such file or directory cat: /sys/bus/scsi/devices/host5/type: No such file or directory cat: /sys/bus/scsi/devices/host5/rev: No such file or directory cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory cat: /sys/bus/scsi/devices/host6/model: No such file or directory cat: /sys/bus/scsi/devices/host6/type: No such file or directory cat: /sys/bus/scsi/devices/host6/rev: No such file or directory cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host7/vendor: No such file or directory cat: /sys/bus/scsi/devices/host7/model: No such file or directory cat: /sys/bus/scsi/devices/host7/type: No such file or directory cat: /sys/bus/scsi/devices/host7/rev: No such file or directory cat: /sys/bus/scsi/devices/host7/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/scsi_level: No such file or directory 2012-04-29 10:49:56 root@i72600s ~ # tail -n 22 /var/log/xen/xend.log [2012-04-29 10:16:45 2385] INFO (SrvDaemon:332) Xend Daemon started [2012-04-29 10:16:45 2385] INFO (SrvDaemon:336) Xend changeset: unavailable. [2012-04-29 10:16:46 2385] DEBUG (XendNode:332) pscsi record count: 12 [2012-04-29 10:16:46 2385] DEBUG (XendCPUPool:747) recreate_active_pools [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:151) XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 14811733730L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 8, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1046144L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) [2012-04-29 10:16:46 2385] INFO (XendDomainInfo:169) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:3420) Storing VM details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0) (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': '255', 'bootloader': '', 'name': 'Domain-0'} [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1794) Storing domain details: {'cpu/3/availability': 'online', 'description': '', 'console/limit': '1048576', 'memory/target': '1046144', 'cpu/2/availability': 'online', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1', 'cpu/6/availability': 'online', 'console/type': 'xenconsoled', 'cpu/4/availability': 'online', 'name': 'Domain-0'} [2012-04-29 10:16:46 2385] DEBUG (XendDomain:476) Adding Domain: 0 [2012-04-29 10:16:46 2385] DEBUG (XendDomain:410) number of vcpus to use is 0 [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VBD.set_device not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VBD.set_type not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: session.get_all_records not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: event.get_record not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: event.get_all not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_device not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_MAC not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_MTU not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: debug.get_all not found [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. 2012-04-29 10:55:45 root@i72600s ~ # updatedb 2012-04-29 10:55:48 root@i72600s ~ # locate xensource.log _______________________________________________ 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 Sun Apr 29 18:10:56 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 18:10:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOYa8-0000BH-Rh; Sun, 29 Apr 2012 18:10:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOYa8-0000BB-26 for xen-api@lists.xen.org; Sun, 29 Apr 2012 18:10:48 +0000 Received: from [85.158.143.99:56491] by server-2.bemta-4.messagelabs.com id 6C/E2-17550-7248D9F4; Sun, 29 Apr 2012 18:10:47 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-11.tower-216.messagelabs.com!1335723044!18235047!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25587 invoked from network); 29 Apr 2012 18:10:45 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-11.tower-216.messagelabs.com with SMTP; 29 Apr 2012 18:10:45 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Sun, 29 Apr 2012 10:59:32 -0700 Message-ID: <4F9D8184.5010509@holgerdanske.com> Date: Sun, 29 Apr 2012 10:59:32 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> In-Reply-To: <4F9D009C.9070307@gmail.com> Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 04/29/2012 01:49 AM, George Shuklin wrote: > I don't know about debian specific yet, but 'connection refused' means > xapi service is not running. Check it and it log (xensource.log). Thanks for the reply. :-) See console session, below. I don't see a 'xapi' service. I can't locate a 'xensource.log' file. Rummaging around yesterday, I recall seeing a message to the effect that xe/xapi won't work when xend is running; but, I don't recall where. David -- 2012-04-29 10:49:27 root@i72600s ~ # ps -A | egrep '(xen|xcp)' 40 ? 00:00:00 xenwatch 41 ? 00:00:00 xenbus 2195 ? 00:00:00 xcp-fe 2236 ? 00:00:00 xenstored 2246 ? 00:00:00 xenconsoled 2384 ? 00:00:00 xend 2385 ? 00:00:01 xend 2012-04-29 10:49:29 root@i72600s ~ # ll /var/log/x* -rw------- 1 root root 1231 Apr 29 10:16 /var/log/xcp-squeezed.log -rw------- 1 root root 728 Apr 29 10:16 /var/log/xcp-v6d.log /var/log/xen: total 100 drwxr-s--- 2 root adm 4096 Apr 27 23:09 ./ drwxr-xr-x 14 root root 45056 Apr 29 10:21 ../ -rw-r--r-- 1 root adm 17160 Apr 29 10:16 xend-debug.log -rw-r--r-- 1 root adm 17506 Apr 29 10:16 xend.log 2012-04-29 10:49:34 root@i72600s ~ # cat /var/log/xcp-squeezed.log [20120428T04:42:22.895Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T05:02:42.248Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T06:09:11.335Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T06:09:11.339Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 [20120428T19:09:29.414Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T19:09:29.417Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 [20120428T22:23:48.016Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T22:23:48.019Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 [20120428T22:39:57.607Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120428T22:39:57.610Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 [20120429T17:16:47.161Z|debug|i72600s|0||xenstore-rpc] Writing reserved-host-memory=9216 KiB [20120429T17:16:47.164Z|debug|i72600s|0||xenstore-rpc] Starting daemon listening on squeezed with idle_timeout = 10 2012-04-29 10:49:39 root@i72600s ~ # cat /var/log/xcp-v6d.log [20120428T04:42:22.977Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T05:02:42.231Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T06:09:09.027Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T19:09:27.022Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T22:23:45.627Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120428T22:39:55.203Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 [20120429T17:16:44.742Z|debug|i72600s|0||http] Establishing Unix domain server on path: /var/lib/xcp/v6 2012-04-29 10:49:46 root@i72600s ~ # tail -n 51 /var/log/xen/xend-debug.log Xend started at Sun Apr 29 10:16:45 2012. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory cat: /sys/bus/scsi/devices/host3/model: No such file or directory cat: /sys/bus/scsi/devices/host3/type: No such file or directory cat: /sys/bus/scsi/devices/host3/rev: No such file or directory cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory cat: /sys/bus/scsi/devices/host4/model: No such file or directory cat: /sys/bus/scsi/devices/host4/type: No such file or directory cat: /sys/bus/scsi/devices/host4/rev: No such file or directory cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory cat: /sys/bus/scsi/devices/host5/model: No such file or directory cat: /sys/bus/scsi/devices/host5/type: No such file or directory cat: /sys/bus/scsi/devices/host5/rev: No such file or directory cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory cat: /sys/bus/scsi/devices/host6/model: No such file or directory cat: /sys/bus/scsi/devices/host6/type: No such file or directory cat: /sys/bus/scsi/devices/host6/rev: No such file or directory cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host7/vendor: No such file or directory cat: /sys/bus/scsi/devices/host7/model: No such file or directory cat: /sys/bus/scsi/devices/host7/type: No such file or directory cat: /sys/bus/scsi/devices/host7/rev: No such file or directory cat: /sys/bus/scsi/devices/host7/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target4:0:0/scsi_level: No such file or directory 2012-04-29 10:49:56 root@i72600s ~ # tail -n 22 /var/log/xen/xend.log [2012-04-29 10:16:45 2385] INFO (SrvDaemon:332) Xend Daemon started [2012-04-29 10:16:45 2385] INFO (SrvDaemon:336) Xend changeset: unavailable. [2012-04-29 10:16:46 2385] DEBUG (XendNode:332) pscsi record count: 12 [2012-04-29 10:16:46 2385] DEBUG (XendCPUPool:747) recreate_active_pools [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:151) XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 14811733730L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 8, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1046144L, 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) [2012-04-29 10:16:46 2385] INFO (XendDomainInfo:169) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:3420) Storing VM details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0) (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': '255', 'bootloader': '', 'name': 'Domain-0'} [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1794) Storing domain details: {'cpu/3/availability': 'online', 'description': '', 'console/limit': '1048576', 'memory/target': '1046144', 'cpu/2/availability': 'online', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1', 'cpu/6/availability': 'online', 'console/type': 'xenconsoled', 'cpu/4/availability': 'online', 'name': 'Domain-0'} [2012-04-29 10:16:46 2385] DEBUG (XendDomain:476) Adding Domain: 0 [2012-04-29 10:16:46 2385] DEBUG (XendDomain:410) number of vcpus to use is 0 [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VBD.set_device not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VBD.set_type not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: session.get_all_records not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: event.get_record not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: event.get_all not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_device not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_MAC not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_MTU not found [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: debug.get_all not found [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. 2012-04-29 10:55:45 root@i72600s ~ # updatedb 2012-04-29 10:55:48 root@i72600s ~ # locate xensource.log _______________________________________________ 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 Sun Apr 29 20:04:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 20:04:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOaM7-0000sL-TY; Sun, 29 Apr 2012 20:04:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOaM5-0000sF-Ra for xen-api@lists.xen.org; Sun, 29 Apr 2012 20:04:26 +0000 Received: from [85.158.138.51:63633] by server-4.bemta-3.messagelabs.com id E6/3F-15341-8CE9D9F4; Sun, 29 Apr 2012 20:04:24 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1335729862!22558294!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9839 invoked from network); 29 Apr 2012 20:04:22 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2012 20:04:22 -0000 Received: by lahe6 with SMTP id e6so1846149lah.32 for ; Sun, 29 Apr 2012 13:04:22 -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=2YPt5E4DUq20uPbZ0+PMKgSIAie9UTURmLzVn8+0yOk=; b=js5Dj0b+oxZY/qPW/SdL+GGx1NgWzmcvJdi+PZD5UP7xfky6xPp0sG0FhKHw/oEh4u zFfbkSXbuGg/vJTaAdR3b9Yn8/fdFuot61QRJ0Wrnx7Rygr3z8ikxdZ9v92Q7PtKkoSe m65XkxU/dC+7pmujn+pZME+aZjYXo5zXDwdIRanRHoufSQEkzyu9a58ZSUSsg8OQPe2k s9zEGI7e+R/inMAjA7yg+nkFen9I4Dk7P4Cso0jpT6eOJbRKMBViVsoRMUwHkEs0skyZ /8Tr4LDKCNqPSWYYtj5/Fxc3R9OZ3okmqIPCK5Q2aPI5UIEcKjco0uoqB0K9+7kftkPj sJXQ== Received: by 10.152.111.41 with SMTP id if9mr17622618lab.19.1335729861883; Sun, 29 Apr 2012 13:04:21 -0700 (PDT) Received: from [192.168.0.103] ([217.145.22.2]) by mx.google.com with ESMTPS id gw17sm14204498lab.11.2012.04.29.13.04.18 (version=SSLv3 cipher=OTHER); Sun, 29 Apr 2012 13:04:20 -0700 (PDT) Message-ID: <4F9D9EC0.8060500@gmail.com> Date: Mon, 30 Apr 2012 00:04:16 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> <4F9D8184.5010509@holgerdanske.com> In-Reply-To: <4F9D8184.5010509@holgerdanske.com> Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 no 'xapi' service means no 'xcp' at all. 90% of functionality provided by it. Try to /etc/init.d/xapi start (or xcp-xapi start). I saw 'xend' log noted below. If this is not from older tests, you need to disable xend service to run xapi. Use command "update-rc.d xend remove" and try to start xapi again. On 29.04.2012 21:59, David Christensen wrote: > On 04/29/2012 01:49 AM, George Shuklin wrote: >> I don't know about debian specific yet, but 'connection refused' means >> xapi service is not running. Check it and it log (xensource.log). > > Thanks for the reply. :-) See console session, below. > > > I don't see a 'xapi' service. > > > I can't locate a 'xensource.log' file. > > > Rummaging around yesterday, I recall seeing a message to the effect > that xe/xapi won't work when xend is running; but, I don't recall where. > > > David > > -- > > 2012-04-29 10:49:27 root@i72600s ~ > # ps -A | egrep '(xen|xcp)' > 40 ? 00:00:00 xenwatch > 41 ? 00:00:00 xenbus > 2195 ? 00:00:00 xcp-fe > 2236 ? 00:00:00 xenstored > 2246 ? 00:00:00 xenconsoled > 2384 ? 00:00:00 xend > 2385 ? 00:00:01 xend > > 2012-04-29 10:49:29 root@i72600s ~ > # ll /var/log/x* > -rw------- 1 root root 1231 Apr 29 10:16 /var/log/xcp-squeezed.log > -rw------- 1 root root 728 Apr 29 10:16 /var/log/xcp-v6d.log > > /var/log/xen: > total 100 > drwxr-s--- 2 root adm 4096 Apr 27 23:09 ./ > drwxr-xr-x 14 root root 45056 Apr 29 10:21 ../ > -rw-r--r-- 1 root adm 17160 Apr 29 10:16 xend-debug.log > -rw-r--r-- 1 root adm 17506 Apr 29 10:16 xend.log > > 2012-04-29 10:49:34 root@i72600s ~ > # cat /var/log/xcp-squeezed.log > [20120428T04:42:22.895Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T05:02:42.248Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T06:09:11.335Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T06:09:11.339Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > [20120428T19:09:29.414Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T19:09:29.417Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > [20120428T22:23:48.016Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T22:23:48.019Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > [20120428T22:39:57.607Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T22:39:57.610Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > [20120429T17:16:47.161Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120429T17:16:47.164Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > > 2012-04-29 10:49:39 root@i72600s ~ > # cat /var/log/xcp-v6d.log > [20120428T04:42:22.977Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T05:02:42.231Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T06:09:09.027Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T19:09:27.022Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T22:23:45.627Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T22:39:55.203Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120429T17:16:44.742Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > > 2012-04-29 10:49:46 root@i72600s ~ > # tail -n 51 /var/log/xen/xend-debug.log > Xend started at Sun Apr 29 10:16:45 2012. > cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host0/model: No such file or directory > cat: /sys/bus/scsi/devices/host0/type: No such file or directory > cat: /sys/bus/scsi/devices/host0/rev: No such file or directory > cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host1/model: No such file or directory > cat: /sys/bus/scsi/devices/host1/type: No such file or directory > cat: /sys/bus/scsi/devices/host1/rev: No such file or directory > cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host2/model: No such file or directory > cat: /sys/bus/scsi/devices/host2/type: No such file or directory > cat: /sys/bus/scsi/devices/host2/rev: No such file or directory > cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host3/model: No such file or directory > cat: /sys/bus/scsi/devices/host3/type: No such file or directory > cat: /sys/bus/scsi/devices/host3/rev: No such file or directory > cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host4/model: No such file or directory > cat: /sys/bus/scsi/devices/host4/type: No such file or directory > cat: /sys/bus/scsi/devices/host4/rev: No such file or directory > cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host5/model: No such file or directory > cat: /sys/bus/scsi/devices/host5/type: No such file or directory > cat: /sys/bus/scsi/devices/host5/rev: No such file or directory > cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host6/model: No such file or directory > cat: /sys/bus/scsi/devices/host6/type: No such file or directory > cat: /sys/bus/scsi/devices/host6/rev: No such file or directory > cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host7/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host7/model: No such file or directory > cat: /sys/bus/scsi/devices/host7/type: No such file or directory > cat: /sys/bus/scsi/devices/host7/rev: No such file or directory > cat: /sys/bus/scsi/devices/host7/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or > directory > cat: /sys/bus/scsi/devices/target4:0:0/vendor: No such file or directory > cat: /sys/bus/scsi/devices/target4:0:0/model: No such file or directory > cat: /sys/bus/scsi/devices/target4:0:0/type: No such file or directory > cat: /sys/bus/scsi/devices/target4:0:0/rev: No such file or directory > cat: /sys/bus/scsi/devices/target4:0:0/scsi_level: No such file or > directory > > 2012-04-29 10:49:56 root@i72600s ~ > # tail -n 22 /var/log/xen/xend.log > [2012-04-29 10:16:45 2385] INFO (SrvDaemon:332) Xend Daemon started > [2012-04-29 10:16:45 2385] INFO (SrvDaemon:336) Xend changeset: > unavailable. > [2012-04-29 10:16:46 2385] DEBUG (XendNode:332) pscsi record count: 12 > [2012-04-29 10:16:46 2385] DEBUG (XendCPUPool:747) recreate_active_pools > [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:151) > XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 14811733730L, > 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, > 'online_vcpus': 8, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': > 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1046144L, > 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, > 0], 'cpupool': 0, 'name': 'Domain-0'}) > [2012-04-29 10:16:46 2385] INFO (XendDomainInfo:169) Recreating domain > 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 > [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:3420) Storing VM > details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', > 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', > 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0) > (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', > 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': > 'restart', 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': > '255', 'bootloader': '', 'name': 'Domain-0'} > [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1794) Storing domain > details: {'cpu/3/availability': 'online', 'description': '', > 'console/limit': '1048576', 'memory/target': '1046144', > 'cpu/2/availability': 'online', 'vm': > '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', > 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', > 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', > 'control/platform-feature-multiprocessor-suspend': '1', > 'cpu/6/availability': 'online', 'console/type': 'xenconsoled', > 'cpu/4/availability': 'online', 'name': 'Domain-0'} > [2012-04-29 10:16:46 2385] DEBUG (XendDomain:476) Adding Domain: 0 > [2012-04-29 10:16:46 2385] DEBUG (XendDomain:410) number of vcpus to > use is 0 > [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1881) > XendDomainInfo.handleShutdownWatch > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > VBD.set_device not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > VBD.set_type not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > session.get_all_records not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > event.get_record not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > event.get_all not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > VIF.set_device not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_MAC > not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_MTU > not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > debug.get_all not found > [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix domain > socket XML-RPC server on /var/run/xend/xen-api.sock; authentication > has been disabled for this server. > [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix domain > socket XML-RPC server on /var/run/xend/xmlrpc.sock. > > 2012-04-29 10:55:45 root@i72600s ~ > # updatedb > > 2012-04-29 10:55:48 root@i72600s ~ > # locate xensource.log > > _______________________________________________ > 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 Sun Apr 29 20:04:34 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 20:04:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOaM7-0000sL-TY; Sun, 29 Apr 2012 20:04:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOaM5-0000sF-Ra for xen-api@lists.xen.org; Sun, 29 Apr 2012 20:04:26 +0000 Received: from [85.158.138.51:63633] by server-4.bemta-3.messagelabs.com id E6/3F-15341-8CE9D9F4; Sun, 29 Apr 2012 20:04:24 +0000 X-Env-Sender: george.shuklin@gmail.com X-Msg-Ref: server-15.tower-174.messagelabs.com!1335729862!22558294!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.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9839 invoked from network); 29 Apr 2012 20:04:22 -0000 Received: from mail-lpp01m010-f45.google.com (HELO mail-lpp01m010-f45.google.com) (209.85.215.45) by server-15.tower-174.messagelabs.com with RC4-SHA encrypted SMTP; 29 Apr 2012 20:04:22 -0000 Received: by lahe6 with SMTP id e6so1846149lah.32 for ; Sun, 29 Apr 2012 13:04:22 -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=2YPt5E4DUq20uPbZ0+PMKgSIAie9UTURmLzVn8+0yOk=; b=js5Dj0b+oxZY/qPW/SdL+GGx1NgWzmcvJdi+PZD5UP7xfky6xPp0sG0FhKHw/oEh4u zFfbkSXbuGg/vJTaAdR3b9Yn8/fdFuot61QRJ0Wrnx7Rygr3z8ikxdZ9v92Q7PtKkoSe m65XkxU/dC+7pmujn+pZME+aZjYXo5zXDwdIRanRHoufSQEkzyu9a58ZSUSsg8OQPe2k s9zEGI7e+R/inMAjA7yg+nkFen9I4Dk7P4Cso0jpT6eOJbRKMBViVsoRMUwHkEs0skyZ /8Tr4LDKCNqPSWYYtj5/Fxc3R9OZ3okmqIPCK5Q2aPI5UIEcKjco0uoqB0K9+7kftkPj sJXQ== Received: by 10.152.111.41 with SMTP id if9mr17622618lab.19.1335729861883; Sun, 29 Apr 2012 13:04:21 -0700 (PDT) Received: from [192.168.0.103] ([217.145.22.2]) by mx.google.com with ESMTPS id gw17sm14204498lab.11.2012.04.29.13.04.18 (version=SSLv3 cipher=OTHER); Sun, 29 Apr 2012 13:04:20 -0700 (PDT) Message-ID: <4F9D9EC0.8060500@gmail.com> Date: Mon, 30 Apr 2012 00:04:16 +0400 From: George Shuklin User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> <4F9D8184.5010509@holgerdanske.com> In-Reply-To: <4F9D8184.5010509@holgerdanske.com> Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 no 'xapi' service means no 'xcp' at all. 90% of functionality provided by it. Try to /etc/init.d/xapi start (or xcp-xapi start). I saw 'xend' log noted below. If this is not from older tests, you need to disable xend service to run xapi. Use command "update-rc.d xend remove" and try to start xapi again. On 29.04.2012 21:59, David Christensen wrote: > On 04/29/2012 01:49 AM, George Shuklin wrote: >> I don't know about debian specific yet, but 'connection refused' means >> xapi service is not running. Check it and it log (xensource.log). > > Thanks for the reply. :-) See console session, below. > > > I don't see a 'xapi' service. > > > I can't locate a 'xensource.log' file. > > > Rummaging around yesterday, I recall seeing a message to the effect > that xe/xapi won't work when xend is running; but, I don't recall where. > > > David > > -- > > 2012-04-29 10:49:27 root@i72600s ~ > # ps -A | egrep '(xen|xcp)' > 40 ? 00:00:00 xenwatch > 41 ? 00:00:00 xenbus > 2195 ? 00:00:00 xcp-fe > 2236 ? 00:00:00 xenstored > 2246 ? 00:00:00 xenconsoled > 2384 ? 00:00:00 xend > 2385 ? 00:00:01 xend > > 2012-04-29 10:49:29 root@i72600s ~ > # ll /var/log/x* > -rw------- 1 root root 1231 Apr 29 10:16 /var/log/xcp-squeezed.log > -rw------- 1 root root 728 Apr 29 10:16 /var/log/xcp-v6d.log > > /var/log/xen: > total 100 > drwxr-s--- 2 root adm 4096 Apr 27 23:09 ./ > drwxr-xr-x 14 root root 45056 Apr 29 10:21 ../ > -rw-r--r-- 1 root adm 17160 Apr 29 10:16 xend-debug.log > -rw-r--r-- 1 root adm 17506 Apr 29 10:16 xend.log > > 2012-04-29 10:49:34 root@i72600s ~ > # cat /var/log/xcp-squeezed.log > [20120428T04:42:22.895Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T05:02:42.248Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T06:09:11.335Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T06:09:11.339Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > [20120428T19:09:29.414Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T19:09:29.417Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > [20120428T22:23:48.016Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T22:23:48.019Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > [20120428T22:39:57.607Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120428T22:39:57.610Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > [20120429T17:16:47.161Z|debug|i72600s|0||xenstore-rpc] Writing > reserved-host-memory=9216 KiB > [20120429T17:16:47.164Z|debug|i72600s|0||xenstore-rpc] Starting daemon > listening on squeezed with idle_timeout = 10 > > 2012-04-29 10:49:39 root@i72600s ~ > # cat /var/log/xcp-v6d.log > [20120428T04:42:22.977Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T05:02:42.231Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T06:09:09.027Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T19:09:27.022Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T22:23:45.627Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120428T22:39:55.203Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > [20120429T17:16:44.742Z|debug|i72600s|0||http] Establishing Unix > domain server on path: /var/lib/xcp/v6 > > 2012-04-29 10:49:46 root@i72600s ~ > # tail -n 51 /var/log/xen/xend-debug.log > Xend started at Sun Apr 29 10:16:45 2012. > cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host0/model: No such file or directory > cat: /sys/bus/scsi/devices/host0/type: No such file or directory > cat: /sys/bus/scsi/devices/host0/rev: No such file or directory > cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host1/model: No such file or directory > cat: /sys/bus/scsi/devices/host1/type: No such file or directory > cat: /sys/bus/scsi/devices/host1/rev: No such file or directory > cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host2/model: No such file or directory > cat: /sys/bus/scsi/devices/host2/type: No such file or directory > cat: /sys/bus/scsi/devices/host2/rev: No such file or directory > cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host3/model: No such file or directory > cat: /sys/bus/scsi/devices/host3/type: No such file or directory > cat: /sys/bus/scsi/devices/host3/rev: No such file or directory > cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host4/model: No such file or directory > cat: /sys/bus/scsi/devices/host4/type: No such file or directory > cat: /sys/bus/scsi/devices/host4/rev: No such file or directory > cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host5/model: No such file or directory > cat: /sys/bus/scsi/devices/host5/type: No such file or directory > cat: /sys/bus/scsi/devices/host5/rev: No such file or directory > cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host6/model: No such file or directory > cat: /sys/bus/scsi/devices/host6/type: No such file or directory > cat: /sys/bus/scsi/devices/host6/rev: No such file or directory > cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/host7/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host7/model: No such file or directory > cat: /sys/bus/scsi/devices/host7/type: No such file or directory > cat: /sys/bus/scsi/devices/host7/rev: No such file or directory > cat: /sys/bus/scsi/devices/host7/scsi_level: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory > cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or > directory > cat: /sys/bus/scsi/devices/target4:0:0/vendor: No such file or directory > cat: /sys/bus/scsi/devices/target4:0:0/model: No such file or directory > cat: /sys/bus/scsi/devices/target4:0:0/type: No such file or directory > cat: /sys/bus/scsi/devices/target4:0:0/rev: No such file or directory > cat: /sys/bus/scsi/devices/target4:0:0/scsi_level: No such file or > directory > > 2012-04-29 10:49:56 root@i72600s ~ > # tail -n 22 /var/log/xen/xend.log > [2012-04-29 10:16:45 2385] INFO (SrvDaemon:332) Xend Daemon started > [2012-04-29 10:16:45 2385] INFO (SrvDaemon:336) Xend changeset: > unavailable. > [2012-04-29 10:16:46 2385] DEBUG (XendNode:332) pscsi record count: 12 > [2012-04-29 10:16:46 2385] DEBUG (XendCPUPool:747) recreate_active_pools > [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:151) > XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 14811733730L, > 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, > 'online_vcpus': 8, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': > 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1046144L, > 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, > 0], 'cpupool': 0, 'name': 'Domain-0'}) > [2012-04-29 10:16:46 2385] INFO (XendDomainInfo:169) Recreating domain > 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 > [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:3420) Storing VM > details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', > 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', > 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0) > (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', > 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': > 'restart', 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': > '255', 'bootloader': '', 'name': 'Domain-0'} > [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1794) Storing domain > details: {'cpu/3/availability': 'online', 'description': '', > 'console/limit': '1048576', 'memory/target': '1046144', > 'cpu/2/availability': 'online', 'vm': > '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', > 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', > 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', > 'control/platform-feature-multiprocessor-suspend': '1', > 'cpu/6/availability': 'online', 'console/type': 'xenconsoled', > 'cpu/4/availability': 'online', 'name': 'Domain-0'} > [2012-04-29 10:16:46 2385] DEBUG (XendDomain:476) Adding Domain: 0 > [2012-04-29 10:16:46 2385] DEBUG (XendDomain:410) number of vcpus to > use is 0 > [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1881) > XendDomainInfo.handleShutdownWatch > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > VBD.set_device not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > VBD.set_type not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > session.get_all_records not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > event.get_record not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > event.get_all not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > VIF.set_device not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_MAC > not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: VIF.set_MTU > not found > [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: > debug.get_all not found > [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix domain > socket XML-RPC server on /var/run/xend/xen-api.sock; authentication > has been disabled for this server. > [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix domain > socket XML-RPC server on /var/run/xend/xmlrpc.sock. > > 2012-04-29 10:55:45 root@i72600s ~ > # updatedb > > 2012-04-29 10:55:48 root@i72600s ~ > # locate xensource.log > > _______________________________________________ > 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 Sun Apr 29 20:30:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 20:30: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 1SOal6-0001Hn-En; Sun, 29 Apr 2012 20:30:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOal4-0001Hi-NV for xen-api@lists.xen.org; Sun, 29 Apr 2012 20:30:15 +0000 Received: from [85.158.139.83:30403] by server-11.bemta-5.messagelabs.com id CE/77-12959-5D4AD9F4; Sun, 29 Apr 2012 20:30:13 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1335731410!22065197!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1107 invoked from network); 29 Apr 2012 20:30:11 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-7.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 20:30:11 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TKU8dT031496 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Apr 2012 22:30:08 +0200 Message-ID: <4F9DA4CE.2020800@swisscenter.com> Date: Sun, 29 Apr 2012 22:30:06 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: George Shuklin References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> <4F9D8184.5010509@holgerdanske.com> <4F9D9EC0.8060500@gmail.com> In-Reply-To: <4F9D9EC0.8060500@gmail.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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, Having installed xcp on debian 6 recently (today), I can confirm that = after installing xcp-xapi package does not disable xend (which is = installed by the xen-hypervisor package). 3044 ? S 0:00 /usr/bin/python2.7 /usr/lib/xen-4.1/bin/xend = start 3045 ? SLl 0:02 /usr/bin/python2.7 /usr/lib/xen-4.1/bin/xend = start This lead to a non fuctionnal xapi. You must stop the process and = removing it from boot. Maybe something that has to be fixed in next releases ? Cheers, S=E9bastien On 29.04.2012 22:04, George Shuklin wrote: > no 'xapi' service means no 'xcp' at all. 90% of functionality provided = > by it. Try to /etc/init.d/xapi start (or xcp-xapi start). > > I saw 'xend' log noted below. If this is not from older tests, you = > need to disable xend service to run xapi. Use command "update-rc.d = > xend remove" and try to start xapi again. > > On 29.04.2012 21:59, David Christensen wrote: >> On 04/29/2012 01:49 AM, George Shuklin wrote: >>> I don't know about debian specific yet, but 'connection refused' means >>> xapi service is not running. Check it and it log (xensource.log). >> >> Thanks for the reply. :-) See console session, below. >> >> >> I don't see a 'xapi' service. >> >> >> I can't locate a 'xensource.log' file. >> >> >> Rummaging around yesterday, I recall seeing a message to the effect = >> that xe/xapi won't work when xend is running; but, I don't recall where. >> >> >> David >> >> -- = >> >> 2012-04-29 10:49:27 root@i72600s ~ >> # ps -A | egrep '(xen|xcp)' >> 40 ? 00:00:00 xenwatch >> 41 ? 00:00:00 xenbus >> 2195 ? 00:00:00 xcp-fe >> 2236 ? 00:00:00 xenstored >> 2246 ? 00:00:00 xenconsoled >> 2384 ? 00:00:00 xend >> 2385 ? 00:00:01 xend >> >> 2012-04-29 10:49:29 root@i72600s ~ >> # ll /var/log/x* >> -rw------- 1 root root 1231 Apr 29 10:16 /var/log/xcp-squeezed.log >> -rw------- 1 root root 728 Apr 29 10:16 /var/log/xcp-v6d.log >> >> /var/log/xen: >> total 100 >> drwxr-s--- 2 root adm 4096 Apr 27 23:09 ./ >> drwxr-xr-x 14 root root 45056 Apr 29 10:21 ../ >> -rw-r--r-- 1 root adm 17160 Apr 29 10:16 xend-debug.log >> -rw-r--r-- 1 root adm 17506 Apr 29 10:16 xend.log >> >> 2012-04-29 10:49:34 root@i72600s ~ >> # cat /var/log/xcp-squeezed.log >> [20120428T04:42:22.895Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T05:02:42.248Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T06:09:11.335Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T06:09:11.339Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> [20120428T19:09:29.414Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T19:09:29.417Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> [20120428T22:23:48.016Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T22:23:48.019Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> [20120428T22:39:57.607Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T22:39:57.610Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> [20120429T17:16:47.161Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120429T17:16:47.164Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> >> 2012-04-29 10:49:39 root@i72600s ~ >> # cat /var/log/xcp-v6d.log >> [20120428T04:42:22.977Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T05:02:42.231Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T06:09:09.027Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T19:09:27.022Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T22:23:45.627Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T22:39:55.203Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120429T17:16:44.742Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> >> 2012-04-29 10:49:46 root@i72600s ~ >> # tail -n 51 /var/log/xen/xend-debug.log >> Xend started at Sun Apr 29 10:16:45 2012. >> cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host0/model: No such file or directory >> cat: /sys/bus/scsi/devices/host0/type: No such file or directory >> cat: /sys/bus/scsi/devices/host0/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host1/model: No such file or directory >> cat: /sys/bus/scsi/devices/host1/type: No such file or directory >> cat: /sys/bus/scsi/devices/host1/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host2/model: No such file or directory >> cat: /sys/bus/scsi/devices/host2/type: No such file or directory >> cat: /sys/bus/scsi/devices/host2/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host3/model: No such file or directory >> cat: /sys/bus/scsi/devices/host3/type: No such file or directory >> cat: /sys/bus/scsi/devices/host3/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host4/model: No such file or directory >> cat: /sys/bus/scsi/devices/host4/type: No such file or directory >> cat: /sys/bus/scsi/devices/host4/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host5/model: No such file or directory >> cat: /sys/bus/scsi/devices/host5/type: No such file or directory >> cat: /sys/bus/scsi/devices/host5/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host6/model: No such file or directory >> cat: /sys/bus/scsi/devices/host6/type: No such file or directory >> cat: /sys/bus/scsi/devices/host6/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host7/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host7/model: No such file or directory >> cat: /sys/bus/scsi/devices/host7/type: No such file or directory >> cat: /sys/bus/scsi/devices/host7/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host7/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or = >> directory >> cat: /sys/bus/scsi/devices/target4:0:0/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/target4:0:0/model: No such file or directory >> cat: /sys/bus/scsi/devices/target4:0:0/type: No such file or directory >> cat: /sys/bus/scsi/devices/target4:0:0/rev: No such file or directory >> cat: /sys/bus/scsi/devices/target4:0:0/scsi_level: No such file or = >> directory >> >> 2012-04-29 10:49:56 root@i72600s ~ >> # tail -n 22 /var/log/xen/xend.log >> [2012-04-29 10:16:45 2385] INFO (SrvDaemon:332) Xend Daemon started >> [2012-04-29 10:16:45 2385] INFO (SrvDaemon:336) Xend changeset: = >> unavailable. >> [2012-04-29 10:16:46 2385] DEBUG (XendNode:332) pscsi record count: 12 >> [2012-04-29 10:16:46 2385] DEBUG (XendCPUPool:747) recreate_active_pools >> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:151) = >> XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 14811733730L, = >> 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, = >> 'online_vcpus': 8, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': = >> 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1046144L, = >> 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, = >> 0], 'cpupool': 0, 'name': 'Domain-0'}) >> [2012-04-29 10:16:46 2385] INFO (XendDomainInfo:169) Recreating = >> domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 >> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:3420) Storing VM = >> details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', = >> 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', = >> 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0) = >> (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', = >> 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': = >> 'restart', 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': = >> '255', 'bootloader': '', 'name': 'Domain-0'} >> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1794) Storing domain = >> details: {'cpu/3/availability': 'online', 'description': '', = >> 'console/limit': '1048576', 'memory/target': '1046144', = >> 'cpu/2/availability': 'online', 'vm': = >> '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', = >> 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', = >> 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', = >> 'control/platform-feature-multiprocessor-suspend': '1', = >> 'cpu/6/availability': 'online', 'console/type': 'xenconsoled', = >> 'cpu/4/availability': 'online', 'name': 'Domain-0'} >> [2012-04-29 10:16:46 2385] DEBUG (XendDomain:476) Adding Domain: 0 >> [2012-04-29 10:16:46 2385] DEBUG (XendDomain:410) number of vcpus to = >> use is 0 >> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1881) = >> XendDomainInfo.handleShutdownWatch >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VBD.set_device not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VBD.set_type not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> session.get_all_records not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> event.get_record not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> event.get_all not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VIF.set_device not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VIF.set_MAC not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VIF.set_MTU not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> debug.get_all not found >> [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix = >> domain socket XML-RPC server on /var/run/xend/xen-api.sock; = >> authentication has been disabled for this server. >> [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix = >> domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. >> >> 2012-04-29 10:55:45 root@i72600s ~ >> # updatedb >> >> 2012-04-29 10:55:48 root@i72600s ~ >> # locate xensource.log >> >> _______________________________________________ >> 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 Sun Apr 29 20:30:24 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 20:30: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 1SOal6-0001Hn-En; Sun, 29 Apr 2012 20:30:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOal4-0001Hi-NV for xen-api@lists.xen.org; Sun, 29 Apr 2012 20:30:15 +0000 Received: from [85.158.139.83:30403] by server-11.bemta-5.messagelabs.com id CE/77-12959-5D4AD9F4; Sun, 29 Apr 2012 20:30:13 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-7.tower-182.messagelabs.com!1335731410!22065197!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1107 invoked from network); 29 Apr 2012 20:30:11 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-7.tower-182.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 20:30:11 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TKU8dT031496 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Apr 2012 22:30:08 +0200 Message-ID: <4F9DA4CE.2020800@swisscenter.com> Date: Sun, 29 Apr 2012 22:30:06 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: George Shuklin References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> <4F9D8184.5010509@holgerdanske.com> <4F9D9EC0.8060500@gmail.com> In-Reply-To: <4F9D9EC0.8060500@gmail.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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, Having installed xcp on debian 6 recently (today), I can confirm that = after installing xcp-xapi package does not disable xend (which is = installed by the xen-hypervisor package). 3044 ? S 0:00 /usr/bin/python2.7 /usr/lib/xen-4.1/bin/xend = start 3045 ? SLl 0:02 /usr/bin/python2.7 /usr/lib/xen-4.1/bin/xend = start This lead to a non fuctionnal xapi. You must stop the process and = removing it from boot. Maybe something that has to be fixed in next releases ? Cheers, S=E9bastien On 29.04.2012 22:04, George Shuklin wrote: > no 'xapi' service means no 'xcp' at all. 90% of functionality provided = > by it. Try to /etc/init.d/xapi start (or xcp-xapi start). > > I saw 'xend' log noted below. If this is not from older tests, you = > need to disable xend service to run xapi. Use command "update-rc.d = > xend remove" and try to start xapi again. > > On 29.04.2012 21:59, David Christensen wrote: >> On 04/29/2012 01:49 AM, George Shuklin wrote: >>> I don't know about debian specific yet, but 'connection refused' means >>> xapi service is not running. Check it and it log (xensource.log). >> >> Thanks for the reply. :-) See console session, below. >> >> >> I don't see a 'xapi' service. >> >> >> I can't locate a 'xensource.log' file. >> >> >> Rummaging around yesterday, I recall seeing a message to the effect = >> that xe/xapi won't work when xend is running; but, I don't recall where. >> >> >> David >> >> -- = >> >> 2012-04-29 10:49:27 root@i72600s ~ >> # ps -A | egrep '(xen|xcp)' >> 40 ? 00:00:00 xenwatch >> 41 ? 00:00:00 xenbus >> 2195 ? 00:00:00 xcp-fe >> 2236 ? 00:00:00 xenstored >> 2246 ? 00:00:00 xenconsoled >> 2384 ? 00:00:00 xend >> 2385 ? 00:00:01 xend >> >> 2012-04-29 10:49:29 root@i72600s ~ >> # ll /var/log/x* >> -rw------- 1 root root 1231 Apr 29 10:16 /var/log/xcp-squeezed.log >> -rw------- 1 root root 728 Apr 29 10:16 /var/log/xcp-v6d.log >> >> /var/log/xen: >> total 100 >> drwxr-s--- 2 root adm 4096 Apr 27 23:09 ./ >> drwxr-xr-x 14 root root 45056 Apr 29 10:21 ../ >> -rw-r--r-- 1 root adm 17160 Apr 29 10:16 xend-debug.log >> -rw-r--r-- 1 root adm 17506 Apr 29 10:16 xend.log >> >> 2012-04-29 10:49:34 root@i72600s ~ >> # cat /var/log/xcp-squeezed.log >> [20120428T04:42:22.895Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T05:02:42.248Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T06:09:11.335Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T06:09:11.339Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> [20120428T19:09:29.414Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T19:09:29.417Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> [20120428T22:23:48.016Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T22:23:48.019Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> [20120428T22:39:57.607Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120428T22:39:57.610Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> [20120429T17:16:47.161Z|debug|i72600s|0||xenstore-rpc] Writing = >> reserved-host-memory=3D9216 KiB >> [20120429T17:16:47.164Z|debug|i72600s|0||xenstore-rpc] Starting = >> daemon listening on squeezed with idle_timeout =3D 10 >> >> 2012-04-29 10:49:39 root@i72600s ~ >> # cat /var/log/xcp-v6d.log >> [20120428T04:42:22.977Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T05:02:42.231Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T06:09:09.027Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T19:09:27.022Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T22:23:45.627Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120428T22:39:55.203Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> [20120429T17:16:44.742Z|debug|i72600s|0||http] Establishing Unix = >> domain server on path: /var/lib/xcp/v6 >> >> 2012-04-29 10:49:46 root@i72600s ~ >> # tail -n 51 /var/log/xen/xend-debug.log >> Xend started at Sun Apr 29 10:16:45 2012. >> cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host0/model: No such file or directory >> cat: /sys/bus/scsi/devices/host0/type: No such file or directory >> cat: /sys/bus/scsi/devices/host0/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host1/model: No such file or directory >> cat: /sys/bus/scsi/devices/host1/type: No such file or directory >> cat: /sys/bus/scsi/devices/host1/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host2/model: No such file or directory >> cat: /sys/bus/scsi/devices/host2/type: No such file or directory >> cat: /sys/bus/scsi/devices/host2/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host3/model: No such file or directory >> cat: /sys/bus/scsi/devices/host3/type: No such file or directory >> cat: /sys/bus/scsi/devices/host3/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host4/model: No such file or directory >> cat: /sys/bus/scsi/devices/host4/type: No such file or directory >> cat: /sys/bus/scsi/devices/host4/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host5/model: No such file or directory >> cat: /sys/bus/scsi/devices/host5/type: No such file or directory >> cat: /sys/bus/scsi/devices/host5/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host6/model: No such file or directory >> cat: /sys/bus/scsi/devices/host6/type: No such file or directory >> cat: /sys/bus/scsi/devices/host6/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/host7/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host7/model: No such file or directory >> cat: /sys/bus/scsi/devices/host7/type: No such file or directory >> cat: /sys/bus/scsi/devices/host7/rev: No such file or directory >> cat: /sys/bus/scsi/devices/host7/scsi_level: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory >> cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or = >> directory >> cat: /sys/bus/scsi/devices/target4:0:0/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/target4:0:0/model: No such file or directory >> cat: /sys/bus/scsi/devices/target4:0:0/type: No such file or directory >> cat: /sys/bus/scsi/devices/target4:0:0/rev: No such file or directory >> cat: /sys/bus/scsi/devices/target4:0:0/scsi_level: No such file or = >> directory >> >> 2012-04-29 10:49:56 root@i72600s ~ >> # tail -n 22 /var/log/xen/xend.log >> [2012-04-29 10:16:45 2385] INFO (SrvDaemon:332) Xend Daemon started >> [2012-04-29 10:16:45 2385] INFO (SrvDaemon:336) Xend changeset: = >> unavailable. >> [2012-04-29 10:16:46 2385] DEBUG (XendNode:332) pscsi record count: 12 >> [2012-04-29 10:16:46 2385] DEBUG (XendCPUPool:747) recreate_active_pools >> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:151) = >> XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 14811733730L, = >> 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, = >> 'online_vcpus': 8, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': = >> 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1046144L, = >> 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, = >> 0], 'cpupool': 0, 'name': 'Domain-0'}) >> [2012-04-29 10:16:46 2385] INFO (XendDomainInfo:169) Recreating = >> domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 >> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:3420) Storing VM = >> details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', = >> 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', = >> 'on_reboot': 'restart', 'image': "(linux (kernel '') (superpages 0) = >> (nomigrate 0) (tsc_mode 0))", 'on_poweroff': 'destroy', = >> 'bootloader_args': '', 'on_xend_start': 'ignore', 'on_crash': = >> 'restart', 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': = >> '255', 'bootloader': '', 'name': 'Domain-0'} >> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1794) Storing domain = >> details: {'cpu/3/availability': 'online', 'description': '', = >> 'console/limit': '1048576', 'memory/target': '1046144', = >> 'cpu/2/availability': 'online', 'vm': = >> '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', = >> 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', = >> 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', = >> 'control/platform-feature-multiprocessor-suspend': '1', = >> 'cpu/6/availability': 'online', 'console/type': 'xenconsoled', = >> 'cpu/4/availability': 'online', 'name': 'Domain-0'} >> [2012-04-29 10:16:46 2385] DEBUG (XendDomain:476) Adding Domain: 0 >> [2012-04-29 10:16:46 2385] DEBUG (XendDomain:410) number of vcpus to = >> use is 0 >> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1881) = >> XendDomainInfo.handleShutdownWatch >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VBD.set_device not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VBD.set_type not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> session.get_all_records not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> event.get_record not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> event.get_all not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VIF.set_device not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VIF.set_MAC not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> VIF.set_MTU not found >> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >> debug.get_all not found >> [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix = >> domain socket XML-RPC server on /var/run/xend/xen-api.sock; = >> authentication has been disabled for this server. >> [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix = >> domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. >> >> 2012-04-29 10:55:45 root@i72600s ~ >> # updatedb >> >> 2012-04-29 10:55:48 root@i72600s ~ >> # locate xensource.log >> >> _______________________________________________ >> 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 Sun Apr 29 20:36:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 20:36: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 1SOaqZ-0001NW-3n; Sun, 29 Apr 2012 20:35:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOaqX-0001NR-Ey for xen-api@lists.xen.org; Sun, 29 Apr 2012 20:35:53 +0000 Received: from [85.158.143.99:51522] by server-3.bemta-4.messagelabs.com id 46/A5-05853-826AD9F4; Sun, 29 Apr 2012 20:35:52 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1335731750!25789320!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12943 invoked from network); 29 Apr 2012 20:35:51 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-9.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 20:35:51 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TKZmMd031982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Apr 2012 22:35:48 +0200 Message-ID: <4F9DA622.6070505@swisscenter.com> Date: Sun, 29 Apr 2012 22:35:46 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: George Shuklin References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> <4F9D8184.5010509@holgerdanske.com> <4F9D9EC0.8060500@gmail.com> <4F9DA4CE.2020800@swisscenter.com> In-Reply-To: <4F9DA4CE.2020800@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Okay, sorry I wrote to quickly. as I can read on the wiki you need to : sed -i -e 's/xend_start$/#xend_start/' -e 's/xend_stop$/#xend_stop/' /etc/i= nit.d/xend update-rc.d xendomains disable and also echo 'TOOLSTACK=3D"xapi"'> /etc/default/xen source: http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distributi= on Cheers, S=E9bastien On 29.04.2012 22:30, S=E9bastien Riccio wrote: > Hi, > > Having installed xcp on debian 6 recently (today), I can confirm that = > after installing xcp-xapi package does not disable xend (which is = > installed by the xen-hypervisor package). > > 3044 ? S 0:00 /usr/bin/python2.7 = > /usr/lib/xen-4.1/bin/xend start > 3045 ? SLl 0:02 /usr/bin/python2.7 = > /usr/lib/xen-4.1/bin/xend start > > This lead to a non fuctionnal xapi. You must stop the process and = > removing it from boot. > > Maybe something that has to be fixed in next releases ? > > Cheers, > S=E9bastien > > > On 29.04.2012 22:04, George Shuklin wrote: >> no 'xapi' service means no 'xcp' at all. 90% of functionality = >> provided by it. Try to /etc/init.d/xapi start (or xcp-xapi start). >> >> I saw 'xend' log noted below. If this is not from older tests, you = >> need to disable xend service to run xapi. Use command "update-rc.d = >> xend remove" and try to start xapi again. >> >> On 29.04.2012 21:59, David Christensen wrote: >>> On 04/29/2012 01:49 AM, George Shuklin wrote: >>>> I don't know about debian specific yet, but 'connection refused' means >>>> xapi service is not running. Check it and it log (xensource.log). >>> >>> Thanks for the reply. :-) See console session, below. >>> >>> >>> I don't see a 'xapi' service. >>> >>> >>> I can't locate a 'xensource.log' file. >>> >>> >>> Rummaging around yesterday, I recall seeing a message to the effect = >>> that xe/xapi won't work when xend is running; but, I don't recall = >>> where. >>> >>> >>> David >>> >>> -- = >>> >>> 2012-04-29 10:49:27 root@i72600s ~ >>> # ps -A | egrep '(xen|xcp)' >>> 40 ? 00:00:00 xenwatch >>> 41 ? 00:00:00 xenbus >>> 2195 ? 00:00:00 xcp-fe >>> 2236 ? 00:00:00 xenstored >>> 2246 ? 00:00:00 xenconsoled >>> 2384 ? 00:00:00 xend >>> 2385 ? 00:00:01 xend >>> >>> 2012-04-29 10:49:29 root@i72600s ~ >>> # ll /var/log/x* >>> -rw------- 1 root root 1231 Apr 29 10:16 /var/log/xcp-squeezed.log >>> -rw------- 1 root root 728 Apr 29 10:16 /var/log/xcp-v6d.log >>> >>> /var/log/xen: >>> total 100 >>> drwxr-s--- 2 root adm 4096 Apr 27 23:09 ./ >>> drwxr-xr-x 14 root root 45056 Apr 29 10:21 ../ >>> -rw-r--r-- 1 root adm 17160 Apr 29 10:16 xend-debug.log >>> -rw-r--r-- 1 root adm 17506 Apr 29 10:16 xend.log >>> >>> 2012-04-29 10:49:34 root@i72600s ~ >>> # cat /var/log/xcp-squeezed.log >>> [20120428T04:42:22.895Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T05:02:42.248Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T06:09:11.335Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T06:09:11.339Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> [20120428T19:09:29.414Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T19:09:29.417Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> [20120428T22:23:48.016Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T22:23:48.019Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> [20120428T22:39:57.607Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T22:39:57.610Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> [20120429T17:16:47.161Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120429T17:16:47.164Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> >>> 2012-04-29 10:49:39 root@i72600s ~ >>> # cat /var/log/xcp-v6d.log >>> [20120428T04:42:22.977Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T05:02:42.231Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T06:09:09.027Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T19:09:27.022Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T22:23:45.627Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T22:39:55.203Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120429T17:16:44.742Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> >>> 2012-04-29 10:49:46 root@i72600s ~ >>> # tail -n 51 /var/log/xen/xend-debug.log >>> Xend started at Sun Apr 29 10:16:45 2012. >>> cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or = >>> directory >>> cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory >>> cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory >>> cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or = >>> directory >>> cat: /sys/bus/scsi/devices/target4:0:0/vendor: No such file or = >>> directory >>> cat: /sys/bus/scsi/devices/target4:0:0/model: No such file or directory >>> cat: /sys/bus/scsi/devices/target4:0:0/type: No such file or directory >>> cat: /sys/bus/scsi/devices/target4:0:0/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/target4:0:0/scsi_level: No such file or = >>> directory >>> >>> 2012-04-29 10:49:56 root@i72600s ~ >>> # tail -n 22 /var/log/xen/xend.log >>> [2012-04-29 10:16:45 2385] INFO (SrvDaemon:332) Xend Daemon started >>> [2012-04-29 10:16:45 2385] INFO (SrvDaemon:336) Xend changeset: = >>> unavailable. >>> [2012-04-29 10:16:46 2385] DEBUG (XendNode:332) pscsi record count: 12 >>> [2012-04-29 10:16:46 2385] DEBUG (XendCPUPool:747) = >>> recreate_active_pools >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:151) = >>> XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 14811733730L, = >>> 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, = >>> 'online_vcpus': 8, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': = >>> 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1046144L, = >>> 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, = >>> 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) >>> [2012-04-29 10:16:46 2385] INFO (XendDomainInfo:169) Recreating = >>> domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:3420) Storing VM = >>> details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', = >>> 'shadow_memory': '0', 'uuid': = >>> '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', = >>> 'image': "(linux (kernel '') (superpages 0) (nomigrate 0) (tsc_mode = >>> 0))", 'on_poweroff': 'destroy', 'bootloader_args': '', = >>> 'on_xend_start': 'ignore', 'on_crash': 'restart', = >>> 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': '255', = >>> 'bootloader': '', 'name': 'Domain-0'} >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1794) Storing = >>> domain details: {'cpu/3/availability': 'online', 'description': '', = >>> 'console/limit': '1048576', 'memory/target': '1046144', = >>> 'cpu/2/availability': 'online', 'vm': = >>> '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', = >>> 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', = >>> 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', = >>> 'control/platform-feature-multiprocessor-suspend': '1', = >>> 'cpu/6/availability': 'online', 'console/type': 'xenconsoled', = >>> 'cpu/4/availability': 'online', 'name': 'Domain-0'} >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomain:476) Adding Domain: 0 >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomain:410) number of vcpus to = >>> use is 0 >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1881) = >>> XendDomainInfo.handleShutdownWatch >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VBD.set_device not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VBD.set_type not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> session.get_all_records not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> event.get_record not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> event.get_all not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VIF.set_device not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VIF.set_MAC not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VIF.set_MTU not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> debug.get_all not found >>> [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix = >>> domain socket XML-RPC server on /var/run/xend/xen-api.sock; = >>> authentication has been disabled for this server. >>> [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix = >>> domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. >>> >>> 2012-04-29 10:55:45 root@i72600s ~ >>> # updatedb >>> >>> 2012-04-29 10:55:48 root@i72600s ~ >>> # locate xensource.log >>> >>> _______________________________________________ >>> 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 > _______________________________________________ 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 Sun Apr 29 20:36:02 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 20:36: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 1SOaqZ-0001NW-3n; Sun, 29 Apr 2012 20:35:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOaqX-0001NR-Ey for xen-api@lists.xen.org; Sun, 29 Apr 2012 20:35:53 +0000 Received: from [85.158.143.99:51522] by server-3.bemta-4.messagelabs.com id 46/A5-05853-826AD9F4; Sun, 29 Apr 2012 20:35:52 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1335731750!25789320!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12943 invoked from network); 29 Apr 2012 20:35:51 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-9.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Apr 2012 20:35:51 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3TKZmMd031982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Apr 2012 22:35:48 +0200 Message-ID: <4F9DA622.6070505@swisscenter.com> Date: Sun, 29 Apr 2012 22:35:46 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: George Shuklin References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> <4F9D8184.5010509@holgerdanske.com> <4F9D9EC0.8060500@gmail.com> <4F9DA4CE.2020800@swisscenter.com> In-Reply-To: <4F9DA4CE.2020800@swisscenter.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Cc: xen-api@lists.xen.org Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Okay, sorry I wrote to quickly. as I can read on the wiki you need to : sed -i -e 's/xend_start$/#xend_start/' -e 's/xend_stop$/#xend_stop/' /etc/i= nit.d/xend update-rc.d xendomains disable and also echo 'TOOLSTACK=3D"xapi"'> /etc/default/xen source: http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distributi= on Cheers, S=E9bastien On 29.04.2012 22:30, S=E9bastien Riccio wrote: > Hi, > > Having installed xcp on debian 6 recently (today), I can confirm that = > after installing xcp-xapi package does not disable xend (which is = > installed by the xen-hypervisor package). > > 3044 ? S 0:00 /usr/bin/python2.7 = > /usr/lib/xen-4.1/bin/xend start > 3045 ? SLl 0:02 /usr/bin/python2.7 = > /usr/lib/xen-4.1/bin/xend start > > This lead to a non fuctionnal xapi. You must stop the process and = > removing it from boot. > > Maybe something that has to be fixed in next releases ? > > Cheers, > S=E9bastien > > > On 29.04.2012 22:04, George Shuklin wrote: >> no 'xapi' service means no 'xcp' at all. 90% of functionality = >> provided by it. Try to /etc/init.d/xapi start (or xcp-xapi start). >> >> I saw 'xend' log noted below. If this is not from older tests, you = >> need to disable xend service to run xapi. Use command "update-rc.d = >> xend remove" and try to start xapi again. >> >> On 29.04.2012 21:59, David Christensen wrote: >>> On 04/29/2012 01:49 AM, George Shuklin wrote: >>>> I don't know about debian specific yet, but 'connection refused' means >>>> xapi service is not running. Check it and it log (xensource.log). >>> >>> Thanks for the reply. :-) See console session, below. >>> >>> >>> I don't see a 'xapi' service. >>> >>> >>> I can't locate a 'xensource.log' file. >>> >>> >>> Rummaging around yesterday, I recall seeing a message to the effect = >>> that xe/xapi won't work when xend is running; but, I don't recall = >>> where. >>> >>> >>> David >>> >>> -- = >>> >>> 2012-04-29 10:49:27 root@i72600s ~ >>> # ps -A | egrep '(xen|xcp)' >>> 40 ? 00:00:00 xenwatch >>> 41 ? 00:00:00 xenbus >>> 2195 ? 00:00:00 xcp-fe >>> 2236 ? 00:00:00 xenstored >>> 2246 ? 00:00:00 xenconsoled >>> 2384 ? 00:00:00 xend >>> 2385 ? 00:00:01 xend >>> >>> 2012-04-29 10:49:29 root@i72600s ~ >>> # ll /var/log/x* >>> -rw------- 1 root root 1231 Apr 29 10:16 /var/log/xcp-squeezed.log >>> -rw------- 1 root root 728 Apr 29 10:16 /var/log/xcp-v6d.log >>> >>> /var/log/xen: >>> total 100 >>> drwxr-s--- 2 root adm 4096 Apr 27 23:09 ./ >>> drwxr-xr-x 14 root root 45056 Apr 29 10:21 ../ >>> -rw-r--r-- 1 root adm 17160 Apr 29 10:16 xend-debug.log >>> -rw-r--r-- 1 root adm 17506 Apr 29 10:16 xend.log >>> >>> 2012-04-29 10:49:34 root@i72600s ~ >>> # cat /var/log/xcp-squeezed.log >>> [20120428T04:42:22.895Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T05:02:42.248Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T06:09:11.335Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T06:09:11.339Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> [20120428T19:09:29.414Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T19:09:29.417Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> [20120428T22:23:48.016Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T22:23:48.019Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> [20120428T22:39:57.607Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120428T22:39:57.610Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> [20120429T17:16:47.161Z|debug|i72600s|0||xenstore-rpc] Writing = >>> reserved-host-memory=3D9216 KiB >>> [20120429T17:16:47.164Z|debug|i72600s|0||xenstore-rpc] Starting = >>> daemon listening on squeezed with idle_timeout =3D 10 >>> >>> 2012-04-29 10:49:39 root@i72600s ~ >>> # cat /var/log/xcp-v6d.log >>> [20120428T04:42:22.977Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T05:02:42.231Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T06:09:09.027Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T19:09:27.022Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T22:23:45.627Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120428T22:39:55.203Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> [20120429T17:16:44.742Z|debug|i72600s|0||http] Establishing Unix = >>> domain server on path: /var/lib/xcp/v6 >>> >>> 2012-04-29 10:49:46 root@i72600s ~ >>> # tail -n 51 /var/log/xen/xend-debug.log >>> Xend started at Sun Apr 29 10:16:45 2012. >>> cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host6/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/model: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/type: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/host7/scsi_level: No such file or directory >>> cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or = >>> directory >>> cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory >>> cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory >>> cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or = >>> directory >>> cat: /sys/bus/scsi/devices/target4:0:0/vendor: No such file or = >>> directory >>> cat: /sys/bus/scsi/devices/target4:0:0/model: No such file or directory >>> cat: /sys/bus/scsi/devices/target4:0:0/type: No such file or directory >>> cat: /sys/bus/scsi/devices/target4:0:0/rev: No such file or directory >>> cat: /sys/bus/scsi/devices/target4:0:0/scsi_level: No such file or = >>> directory >>> >>> 2012-04-29 10:49:56 root@i72600s ~ >>> # tail -n 22 /var/log/xen/xend.log >>> [2012-04-29 10:16:45 2385] INFO (SrvDaemon:332) Xend Daemon started >>> [2012-04-29 10:16:45 2385] INFO (SrvDaemon:336) Xend changeset: = >>> unavailable. >>> [2012-04-29 10:16:46 2385] DEBUG (XendNode:332) pscsi record count: 12 >>> [2012-04-29 10:16:46 2385] DEBUG (XendCPUPool:747) = >>> recreate_active_pools >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:151) = >>> XendDomainInfo.recreate({'max_vcpu_id': 7, 'cpu_time': 14811733730L, = >>> 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, = >>> 'online_vcpus': 8, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': = >>> 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 1046144L, = >>> 'blocked': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, = >>> 0, 0], 'cpupool': 0, 'name': 'Domain-0'}) >>> [2012-04-29 10:16:46 2385] INFO (XendDomainInfo:169) Recreating = >>> domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:3420) Storing VM = >>> details: {'on_xend_stop': 'ignore', 'pool_name': 'Pool-0', = >>> 'shadow_memory': '0', 'uuid': = >>> '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', = >>> 'image': "(linux (kernel '') (superpages 0) (nomigrate 0) (tsc_mode = >>> 0))", 'on_poweroff': 'destroy', 'bootloader_args': '', = >>> 'on_xend_start': 'ignore', 'on_crash': 'restart', = >>> 'xend/restart_count': '0', 'vcpus': '8', 'vcpu_avail': '255', = >>> 'bootloader': '', 'name': 'Domain-0'} >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1794) Storing = >>> domain details: {'cpu/3/availability': 'online', 'description': '', = >>> 'console/limit': '1048576', 'memory/target': '1046144', = >>> 'cpu/2/availability': 'online', 'vm': = >>> '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', = >>> 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', = >>> 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', = >>> 'control/platform-feature-multiprocessor-suspend': '1', = >>> 'cpu/6/availability': 'online', 'console/type': 'xenconsoled', = >>> 'cpu/4/availability': 'online', 'name': 'Domain-0'} >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomain:476) Adding Domain: 0 >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomain:410) number of vcpus to = >>> use is 0 >>> [2012-04-29 10:16:46 2385] DEBUG (XendDomainInfo:1881) = >>> XendDomainInfo.handleShutdownWatch >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VBD.set_device not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VBD.set_type not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> session.get_all_records not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> event.get_record not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> event.get_all not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VIF.set_device not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VIF.set_MAC not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> VIF.set_MTU not found >>> [2012-04-29 10:16:46 2385] WARNING (XendAPI:708) API call: = >>> debug.get_all not found >>> [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix = >>> domain socket XML-RPC server on /var/run/xend/xen-api.sock; = >>> authentication has been disabled for this server. >>> [2012-04-29 10:16:46 2385] INFO (XMLRPCServer:161) Opening Unix = >>> domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. >>> >>> 2012-04-29 10:55:45 root@i72600s ~ >>> # updatedb >>> >>> 2012-04-29 10:55:48 root@i72600s ~ >>> # locate xensource.log >>> >>> _______________________________________________ >>> 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 > _______________________________________________ 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 Sun Apr 29 23:25:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 23:25: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 1SOdUo-0001s5-VJ; Sun, 29 Apr 2012 23:25:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOdUo-0001s0-9w for xen-api@lists.xen.org; Sun, 29 Apr 2012 23:25:38 +0000 Received: from [85.158.138.51:61665] by server-6.bemta-3.messagelabs.com id 01/42-05145-1FDCD9F4; Sun, 29 Apr 2012 23:25:37 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1335741935!24348607!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9539 invoked from network); 29 Apr 2012 23:25:36 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-3.tower-174.messagelabs.com with SMTP; 29 Apr 2012 23:25:36 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Sun, 29 Apr 2012 16:25:28 -0700 Message-ID: <4F9DCDE7.3000101@holgerdanske.com> Date: Sun, 29 Apr 2012 16:25:27 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> <4F9D8184.5010509@holgerdanske.com> <4F9D9EC0.8060500@gmail.com> <4F9DA4CE.2020800@swisscenter.com> <4F9DA622.6070505@swisscenter.com> In-Reply-To: <4F9DA622.6070505@swisscenter.com> Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gMDQvMjkvMjAxMiAwMTowNCBQTSwgR2VvcmdlIFNodWtsaW4gd3JvdGU6Ck9uIDA0LzI5LzIw MTIgMDE6MzAgUE0sIFPDqWJhc3RpZW4gUmljY2lvIHdyb3RlOgpPbiAwNC8yOS8yMDEyIDAxOjM1 IFBNLCBTw6liYXN0aWVuIFJpY2NpbyB3cm90ZToKClRoYW5rcyBmb3IgdGhlIHJlcGxpZXMuICA6 LSkKCgpDb21tZW50aW5nLW91dCB4ZW5kX3N0YXJ0IGFuZCB4ZW5kX3N0b3AgaW4gL2V0Yy9pbml0 LmQveGVuZCBhbmQgc2V0dGluZyAKVE9PTFNUQUNLIGluIC9ldGMvZGVmYXVsdC94ZW4gd2VyZSB1 bmV2ZW50ZnVsLgoKClVwZGF0aW5nIHRoZSBpbml0IHNjcmlwdCBsaW5rcyBmb3IgeGVuZG9tYWlu cyBwcm9kdWNlZCBzb21lIHdhcm5pbmdzIAooc2VlIGJlbG93KS4KCgp4ZSBzZWVtcyB0byBiZSB3 b3JraW5nIG5vdy4gIDotKQoKCkRhdmlkCgotLQoKICAgICAgICAgMjAxMi0wNC0yOSAxNTo1MDo1 NiByb290QGk3MjYwMHMgL2V0Yy9pbml0LmQKICAgICAgICAgIyB1cGRhdGUtcmMuZCB4ZW5kb21h aW5zIGRpc2FibGUKICAgICAgICAgdXBkYXRlLXJjLmQ6IHVzaW5nIGRlcGVuZGVuY3kgYmFzZWQg Ym9vdCBzZXF1ZW5jaW5nCiAgICAgICAgIGluc3NlcnY6IHdhcm5pbmc6IGN1cnJlbnQgc3RhcnQg cnVubGV2ZWwocykgKGVtcHR5KSBvZiBzY3JpcHQgCmB4ZW5kb21haW5zJyBvdmVyd3JpdGVzIGRl ZmF1bHRzICgyIDMgNCA1KS4KICAgICAgICAgaW5zc2Vydjogd2FybmluZzogY3VycmVudCBzdG9w IHJ1bmxldmVsKHMpICgwIDEgMiAzIDQgNSA2KSBvZiAKc2NyaXB0IGB4ZW5kb21haW5zJyBvdmVy d3JpdGVzIGRlZmF1bHRzICgwIDEgNikuCiAgICAgICAgIGluc3NlcnY6IHNjcmlwdCB4ZW5kLW9y aWc6IHNlcnZpY2UgeGVuZCBhbHJlYWR5IHByb3ZpZGVkIQoKICAgICAgICAgMjAxMi0wNC0yOSAx NTo1NTowMyByb290QGk3MjYwMHMgL2V0YwogICAgICAgICAjIGZpbmQgL2V0YyAtbmFtZSAnKnhl bmQqJwogICAgICAgICAvZXRjL3JjMi5kL0swMXhlbmRvbWFpbnMKICAgICAgICAgL2V0Yy9yYzIu ZC9TMjB4ZW5kCiAgICAgICAgIC9ldGMvcmMwLmQvSzAxeGVuZG9tYWlucwogICAgICAgICAvZXRj L3JjMC5kL0swMnhlbmQKICAgICAgICAgL2V0Yy9yYzYuZC9LMDF4ZW5kb21haW5zCiAgICAgICAg IC9ldGMvcmM2LmQvSzAyeGVuZAogICAgICAgICAvZXRjL3JjNC5kL0swMXhlbmRvbWFpbnMKICAg ICAgICAgL2V0Yy9yYzQuZC9TMjB4ZW5kCiAgICAgICAgIC9ldGMveGVuL3hlbmQtY29uZmlnLnN4 cAogICAgICAgICAvZXRjL3hlbi94ZW5kLXBjaS1xdWlya3Muc3hwCiAgICAgICAgIC9ldGMveGVu L3hlbmQtcGNpLXBlcm1pc3NpdmUuc3hwCiAgICAgICAgIC9ldGMvZGVmYXVsdC94ZW5kb21haW5z CiAgICAgICAgIC9ldGMvZGVmYXVsdC94ZW5kCiAgICAgICAgIC9ldGMvcmMxLmQvSzAxeGVuZG9t YWlucwogICAgICAgICAvZXRjL3JjMS5kL0swMnhlbmQKICAgICAgICAgL2V0Yy9yYzUuZC9LMDF4 ZW5kb21haW5zCiAgICAgICAgIC9ldGMvcmM1LmQvUzIweGVuZAogICAgICAgICAvZXRjL2luaXQu ZC94ZW5kb21haW5zCiAgICAgICAgIC9ldGMvaW5pdC5kL3hlbmQtb3JpZwogICAgICAgICAvZXRj L2luaXQuZC94ZW5kCiAgICAgICAgIC9ldGMvcmMzLmQvSzAxeGVuZG9tYWlucwogICAgICAgICAv ZXRjL3JjMy5kL1MyMHhlbmQKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRw Oi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Sun Apr 29 23:25:47 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Sun, 29 Apr 2012 23:25: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 1SOdUo-0001s5-VJ; Sun, 29 Apr 2012 23:25:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOdUo-0001s0-9w for xen-api@lists.xen.org; Sun, 29 Apr 2012 23:25:38 +0000 Received: from [85.158.138.51:61665] by server-6.bemta-3.messagelabs.com id 01/42-05145-1FDCD9F4; Sun, 29 Apr 2012 23:25:37 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1335741935!24348607!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9539 invoked from network); 29 Apr 2012 23:25:36 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-3.tower-174.messagelabs.com with SMTP; 29 Apr 2012 23:25:36 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Sun, 29 Apr 2012 16:25:28 -0700 Message-ID: <4F9DCDE7.3000101@holgerdanske.com> Date: Sun, 29 Apr 2012 16:25:27 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org References: <4F9CA228.3040307@holgerdanske.com> <4F9D009C.9070307@gmail.com> <4F9D8184.5010509@holgerdanske.com> <4F9D9EC0.8060500@gmail.com> <4F9DA4CE.2020800@swisscenter.com> <4F9DA622.6070505@swisscenter.com> In-Reply-To: <4F9DA622.6070505@swisscenter.com> Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian xe Error: Connection refused (calling connect ) X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org T24gMDQvMjkvMjAxMiAwMTowNCBQTSwgR2VvcmdlIFNodWtsaW4gd3JvdGU6Ck9uIDA0LzI5LzIw MTIgMDE6MzAgUE0sIFPDqWJhc3RpZW4gUmljY2lvIHdyb3RlOgpPbiAwNC8yOS8yMDEyIDAxOjM1 IFBNLCBTw6liYXN0aWVuIFJpY2NpbyB3cm90ZToKClRoYW5rcyBmb3IgdGhlIHJlcGxpZXMuICA6 LSkKCgpDb21tZW50aW5nLW91dCB4ZW5kX3N0YXJ0IGFuZCB4ZW5kX3N0b3AgaW4gL2V0Yy9pbml0 LmQveGVuZCBhbmQgc2V0dGluZyAKVE9PTFNUQUNLIGluIC9ldGMvZGVmYXVsdC94ZW4gd2VyZSB1 bmV2ZW50ZnVsLgoKClVwZGF0aW5nIHRoZSBpbml0IHNjcmlwdCBsaW5rcyBmb3IgeGVuZG9tYWlu cyBwcm9kdWNlZCBzb21lIHdhcm5pbmdzIAooc2VlIGJlbG93KS4KCgp4ZSBzZWVtcyB0byBiZSB3 b3JraW5nIG5vdy4gIDotKQoKCkRhdmlkCgotLQoKICAgICAgICAgMjAxMi0wNC0yOSAxNTo1MDo1 NiByb290QGk3MjYwMHMgL2V0Yy9pbml0LmQKICAgICAgICAgIyB1cGRhdGUtcmMuZCB4ZW5kb21h aW5zIGRpc2FibGUKICAgICAgICAgdXBkYXRlLXJjLmQ6IHVzaW5nIGRlcGVuZGVuY3kgYmFzZWQg Ym9vdCBzZXF1ZW5jaW5nCiAgICAgICAgIGluc3NlcnY6IHdhcm5pbmc6IGN1cnJlbnQgc3RhcnQg cnVubGV2ZWwocykgKGVtcHR5KSBvZiBzY3JpcHQgCmB4ZW5kb21haW5zJyBvdmVyd3JpdGVzIGRl ZmF1bHRzICgyIDMgNCA1KS4KICAgICAgICAgaW5zc2Vydjogd2FybmluZzogY3VycmVudCBzdG9w IHJ1bmxldmVsKHMpICgwIDEgMiAzIDQgNSA2KSBvZiAKc2NyaXB0IGB4ZW5kb21haW5zJyBvdmVy d3JpdGVzIGRlZmF1bHRzICgwIDEgNikuCiAgICAgICAgIGluc3NlcnY6IHNjcmlwdCB4ZW5kLW9y aWc6IHNlcnZpY2UgeGVuZCBhbHJlYWR5IHByb3ZpZGVkIQoKICAgICAgICAgMjAxMi0wNC0yOSAx NTo1NTowMyByb290QGk3MjYwMHMgL2V0YwogICAgICAgICAjIGZpbmQgL2V0YyAtbmFtZSAnKnhl bmQqJwogICAgICAgICAvZXRjL3JjMi5kL0swMXhlbmRvbWFpbnMKICAgICAgICAgL2V0Yy9yYzIu ZC9TMjB4ZW5kCiAgICAgICAgIC9ldGMvcmMwLmQvSzAxeGVuZG9tYWlucwogICAgICAgICAvZXRj L3JjMC5kL0swMnhlbmQKICAgICAgICAgL2V0Yy9yYzYuZC9LMDF4ZW5kb21haW5zCiAgICAgICAg IC9ldGMvcmM2LmQvSzAyeGVuZAogICAgICAgICAvZXRjL3JjNC5kL0swMXhlbmRvbWFpbnMKICAg ICAgICAgL2V0Yy9yYzQuZC9TMjB4ZW5kCiAgICAgICAgIC9ldGMveGVuL3hlbmQtY29uZmlnLnN4 cAogICAgICAgICAvZXRjL3hlbi94ZW5kLXBjaS1xdWlya3Muc3hwCiAgICAgICAgIC9ldGMveGVu L3hlbmQtcGNpLXBlcm1pc3NpdmUuc3hwCiAgICAgICAgIC9ldGMvZGVmYXVsdC94ZW5kb21haW5z CiAgICAgICAgIC9ldGMvZGVmYXVsdC94ZW5kCiAgICAgICAgIC9ldGMvcmMxLmQvSzAxeGVuZG9t YWlucwogICAgICAgICAvZXRjL3JjMS5kL0swMnhlbmQKICAgICAgICAgL2V0Yy9yYzUuZC9LMDF4 ZW5kb21haW5zCiAgICAgICAgIC9ldGMvcmM1LmQvUzIweGVuZAogICAgICAgICAvZXRjL2luaXQu ZC94ZW5kb21haW5zCiAgICAgICAgIC9ldGMvaW5pdC5kL3hlbmQtb3JpZwogICAgICAgICAvZXRj L2luaXQuZC94ZW5kCiAgICAgICAgIC9ldGMvcmMzLmQvSzAxeGVuZG9tYWlucwogICAgICAgICAv ZXRjL3JjMy5kL1MyMHhlbmQKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fClhlbi1hcGkgbWFpbGluZyBsaXN0Clhlbi1hcGlAbGlzdHMueGVuLm9yZwpodHRw Oi8vbGlzdHMueGVuLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8veGVuLWFwaQo= From xen-api-bounces@lists.xen.org Mon Apr 30 00:59:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 00:59: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 1SOex1-0002Xh-R9; Mon, 30 Apr 2012 00:58:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOex0-0002Xc-93 for xen-api@lists.xen.org; Mon, 30 Apr 2012 00:58:50 +0000 Received: from [193.109.254.147:13659] by server-7.bemta-14.messagelabs.com id D3/E2-01627-9C3ED9F4; Mon, 30 Apr 2012 00:58:49 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1335747528!6860605!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8143 invoked from network); 30 Apr 2012 00:58:48 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-16.tower-27.messagelabs.com with SMTP; 30 Apr 2012 00:58:48 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Sun, 29 Apr 2012 17:58:37 -0700 Message-ID: <4F9DE3BD.1040806@holgerdanske.com> Date: Sun, 29 Apr 2012 17:58:37 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 xen-api: I'm attempting to follow along with the xcp-xapi README.Debian on Wheezy per: http://www.debian.org/News/2012/20120425 When I attempt to mount a directory that contains ISO images via NFS, the "xe-mount-iso-sr" command doesn't seem to exist: 2012-04-29 17:48:31 root@i72600s ~ # xe-mount-iso-sr -bash: xe-mount-iso-sr: command not found Using Bash tab completion, I don't see any xe-* commands: 2012-04-29 17:52:50 root@i72600s ~ # xe xe xenstore-chmod xenstore-watch xentrace_setsize xedit xenstore-exists xenstore-write xev xen xenstore-list xentop xeyes xend xenstore-ls xentrace xenperf xenstore-read xentrace_format xenpm xenstore-rm xentrace_setmask Searching the xe help page for anything related to ISO yields nothing: 2012-04-29 17:52:50 root@i72600s ~ # xe help --all | grep -i iso Same goes for the man page: 2012-04-29 17:56:47 root@i72600s ~ # export MANWIDTH=72; man xapi | grep -i iso and data centers by combining the isolation and multitenancy capabilities of the Xen hypervisor with enhanced security, mance and isolation across both private and public clouds. Any suggestions? TIA, David _______________________________________________ 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 Apr 30 00:59:00 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 00:59: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 1SOex1-0002Xh-R9; Mon, 30 Apr 2012 00:58:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOex0-0002Xc-93 for xen-api@lists.xen.org; Mon, 30 Apr 2012 00:58:50 +0000 Received: from [193.109.254.147:13659] by server-7.bemta-14.messagelabs.com id D3/E2-01627-9C3ED9F4; Mon, 30 Apr 2012 00:58:49 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1335747528!6860605!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8143 invoked from network); 30 Apr 2012 00:58:48 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-16.tower-27.messagelabs.com with SMTP; 30 Apr 2012 00:58:48 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Sun, 29 Apr 2012 17:58:37 -0700 Message-ID: <4F9DE3BD.1040806@holgerdanske.com> Date: Sun, 29 Apr 2012 17:58:37 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 xen-api: I'm attempting to follow along with the xcp-xapi README.Debian on Wheezy per: http://www.debian.org/News/2012/20120425 When I attempt to mount a directory that contains ISO images via NFS, the "xe-mount-iso-sr" command doesn't seem to exist: 2012-04-29 17:48:31 root@i72600s ~ # xe-mount-iso-sr -bash: xe-mount-iso-sr: command not found Using Bash tab completion, I don't see any xe-* commands: 2012-04-29 17:52:50 root@i72600s ~ # xe xe xenstore-chmod xenstore-watch xentrace_setsize xedit xenstore-exists xenstore-write xev xen xenstore-list xentop xeyes xend xenstore-ls xentrace xenperf xenstore-read xentrace_format xenpm xenstore-rm xentrace_setmask Searching the xe help page for anything related to ISO yields nothing: 2012-04-29 17:52:50 root@i72600s ~ # xe help --all | grep -i iso Same goes for the man page: 2012-04-29 17:56:47 root@i72600s ~ # export MANWIDTH=72; man xapi | grep -i iso and data centers by combining the isolation and multitenancy capabilities of the Xen hypervisor with enhanced security, mance and isolation across both private and public clouds. Any suggestions? TIA, David _______________________________________________ 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 Apr 30 08:46:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 08:46:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmFf-0002gB-Hg; Mon, 30 Apr 2012 08:46:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmFd-0002g6-UR for xen-api@lists.xensource.com; Mon, 30 Apr 2012 08:46:34 +0000 Received: from [193.109.254.147:4439] by server-12.bemta-14.messagelabs.com id 1E/39-05898-9615E9F4; Mon, 30 Apr 2012 08:46:33 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1335775591!84822!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7464 invoked from network); 30 Apr 2012 08:46:32 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2012 08:46:32 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3U8chBt028279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Apr 2012 10:38:43 +0200 Message-ID: <4F9E4F92.3080200@swisscenter.com> Date: Mon, 30 Apr 2012 10:38:42 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Uli_St=E4rk?= , "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com>, <4F9D7917.8060804@swisscenter.com> In-Reply-To: X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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, Yes I've almost tried everything that is on the network tweaking guide: http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide But the bottleneck seems to be the xen hypervisor used in xcp and xenserver. On the same machine but with xcp-xapi (over debian) I get almost normal = 10gbit/s speeds from dom0. What is kinda relevant is that even doing an iperf "localhost to = localhost" it's stuck to that 3gbit in a xcp or xenserver dom0... XCP: [root@xen-blade13 ~]# iperf -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 5001 ------------------------------------------------------------ [ 3] local 127.0.0.1 port 43138 connected with 127.0.0.1 port 5001 [ 3] 0.0-10.0 sec 3.43 GBytes 2.94 Gbits/sec Kronos (xapi on debian) root@xen-blade11:~# iperf -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 5001 ------------------------------------------------------------ [ 3] local 127.0.0.1 port 34438 connected with 127.0.0.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 18.9 GBytes 16.3 Gbits/sec So I'll never get more than 3gbit/s in one thread on xenserver or xcp... = and that is kinda ... bad :/ Not sure yet if it's a limitation of the dom0 kernel or the hypervisor = itself... I tend to think it's the hypervisor. xcp 1.5 host : xen-blade13 release : 2.6.32.12-0.7.1.xs1.4.90.530.170661xen version : #1 SMP Sat Apr 28 21:26:23 CEST 2012 machine : i686 nr_cpus : 16 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2394 hw_caps : = bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32758 free_memory : 31516 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 = hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xfdc00000 xen_changeset : unavailable xen_commandline : dom0_mem=3D752M lowmem_emergency_pool=3D1M = crashkernel=3D64M@32M console=3D vga=3Dmode-0x0311 dom0_max_vcpus=3D8 cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) cc_compile_by : root cc_compile_domain : uk.xensource.com cc_compile_date : Mon Feb 6 19:01:42 EST 2012 xend_config_format : 4 xcp-xapi (debian) host : xen-blade11 release : 3.2.0-2-686-pae version : #1 SMP Sun Apr 15 17:56:31 UTC 2012 machine : i686 nr_cpus : 8 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2394 hw_caps : = bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32758 free_memory : 30560 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 = hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xfdc00000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=3D1024M cc_compiler : gcc version 4.6.2 (Debian 4.6.2-6) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Sun Dec 11 13:32:25 UTC 2011 xend_config_format : 4 I see not much difference except 4.1.1 for xcp 4.1.2 for xcp-xapi with = same scheduler (credit) Also I found an old post (2008) of someone having the same symptoms back = in the years: http://old-list-archives.xen.org/archives/html/xen-users/2008-12/msg00508.h= tml but didn't find any follow ups ... Cheers, S=E9bastien On 30.04.2012 10:13, Uli St=E4rk wrote: > did you enable jumbo frames? > > ip link set eth2 mtu 9000 > > > ________________________________________ > Von: xen-api-bounces@lists.xen.org [xen-api-bounces@lists.xen.org]" = im Auftrag von"S=E9bastien Riccio [sr@swisscenter.com] > Gesendet: Sonntag, 29. April 2012 19:23 > Bis: xen-api@lists.xensource.com > Betreff: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit net= work cards > > Another discovery: > > On XCP 1.5 > > iperf on dom0 to localhost (loopback) > > Client connecting to localhost, TCP port 5001 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 38278 connected with 127.0.0.1 port 5001 > ^C[ 3] 0.0- 5.2 sec 1.79 GBytes 2.97 Gbits/sec > > Limited to 3gbit > > on xapi/debian > > root@kronos:~# iperf -c 10.50.50.111 > ------------------------------------------------------------ > Client connecting to 10.50.50.111, TCP port 5001 > TCP window size: 167 KByte (default) > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 41137 connected with 127.0.0.1 port 5001 > [ ID] Interval Transfer Bandwidth[ 3] 0.0- 5.6 sec 13.1 > GBytes 20.0 Gbits/sec > > clearly not a nic issue.... > > Cheers, > S=E9bastien > > > > > > > On 29.04.2012 17:28, S=E9bastien Riccio wrote: >> Me again (sorry), >> >> Still trying to sort things out to understand why it's slow under xcp, >> I've installed xcp on debian (project kronos), and did an iperf from dom0 >> >> [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec >> [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec >> [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec >> [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec >> >> It's not getting to the 10gibt/s so it looks that it's related to the >> xen hypervisor. >> But it still 2x better than with xcp/xenserver. >> >> Any ideas how to improve this? >> >> Cheers, >> S=E9bastien >> >> On 29.04.2012 14:44, S=E9bastien Riccio wrote: >>> Hi again, again :) >>> >>> Something strange : >>> >>> If i issue parallel threads with iperf (8 in this example, the >>> 10Gbit/s speed is reached) >>> >>> [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec >>> [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>> [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec >>> [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec >>> [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec >>> [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec >>> [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>> [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec >>> [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec >>> >>> So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? >>> It's really not efficient as we connect the iscsi storage to the >>> filer from dom0, so it will always be a single thread, so no >>> possibility to get the full 10Gbit bw for our storage. >>> >>> Is there a way to get rid of that (bug?) limitation ? >>> >>> Cheers, >>> S=E9bastien >>> >>> >>> >>> >>> On 29.04.2012 14:23, S=E9bastien Riccio wrote: >>>> Hi again, >>>> >>>> So I did my test with a debian 6 on the same hardware than I'm using >>>> to try the xcp 1.5. >>>> >>>> Speed to the filer via the 10gig nic: >>>> >>>> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >>>> >>>> I would tend to conclude that there is something wrong with the >>>> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >>>> >>>> (Note that our Dell hardware is certified as supported by XenServer, >>>> so it seems not so true :/) >>>> >>>> modinfo for bnx2x on debian 6 >>>> >>>> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko >>>> firmware: bnx2x-e1h-5.0.21.0.fw >>>> firmware: bnx2x-e1-5.0.21.0.fw >>>> version: 1.52.1 >>>> license: GPL >>>> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >>>> author: Eliezer Tamir >>>> srcversion: 050FF749F80E43CB5873BC9 >>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>> depends: mdio,libcrc32c >>>> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>> (default)) (int) >>>> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 >>>> (default is half number of CPUs) (int) >>>> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 >>>> (default is half number of CPUs) (int) >>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>> parm: poll: Use polling (for debug) (int) >>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>> parm: debug: Default debug msglevel (int) >>>> >>>> modinfo for bnx2x on xcp 1.5 >>>> >>>> [root@xen-blade13 ~]# modinfo bnx2x >>>> filename: >>>> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net= /bnx2x.ko >>>> version: 1.62.17 >>>> license: GPL >>>> description: Broadcom NetXtreme II >>>> BCM57710/57711/57711E/57712/57712E Driver >>>> author: Eliezer Tamir >>>> srcversion: 13EA885EBE061121BAEC28D >>>> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>> depends: mdio >>>> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP >>>> mod_unload modversions Xen 686 >>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >>>> parm: pri_map: Priority to HW queue mapping (int) >>>> parm: qs_per_cos: Number of queues per HW queue (int) >>>> parm: cos_min_rate: Weight for RR between HW queues (int) >>>> parm: num_queues: Number of queues for multi_mode=3D1 >>>> (default is as a number of CPUs) (int) >>>> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>> parm: int_mode: Force interrupt mode other than MSI-X (1 >>>> INT#x; 2 MSI) (int) >>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>> parm: poll: Use polling (for debug) (int) >>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>> parm: debug: Default debug msglevel (int) >>>> >>>> Seems that the xcp 1.5 got a more recent version of the module. So >>>> that might not be the problem. >>>> Maybe another problem in the kernel ? >>>> >>>> Any ideas how I could debug this ? >>>> >>>> Cheers, >>>> S=E9bastien >>>> >>>> >>>> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>>>> Hi, >>>>> >>>>> I'm currently playing with XCP 1.5 beta on a Dell Blade >>>>> infrastructure that is linked to redundent filers with 10gbits NICs. >>>>> >>>>> The redundent 10gigs interfaces are not managed by xapi (i've told >>>>> xapi to forget them) and are configured like on any normal linux box. >>>>> >>>>> They are connected to the same 10gig switch where the filers are >>>>> connected to. >>>>> >>>>> Interfaces on the filers: >>>>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> >>>>> Interfaces on the blades: >>>>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> >>>>> The problem is that after some testing with iperf i get to this >>>>> conclusion: >>>>> >>>>> 1) Between the filers the speed is 9.9Gbit/s. >>>>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is >>>>> quite poor >>>>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is >>>>> quite poor (so that's not a new 1.5 bug) >>>>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>>>> >>>>> Do you have any ideas what could be the problem ? knowing that >>>>> between the filers the speed is good and it's passing through the >>>>> same switch. >>>>> >>>>> Is there a DDK VM available for XCP 1.5 beta? I would like to try >>>>> to build the latest Broadcom drivers for these nics (bnx2x) for the >>>>> kernel used on xcp 1.5... >>>>> >>>>> In the meantime I will try to install a debian on another blade to >>>>> check if the speed are correct with the filers. >>>>> >>>>> Thanks, >>>>> S=E9bastien >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> _______________________________________________ >> 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 Mon Apr 30 08:46:42 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 08:46:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmFf-0002gB-Hg; Mon, 30 Apr 2012 08:46:35 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmFd-0002g6-UR for xen-api@lists.xensource.com; Mon, 30 Apr 2012 08:46:34 +0000 Received: from [193.109.254.147:4439] by server-12.bemta-14.messagelabs.com id 1E/39-05898-9615E9F4; Mon, 30 Apr 2012 08:46:33 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1335775591!84822!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7464 invoked from network); 30 Apr 2012 08:46:32 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2012 08:46:32 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3U8chBt028279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Apr 2012 10:38:43 +0200 Message-ID: <4F9E4F92.3080200@swisscenter.com> Date: Mon, 30 Apr 2012 10:38:42 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Uli_St=E4rk?= , "xen-api@lists.xensource.com" References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com>, <4F9D7917.8060804@swisscenter.com> In-Reply-To: X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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, Yes I've almost tried everything that is on the network tweaking guide: http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide But the bottleneck seems to be the xen hypervisor used in xcp and xenserver. On the same machine but with xcp-xapi (over debian) I get almost normal = 10gbit/s speeds from dom0. What is kinda relevant is that even doing an iperf "localhost to = localhost" it's stuck to that 3gbit in a xcp or xenserver dom0... XCP: [root@xen-blade13 ~]# iperf -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 5001 ------------------------------------------------------------ [ 3] local 127.0.0.1 port 43138 connected with 127.0.0.1 port 5001 [ 3] 0.0-10.0 sec 3.43 GBytes 2.94 Gbits/sec Kronos (xapi on debian) root@xen-blade11:~# iperf -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 5001 ------------------------------------------------------------ [ 3] local 127.0.0.1 port 34438 connected with 127.0.0.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 18.9 GBytes 16.3 Gbits/sec So I'll never get more than 3gbit/s in one thread on xenserver or xcp... = and that is kinda ... bad :/ Not sure yet if it's a limitation of the dom0 kernel or the hypervisor = itself... I tend to think it's the hypervisor. xcp 1.5 host : xen-blade13 release : 2.6.32.12-0.7.1.xs1.4.90.530.170661xen version : #1 SMP Sat Apr 28 21:26:23 CEST 2012 machine : i686 nr_cpus : 16 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2394 hw_caps : = bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32758 free_memory : 31516 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 = hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xfdc00000 xen_changeset : unavailable xen_commandline : dom0_mem=3D752M lowmem_emergency_pool=3D1M = crashkernel=3D64M@32M console=3D vga=3Dmode-0x0311 dom0_max_vcpus=3D8 cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) cc_compile_by : root cc_compile_domain : uk.xensource.com cc_compile_date : Mon Feb 6 19:01:42 EST 2012 xend_config_format : 4 xcp-xapi (debian) host : xen-blade11 release : 3.2.0-2-686-pae version : #1 SMP Sun Apr 15 17:56:31 UTC 2012 machine : i686 nr_cpus : 8 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2394 hw_caps : = bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32758 free_memory : 30560 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 = hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xfdc00000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=3D1024M cc_compiler : gcc version 4.6.2 (Debian 4.6.2-6) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Sun Dec 11 13:32:25 UTC 2011 xend_config_format : 4 I see not much difference except 4.1.1 for xcp 4.1.2 for xcp-xapi with = same scheduler (credit) Also I found an old post (2008) of someone having the same symptoms back = in the years: http://old-list-archives.xen.org/archives/html/xen-users/2008-12/msg00508.h= tml but didn't find any follow ups ... Cheers, S=E9bastien On 30.04.2012 10:13, Uli St=E4rk wrote: > did you enable jumbo frames? > > ip link set eth2 mtu 9000 > > > ________________________________________ > Von: xen-api-bounces@lists.xen.org [xen-api-bounces@lists.xen.org]" = im Auftrag von"S=E9bastien Riccio [sr@swisscenter.com] > Gesendet: Sonntag, 29. April 2012 19:23 > Bis: xen-api@lists.xensource.com > Betreff: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit net= work cards > > Another discovery: > > On XCP 1.5 > > iperf on dom0 to localhost (loopback) > > Client connecting to localhost, TCP port 5001 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 38278 connected with 127.0.0.1 port 5001 > ^C[ 3] 0.0- 5.2 sec 1.79 GBytes 2.97 Gbits/sec > > Limited to 3gbit > > on xapi/debian > > root@kronos:~# iperf -c 10.50.50.111 > ------------------------------------------------------------ > Client connecting to 10.50.50.111, TCP port 5001 > TCP window size: 167 KByte (default) > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 41137 connected with 127.0.0.1 port 5001 > [ ID] Interval Transfer Bandwidth[ 3] 0.0- 5.6 sec 13.1 > GBytes 20.0 Gbits/sec > > clearly not a nic issue.... > > Cheers, > S=E9bastien > > > > > > > On 29.04.2012 17:28, S=E9bastien Riccio wrote: >> Me again (sorry), >> >> Still trying to sort things out to understand why it's slow under xcp, >> I've installed xcp on debian (project kronos), and did an iperf from dom0 >> >> [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec >> [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec >> [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec >> [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec >> >> It's not getting to the 10gibt/s so it looks that it's related to the >> xen hypervisor. >> But it still 2x better than with xcp/xenserver. >> >> Any ideas how to improve this? >> >> Cheers, >> S=E9bastien >> >> On 29.04.2012 14:44, S=E9bastien Riccio wrote: >>> Hi again, again :) >>> >>> Something strange : >>> >>> If i issue parallel threads with iperf (8 in this example, the >>> 10Gbit/s speed is reached) >>> >>> [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec >>> [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>> [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec >>> [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec >>> [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec >>> [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec >>> [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>> [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec >>> [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec >>> >>> So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? >>> It's really not efficient as we connect the iscsi storage to the >>> filer from dom0, so it will always be a single thread, so no >>> possibility to get the full 10Gbit bw for our storage. >>> >>> Is there a way to get rid of that (bug?) limitation ? >>> >>> Cheers, >>> S=E9bastien >>> >>> >>> >>> >>> On 29.04.2012 14:23, S=E9bastien Riccio wrote: >>>> Hi again, >>>> >>>> So I did my test with a debian 6 on the same hardware than I'm using >>>> to try the xcp 1.5. >>>> >>>> Speed to the filer via the 10gig nic: >>>> >>>> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >>>> >>>> I would tend to conclude that there is something wrong with the >>>> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >>>> >>>> (Note that our Dell hardware is certified as supported by XenServer, >>>> so it seems not so true :/) >>>> >>>> modinfo for bnx2x on debian 6 >>>> >>>> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko >>>> firmware: bnx2x-e1h-5.0.21.0.fw >>>> firmware: bnx2x-e1-5.0.21.0.fw >>>> version: 1.52.1 >>>> license: GPL >>>> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >>>> author: Eliezer Tamir >>>> srcversion: 050FF749F80E43CB5873BC9 >>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>> depends: mdio,libcrc32c >>>> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>> (default)) (int) >>>> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 >>>> (default is half number of CPUs) (int) >>>> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 >>>> (default is half number of CPUs) (int) >>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>> parm: poll: Use polling (for debug) (int) >>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>> parm: debug: Default debug msglevel (int) >>>> >>>> modinfo for bnx2x on xcp 1.5 >>>> >>>> [root@xen-blade13 ~]# modinfo bnx2x >>>> filename: >>>> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net= /bnx2x.ko >>>> version: 1.62.17 >>>> license: GPL >>>> description: Broadcom NetXtreme II >>>> BCM57710/57711/57711E/57712/57712E Driver >>>> author: Eliezer Tamir >>>> srcversion: 13EA885EBE061121BAEC28D >>>> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>> depends: mdio >>>> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP >>>> mod_unload modversions Xen 686 >>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >>>> parm: pri_map: Priority to HW queue mapping (int) >>>> parm: qs_per_cos: Number of queues per HW queue (int) >>>> parm: cos_min_rate: Weight for RR between HW queues (int) >>>> parm: num_queues: Number of queues for multi_mode=3D1 >>>> (default is as a number of CPUs) (int) >>>> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>> parm: int_mode: Force interrupt mode other than MSI-X (1 >>>> INT#x; 2 MSI) (int) >>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>> parm: poll: Use polling (for debug) (int) >>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>> parm: debug: Default debug msglevel (int) >>>> >>>> Seems that the xcp 1.5 got a more recent version of the module. So >>>> that might not be the problem. >>>> Maybe another problem in the kernel ? >>>> >>>> Any ideas how I could debug this ? >>>> >>>> Cheers, >>>> S=E9bastien >>>> >>>> >>>> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>>>> Hi, >>>>> >>>>> I'm currently playing with XCP 1.5 beta on a Dell Blade >>>>> infrastructure that is linked to redundent filers with 10gbits NICs. >>>>> >>>>> The redundent 10gigs interfaces are not managed by xapi (i've told >>>>> xapi to forget them) and are configured like on any normal linux box. >>>>> >>>>> They are connected to the same 10gig switch where the filers are >>>>> connected to. >>>>> >>>>> Interfaces on the filers: >>>>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> >>>>> Interfaces on the blades: >>>>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> >>>>> The problem is that after some testing with iperf i get to this >>>>> conclusion: >>>>> >>>>> 1) Between the filers the speed is 9.9Gbit/s. >>>>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is >>>>> quite poor >>>>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is >>>>> quite poor (so that's not a new 1.5 bug) >>>>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>>>> >>>>> Do you have any ideas what could be the problem ? knowing that >>>>> between the filers the speed is good and it's passing through the >>>>> same switch. >>>>> >>>>> Is there a DDK VM available for XCP 1.5 beta? I would like to try >>>>> to build the latest Broadcom drivers for these nics (bnx2x) for the >>>>> kernel used on xcp 1.5... >>>>> >>>>> In the meantime I will try to install a debian on another blade to >>>>> check if the speed are correct with the filers. >>>>> >>>>> Thanks, >>>>> S=E9bastien >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> _______________________________________________ >> 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 Mon Apr 30 09:01:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 09:01:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmUI-0002q7-Ik; Mon, 30 Apr 2012 09:01:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmUG-0002pu-U3 for xen-api@lists.xensource.com; Mon, 30 Apr 2012 09:01:41 +0000 Received: from [85.158.138.51:63707] by server-7.bemta-3.messagelabs.com id A5/7D-03078-4F45E9F4; Mon, 30 Apr 2012 09:01:40 +0000 X-Env-Sender: Uli.Staerk@globalways.net X-Msg-Ref: server-12.tower-174.messagelabs.com!1335776498!16504157!1 X-Originating-IP: [94.186.131.12] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16805 invoked from network); 30 Apr 2012 09:01:38 -0000 Received: from mx3.emx.globalways.net (HELO mx3.emx.globalways.net) (94.186.131.12) by server-12.tower-174.messagelabs.com with SMTP; 30 Apr 2012 09:01:38 -0000 Received: (qmail 10329 invoked by uid 5007); 30 Apr 2012 11:01:37 +0200 Received: from mail-out1.emx.globalways.net by mx3 (envelope-from , uid 5001) with qmail-scanner-2.08 (clamdscan: 0.96/12115. spamassassin: 3.2.5. Clear:RC:1(94.186.131.60):. Processed in 0.030312 secs); 30 Apr 2012 09:01:37 -0000 Received: from mail-out1.emx.globalways.net (94.186.131.60) by mx3.emx.globalways.net with SMTP; 30 Apr 2012 11:01:37 +0200 Received: (qmail 4309 invoked from network); 30 Apr 2012 09:01:37 -0000 Received: from unknown (HELO EX1-STGT.intern.globalways.net) (94.186.131.40) by mail-out1.emx.globalways.net with ESMTPS (AES128-SHA encrypted); 30 Apr 2012 09:01:37 -0000 Received: from EX1-STGT.intern.globalways.net ([10.9.0.3]) by EX1-STGT.intern.globalways.net ([10.9.0.3]) with mapi id 14.01.0218.012; Mon, 30 Apr 2012 11:02:38 +0200 From: =?iso-8859-1?Q?Uli_St=E4rk?= To: =?iso-8859-1?Q?S=E9bastien_Riccio?= , "xen-api@lists.xensource.com" Thread-Topic: AW: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards Thread-Index: AQHNJgMhnCGMOxnP6EC2aMoPG9NVAZaxnfqAgAAuAoCAACATgIABGOUA///mygCAACQ+oA== Date: Mon, 30 Apr 2012 09:02:37 +0000 Message-ID: References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com>,<4F9D7917.8060804@swisscenter.com> , <4F9E4F92.3080200@swisscenter.com> In-Reply-To: <4F9E4F92.3080200@swisscenter.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.0.1] MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Did you try to disable all power saving functions in bios? Power saving has= a big impact on interrupt handling :( ________________________________________ Von: S=E9bastien Riccio [sr@swisscenter.com] Gesendet: Montag, 30. April 2012 10:38 Bis: Uli St=E4rk; xen-api@lists.xensource.com Betreff: Re: AW: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit n= etwork cards Hi, Yes I've almost tried everything that is on the network tweaking guide: http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide But the bottleneck seems to be the xen hypervisor used in xcp and xenserver. On the same machine but with xcp-xapi (over debian) I get almost normal 10gbit/s speeds from dom0. What is kinda relevant is that even doing an iperf "localhost to localhost" it's stuck to that 3gbit in a xcp or xenserver dom0... XCP: [root@xen-blade13 ~]# iperf -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 5001 ------------------------------------------------------------ [ 3] local 127.0.0.1 port 43138 connected with 127.0.0.1 port 5001 [ 3] 0.0-10.0 sec 3.43 GBytes 2.94 Gbits/sec Kronos (xapi on debian) root@xen-blade11:~# iperf -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 5001 ------------------------------------------------------------ [ 3] local 127.0.0.1 port 34438 connected with 127.0.0.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 18.9 GBytes 16.3 Gbits/sec So I'll never get more than 3gbit/s in one thread on xenserver or xcp... and that is kinda ... bad :/ Not sure yet if it's a limitation of the dom0 kernel or the hypervisor itself... I tend to think it's the hypervisor. xcp 1.5 host : xen-blade13 release : 2.6.32.12-0.7.1.xs1.4.90.530.170661xen version : #1 SMP Sat Apr 28 21:26:23 CEST 2012 machine : i686 nr_cpus : 16 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2394 hw_caps : bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32758 free_memory : 31516 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xfdc00000 xen_changeset : unavailable xen_commandline : dom0_mem=3D752M lowmem_emergency_pool=3D1M crashkernel=3D64M@32M console=3D vga=3Dmode-0x0311 dom0_max_vcpus=3D8 cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) cc_compile_by : root cc_compile_domain : uk.xensource.com cc_compile_date : Mon Feb 6 19:01:42 EST 2012 xend_config_format : 4 xcp-xapi (debian) host : xen-blade11 release : 3.2.0-2-686-pae version : #1 SMP Sun Apr 15 17:56:31 UTC 2012 machine : i686 nr_cpus : 8 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2394 hw_caps : bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32758 free_memory : 30560 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xfdc00000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=3D1024M cc_compiler : gcc version 4.6.2 (Debian 4.6.2-6) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Sun Dec 11 13:32:25 UTC 2011 xend_config_format : 4 I see not much difference except 4.1.1 for xcp 4.1.2 for xcp-xapi with same scheduler (credit) Also I found an old post (2008) of someone having the same symptoms back in the years: http://old-list-archives.xen.org/archives/html/xen-users/2008-12/msg00508.h= tml but didn't find any follow ups ... Cheers, S=E9bastien On 30.04.2012 10:13, Uli St=E4rk wrote: > did you enable jumbo frames? > > ip link set eth2 mtu 9000 > > > ________________________________________ > Von: xen-api-bounces@lists.xen.org [xen-api-bounces@lists.xen.org]" = im Auftrag von"S=E9bastien Riccio [sr@swisscenter.com] > Gesendet: Sonntag, 29. April 2012 19:23 > Bis: xen-api@lists.xensource.com > Betreff: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit net= work cards > > Another discovery: > > On XCP 1.5 > > iperf on dom0 to localhost (loopback) > > Client connecting to localhost, TCP port 5001 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 38278 connected with 127.0.0.1 port 5001 > ^C[ 3] 0.0- 5.2 sec 1.79 GBytes 2.97 Gbits/sec > > Limited to 3gbit > > on xapi/debian > > root@kronos:~# iperf -c 10.50.50.111 > ------------------------------------------------------------ > Client connecting to 10.50.50.111, TCP port 5001 > TCP window size: 167 KByte (default) > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 41137 connected with 127.0.0.1 port 5001 > [ ID] Interval Transfer Bandwidth[ 3] 0.0- 5.6 sec 13.1 > GBytes 20.0 Gbits/sec > > clearly not a nic issue.... > > Cheers, > S=E9bastien > > > > > > > On 29.04.2012 17:28, S=E9bastien Riccio wrote: >> Me again (sorry), >> >> Still trying to sort things out to understand why it's slow under xcp, >> I've installed xcp on debian (project kronos), and did an iperf from dom0 >> >> [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec >> [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec >> [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec >> [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec >> >> It's not getting to the 10gibt/s so it looks that it's related to the >> xen hypervisor. >> But it still 2x better than with xcp/xenserver. >> >> Any ideas how to improve this? >> >> Cheers, >> S=E9bastien >> >> On 29.04.2012 14:44, S=E9bastien Riccio wrote: >>> Hi again, again :) >>> >>> Something strange : >>> >>> If i issue parallel threads with iperf (8 in this example, the >>> 10Gbit/s speed is reached) >>> >>> [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec >>> [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>> [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec >>> [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec >>> [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec >>> [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec >>> [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>> [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec >>> [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec >>> >>> So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? >>> It's really not efficient as we connect the iscsi storage to the >>> filer from dom0, so it will always be a single thread, so no >>> possibility to get the full 10Gbit bw for our storage. >>> >>> Is there a way to get rid of that (bug?) limitation ? >>> >>> Cheers, >>> S=E9bastien >>> >>> >>> >>> >>> On 29.04.2012 14:23, S=E9bastien Riccio wrote: >>>> Hi again, >>>> >>>> So I did my test with a debian 6 on the same hardware than I'm using >>>> to try the xcp 1.5. >>>> >>>> Speed to the filer via the 10gig nic: >>>> >>>> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >>>> >>>> I would tend to conclude that there is something wrong with the >>>> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >>>> >>>> (Note that our Dell hardware is certified as supported by XenServer, >>>> so it seems not so true :/) >>>> >>>> modinfo for bnx2x on debian 6 >>>> >>>> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko >>>> firmware: bnx2x-e1h-5.0.21.0.fw >>>> firmware: bnx2x-e1-5.0.21.0.fw >>>> version: 1.52.1 >>>> license: GPL >>>> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >>>> author: Eliezer Tamir >>>> srcversion: 050FF749F80E43CB5873BC9 >>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>> depends: mdio,libcrc32c >>>> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>> (default)) (int) >>>> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 >>>> (default is half number of CPUs) (int) >>>> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 >>>> (default is half number of CPUs) (int) >>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>> parm: poll: Use polling (for debug) (int) >>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>> parm: debug: Default debug msglevel (int) >>>> >>>> modinfo for bnx2x on xcp 1.5 >>>> >>>> [root@xen-blade13 ~]# modinfo bnx2x >>>> filename: >>>> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net= /bnx2x.ko >>>> version: 1.62.17 >>>> license: GPL >>>> description: Broadcom NetXtreme II >>>> BCM57710/57711/57711E/57712/57712E Driver >>>> author: Eliezer Tamir >>>> srcversion: 13EA885EBE061121BAEC28D >>>> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>> depends: mdio >>>> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP >>>> mod_unload modversions Xen 686 >>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >>>> parm: pri_map: Priority to HW queue mapping (int) >>>> parm: qs_per_cos: Number of queues per HW queue (int) >>>> parm: cos_min_rate: Weight for RR between HW queues (int) >>>> parm: num_queues: Number of queues for multi_mode=3D1 >>>> (default is as a number of CPUs) (int) >>>> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>> parm: int_mode: Force interrupt mode other than MSI-X (1 >>>> INT#x; 2 MSI) (int) >>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>> parm: poll: Use polling (for debug) (int) >>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>> parm: debug: Default debug msglevel (int) >>>> >>>> Seems that the xcp 1.5 got a more recent version of the module. So >>>> that might not be the problem. >>>> Maybe another problem in the kernel ? >>>> >>>> Any ideas how I could debug this ? >>>> >>>> Cheers, >>>> S=E9bastien >>>> >>>> >>>> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>>>> Hi, >>>>> >>>>> I'm currently playing with XCP 1.5 beta on a Dell Blade >>>>> infrastructure that is linked to redundent filers with 10gbits NICs. >>>>> >>>>> The redundent 10gigs interfaces are not managed by xapi (i've told >>>>> xapi to forget them) and are configured like on any normal linux box. >>>>> >>>>> They are connected to the same 10gig switch where the filers are >>>>> connected to. >>>>> >>>>> Interfaces on the filers: >>>>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> >>>>> Interfaces on the blades: >>>>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> >>>>> The problem is that after some testing with iperf i get to this >>>>> conclusion: >>>>> >>>>> 1) Between the filers the speed is 9.9Gbit/s. >>>>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is >>>>> quite poor >>>>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is >>>>> quite poor (so that's not a new 1.5 bug) >>>>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>>>> >>>>> Do you have any ideas what could be the problem ? knowing that >>>>> between the filers the speed is good and it's passing through the >>>>> same switch. >>>>> >>>>> Is there a DDK VM available for XCP 1.5 beta? I would like to try >>>>> to build the latest Broadcom drivers for these nics (bnx2x) for the >>>>> kernel used on xcp 1.5... >>>>> >>>>> In the meantime I will try to install a debian on another blade to >>>>> check if the speed are correct with the filers. >>>>> >>>>> Thanks, >>>>> S=E9bastien >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> _______________________________________________ >> 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 Mon Apr 30 09:01:50 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 09:01:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmUI-0002q7-Ik; Mon, 30 Apr 2012 09:01:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmUG-0002pu-U3 for xen-api@lists.xensource.com; Mon, 30 Apr 2012 09:01:41 +0000 Received: from [85.158.138.51:63707] by server-7.bemta-3.messagelabs.com id A5/7D-03078-4F45E9F4; Mon, 30 Apr 2012 09:01:40 +0000 X-Env-Sender: Uli.Staerk@globalways.net X-Msg-Ref: server-12.tower-174.messagelabs.com!1335776498!16504157!1 X-Originating-IP: [94.186.131.12] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16805 invoked from network); 30 Apr 2012 09:01:38 -0000 Received: from mx3.emx.globalways.net (HELO mx3.emx.globalways.net) (94.186.131.12) by server-12.tower-174.messagelabs.com with SMTP; 30 Apr 2012 09:01:38 -0000 Received: (qmail 10329 invoked by uid 5007); 30 Apr 2012 11:01:37 +0200 Received: from mail-out1.emx.globalways.net by mx3 (envelope-from , uid 5001) with qmail-scanner-2.08 (clamdscan: 0.96/12115. spamassassin: 3.2.5. Clear:RC:1(94.186.131.60):. Processed in 0.030312 secs); 30 Apr 2012 09:01:37 -0000 Received: from mail-out1.emx.globalways.net (94.186.131.60) by mx3.emx.globalways.net with SMTP; 30 Apr 2012 11:01:37 +0200 Received: (qmail 4309 invoked from network); 30 Apr 2012 09:01:37 -0000 Received: from unknown (HELO EX1-STGT.intern.globalways.net) (94.186.131.40) by mail-out1.emx.globalways.net with ESMTPS (AES128-SHA encrypted); 30 Apr 2012 09:01:37 -0000 Received: from EX1-STGT.intern.globalways.net ([10.9.0.3]) by EX1-STGT.intern.globalways.net ([10.9.0.3]) with mapi id 14.01.0218.012; Mon, 30 Apr 2012 11:02:38 +0200 From: =?iso-8859-1?Q?Uli_St=E4rk?= To: =?iso-8859-1?Q?S=E9bastien_Riccio?= , "xen-api@lists.xensource.com" Thread-Topic: AW: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards Thread-Index: AQHNJgMhnCGMOxnP6EC2aMoPG9NVAZaxnfqAgAAuAoCAACATgIABGOUA///mygCAACQ+oA== Date: Mon, 30 Apr 2012 09:02:37 +0000 Message-ID: References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com>,<4F9D7917.8060804@swisscenter.com> , <4F9E4F92.3080200@swisscenter.com> In-Reply-To: <4F9E4F92.3080200@swisscenter.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.0.1] MIME-Version: 1.0 Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Did you try to disable all power saving functions in bios? Power saving has= a big impact on interrupt handling :( ________________________________________ Von: S=E9bastien Riccio [sr@swisscenter.com] Gesendet: Montag, 30. April 2012 10:38 Bis: Uli St=E4rk; xen-api@lists.xensource.com Betreff: Re: AW: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit n= etwork cards Hi, Yes I've almost tried everything that is on the network tweaking guide: http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide But the bottleneck seems to be the xen hypervisor used in xcp and xenserver. On the same machine but with xcp-xapi (over debian) I get almost normal 10gbit/s speeds from dom0. What is kinda relevant is that even doing an iperf "localhost to localhost" it's stuck to that 3gbit in a xcp or xenserver dom0... XCP: [root@xen-blade13 ~]# iperf -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 5001 ------------------------------------------------------------ [ 3] local 127.0.0.1 port 43138 connected with 127.0.0.1 port 5001 [ 3] 0.0-10.0 sec 3.43 GBytes 2.94 Gbits/sec Kronos (xapi on debian) root@xen-blade11:~# iperf -c localhost ------------------------------------------------------------ Client connecting to localhost, TCP port 5001 ------------------------------------------------------------ [ 3] local 127.0.0.1 port 34438 connected with 127.0.0.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 18.9 GBytes 16.3 Gbits/sec So I'll never get more than 3gbit/s in one thread on xenserver or xcp... and that is kinda ... bad :/ Not sure yet if it's a limitation of the dom0 kernel or the hypervisor itself... I tend to think it's the hypervisor. xcp 1.5 host : xen-blade13 release : 2.6.32.12-0.7.1.xs1.4.90.530.170661xen version : #1 SMP Sat Apr 28 21:26:23 CEST 2012 machine : i686 nr_cpus : 16 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 2 cpu_mhz : 2394 hw_caps : bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32758 free_memory : 31516 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xfdc00000 xen_changeset : unavailable xen_commandline : dom0_mem=3D752M lowmem_emergency_pool=3D1M crashkernel=3D64M@32M console=3D vga=3Dmode-0x0311 dom0_max_vcpus=3D8 cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) cc_compile_by : root cc_compile_domain : uk.xensource.com cc_compile_date : Mon Feb 6 19:01:42 EST 2012 xend_config_format : 4 xcp-xapi (debian) host : xen-blade11 release : 3.2.0-2-686-pae version : #1 SMP Sun Apr 15 17:56:31 UTC 2012 machine : i686 nr_cpus : 8 nr_nodes : 2 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2394 hw_caps : bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 32758 free_memory : 30560 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=3D0xfdc00000 xen_changeset : unavailable xen_commandline : placeholder dom0_mem=3D1024M cc_compiler : gcc version 4.6.2 (Debian 4.6.2-6) cc_compile_by : waldi cc_compile_domain : debian.org cc_compile_date : Sun Dec 11 13:32:25 UTC 2011 xend_config_format : 4 I see not much difference except 4.1.1 for xcp 4.1.2 for xcp-xapi with same scheduler (credit) Also I found an old post (2008) of someone having the same symptoms back in the years: http://old-list-archives.xen.org/archives/html/xen-users/2008-12/msg00508.h= tml but didn't find any follow ups ... Cheers, S=E9bastien On 30.04.2012 10:13, Uli St=E4rk wrote: > did you enable jumbo frames? > > ip link set eth2 mtu 9000 > > > ________________________________________ > Von: xen-api-bounces@lists.xen.org [xen-api-bounces@lists.xen.org]" = im Auftrag von"S=E9bastien Riccio [sr@swisscenter.com] > Gesendet: Sonntag, 29. April 2012 19:23 > Bis: xen-api@lists.xensource.com > Betreff: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit net= work cards > > Another discovery: > > On XCP 1.5 > > iperf on dom0 to localhost (loopback) > > Client connecting to localhost, TCP port 5001 > TCP window size: 64.0 KByte (default) > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 38278 connected with 127.0.0.1 port 5001 > ^C[ 3] 0.0- 5.2 sec 1.79 GBytes 2.97 Gbits/sec > > Limited to 3gbit > > on xapi/debian > > root@kronos:~# iperf -c 10.50.50.111 > ------------------------------------------------------------ > Client connecting to 10.50.50.111, TCP port 5001 > TCP window size: 167 KByte (default) > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 41137 connected with 127.0.0.1 port 5001 > [ ID] Interval Transfer Bandwidth[ 3] 0.0- 5.6 sec 13.1 > GBytes 20.0 Gbits/sec > > clearly not a nic issue.... > > Cheers, > S=E9bastien > > > > > > > On 29.04.2012 17:28, S=E9bastien Riccio wrote: >> Me again (sorry), >> >> Still trying to sort things out to understand why it's slow under xcp, >> I've installed xcp on debian (project kronos), and did an iperf from dom0 >> >> [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec >> [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec >> [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec >> [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec >> [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec >> >> It's not getting to the 10gibt/s so it looks that it's related to the >> xen hypervisor. >> But it still 2x better than with xcp/xenserver. >> >> Any ideas how to improve this? >> >> Cheers, >> S=E9bastien >> >> On 29.04.2012 14:44, S=E9bastien Riccio wrote: >>> Hi again, again :) >>> >>> Something strange : >>> >>> If i issue parallel threads with iperf (8 in this example, the >>> 10Gbit/s speed is reached) >>> >>> [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec >>> [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>> [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec >>> [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec >>> [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec >>> [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec >>> [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>> [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec >>> [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec >>> >>> So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? >>> It's really not efficient as we connect the iscsi storage to the >>> filer from dom0, so it will always be a single thread, so no >>> possibility to get the full 10Gbit bw for our storage. >>> >>> Is there a way to get rid of that (bug?) limitation ? >>> >>> Cheers, >>> S=E9bastien >>> >>> >>> >>> >>> On 29.04.2012 14:23, S=E9bastien Riccio wrote: >>>> Hi again, >>>> >>>> So I did my test with a debian 6 on the same hardware than I'm using >>>> to try the xcp 1.5. >>>> >>>> Speed to the filer via the 10gig nic: >>>> >>>> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >>>> >>>> I would tend to conclude that there is something wrong with the >>>> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >>>> >>>> (Note that our Dell hardware is certified as supported by XenServer, >>>> so it seems not so true :/) >>>> >>>> modinfo for bnx2x on debian 6 >>>> >>>> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.ko >>>> firmware: bnx2x-e1h-5.0.21.0.fw >>>> firmware: bnx2x-e1-5.0.21.0.fw >>>> version: 1.52.1 >>>> license: GPL >>>> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >>>> author: Eliezer Tamir >>>> srcversion: 050FF749F80E43CB5873BC9 >>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>> depends: mdio,libcrc32c >>>> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>> (default)) (int) >>>> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 >>>> (default is half number of CPUs) (int) >>>> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 >>>> (default is half number of CPUs) (int) >>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>> parm: poll: Use polling (for debug) (int) >>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>> parm: debug: Default debug msglevel (int) >>>> >>>> modinfo for bnx2x on xcp 1.5 >>>> >>>> [root@xen-blade13 ~]# modinfo bnx2x >>>> filename: >>>> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/net= /bnx2x.ko >>>> version: 1.62.17 >>>> license: GPL >>>> description: Broadcom NetXtreme II >>>> BCM57710/57711/57711E/57712/57712E Driver >>>> author: Eliezer Tamir >>>> srcversion: 13EA885EBE061121BAEC28D >>>> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>> depends: mdio >>>> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP >>>> mod_unload modversions Xen 686 >>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >>>> parm: pri_map: Priority to HW queue mapping (int) >>>> parm: qs_per_cos: Number of queues per HW queue (int) >>>> parm: cos_min_rate: Weight for RR between HW queues (int) >>>> parm: num_queues: Number of queues for multi_mode=3D1 >>>> (default is as a number of CPUs) (int) >>>> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>> parm: int_mode: Force interrupt mode other than MSI-X (1 >>>> INT#x; 2 MSI) (int) >>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>> parm: poll: Use polling (for debug) (int) >>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>> parm: debug: Default debug msglevel (int) >>>> >>>> Seems that the xcp 1.5 got a more recent version of the module. So >>>> that might not be the problem. >>>> Maybe another problem in the kernel ? >>>> >>>> Any ideas how I could debug this ? >>>> >>>> Cheers, >>>> S=E9bastien >>>> >>>> >>>> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>>>> Hi, >>>>> >>>>> I'm currently playing with XCP 1.5 beta on a Dell Blade >>>>> infrastructure that is linked to redundent filers with 10gbits NICs. >>>>> >>>>> The redundent 10gigs interfaces are not managed by xapi (i've told >>>>> xapi to forget them) and are configured like on any normal linux box. >>>>> >>>>> They are connected to the same 10gig switch where the filers are >>>>> connected to. >>>>> >>>>> Interfaces on the filers: >>>>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> >>>>> Interfaces on the blades: >>>>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>> BCM57711 10-Gigabit PCIe >>>>> >>>>> The problem is that after some testing with iperf i get to this >>>>> conclusion: >>>>> >>>>> 1) Between the filers the speed is 9.9Gbit/s. >>>>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is >>>>> quite poor >>>>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is >>>>> quite poor (so that's not a new 1.5 bug) >>>>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>>>> >>>>> Do you have any ideas what could be the problem ? knowing that >>>>> between the filers the speed is good and it's passing through the >>>>> same switch. >>>>> >>>>> Is there a DDK VM available for XCP 1.5 beta? I would like to try >>>>> to build the latest Broadcom drivers for these nics (bnx2x) for the >>>>> kernel used on xcp 1.5... >>>>> >>>>> In the meantime I will try to install a debian on another blade to >>>>> check if the speed are correct with the filers. >>>>> >>>>> Thanks, >>>>> S=E9bastien >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> _______________________________________________ >> 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 Mon Apr 30 09:04:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 09:04: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 1SOmWr-00032f-Tp; Mon, 30 Apr 2012 09:04:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmWq-00032U-I1 for xen-api@lists.xensource.com; Mon, 30 Apr 2012 09:04:20 +0000 Received: from [85.158.143.99:41940] by server-2.bemta-4.messagelabs.com id 1D/38-17550-3955E9F4; Mon, 30 Apr 2012 09:04:19 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1335776657!25805955!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21833 invoked from network); 30 Apr 2012 09:04:18 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-15.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2012 09:04:18 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3U94CGR030493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Apr 2012 11:04:12 +0200 Message-ID: <4F9E558B.6080703@swisscenter.com> Date: Mon, 30 Apr 2012 11:04:11 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Uli_St=E4rk?= References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com>, <4F9D7917.8060804@swisscenter.com> , <4F9E4F92.3080200@swisscenter.com> In-Reply-To: X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Yeah, I had tried that but it didn't make a difference at all, and on = the same hardware but different version of xen it works quite well. It = looks like it's a software oriented problem not hw :/ S=E9bastien On 30.04.2012 11:02, Uli St=E4rk wrote: > Did you try to disable all power saving functions in bios? Power saving h= as a big impact on interrupt handling :( > > ________________________________________ > Von: S=E9bastien Riccio [sr@swisscenter.com] > Gesendet: Montag, 30. April 2012 10:38 > Bis: Uli St=E4rk; xen-api@lists.xensource.com > Betreff: Re: AW: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit= network cards > > Hi, > > Yes I've almost tried everything that is on the network tweaking guide: > > http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide > > But the bottleneck seems to be the xen hypervisor used in xcp and xenserv= er. > > On the same machine but with xcp-xapi (over debian) I get almost normal > 10gbit/s speeds from dom0. > > What is kinda relevant is that even doing an iperf "localhost to > localhost" it's stuck to that 3gbit in a xcp or xenserver dom0... > > XCP: > > [root@xen-blade13 ~]# iperf -c localhost > ------------------------------------------------------------ > Client connecting to localhost, TCP port 5001 > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 43138 connected with 127.0.0.1 port 5001 > [ 3] 0.0-10.0 sec 3.43 GBytes 2.94 Gbits/sec > > Kronos (xapi on debian) > root@xen-blade11:~# iperf -c localhost > ------------------------------------------------------------ > Client connecting to localhost, TCP port 5001 > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 34438 connected with 127.0.0.1 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.0 sec 18.9 GBytes 16.3 Gbits/sec > > So I'll never get more than 3gbit/s in one thread on xenserver or xcp... > and that is kinda ... bad :/ > > Not sure yet if it's a limitation of the dom0 kernel or the hypervisor > itself... I tend to think it's the hypervisor. > > xcp 1.5 > > host : xen-blade13 > release : 2.6.32.12-0.7.1.xs1.4.90.530.170661xen > version : #1 SMP Sat Apr 28 21:26:23 CEST 2012 > machine : i686 > nr_cpus : 16 > nr_nodes : 2 > cores_per_socket : 4 > threads_per_core : 2 > cpu_mhz : 2394 > hw_caps : > bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 32758 > free_memory : 31516 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xfdc00000 > xen_changeset : unavailable > xen_commandline : dom0_mem=3D752M lowmem_emergency_pool=3D1M > crashkernel=3D64M@32M console=3D vga=3Dmode-0x0311 dom0_max_vcpus=3D8 > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) > cc_compile_by : root > cc_compile_domain : uk.xensource.com > cc_compile_date : Mon Feb 6 19:01:42 EST 2012 > xend_config_format : 4 > > xcp-xapi (debian) > host : xen-blade11 > release : 3.2.0-2-686-pae > version : #1 SMP Sun Apr 15 17:56:31 UTC 2012 > machine : i686 > nr_cpus : 8 > nr_nodes : 2 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2394 > hw_caps : > bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 32758 > free_memory : 30560 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xfdc00000 > xen_changeset : unavailable > xen_commandline : placeholder dom0_mem=3D1024M > cc_compiler : gcc version 4.6.2 (Debian 4.6.2-6) > cc_compile_by : waldi > cc_compile_domain : debian.org > cc_compile_date : Sun Dec 11 13:32:25 UTC 2011 > xend_config_format : 4 > > I see not much difference except 4.1.1 for xcp 4.1.2 for xcp-xapi with > same scheduler (credit) > > Also I found an old post (2008) of someone having the same symptoms back > in the years: > > http://old-list-archives.xen.org/archives/html/xen-users/2008-12/msg00508= .html > > but didn't find any follow ups ... > > Cheers, > S=E9bastien > > > On 30.04.2012 10:13, Uli St=E4rk wrote: >> did you enable jumbo frames? >> >> ip link set eth2 mtu 9000 >> >> >> ________________________________________ >> Von: xen-api-bounces@lists.xen.org [xen-api-bounces@lists.xen.org]"= im Auftrag von"S=E9bastien Riccio [sr@swisscenter.com] >> Gesendet: Sonntag, 29. April 2012 19:23 >> Bis: xen-api@lists.xensource.com >> Betreff: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit ne= twork cards >> >> Another discovery: >> >> On XCP 1.5 >> >> iperf on dom0 to localhost (loopback) >> >> Client connecting to localhost, TCP port 5001 >> TCP window size: 64.0 KByte (default) >> ------------------------------------------------------------ >> [ 3] local 127.0.0.1 port 38278 connected with 127.0.0.1 port 5001 >> ^C[ 3] 0.0- 5.2 sec 1.79 GBytes 2.97 Gbits/sec >> >> Limited to 3gbit >> >> on xapi/debian >> >> root@kronos:~# iperf -c 10.50.50.111 >> ------------------------------------------------------------ >> Client connecting to 10.50.50.111, TCP port 5001 >> TCP window size: 167 KByte (default) >> ------------------------------------------------------------ >> [ 3] local 127.0.0.1 port 41137 connected with 127.0.0.1 port 5001 >> [ ID] Interval Transfer Bandwidth[ 3] 0.0- 5.6 sec 13.1 >> GBytes 20.0 Gbits/sec >> >> clearly not a nic issue.... >> >> Cheers, >> S=E9bastien >> >> >> >> >> >> >> On 29.04.2012 17:28, S=E9bastien Riccio wrote: >>> Me again (sorry), >>> >>> Still trying to sort things out to understand why it's slow under xcp, >>> I've installed xcp on debian (project kronos), and did an iperf from do= m0 >>> >>> [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec >>> [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec >>> [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec >>> [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec >>> [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec >>> [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec >>> [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec >>> >>> It's not getting to the 10gibt/s so it looks that it's related to the >>> xen hypervisor. >>> But it still 2x better than with xcp/xenserver. >>> >>> Any ideas how to improve this? >>> >>> Cheers, >>> S=E9bastien >>> >>> On 29.04.2012 14:44, S=E9bastien Riccio wrote: >>>> Hi again, again :) >>>> >>>> Something strange : >>>> >>>> If i issue parallel threads with iperf (8 in this example, the >>>> 10Gbit/s speed is reached) >>>> >>>> [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec >>>> [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>>> [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec >>>> [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec >>>> [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec >>>> [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec >>>> [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>>> [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec >>>> [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec >>>> >>>> So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? >>>> It's really not efficient as we connect the iscsi storage to the >>>> filer from dom0, so it will always be a single thread, so no >>>> possibility to get the full 10Gbit bw for our storage. >>>> >>>> Is there a way to get rid of that (bug?) limitation ? >>>> >>>> Cheers, >>>> S=E9bastien >>>> >>>> >>>> >>>> >>>> On 29.04.2012 14:23, S=E9bastien Riccio wrote: >>>>> Hi again, >>>>> >>>>> So I did my test with a debian 6 on the same hardware than I'm using >>>>> to try the xcp 1.5. >>>>> >>>>> Speed to the filer via the 10gig nic: >>>>> >>>>> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >>>>> >>>>> I would tend to conclude that there is something wrong with the >>>>> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >>>>> >>>>> (Note that our Dell hardware is certified as supported by XenServer, >>>>> so it seems not so true :/) >>>>> >>>>> modinfo for bnx2x on debian 6 >>>>> >>>>> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.= ko >>>>> firmware: bnx2x-e1h-5.0.21.0.fw >>>>> firmware: bnx2x-e1-5.0.21.0.fw >>>>> version: 1.52.1 >>>>> license: GPL >>>>> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >>>>> author: Eliezer Tamir >>>>> srcversion: 050FF749F80E43CB5873BC9 >>>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>>> depends: mdio,libcrc32c >>>>> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >>>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>>> (default)) (int) >>>>> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 >>>>> (default is half number of CPUs) (int) >>>>> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 >>>>> (default is half number of CPUs) (int) >>>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>>> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >>>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>>> parm: poll: Use polling (for debug) (int) >>>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>>> parm: debug: Default debug msglevel (int) >>>>> >>>>> modinfo for bnx2x on xcp 1.5 >>>>> >>>>> [root@xen-blade13 ~]# modinfo bnx2x >>>>> filename: >>>>> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/ne= t/bnx2x.ko >>>>> version: 1.62.17 >>>>> license: GPL >>>>> description: Broadcom NetXtreme II >>>>> BCM57710/57711/57711E/57712/57712E Driver >>>>> author: Eliezer Tamir >>>>> srcversion: 13EA885EBE061121BAEC28D >>>>> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>>> depends: mdio >>>>> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP >>>>> mod_unload modversions Xen 686 >>>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>>> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >>>>> parm: pri_map: Priority to HW queue mapping (int) >>>>> parm: qs_per_cos: Number of queues per HW queue (int) >>>>> parm: cos_min_rate: Weight for RR between HW queues (int) >>>>> parm: num_queues: Number of queues for multi_mode=3D1 >>>>> (default is as a number of CPUs) (int) >>>>> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >>>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>>> parm: int_mode: Force interrupt mode other than MSI-X (1 >>>>> INT#x; 2 MSI) (int) >>>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>>> parm: poll: Use polling (for debug) (int) >>>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>>> parm: debug: Default debug msglevel (int) >>>>> >>>>> Seems that the xcp 1.5 got a more recent version of the module. So >>>>> that might not be the problem. >>>>> Maybe another problem in the kernel ? >>>>> >>>>> Any ideas how I could debug this ? >>>>> >>>>> Cheers, >>>>> S=E9bastien >>>>> >>>>> >>>>> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>>>>> Hi, >>>>>> >>>>>> I'm currently playing with XCP 1.5 beta on a Dell Blade >>>>>> infrastructure that is linked to redundent filers with 10gbits NICs. >>>>>> >>>>>> The redundent 10gigs interfaces are not managed by xapi (i've told >>>>>> xapi to forget them) and are configured like on any normal linux box. >>>>>> >>>>>> They are connected to the same 10gig switch where the filers are >>>>>> connected to. >>>>>> >>>>>> Interfaces on the filers: >>>>>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> >>>>>> Interfaces on the blades: >>>>>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> >>>>>> The problem is that after some testing with iperf i get to this >>>>>> conclusion: >>>>>> >>>>>> 1) Between the filers the speed is 9.9Gbit/s. >>>>>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is >>>>>> quite poor >>>>>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is >>>>>> quite poor (so that's not a new 1.5 bug) >>>>>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>>>>> >>>>>> Do you have any ideas what could be the problem ? knowing that >>>>>> between the filers the speed is good and it's passing through the >>>>>> same switch. >>>>>> >>>>>> Is there a DDK VM available for XCP 1.5 beta? I would like to try >>>>>> to build the latest Broadcom drivers for these nics (bnx2x) for the >>>>>> kernel used on xcp 1.5... >>>>>> >>>>>> In the meantime I will try to install a debian on another blade to >>>>>> check if the speed are correct with the filers. >>>>>> >>>>>> Thanks, >>>>>> S=E9bastien >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>> _______________________________________________ >>> 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 Mon Apr 30 09:04:28 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 09:04: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 1SOmWr-00032f-Tp; Mon, 30 Apr 2012 09:04:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmWq-00032U-I1 for xen-api@lists.xensource.com; Mon, 30 Apr 2012 09:04:20 +0000 Received: from [85.158.143.99:41940] by server-2.bemta-4.messagelabs.com id 1D/38-17550-3955E9F4; Mon, 30 Apr 2012 09:04:19 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-15.tower-216.messagelabs.com!1335776657!25805955!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21833 invoked from network); 30 Apr 2012 09:04:18 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-15.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2012 09:04:18 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3U94CGR030493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Apr 2012 11:04:12 +0200 Message-ID: <4F9E558B.6080703@swisscenter.com> Date: Mon, 30 Apr 2012 11:04:11 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Uli_St=E4rk?= References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com>, <4F9D7917.8060804@swisscenter.com> , <4F9E4F92.3080200@swisscenter.com> In-Reply-To: X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Yeah, I had tried that but it didn't make a difference at all, and on = the same hardware but different version of xen it works quite well. It = looks like it's a software oriented problem not hw :/ S=E9bastien On 30.04.2012 11:02, Uli St=E4rk wrote: > Did you try to disable all power saving functions in bios? Power saving h= as a big impact on interrupt handling :( > > ________________________________________ > Von: S=E9bastien Riccio [sr@swisscenter.com] > Gesendet: Montag, 30. April 2012 10:38 > Bis: Uli St=E4rk; xen-api@lists.xensource.com > Betreff: Re: AW: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit= network cards > > Hi, > > Yes I've almost tried everything that is on the network tweaking guide: > > http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide > > But the bottleneck seems to be the xen hypervisor used in xcp and xenserv= er. > > On the same machine but with xcp-xapi (over debian) I get almost normal > 10gbit/s speeds from dom0. > > What is kinda relevant is that even doing an iperf "localhost to > localhost" it's stuck to that 3gbit in a xcp or xenserver dom0... > > XCP: > > [root@xen-blade13 ~]# iperf -c localhost > ------------------------------------------------------------ > Client connecting to localhost, TCP port 5001 > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 43138 connected with 127.0.0.1 port 5001 > [ 3] 0.0-10.0 sec 3.43 GBytes 2.94 Gbits/sec > > Kronos (xapi on debian) > root@xen-blade11:~# iperf -c localhost > ------------------------------------------------------------ > Client connecting to localhost, TCP port 5001 > ------------------------------------------------------------ > [ 3] local 127.0.0.1 port 34438 connected with 127.0.0.1 port 5001 > [ ID] Interval Transfer Bandwidth > [ 3] 0.0-10.0 sec 18.9 GBytes 16.3 Gbits/sec > > So I'll never get more than 3gbit/s in one thread on xenserver or xcp... > and that is kinda ... bad :/ > > Not sure yet if it's a limitation of the dom0 kernel or the hypervisor > itself... I tend to think it's the hypervisor. > > xcp 1.5 > > host : xen-blade13 > release : 2.6.32.12-0.7.1.xs1.4.90.530.170661xen > version : #1 SMP Sat Apr 28 21:26:23 CEST 2012 > machine : i686 > nr_cpus : 16 > nr_nodes : 2 > cores_per_socket : 4 > threads_per_core : 2 > cpu_mhz : 2394 > hw_caps : > bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 32758 > free_memory : 31516 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xfdc00000 > xen_changeset : unavailable > xen_commandline : dom0_mem=3D752M lowmem_emergency_pool=3D1M > crashkernel=3D64M@32M console=3D vga=3Dmode-0x0311 dom0_max_vcpus=3D8 > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) > cc_compile_by : root > cc_compile_domain : uk.xensource.com > cc_compile_date : Mon Feb 6 19:01:42 EST 2012 > xend_config_format : 4 > > xcp-xapi (debian) > host : xen-blade11 > release : 3.2.0-2-686-pae > version : #1 SMP Sun Apr 15 17:56:31 UTC 2012 > machine : i686 > nr_cpus : 8 > nr_nodes : 2 > cores_per_socket : 4 > threads_per_core : 1 > cpu_mhz : 2394 > hw_caps : > bfebfbff:2c100800:00000000:00003f40:029ee3ff:00000000:00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 32758 > free_memory : 30560 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .2 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=3D0xfdc00000 > xen_changeset : unavailable > xen_commandline : placeholder dom0_mem=3D1024M > cc_compiler : gcc version 4.6.2 (Debian 4.6.2-6) > cc_compile_by : waldi > cc_compile_domain : debian.org > cc_compile_date : Sun Dec 11 13:32:25 UTC 2011 > xend_config_format : 4 > > I see not much difference except 4.1.1 for xcp 4.1.2 for xcp-xapi with > same scheduler (credit) > > Also I found an old post (2008) of someone having the same symptoms back > in the years: > > http://old-list-archives.xen.org/archives/html/xen-users/2008-12/msg00508= .html > > but didn't find any follow ups ... > > Cheers, > S=E9bastien > > > On 30.04.2012 10:13, Uli St=E4rk wrote: >> did you enable jumbo frames? >> >> ip link set eth2 mtu 9000 >> >> >> ________________________________________ >> Von: xen-api-bounces@lists.xen.org [xen-api-bounces@lists.xen.org]"= im Auftrag von"S=E9bastien Riccio [sr@swisscenter.com] >> Gesendet: Sonntag, 29. April 2012 19:23 >> Bis: xen-api@lists.xensource.com >> Betreff: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit ne= twork cards >> >> Another discovery: >> >> On XCP 1.5 >> >> iperf on dom0 to localhost (loopback) >> >> Client connecting to localhost, TCP port 5001 >> TCP window size: 64.0 KByte (default) >> ------------------------------------------------------------ >> [ 3] local 127.0.0.1 port 38278 connected with 127.0.0.1 port 5001 >> ^C[ 3] 0.0- 5.2 sec 1.79 GBytes 2.97 Gbits/sec >> >> Limited to 3gbit >> >> on xapi/debian >> >> root@kronos:~# iperf -c 10.50.50.111 >> ------------------------------------------------------------ >> Client connecting to 10.50.50.111, TCP port 5001 >> TCP window size: 167 KByte (default) >> ------------------------------------------------------------ >> [ 3] local 127.0.0.1 port 41137 connected with 127.0.0.1 port 5001 >> [ ID] Interval Transfer Bandwidth[ 3] 0.0- 5.6 sec 13.1 >> GBytes 20.0 Gbits/sec >> >> clearly not a nic issue.... >> >> Cheers, >> S=E9bastien >> >> >> >> >> >> >> On 29.04.2012 17:28, S=E9bastien Riccio wrote: >>> Me again (sorry), >>> >>> Still trying to sort things out to understand why it's slow under xcp, >>> I've installed xcp on debian (project kronos), and did an iperf from do= m0 >>> >>> [ 3] 0.0- 1.0 sec 623 MBytes 5.23 Gbits/sec >>> [ 3] 1.0- 2.0 sec 817 MBytes 6.85 Gbits/sec >>> [ 3] 2.0- 3.0 sec 818 MBytes 6.86 Gbits/sec >>> [ 3] 3.0- 4.0 sec 816 MBytes 6.84 Gbits/sec >>> [ 3] 4.0- 5.0 sec 818 MBytes 6.86 Gbits/sec >>> [ 3] 5.0- 6.0 sec 818 MBytes 6.86 Gbits/sec >>> [ 3] 6.0- 7.0 sec 816 MBytes 6.85 Gbits/sec >>> >>> It's not getting to the 10gibt/s so it looks that it's related to the >>> xen hypervisor. >>> But it still 2x better than with xcp/xenserver. >>> >>> Any ideas how to improve this? >>> >>> Cheers, >>> S=E9bastien >>> >>> On 29.04.2012 14:44, S=E9bastien Riccio wrote: >>>> Hi again, again :) >>>> >>>> Something strange : >>>> >>>> If i issue parallel threads with iperf (8 in this example, the >>>> 10Gbit/s speed is reached) >>>> >>>> [ 5] 0.0- 1.0 sec 151 MBytes 1.27 Gbits/sec >>>> [ 6] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>>> [ 7] 0.0- 1.0 sec 136 MBytes 1.14 Gbits/sec >>>> [ 8] 0.0- 1.0 sec 189 MBytes 1.59 Gbits/sec >>>> [ 10] 0.0- 1.0 sec 161 MBytes 1.35 Gbits/sec >>>> [ 4] 0.0- 1.0 sec 124 MBytes 1.04 Gbits/sec >>>> [ 3] 0.0- 1.0 sec 178 MBytes 1.49 Gbits/sec >>>> [ 9] 0.0- 1.0 sec 74.8 MBytes 627 Mbits/sec >>>> [SUM] 0.0- 1.0 sec 1.16 GBytes 10.0 Gbits/sec >>>> >>>> So it's surely not a NIC/driver issue but maybe a limitation in dom0 ? >>>> It's really not efficient as we connect the iscsi storage to the >>>> filer from dom0, so it will always be a single thread, so no >>>> possibility to get the full 10Gbit bw for our storage. >>>> >>>> Is there a way to get rid of that (bug?) limitation ? >>>> >>>> Cheers, >>>> S=E9bastien >>>> >>>> >>>> >>>> >>>> On 29.04.2012 14:23, S=E9bastien Riccio wrote: >>>>> Hi again, >>>>> >>>>> So I did my test with a debian 6 on the same hardware than I'm using >>>>> to try the xcp 1.5. >>>>> >>>>> Speed to the filer via the 10gig nic: >>>>> >>>>> [ 3] 0.0- 8.0 sec 8.71 GBytes 9.41 Gbits/sec >>>>> >>>>> I would tend to conclude that there is something wrong with the >>>>> XCP/XenServer kernel and the 10gigs interfaces (at least broadcom). >>>>> >>>>> (Note that our Dell hardware is certified as supported by XenServer, >>>>> so it seems not so true :/) >>>>> >>>>> modinfo for bnx2x on debian 6 >>>>> >>>>> filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/net/bnx2x.= ko >>>>> firmware: bnx2x-e1h-5.0.21.0.fw >>>>> firmware: bnx2x-e1-5.0.21.0.fw >>>>> version: 1.52.1 >>>>> license: GPL >>>>> description: Broadcom NetXtreme II BCM57710/57711/57711E Driver >>>>> author: Eliezer Tamir >>>>> srcversion: 050FF749F80E43CB5873BC9 >>>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>>> depends: mdio,libcrc32c >>>>> vermagic: 2.6.32-5-amd64 SMP mod_unload modversions >>>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>>> (default)) (int) >>>>> parm: num_rx_queues: Number of Rx queues for multi_mode=3D1 >>>>> (default is half number of CPUs) (int) >>>>> parm: num_tx_queues: Number of Tx queues for multi_mode=3D1 >>>>> (default is half number of CPUs) (int) >>>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>>> parm: int_mode: Force interrupt mode (1 INT#x; 2 MSI) (int) >>>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>>> parm: poll: Use polling (for debug) (int) >>>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>>> parm: debug: Default debug msglevel (int) >>>>> >>>>> modinfo for bnx2x on xcp 1.5 >>>>> >>>>> [root@xen-blade13 ~]# modinfo bnx2x >>>>> filename: >>>>> /lib/modules/2.6.32.12-0.7.1.xs1.4.90.530.170661xen/kernel/drivers/ne= t/bnx2x.ko >>>>> version: 1.62.17 >>>>> license: GPL >>>>> description: Broadcom NetXtreme II >>>>> BCM57710/57711/57711E/57712/57712E Driver >>>>> author: Eliezer Tamir >>>>> srcversion: 13EA885EBE061121BAEC28D >>>>> alias: pci:v000014E4d00001663sv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d00001662sv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d00001650sv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* >>>>> alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* >>>>> depends: mdio >>>>> vermagic: 2.6.32.12-0.7.1.xs1.4.90.530.170661xen SMP >>>>> mod_unload modversions Xen 686 >>>>> parm: multi_mode: Multi queue mode (0 Disable; 1 Enable >>>>> (default); 2 VLAN PRI; 3 E1HOV PRI; 4 IP DSCP) (int) >>>>> parm: pri_map: Priority to HW queue mapping (int) >>>>> parm: qs_per_cos: Number of queues per HW queue (int) >>>>> parm: cos_min_rate: Weight for RR between HW queues (int) >>>>> parm: num_queues: Number of queues for multi_mode=3D1 >>>>> (default is as a number of CPUs) (int) >>>>> parm: disable_iscsi_ooo: Disable iSCSI OOO support (int) >>>>> parm: disable_tpa: Disable the TPA (LRO) feature (int) >>>>> parm: int_mode: Force interrupt mode other than MSI-X (1 >>>>> INT#x; 2 MSI) (int) >>>>> parm: dropless_fc: Pause on exhausted host ring (int) >>>>> parm: poll: Use polling (for debug) (int) >>>>> parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) >>>>> parm: debug: Default debug msglevel (int) >>>>> >>>>> Seems that the xcp 1.5 got a more recent version of the module. So >>>>> that might not be the problem. >>>>> Maybe another problem in the kernel ? >>>>> >>>>> Any ideas how I could debug this ? >>>>> >>>>> Cheers, >>>>> S=E9bastien >>>>> >>>>> >>>>> On 29.04.2012 13:23, S=E9bastien Riccio wrote: >>>>>> Hi, >>>>>> >>>>>> I'm currently playing with XCP 1.5 beta on a Dell Blade >>>>>> infrastructure that is linked to redundent filers with 10gbits NICs. >>>>>> >>>>>> The redundent 10gigs interfaces are not managed by xapi (i've told >>>>>> xapi to forget them) and are configured like on any normal linux box. >>>>>> >>>>>> They are connected to the same 10gig switch where the filers are >>>>>> connected to. >>>>>> >>>>>> Interfaces on the filers: >>>>>> 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> 03:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> 04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> >>>>>> Interfaces on the blades: >>>>>> 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> 05:00.1 Ethernet controller: Broadcom Corporation NetXtreme II >>>>>> BCM57711 10-Gigabit PCIe >>>>>> >>>>>> The problem is that after some testing with iperf i get to this >>>>>> conclusion: >>>>>> >>>>>> 1) Between the filers the speed is 9.9Gbit/s. >>>>>> 2) Between xcp 1.5 and both filer i get around 3Gbit/s which is >>>>>> quite poor >>>>>> 2) Between an xcp 1.1 and both filer i get around 3Gbit/s which is >>>>>> quite poor (so that's not a new 1.5 bug) >>>>>> 3) Between an xcp 1.5 and another xcp (1.1) i get too around 3Gbit/s. >>>>>> >>>>>> Do you have any ideas what could be the problem ? knowing that >>>>>> between the filers the speed is good and it's passing through the >>>>>> same switch. >>>>>> >>>>>> Is there a DDK VM available for XCP 1.5 beta? I would like to try >>>>>> to build the latest Broadcom drivers for these nics (bnx2x) for the >>>>>> kernel used on xcp 1.5... >>>>>> >>>>>> In the meantime I will try to install a debian on another blade to >>>>>> check if the speed are correct with the filers. >>>>>> >>>>>> Thanks, >>>>>> S=E9bastien >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>> _______________________________________________ >>> 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 Mon Apr 30 09:13:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 09:13: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 1SOmfD-0003Z0-O6; Mon, 30 Apr 2012 09:12:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmfC-0003Ys-P1 for xen-api@lists.xen.org; Mon, 30 Apr 2012 09:12:58 +0000 Received: from [85.158.143.99:34409] by server-1.bemta-4.messagelabs.com id 5F/3C-20925-A975E9F4; Mon, 30 Apr 2012 09:12:58 +0000 X-Env-Sender: Jonathan.Ludlam@eu.citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1335777176!25847167!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NjkwNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14300 invoked from network); 30 Apr 2012 09:12:56 -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; 30 Apr 2012 09:12:56 -0000 X-IronPort-AV: E=Sophos;i="4.75,503,1330905600"; d="scan'208";a="12199459" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 30 Apr 2012 09:12:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 30 Apr 2012 10:12:55 +0100 From: Jonathan Ludlam To: David Christensen Date: Mon, 30 Apr 2012 10:12:52 +0100 Thread-Topic: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found Thread-Index: Ac0msW2GUyFd1qFcRPubuzO9lzkWQA== Message-ID: References: <4F9DE3BD.1040806@holgerdanske.com> In-Reply-To: <4F9DE3BD.1040806@holgerdanske.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] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Have you managed to get the xe command working at all yet? xe-mount-iso-sr is in /usr/lib/xcp/bin - it's not on the path. Documentation is an area where we're lacking at the moment, unfortunately :-( Jon On 30 Apr 2012, at 01:58, David Christensen wrote: > xen-api: > > I'm attempting to follow along with the xcp-xapi README.Debian on Wheezy > per: > > http://www.debian.org/News/2012/20120425 > > > When I attempt to mount a directory that contains ISO images via NFS, > the "xe-mount-iso-sr" command doesn't seem to exist: > > 2012-04-29 17:48:31 root@i72600s ~ > # xe-mount-iso-sr > -bash: xe-mount-iso-sr: command not found > > > Using Bash tab completion, I don't see any xe-* commands: > > 2012-04-29 17:52:50 root@i72600s ~ > # xe > xe xenstore-chmod xenstore-watch xentrace_setsize > xedit xenstore-exists xenstore-write xev > xen xenstore-list xentop xeyes > xend xenstore-ls xentrace > xenperf xenstore-read xentrace_format > xenpm xenstore-rm xentrace_setmask > > > > Searching the xe help page for anything related to ISO yields nothing: > > 2012-04-29 17:52:50 root@i72600s ~ > # xe help --all | grep -i iso > > > Same goes for the man page: > > 2012-04-29 17:56:47 root@i72600s ~ > # export MANWIDTH=72; man xapi | grep -i iso > and data centers by combining the isolation and multitenancy > capabilities of the Xen hypervisor with enhanced security, > mance and isolation across both private and public clouds. > > > Any suggestions? > > > TIA, > > David > > > > _______________________________________________ > 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 Apr 30 09:13:04 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 09:13: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 1SOmfD-0003Z0-O6; Mon, 30 Apr 2012 09:12:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOmfC-0003Ys-P1 for xen-api@lists.xen.org; Mon, 30 Apr 2012 09:12:58 +0000 Received: from [85.158.143.99:34409] by server-1.bemta-4.messagelabs.com id 5F/3C-20925-A975E9F4; Mon, 30 Apr 2012 09:12:58 +0000 X-Env-Sender: Jonathan.Ludlam@eu.citrix.com X-Msg-Ref: server-9.tower-216.messagelabs.com!1335777176!25847167!1 X-Originating-IP: [62.200.22.115] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjIuMjAwLjIyLjExNSA9PiA5NjkwNw==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14300 invoked from network); 30 Apr 2012 09:12:56 -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; 30 Apr 2012 09:12:56 -0000 X-IronPort-AV: E=Sophos;i="4.75,503,1330905600"; d="scan'208";a="12199459" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 30 Apr 2012 09:12:55 +0000 Received: from LONPMAILBOX01.citrite.net ([10.30.224.160]) by LONPMAILMX01.citrite.net ([10.30.203.162]) with mapi; Mon, 30 Apr 2012 10:12:55 +0100 From: Jonathan Ludlam To: David Christensen Date: Mon, 30 Apr 2012 10:12:52 +0100 Thread-Topic: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found Thread-Index: Ac0msW2GUyFd1qFcRPubuzO9lzkWQA== Message-ID: References: <4F9DE3BD.1040806@holgerdanske.com> In-Reply-To: <4F9DE3BD.1040806@holgerdanske.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] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Have you managed to get the xe command working at all yet? xe-mount-iso-sr is in /usr/lib/xcp/bin - it's not on the path. Documentation is an area where we're lacking at the moment, unfortunately :-( Jon On 30 Apr 2012, at 01:58, David Christensen wrote: > xen-api: > > I'm attempting to follow along with the xcp-xapi README.Debian on Wheezy > per: > > http://www.debian.org/News/2012/20120425 > > > When I attempt to mount a directory that contains ISO images via NFS, > the "xe-mount-iso-sr" command doesn't seem to exist: > > 2012-04-29 17:48:31 root@i72600s ~ > # xe-mount-iso-sr > -bash: xe-mount-iso-sr: command not found > > > Using Bash tab completion, I don't see any xe-* commands: > > 2012-04-29 17:52:50 root@i72600s ~ > # xe > xe xenstore-chmod xenstore-watch xentrace_setsize > xedit xenstore-exists xenstore-write xev > xen xenstore-list xentop xeyes > xend xenstore-ls xentrace > xenperf xenstore-read xentrace_format > xenpm xenstore-rm xentrace_setmask > > > > Searching the xe help page for anything related to ISO yields nothing: > > 2012-04-29 17:52:50 root@i72600s ~ > # xe help --all | grep -i iso > > > Same goes for the man page: > > 2012-04-29 17:56:47 root@i72600s ~ > # export MANWIDTH=72; man xapi | grep -i iso > and data centers by combining the isolation and multitenancy > capabilities of the Xen hypervisor with enhanced security, > mance and isolation across both private and public clouds. > > > Any suggestions? > > > TIA, > > David > > > > _______________________________________________ > 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 Apr 30 14:07:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 14:07: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 1SOrG4-0007Zx-R5; Mon, 30 Apr 2012 14:07:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOrG3-0007Zg-Qt for xen-api@lists.xen.org; Mon, 30 Apr 2012 14:07:19 +0000 Received: from [85.158.143.35:5953] by server-3.bemta-4.messagelabs.com id 74/A8-05853-79C9E9F4; Mon, 30 Apr 2012 14:07:19 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1335794837!12147447!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 18936 invoked from network); 30 Apr 2012 14:07:18 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2012 14:07:18 -0000 Received: by bkty15 with SMTP id y15so2383907bkt.32 for ; Mon, 30 Apr 2012 07:07:17 -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=u88rlYbvqAmT/KH1+3YrAFV0pVnmnf/DinTh0/GwT30=; b=vbTjVOfMYHWs0AhQsEMnJtSY7HTLnXOASGrUYRKc9g6ZWp6WY7GzwlckznBnDYh7Ki 9hzEDmHrX8/q3ObrqxzvffHjiCVUyJ0+E0/Kjbe3d6Sloj7ubKGMtY26th6nyJIU5hY3 Ooae45n7iYqAqL1Fks/wF1p5T/wSpHCUWpWsds8Jn/6jWIgTXFKaiIQ4NUzBYrDpNQmf D3X51nwDqzv7vmKAp8UqPofnV9FfCOfMqpjaGF1jEPjDWKUiWxyP5DSr0WYxlLR8dJKv cRy9djQ9W6NmzvVRnSvhLck7M4Qv7UTusKmkglRNtR4y4gj0As0tDtjo1velGep3tFqs fN0g== Received: by 10.205.133.210 with SMTP id hz18mr7016487bkc.117.1335794837078; Mon, 30 Apr 2012 07:07:17 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id h18sm27243851bkh.8.2012.04.30.07.07.15 (version=SSLv3 cipher=OTHER); Mon, 30 Apr 2012 07:07:15 -0700 (PDT) Message-ID: <4F9E9C91.50403@xen.org> Date: Mon, 30 Apr 2012 15:07:13 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org, xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: [Xen-API] Regarding a XenDev Day at XenSummit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Development list for XCP and Xen API 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 everybody, we had an overwhelming vote for a 1/2 day invite only DevDay on the Sunday before XenSummit. I will look at logistics and then get back to you. Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Apr 30 14:07:29 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 14:07: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 1SOrG4-0007Zx-R5; Mon, 30 Apr 2012 14:07:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOrG3-0007Zg-Qt for xen-api@lists.xen.org; Mon, 30 Apr 2012 14:07:19 +0000 Received: from [85.158.143.35:5953] by server-3.bemta-4.messagelabs.com id 74/A8-05853-79C9E9F4; Mon, 30 Apr 2012 14:07:19 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1335794837!12147447!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 18936 invoked from network); 30 Apr 2012 14:07:18 -0000 Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com) (209.85.214.45) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 30 Apr 2012 14:07:18 -0000 Received: by bkty15 with SMTP id y15so2383907bkt.32 for ; Mon, 30 Apr 2012 07:07:17 -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=u88rlYbvqAmT/KH1+3YrAFV0pVnmnf/DinTh0/GwT30=; b=vbTjVOfMYHWs0AhQsEMnJtSY7HTLnXOASGrUYRKc9g6ZWp6WY7GzwlckznBnDYh7Ki 9hzEDmHrX8/q3ObrqxzvffHjiCVUyJ0+E0/Kjbe3d6Sloj7ubKGMtY26th6nyJIU5hY3 Ooae45n7iYqAqL1Fks/wF1p5T/wSpHCUWpWsds8Jn/6jWIgTXFKaiIQ4NUzBYrDpNQmf D3X51nwDqzv7vmKAp8UqPofnV9FfCOfMqpjaGF1jEPjDWKUiWxyP5DSr0WYxlLR8dJKv cRy9djQ9W6NmzvVRnSvhLck7M4Qv7UTusKmkglRNtR4y4gj0As0tDtjo1velGep3tFqs fN0g== Received: by 10.205.133.210 with SMTP id hz18mr7016487bkc.117.1335794837078; Mon, 30 Apr 2012 07:07:17 -0700 (PDT) Received: from [172.16.25.10] (b0fb6237.bb.sky.com. [176.251.98.55]) by mx.google.com with ESMTPS id h18sm27243851bkh.8.2012.04.30.07.07.15 (version=SSLv3 cipher=OTHER); Mon, 30 Apr 2012 07:07:15 -0700 (PDT) Message-ID: <4F9E9C91.50403@xen.org> Date: Mon, 30 Apr 2012 15:07:13 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: xen-api@lists.xen.org, xen-arm@lists.xen.org, xen-devel@lists.xen.org Subject: [Xen-API] Regarding a XenDev Day at XenSummit X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Development list for XCP and Xen API 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 everybody, we had an overwhelming vote for a 1/2 day invite only DevDay on the Sunday before XenSummit. I will look at logistics and then get back to you. Regards Lars _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api From xen-api-bounces@lists.xen.org Mon Apr 30 14:54:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 14:54: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 1SOrzC-0001GO-Ub; Mon, 30 Apr 2012 14:53:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOrzA-0001GH-W2 for xen-api@lists.xensource.com; Mon, 30 Apr 2012 14:53:57 +0000 Received: from [85.158.138.51:32135] by server-4.bemta-3.messagelabs.com id 10/2A-15341-487AE9F4; Mon, 30 Apr 2012 14:53:56 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1335797634!20429728!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDUwMjcyMQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21027 invoked from network); 30 Apr 2012 14:53:55 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-10.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2012 14:53:55 -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 q3UErjwG025909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 30 Apr 2012 14:53:46 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 q3UEriUX007788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Apr 2012 14:53:44 GMT Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q3UErh5O030398; Mon, 30 Apr 2012 09:53:43 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 30 Apr 2012 07:53:42 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 5D8DA40357; Mon, 30 Apr 2012 10:48:01 -0400 (EDT) Date: Mon, 30 Apr 2012 10:48:01 -0400 From: Konrad Rzeszutek Wilk To: =?iso-8859-1?Q?S=E9bastien?= Riccio Message-ID: <20120430144801.GC16668@phenom.dumpdata.com> References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com> <4F9D7917.8060804@swisscenter.com> <4F9E4F92.3080200@swisscenter.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4F9E4F92.3080200@swisscenter.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Mon, Apr 30, 2012 at 10:38:42AM +0200, S=E9bastien Riccio wrote: > Hi, > = > Yes I've almost tried everything that is on the network tweaking guide: > = > http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide > = > But the bottleneck seems to be the xen hypervisor used in xcp and xenserv= er. > = > On the same machine but with xcp-xapi (over debian) I get almost > normal 10gbit/s speeds from dom0. Debian meaning what version? 3.0 kernel? _______________________________________________ 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 Apr 30 14:54:03 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 14:54: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 1SOrzC-0001GO-Ub; Mon, 30 Apr 2012 14:53:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOrzA-0001GH-W2 for xen-api@lists.xensource.com; Mon, 30 Apr 2012 14:53:57 +0000 Received: from [85.158.138.51:32135] by server-4.bemta-3.messagelabs.com id 10/2A-15341-487AE9F4; Mon, 30 Apr 2012 14:53:56 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-10.tower-174.messagelabs.com!1335797634!20429728!1 X-Originating-IP: [141.146.126.227] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuMjI3ID0+IDUwMjcyMQ==\n X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21027 invoked from network); 30 Apr 2012 14:53:55 -0000 Received: from acsinet15.oracle.com (HELO acsinet15.oracle.com) (141.146.126.227) by server-10.tower-174.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2012 14:53:55 -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 q3UErjwG025909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 30 Apr 2012 14:53:46 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 q3UEriUX007788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Apr 2012 14:53:44 GMT Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q3UErh5O030398; Mon, 30 Apr 2012 09:53:43 -0500 Received: from phenom.dumpdata.com (/209.6.85.33) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 30 Apr 2012 07:53:42 -0700 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 5D8DA40357; Mon, 30 Apr 2012 10:48:01 -0400 (EDT) Date: Mon, 30 Apr 2012 10:48:01 -0400 From: Konrad Rzeszutek Wilk To: =?iso-8859-1?Q?S=E9bastien?= Riccio Message-ID: <20120430144801.GC16668@phenom.dumpdata.com> References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com> <4F9D7917.8060804@swisscenter.com> <4F9E4F92.3080200@swisscenter.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4F9E4F92.3080200@swisscenter.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 Mon, Apr 30, 2012 at 10:38:42AM +0200, S=E9bastien Riccio wrote: > Hi, > = > Yes I've almost tried everything that is on the network tweaking guide: > = > http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide > = > But the bottleneck seems to be the xen hypervisor used in xcp and xenserv= er. > = > On the same machine but with xcp-xapi (over debian) I get almost > normal 10gbit/s speeds from dom0. Debian meaning what version? 3.0 kernel? _______________________________________________ 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 Apr 30 15:45:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 15:45:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOsmt-0001xD-64; Mon, 30 Apr 2012 15:45:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOsmr-0001x8-8G for xen-api@lists.xensource.com; Mon, 30 Apr 2012 15:45:17 +0000 Received: from [85.158.143.99:45360] by server-3.bemta-4.messagelabs.com id 11/4D-05853-C83BE9F4; Mon, 30 Apr 2012 15:45:16 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1335800714!18850229!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22173 invoked from network); 30 Apr 2012 15:45:15 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-6.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2012 15:45:15 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3UFj8u7006843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Apr 2012 17:45:09 +0200 Message-ID: <4F9EB383.7030105@swisscenter.com> Date: Mon, 30 Apr 2012 17:45:07 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com> <4F9D7917.8060804@swisscenter.com> <4F9E4F92.3080200@swisscenter.com> <20120430144801.GC16668@phenom.dumpdata.com> In-Reply-To: <20120430144801.GC16668@phenom.dumpdata.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 root@xen-blade11:~# uname -a Linux xen-blade11 3.2.0-2-686-pae #1 SMP Sun Apr 15 17:56:31 UTC 2012 = i686 GNU/Linux (debian unstable) On 30.04.2012 16:48, Konrad Rzeszutek Wilk wrote: > On Mon, Apr 30, 2012 at 10:38:42AM +0200, S=E9bastien Riccio wrote: >> Hi, >> >> Yes I've almost tried everything that is on the network tweaking guide: >> >> http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide >> >> But the bottleneck seems to be the xen hypervisor used in xcp and xenser= ver. >> >> On the same machine but with xcp-xapi (over debian) I get almost >> normal 10gbit/s speeds from dom0. > Debian meaning what version? 3.0 kernel? > _______________________________________________ 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 Apr 30 15:45:25 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 15:45:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOsmt-0001xD-64; Mon, 30 Apr 2012 15:45:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOsmr-0001x8-8G for xen-api@lists.xensource.com; Mon, 30 Apr 2012 15:45:17 +0000 Received: from [85.158.143.99:45360] by server-3.bemta-4.messagelabs.com id 11/4D-05853-C83BE9F4; Mon, 30 Apr 2012 15:45:16 +0000 X-Env-Sender: sr@swisscenter.com X-Msg-Ref: server-6.tower-216.messagelabs.com!1335800714!18850229!1 X-Originating-IP: [94.103.96.90] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22173 invoked from network); 30 Apr 2012 15:45:15 -0000 Received: from mail.swisslink.ch (HELO mail.swisslink.ch) (94.103.96.90) by server-6.tower-216.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 30 Apr 2012 15:45:15 -0000 Received: from [10.8.0.10] (gate.swisslink.ch [62.2.195.10]) (authenticated bits=0) by mail.swisslink.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id q3UFj8u7006843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Apr 2012 17:45:09 +0200 Message-ID: <4F9EB383.7030105@swisscenter.com> Date: Mon, 30 Apr 2012 17:45:07 +0200 From: =?ISO-8859-1?Q?S=E9bastien_Riccio?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk References: <4F9D24B9.8010508@swisscenter.com> <4F9D32B3.6010501@swisscenter.com> <4F9D3797.5050406@swisscenter.com> <4F9D5E2F.2090906@swisscenter.com> <4F9D7917.8060804@swisscenter.com> <4F9E4F92.3080200@swisscenter.com> <20120430144801.GC16668@phenom.dumpdata.com> In-Reply-To: <20120430144801.GC16668@phenom.dumpdata.com> X-Virus-Scanned: clamav-milter 0.97.3 at mail X-Virus-Status: Clean Cc: "xen-api@lists.xensource.com" Subject: Re: [Xen-API] XCP 1.5 BETA BUG: Slow performance with 10Gbit network cards X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 root@xen-blade11:~# uname -a Linux xen-blade11 3.2.0-2-686-pae #1 SMP Sun Apr 15 17:56:31 UTC 2012 = i686 GNU/Linux (debian unstable) On 30.04.2012 16:48, Konrad Rzeszutek Wilk wrote: > On Mon, Apr 30, 2012 at 10:38:42AM +0200, S=E9bastien Riccio wrote: >> Hi, >> >> Yes I've almost tried everything that is on the network tweaking guide: >> >> http://wiki.xen.org/wiki/Network_Throughput_and_Performance_Guide >> >> But the bottleneck seems to be the xen hypervisor used in xcp and xenser= ver. >> >> On the same machine but with xcp-xapi (over debian) I get almost >> normal 10gbit/s speeds from dom0. > Debian meaning what version? 3.0 kernel? > _______________________________________________ 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 Apr 30 17:00:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 17:00:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOtxv-0002kv-24; Mon, 30 Apr 2012 17:00:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOtxu-0002kq-26 for xen-api@lists.xen.org; Mon, 30 Apr 2012 17:00:46 +0000 Received: from [85.158.139.83:43011] by server-6.bemta-5.messagelabs.com id FF/D1-13222-D35CE9F4; Mon, 30 Apr 2012 17:00:45 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1335805242!23433445!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26639 invoked from network); 30 Apr 2012 17:00:43 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-4.tower-182.messagelabs.com with SMTP; 30 Apr 2012 17:00:43 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Mon, 30 Apr 2012 10:00:29 -0700 Message-ID: <4F9EC52C.60208@holgerdanske.com> Date: Mon, 30 Apr 2012 10:00:28 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <4F9DE3BD.1040806@holgerdanske.com> In-Reply-To: Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 04/30/2012 02:12 AM, Jonathan Ludlam wrote: Thanks for the reply. :-) > Have you managed to get the xe command working at all yet? Yes: http://lists.xen.org/archives/html/xen-api/2012-04/msg00057.html > xe-mount-iso-sr is in /usr/lib/xcp/bin - it's not on the path. Sneaky. Next time, I'll try to remember to locate it: 2012-04-30 09:26:38 root@i72600s ~ # locate xe-mount-iso-sr /usr/lib/xcp/bin/xe-mount-iso-sr > Documentation is an area where we're lacking at the moment, unfortunately :-( Producing software for FOSS OS's is a conundrum -- every vendor and distribution is different (Debian GNU/Linux, GNU/kFreeBSD, i386, amd64, stable, testing, unstable, etc.; Red Hat ...; SUSE ...; *BSD ..., OpenSolaris ..., etc.). There are too many permutations, which imposes uncomfortable choices and duplicated effort. Fortunately, I'm using Debian GNU/Linux amd64 testing and the Debian and Xen projects are making an effort to make XCP available on this platform. :-) David _______________________________________________ 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 Apr 30 17:00:54 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 17:00:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOtxv-0002kv-24; Mon, 30 Apr 2012 17:00:47 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOtxu-0002kq-26 for xen-api@lists.xen.org; Mon, 30 Apr 2012 17:00:46 +0000 Received: from [85.158.139.83:43011] by server-6.bemta-5.messagelabs.com id FF/D1-13222-D35CE9F4; Mon, 30 Apr 2012 17:00:45 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-4.tower-182.messagelabs.com!1335805242!23433445!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26639 invoked from network); 30 Apr 2012 17:00:43 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-4.tower-182.messagelabs.com with SMTP; 30 Apr 2012 17:00:43 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Mon, 30 Apr 2012 10:00:29 -0700 Message-ID: <4F9EC52C.60208@holgerdanske.com> Date: Mon, 30 Apr 2012 10:00:28 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <4F9DE3BD.1040806@holgerdanske.com> In-Reply-To: Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 04/30/2012 02:12 AM, Jonathan Ludlam wrote: Thanks for the reply. :-) > Have you managed to get the xe command working at all yet? Yes: http://lists.xen.org/archives/html/xen-api/2012-04/msg00057.html > xe-mount-iso-sr is in /usr/lib/xcp/bin - it's not on the path. Sneaky. Next time, I'll try to remember to locate it: 2012-04-30 09:26:38 root@i72600s ~ # locate xe-mount-iso-sr /usr/lib/xcp/bin/xe-mount-iso-sr > Documentation is an area where we're lacking at the moment, unfortunately :-( Producing software for FOSS OS's is a conundrum -- every vendor and distribution is different (Debian GNU/Linux, GNU/kFreeBSD, i386, amd64, stable, testing, unstable, etc.; Red Hat ...; SUSE ...; *BSD ..., OpenSolaris ..., etc.). There are too many permutations, which imposes uncomfortable choices and duplicated effort. Fortunately, I'm using Debian GNU/Linux amd64 testing and the Debian and Xen projects are making an effort to make XCP available on this platform. :-) David _______________________________________________ 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 Apr 30 18:09:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 18:09:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOv2a-0003rd-5p; Mon, 30 Apr 2012 18:09:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOv2Y-0003rY-4K for xen-api@lists.xen.org; Mon, 30 Apr 2012 18:09:38 +0000 Received: from [85.158.138.51:5040] by server-10.bemta-3.messagelabs.com id 08/C6-29478-165DE9F4; Mon, 30 Apr 2012 18:09:37 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1335809373!24497338!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3290 invoked from network); 30 Apr 2012 18:09:34 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-3.tower-174.messagelabs.com with SMTP; 30 Apr 2012 18:09:34 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Mon, 30 Apr 2012 11:09:25 -0700 Message-ID: <4F9ED555.6020702@holgerdanske.com> Date: Mon, 30 Apr 2012 11:09:25 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Debian Wheezy xcp-xapi winbind hangs and times out on shutdown X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 xen-xapi: I recently built a new computer with Debian Wheezy and xcp-xapi. I've noticed that winbind hangs and times out on shutdown. I can't remember if this happened prior to installing xcp-xapi (?). How do I troubleshoot winbind hanging on shutdown? TIA, David -- 2012-04-30 08:54:31 root@i72600s ~ # cat /etc/default/winbind # Defaults for winbind initscript # sourced by /etc/init.d/winbind # # # This is a POSIX shell fragment # # Winbind configuration #WINBINDD_OPTS="-n" 2012-04-30 08:55:44 root@i72600s ~ # cat /etc/init.d/winbind #!/bin/sh ### BEGIN INIT INFO # Provides: winbind # Required-Start: $network $remote_fs $syslog # Required-Stop: $network $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: start Winbind daemon ### END INIT INFO PATH=/sbin:/bin:/usr/sbin:/usr/bin [ -r /etc/default/winbind ] && . /etc/default/winbind DAEMON=/usr/sbin/winbindd PIDDIR=/var/run/samba WINBINDPID=$PIDDIR/winbindd.pid # clear conflicting settings from the environment unset TMPDIR # See if the daemon is there test -x $DAEMON || exit 0 . /lib/lsb/init-functions case "$1" in start) log_daemon_msg "Starting the Winbind daemon" "winbind" mkdir -p /var/run/samba/winbindd_privileged || return 1 chgrp winbindd_priv $PIDDIR/winbindd_privileged/ || return 1 chmod 0750 $PIDDIR/winbindd_privileged/ || return 1 start-stop-daemon --start --quiet --oknodo --exec $DAEMON -- $WINBINDD_OPTS log_end_msg $? ;; stop) log_daemon_msg "Stopping the Winbind daemon" "winbind" start-stop-daemon --stop --quiet --oknodo --exec $DAEMON log_end_msg $? ;; restart|force-reload) $0 stop && sleep 2 && $0 start ;; status) status_of_proc -p $WINBINDPID $DAEMON winbind && exit 0 || exit $? ;; *) echo "Usage: /etc/init.d/winbind {start|stop|restart|force-reload|status}" exit 1 ;; esac 2012-04-30 08:59:02 root@i72600s ~ # grep -r winbind /var/log/* /var/log/apt/term.log:Selecting previously unselected package winbind. /var/log/apt/term.log:Unpacking winbind (from .../winbind_2%3a3.6.4-1_amd64.deb) ... /var/log/apt/term.log:Selecting previously unselected package libpam-winbind:amd64. /var/log/apt/term.log:Unpacking libpam-winbind:amd64 (from .../libpam-winbind_2%3a3.6.4-1_amd64.deb) ... /var/log/apt/term.log:Setting up winbind (2:3.6.4-1) ... /var/log/apt/term.log:Starting the Winbind daemon: winbind. /var/log/apt/term.log:Setting up libpam-winbind:amd64 (2:3.6.4-1) ... /var/log/apt/history.log:Install: blktap-dkms:amd64 (2.0.91-1, automatic), libpam-winbind:amd64 (3.6.4-1, automatic), linux-headers-amd64:amd64 (3.2+44, automatic), uuid-runtime:amd64 (2.20.1-4, automatic), fakeroot:amd64 (1.18.2-1, automatic), librbd1:amd64 (0.43-1, automatic), xcp-storage-managers:amd64 (0.1.1-2, automatic), xen-hypervisor-4.1-amd64:amd64 (4.1.2-2, automatic), xen-utils-common:amd64 (4.1.2-1, automatic), qemu-keymaps:amd64 (1.0.1+dfsg-1, automatic), libaio1:amd64 (0.3.109-2, automatic), libcrypto++9:amd64 (5.6.1-6, automatic), smbfs:amd64 (5.3-2, automatic), libiscsi1:amd64 (1.0.1-1, automatic), xcp-vncterm:amd64 (0.1-2, automatic), xen-utils-4.1:amd64 (4.1.2-2, automatic), libblktapctl0:amd64 (2.0.90-1, automatic), librados2:amd64 (0.43-1, automatic), libvhdio-2.0.90:amd64 (2.0.90-1, automatic), libxenstore3.0:amd64 (4.1.2-2, automatic), gcc-4.6:amd64 (4.6.3-1, automatic), libvhd0:amd64 (2.0.90-1, automatic), stunnel4:amd64 (4.52-1, automatic), linux-headers-3.2.0-2-amd64:amd64 (3.2.15-1, automatic), xcp-squeezed:amd64 (1.3-16, automatic), xcp-eliloader:amd64 (0.1-4, automatic), gcc:amd64 (4.6.2-4, automatic), python-xenapi:amd64 (1.3-16, automatic), dkms:amd64 (2.2.0.3-1, automatic), gawk:amd64 (4.0.1+dfsg-1, automatic), linux-kbuild-3.2:amd64 (3.2.7-2, automatic), blktap-utils:amd64 (2.0.90-1, automatic), libc6-dev:amd64 (2.13-30, automatic), libsigsegv2:amd64 (2.9-4, automatic), cifs-utils:amd64 (5.3-2, automatic), qemu-utils:amd64 (1.0.1+dfsg-1, automatic), xcp-guest-templates:amd64 (0.1-3, automatic), libxen-4.1:amd64 (4.1.2-2, automatic), xcp-v6d:amd64 (1.3-16, automatic), linux-libc-dev:amd64 (3.2.15-1, automatic), xcp-xapi:amd64 (1.3-16), manpages-dev:amd64 (3.35-0.1, automatic), winbind:amd64 (3.6.4-1, automatic), bridge-utils:amd64 (1.5-2, automatic), libc-dev-bin:amd64 (2.13-30, automatic), binutils:amd64 (2.22-6, automatic), xcp-fe:amd64 (0.5.2-3, automatic), keyutils:amd64 (1.5.5-2, automatic), linux-headers-3.2.0-2-common:amd64 (3.2.15-1, automatic), make:amd64 (3.81-8.2, automatic), xcp-xe:amd64 (1.3-16, automatic), xenstore-utils:amd64 (4.1.2-2, automatic) /var/log/auth.log.1:Apr 27 21:42:20 i72600s groupadd[8456]: group added to /etc/group: name=winbindd_priv, GID=123 /var/log/auth.log.1:Apr 27 21:42:20 i72600s groupadd[8456]: group added to /etc/gshadow: name=winbindd_priv /var/log/auth.log.1:Apr 27 21:42:20 i72600s groupadd[8456]: new group: name=winbindd_priv, GID=123 /var/log/auth.log.1:Apr 28 14:18:00 i72600s gdm-session-worker[4597]: pam_winbind(gdm3:auth): getting password (0x00000388) /var/log/auth.log.1:Apr 28 14:18:00 i72600s gdm-session-worker[4597]: pam_winbind(gdm3:auth): Could not retrieve user's password /var/log/dpkg.log:2012-04-27 21:41:59 install winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status half-installed winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status half-installed winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 install libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status half-installed libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status half-installed libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status unpacked libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status unpacked libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 configure winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status half-configured winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 status installed winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 configure libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 status unpacked libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 status half-configured libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 status installed libpam-winbind:amd64 2:3.6.4-1 /var/log/samba/log.winbindd:[2012/04/29 11:58:07.387607, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.winbindd:[2012/04/29 15:31:06, 0] winbindd/winbindd.c:1336(main) /var/log/samba/log.winbindd: winbindd version 3.6.4 started. /var/log/samba/log.winbindd:[2012/04/29 15:31:06.042410, 0] winbindd/winbindd_cache.c:3147(initialize_winbindd_cache) /var/log/samba/log.winbindd: initialize_winbindd_cache: clearing cache and re-creating with version number 2 /var/log/samba/log.winbindd:[2012/04/29 16:01:00.913425, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.winbindd:[2012/04/29 16:02:29, 0] winbindd/winbindd.c:1336(main) /var/log/samba/log.winbindd: winbindd version 3.6.4 started. /var/log/samba/log.winbindd:[2012/04/29 16:02:29.484990, 0] winbindd/winbindd_cache.c:3147(initialize_winbindd_cache) /var/log/samba/log.winbindd: initialize_winbindd_cache: clearing cache and re-creating with version number 2 /var/log/samba/log.winbindd:[2012/04/29 23:15:58.121524, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.winbindd:[2012/04/30 08:49:10, 0] winbindd/winbindd.c:1336(main) /var/log/samba/log.winbindd: winbindd version 3.6.4 started. /var/log/samba/log.winbindd:[2012/04/30 08:49:10.842746, 0] winbindd/winbindd_cache.c:3147(initialize_winbindd_cache) /var/log/samba/log.winbindd: initialize_winbindd_cache: clearing cache and re-creating with version number 2 /var/log/samba/log.wb-I72600S:[2012/04/27 21:58:12.012104, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/27 23:07:24.660043, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/27 23:25:13.050986, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/28 14:18:06.280048, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/28 15:38:35.138139, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/28 16:21:02.391059, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/29 11:58:07.387594, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/29 16:01:00.913603, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/29 23:15:58.121520, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) 2012-04-30 09:06:54 root@i72600s ~ # grep 'Apr 29 23' /var/log/messages Apr 29 23:15:54 i72600s shutdown[3437]: shutting down for system halt Apr 29 23:16:28 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:34 i72600s rsyslogd-2177: imuxsock lost 282210 messages from pid 2313 due to rate-limiting Apr 29 23:16:34 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:40 i72600s rsyslogd-2177: imuxsock lost 286410 messages from pid 2313 due to rate-limiting Apr 29 23:16:40 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:46 i72600s rsyslogd-2177: imuxsock lost 289712 messages from pid 2313 due to rate-limiting Apr 29 23:16:46 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:52 i72600s rsyslogd-2177: imuxsock lost 290233 messages from pid 2313 due to rate-limiting Apr 29 23:16:52 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:58 i72600s rsyslogd-2177: imuxsock lost 290022 messages from pid 2313 due to rate-limiting Apr 29 23:16:58 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:17:00 i72600s kernel: Kernel logging (proc) stopped. Apr 29 23:17:00 i72600s rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1476" x-info="http://www.rsyslog.com"] exiting on signal 15. _______________________________________________ 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 Apr 30 18:09:48 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 18:09:48 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOv2a-0003rd-5p; Mon, 30 Apr 2012 18:09:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOv2Y-0003rY-4K for xen-api@lists.xen.org; Mon, 30 Apr 2012 18:09:38 +0000 Received: from [85.158.138.51:5040] by server-10.bemta-3.messagelabs.com id 08/C6-29478-165DE9F4; Mon, 30 Apr 2012 18:09:37 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-3.tower-174.messagelabs.com!1335809373!24497338!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3290 invoked from network); 30 Apr 2012 18:09:34 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-3.tower-174.messagelabs.com with SMTP; 30 Apr 2012 18:09:34 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Mon, 30 Apr 2012 11:09:25 -0700 Message-ID: <4F9ED555.6020702@holgerdanske.com> Date: Mon, 30 Apr 2012 11:09:25 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: xen-api@lists.xen.org Subject: [Xen-API] Debian Wheezy xcp-xapi winbind hangs and times out on shutdown X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API 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 xen-xapi: I recently built a new computer with Debian Wheezy and xcp-xapi. I've noticed that winbind hangs and times out on shutdown. I can't remember if this happened prior to installing xcp-xapi (?). How do I troubleshoot winbind hanging on shutdown? TIA, David -- 2012-04-30 08:54:31 root@i72600s ~ # cat /etc/default/winbind # Defaults for winbind initscript # sourced by /etc/init.d/winbind # # # This is a POSIX shell fragment # # Winbind configuration #WINBINDD_OPTS="-n" 2012-04-30 08:55:44 root@i72600s ~ # cat /etc/init.d/winbind #!/bin/sh ### BEGIN INIT INFO # Provides: winbind # Required-Start: $network $remote_fs $syslog # Required-Stop: $network $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: start Winbind daemon ### END INIT INFO PATH=/sbin:/bin:/usr/sbin:/usr/bin [ -r /etc/default/winbind ] && . /etc/default/winbind DAEMON=/usr/sbin/winbindd PIDDIR=/var/run/samba WINBINDPID=$PIDDIR/winbindd.pid # clear conflicting settings from the environment unset TMPDIR # See if the daemon is there test -x $DAEMON || exit 0 . /lib/lsb/init-functions case "$1" in start) log_daemon_msg "Starting the Winbind daemon" "winbind" mkdir -p /var/run/samba/winbindd_privileged || return 1 chgrp winbindd_priv $PIDDIR/winbindd_privileged/ || return 1 chmod 0750 $PIDDIR/winbindd_privileged/ || return 1 start-stop-daemon --start --quiet --oknodo --exec $DAEMON -- $WINBINDD_OPTS log_end_msg $? ;; stop) log_daemon_msg "Stopping the Winbind daemon" "winbind" start-stop-daemon --stop --quiet --oknodo --exec $DAEMON log_end_msg $? ;; restart|force-reload) $0 stop && sleep 2 && $0 start ;; status) status_of_proc -p $WINBINDPID $DAEMON winbind && exit 0 || exit $? ;; *) echo "Usage: /etc/init.d/winbind {start|stop|restart|force-reload|status}" exit 1 ;; esac 2012-04-30 08:59:02 root@i72600s ~ # grep -r winbind /var/log/* /var/log/apt/term.log:Selecting previously unselected package winbind. /var/log/apt/term.log:Unpacking winbind (from .../winbind_2%3a3.6.4-1_amd64.deb) ... /var/log/apt/term.log:Selecting previously unselected package libpam-winbind:amd64. /var/log/apt/term.log:Unpacking libpam-winbind:amd64 (from .../libpam-winbind_2%3a3.6.4-1_amd64.deb) ... /var/log/apt/term.log:Setting up winbind (2:3.6.4-1) ... /var/log/apt/term.log:Starting the Winbind daemon: winbind. /var/log/apt/term.log:Setting up libpam-winbind:amd64 (2:3.6.4-1) ... /var/log/apt/history.log:Install: blktap-dkms:amd64 (2.0.91-1, automatic), libpam-winbind:amd64 (3.6.4-1, automatic), linux-headers-amd64:amd64 (3.2+44, automatic), uuid-runtime:amd64 (2.20.1-4, automatic), fakeroot:amd64 (1.18.2-1, automatic), librbd1:amd64 (0.43-1, automatic), xcp-storage-managers:amd64 (0.1.1-2, automatic), xen-hypervisor-4.1-amd64:amd64 (4.1.2-2, automatic), xen-utils-common:amd64 (4.1.2-1, automatic), qemu-keymaps:amd64 (1.0.1+dfsg-1, automatic), libaio1:amd64 (0.3.109-2, automatic), libcrypto++9:amd64 (5.6.1-6, automatic), smbfs:amd64 (5.3-2, automatic), libiscsi1:amd64 (1.0.1-1, automatic), xcp-vncterm:amd64 (0.1-2, automatic), xen-utils-4.1:amd64 (4.1.2-2, automatic), libblktapctl0:amd64 (2.0.90-1, automatic), librados2:amd64 (0.43-1, automatic), libvhdio-2.0.90:amd64 (2.0.90-1, automatic), libxenstore3.0:amd64 (4.1.2-2, automatic), gcc-4.6:amd64 (4.6.3-1, automatic), libvhd0:amd64 (2.0.90-1, automatic), stunnel4:amd64 (4.52-1, automatic), linux-headers-3.2.0-2-amd64:amd64 (3.2.15-1, automatic), xcp-squeezed:amd64 (1.3-16, automatic), xcp-eliloader:amd64 (0.1-4, automatic), gcc:amd64 (4.6.2-4, automatic), python-xenapi:amd64 (1.3-16, automatic), dkms:amd64 (2.2.0.3-1, automatic), gawk:amd64 (4.0.1+dfsg-1, automatic), linux-kbuild-3.2:amd64 (3.2.7-2, automatic), blktap-utils:amd64 (2.0.90-1, automatic), libc6-dev:amd64 (2.13-30, automatic), libsigsegv2:amd64 (2.9-4, automatic), cifs-utils:amd64 (5.3-2, automatic), qemu-utils:amd64 (1.0.1+dfsg-1, automatic), xcp-guest-templates:amd64 (0.1-3, automatic), libxen-4.1:amd64 (4.1.2-2, automatic), xcp-v6d:amd64 (1.3-16, automatic), linux-libc-dev:amd64 (3.2.15-1, automatic), xcp-xapi:amd64 (1.3-16), manpages-dev:amd64 (3.35-0.1, automatic), winbind:amd64 (3.6.4-1, automatic), bridge-utils:amd64 (1.5-2, automatic), libc-dev-bin:amd64 (2.13-30, automatic), binutils:amd64 (2.22-6, automatic), xcp-fe:amd64 (0.5.2-3, automatic), keyutils:amd64 (1.5.5-2, automatic), linux-headers-3.2.0-2-common:amd64 (3.2.15-1, automatic), make:amd64 (3.81-8.2, automatic), xcp-xe:amd64 (1.3-16, automatic), xenstore-utils:amd64 (4.1.2-2, automatic) /var/log/auth.log.1:Apr 27 21:42:20 i72600s groupadd[8456]: group added to /etc/group: name=winbindd_priv, GID=123 /var/log/auth.log.1:Apr 27 21:42:20 i72600s groupadd[8456]: group added to /etc/gshadow: name=winbindd_priv /var/log/auth.log.1:Apr 27 21:42:20 i72600s groupadd[8456]: new group: name=winbindd_priv, GID=123 /var/log/auth.log.1:Apr 28 14:18:00 i72600s gdm-session-worker[4597]: pam_winbind(gdm3:auth): getting password (0x00000388) /var/log/auth.log.1:Apr 28 14:18:00 i72600s gdm-session-worker[4597]: pam_winbind(gdm3:auth): Could not retrieve user's password /var/log/dpkg.log:2012-04-27 21:41:59 install winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status half-installed winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status half-installed winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 install libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status half-installed libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status half-installed libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status unpacked libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:41:59 status unpacked libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 configure winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status unpacked winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:19 status half-configured winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 status installed winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 configure libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 status unpacked libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 status half-configured libpam-winbind:amd64 2:3.6.4-1 /var/log/dpkg.log:2012-04-27 21:42:20 status installed libpam-winbind:amd64 2:3.6.4-1 /var/log/samba/log.winbindd:[2012/04/29 11:58:07.387607, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.winbindd:[2012/04/29 15:31:06, 0] winbindd/winbindd.c:1336(main) /var/log/samba/log.winbindd: winbindd version 3.6.4 started. /var/log/samba/log.winbindd:[2012/04/29 15:31:06.042410, 0] winbindd/winbindd_cache.c:3147(initialize_winbindd_cache) /var/log/samba/log.winbindd: initialize_winbindd_cache: clearing cache and re-creating with version number 2 /var/log/samba/log.winbindd:[2012/04/29 16:01:00.913425, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.winbindd:[2012/04/29 16:02:29, 0] winbindd/winbindd.c:1336(main) /var/log/samba/log.winbindd: winbindd version 3.6.4 started. /var/log/samba/log.winbindd:[2012/04/29 16:02:29.484990, 0] winbindd/winbindd_cache.c:3147(initialize_winbindd_cache) /var/log/samba/log.winbindd: initialize_winbindd_cache: clearing cache and re-creating with version number 2 /var/log/samba/log.winbindd:[2012/04/29 23:15:58.121524, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.winbindd:[2012/04/30 08:49:10, 0] winbindd/winbindd.c:1336(main) /var/log/samba/log.winbindd: winbindd version 3.6.4 started. /var/log/samba/log.winbindd:[2012/04/30 08:49:10.842746, 0] winbindd/winbindd_cache.c:3147(initialize_winbindd_cache) /var/log/samba/log.winbindd: initialize_winbindd_cache: clearing cache and re-creating with version number 2 /var/log/samba/log.wb-I72600S:[2012/04/27 21:58:12.012104, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/27 23:07:24.660043, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/27 23:25:13.050986, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/28 14:18:06.280048, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/28 15:38:35.138139, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/28 16:21:02.391059, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/29 11:58:07.387594, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/29 16:01:00.913603, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) /var/log/samba/log.wb-I72600S:[2012/04/29 23:15:58.121520, 0] winbindd/winbindd.c:211(winbindd_sig_term_handler) 2012-04-30 09:06:54 root@i72600s ~ # grep 'Apr 29 23' /var/log/messages Apr 29 23:15:54 i72600s shutdown[3437]: shutting down for system halt Apr 29 23:16:28 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:34 i72600s rsyslogd-2177: imuxsock lost 282210 messages from pid 2313 due to rate-limiting Apr 29 23:16:34 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:40 i72600s rsyslogd-2177: imuxsock lost 286410 messages from pid 2313 due to rate-limiting Apr 29 23:16:40 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:46 i72600s rsyslogd-2177: imuxsock lost 289712 messages from pid 2313 due to rate-limiting Apr 29 23:16:46 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:52 i72600s rsyslogd-2177: imuxsock lost 290233 messages from pid 2313 due to rate-limiting Apr 29 23:16:52 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:16:58 i72600s rsyslogd-2177: imuxsock lost 290022 messages from pid 2313 due to rate-limiting Apr 29 23:16:58 i72600s rsyslogd-2177: imuxsock begins to drop messages from pid 2313 due to rate-limiting Apr 29 23:17:00 i72600s kernel: Kernel logging (proc) stopped. Apr 29 23:17:00 i72600s rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1476" x-info="http://www.rsyslog.com"] exiting on signal 15. _______________________________________________ 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 Apr 30 18:25:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 18:25:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOvHf-0003xS-HO; Mon, 30 Apr 2012 18:25:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOvHe-0003xN-VT for xen-api@lists.xen.org; Mon, 30 Apr 2012 18:25:15 +0000 Received: from [85.158.143.99:28146] by server-3.bemta-4.messagelabs.com id 60/6B-05853-A09DE9F4; Mon, 30 Apr 2012 18:25:14 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1335810312!20658753!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16619 invoked from network); 30 Apr 2012 18:25:12 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-12.tower-216.messagelabs.com with SMTP; 30 Apr 2012 18:25:12 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Mon, 30 Apr 2012 11:25:04 -0700 Message-ID: <4F9ED900.104@holgerdanske.com> Date: Mon, 30 Apr 2012 11:25:04 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <4F9DE3BD.1040806@holgerdanske.com> In-Reply-To: Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 04/29/2012 10:54 PM, Tomoiaga Cristian wrote: > Not sure if I understand correctly what you try to accomplish but can this be done by simply creating a NFS sr ? VDIs from ISOs on the NFS share will be created automatically for you and you should be able to use the ISOs after that. Most likely the command you try to run does just that and may not be implemented in your distro yet (although this should just be a bash or python script created as a shortcut). Thanks for the reply. :-) Jonathan helped me find the "xe-mount-iso-sr" command: http://lists.xen.org/archives/html/xen-api/2012-04/msg00066.html David _______________________________________________ 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 Apr 30 18:25:21 2012 Return-path: Envelope-to: archives@lists.xen.org Delivery-date: Mon, 30 Apr 2012 18:25:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOvHf-0003xS-HO; Mon, 30 Apr 2012 18:25:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1SOvHe-0003xN-VT for xen-api@lists.xen.org; Mon, 30 Apr 2012 18:25:15 +0000 Received: from [85.158.143.99:28146] by server-3.bemta-4.messagelabs.com id 60/6B-05853-A09DE9F4; Mon, 30 Apr 2012 18:25:14 +0000 X-Env-Sender: dpchrist@holgerdanske.com X-Msg-Ref: server-12.tower-216.messagelabs.com!1335810312!20658753!1 X-Originating-IP: [184.105.128.27] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Version: 6.5.7; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16619 invoked from network); 30 Apr 2012 18:25:12 -0000 Received: from holgerdanske.com (HELO holgerdanske.com) (184.105.128.27) by server-12.tower-216.messagelabs.com with SMTP; 30 Apr 2012 18:25:12 -0000 Received: from ::ffff:69.12.202.165 ([69.12.202.165]) by holgerdanske.com for ; Mon, 30 Apr 2012 11:25:04 -0700 Message-ID: <4F9ED900.104@holgerdanske.com> Date: Mon, 30 Apr 2012 11:25:04 -0700 From: David Christensen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20120320 Icedove/3.0.11 MIME-Version: 1.0 To: "xen-api@lists.xen.org" References: <4F9DE3BD.1040806@holgerdanske.com> In-Reply-To: Subject: Re: [Xen-API] Wheezy xcp-xapi /usr/share/doc/xcp-xapi/README.Debian -bash: xe-mount-iso-sr: command not found X-BeenThere: xen-api@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development list for XCP and Xen API List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-api-bounces@lists.xen.org Errors-To: xen-api-bounces@lists.xen.org On 04/29/2012 10:54 PM, Tomoiaga Cristian wrote: > Not sure if I understand correctly what you try to accomplish but can this be done by simply creating a NFS sr ? VDIs from ISOs on the NFS share will be created automatically for you and you should be able to use the ISOs after that. Most likely the command you try to run does just that and may not be implemented in your distro yet (although this should just be a bash or python script created as a shortcut). Thanks for the reply. :-) Jonathan helped me find the "xe-mount-iso-sr" command: http://lists.xen.org/archives/html/xen-api/2012-04/msg00066.html David _______________________________________________ Xen-api mailing list Xen-api@lists.xen.org http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api