From minios-devel-bounces@lists.xenproject.org Fri Feb 05 09:54:36 2016 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Feb 2016 09:54: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 1aRd63-0003Mu-OG; Fri, 05 Feb 2016 09:54:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aRd62-0003Mn-Ag for minios-devel@lists.xenproject.org; Fri, 05 Feb 2016 09:54:34 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id FB/8A-29478-95174B65; Fri, 05 Feb 2016 09:54:33 +0000 X-Env-Sender: claudio.pisa@uniroma2.it X-Msg-Ref: server-13.tower-206.messagelabs.com!1454666072!20251265!1 X-Originating-IP: [160.80.6.23] X-SpamReason: No, hits=0.0 required=7.0 tests=surbl: U291cmNlOiAgSEVMTyA=[dW5pcm9tYTIuaXQ=] X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7570 invoked from network); 5 Feb 2016 09:54:33 -0000 Received: from smtp.uniroma2.it (HELO smtp.uniroma2.it) (160.80.6.23) by server-13.tower-206.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 5 Feb 2016 09:54:33 -0000 Received: from smtpauth.uniroma2.it (smtpauth.uniroma2.it [160.80.6.47]) by smtp-2015.uniroma2.it (8.14.4/8.14.4/Debian-8) with ESMTP id u159sQ98013982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 5 Feb 2016 10:54:31 +0100 Received: from [192.168.100.157] ([160.80.103.191]) (authenticated bits=0) by smtpauth.uniroma2.it (8.14.3/8.14.3/Debian-9.4) with ESMTP id u159sLtD016519 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 5 Feb 2016 10:54:21 +0100 To: minios-devel@lists.xenproject.org From: Claudio Pisa X-Enigmail-Draft-Status: N1110 Organization: CNIT Message-ID: <56B4714D.6000603@uniroma2.it> Date: Fri, 5 Feb 2016 10:54:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 X-Virus-Scanned: clamav-milter 0.98.6 at smtp-2015 X-Virus-Status: Clean Subject: [Minios-devel] Booting MiniOS using the xe/xapi toolstack X-BeenThere: minios-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Mini-os development list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: minios-devel-bounces@lists.xenproject.org Errors-To: minios-devel-bounces@lists.xenproject.org Hello. I am trying to boot MiniOS through the xe/xapi toolstack, but I am not succeeding. I hope this is the right place to ask for advice. I have tried to: - create an image that includes the MiniOS kernel (with dd, mkfs, mount, etc.) and import it with vdi-import - set the PV-kernel parameter to the path of the MiniOS kernel - set the PV-bootloader parameter both to none or to pygrub - change the name of the kernel inside the image to "xenkernel" The best that I could achieve until now is starting the vm but then it immediately halts with no errors and no useful hints in the logs. What am I missing? thanks in advance and best regards, -- Claudio Pisa, Ph.D. Researcher at CNIT - University of Rome "Tor Vergata" Research Unit Via del Politecnico, 1 - 00133 - Rome, Italy Phone: +39 067259 7773 E-mail: claudio.pisa@uniroma2.it _______________________________________________ Minios-devel mailing list Minios-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel From minios-devel-bounces@lists.xenproject.org Fri Feb 05 09:54:36 2016 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Feb 2016 09:54: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 1aRd63-0003Mu-OG; Fri, 05 Feb 2016 09:54:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aRd62-0003Mn-Ag for minios-devel@lists.xenproject.org; Fri, 05 Feb 2016 09:54:34 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id FB/8A-29478-95174B65; Fri, 05 Feb 2016 09:54:33 +0000 X-Env-Sender: claudio.pisa@uniroma2.it X-Msg-Ref: server-13.tower-206.messagelabs.com!1454666072!20251265!1 X-Originating-IP: [160.80.6.23] X-SpamReason: No, hits=0.0 required=7.0 tests=surbl: U291cmNlOiAgSEVMTyA=[dW5pcm9tYTIuaXQ=] X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7570 invoked from network); 5 Feb 2016 09:54:33 -0000 Received: from smtp.uniroma2.it (HELO smtp.uniroma2.it) (160.80.6.23) by server-13.tower-206.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 5 Feb 2016 09:54:33 -0000 Received: from smtpauth.uniroma2.it (smtpauth.uniroma2.it [160.80.6.47]) by smtp-2015.uniroma2.it (8.14.4/8.14.4/Debian-8) with ESMTP id u159sQ98013982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 5 Feb 2016 10:54:31 +0100 Received: from [192.168.100.157] ([160.80.103.191]) (authenticated bits=0) by smtpauth.uniroma2.it (8.14.3/8.14.3/Debian-9.4) with ESMTP id u159sLtD016519 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 5 Feb 2016 10:54:21 +0100 To: minios-devel@lists.xenproject.org From: Claudio Pisa X-Enigmail-Draft-Status: N1110 Organization: CNIT Message-ID: <56B4714D.6000603@uniroma2.it> Date: Fri, 5 Feb 2016 10:54:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 X-Virus-Scanned: clamav-milter 0.98.6 at smtp-2015 X-Virus-Status: Clean Subject: [Minios-devel] Booting MiniOS using the xe/xapi toolstack X-BeenThere: minios-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Mini-os development list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: minios-devel-bounces@lists.xenproject.org Errors-To: minios-devel-bounces@lists.xenproject.org Hello. I am trying to boot MiniOS through the xe/xapi toolstack, but I am not succeeding. I hope this is the right place to ask for advice. I have tried to: - create an image that includes the MiniOS kernel (with dd, mkfs, mount, etc.) and import it with vdi-import - set the PV-kernel parameter to the path of the MiniOS kernel - set the PV-bootloader parameter both to none or to pygrub - change the name of the kernel inside the image to "xenkernel" The best that I could achieve until now is starting the vm but then it immediately halts with no errors and no useful hints in the logs. What am I missing? thanks in advance and best regards, -- Claudio Pisa, Ph.D. Researcher at CNIT - University of Rome "Tor Vergata" Research Unit Via del Politecnico, 1 - 00133 - Rome, Italy Phone: +39 067259 7773 E-mail: claudio.pisa@uniroma2.it _______________________________________________ Minios-devel mailing list Minios-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel From minios-devel-bounces@lists.xenproject.org Fri Feb 05 10:39:55 2016 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Feb 2016 10:39: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 1aRdnv-0007Qb-9K; Fri, 05 Feb 2016 10:39:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aRdnu-0007QV-AH for minios-devel@lists.xenproject.org; Fri, 05 Feb 2016 10:39:54 +0000 Received: from [85.158.139.211] by server-2.bemta-5.messagelabs.com id A4/10-21594-9FB74B65; Fri, 05 Feb 2016 10:39:53 +0000 X-Env-Sender: prvs=836feaa16=wei.liu2@citrix.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1454668791!20551094!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 51503 invoked from network); 5 Feb 2016 10:39:52 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2016 10:39:52 -0000 X-IronPort-AV: E=Sophos;i="5.22,399,1449532800"; d="scan'208";a="329886592" Date: Fri, 5 Feb 2016 10:39:50 +0000 From: Wei Liu To: Claudio Pisa Message-ID: <20160205103950.GU23178@citrix.com> References: <56B4714D.6000603@uniroma2.it> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <56B4714D.6000603@uniroma2.it> User-Agent: Mutt/1.5.23 (2014-03-12) X-DLP: MIA1 Cc: minios-devel@lists.xenproject.org, wei.liu2@citrix.com Subject: Re: [Minios-devel] Booting MiniOS using the xe/xapi toolstack X-BeenThere: minios-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Mini-os development list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: minios-devel-bounces@lists.xenproject.org Errors-To: minios-devel-bounces@lists.xenproject.org On Fri, Feb 05, 2016 at 10:54:21AM +0100, Claudio Pisa wrote: > Hello. > I am trying to boot MiniOS through the xe/xapi toolstack, but I am not > succeeding. I hope this is the right place to ask for advice. > This list is for development of mini-os itself. If you don't encounter problem building or developing mini-os, I don't think this is the right channel. As far as I can tell, this things you list are more like issues with the toolstack you're using. You should go to xe / xapi channel (list, forum) instead. Wei. > I have tried to: > - create an image that includes the MiniOS kernel (with dd, mkfs, > mount, etc.) and import it with vdi-import > - set the PV-kernel parameter to the path of the MiniOS kernel > - set the PV-bootloader parameter both to none or to pygrub > - change the name of the kernel inside the image to "xenkernel" > > The best that I could achieve until now is starting the vm but then it > immediately halts with no errors and no useful hints in the logs. > > What am I missing? > thanks in advance and best regards, > -- > Claudio Pisa, Ph.D. > Researcher at CNIT - University of Rome "Tor Vergata" Research Unit > Via del Politecnico, 1 - 00133 - Rome, Italy > Phone: +39 067259 7773 E-mail: claudio.pisa@uniroma2.it > > > _______________________________________________ > Minios-devel mailing list > Minios-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel _______________________________________________ Minios-devel mailing list Minios-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel From minios-devel-bounces@lists.xenproject.org Fri Feb 05 10:39:55 2016 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Feb 2016 10:39: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 1aRdnv-0007Qb-9K; Fri, 05 Feb 2016 10:39:55 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aRdnu-0007QV-AH for minios-devel@lists.xenproject.org; Fri, 05 Feb 2016 10:39:54 +0000 Received: from [85.158.139.211] by server-2.bemta-5.messagelabs.com id A4/10-21594-9FB74B65; Fri, 05 Feb 2016 10:39:53 +0000 X-Env-Sender: prvs=836feaa16=wei.liu2@citrix.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1454668791!20551094!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 51503 invoked from network); 5 Feb 2016 10:39:52 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2016 10:39:52 -0000 X-IronPort-AV: E=Sophos;i="5.22,399,1449532800"; d="scan'208";a="329886592" Date: Fri, 5 Feb 2016 10:39:50 +0000 From: Wei Liu To: Claudio Pisa Message-ID: <20160205103950.GU23178@citrix.com> References: <56B4714D.6000603@uniroma2.it> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <56B4714D.6000603@uniroma2.it> User-Agent: Mutt/1.5.23 (2014-03-12) X-DLP: MIA1 Cc: minios-devel@lists.xenproject.org, wei.liu2@citrix.com Subject: Re: [Minios-devel] Booting MiniOS using the xe/xapi toolstack X-BeenThere: minios-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Mini-os development list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: minios-devel-bounces@lists.xenproject.org Errors-To: minios-devel-bounces@lists.xenproject.org On Fri, Feb 05, 2016 at 10:54:21AM +0100, Claudio Pisa wrote: > Hello. > I am trying to boot MiniOS through the xe/xapi toolstack, but I am not > succeeding. I hope this is the right place to ask for advice. > This list is for development of mini-os itself. If you don't encounter problem building or developing mini-os, I don't think this is the right channel. As far as I can tell, this things you list are more like issues with the toolstack you're using. You should go to xe / xapi channel (list, forum) instead. Wei. > I have tried to: > - create an image that includes the MiniOS kernel (with dd, mkfs, > mount, etc.) and import it with vdi-import > - set the PV-kernel parameter to the path of the MiniOS kernel > - set the PV-bootloader parameter both to none or to pygrub > - change the name of the kernel inside the image to "xenkernel" > > The best that I could achieve until now is starting the vm but then it > immediately halts with no errors and no useful hints in the logs. > > What am I missing? > thanks in advance and best regards, > -- > Claudio Pisa, Ph.D. > Researcher at CNIT - University of Rome "Tor Vergata" Research Unit > Via del Politecnico, 1 - 00133 - Rome, Italy > Phone: +39 067259 7773 E-mail: claudio.pisa@uniroma2.it > > > _______________________________________________ > Minios-devel mailing list > Minios-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel _______________________________________________ Minios-devel mailing list Minios-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel From minios-devel-bounces@lists.xenproject.org Wed Feb 24 18:51:13 2016 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 24 Feb 2016 18:51: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 1aYeWl-00012S-Nk; Wed, 24 Feb 2016 18:51:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aYeWj-00011z-Kz; Wed, 24 Feb 2016 18:51:09 +0000 Received: from [85.158.137.68] by server-11.bemta-3.messagelabs.com id 06/12-02978-B9BFDC65; Wed, 24 Feb 2016 18:51:07 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1456339864!24275828!1 X-Originating-IP: [74.125.82.53] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_8,spamassassin: ,surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiBBbGwgdXJscyByZXR1cm5lZCBsZ l9u\nZWdhdGl2ZSk=\n X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 47469 invoked from network); 24 Feb 2016 18:51:05 -0000 Received: from mail-wm0-f53.google.com (HELO mail-wm0-f53.google.com) (74.125.82.53) by server-13.tower-31.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 24 Feb 2016 18:51:05 -0000 Received: by mail-wm0-f53.google.com with SMTP id b205so1831754wmb.1; Wed, 24 Feb 2016 10:51:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; bh=WKzbcDdHtApKEgyblR7yQGihrsaWfSOID40I398qFhM=; b=I51I/Gog2NJs0K9aVwkqtYGkZLx94CB4wB8UBi4rTP3lsrkxKrQa4np0tKXGnxkaTq Jbxp+fNR3zIzzumGmKcP+oEriLia6ev45hualbu2O2t/kqT3Vor6EtIgb3efH9SbGVcO 7qCsgthxfW5EP6k2ToqLW6czhnwGvfC00OVL9+kxxnksfzYo8MT5M4TFpNmRut/hSIsT fAdeQYw4etl772VWl646AtfwI3bqGA7DLgrPHE2FkE3+1yoraahBCP60HhmEaRiQNOOl u9qBS0M1GUftyrTTuEBQrwEP76UmmPCOJwiuHa2QsApDcxBWQTlLXoVoY3VeZ3QS5y7E JkiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version; bh=WKzbcDdHtApKEgyblR7yQGihrsaWfSOID40I398qFhM=; b=A3wqO87T249PaLsZ39Ii7z0AvDQquH/HS8KR/DlT14B7NxX80dZiN3cfMdGT1Ah9F0 TrJgcstpn2FxQszGGBlhlH302GmlgvfPvhfnhQniJwOgYZZh7QihWV1vZ3mMeeQhjVkp 2i/8ktAqtQDJylGZmfQ9XT2LEKMBFoQNEFJCgffMM5uao0Z/ykaf6H8YEB4yWHsoOVBy XbZFduxqhDMl8Aht8a8wqvhXNkUhYy2puD6mlql6GQTR7Xx0eTaz9qVtVGYbRler1QqN SyXxU/NMYHyXot6DVn87FvBd++3RNG/zzbZdtW2bR202mIQHozzGFxw1zz1tDdJrKDZJ IXDA== X-Gm-Message-State: AG10YOQyWHoNJRK/HmXE+cIQfelr0pFOhTo0LRuPdRvMamPILSRWB0b9Q+IC5Kr4GxX+iA== X-Received: by 10.28.98.138 with SMTP id w132mr24076079wmb.45.1456339864676; Wed, 24 Feb 2016 10:51:04 -0800 (PST) Received: from dhcp-3-217.uk.xensource.com (default-46-102-197-194.interdsl.co.uk. [46.102.197.194]) by smtp.gmail.com with ESMTPSA id pu8sm4295288wjc.17.2016.02.24.10.51.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 24 Feb 2016 10:51:04 -0800 (PST) From: Lars Kurth Date: Wed, 24 Feb 2016 18:51:02 +0000 Message-Id: <884EC716-0ED5-4D36-886A-4752AAC6C913@gmail.com> To: xen-devel , xen-announce Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Cc: Keir Fraser , Ian Campbell , xen-api , Tim Deegan , minios-devel , embedded-pv-devel , mirageos-devel , win-pv-devel Subject: [Minios-devel] Call for nominations for new Hypervisor subproject maintainers and committers X-BeenThere: minios-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Mini-os development list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: minios-devel-bounces@lists.xenproject.org Errors-To: minios-devel-bounces@lists.xenproject.org Dear Community members, I wanted to inform you that both Keir Fraser and Tim Deegan, have formally stepped down in their roles as committers from the Hypervisor team. In addition, you may have seen that Ian Campbell recently transferred maintainer-ship for many components to other community members (see http://bit.ly/1RnM8JP). This means that Ian will take a much less active role within the project in the future. First and foremost, the remaining committers and the Xen Project Advisory Board would like to thank Keir, Tim and Ian for serving the Xen Project community and their manyfold and diverse contributions. Given, that as a project, we have found it difficult to promote contributors to maintainer and committer roles in the past, the remaining group of committers felt that we should use a more formal appointment process to successions and succession planning and have asked me to organise this process. Taking a longer term view, the committers also felt that we should not restrict the appointment process to replacing committer positions only, but to consider additional committer positions based on merit and to also include new maintainer nominations. Thus, to fill these positions, we are soliciting nominations. To nominate yourself or someone else within the community, please send e-mail to appointments@xenproject.org with one of the following subject lines: - "Maintainer Nomination of [name]" - "Committer Nomination of [name]" Nominees will of course be asked, privately, whether they would be willing to serve, if they have been nominated by someone else. Please provide contact details (at least the full name and e-mail address of nominee) in the body of the e-mail and describe why the nominee would be a good fit a maintainer and/or committer. The body of the nomination should list technical knowledge that is needed to be a maintainer and/or committer and highlight core areas of expertise. In addition, we are also interested in specific instances, where the nominee showed communication and open source leadership qualities. For example: * Was able to help resolve disagreements, both technical and non- technical, which you were a party to or observer of. * Was able to contribute to improve quality and architectural consistency across several components within the Hypervisor * Has been involved in coordinating the activities of several community members * Has led or driven technical initiatives or larger scale feature development within the community * Has mentored and encouraged newcomers to the community * Has represented the project or aspects of it (e.g. via talks, blog posts, ...) * Has shown other communication and open source leadership qualities Being a maintainer and/or committer does require a time commitment. Nominees should be able to follow e-mail discussions on xen-devel@ on an ongoing basis and respond within a couple of days so that discussions progress. Committers should ideally be able to spend a minimum of 4-5 days working on the project per month. For maintainers, the time requirement is likely less. We anticipate starting our selection process according to the following rough time-table. Today: Public call for nominations for new committers and maintainers (self-nominations and 3rd-party nominations both welcome) March 11: Closing date for nominations up to March 30: We email non-self-nominated nominees in private to ask them to confirm whether they are willing to act as nominees. We will also discuss with all nominees, time commitment and other possible questions (from both nominees and existing committers), related to the proposed nominations. March 30: We conduct a formal vote to ratify nominations April 6: We publish the new maintainers and committers (we may do this earlier) Note that we have identified some issues in our governance, such as whether we need to elect a new project lead or whether we introduce a committee to steer the project instead, alongside other issues. We aim to resolve these issues *after* new maintainers and committers have been elected. If you do have any questions related to the process, feel free to reply to this thread. In addition, if you want to nominate someone else or yourself but are not sure, feel free to send your question to appointments@xenproject.org preceded by "Question:" in the subject line. Best Regards Lars Kurth Xen Project Community Manager Chairman of Xen Project Advisory Board _______________________________________________ Minios-devel mailing list Minios-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel From minios-devel-bounces@lists.xenproject.org Wed Feb 24 18:51:13 2016 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 24 Feb 2016 18:51: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 1aYeWl-00012S-Nk; Wed, 24 Feb 2016 18:51:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aYeWj-00011z-Kz; Wed, 24 Feb 2016 18:51:09 +0000 Received: from [85.158.137.68] by server-11.bemta-3.messagelabs.com id 06/12-02978-B9BFDC65; Wed, 24 Feb 2016 18:51:07 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1456339864!24275828!1 X-Originating-IP: [74.125.82.53] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_8,spamassassin: ,surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRvbmVkOiBBbGwgdXJscyByZXR1cm5lZCBsZ l9u\nZWdhdGl2ZSk=\n X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 47469 invoked from network); 24 Feb 2016 18:51:05 -0000 Received: from mail-wm0-f53.google.com (HELO mail-wm0-f53.google.com) (74.125.82.53) by server-13.tower-31.messagelabs.com with AES128-GCM-SHA256 encrypted SMTP; 24 Feb 2016 18:51:05 -0000 Received: by mail-wm0-f53.google.com with SMTP id b205so1831754wmb.1; Wed, 24 Feb 2016 10:51:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; bh=WKzbcDdHtApKEgyblR7yQGihrsaWfSOID40I398qFhM=; b=I51I/Gog2NJs0K9aVwkqtYGkZLx94CB4wB8UBi4rTP3lsrkxKrQa4np0tKXGnxkaTq Jbxp+fNR3zIzzumGmKcP+oEriLia6ev45hualbu2O2t/kqT3Vor6EtIgb3efH9SbGVcO 7qCsgthxfW5EP6k2ToqLW6czhnwGvfC00OVL9+kxxnksfzYo8MT5M4TFpNmRut/hSIsT fAdeQYw4etl772VWl646AtfwI3bqGA7DLgrPHE2FkE3+1yoraahBCP60HhmEaRiQNOOl u9qBS0M1GUftyrTTuEBQrwEP76UmmPCOJwiuHa2QsApDcxBWQTlLXoVoY3VeZ3QS5y7E JkiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version; bh=WKzbcDdHtApKEgyblR7yQGihrsaWfSOID40I398qFhM=; b=A3wqO87T249PaLsZ39Ii7z0AvDQquH/HS8KR/DlT14B7NxX80dZiN3cfMdGT1Ah9F0 TrJgcstpn2FxQszGGBlhlH302GmlgvfPvhfnhQniJwOgYZZh7QihWV1vZ3mMeeQhjVkp 2i/8ktAqtQDJylGZmfQ9XT2LEKMBFoQNEFJCgffMM5uao0Z/ykaf6H8YEB4yWHsoOVBy XbZFduxqhDMl8Aht8a8wqvhXNkUhYy2puD6mlql6GQTR7Xx0eTaz9qVtVGYbRler1QqN SyXxU/NMYHyXot6DVn87FvBd++3RNG/zzbZdtW2bR202mIQHozzGFxw1zz1tDdJrKDZJ IXDA== X-Gm-Message-State: AG10YOQyWHoNJRK/HmXE+cIQfelr0pFOhTo0LRuPdRvMamPILSRWB0b9Q+IC5Kr4GxX+iA== X-Received: by 10.28.98.138 with SMTP id w132mr24076079wmb.45.1456339864676; Wed, 24 Feb 2016 10:51:04 -0800 (PST) Received: from dhcp-3-217.uk.xensource.com (default-46-102-197-194.interdsl.co.uk. [46.102.197.194]) by smtp.gmail.com with ESMTPSA id pu8sm4295288wjc.17.2016.02.24.10.51.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 24 Feb 2016 10:51:04 -0800 (PST) From: Lars Kurth Date: Wed, 24 Feb 2016 18:51:02 +0000 Message-Id: <884EC716-0ED5-4D36-886A-4752AAC6C913@gmail.com> To: xen-devel , xen-announce Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Cc: Keir Fraser , Ian Campbell , xen-api , Tim Deegan , minios-devel , embedded-pv-devel , mirageos-devel , win-pv-devel Subject: [Minios-devel] Call for nominations for new Hypervisor subproject maintainers and committers X-BeenThere: minios-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Mini-os development list List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: minios-devel-bounces@lists.xenproject.org Errors-To: minios-devel-bounces@lists.xenproject.org Dear Community members, I wanted to inform you that both Keir Fraser and Tim Deegan, have formally stepped down in their roles as committers from the Hypervisor team. In addition, you may have seen that Ian Campbell recently transferred maintainer-ship for many components to other community members (see http://bit.ly/1RnM8JP). This means that Ian will take a much less active role within the project in the future. First and foremost, the remaining committers and the Xen Project Advisory Board would like to thank Keir, Tim and Ian for serving the Xen Project community and their manyfold and diverse contributions. Given, that as a project, we have found it difficult to promote contributors to maintainer and committer roles in the past, the remaining group of committers felt that we should use a more formal appointment process to successions and succession planning and have asked me to organise this process. Taking a longer term view, the committers also felt that we should not restrict the appointment process to replacing committer positions only, but to consider additional committer positions based on merit and to also include new maintainer nominations. Thus, to fill these positions, we are soliciting nominations. To nominate yourself or someone else within the community, please send e-mail to appointments@xenproject.org with one of the following subject lines: - "Maintainer Nomination of [name]" - "Committer Nomination of [name]" Nominees will of course be asked, privately, whether they would be willing to serve, if they have been nominated by someone else. Please provide contact details (at least the full name and e-mail address of nominee) in the body of the e-mail and describe why the nominee would be a good fit a maintainer and/or committer. The body of the nomination should list technical knowledge that is needed to be a maintainer and/or committer and highlight core areas of expertise. In addition, we are also interested in specific instances, where the nominee showed communication and open source leadership qualities. For example: * Was able to help resolve disagreements, both technical and non- technical, which you were a party to or observer of. * Was able to contribute to improve quality and architectural consistency across several components within the Hypervisor * Has been involved in coordinating the activities of several community members * Has led or driven technical initiatives or larger scale feature development within the community * Has mentored and encouraged newcomers to the community * Has represented the project or aspects of it (e.g. via talks, blog posts, ...) * Has shown other communication and open source leadership qualities Being a maintainer and/or committer does require a time commitment. Nominees should be able to follow e-mail discussions on xen-devel@ on an ongoing basis and respond within a couple of days so that discussions progress. Committers should ideally be able to spend a minimum of 4-5 days working on the project per month. For maintainers, the time requirement is likely less. We anticipate starting our selection process according to the following rough time-table. Today: Public call for nominations for new committers and maintainers (self-nominations and 3rd-party nominations both welcome) March 11: Closing date for nominations up to March 30: We email non-self-nominated nominees in private to ask them to confirm whether they are willing to act as nominees. We will also discuss with all nominees, time commitment and other possible questions (from both nominees and existing committers), related to the proposed nominations. March 30: We conduct a formal vote to ratify nominations April 6: We publish the new maintainers and committers (we may do this earlier) Note that we have identified some issues in our governance, such as whether we need to elect a new project lead or whether we introduce a committee to steer the project instead, alongside other issues. We aim to resolve these issues *after* new maintainers and committers have been elected. If you do have any questions related to the process, feel free to reply to this thread. In addition, if you want to nominate someone else or yourself but are not sure, feel free to send your question to appointments@xenproject.org preceded by "Question:" in the subject line. Best Regards Lars Kurth Xen Project Community Manager Chairman of Xen Project Advisory Board _______________________________________________ Minios-devel mailing list Minios-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/minios-devel