From xci-devel-bounces@lists.xen.org Thu Mar 29 12:20:56 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 29 Mar 2012 12:20:56 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDELW-0000it-7A; Thu, 29 Mar 2012 12:20:54 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <10917318lyf@gmail.com>) id 1S8k48-0001b9-IA
	for xci-devel@lists.xen.org; Sat, 17 Mar 2012 03:12:24 +0000
Received: from [193.109.254.147:50533] by server-3.bemta-14.messagelabs.com id
	D6/9A-23274-711046F4; Sat, 17 Mar 2012 03:12:23 +0000
X-Env-Sender: 10917318lyf@gmail.com
X-Msg-Ref: server-11.tower-27.messagelabs.com!1331953942!917302!1
X-Originating-IP: [209.85.220.173]
X-SpamReason: No, hits=1.1 required=7.0 tests=FROM_STARTS_WITH_NUMS,
	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 6947 invoked from network); 17 Mar 2012 03:12:23 -0000
Received: from mail-vx0-f173.google.com (HELO mail-vx0-f173.google.com)
	(209.85.220.173)
	by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Mar 2012 03:12:23 -0000
Received: by vcbfl11 with SMTP id fl11so6958088vcb.32
	for <xci-devel@lists.xen.org>; Fri, 16 Mar 2012 20:12:21 -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=uRQ8wXBQevUDJ7cdtmwDH10fCZgWTnHNOUx1tBtm6Jc=;
	b=TymiJ1L72SYd+9NT1w/0mbxsm8wCE+ET3lmRoMaZSKQSyZ0OHXXq72p9cTGUquqkY6
	F/dWbtBJ7Ea8dDEJ8ePCiR+CdBv5LUdBwe7PRlZntoBfMGZGD9RO1osKxfrf67yWgfV2
	8nCysi+76Ad4LAECuVtzjG7hw+iiLenISslw8nGBwZH7x6lBX9w7tOYhVxIgffsX9Zre
	ePzqvOHy+vfS3tcxDC+cFn8sfpbIEMfsV+WWAdZ3oacim2gmH3jn98GPrQuoLx2XAl0D
	AfLe9RBw9eWBDMHinp4clEvkvNDEaIH7RpXzD38FkpK4n1O1YVhuRNv/MoaOzMSGwmNL
	/cBw==
MIME-Version: 1.0
Received: by 10.52.240.232 with SMTP id wd8mr2374143vdc.96.1331953941859; Fri,
	16 Mar 2012 20:12:21 -0700 (PDT)
Received: by 10.220.153.132 with HTTP; Fri, 16 Mar 2012 20:12:21 -0700 (PDT)
Date: Sat, 17 Mar 2012 11:12:21 +0800
Message-ID: <CAC-jVM_g5e3LXiH5pe2fhBW2MMdT86nzBFNis09_3yQ+DPvH8g@mail.gmail.com>
From: =?GB2312?B?wsDSu7fy?= <10917318lyf@gmail.com>
To: xci-devel@lists.xen.org
X-Mailman-Approved-At: Thu, 29 Mar 2012 12:20:52 +0000
Subject: [Xci-devel] The problem about the stubdom
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8947862397992005209=="
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org

--===============8947862397992005209==
Content-Type: multipart/alternative; boundary=20cf307cfd048fcf4404bb67b181

--20cf307cfd048fcf4404bb67b181
Content-Type: text/plain; charset=ISO-8859-1

hi, I installed the xen 4.1 in my ubuntu 11.10 , and follow the guide
http://www.beyondlinux.com/2011/11/02/install-xen-4-1-and-setup-your-cloud-os-on-ubuntu-11-10/.
After installing the xen,  how should I install and run the stubdom?

--20cf307cfd048fcf4404bb67b181
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi, I installed the xen 4.1 in my ubuntu 11.10 , and follow the guide <a hr=
ef=3D"http://www.beyondlinux.com/2011/11/02/install-xen-4-1-and-setup-your-=
cloud-os-on-ubuntu-11-10/">http://www.beyondlinux.com/2011/11/02/install-xe=
n-4-1-and-setup-your-cloud-os-on-ubuntu-11-10/</a>. After installing the xe=
n,=A0 how should I install and run the stubdom? <br>

--20cf307cfd048fcf4404bb67b181--


--===============8947862397992005209==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============8947862397992005209==--


From xci-devel-bounces@lists.xen.org Thu Mar 29 12:20:56 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 29 Mar 2012 12:20:56 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDELW-0000it-7A; Thu, 29 Mar 2012 12:20:54 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <10917318lyf@gmail.com>) id 1S8k48-0001b9-IA
	for xci-devel@lists.xen.org; Sat, 17 Mar 2012 03:12:24 +0000
Received: from [193.109.254.147:50533] by server-3.bemta-14.messagelabs.com id
	D6/9A-23274-711046F4; Sat, 17 Mar 2012 03:12:23 +0000
X-Env-Sender: 10917318lyf@gmail.com
X-Msg-Ref: server-11.tower-27.messagelabs.com!1331953942!917302!1
X-Originating-IP: [209.85.220.173]
X-SpamReason: No, hits=1.1 required=7.0 tests=FROM_STARTS_WITH_NUMS,
	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 6947 invoked from network); 17 Mar 2012 03:12:23 -0000
Received: from mail-vx0-f173.google.com (HELO mail-vx0-f173.google.com)
	(209.85.220.173)
	by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Mar 2012 03:12:23 -0000
Received: by vcbfl11 with SMTP id fl11so6958088vcb.32
	for <xci-devel@lists.xen.org>; Fri, 16 Mar 2012 20:12:21 -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=uRQ8wXBQevUDJ7cdtmwDH10fCZgWTnHNOUx1tBtm6Jc=;
	b=TymiJ1L72SYd+9NT1w/0mbxsm8wCE+ET3lmRoMaZSKQSyZ0OHXXq72p9cTGUquqkY6
	F/dWbtBJ7Ea8dDEJ8ePCiR+CdBv5LUdBwe7PRlZntoBfMGZGD9RO1osKxfrf67yWgfV2
	8nCysi+76Ad4LAECuVtzjG7hw+iiLenISslw8nGBwZH7x6lBX9w7tOYhVxIgffsX9Zre
	ePzqvOHy+vfS3tcxDC+cFn8sfpbIEMfsV+WWAdZ3oacim2gmH3jn98GPrQuoLx2XAl0D
	AfLe9RBw9eWBDMHinp4clEvkvNDEaIH7RpXzD38FkpK4n1O1YVhuRNv/MoaOzMSGwmNL
	/cBw==
MIME-Version: 1.0
Received: by 10.52.240.232 with SMTP id wd8mr2374143vdc.96.1331953941859; Fri,
	16 Mar 2012 20:12:21 -0700 (PDT)
Received: by 10.220.153.132 with HTTP; Fri, 16 Mar 2012 20:12:21 -0700 (PDT)
Date: Sat, 17 Mar 2012 11:12:21 +0800
Message-ID: <CAC-jVM_g5e3LXiH5pe2fhBW2MMdT86nzBFNis09_3yQ+DPvH8g@mail.gmail.com>
From: =?GB2312?B?wsDSu7fy?= <10917318lyf@gmail.com>
To: xci-devel@lists.xen.org
X-Mailman-Approved-At: Thu, 29 Mar 2012 12:20:52 +0000
Subject: [Xci-devel] The problem about the stubdom
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8947862397992005209=="
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org

--===============8947862397992005209==
Content-Type: multipart/alternative; boundary=20cf307cfd048fcf4404bb67b181

--20cf307cfd048fcf4404bb67b181
Content-Type: text/plain; charset=ISO-8859-1

hi, I installed the xen 4.1 in my ubuntu 11.10 , and follow the guide
http://www.beyondlinux.com/2011/11/02/install-xen-4-1-and-setup-your-cloud-os-on-ubuntu-11-10/.
After installing the xen,  how should I install and run the stubdom?

--20cf307cfd048fcf4404bb67b181
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

hi, I installed the xen 4.1 in my ubuntu 11.10 , and follow the guide <a hr=
ef=3D"http://www.beyondlinux.com/2011/11/02/install-xen-4-1-and-setup-your-=
cloud-os-on-ubuntu-11-10/">http://www.beyondlinux.com/2011/11/02/install-xe=
n-4-1-and-setup-your-cloud-os-on-ubuntu-11-10/</a>. After installing the xe=
n,=A0 how should I install and run the stubdom? <br>

--20cf307cfd048fcf4404bb67b181--


--===============8947862397992005209==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============8947862397992005209==--


From xci-devel-bounces@lists.xen.org Thu Mar 29 12:45:14 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 29 Mar 2012 12:45:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDEj2-0000zG-Ql; Thu, 29 Mar 2012 12:45:12 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>) id 1SDEif-0000xH-4K
	for xci-devel@lists.xen.org; Thu, 29 Mar 2012 12:44:49 +0000
Received: from [85.158.138.51:41364] by server-2.bemta-3.messagelabs.com id
	87/51-15460-049547F4; Thu, 29 Mar 2012 12:44:48 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-8.tower-174.messagelabs.com!1333025087!19790069!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 24027 invoked from network); 29 Mar 2012 12:44:47 -0000
Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com)
	(209.85.214.45)
	by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Mar 2012 12:44:47 -0000
Received: by bkcjg9 with SMTP id jg9so2247075bkc.32
	for <multiple recipients>; Thu, 29 Mar 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:content-transfer-encoding;
	bh=57fp7pBcgtCP2pWC3XjXLeYTiQuWIrDEVb1VT83niyU=;
	b=Sc16S4/PG53la3JDBh0nXYALAHIV2xLViXB1tOKQmWkLaY8PSWV5YaRThJQkimx3Kq
	VJnXLaL4W6euXGcjKLVv8n7nBJtBUBFdKG9S2S3E/s0EXeieAI0zq6SHHPax6C2Pklzx
	pzSDDHtROmtGAaXvC1/AccomGz2p6PCTclfd3jFmeYTZr7o9vJPwBLncji070Fnsrjq+
	Nbcg31TwiqBL3/1Vn+4TAwJCXWBqV8M8aLppsGbUgy8mHOHFxqR/VDyGPXpOWgY0LyQv
	+pM50o/HXy1i4HMZcnalq2CXznRD/KJllcC0HLmRRMRr6dwsWzEHhYTTRPGPVnj5W257
	EY1w==
Received: by 10.204.128.65 with SMTP id j1mr13540823bks.74.1333025087264;
	Thu, 29 Mar 2012 05:44:47 -0700 (PDT)
Received: from [172.16.25.10] ([176.251.82.166])
	by mx.google.com with ESMTPS id f5sm13464952bke.9.2012.03.29.05.44.45
	(version=SSLv3 cipher=OTHER); Thu, 29 Mar 2012 05:44:46 -0700 (PDT)
Message-ID: <4F74593B.9000003@xen.org>
Date: Thu, 29 Mar 2012 13:44:43 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: xen-devel@lists.xen.org, xci-devel@lists.xen.org
X-Mailman-Approved-At: Thu, 29 Mar 2012 12:45:11 +0000
Subject: [Xci-devel] Archiving XCI : Request for an Archivation Review for
	the XCI project
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org


Hi everybody,

the XCI project appears to have been dormant for a while and there is no 
project lead for XCI today.  In line with Xen governance (see 
phttp://www.xen.org/projects/governance.html), I would like to first get 
community views on the health of the project and then schedule an 
archivation review.

Let me quote from the process: "The review is essentially a pitch why 
the project should be archived. The purpose of the review is not 
necessarily to archive a project, but also to provide a last opportunity 
for interested parties in the Xen.org community to save the project and 
step up. The Xen.org community manager will support efforts to save the 
project, should community members want to step up. There is the special 
case that a project has been completed: in this case the normal 
situation would be for the project lead to make the case, why this is so."

Right now, the project shows a number of issues:
a) There is little or no activity
b) There is no project lead
c) There is no mentor for the project
d) Maybe there is a case, that the project has actually been completed

The first step of addressing these issues, would be to find a mentor and 
new project lead for the XCI project. This could be a vendor expressing 
interest in leading the project, who would ultimately provide the 
project lead. The project lead could also be an individual. My 
suggestion is to first have an open discussion about the issues and see 
if somebody is willing to step up. If so, I will work with the vendor or 
individual who steps up. Failing this, we will schedule an archivation 
review.

My suggestion is, to allow 2 weeks for discussion. In other words, I 
will collate the input that I have received by April 12th. We will then 
schedule the actual review.

We have not had archivation reviews in the past, but I believe we should 
run this as a semi-public meeting. I.e. interested parties approach me 
and will be invited to the meeting.

Best Regards
Lars

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

From xci-devel-bounces@lists.xen.org Thu Mar 29 12:45:14 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 29 Mar 2012 12:45:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDEj2-0000zG-Ql; Thu, 29 Mar 2012 12:45:12 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>) id 1SDEif-0000xH-4K
	for xci-devel@lists.xen.org; Thu, 29 Mar 2012 12:44:49 +0000
Received: from [85.158.138.51:41364] by server-2.bemta-3.messagelabs.com id
	87/51-15460-049547F4; Thu, 29 Mar 2012 12:44:48 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-8.tower-174.messagelabs.com!1333025087!19790069!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 24027 invoked from network); 29 Mar 2012 12:44:47 -0000
Received: from mail-bk0-f45.google.com (HELO mail-bk0-f45.google.com)
	(209.85.214.45)
	by server-8.tower-174.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Mar 2012 12:44:47 -0000
Received: by bkcjg9 with SMTP id jg9so2247075bkc.32
	for <multiple recipients>; Thu, 29 Mar 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:content-transfer-encoding;
	bh=57fp7pBcgtCP2pWC3XjXLeYTiQuWIrDEVb1VT83niyU=;
	b=Sc16S4/PG53la3JDBh0nXYALAHIV2xLViXB1tOKQmWkLaY8PSWV5YaRThJQkimx3Kq
	VJnXLaL4W6euXGcjKLVv8n7nBJtBUBFdKG9S2S3E/s0EXeieAI0zq6SHHPax6C2Pklzx
	pzSDDHtROmtGAaXvC1/AccomGz2p6PCTclfd3jFmeYTZr7o9vJPwBLncji070Fnsrjq+
	Nbcg31TwiqBL3/1Vn+4TAwJCXWBqV8M8aLppsGbUgy8mHOHFxqR/VDyGPXpOWgY0LyQv
	+pM50o/HXy1i4HMZcnalq2CXznRD/KJllcC0HLmRRMRr6dwsWzEHhYTTRPGPVnj5W257
	EY1w==
Received: by 10.204.128.65 with SMTP id j1mr13540823bks.74.1333025087264;
	Thu, 29 Mar 2012 05:44:47 -0700 (PDT)
Received: from [172.16.25.10] ([176.251.82.166])
	by mx.google.com with ESMTPS id f5sm13464952bke.9.2012.03.29.05.44.45
	(version=SSLv3 cipher=OTHER); Thu, 29 Mar 2012 05:44:46 -0700 (PDT)
Message-ID: <4F74593B.9000003@xen.org>
Date: Thu, 29 Mar 2012 13:44:43 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: xen-devel@lists.xen.org, xci-devel@lists.xen.org
X-Mailman-Approved-At: Thu, 29 Mar 2012 12:45:11 +0000
Subject: [Xci-devel] Archiving XCI : Request for an Archivation Review for
	the XCI project
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org


Hi everybody,

the XCI project appears to have been dormant for a while and there is no 
project lead for XCI today.  In line with Xen governance (see 
phttp://www.xen.org/projects/governance.html), I would like to first get 
community views on the health of the project and then schedule an 
archivation review.

Let me quote from the process: "The review is essentially a pitch why 
the project should be archived. The purpose of the review is not 
necessarily to archive a project, but also to provide a last opportunity 
for interested parties in the Xen.org community to save the project and 
step up. The Xen.org community manager will support efforts to save the 
project, should community members want to step up. There is the special 
case that a project has been completed: in this case the normal 
situation would be for the project lead to make the case, why this is so."

Right now, the project shows a number of issues:
a) There is little or no activity
b) There is no project lead
c) There is no mentor for the project
d) Maybe there is a case, that the project has actually been completed

The first step of addressing these issues, would be to find a mentor and 
new project lead for the XCI project. This could be a vendor expressing 
interest in leading the project, who would ultimately provide the 
project lead. The project lead could also be an individual. My 
suggestion is to first have an open discussion about the issues and see 
if somebody is willing to step up. If so, I will work with the vendor or 
individual who steps up. Failing this, we will schedule an archivation 
review.

My suggestion is, to allow 2 weeks for discussion. In other words, I 
will collate the input that I have received by April 12th. We will then 
schedule the actual review.

We have not had archivation reviews in the past, but I believe we should 
run this as a semi-public meeting. I.e. interested parties approach me 
and will be invited to the meeting.

Best Regards
Lars

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

From xci-devel-bounces@lists.xen.org Fri Mar 30 01:51:08 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 30 Mar 2012 01:51:08 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDQzb-0005Lo-87; Fri, 30 Mar 2012 01:51:07 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <andreww591@gmail.com>) id 1SDQzZ-0005Lf-5s
	for xci-devel@lists.xen.org; Fri, 30 Mar 2012 01:51:05 +0000
Received: from [85.158.143.99:51843] by server-1.bemta-4.messagelabs.com id
	C6/E9-20925-881157F4; Fri, 30 Mar 2012 01:51:04 +0000
X-Env-Sender: andreww591@gmail.com
X-Msg-Ref: server-10.tower-216.messagelabs.com!1333072262!15147645!1
X-Originating-IP: [209.85.210.173]
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 11916 invoked from network); 30 Mar 2012 01:51:03 -0000
Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com)
	(209.85.210.173)
	by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Mar 2012 01:51:03 -0000
Received: by iafj26 with SMTP id j26so299332iaf.32
	for <multiple recipients>; Thu, 29 Mar 2012 18:51:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=d0X26b/EN4GHgdMNGot3MajyvozQDzAMt22tGKTiZ6U=;
	b=yUUnqBZV7MuMo5e2LdcpVOJqgWvh/xTsyB08mkPpFy/DEvee6UuFVe7YAhMbgLF4Mk
	zEGae+yRnR0j4WgVhswppPvgi0URCNgohX4f7R9rm2xStfrMTH73YYRyiYcOryY4WE52
	3eBPVwY9A8uuKsmPcjJ5WUvlVKlwfC56auUt0T2tTLB7g4IUZfLtVSELUPH8dcTxWaH8
	Bb52eHbiJ8mpablc6HqhaUiQDgpgj1soNnY8Cr1AgzrotZ/DO3vNg9j9TrpiOm/yZr/a
	6Z8+JwIQVQThPHvXJgHItIxVX9YTH60xvC+FgVGrHB4cDnLE5qbToDCGls9j/oVLOJ7W
	UOvg==
MIME-Version: 1.0
Received: by 10.43.126.68 with SMTP id gv4mr181888icc.30.1333072262177; Thu,
	29 Mar 2012 18:51:02 -0700 (PDT)
Received: by 10.231.133.201 with HTTP; Thu, 29 Mar 2012 18:51:02 -0700 (PDT)
In-Reply-To: <4F74593B.9000003@xen.org>
References: <4F74593B.9000003@xen.org>
Date: Thu, 29 Mar 2012 19:51:02 -0600
Message-ID: <CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
From: Andrew Warkentin <andreww591@gmail.com>
To: xen-devel@lists.xen.org
Cc: xci-devel@lists.xen.org
Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an
 Archivation Review for the XCI project
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org

On 3/29/12, Lars Kurth <lars.kurth@xen.org> wrote:
>
> Hi everybody,
>
> the XCI project appears to have been dormant for a while and there is no
> project lead for XCI today.  In line with Xen governance (see
> phttp://www.xen.org/projects/governance.html), I would like to first get
> community views on the health of the project and then schedule an
> archivation review.
>
> Let me quote from the process: "The review is essentially a pitch why
> the project should be archived. The purpose of the review is not
> necessarily to archive a project, but also to provide a last opportunity
> for interested parties in the Xen.org community to save the project and
> step up. The Xen.org community manager will support efforts to save the
> project, should community members want to step up. There is the special
> case that a project has been completed: in this case the normal
> situation would be for the project lead to make the case, why this is so."
>
> Right now, the project shows a number of issues:
> a) There is little or no activity
> b) There is no project lead
> c) There is no mentor for the project
> d) Maybe there is a case, that the project has actually been completed
>
> The first step of addressing these issues, would be to find a mentor and
> new project lead for the XCI project. This could be a vendor expressing
> interest in leading the project, who would ultimately provide the
> project lead. The project lead could also be an individual. My
> suggestion is to first have an open discussion about the issues and see
> if somebody is willing to step up. If so, I will work with the vendor or
> individual who steps up. Failing this, we will schedule an archivation
> review.
>
> My suggestion is, to allow 2 weeks for discussion. In other words, I
> will collate the input that I have received by April 12th. We will then
> schedule the actual review.
>
> We have not had archivation reviews in the past, but I believe we should
> run this as a semi-public meeting. I.e. interested parties approach me
> and will be invited to the meeting.
>

While I am not necessarily wanting to take over the XCI project
(however, I might consider it), I am putting together my own XCI
distribution, OpenXCI. It is not based on the xen.org XCI project
(which is rather outdated), but instead will be based on a fork of the
free parts of the XCI toolstack from XenClient 2 running on a Debian
6.0 base. OpenXCI will be different from other desktop hypervisors in
that it will be just a multi-boot alternative without any support for
remote provisioning or management other than SSH (it's intended for
people who can manage their own computers by themselves), but there is
no reason that the toolstack couldn't be used elsewhere.

Currently, I have working graphics and input servers, and am using
them with a more or less stock Debian 6.0 system. I haven't yet ported
the XCI toolstack because I am trying to find a more stable kernel
(pv-ops kernels seem to be rather unstable on my system, whereas the
XenClient 2 xenlinux kernel never crashed except when the drive
failed). The SourceForge page is at <http://sf.net/projects/openxci/>
(the graphics and input servers as well as the corresponding QEMU
patches are available there; I'll post more information soon).

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

From xci-devel-bounces@lists.xen.org Fri Mar 30 01:51:08 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 30 Mar 2012 01:51:08 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDQzb-0005Lo-87; Fri, 30 Mar 2012 01:51:07 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <andreww591@gmail.com>) id 1SDQzZ-0005Lf-5s
	for xci-devel@lists.xen.org; Fri, 30 Mar 2012 01:51:05 +0000
Received: from [85.158.143.99:51843] by server-1.bemta-4.messagelabs.com id
	C6/E9-20925-881157F4; Fri, 30 Mar 2012 01:51:04 +0000
X-Env-Sender: andreww591@gmail.com
X-Msg-Ref: server-10.tower-216.messagelabs.com!1333072262!15147645!1
X-Originating-IP: [209.85.210.173]
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 11916 invoked from network); 30 Mar 2012 01:51:03 -0000
Received: from mail-iy0-f173.google.com (HELO mail-iy0-f173.google.com)
	(209.85.210.173)
	by server-10.tower-216.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Mar 2012 01:51:03 -0000
Received: by iafj26 with SMTP id j26so299332iaf.32
	for <multiple recipients>; Thu, 29 Mar 2012 18:51:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=d0X26b/EN4GHgdMNGot3MajyvozQDzAMt22tGKTiZ6U=;
	b=yUUnqBZV7MuMo5e2LdcpVOJqgWvh/xTsyB08mkPpFy/DEvee6UuFVe7YAhMbgLF4Mk
	zEGae+yRnR0j4WgVhswppPvgi0URCNgohX4f7R9rm2xStfrMTH73YYRyiYcOryY4WE52
	3eBPVwY9A8uuKsmPcjJ5WUvlVKlwfC56auUt0T2tTLB7g4IUZfLtVSELUPH8dcTxWaH8
	Bb52eHbiJ8mpablc6HqhaUiQDgpgj1soNnY8Cr1AgzrotZ/DO3vNg9j9TrpiOm/yZr/a
	6Z8+JwIQVQThPHvXJgHItIxVX9YTH60xvC+FgVGrHB4cDnLE5qbToDCGls9j/oVLOJ7W
	UOvg==
MIME-Version: 1.0
Received: by 10.43.126.68 with SMTP id gv4mr181888icc.30.1333072262177; Thu,
	29 Mar 2012 18:51:02 -0700 (PDT)
Received: by 10.231.133.201 with HTTP; Thu, 29 Mar 2012 18:51:02 -0700 (PDT)
In-Reply-To: <4F74593B.9000003@xen.org>
References: <4F74593B.9000003@xen.org>
Date: Thu, 29 Mar 2012 19:51:02 -0600
Message-ID: <CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
From: Andrew Warkentin <andreww591@gmail.com>
To: xen-devel@lists.xen.org
Cc: xci-devel@lists.xen.org
Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an
 Archivation Review for the XCI project
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org

On 3/29/12, Lars Kurth <lars.kurth@xen.org> wrote:
>
> Hi everybody,
>
> the XCI project appears to have been dormant for a while and there is no
> project lead for XCI today.  In line with Xen governance (see
> phttp://www.xen.org/projects/governance.html), I would like to first get
> community views on the health of the project and then schedule an
> archivation review.
>
> Let me quote from the process: "The review is essentially a pitch why
> the project should be archived. The purpose of the review is not
> necessarily to archive a project, but also to provide a last opportunity
> for interested parties in the Xen.org community to save the project and
> step up. The Xen.org community manager will support efforts to save the
> project, should community members want to step up. There is the special
> case that a project has been completed: in this case the normal
> situation would be for the project lead to make the case, why this is so."
>
> Right now, the project shows a number of issues:
> a) There is little or no activity
> b) There is no project lead
> c) There is no mentor for the project
> d) Maybe there is a case, that the project has actually been completed
>
> The first step of addressing these issues, would be to find a mentor and
> new project lead for the XCI project. This could be a vendor expressing
> interest in leading the project, who would ultimately provide the
> project lead. The project lead could also be an individual. My
> suggestion is to first have an open discussion about the issues and see
> if somebody is willing to step up. If so, I will work with the vendor or
> individual who steps up. Failing this, we will schedule an archivation
> review.
>
> My suggestion is, to allow 2 weeks for discussion. In other words, I
> will collate the input that I have received by April 12th. We will then
> schedule the actual review.
>
> We have not had archivation reviews in the past, but I believe we should
> run this as a semi-public meeting. I.e. interested parties approach me
> and will be invited to the meeting.
>

While I am not necessarily wanting to take over the XCI project
(however, I might consider it), I am putting together my own XCI
distribution, OpenXCI. It is not based on the xen.org XCI project
(which is rather outdated), but instead will be based on a fork of the
free parts of the XCI toolstack from XenClient 2 running on a Debian
6.0 base. OpenXCI will be different from other desktop hypervisors in
that it will be just a multi-boot alternative without any support for
remote provisioning or management other than SSH (it's intended for
people who can manage their own computers by themselves), but there is
no reason that the toolstack couldn't be used elsewhere.

Currently, I have working graphics and input servers, and am using
them with a more or less stock Debian 6.0 system. I haven't yet ported
the XCI toolstack because I am trying to find a more stable kernel
(pv-ops kernels seem to be rather unstable on my system, whereas the
XenClient 2 xenlinux kernel never crashed except when the drive
failed). The SourceForge page is at <http://sf.net/projects/openxci/>
(the graphics and input servers as well as the corresponding QEMU
patches are available there; I'll post more information soon).

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

From xci-devel-bounces@lists.xen.org Fri Mar 30 11:21:11 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 30 Mar 2012 11:21:11 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDZtF-0005Hr-Li; Fri, 30 Mar 2012 11:21:09 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>) id 1SDZrv-0005Cp-Gq
	for xci-devel@lists.xen.org; Fri, 30 Mar 2012 11:19:47 +0000
Received: from [85.158.139.83:46907] by server-1.bemta-5.messagelabs.com id
	E8/68-28458-2D6957F4; Fri, 30 Mar 2012 11:19:46 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-13.tower-182.messagelabs.com!1333106386!21179319!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG,
  RCVD_BY_IP
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8831 invoked from network); 30 Mar 2012 11:19:46 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Mar 2012 11:19:46 -0000
Received: by eeit10 with SMTP id t10so148745eei.32
	for <multiple recipients>; Fri, 30 Mar 2012 04:19:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=2i9e5AJLpfeNeulMNLWzY3WdfnfIQMrwgam5D0V7rdE=;
	b=z2PB6rY/nwfFzC2qza8AwmFXbx6uy1ZCQceMuJPqMlCTjYzjd7Ku9oxJhoNeTmk4+L
	pNUiay6NYhQr8VAFppXebtsNmeOC9b6y43cLe0ET33kvL84LasEYsj9zzA+GXntdJ7id
	L8wWZPHtt8Y7QrZkINNGZqByMhq3DG+84Mh0BOViwETmVbDZ7HGRMRc+U0xF7gkfmYBB
	c3yEfGPAgxsWQy9qcldBYkTmVsGdUdlr1/IGEoN1HmMB/IjjOyBMDzyu/MT+K6ney11i
	1ovQdoeTg8hA6wKz/nkge5YSWx7AFlb6pNhk5agd/pnQIE0MS9BdCGabJ/Vv/nv6/WBp
	WY0Q==
Received: by 10.213.114.148 with SMTP id e20mr447148ebq.121.1333106385700;
	Fri, 30 Mar 2012 04:19:45 -0700 (PDT)
Received: from [172.16.25.10] (b0fb52a6.bb.sky.com. [176.251.82.166])
	by mx.google.com with ESMTPS id z47sm31780626een.5.2012.03.30.04.19.43
	(version=SSLv3 cipher=OTHER); Fri, 30 Mar 2012 04:19:44 -0700 (PDT)
Message-ID: <4F7596CE.6000103@xen.org>
Date: Fri, 30 Mar 2012 12:19:42 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: Andrew Warkentin <andreww591@gmail.com>
References: <4F74593B.9000003@xen.org>
	<CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
In-Reply-To: <CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
X-Mailman-Approved-At: Fri, 30 Mar 2012 11:21:09 +0000
Cc: xci-devel@lists.xen.org, xen-devel@lists.xen.org
Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an
 Archivation Review for the XCI project
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org

Andrew,

that is good news. I see a number of options going forward, which really 
depends on your preference and also what committers and maintainers in 
the community think:
1) OpenXCI as a new project hosted on Xen.org - starting as an 
incubation project as per http://www.xen.org/projects/governance.html 
and archive the old one. What you describe sounds sufficiently different.

2) OpenXCI as a separate project: Xen.org can help you promoting the 
project in various ways

If you want and have a bit more clarity on what you want to do and how 
you want to achieve things, I could arrange a call with you and walk you 
through the details.

Regards
Lars

On 30/03/2012 02:51, Andrew Warkentin wrote:
> On 3/29/12, Lars Kurth<lars.kurth@xen.org>  wrote:
>> Hi everybody,
>>
>> the XCI project appears to have been dormant for a while and there is no
>> project lead for XCI today.  In line with Xen governance (see
>> phttp://www.xen.org/projects/governance.html), I would like to first get
>> community views on the health of the project and then schedule an
>> archivation review.
>>
>> Let me quote from the process: "The review is essentially a pitch why
>> the project should be archived. The purpose of the review is not
>> necessarily to archive a project, but also to provide a last opportunity
>> for interested parties in the Xen.org community to save the project and
>> step up. The Xen.org community manager will support efforts to save the
>> project, should community members want to step up. There is the special
>> case that a project has been completed: in this case the normal
>> situation would be for the project lead to make the case, why this is so."
>>
>> Right now, the project shows a number of issues:
>> a) There is little or no activity
>> b) There is no project lead
>> c) There is no mentor for the project
>> d) Maybe there is a case, that the project has actually been completed
>>
>> The first step of addressing these issues, would be to find a mentor and
>> new project lead for the XCI project. This could be a vendor expressing
>> interest in leading the project, who would ultimately provide the
>> project lead. The project lead could also be an individual. My
>> suggestion is to first have an open discussion about the issues and see
>> if somebody is willing to step up. If so, I will work with the vendor or
>> individual who steps up. Failing this, we will schedule an archivation
>> review.
>>
>> My suggestion is, to allow 2 weeks for discussion. In other words, I
>> will collate the input that I have received by April 12th. We will then
>> schedule the actual review.
>>
>> We have not had archivation reviews in the past, but I believe we should
>> run this as a semi-public meeting. I.e. interested parties approach me
>> and will be invited to the meeting.
>>
> While I am not necessarily wanting to take over the XCI project
> (however, I might consider it), I am putting together my own XCI
> distribution, OpenXCI. It is not based on the xen.org XCI project
> (which is rather outdated), but instead will be based on a fork of the
> free parts of the XCI toolstack from XenClient 2 running on a Debian
> 6.0 base. OpenXCI will be different from other desktop hypervisors in
> that it will be just a multi-boot alternative without any support for
> remote provisioning or management other than SSH (it's intended for
> people who can manage their own computers by themselves), but there is
> no reason that the toolstack couldn't be used elsewhere.
>
> Currently, I have working graphics and input servers, and am using
> them with a more or less stock Debian 6.0 system. I haven't yet ported
> the XCI toolstack because I am trying to find a more stable kernel
> (pv-ops kernels seem to be rather unstable on my system, whereas the
> XenClient 2 xenlinux kernel never crashed except when the drive
> failed). The SourceForge page is at<http://sf.net/projects/openxci/>
> (the graphics and input servers as well as the corresponding QEMU
> patches are available there; I'll post more information soon).
>
> _______________________________________________
> Xci-devel mailing list
> Xci-devel@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel


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

From xci-devel-bounces@lists.xen.org Fri Mar 30 11:21:11 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 30 Mar 2012 11:21:11 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDZtF-0005Hr-Li; Fri, 30 Mar 2012 11:21:09 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>) id 1SDZrv-0005Cp-Gq
	for xci-devel@lists.xen.org; Fri, 30 Mar 2012 11:19:47 +0000
Received: from [85.158.139.83:46907] by server-1.bemta-5.messagelabs.com id
	E8/68-28458-2D6957F4; Fri, 30 Mar 2012 11:19:46 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-13.tower-182.messagelabs.com!1333106386!21179319!1
X-Originating-IP: [74.125.83.45]
X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG,
  RCVD_BY_IP
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8831 invoked from network); 30 Mar 2012 11:19:46 -0000
Received: from mail-ee0-f45.google.com (HELO mail-ee0-f45.google.com)
	(74.125.83.45)
	by server-13.tower-182.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Mar 2012 11:19:46 -0000
Received: by eeit10 with SMTP id t10so148745eei.32
	for <multiple recipients>; Fri, 30 Mar 2012 04:19:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=2i9e5AJLpfeNeulMNLWzY3WdfnfIQMrwgam5D0V7rdE=;
	b=z2PB6rY/nwfFzC2qza8AwmFXbx6uy1ZCQceMuJPqMlCTjYzjd7Ku9oxJhoNeTmk4+L
	pNUiay6NYhQr8VAFppXebtsNmeOC9b6y43cLe0ET33kvL84LasEYsj9zzA+GXntdJ7id
	L8wWZPHtt8Y7QrZkINNGZqByMhq3DG+84Mh0BOViwETmVbDZ7HGRMRc+U0xF7gkfmYBB
	c3yEfGPAgxsWQy9qcldBYkTmVsGdUdlr1/IGEoN1HmMB/IjjOyBMDzyu/MT+K6ney11i
	1ovQdoeTg8hA6wKz/nkge5YSWx7AFlb6pNhk5agd/pnQIE0MS9BdCGabJ/Vv/nv6/WBp
	WY0Q==
Received: by 10.213.114.148 with SMTP id e20mr447148ebq.121.1333106385700;
	Fri, 30 Mar 2012 04:19:45 -0700 (PDT)
Received: from [172.16.25.10] (b0fb52a6.bb.sky.com. [176.251.82.166])
	by mx.google.com with ESMTPS id z47sm31780626een.5.2012.03.30.04.19.43
	(version=SSLv3 cipher=OTHER); Fri, 30 Mar 2012 04:19:44 -0700 (PDT)
Message-ID: <4F7596CE.6000103@xen.org>
Date: Fri, 30 Mar 2012 12:19:42 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: Andrew Warkentin <andreww591@gmail.com>
References: <4F74593B.9000003@xen.org>
	<CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
In-Reply-To: <CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
X-Mailman-Approved-At: Fri, 30 Mar 2012 11:21:09 +0000
Cc: xci-devel@lists.xen.org, xen-devel@lists.xen.org
Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an
 Archivation Review for the XCI project
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org

Andrew,

that is good news. I see a number of options going forward, which really 
depends on your preference and also what committers and maintainers in 
the community think:
1) OpenXCI as a new project hosted on Xen.org - starting as an 
incubation project as per http://www.xen.org/projects/governance.html 
and archive the old one. What you describe sounds sufficiently different.

2) OpenXCI as a separate project: Xen.org can help you promoting the 
project in various ways

If you want and have a bit more clarity on what you want to do and how 
you want to achieve things, I could arrange a call with you and walk you 
through the details.

Regards
Lars

On 30/03/2012 02:51, Andrew Warkentin wrote:
> On 3/29/12, Lars Kurth<lars.kurth@xen.org>  wrote:
>> Hi everybody,
>>
>> the XCI project appears to have been dormant for a while and there is no
>> project lead for XCI today.  In line with Xen governance (see
>> phttp://www.xen.org/projects/governance.html), I would like to first get
>> community views on the health of the project and then schedule an
>> archivation review.
>>
>> Let me quote from the process: "The review is essentially a pitch why
>> the project should be archived. The purpose of the review is not
>> necessarily to archive a project, but also to provide a last opportunity
>> for interested parties in the Xen.org community to save the project and
>> step up. The Xen.org community manager will support efforts to save the
>> project, should community members want to step up. There is the special
>> case that a project has been completed: in this case the normal
>> situation would be for the project lead to make the case, why this is so."
>>
>> Right now, the project shows a number of issues:
>> a) There is little or no activity
>> b) There is no project lead
>> c) There is no mentor for the project
>> d) Maybe there is a case, that the project has actually been completed
>>
>> The first step of addressing these issues, would be to find a mentor and
>> new project lead for the XCI project. This could be a vendor expressing
>> interest in leading the project, who would ultimately provide the
>> project lead. The project lead could also be an individual. My
>> suggestion is to first have an open discussion about the issues and see
>> if somebody is willing to step up. If so, I will work with the vendor or
>> individual who steps up. Failing this, we will schedule an archivation
>> review.
>>
>> My suggestion is, to allow 2 weeks for discussion. In other words, I
>> will collate the input that I have received by April 12th. We will then
>> schedule the actual review.
>>
>> We have not had archivation reviews in the past, but I believe we should
>> run this as a semi-public meeting. I.e. interested parties approach me
>> and will be invited to the meeting.
>>
> While I am not necessarily wanting to take over the XCI project
> (however, I might consider it), I am putting together my own XCI
> distribution, OpenXCI. It is not based on the xen.org XCI project
> (which is rather outdated), but instead will be based on a fork of the
> free parts of the XCI toolstack from XenClient 2 running on a Debian
> 6.0 base. OpenXCI will be different from other desktop hypervisors in
> that it will be just a multi-boot alternative without any support for
> remote provisioning or management other than SSH (it's intended for
> people who can manage their own computers by themselves), but there is
> no reason that the toolstack couldn't be used elsewhere.
>
> Currently, I have working graphics and input servers, and am using
> them with a more or less stock Debian 6.0 system. I haven't yet ported
> the XCI toolstack because I am trying to find a more stable kernel
> (pv-ops kernels seem to be rather unstable on my system, whereas the
> XenClient 2 xenlinux kernel never crashed except when the drive
> failed). The SourceForge page is at<http://sf.net/projects/openxci/>
> (the graphics and input servers as well as the corresponding QEMU
> patches are available there; I'll post more information soon).
>
> _______________________________________________
> Xci-devel mailing list
> Xci-devel@lists.xen.org
> http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel


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

From xci-devel-bounces@lists.xen.org Sat Mar 31 10:56:15 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 31 Mar 2012 10:56:15 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDvyf-0004r3-IE; Sat, 31 Mar 2012 10:56:13 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <pasik@iki.fi>) id 1SDvye-0004qu-Jw
	for xci-devel@lists.xen.org; Sat, 31 Mar 2012 10:56:12 +0000
Received: from [193.109.254.147:34253] by server-4.bemta-14.messagelabs.com id
	12/AC-11570-BC2E67F4; Sat, 31 Mar 2012 10:56:11 +0000
X-Env-Sender: pasik@iki.fi
X-Msg-Ref: server-6.tower-27.messagelabs.com!1333191370!2817242!1
X-Originating-IP: [192.89.123.25]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0MDkxNTc=\n
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23877 invoked from network); 31 Mar 2012 10:56:11 -0000
Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25)
	by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 31 Mar 2012 10:56:11 -0000
X-Originating-Ip: [194.89.68.22]
Received: from ydin.reaktio.net (reaktio.net [194.89.68.22])
	by smtp.tele.fi (Postfix) with ESMTP id 31BE41A00;
	Sat, 31 Mar 2012 13:56:10 +0300 (EEST)
Received: by ydin.reaktio.net (Postfix, from userid 1001)
	id 1708F200F0; Sat, 31 Mar 2012 13:56:10 +0300 (EEST)
Date: Sat, 31 Mar 2012 13:56:10 +0300
From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>
To: Andrew Warkentin <andreww591@gmail.com>
Message-ID: <20120331105610.GW12984@reaktio.net>
References: <4F74593B.9000003@xen.org>
	<CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: xci-devel@lists.xen.org, xen-devel@lists.xen.org
Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an
	Archivation Review	for the XCI project
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org

On Thu, Mar 29, 2012 at 07:51:02PM -0600, Andrew Warkentin wrote:
> 
> While I am not necessarily wanting to take over the XCI project
> (however, I might consider it), I am putting together my own XCI
> distribution, OpenXCI. It is not based on the xen.org XCI project
> (which is rather outdated), but instead will be based on a fork of the
> free parts of the XCI toolstack from XenClient 2 running on a Debian
> 6.0 base. OpenXCI will be different from other desktop hypervisors in
> that it will be just a multi-boot alternative without any support for
> remote provisioning or management other than SSH (it's intended for
> people who can manage their own computers by themselves), but there is
> no reason that the toolstack couldn't be used elsewhere.
> 

Nice!

> Currently, I have working graphics and input servers, and am using
> them with a more or less stock Debian 6.0 system. I haven't yet ported
> the XCI toolstack because I am trying to find a more stable kernel
> (pv-ops kernels seem to be rather unstable on my system, whereas the
> XenClient 2 xenlinux kernel never crashed except when the drive
> failed). The SourceForge page is at <http://sf.net/projects/openxci/>
> (the graphics and input servers as well as the corresponding QEMU
> patches are available there; I'll post more information soon).
> 

It'd be nice if you could capture the pvops dom0 kernel errors/logs,
so the problems can be fixed. Everyone should switch to pvops kernel by now,
so all the issues and rough edges can be sorted out!

You can use serial console to capture the boot messages/errors:
http://wiki.xen.org/wiki/Xen_Serial_Console

In the case of a laptop you can use SOL (if your hardware has it),
or you can get a suitable ExpressCard (PCIe) serial adapter.

-- Pasi


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

From xci-devel-bounces@lists.xen.org Sat Mar 31 10:56:15 2012
Return-path: <xci-devel-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 31 Mar 2012 10:56:15 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xci-devel-bounces@lists.xen.org>)
	id 1SDvyf-0004r3-IE; Sat, 31 Mar 2012 10:56:13 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <pasik@iki.fi>) id 1SDvye-0004qu-Jw
	for xci-devel@lists.xen.org; Sat, 31 Mar 2012 10:56:12 +0000
Received: from [193.109.254.147:34253] by server-4.bemta-14.messagelabs.com id
	12/AC-11570-BC2E67F4; Sat, 31 Mar 2012 10:56:11 +0000
X-Env-Sender: pasik@iki.fi
X-Msg-Ref: server-6.tower-27.messagelabs.com!1333191370!2817242!1
X-Originating-IP: [192.89.123.25]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTkyLjg5LjEyMy4yNSA9PiA0MDkxNTc=\n
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23877 invoked from network); 31 Mar 2012 10:56:11 -0000
Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25)
	by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 31 Mar 2012 10:56:11 -0000
X-Originating-Ip: [194.89.68.22]
Received: from ydin.reaktio.net (reaktio.net [194.89.68.22])
	by smtp.tele.fi (Postfix) with ESMTP id 31BE41A00;
	Sat, 31 Mar 2012 13:56:10 +0300 (EEST)
Received: by ydin.reaktio.net (Postfix, from userid 1001)
	id 1708F200F0; Sat, 31 Mar 2012 13:56:10 +0300 (EEST)
Date: Sat, 31 Mar 2012 13:56:10 +0300
From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>
To: Andrew Warkentin <andreww591@gmail.com>
Message-ID: <20120331105610.GW12984@reaktio.net>
References: <4F74593B.9000003@xen.org>
	<CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CAD-qYGr6xqRoH+evek2iRz0G5gThWbrztZf=EuLU01DAkBdMfQ@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: xci-devel@lists.xen.org, xen-devel@lists.xen.org
Subject: Re: [Xci-devel] [Xen-devel] Archiving XCI : Request for an
	Archivation Review	for the XCI project
X-BeenThere: xci-devel@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: <xci-devel.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=unsubscribe>
List-Archive: <http://lists.xen.org/archives/html/xci-devel>
List-Post: <mailto:xci-devel@lists.xen.org>
List-Help: <mailto:xci-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xci-devel>,
	<mailto:xci-devel-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xci-devel-bounces@lists.xen.org
Errors-To: xci-devel-bounces@lists.xen.org

On Thu, Mar 29, 2012 at 07:51:02PM -0600, Andrew Warkentin wrote:
> 
> While I am not necessarily wanting to take over the XCI project
> (however, I might consider it), I am putting together my own XCI
> distribution, OpenXCI. It is not based on the xen.org XCI project
> (which is rather outdated), but instead will be based on a fork of the
> free parts of the XCI toolstack from XenClient 2 running on a Debian
> 6.0 base. OpenXCI will be different from other desktop hypervisors in
> that it will be just a multi-boot alternative without any support for
> remote provisioning or management other than SSH (it's intended for
> people who can manage their own computers by themselves), but there is
> no reason that the toolstack couldn't be used elsewhere.
> 

Nice!

> Currently, I have working graphics and input servers, and am using
> them with a more or less stock Debian 6.0 system. I haven't yet ported
> the XCI toolstack because I am trying to find a more stable kernel
> (pv-ops kernels seem to be rather unstable on my system, whereas the
> XenClient 2 xenlinux kernel never crashed except when the drive
> failed). The SourceForge page is at <http://sf.net/projects/openxci/>
> (the graphics and input servers as well as the corresponding QEMU
> patches are available there; I'll post more information soon).
> 

It'd be nice if you could capture the pvops dom0 kernel errors/logs,
so the problems can be fixed. Everyone should switch to pvops kernel by now,
so all the issues and rough edges can be sorted out!

You can use serial console to capture the boot messages/errors:
http://wiki.xen.org/wiki/Xen_Serial_Console

In the case of a laptop you can use SOL (if your hardware has it),
or you can get a suitable ExpressCard (PCIe) serial adapter.

-- Pasi


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

