From mirageos-devel-bounces@lists.xenproject.org Mon Feb 03 23:00:29 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 03 Feb 2014 23:00: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 1WASV6-0006Ji-NJ; Mon, 03 Feb 2014 23:00:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WASV4-0006Jd-Sx for mirageos-devel@lists.xenproject.org; Mon, 03 Feb 2014 23:00:23 +0000 Received: from [85.158.137.68:18001] by server-2.bemta-3.messagelabs.com id BF/F1-06531-68F10F25; Mon, 03 Feb 2014 23:00:22 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-31.messagelabs.com!1391468421!13124344!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14633 invoked from network); 3 Feb 2014 23:00:21 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-31.messagelabs.com with SMTP; 3 Feb 2014 23:00:21 -0000 Received: (qmail 8747 invoked by uid 634); 3 Feb 2014 23:00:20 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 03 Feb 2014 23:00:20 +0000 From: Anil Madhavapeddy Date: Mon, 3 Feb 2014 23:00:17 +0000 Message-Id: <3A5EE044-D470-401D-B8BE-2877938349D4@recoil.org> To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Sheets Subject: [MirageOS-devel] some pointers for xen/arm on cubie2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org A few useful pointers to anyone else looking into Xen/ARM for Mirage. Ian Campbell has tidied up the Allwinner Xen wiki and it's far more accurate now: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner I'm currently booting my Cubie2 using an NFS root, but a SATA drive should work fine too. MMC is still problematic by most reports. As for a MiniOS to get Mirage up on ARM, Julien suggested that a stripped down FreeBSD would be easier than a MiniOS, which I quite like given that sharing the header files with FreeBSD will make porting the kFreeBSD backend easier too in the medium term. The FreeBSD Xen/ARM working git tree is here: http://xenbits.xen.org/gitweb/?p=people/julieng/freebsd.git;a=tree;f=sys/arm/xenhvm;h=26ec9810bc775e24f08d18547a84ebba44792cf0;hb=xen-arm -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 03 23:00:29 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 03 Feb 2014 23:00: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 1WASV6-0006Ji-NJ; Mon, 03 Feb 2014 23:00:24 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WASV4-0006Jd-Sx for mirageos-devel@lists.xenproject.org; Mon, 03 Feb 2014 23:00:23 +0000 Received: from [85.158.137.68:18001] by server-2.bemta-3.messagelabs.com id BF/F1-06531-68F10F25; Mon, 03 Feb 2014 23:00:22 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-31.messagelabs.com!1391468421!13124344!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14633 invoked from network); 3 Feb 2014 23:00:21 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-31.messagelabs.com with SMTP; 3 Feb 2014 23:00:21 -0000 Received: (qmail 8747 invoked by uid 634); 3 Feb 2014 23:00:20 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 03 Feb 2014 23:00:20 +0000 From: Anil Madhavapeddy Date: Mon, 3 Feb 2014 23:00:17 +0000 Message-Id: <3A5EE044-D470-401D-B8BE-2877938349D4@recoil.org> To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Sheets Subject: [MirageOS-devel] some pointers for xen/arm on cubie2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org A few useful pointers to anyone else looking into Xen/ARM for Mirage. Ian Campbell has tidied up the Allwinner Xen wiki and it's far more accurate now: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Allwinner I'm currently booting my Cubie2 using an NFS root, but a SATA drive should work fine too. MMC is still problematic by most reports. As for a MiniOS to get Mirage up on ARM, Julien suggested that a stripped down FreeBSD would be easier than a MiniOS, which I quite like given that sharing the header files with FreeBSD will make porting the kFreeBSD backend easier too in the medium term. The FreeBSD Xen/ARM working git tree is here: http://xenbits.xen.org/gitweb/?p=people/julieng/freebsd.git;a=tree;f=sys/arm/xenhvm;h=26ec9810bc775e24f08d18547a84ebba44792cf0;hb=xen-arm -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 04 17:01:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 04 Feb 2014 17:01: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 1WAjNT-0006Ex-Ky; Tue, 04 Feb 2014 17:01:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WAjNS-0006Er-N3 for mirageos-devel@lists.xenproject.org; Tue, 04 Feb 2014 17:01:38 +0000 Received: from [85.158.137.68:36836] by server-16.bemta-3.messagelabs.com id D4/2E-29917-1FC11F25; Tue, 04 Feb 2014 17:01:37 +0000 X-Env-Sender: mike.mcclurg@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1391533295!13350300!1 X-Originating-IP: [209.85.220.169] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 908 invoked from network); 4 Feb 2014 17:01:36 -0000 Received: from mail-vc0-f169.google.com (HELO mail-vc0-f169.google.com) (209.85.220.169) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2014 17:01:36 -0000 Received: by mail-vc0-f169.google.com with SMTP id hq11so6145755vcb.0 for ; Tue, 04 Feb 2014 09:01:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xdwsBiEciRKEpMkvbJiPqg3JiTZ0R3zqgXeTOB3q+jE=; b=En1qMiPOjE87OdeYsHka2n4j2g3ZgiVe1uf5MFv5hPTkQS2Kqj14t/9UJbH1SLmCZ/ N9jSAHYATqCJpVDIKIa9B7i2KP1xoEVE+/96ZU7BS1Y9ch1PMjAJfmEUwTqVOZ5FZlLm rtH8UWA4nlpyvFOWC08iWJwlCWKwOQOpDef/wwqLqB1J/BplTta5Blo1TKiT9eEdm7pQ pAa9Nn1EC6Lh2D+t83zLJwb7d0yHMtvHUXJRZd7V2flWFQA7Q+Olydmrb+ZXhjgmKZc9 9W77cIN4ooFZjkWNlM8gfe9cxjyPn+xmRhd1C6eKSwZ+9J9Axj65O0Wimho6fJKllCpR a3QQ== MIME-Version: 1.0 X-Received: by 10.52.95.233 with SMTP id dn9mr28162136vdb.3.1391533295396; Tue, 04 Feb 2014 09:01:35 -0800 (PST) Received: by 10.58.156.35 with HTTP; Tue, 4 Feb 2014 09:01:35 -0800 (PST) In-Reply-To: <3A5EE044-D470-401D-B8BE-2877938349D4@recoil.org> References: <3A5EE044-D470-401D-B8BE-2877938349D4@recoil.org> Date: Tue, 4 Feb 2014 10:01:35 -0700 Message-ID: From: Mike McClurg To: Anil Madhavapeddy Cc: David Sheets , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] some pointers for xen/arm on cubie2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1171835603987891173==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1171835603987891173== Content-Type: multipart/alternative; boundary=001a1136b610c3eadd04f1979777 --001a1136b610c3eadd04f1979777 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Feb 3, 2014 at 4:00 PM, Anil Madhavapeddy wrote: > As for a MiniOS to get Mirage up on ARM, Julien suggested that a stripped > down FreeBSD would be easier than a MiniOS, which I quite like given that > sharing the header files with FreeBSD will make porting the kFreeBSD > backend easier too in the medium term. The FreeBSD Xen/ARM working git > tree is here: > > > http://xenbits.xen.org/gitweb/?p=people/julieng/freebsd.git;a=tree;f=sys/arm/xenhvm;h=26ec9810bc775e24f08d18547a84ebba44792cf0;hb=xen-arm > Might NetBSD's rump kernels also be a good replacement for MiniOS? From what I can tell, FreeBSD's ARM support is better than NetBSD's, so this is a moot point for the Cubie discussion. I was mostly just wondering what your thoughts were on a NetBSD rump kernel versus a stripped down FreeBSD kernel. Mike --001a1136b610c3eadd04f1979777 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On M= on, Feb 3, 2014 at 4:00 PM, Anil Madhavapeddy <anil@recoil.org> wrote:
As for a MiniOS to get Mirage up on ARM, Julien suggested that a stripped d= own FreeBSD would be easier than a MiniOS, which I quite like given that sh= aring the header files with FreeBSD will make porting the kFreeBSD backend = easier too in the medium term. =A0The FreeBSD Xen/ARM working git tree is h= ere:

http://xenbits.xen.org/gitweb/?p=3Dpeople/jul= ieng/freebsd.git;a=3Dtree;f=3Dsys/arm/xenhvm;h=3D26ec9810bc775e24f08d18547a= 84ebba44792cf0;hb=3Dxen-arm

Might NetBSD's rump kernels also be a = good replacement for MiniOS? From what I can tell, FreeBSD's ARM suppor= t is better than NetBSD's, so this is a moot point for the Cubie discus= sion. I was mostly just wondering what your thoughts were on a NetBSD rump = kernel versus a stripped down FreeBSD kernel.

Mike
--001a1136b610c3eadd04f1979777-- --===============1171835603987891173== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1171835603987891173==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 04 17:01:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 04 Feb 2014 17:01: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 1WAjNT-0006Ex-Ky; Tue, 04 Feb 2014 17:01:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WAjNS-0006Er-N3 for mirageos-devel@lists.xenproject.org; Tue, 04 Feb 2014 17:01:38 +0000 Received: from [85.158.137.68:36836] by server-16.bemta-3.messagelabs.com id D4/2E-29917-1FC11F25; Tue, 04 Feb 2014 17:01:37 +0000 X-Env-Sender: mike.mcclurg@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1391533295!13350300!1 X-Originating-IP: [209.85.220.169] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 908 invoked from network); 4 Feb 2014 17:01:36 -0000 Received: from mail-vc0-f169.google.com (HELO mail-vc0-f169.google.com) (209.85.220.169) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Feb 2014 17:01:36 -0000 Received: by mail-vc0-f169.google.com with SMTP id hq11so6145755vcb.0 for ; Tue, 04 Feb 2014 09:01:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xdwsBiEciRKEpMkvbJiPqg3JiTZ0R3zqgXeTOB3q+jE=; b=En1qMiPOjE87OdeYsHka2n4j2g3ZgiVe1uf5MFv5hPTkQS2Kqj14t/9UJbH1SLmCZ/ N9jSAHYATqCJpVDIKIa9B7i2KP1xoEVE+/96ZU7BS1Y9ch1PMjAJfmEUwTqVOZ5FZlLm rtH8UWA4nlpyvFOWC08iWJwlCWKwOQOpDef/wwqLqB1J/BplTta5Blo1TKiT9eEdm7pQ pAa9Nn1EC6Lh2D+t83zLJwb7d0yHMtvHUXJRZd7V2flWFQA7Q+Olydmrb+ZXhjgmKZc9 9W77cIN4ooFZjkWNlM8gfe9cxjyPn+xmRhd1C6eKSwZ+9J9Axj65O0Wimho6fJKllCpR a3QQ== MIME-Version: 1.0 X-Received: by 10.52.95.233 with SMTP id dn9mr28162136vdb.3.1391533295396; Tue, 04 Feb 2014 09:01:35 -0800 (PST) Received: by 10.58.156.35 with HTTP; Tue, 4 Feb 2014 09:01:35 -0800 (PST) In-Reply-To: <3A5EE044-D470-401D-B8BE-2877938349D4@recoil.org> References: <3A5EE044-D470-401D-B8BE-2877938349D4@recoil.org> Date: Tue, 4 Feb 2014 10:01:35 -0700 Message-ID: From: Mike McClurg To: Anil Madhavapeddy Cc: David Sheets , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] some pointers for xen/arm on cubie2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1171835603987891173==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1171835603987891173== Content-Type: multipart/alternative; boundary=001a1136b610c3eadd04f1979777 --001a1136b610c3eadd04f1979777 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Feb 3, 2014 at 4:00 PM, Anil Madhavapeddy wrote: > As for a MiniOS to get Mirage up on ARM, Julien suggested that a stripped > down FreeBSD would be easier than a MiniOS, which I quite like given that > sharing the header files with FreeBSD will make porting the kFreeBSD > backend easier too in the medium term. The FreeBSD Xen/ARM working git > tree is here: > > > http://xenbits.xen.org/gitweb/?p=people/julieng/freebsd.git;a=tree;f=sys/arm/xenhvm;h=26ec9810bc775e24f08d18547a84ebba44792cf0;hb=xen-arm > Might NetBSD's rump kernels also be a good replacement for MiniOS? From what I can tell, FreeBSD's ARM support is better than NetBSD's, so this is a moot point for the Cubie discussion. I was mostly just wondering what your thoughts were on a NetBSD rump kernel versus a stripped down FreeBSD kernel. Mike --001a1136b610c3eadd04f1979777 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On M= on, Feb 3, 2014 at 4:00 PM, Anil Madhavapeddy <anil@recoil.org> wrote:
As for a MiniOS to get Mirage up on ARM, Julien suggested that a stripped d= own FreeBSD would be easier than a MiniOS, which I quite like given that sh= aring the header files with FreeBSD will make porting the kFreeBSD backend = easier too in the medium term. =A0The FreeBSD Xen/ARM working git tree is h= ere:

http://xenbits.xen.org/gitweb/?p=3Dpeople/jul= ieng/freebsd.git;a=3Dtree;f=3Dsys/arm/xenhvm;h=3D26ec9810bc775e24f08d18547a= 84ebba44792cf0;hb=3Dxen-arm

Might NetBSD's rump kernels also be a = good replacement for MiniOS? From what I can tell, FreeBSD's ARM suppor= t is better than NetBSD's, so this is a moot point for the Cubie discus= sion. I was mostly just wondering what your thoughts were on a NetBSD rump = kernel versus a stripped down FreeBSD kernel.

Mike
--001a1136b610c3eadd04f1979777-- --===============1171835603987891173== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1171835603987891173==-- From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 11:11:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 11:11: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 1WB0O6-000211-82; Wed, 05 Feb 2014 11:11:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB0O4-00020o-KM for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 11:11:24 +0000 Received: from [85.158.139.211:16963] by server-1.bemta-5.messagelabs.com id 54/71-12859-B5C12F25; Wed, 05 Feb 2014 11:11:23 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1391598681!1798612!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7123 invoked from network); 5 Feb 2014 11:11:23 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 11:11:23 -0000 Received: by mail-pb0-f47.google.com with SMTP id rp16so228707pbb.34 for ; Wed, 05 Feb 2014 03:11:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=N6f8RJOToHuSocCd/bburcrLda/qeVPK5obC2hvr5cY=; b=DQBRZG8Im7Y9D9FEs8hJ5xUnPfvZFLi8ev/jToqc4Q4/2qMIKtHzP8TZ4fn1TNpoyI 61Kd0wbeerlFuGdK26o2oaXaU8Ae5POHIdtN3Db7e/5N+dmpDfIel4iDUIXRxuoB5Fl/ Bl3jjdXzsf/OVslwMqww4UJL96e5blFFRxIqO6uYZkXQ8f/amcqyMY9P3IXnZSTVRibg 9cX3s+d7gG53gDjSb6C6FFblstVmthhDIN/pQxsDnnBZlvGjPrtKAyVQUc6L/CH0WSK4 d9e2YyqOCSHhANOHYD9L1eKtG1qr1SMVXD53WxuyUL9bR9JKbOOSC5AwlGRUTc/sMAT+ Wrxw== MIME-Version: 1.0 X-Received: by 10.66.139.100 with SMTP id qx4mr901166pab.141.1391598680614; Wed, 05 Feb 2014 03:11:20 -0800 (PST) Received: by 10.70.55.132 with HTTP; Wed, 5 Feb 2014 03:11:20 -0800 (PST) Date: Wed, 5 Feb 2014 11:11:20 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today (wednesday), 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5648489017261667470==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5648489017261667470== Content-Type: multipart/alternative; boundary=001a113315de072bb104f1a6d169 --001a113315de072bb104f1a6d169 Content-Type: text/plain; charset=ISO-8859-1 Let's meet today and discuss * how was the belgian beer at FOSDEM? * what's the state of mirage-1.1.0? 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817 United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Meeting ID: 591-890-401 -- Dave Scott --001a113315de072bb104f1a6d169 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Let's meet today and discuss
* how was the belgian beer at FOSDEM?
* what's the state of mirage-1.1.0?

1. =A0Please join my meeting.

2. =A0Use your microphone and speakers (VoIP) - a headset is recommended. = =A0Or,=A0call<= /span>=A0in using your telephone.

United= Kingdom (toll-free): 0 808 168 0209 United Kingdom:=A0+4= 4 (0) 207 151 1817

United States (toll-fr= ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00= 17

Access Code: 591-890-4= 01
Audio PI= N: Shown after joining the meeting

Meeting ID: 591-890-40= 1

--
Dave Scott
--001a113315de072bb104f1a6d169-- --===============5648489017261667470== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============5648489017261667470==-- From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 11:11:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 11:11: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 1WB0O6-000211-82; Wed, 05 Feb 2014 11:11:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB0O4-00020o-KM for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 11:11:24 +0000 Received: from [85.158.139.211:16963] by server-1.bemta-5.messagelabs.com id 54/71-12859-B5C12F25; Wed, 05 Feb 2014 11:11:23 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1391598681!1798612!1 X-Originating-IP: [209.85.160.47] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7123 invoked from network); 5 Feb 2014 11:11:23 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 11:11:23 -0000 Received: by mail-pb0-f47.google.com with SMTP id rp16so228707pbb.34 for ; Wed, 05 Feb 2014 03:11:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=N6f8RJOToHuSocCd/bburcrLda/qeVPK5obC2hvr5cY=; b=DQBRZG8Im7Y9D9FEs8hJ5xUnPfvZFLi8ev/jToqc4Q4/2qMIKtHzP8TZ4fn1TNpoyI 61Kd0wbeerlFuGdK26o2oaXaU8Ae5POHIdtN3Db7e/5N+dmpDfIel4iDUIXRxuoB5Fl/ Bl3jjdXzsf/OVslwMqww4UJL96e5blFFRxIqO6uYZkXQ8f/amcqyMY9P3IXnZSTVRibg 9cX3s+d7gG53gDjSb6C6FFblstVmthhDIN/pQxsDnnBZlvGjPrtKAyVQUc6L/CH0WSK4 d9e2YyqOCSHhANOHYD9L1eKtG1qr1SMVXD53WxuyUL9bR9JKbOOSC5AwlGRUTc/sMAT+ Wrxw== MIME-Version: 1.0 X-Received: by 10.66.139.100 with SMTP id qx4mr901166pab.141.1391598680614; Wed, 05 Feb 2014 03:11:20 -0800 (PST) Received: by 10.70.55.132 with HTTP; Wed, 5 Feb 2014 03:11:20 -0800 (PST) Date: Wed, 5 Feb 2014 11:11:20 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today (wednesday), 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5648489017261667470==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5648489017261667470== Content-Type: multipart/alternative; boundary=001a113315de072bb104f1a6d169 --001a113315de072bb104f1a6d169 Content-Type: text/plain; charset=ISO-8859-1 Let's meet today and discuss * how was the belgian beer at FOSDEM? * what's the state of mirage-1.1.0? 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817 United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Meeting ID: 591-890-401 -- Dave Scott --001a113315de072bb104f1a6d169 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Let's meet today and discuss
* how was the belgian beer at FOSDEM?
* what's the state of mirage-1.1.0?

1. =A0Please join my meeting.

2. =A0Use your microphone and speakers (VoIP) - a headset is recommended. = =A0Or,=A0call<= /span>=A0in using your telephone.

United= Kingdom (toll-free): 0 808 168 0209 United Kingdom:=A0+4= 4 (0) 207 151 1817

United States (toll-fr= ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00= 17

Access Code: 591-890-4= 01
Audio PI= N: Shown after joining the meeting

Meeting ID: 591-890-40= 1

--
Dave Scott
--001a113315de072bb104f1a6d169-- --===============5648489017261667470== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============5648489017261667470==-- From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 14:16:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 14:16: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 1WB3HO-0002tr-I0; Wed, 05 Feb 2014 14:16:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3HN-0002tl-Bn for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:16:41 +0000 Received: from [193.109.254.147:59643] by server-7.bemta-14.messagelabs.com id 89/B6-23424-8C742F25; Wed, 05 Feb 2014 14:16:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-27.messagelabs.com!1391609799!2190717!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23340 invoked from network); 5 Feb 2014 14:16:39 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-27.messagelabs.com with SMTP; 5 Feb 2014 14:16:39 -0000 Received: (qmail 8263 invoked by uid 634); 5 Feb 2014 14:16:39 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 05 Feb 2014 14:16:36 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 5 Feb 2014 14:16:35 +0000 Message-Id: References: <3A5EE044-D470-401D-B8BE-2877938349D4@recoil.org> To: Mike McClurg X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Sheets , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] some pointers for xen/arm on cubie2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0268394072596739673==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0268394072596739673== Content-Type: multipart/alternative; boundary="Apple-Mail=_A132E45E-9581-4BE8-8B12-B5F997A9C570" --Apple-Mail=_A132E45E-9581-4BE8-8B12-B5F997A9C570 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 4 Feb 2014, at 17:01, Mike McClurg wrote: > On Mon, Feb 3, 2014 at 4:00 PM, Anil Madhavapeddy = wrote: > As for a MiniOS to get Mirage up on ARM, Julien suggested that a = stripped down FreeBSD would be easier than a MiniOS, which I quite like = given that sharing the header files with FreeBSD will make porting the = kFreeBSD backend easier too in the medium term. The FreeBSD Xen/ARM = working git tree is here: >=20 > = http://xenbits.xen.org/gitweb/?p=3Dpeople/julieng/freebsd.git;a=3Dtree;f=3D= sys/arm/xenhvm;h=3D26ec9810bc775e24f08d18547a84ebba44792cf0;hb=3Dxen-arm >=20 > Might NetBSD's rump kernels also be a good replacement for MiniOS? = =46rom what I can tell, FreeBSD's ARM support is better than NetBSD's, = so this is a moot point for the Cubie discussion. I was mostly just = wondering what your thoughts were on a NetBSD rump kernel versus a = stripped down FreeBSD kernel. Either would suitable, but given that we have a kernel-module FreeBSD = backend already and FreeBSD Xen/ARM already, I don't see the point of = considering anything else in the short term. It should be quite = straightforward to port the OCaml runtime to rump kernels on NetBSD for = any interested party. -anil --Apple-Mail=_A132E45E-9581-4BE8-8B12-B5F997A9C570 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1 On 4 Feb 2014, at 17:01, Mike McClurg <mike.mcclurg@gmail.com> wrote:

On Mon, Feb 3, 2014 at 4:00 PM, Anil Madhavapeddy <anil@recoil.org> wrote:
As for a MiniOS to get Mirage up on ARM, Julien suggested that a stripped down FreeBSD would be easier than a MiniOS, which I quite like given that sharing the header files with FreeBSD will make porting the kFreeBSD backend easier too in the medium term.  The FreeBSD Xen/ARM working git tree is here:

http://xenbits.xen.org/gitweb/?p=people/julieng/freebsd.git;a=tree;f=sys/arm/xenhvm;h=26ec9810bc775e24f08d18547a84ebba44792cf0;hb=xen-arm

Might NetBSD's rump kernels also be a good replacement for MiniOS? From what I can tell, FreeBSD's ARM support is better than NetBSD's, so this is a moot point for the Cubie discussion. I was mostly just wondering what your thoughts were on a NetBSD rump kernel versus a stripped down FreeBSD kernel.

Either would suitable, but given that we have a kernel-module FreeBSD backend already and FreeBSD Xen/ARM already, I don't see the point of considering anything else in the short term.  It should be quite straightforward to port the OCaml runtime to rump kernels on NetBSD for any interested party.

-anil

--Apple-Mail=_A132E45E-9581-4BE8-8B12-B5F997A9C570-- --===============0268394072596739673== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============0268394072596739673==-- From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 14:16:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 14:16: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 1WB3HO-0002tr-I0; Wed, 05 Feb 2014 14:16:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3HN-0002tl-Bn for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:16:41 +0000 Received: from [193.109.254.147:59643] by server-7.bemta-14.messagelabs.com id 89/B6-23424-8C742F25; Wed, 05 Feb 2014 14:16:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-27.messagelabs.com!1391609799!2190717!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23340 invoked from network); 5 Feb 2014 14:16:39 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-27.messagelabs.com with SMTP; 5 Feb 2014 14:16:39 -0000 Received: (qmail 8263 invoked by uid 634); 5 Feb 2014 14:16:39 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 05 Feb 2014 14:16:36 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 5 Feb 2014 14:16:35 +0000 Message-Id: References: <3A5EE044-D470-401D-B8BE-2877938349D4@recoil.org> To: Mike McClurg X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Sheets , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] some pointers for xen/arm on cubie2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0268394072596739673==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0268394072596739673== Content-Type: multipart/alternative; boundary="Apple-Mail=_A132E45E-9581-4BE8-8B12-B5F997A9C570" --Apple-Mail=_A132E45E-9581-4BE8-8B12-B5F997A9C570 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 4 Feb 2014, at 17:01, Mike McClurg wrote: > On Mon, Feb 3, 2014 at 4:00 PM, Anil Madhavapeddy = wrote: > As for a MiniOS to get Mirage up on ARM, Julien suggested that a = stripped down FreeBSD would be easier than a MiniOS, which I quite like = given that sharing the header files with FreeBSD will make porting the = kFreeBSD backend easier too in the medium term. The FreeBSD Xen/ARM = working git tree is here: >=20 > = http://xenbits.xen.org/gitweb/?p=3Dpeople/julieng/freebsd.git;a=3Dtree;f=3D= sys/arm/xenhvm;h=3D26ec9810bc775e24f08d18547a84ebba44792cf0;hb=3Dxen-arm >=20 > Might NetBSD's rump kernels also be a good replacement for MiniOS? = =46rom what I can tell, FreeBSD's ARM support is better than NetBSD's, = so this is a moot point for the Cubie discussion. I was mostly just = wondering what your thoughts were on a NetBSD rump kernel versus a = stripped down FreeBSD kernel. Either would suitable, but given that we have a kernel-module FreeBSD = backend already and FreeBSD Xen/ARM already, I don't see the point of = considering anything else in the short term. It should be quite = straightforward to port the OCaml runtime to rump kernels on NetBSD for = any interested party. -anil --Apple-Mail=_A132E45E-9581-4BE8-8B12-B5F997A9C570 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1 On 4 Feb 2014, at 17:01, Mike McClurg <mike.mcclurg@gmail.com> wrote:

On Mon, Feb 3, 2014 at 4:00 PM, Anil Madhavapeddy <anil@recoil.org> wrote:
As for a MiniOS to get Mirage up on ARM, Julien suggested that a stripped down FreeBSD would be easier than a MiniOS, which I quite like given that sharing the header files with FreeBSD will make porting the kFreeBSD backend easier too in the medium term.  The FreeBSD Xen/ARM working git tree is here:

http://xenbits.xen.org/gitweb/?p=people/julieng/freebsd.git;a=tree;f=sys/arm/xenhvm;h=26ec9810bc775e24f08d18547a84ebba44792cf0;hb=xen-arm

Might NetBSD's rump kernels also be a good replacement for MiniOS? From what I can tell, FreeBSD's ARM support is better than NetBSD's, so this is a moot point for the Cubie discussion. I was mostly just wondering what your thoughts were on a NetBSD rump kernel versus a stripped down FreeBSD kernel.

Either would suitable, but given that we have a kernel-module FreeBSD backend already and FreeBSD Xen/ARM already, I don't see the point of considering anything else in the short term.  It should be quite straightforward to port the OCaml runtime to rump kernels on NetBSD for any interested party.

-anil

--Apple-Mail=_A132E45E-9581-4BE8-8B12-B5F997A9C570-- --===============0268394072596739673== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============0268394072596739673==-- From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 18:02:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 18:02: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 1WB6nu-0004QN-PE; Wed, 05 Feb 2014 18:02:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB6nu-0004QI-24 for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 18:02:30 +0000 Received: from [85.158.139.211:5736] by server-4.bemta-5.messagelabs.com id 92/E3-08092-5BC72F25; Wed, 05 Feb 2014 18:02:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1391623348!1897956!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23065 invoked from network); 5 Feb 2014 18:02:28 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 5 Feb 2014 18:02:28 -0000 Received: (qmail 26041 invoked by uid 634); 5 Feb 2014 18:02:27 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 05 Feb 2014 18:02:26 +0000 From: Anil Madhavapeddy Message-Id: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> Date: Wed, 5 Feb 2014 18:02:25 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, Dave and I bravely wrestled with Git today to rebase the Mirage 1.1 branch and send a mega unified pull request upstream: https://github.com/ocaml/opam-repository/pull/1655 This passes Travis (except for a few minor problems on OCaml 3.12.1), so I'm just going through the checklist for what else we need to do to push 1.1.x out the door: - update mirage-www config.ml examples on the wiki - add a blog post about how the net stack works with its functors (should work from the toplevel now) - port some of balraj's iperf examples to give him a template to work from (with 2 vifs <-> localhost) - merge in mirage-skeleton to new scheme - refresh the opam-doc on mirage.github.io Regarding mirage-skeleton, should we merge mirage-skeleton and mirage/lib_test? They seem to have broadly the same content, and it's useful to have just one repo. Mort, you had a FOSDEM branch, so your thoughts welcome here. Can anyone think of anything else? -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 18:02:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 18:02: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 1WB6nu-0004QN-PE; Wed, 05 Feb 2014 18:02:30 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB6nu-0004QI-24 for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 18:02:30 +0000 Received: from [85.158.139.211:5736] by server-4.bemta-5.messagelabs.com id 92/E3-08092-5BC72F25; Wed, 05 Feb 2014 18:02:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1391623348!1897956!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23065 invoked from network); 5 Feb 2014 18:02:28 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 5 Feb 2014 18:02:28 -0000 Received: (qmail 26041 invoked by uid 634); 5 Feb 2014 18:02:27 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 05 Feb 2014 18:02:26 +0000 From: Anil Madhavapeddy Message-Id: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> Date: Wed, 5 Feb 2014 18:02:25 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, Dave and I bravely wrestled with Git today to rebase the Mirage 1.1 branch and send a mega unified pull request upstream: https://github.com/ocaml/opam-repository/pull/1655 This passes Travis (except for a few minor problems on OCaml 3.12.1), so I'm just going through the checklist for what else we need to do to push 1.1.x out the door: - update mirage-www config.ml examples on the wiki - add a blog post about how the net stack works with its functors (should work from the toplevel now) - port some of balraj's iperf examples to give him a template to work from (with 2 vifs <-> localhost) - merge in mirage-skeleton to new scheme - refresh the opam-doc on mirage.github.io Regarding mirage-skeleton, should we merge mirage-skeleton and mirage/lib_test? They seem to have broadly the same content, and it's useful to have just one repo. Mort, you had a FOSDEM branch, so your thoughts welcome here. Can anyone think of anything else? -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 20:21:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 20: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 ) id 1WB8y3-0008JU-Ip; Wed, 05 Feb 2014 20:21:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB8y1-0008JP-Sq for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 20:21:06 +0000 Received: from [85.158.137.68:14156] by server-8.bemta-3.messagelabs.com id 59/1E-16039-13D92F25; Wed, 05 Feb 2014 20:21:05 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1391631664!13665222!1 X-Originating-IP: [195.62.217.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 582 invoked from network); 5 Feb 2014 20:21:04 -0000 Received: from engine02-20433-2.icritical.com (HELO engine02-20433-2.icritical.com) (195.62.217.151) by server-11.tower-31.messagelabs.com with SMTP; 5 Feb 2014 20:21:04 -0000 Received: (qmail 22356 invoked from network); 5 Feb 2014 20:20:58 -0000 Received: from localhost (127.0.0.1) by engine02-20433-2.icritical.com with SMTP; 5 Feb 2014 20:20:58 -0000 Received: from engine02-20433-2.icritical.com ([127.0.0.1]) by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 21876-09 for ; Wed, 5 Feb 2014 20:20:56 +0000 (GMT) Received: (qmail 22343 invoked by uid 599); 5 Feb 2014 20:20:56 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 05 Feb 2014 20:20:56 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WB8xw-0006Vp-Os; Wed, 05 Feb 2014 20:21:00 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Wed, 5 Feb 2014 20:20:59 +0000 Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: Ac8ir8ifffD2Cg2mTGqEAMCxedbKhQ== Message-ID: <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> In-Reply-To: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 18:02, Anil Madhavapeddy wrote: > Dave and I bravely wrestled with Git today the bards will still sing of your names years hence! > to rebase the Mirage 1.1 branch and send a mega unified pull request upstream: > > https://github.com/ocaml/opam-repository/pull/1655 out of curiosity, is there a rationale for naming (e.g. mirage-http vs simply tcpip)? > This passes Travis (except for a few minor problems on OCaml 3.12.1), we're still aiming to support 3.12.1 (and 4.00.1) then? > so I'm just going through the checklist for what else we need to do to push 1.1.x out the door: ... > - port some of balraj's iperf examples to give him a template to work from (with 2 vifs <-> localhost) > - merge in mirage-skeleton to new scheme i will have a PR for mirage-skeleton ready soon (maybe this evening). have been working through trying to organise & update the samples as well as incorporate the extra ones from fosdem. i'll see if i can get balraj's examples in there too. > Regarding mirage-skeleton, should we merge mirage-skeleton and mirage/lib_test? They seem to have broadly the same content, and it's useful to have just one repo. Mort, you had a FOSDEM branch, so your thoughts welcome here. i wondered about this putting the demo together. my own feeling is that they should be separate though there's lots of overlap for now. lib_test == unit tests which are definitely not the same thing as skeleton, which i think of as idiomatic/best-practice samples as a starting point for other development. i'd expect that lib_test should get more detailed and more complex test and regression cases that grow as time passes. skeleton probably stays relatively small and gets the cruft trimmed out over time. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 20:21:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 20: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 ) id 1WB8y3-0008JU-Ip; Wed, 05 Feb 2014 20:21:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB8y1-0008JP-Sq for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 20:21:06 +0000 Received: from [85.158.137.68:14156] by server-8.bemta-3.messagelabs.com id 59/1E-16039-13D92F25; Wed, 05 Feb 2014 20:21:05 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1391631664!13665222!1 X-Originating-IP: [195.62.217.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 582 invoked from network); 5 Feb 2014 20:21:04 -0000 Received: from engine02-20433-2.icritical.com (HELO engine02-20433-2.icritical.com) (195.62.217.151) by server-11.tower-31.messagelabs.com with SMTP; 5 Feb 2014 20:21:04 -0000 Received: (qmail 22356 invoked from network); 5 Feb 2014 20:20:58 -0000 Received: from localhost (127.0.0.1) by engine02-20433-2.icritical.com with SMTP; 5 Feb 2014 20:20:58 -0000 Received: from engine02-20433-2.icritical.com ([127.0.0.1]) by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 21876-09 for ; Wed, 5 Feb 2014 20:20:56 +0000 (GMT) Received: (qmail 22343 invoked by uid 599); 5 Feb 2014 20:20:56 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 05 Feb 2014 20:20:56 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WB8xw-0006Vp-Os; Wed, 05 Feb 2014 20:21:00 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Wed, 5 Feb 2014 20:20:59 +0000 Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: Ac8ir8ifffD2Cg2mTGqEAMCxedbKhQ== Message-ID: <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> In-Reply-To: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 18:02, Anil Madhavapeddy wrote: > Dave and I bravely wrestled with Git today the bards will still sing of your names years hence! > to rebase the Mirage 1.1 branch and send a mega unified pull request upstream: > > https://github.com/ocaml/opam-repository/pull/1655 out of curiosity, is there a rationale for naming (e.g. mirage-http vs simply tcpip)? > This passes Travis (except for a few minor problems on OCaml 3.12.1), we're still aiming to support 3.12.1 (and 4.00.1) then? > so I'm just going through the checklist for what else we need to do to push 1.1.x out the door: ... > - port some of balraj's iperf examples to give him a template to work from (with 2 vifs <-> localhost) > - merge in mirage-skeleton to new scheme i will have a PR for mirage-skeleton ready soon (maybe this evening). have been working through trying to organise & update the samples as well as incorporate the extra ones from fosdem. i'll see if i can get balraj's examples in there too. > Regarding mirage-skeleton, should we merge mirage-skeleton and mirage/lib_test? They seem to have broadly the same content, and it's useful to have just one repo. Mort, you had a FOSDEM branch, so your thoughts welcome here. i wondered about this putting the demo together. my own feeling is that they should be separate though there's lots of overlap for now. lib_test == unit tests which are definitely not the same thing as skeleton, which i think of as idiomatic/best-practice samples as a starting point for other development. i'd expect that lib_test should get more detailed and more complex test and regression cases that grow as time passes. skeleton probably stays relatively small and gets the cruft trimmed out over time. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 20:52:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 20:52: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 1WB9SI-0001wv-Q7; Wed, 05 Feb 2014 20:52:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB9SH-0001wq-LF for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 20:52:21 +0000 Received: from [85.158.143.35:29257] by server-3.bemta-4.messagelabs.com id F4/7B-11539-484A2F25; Wed, 05 Feb 2014 20:52:20 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-5.tower-21.messagelabs.com!1391633540!3418054!1 X-Originating-IP: [131.111.8.133] X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26800 invoked from network); 5 Feb 2014 20:52:20 -0000 Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk) (131.111.8.133) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Feb 2014 20:52:20 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dab-hlw1-h-45-6.dab.02.net ([82.132.234.110]:13375 helo=[10.138.0.38]) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1WB9SB-00006m-ig (Exim 4.82_3-c0e5623) (return-path ); Wed, 05 Feb 2014 20:52:18 +0000 References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> Mime-Version: 1.0 (1.0) In-Reply-To: <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> Message-Id: X-Mailer: iPhone Mail (11B554a) From: Amir Chaudhry Date: Wed, 5 Feb 2014 20:52:05 +0000 To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org -- sent via mobile > On 5 Feb 2014, at 20:20, Richard Mortier wrote: > > >> On 5 Feb 2014, at 18:02, Anil Madhavapeddy wrote: >> >> Dave and I bravely wrestled with Git today > > the bards will still sing of your names years hence! [TODO: insert witty limerick] >> This passes Travis (except for a few minor problems on OCaml 3.12.1), > > we're still aiming to support 3.12.1 (and 4.00.1) then? Is this an upstream thing? Wheezy has 3.12.x, so supporting that would make getting started pretty quick (no need to wait for opam to get a newer version). AC _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 20:52:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 20:52: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 1WB9SI-0001wv-Q7; Wed, 05 Feb 2014 20:52:22 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB9SH-0001wq-LF for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 20:52:21 +0000 Received: from [85.158.143.35:29257] by server-3.bemta-4.messagelabs.com id F4/7B-11539-484A2F25; Wed, 05 Feb 2014 20:52:20 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-5.tower-21.messagelabs.com!1391633540!3418054!1 X-Originating-IP: [131.111.8.133] X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26800 invoked from network); 5 Feb 2014 20:52:20 -0000 Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk) (131.111.8.133) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Feb 2014 20:52:20 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dab-hlw1-h-45-6.dab.02.net ([82.132.234.110]:13375 helo=[10.138.0.38]) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1WB9SB-00006m-ig (Exim 4.82_3-c0e5623) (return-path ); Wed, 05 Feb 2014 20:52:18 +0000 References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> Mime-Version: 1.0 (1.0) In-Reply-To: <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> Message-Id: X-Mailer: iPhone Mail (11B554a) From: Amir Chaudhry Date: Wed, 5 Feb 2014 20:52:05 +0000 To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org -- sent via mobile > On 5 Feb 2014, at 20:20, Richard Mortier wrote: > > >> On 5 Feb 2014, at 18:02, Anil Madhavapeddy wrote: >> >> Dave and I bravely wrestled with Git today > > the bards will still sing of your names years hence! [TODO: insert witty limerick] >> This passes Travis (except for a few minor problems on OCaml 3.12.1), > > we're still aiming to support 3.12.1 (and 4.00.1) then? Is this an upstream thing? Wheezy has 3.12.x, so supporting that would make getting started pretty quick (no need to wait for opam to get a newer version). AC _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 21:06:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 21:06: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 1WB9gA-0002Ne-EB; Wed, 05 Feb 2014 21:06:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB9g9-0002NZ-3F for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 21:06:41 +0000 Received: from [193.109.254.147:53192] by server-9.bemta-14.messagelabs.com id FE/3D-24895-0E7A2F25; Wed, 05 Feb 2014 21:06:40 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1391634398!2272731!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4083 invoked from network); 5 Feb 2014 21:06:39 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 21:06:39 -0000 X-IronPort-AV: E=Sophos;i="4.95,788,1384300800"; d="scan'208";a="98404264" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Feb 2014 21:06:28 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server (TLS) id 14.2.342.4; Wed, 5 Feb 2014 16:06:27 -0500 Received: from AMSPEX01CL03.citrite.net ([169.254.8.218]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Wed, 5 Feb 2014 22:06:26 +0100 From: Dave Scott To: Amir Chaudhry Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: AQHPIpx/g8KJojSwP0mZoDLFw3UO3ZqnCZOAgAAIsYCAABTGgA== Date: Wed, 5 Feb 2014 21:06:26 +0000 Message-ID: <3AC3B5BA-ACA9-4048-A5E6-15F1514D7DBF@eu.citrix.com> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk>, In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: MIA1 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On Feb 5, 2014, at 8:53 PM, "Amir Chaudhry" wrote: > > > > -- > sent via mobile > >> On 5 Feb 2014, at 20:20, Richard Mortier wrote: >> >> >>> On 5 Feb 2014, at 18:02, Anil Madhavapeddy wrote: >>> >>> Dave and I bravely wrestled with Git today >> >> the bards will still sing of your names years hence! > > [TODO: insert witty limerick] > >>> This passes Travis (except for a few minor problems on OCaml 3.12.1), >> >> we're still aiming to support 3.12.1 (and 4.00.1) then? > > Is this an upstream thing? Wheezy has 3.12.x, so supporting that would make getting started pretty quick (no need to wait for opam to get a newer version). Tbh I've been ignoring 3.12 build failures since I'm pretty sure I'm using v4 features around the place. I have been fixing 4.00.1 issues though (eg by defining |> ) Cheers, Dave > > AC > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 21:06:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 21:06: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 1WB9gA-0002Ne-EB; Wed, 05 Feb 2014 21:06:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB9g9-0002NZ-3F for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 21:06:41 +0000 Received: from [193.109.254.147:53192] by server-9.bemta-14.messagelabs.com id FE/3D-24895-0E7A2F25; Wed, 05 Feb 2014 21:06:40 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1391634398!2272731!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4083 invoked from network); 5 Feb 2014 21:06:39 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 21:06:39 -0000 X-IronPort-AV: E=Sophos;i="4.95,788,1384300800"; d="scan'208";a="98404264" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Feb 2014 21:06:28 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server (TLS) id 14.2.342.4; Wed, 5 Feb 2014 16:06:27 -0500 Received: from AMSPEX01CL03.citrite.net ([169.254.8.218]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Wed, 5 Feb 2014 22:06:26 +0100 From: Dave Scott To: Amir Chaudhry Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: AQHPIpx/g8KJojSwP0mZoDLFw3UO3ZqnCZOAgAAIsYCAABTGgA== Date: Wed, 5 Feb 2014 21:06:26 +0000 Message-ID: <3AC3B5BA-ACA9-4048-A5E6-15F1514D7DBF@eu.citrix.com> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk>, In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: MIA1 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > On Feb 5, 2014, at 8:53 PM, "Amir Chaudhry" wrote: > > > > -- > sent via mobile > >> On 5 Feb 2014, at 20:20, Richard Mortier wrote: >> >> >>> On 5 Feb 2014, at 18:02, Anil Madhavapeddy wrote: >>> >>> Dave and I bravely wrestled with Git today >> >> the bards will still sing of your names years hence! > > [TODO: insert witty limerick] > >>> This passes Travis (except for a few minor problems on OCaml 3.12.1), >> >> we're still aiming to support 3.12.1 (and 4.00.1) then? > > Is this an upstream thing? Wheezy has 3.12.x, so supporting that would make getting started pretty quick (no need to wait for opam to get a newer version). Tbh I've been ignoring 3.12 build failures since I'm pretty sure I'm using v4 features around the place. I have been fixing 4.00.1 issues though (eg by defining |> ) Cheers, Dave > > AC > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 21:11:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 21:11: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 1WB9kL-0002bl-R0; Wed, 05 Feb 2014 21:11:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB9kJ-0002bg-UP for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 21:11:00 +0000 Received: from [85.158.143.35:48937] by server-2.bemta-4.messagelabs.com id 5F/72-10891-3E8A2F25; Wed, 05 Feb 2014 21:10:59 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-21.messagelabs.com!1391634658!3454604!1 X-Originating-IP: [195.62.217.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTIgPT4gMTY3OTY=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13070 invoked from network); 5 Feb 2014 21:10:58 -0000 Received: from engine04-20433-4.icritical.com (HELO engine04-20433-4.icritical.com) (195.62.217.152) by server-13.tower-21.messagelabs.com with SMTP; 5 Feb 2014 21:10:58 -0000 Received: (qmail 13676 invoked from network); 5 Feb 2014 21:10:51 -0000 Received: from localhost (127.0.0.1) by engine04-20433-4.icritical.com with SMTP; 5 Feb 2014 21:10:51 -0000 Received: from engine04-20433-4.icritical.com ([127.0.0.1]) by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 13325-01 for ; Wed, 5 Feb 2014 21:10:50 +0000 (GMT) Received: (qmail 13665 invoked by uid 599); 5 Feb 2014 21:10:50 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 05 Feb 2014 21:10:50 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WB9kG-0007QY-5u; Wed, 05 Feb 2014 21:10:56 +0000 From: Richard Mortier To: Dave Scott Date: Wed, 5 Feb 2014 21:10:55 +0000 Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: Ac8itsIUvT8MOu/4QM67LdBkSLTXig== Message-ID: <00A802D7-6D3B-49EF-B4B9-720A1F5E98A2@nottingham.ac.uk> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk>, <3AC3B5BA-ACA9-4048-A5E6-15F1514D7DBF@eu.citrix.com> In-Reply-To: <3AC3B5BA-ACA9-4048-A5E6-15F1514D7DBF@eu.citrix.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com Cc: Anil Madhavapeddy , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 21:06, Dave Scott wrote: > On Feb 5, 2014, at 8:53 PM, "Amir Chaudhry" wrote: >> >> On 5 Feb 2014, at 20:20, Richard Mortier wrote: >> >>> we're still aiming to support 3.12.1 (and 4.00.1) then? >> >> Is this an upstream thing? Wheezy has 3.12.x, so supporting that would make getting started pretty quick (no need to wait for opam to get a newer version). > > Tbh I've been ignoring 3.12 build failures since I'm pretty sure I'm using v4 features around the place. I have been fixing 4.00.1 issues though (eg by defining |> ) btw, out of curiosity, are there other common points of incompatibility between 4.01 and 4.00.1? -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Feb 05 21:11:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 05 Feb 2014 21:11: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 1WB9kL-0002bl-R0; Wed, 05 Feb 2014 21:11:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB9kJ-0002bg-UP for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 21:11:00 +0000 Received: from [85.158.143.35:48937] by server-2.bemta-4.messagelabs.com id 5F/72-10891-3E8A2F25; Wed, 05 Feb 2014 21:10:59 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-21.messagelabs.com!1391634658!3454604!1 X-Originating-IP: [195.62.217.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTIgPT4gMTY3OTY=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13070 invoked from network); 5 Feb 2014 21:10:58 -0000 Received: from engine04-20433-4.icritical.com (HELO engine04-20433-4.icritical.com) (195.62.217.152) by server-13.tower-21.messagelabs.com with SMTP; 5 Feb 2014 21:10:58 -0000 Received: (qmail 13676 invoked from network); 5 Feb 2014 21:10:51 -0000 Received: from localhost (127.0.0.1) by engine04-20433-4.icritical.com with SMTP; 5 Feb 2014 21:10:51 -0000 Received: from engine04-20433-4.icritical.com ([127.0.0.1]) by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 13325-01 for ; Wed, 5 Feb 2014 21:10:50 +0000 (GMT) Received: (qmail 13665 invoked by uid 599); 5 Feb 2014 21:10:50 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 05 Feb 2014 21:10:50 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WB9kG-0007QY-5u; Wed, 05 Feb 2014 21:10:56 +0000 From: Richard Mortier To: Dave Scott Date: Wed, 5 Feb 2014 21:10:55 +0000 Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: Ac8itsIUvT8MOu/4QM67LdBkSLTXig== Message-ID: <00A802D7-6D3B-49EF-B4B9-720A1F5E98A2@nottingham.ac.uk> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk>, <3AC3B5BA-ACA9-4048-A5E6-15F1514D7DBF@eu.citrix.com> In-Reply-To: <3AC3B5BA-ACA9-4048-A5E6-15F1514D7DBF@eu.citrix.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com Cc: Anil Madhavapeddy , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 21:06, Dave Scott wrote: > On Feb 5, 2014, at 8:53 PM, "Amir Chaudhry" wrote: >> >> On 5 Feb 2014, at 20:20, Richard Mortier wrote: >> >>> we're still aiming to support 3.12.1 (and 4.00.1) then? >> >> Is this an upstream thing? Wheezy has 3.12.x, so supporting that would make getting started pretty quick (no need to wait for opam to get a newer version). > > Tbh I've been ignoring 3.12 build failures since I'm pretty sure I'm using v4 features around the place. I have been fixing 4.00.1 issues though (eg by defining |> ) btw, out of curiosity, are there other common points of incompatibility between 4.01 and 4.00.1? -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 09:45:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 09:45:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLWs-0005V4-V7; Thu, 06 Feb 2014 09:45:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLWr-0005Uv-Gi for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 09:45:53 +0000 Received: from [193.109.254.147:42893] by server-6.bemta-14.messagelabs.com id D8/A1-03396-0D953F25; Thu, 06 Feb 2014 09:45:52 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1391679951!2413351!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3308 invoked from network); 6 Feb 2014 09:45:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-27.messagelabs.com with SMTP; 6 Feb 2014 09:45:52 -0000 Received: (qmail 5406 invoked by uid 634); 6 Feb 2014 09:45:51 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 06 Feb 2014 09:45:50 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> Date: Thu, 6 Feb 2014 09:45:49 +0000 Message-Id: <188704D8-9162-41F8-B508-C69F428DA576@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 20:20, Richard Mortier wrote: > >> to rebase the Mirage 1.1 branch and send a mega unified pull request upstream: >> >> https://github.com/ocaml/opam-repository/pull/1655 > > out of curiosity, is there a rationale for naming (e.g. mirage-http vs simply tcpip)? Good question -- the tcpip stack is pretty independent of Mirage -- I'm writing some testcases that just directly use ocaml-tuntap to spin up some packet tests. The mirage-http repo is fairly Mirage-specific, as it's just a thin wrapper over cohttp_lwt. A fine distinction, and possibly not one worth making, but probably easier to keep for now since most people will never notice the difference anyway. > >> This passes Travis (except for a few minor problems on OCaml 3.12.1), > > we're still aiming to support 3.12.1 (and 4.00.1) then? I'm trying to maintain 3.12.1 support for individual libraries where feasible, but not for the overall Mirage tool. The Xen runtime is only available for 4.00.1 an 4.01.0 at the moment, so that backend won't compile on 3.12.1. > >> Regarding mirage-skeleton, should we merge mirage-skeleton and mirage/lib_test? They seem to have broadly the same content, and it's useful to have just one repo. Mort, you had a FOSDEM branch, so your thoughts welcome here. > > i wondered about this putting the demo together. my own feeling is that they should be separate though there's lots of overlap for now. lib_test == unit tests which are definitely not the same thing as skeleton, which i think of as idiomatic/best-practice samples as a starting point for other development. i'd expect that lib_test should get more detailed and more complex test and regression cases that grow as time passes. skeleton probably stays relatively small and gets the cruft trimmed out over time. That makes sense to me. Let's keep them separate then. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 09:45:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 09:45:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLWs-0005V4-V7; Thu, 06 Feb 2014 09:45:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLWr-0005Uv-Gi for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 09:45:53 +0000 Received: from [193.109.254.147:42893] by server-6.bemta-14.messagelabs.com id D8/A1-03396-0D953F25; Thu, 06 Feb 2014 09:45:52 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1391679951!2413351!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3308 invoked from network); 6 Feb 2014 09:45:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-27.messagelabs.com with SMTP; 6 Feb 2014 09:45:52 -0000 Received: (qmail 5406 invoked by uid 634); 6 Feb 2014 09:45:51 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 06 Feb 2014 09:45:50 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> Date: Thu, 6 Feb 2014 09:45:49 +0000 Message-Id: <188704D8-9162-41F8-B508-C69F428DA576@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 20:20, Richard Mortier wrote: > >> to rebase the Mirage 1.1 branch and send a mega unified pull request upstream: >> >> https://github.com/ocaml/opam-repository/pull/1655 > > out of curiosity, is there a rationale for naming (e.g. mirage-http vs simply tcpip)? Good question -- the tcpip stack is pretty independent of Mirage -- I'm writing some testcases that just directly use ocaml-tuntap to spin up some packet tests. The mirage-http repo is fairly Mirage-specific, as it's just a thin wrapper over cohttp_lwt. A fine distinction, and possibly not one worth making, but probably easier to keep for now since most people will never notice the difference anyway. > >> This passes Travis (except for a few minor problems on OCaml 3.12.1), > > we're still aiming to support 3.12.1 (and 4.00.1) then? I'm trying to maintain 3.12.1 support for individual libraries where feasible, but not for the overall Mirage tool. The Xen runtime is only available for 4.00.1 an 4.01.0 at the moment, so that backend won't compile on 3.12.1. > >> Regarding mirage-skeleton, should we merge mirage-skeleton and mirage/lib_test? They seem to have broadly the same content, and it's useful to have just one repo. Mort, you had a FOSDEM branch, so your thoughts welcome here. > > i wondered about this putting the demo together. my own feeling is that they should be separate though there's lots of overlap for now. lib_test == unit tests which are definitely not the same thing as skeleton, which i think of as idiomatic/best-practice samples as a starting point for other development. i'd expect that lib_test should get more detailed and more complex test and regression cases that grow as time passes. skeleton probably stays relatively small and gets the cruft trimmed out over time. That makes sense to me. Let's keep them separate then. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 09:47:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 09:47:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLY1-0005ZV-5w; Thu, 06 Feb 2014 09:47:05 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLXz-0005ZO-TP for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 09:47:04 +0000 Received: from [193.109.254.147:6843] by server-6.bemta-14.messagelabs.com id F7/43-03396-71A53F25; Thu, 06 Feb 2014 09:47:03 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1391680022!2413818!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22534 invoked from network); 6 Feb 2014 09:47:02 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-27.messagelabs.com with SMTP; 6 Feb 2014 09:47:02 -0000 Received: (qmail 29569 invoked by uid 634); 6 Feb 2014 09:47:02 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 06 Feb 2014 09:47:02 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 6 Feb 2014 09:47:00 +0000 Message-Id: References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> To: Amir M Chaudhry X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 20:52, Amir Chaudhry wrote: >>> This passes Travis (except for a few minor problems on OCaml 3.12.1), >> >> we're still aiming to support 3.12.1 (and 4.00.1) then? > > Is this an upstream thing? Wheezy has 3.12.x, so supporting that would make getting started pretty quick (no need to wait for opam to get a newer version). Right, it makes binary packages easier for upstream users (such as Xen). We're unlikely to support 3.12.1 ever though... Debian testing has 4.01.0 now, and I publish Ubuntu PPA packages with 4.01.0 as well. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 09:47:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 09:47:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLY1-0005ZV-5w; Thu, 06 Feb 2014 09:47:05 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLXz-0005ZO-TP for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 09:47:04 +0000 Received: from [193.109.254.147:6843] by server-6.bemta-14.messagelabs.com id F7/43-03396-71A53F25; Thu, 06 Feb 2014 09:47:03 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1391680022!2413818!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22534 invoked from network); 6 Feb 2014 09:47:02 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-27.messagelabs.com with SMTP; 6 Feb 2014 09:47:02 -0000 Received: (qmail 29569 invoked by uid 634); 6 Feb 2014 09:47:02 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 06 Feb 2014 09:47:02 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 6 Feb 2014 09:47:00 +0000 Message-Id: References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> To: Amir M Chaudhry X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 20:52, Amir Chaudhry wrote: >>> This passes Travis (except for a few minor problems on OCaml 3.12.1), >> >> we're still aiming to support 3.12.1 (and 4.00.1) then? > > Is this an upstream thing? Wheezy has 3.12.x, so supporting that would make getting started pretty quick (no need to wait for opam to get a newer version). Right, it makes binary packages easier for upstream users (such as Xen). We're unlikely to support 3.12.1 ever though... Debian testing has 4.01.0 now, and I publish Ubuntu PPA packages with 4.01.0 as well. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 09:50:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 09:50:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLar-0005qr-Gt; Thu, 06 Feb 2014 09:50:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLap-0005qk-SY for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 09:50:00 +0000 Received: from [193.109.254.147:27265] by server-5.bemta-14.messagelabs.com id B7/BE-16688-7CA53F25; Thu, 06 Feb 2014 09:49:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1391680198!2416060!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 498 invoked from network); 6 Feb 2014 09:49:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-27.messagelabs.com with SMTP; 6 Feb 2014 09:49:58 -0000 Received: (qmail 19412 invoked by uid 634); 6 Feb 2014 09:49:58 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 06 Feb 2014 09:49:58 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <00A802D7-6D3B-49EF-B4B9-720A1F5E98A2@nottingham.ac.uk> Date: Thu, 6 Feb 2014 09:49:56 +0000 Message-Id: <779C4FE7-9A31-476C-8398-6C0994C9B133@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk>, <3AC3B5BA-ACA9-4048-A5E6-15F1514D7DBF@eu.citrix.com> <00A802D7-6D3B-49EF-B4B9-720A1F5E98A2@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 21:10, Richard Mortier wrote: > btw, out of curiosity, are there other common points of incompatibility between 4.01 and 4.00.1? The main differentiator is the addition of record disambiguation in 4.01.0, which lets you shadow field names across records in the same module, but still access both types. Spotting hidden uses of this (very useful) feature is why I normally activate the `principal` tag in my libraries (by editing _tags). You can read more about it here: https://realworldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-type-checking.html#enforcing-principal-typing There are some significant performance improvements in 4.01.0 (direct bigarray intrinsics, faster write barrier, code generation quality particularly for ARM) that will not be user facing, but mean that you should always benchmark using 4.01.0 to keep a consistent baseline. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 09:50:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 09:50:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLar-0005qr-Gt; Thu, 06 Feb 2014 09:50:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBLap-0005qk-SY for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 09:50:00 +0000 Received: from [193.109.254.147:27265] by server-5.bemta-14.messagelabs.com id B7/BE-16688-7CA53F25; Thu, 06 Feb 2014 09:49:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1391680198!2416060!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 498 invoked from network); 6 Feb 2014 09:49:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-27.messagelabs.com with SMTP; 6 Feb 2014 09:49:58 -0000 Received: (qmail 19412 invoked by uid 634); 6 Feb 2014 09:49:58 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 06 Feb 2014 09:49:58 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <00A802D7-6D3B-49EF-B4B9-720A1F5E98A2@nottingham.ac.uk> Date: Thu, 6 Feb 2014 09:49:56 +0000 Message-Id: <779C4FE7-9A31-476C-8398-6C0994C9B133@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk>, <3AC3B5BA-ACA9-4048-A5E6-15F1514D7DBF@eu.citrix.com> <00A802D7-6D3B-49EF-B4B9-720A1F5E98A2@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: David Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 21:10, Richard Mortier wrote: > btw, out of curiosity, are there other common points of incompatibility between 4.01 and 4.00.1? The main differentiator is the addition of record disambiguation in 4.01.0, which lets you shadow field names across records in the same module, but still access both types. Spotting hidden uses of this (very useful) feature is why I normally activate the `principal` tag in my libraries (by editing _tags). You can read more about it here: https://realworldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-type-checking.html#enforcing-principal-typing There are some significant performance improvements in 4.01.0 (direct bigarray intrinsics, faster write barrier, code generation quality particularly for ARM) that will not be user facing, but mean that you should always benchmark using 4.01.0 to keep a consistent baseline. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002it-Mc; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3jo-0005bU-Eg for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:46:08 +0000 Received: from [193.109.254.147:26381] by server-7.bemta-14.messagelabs.com id 07/A0-23424-BAE42F25; Wed, 05 Feb 2014 14:46:03 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1391611561!2223046!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20156 invoked from network); 5 Feb 2014 14:46:03 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:46:03 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="98224477" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Feb 2014 14:46:01 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:46:00 -0500 Message-ID: <1391611558.23098.2.camel@kazak.uk.xensource.com> From: Ian Campbell To: Andrew Cooper Date: Wed, 5 Feb 2014 14:45:58 +0000 In-Reply-To: <52F24D4D.7040004@citrix.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <52F24D4D.7040004@citrix.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Konrad Rzeszutek Wilk , Dario Faggioli , Ian Jackson , Paul Durrant , Santosh Jodh , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote: > On 05/02/14 14:09, Ian Campbell wrote: > > > > Andy: > > > > * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA > > allocations > > > > Sounds too hard for a GSoC to me. Would need fleshing out in any > > case. > > Malcolm made a prototype for this on the first day of the Hackathon. It > can disappear. Removed. > > * CPU/RAM/PCI diagram tool > > > > Does this not already exist somewhere? > > Not as far as I (or my ability to google) am aware. > > My furrowing into hwloc interacting with Xen and libxc is a start to all > of this, but it is still very much in my copious free time and there is > more than enough other work which could be done if someone were interested. OK, left in place. This could conceivably be done under another umbrella such as the Linux one too, since it seems generic. Ian. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002ij-Ip; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3ed-0004yB-9b for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:40:43 +0000 Received: from [85.158.139.211:48402] by server-9.bemta-5.messagelabs.com id 66/76-11237-A6D42F25; Wed, 05 Feb 2014 14:40:42 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1391611240!1867900!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11462 invoked from network); 5 Feb 2014 14:40:41 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:40:41 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="100113523" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Feb 2014 14:40:14 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:40:13 -0500 Received: from andrewcoop.uk.xensource.com ([10.80.2.18]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1WB3e9-0006vT-OJ; Wed, 05 Feb 2014 14:40:13 +0000 Message-ID: <52F24D4D.7040004@citrix.com> Date: Wed, 5 Feb 2014 14:40:13 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: Ian Campbell References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> X-Enigmail-Version: 1.6 X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Konrad Rzeszutek Wilk , Dario Faggioli , Ian Jackson , Paul Durrant , Santosh Jodh , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 05/02/14 14:09, Ian Campbell wrote: > > Andy: > > * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA > allocations > > Sounds too hard for a GSoC to me. Would need fleshing out in any > case. Malcolm made a prototype for this on the first day of the Hackathon. It can disappear. > > * CPU/RAM/PCI diagram tool > > Does this not already exist somewhere? Not as far as I (or my ability to google) am aware. My furrowing into hwloc interacting with Xen and libxc is a start to all of this, but it is still very much in my copious free time and there is more than enough other work which could be done if someone were interested. ~Andrew _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002j3-QL; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBMvu-0002Se-RI for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 11:15:51 +0000 Received: from [85.158.143.35:35776] by server-3.bemta-4.messagelabs.com id 60/5B-11539-6EE63F25; Thu, 06 Feb 2014 11:15:50 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1391685341!3571066!1 X-Originating-IP: [74.125.82.169] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14664 invoked from network); 6 Feb 2014 11:15:44 -0000 Received: from mail-we0-f169.google.com (HELO mail-we0-f169.google.com) (74.125.82.169) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 11:15:44 -0000 Received: by mail-we0-f169.google.com with SMTP id t61so1199184wes.0 for ; Thu, 06 Feb 2014 03:15:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tWfx+hLlkvxWNgFPg9BXDw3USJ/gmN2xeV97+hLEYc8=; b=ZPdXleKA3TLfRZoqyL4wZgL/QYOCnA3f1ZiGatPpxDwT6/lJiAQPpkpOMQxFjT3FLH woO5+21KB/3It78R+5tCaAJhBP2NTcfwurDvDZbBvAC0t7yv7sgtA6SdytjnsvVFSu/k G1gl+Ir9nxfzm6LZtLIwT6NghoKQzu8iVbtpXmQYgUL0W/YjTbc8u+KAJYZfH1MgC9sj idDUzYXmkzeKYPdvteL7wDthnPjTMjLpc9/UGzbnJsLRYUfnkkpMJat2KxWHWcwXS5zg ONSXrkEbiJqdx+fR6QTaW0NF8Hk0U9Pnk0JnhGaQ5k8Zj7Gxga2bvmGNjD7RKSRxhZ4A K43w== MIME-Version: 1.0 X-Received: by 10.180.185.197 with SMTP id fe5mr20783079wic.56.1391685341063; Thu, 06 Feb 2014 03:15:41 -0800 (PST) Received: by 10.194.75.163 with HTTP; Thu, 6 Feb 2014 03:15:40 -0800 (PST) In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> Date: Thu, 6 Feb 2014 11:15:40 +0000 X-Google-Sender-Auth: zbmLP1_IZa_gNqVy2VQhCv5jGkQ Message-ID: From: George Dunlap To: Ian Campbell X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Konrad Rzeszutek Wilk , Andrew Cooper , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , Santosh Jodh , "xen-api@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, Feb 5, 2014 at 2:09 PM, Ian Campbell wrote: > George: > > * Introducing PowerClamp-like driver for Xen > > I don't think this has been done? Not that I'm aware of. > George: > > * Allowing guests to boot with a passed-through GPU as the primary > display > > This seems like a bit of a rathole for a GSoC student to me... Possibly. I thought it might be a bit more attractive project, but maybe that's a bad thing... > * Advanced Scheduling Parameters > > Still to do? Yes. -George _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5n-0002jn-3u; Thu, 06 Feb 2014 17:50:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBT35-0002Vx-ND for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 17:47:39 +0000 Received: from [85.158.137.68:28028] by server-3.bemta-3.messagelabs.com id 17/A4-14520-ABAC3F25; Thu, 06 Feb 2014 17:47:38 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1391708856!140730!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29538 invoked from network); 6 Feb 2014 17:47:38 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 17:47:38 -0000 X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="98665806" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 06 Feb 2014 17:47:35 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server (TLS) id 14.2.342.4; Thu, 6 Feb 2014 12:47:35 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.176]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Thu, 6 Feb 2014 18:47:33 +0100 From: Paul Durrant To: Ian Campbell Thread-Topic: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Thread-Index: AQHPInvYpj3b21EIS0q8f9DE1KOLi5qoX58AgAAhFQD//++gAIAAEZ5w Date: Thu, 6 Feb 2014 17:47:32 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD022712E@AMSPEX01CL01.citrite.net> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD02270E9@AMSPEX01CL01.citrite.net> <1391708646.2162.12.camel@kazak.uk.xensource.com> In-Reply-To: <1391708646.2162.12.camel@kazak.uk.xensource.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.2.29] MIME-Version: 1.0 X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Konrad Rzeszutek Wilk , Andrew Cooper , Dario Faggioli , Ben Guthro , Santosh Jodh , "xen-api@lists.xen.org" , Ian Jackson , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBJYW4gQ2FtcGJlbGwNCj4gU2Vu dDogMDYgRmVicnVhcnkgMjAxNCAxNzo0NA0KPiBUbzogUGF1bCBEdXJyYW50DQo+IENjOiBTYW50 b3NoIEpvZGg7IGxhcnMua3VydGhAeGVuLm9yZzsgUm9nZXIgUGF1IE1vbm5lOyBEYXJpbyBGYWdn aW9saTsNCj4gS29ucmFkIFJ6ZXN6dXRlayBXaWxrOyBCZW4gR3V0aHJvOyBBbmRyZXcgQ29vcGVy OyBJYW4gSmFja3NvbjsgeGVuLQ0KPiBkZXZlbEBsaXN0cy54ZW4ub3JnOyB4ZW4tYXBpQGxpc3Rz Lnhlbi5vcmc7IG1pcmFnZW9zLQ0KPiBkZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZw0KPiBTdWJq ZWN0OiBSZTogW1hlbi1kZXZlbF0gUHJlcHBpbmcgZm9yIEdTT0MgMjAxNCBbVVJHRU5UXSAtIGRl YWRsaW5lIEZlYiAxNA0KPiAyMDE0DQo+IA0KPiBPbiBUaHUsIDIwMTQtMDItMDYgYXQgMTc6NDMg KzAwMDAsIFBhdWwgRHVycmFudCB3cm90ZToNCj4gPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t LS0tDQo+ID4gPiBGcm9tOiBTYW50b3NoIEpvZGgNCj4gPiA+IFNlbnQ6IDA2IEZlYnJ1YXJ5IDIw MTQgMTY6NDQNCj4gPiA+IFRvOiBJYW4gQ2FtcGJlbGw7IGxhcnMua3VydGhAeGVuLm9yZzsgUm9n ZXIgUGF1IE1vbm5lOyBEYXJpbyBGYWdnaW9saTsNCj4gPiA+IEtvbnJhZCBSemVzenV0ZWsgV2ls azsgQmVuIEd1dGhybzsgQW5kcmV3IENvb3BlcjsgUGF1bCBEdXJyYW50OyBJYW4NCj4gPiA+IEph Y2tzb24NCj4gPiA+IENjOiB4ZW4tZGV2ZWxAbGlzdHMueGVuLm9yZzsgeGVuLWFwaUBsaXN0cy54 ZW4ub3JnOyBtaXJhZ2Vvcy0NCj4gPiA+IGRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnDQo+ID4g PiBTdWJqZWN0OiBSRTogW1hlbi1kZXZlbF0gUHJlcHBpbmcgZm9yIEdTT0MgMjAxNCBbVVJHRU5U XSAtIGRlYWRsaW5lDQo+IEZlYiAxNA0KPiA+ID4gMjAxNA0KPiA+ID4NCj4gPiA+ID4NCj4gPiA+ ID4gU2FudG9zaDoNCj4gPiA+ID4NCj4gPiA+ID4gICAgICAgKiBLREQgKFdpbmRvd3MgRGVidWdn ZXIgU3R1YikgZW5oYW5jZW1lbnRzDQo+ID4gPiA+DQo+ID4gPiBbU2FudG9zaCBKb2RoXSBJIGJl bGlldmUgdGhpcyBpcyBzdGlsbCBhIGdvb2QgR1NPQyBwcm9qZWN0LiBIb3dldmVyLCBpbiBsaWdo dA0KPiBvZg0KPiA+ID4gbXkgbmV3IGRpcmVjdGlvbiwgSSBhbSBub3Qgc3VyZSBpZiBJIHdpbGwg YmUgYWJsZSB0byBtZW50b3IuIERvbuKAmXQga25vdyBpZg0KPiBQYXVsDQo+ID4gPiBvciBzb21l b25lIGVsc2Ugb24gdGhlIFdpbmRvd3MgdGVhbSB3b3VsZCB3YW50IHRvIHNwb25zb3IgdGhpcy4N Cj4gPiA+DQo+ID4NCj4gPiBZZXMsIGl0J3Mgc3RpbGwgYSB3b3J0aHkgcHJvamVjdC4gSSdkIGJl IGhhcHB5IHRvIHNwb25zb3IuDQo+IA0KPiBEbyB5b3UgbWVhbiAibWVudG9yIj8NCg0KWWVzLCB3 aGF0ZXZlciB0aGUgYXBwcm9wcmlhdGUgdGVybSBpcy4NCg0KPiANCj4gQ2FuIHlvdSB1cGRhdGUg aHRlIHByb2plY3Qgb24gdGhlIHdpa2kgcGxlYXNlLg0KPiANCg0KU3VyZS4NCg0KICBQYXVsDQoN Cj4gSWFuLg0KPiANCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhl bnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4v bGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002it-Mc; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3jo-0005bU-Eg for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:46:08 +0000 Received: from [193.109.254.147:26381] by server-7.bemta-14.messagelabs.com id 07/A0-23424-BAE42F25; Wed, 05 Feb 2014 14:46:03 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1391611561!2223046!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20156 invoked from network); 5 Feb 2014 14:46:03 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:46:03 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="98224477" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Feb 2014 14:46:01 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:46:00 -0500 Message-ID: <1391611558.23098.2.camel@kazak.uk.xensource.com> From: Ian Campbell To: Andrew Cooper Date: Wed, 5 Feb 2014 14:45:58 +0000 In-Reply-To: <52F24D4D.7040004@citrix.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <52F24D4D.7040004@citrix.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Konrad Rzeszutek Wilk , Dario Faggioli , Ian Jackson , Paul Durrant , Santosh Jodh , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote: > On 05/02/14 14:09, Ian Campbell wrote: > > > > Andy: > > > > * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA > > allocations > > > > Sounds too hard for a GSoC to me. Would need fleshing out in any > > case. > > Malcolm made a prototype for this on the first day of the Hackathon. It > can disappear. Removed. > > * CPU/RAM/PCI diagram tool > > > > Does this not already exist somewhere? > > Not as far as I (or my ability to google) am aware. > > My furrowing into hwloc interacting with Xen and libxc is a start to all > of this, but it is still very much in my copious free time and there is > more than enough other work which could be done if someone were interested. OK, left in place. This could conceivably be done under another umbrella such as the Linux one too, since it seems generic. Ian. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002j3-QL; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBMvu-0002Se-RI for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 11:15:51 +0000 Received: from [85.158.143.35:35776] by server-3.bemta-4.messagelabs.com id 60/5B-11539-6EE63F25; Thu, 06 Feb 2014 11:15:50 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1391685341!3571066!1 X-Originating-IP: [74.125.82.169] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14664 invoked from network); 6 Feb 2014 11:15:44 -0000 Received: from mail-we0-f169.google.com (HELO mail-we0-f169.google.com) (74.125.82.169) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 11:15:44 -0000 Received: by mail-we0-f169.google.com with SMTP id t61so1199184wes.0 for ; Thu, 06 Feb 2014 03:15:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tWfx+hLlkvxWNgFPg9BXDw3USJ/gmN2xeV97+hLEYc8=; b=ZPdXleKA3TLfRZoqyL4wZgL/QYOCnA3f1ZiGatPpxDwT6/lJiAQPpkpOMQxFjT3FLH woO5+21KB/3It78R+5tCaAJhBP2NTcfwurDvDZbBvAC0t7yv7sgtA6SdytjnsvVFSu/k G1gl+Ir9nxfzm6LZtLIwT6NghoKQzu8iVbtpXmQYgUL0W/YjTbc8u+KAJYZfH1MgC9sj idDUzYXmkzeKYPdvteL7wDthnPjTMjLpc9/UGzbnJsLRYUfnkkpMJat2KxWHWcwXS5zg ONSXrkEbiJqdx+fR6QTaW0NF8Hk0U9Pnk0JnhGaQ5k8Zj7Gxga2bvmGNjD7RKSRxhZ4A K43w== MIME-Version: 1.0 X-Received: by 10.180.185.197 with SMTP id fe5mr20783079wic.56.1391685341063; Thu, 06 Feb 2014 03:15:41 -0800 (PST) Received: by 10.194.75.163 with HTTP; Thu, 6 Feb 2014 03:15:40 -0800 (PST) In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> Date: Thu, 6 Feb 2014 11:15:40 +0000 X-Google-Sender-Auth: zbmLP1_IZa_gNqVy2VQhCv5jGkQ Message-ID: From: George Dunlap To: Ian Campbell X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Konrad Rzeszutek Wilk , Andrew Cooper , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , Santosh Jodh , "xen-api@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, Feb 5, 2014 at 2:09 PM, Ian Campbell wrote: > George: > > * Introducing PowerClamp-like driver for Xen > > I don't think this has been done? Not that I'm aware of. > George: > > * Allowing guests to boot with a passed-through GPU as the primary > display > > This seems like a bit of a rathole for a GSoC student to me... Possibly. I thought it might be a bit more attractive project, but maybe that's a bad thing... > * Advanced Scheduling Parameters > > Still to do? Yes. -George _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iK-8Z; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3AA-0002Ts-Ac for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:09:14 +0000 Received: from [193.109.254.147:9910] by server-13.bemta-14.messagelabs.com id A2/4B-01226-90642F25; Wed, 05 Feb 2014 14:09:13 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1391609351!2187672!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12969 invoked from network); 5 Feb 2014 14:09:12 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:09:12 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="98207648" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Feb 2014 14:09:10 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:09:10 -0500 Message-ID: <1391609348.6497.178.camel@kazak.uk.xensource.com> From: Ian Campbell To: , Roger Pau Monne , "Dario Faggioli" , Konrad Rzeszutek Wilk , Ben Guthro , "Andrew Cooper" , Paul Durrant , Santosh Jodh , Ian Jackson Date: Wed, 5 Feb 2014 14:09:08 +0000 In-Reply-To: <52E7B6AF.3050604@xen.org> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gVHVlLCAyMDE0LTAxLTI4IGF0IDEzOjU0ICswMDAwLCBMYXJzIEt1cnRoIHdyb3RlOgo+IEhp IGFsbCwKPiBJIGhhdmUgbm90IGdvdHRlbiBhbnkgcmVwbHkgdG8gdGhpcyB0aHJlYWQuIEkgc2F3 IFdlaSBMdWkgYW5kIEFuZHLDqXMgCj4gTGFnYXItQ2F2aWxsYSBtYWtlIGNoYW5nZXMgdG8gdGhl IHByb2plY3QgbGlzdC4gUGxlYXNlIGdvIHRocm91Z2ggdGhlIAo+IGl0ZW1zIGJlbG93IGFuZCBt YWtlIGNoYW5nZXMgYXMgc3VnZ2VzdGVkLiBPdGhlcndpc2UsIG91ciBjaGFuY2VzIHRvIGdldCAK PiBpbnRvIEdTb0MgMjAxNCB3aWxsIGJlIHJlbGF0aXZlbHkgc2xpbS4KCkdvaW5nIHRocm91Z2gg dGhlIGxpc3QsIHBlb3BsZSBsaXN0ZWQgYXMgdGVjaG5pY2FsIGNvbnRhY3RzIGZvciBwcm9qZWN0 cwp3aXRoIEdTb0MgPT0geWVzIChvciB1bmtub3duKSBhcmUgaW4gdGhlIFRvIGxpbmUuIFBsZWFz ZSByZWl0ZXJhdGUgeW91cgppbnRlcmVzdCBpbiBtZW50b3JpbmcgdGhlIHByb2plY3QocykgYW5k IHVwZGF0ZSBvciByZW1vdmUgdGhlIGVudHJ5IGFzCm5lY2Vzc2FyeS4KCkkgc2tpcHBlZCB0aGlu Z3MgYWRkZWQgcmVjZW50bHkgYW5kIEkgc2tpcHBlZCAiWGVuIENsb3VkIFBsYXRmb3JtIChYQ1Ap CmFuZCBYQVBJIHByb2plY3RzIiwgc29tZW9uZSBlbHNlIGNhbiBwaWNrIHRoYXQgdXAuCgpBbmQg dG8gcmVpdGVyYXRlIHdoYXQgTGFycyBzYWlkOgoKPiBBZGQgbmV3IHdvcmsgaXRlbXMgOiB3ZSBv dWdodCB0byBoYXZlIGEgZmV3IHNleHkgdG9waWNzIG9uIHNheSAKPiBSZWFsLXRpbWUsIG1vYmls ZSBhbmQgc29tZSBvZiB0aGUgb3RoZXIgc2VnbWVudHMgKGFzc3VtaW5nIHdlIGNhbiBnZXQKPiBI VykKWy4uLl0KPiBiKSBBbnlvbmUgd2hvIGhhcyBzb21lIGtlcm5lbC9saW51eC9ic2QvZGlzdHJv L3FlbXUgd29yay1pdGVtcywgc2hvdWxkIAo+IGdldCB0aGVzZSBsaXN0ZWQgb24gdGhlIHJlc3Bl Y3RpdmUgb3RoZXIgcHJvZ3JhbXMuIEFuZCB3ZSBzaG91bGQgbGluayAKPiB0byB0aGVzZSBmcm9t IG91ciBwcm9qZWN0IHBhZ2UuCgpUaGUgbGlzdDoKClBhc2k6CiAgICAgICogSW1wbGVtZW50IFhl biBQVlNDU0kgc3VwcG9ydCBpbiB4bC9saWJ4bCB0b29sc3RhY2sKICAgICAgKiBJbXBsZW1lbnQg WGVuIFBWVVNCIHN1cHBvcnQgaW4geGwvbGlieGwgdG9vbHN0YWNrCgogICAgICAgIEJvdGggaGF2 ZSB1bmFuc3dlcmVkIHF1ZXN0aW9ucyBwb3NlZCBieSBMYXJzIGluIEphbnVhcnkgMjAxMy4KICAg ICAgICAKS29ucmFkOgogICAgICAqIEJsb2NrIGJhY2tlbmQvZnJvbnRlbmQgaW1wcm92ZW1lbnRz CgogICAgICAgIEkgc3VzcGVjdCBhIGJ1bmNoIG9mIHRoZXNlIGFyZSBkb25lPyAoQWxzbyBDQyBS b2dlciwgd2hvIG1heQogICAgICAgIGhhdmUgZG9uZSB0aGVtLi4uKQogICAgICAgIAogICAgICAg IFdhcyBpbiB0aGUgbGlzdCB0d2ljZSwgdGhleSBsb29rZWQgaWRlbnRpY2FsIHNvIEkgbnVrZWQg b25lLgogICAgICAgIAogICAgICAqIFV0aWxpemUgSW50ZWwgUXVpY2tQYXRoIG9uIG5ldHdvcmsg YW5kIGJsb2NrIHBhdGguCgogICAgICAgIE5vIGNvbW1lbnRzIGV0YywgYnV0IHNvdW5kcyBhZHZh bmNlZCBmb3IgYSBHU29DIHN0dWRlbnQsIHBsdXMKICAgICAgICBpdHMgdW5jbGVhciB3aGVuIHN1 Y2ggaGFyZHdhcmUgYmVjYW1lIGF2YWlsYWJsZSwgYXJlIHRoZXkgbGlrZWx5CiAgICAgICAgdG8g aGF2ZSBpdD8gSXQgc291bmRzIGxpa2UgaXQgbWlnaHQgYWxzbyBiZSBxdWl0ZSBoaWdoIGVuZC4K ICAgICAgICAKICAgICAgKiBwZXJmIHdvcmtpbmcgd2l0aCBYZW4KCiAgICAgICAgRG9uZS9pbiBw cm9ncmVzcyBieSBCb3JpcyBJIHRoaW5rCiAgICAgICAgCiAgICAgICogUEFUIHdyaXRlY29tYmlu ZSBmaXh1cAoKICAgICAgICBEaWQgSSBzZWUgYSBmaXggZm9yIHRoaXMgZ28gcGFzdD8gR1NvQyA9 PSB1bmtub3duPwogICAgICAgIAogICAgICAqIFBhcmFsbGVsIHhlbndhdGNoCgogICAgICAgIEJp dCBzcGFyc2Ugb24gZGV0YWlscywgR1NPQyA9PSB1bmtub3duCgogICAgICAqIE1pY3JvY29kZSB1 cGxvYWRlciBpbXBsZW1lbnRhdGlvbgogICAgICAgIAogICAgICAgIERvbmUgSSB0aGluaz8KCiAg ICAgICogSW50ZWdyYXRpbmcgTlVNQSBhbmQgVG1lbQogICAgICAgIAogICAgICAgIExpc3RzIERh biBhcyBjby1tYWludGFpbmVyIC0tIEtvbnJhZCBkbyB5b3Ugd2FudCB0byBwcm9wb3NlIHRoaXMK ICAgICAgICB0byB0aGUgbmV3IHRtZW0gZ3V5IChJJ3ZlIGZvcmdvdHRlbiBoaXMgbmFtZSkKICAg ICAgICAKICAgICAgKiBQZXJmb3JtYW5jZSB0b29scyBvdmVyaGF1bAoKICAgICAgICBCaXQgdmFn dWUuIEFuZCBoYXMgc29tZSBvZiB0aGlzIGJlZW4gZG9uZT8KCiAgICAgICogIlVwc3RyZWFtIGJ1 Z3MiCgogICAgICAgIFRoZXJlIHdlcmUgNCBvZiB0aGVzZSwgZGF0aW5nIGJhY2sgdG8gMjAxMiwg SSBkb24ndCB0aGluayB0aGlzCiAgICAgICAgbGlzdCBpcyBhIGdvb2QgcGxhY2UgdG8gdHJhY2sg YnVncyBhbmQgaXQgc2VlbXMgbGlrZSBhdCBsZWFzdAogICAgICAgIHNvbWUgb2YgdGhlbSBhcmUg bm93IG9ic29sZXRlLiBTbyBJJ3ZlIG51a2VkIHRoZSBsb3QuIElmIHRoZXkKICAgICAgICBhcmUg c3RpbGwgcmVsZXZhbnQgSSB0aGluayBpdCB3b3VsZCBiZSBiZXN0IHRvIGdldCB0aGVtIGludG8g dGhlCiAgICAgICAgYnVnIHRyYWNrZXIuCiAgICAgICAgCkJlbjoKICAgICAgKiBkb20wIGtnZGIg c3VwcG9ydAoKICAgICAgICBJcyB0aGlzIGZvciBHU29DPwoKR2VvcmdlOgoKICAgICAgKiBJbnRy b2R1Y2luZyBQb3dlckNsYW1wLWxpa2UgZHJpdmVyIGZvciBYZW4KCiAgICAgICAgSSBkb24ndCB0 aGluayB0aGlzIGhhcyBiZWVuIGRvbmU/CgpEYXJpbzoKICAgICAgKiBOVU1BIGVmZmVjdHMgb24g aW50ZXItVk0gY29tbXVuaWNhdGlvbiBhbmQgb24gbXVsdGktVk0gd29ya2xvYWRzCgogICAgICAg IEkgdGhpbmsgdGhpcyB3YXMgdW5kZXIgd2F5IGFzIHBhcnQgb2YgdGhlIEdOT01FIE91dHJlYWNo CiAgICAgICAgcHJvZ3JhbS4gSW4gdGhhdCBjYXNlIHBlcmhhcHMgaXQgbmVlZHMgdXBkYXRpbmcg dG8gcmVmbGVjdCB3aGF0CiAgICAgICAgaGFzIGJlZW4gZG9uZSBhbmQgd2hhdCBzdGlsbCBuZWVk cyB0byBiZSBkb25lPwogICAgICAgIAogICAgICAqIEludGVncmF0aW5nIE5VTUEgYW5kIFRtZW0K CiAgICAgICAgTGlzdHMgRGFuIGFzIGNvLW1haW50YWluZXIgLS0gY292ZXJlZCB1bmRlciBLb25y YWQncyBuYW1lIGFib3ZlLgogICAgICAgIAogICAgICAqIElzIFhlbiByZWFkeSBmb3IgdGhlIFJl YWwtVGltZS9FbWJlZGRlZCBXb3JsZD8KICAgICAgICAgICAgICAgIAogICAgICAgIFNvdW5kcyBh IGJpdCBibHVlIHNreT8gTm93IHRoYXQgdGhlcmUgaXMgYWN0aXZlIGludGVyZXN0IGluIHRoaXMK ICAgICAgICBvbiBBUk0gcGVyaGFwcyBhIGZldyBjb25jcmV0ZSBwcm9qZWN0cyBjb3VsZCBiZSBw cm9wb3NlZCB0bwogICAgICAgIHJlcGxhY2UgaXQ/CgpBbmR5OgoKICAgICAgKiBJT01NVSBjb250 cm9sIGZvciBTV0lPVExCLCB0byBhdm9pZCBkb20wIGNvcHkgb2YgYWxsID40SyBETUEKICAgICAg ICBhbGxvY2F0aW9ucwoKICAgICAgICBTb3VuZHMgdG9vIGhhcmQgZm9yIGEgR1NvQyB0byBtZS4g V291bGQgbmVlZCBmbGVzaGluZyBvdXQgaW4gYW55CiAgICAgICAgY2FzZS4KICAgICAgICAKICAg ICAgKiBDUFUvUkFNL1BDSSBkaWFncmFtIHRvb2wKCiAgICAgICAgRG9lcyB0aGlzIG5vdCBhbHJl YWR5IGV4aXN0IHNvbWV3aGVyZT8KICAgICAgICAKUGF1bDoKCiAgICAgICogSFZNIHBlci1ldmVu dC1jaGFubmVsIGludGVycnVwdHMKCiAgICAgICAgTWlnaHQgYmUgZWFzaWVyIG5vdyB0aGF0IFdp bmRvd3MgUFYgZHJpdmVycyBhcmUgb3BlbmVkIHVwPwoKUm9nZXI6CiAgICAgICogUmVmYWN0b3Ig TGludXggaG90cGx1ZyBzY3JpcHRzCgogICAgICAgIFlvdSBkaWQgc29tZSBvZiB0aGlzIEkgdGhp bms/CiAgICAgICAgCklhbiBDOgoKICAgICAgKiBYTCB0byBYQ1AgVk0gbW90aW9uCgogICAgICAg IFBlcmhhcHMgdGhpcyBjb3VsZCBiZSBicm9hZGVuZWQgaW50byBWTSB0cmFuc3BvcnQgYmV0d2Vl biBYTCBhbmQKICAgICAgICBvdGhlciB0aGluZ3MgdG9vIC0tIGUuZy4gbGlidmlydD8KClN0ZWZh bm86CgogICAgICAqIFZNIFNuYXBzaG90cwoKICAgICAgICBTdGlsbCBhIGdvb2QgcHJvamVjdCBJ IHRoaW5rCiAgICAgICAgCkdlb3JnZToKCiAgICAgICogQWxsb3dpbmcgZ3Vlc3RzIHRvIGJvb3Qg d2l0aCBhIHBhc3NlZC10aHJvdWdoIEdQVSBhcyB0aGUgcHJpbWFyeQogICAgICAgIGRpc3BsYXkK CiAgICAgICAgVGhpcyBzZWVtcyBsaWtlIGEgYml0IG9mIGEgcmF0aG9sZSBmb3IgYSBHU29DIHN0 dWRlbnQgdG8gbWUuLi4KICAgICAgICAKICAgICAgKiBBZHZhbmNlZCBTY2hlZHVsaW5nIFBhcmFt ZXRlcnMKICAgICAgICAKICAgICAgICBTdGlsbCB0byBkbz8KClNhbnRvc2g6CgogICAgICAqIEtE RCAoV2luZG93cyBEZWJ1Z2dlciBTdHViKSBlbmhhbmNlbWVudHMKICAgICAgICAKRGF2ZQoKICAg ICAgKiBDcmVhdGUgYSB0aW55IFZNIGZvciBlYXN5IGxvYWQgdGVzdGluZwoKICAgICAgICBTb21l b25lIHdhcyBsb29raW5nIGF0IHRoaXMgSSB0aGluaz8KICAgICAgICAKSWFuIEo6CgogICAgICAq IFRlc3RpbmcgUFYgYW5kIEhWTSBpbnN0YWxscyBvZiBEZWJpYW4gdXNpbmcgZGViaWFuLWluc3Rh bGxlcgogICAgICAqIFRlc3RpbmcgTmV0QlNECgogICAgICAgIEJTRCBpcyBkb25lIEkgdGhpbmss IGFuZCBJJ20gbG9va2luZyBhdCBEZWJpYW4gSW5zdGFsbGVyIHN0dWZmCiAgICAgICAgbXlzZWxm LiBJJ3ZlIHJlbW92ZWQgdGhlc2UuCgoKUGhldyEKSWFuLgoKCgo+IExhcnMKPiAKPiBPbiAyMC8w MS8yMDE0IDA5OjE4LCBMYXJzIEt1cnRoIHdyb3RlOgo+ID4gSGkgYWxsLAo+ID4KPiA+IHRoZSBH U29DIGFwcGxpY2F0aW9uIGRlYWRsaW5lIGlzIGNvbWluZyB1cCA6IEZlYiAyMDE0LiBJZiB3ZSB3 YW50IHRvIAo+ID4gaGF2ZSBhbnkgY2hhbmNlIG9mIGdldHRpbmcgYWNjZXB0ZWQgdGhpcyB5ZWFy LCB3ZSBvdWdodCB0byBnZXQgb3VyIAo+ID4gcHJvamVjdCBsaXN0IGludG8gZ29vZCBzaGFwZS4g VGhlIHByb2plY3QgbGlzdCBhbmQgaG93IHRoZSBwcm9qZWN0IGFuZCAKPiA+IG1lbnRlcnMgcHJl c2VudCB0aGVtc2VsdmVzIGhhcyBhIGJpZ2dlciBpbXBhY3Qgb24gd2hldGhlciB3ZSBnZXQgCj4g PiBhY2NlcHRlZCB0aGFuIHRoZSBhY3R1YWwgYXBwbGljYXRpb24uCj4gPgo+ID4gQWxzbywgSSB3 b3VsZCBsaWtlIHRvIGFkZCBhIG1lbnRvciBzZWN0aW9uIHRoaXMgeWVhcjogYSBzaG9ydCBiaW8s IAo+ID4gd2hhdCB0aGUgbWVudG9yIGNhcmVzIGFib3V0IGFuZCBhIHBpY3R1cmUuIFRoaXMgd2ls bCBoZWxwIG1ha2UgdGhlIAo+ID4gcHJvamVjdCBsaXN0IG1vcmUgcmVhbC4KPiA+Cj4gPiBXZSBo YXZlICo0IHdlZWtzKiB0byBkbyB0aGlzLiBUaGUgYmFyIGZvciBHU29DIGhhcyBiZWVuIGdldHRp bmcgCj4gPiBpbmNyZWFzaW5nbHkgaGlnaC4gSSBrbm93LCB3ZSBhcmUgdGllZCBkb3duIHdpdGgg WGVuIDQuNCwgYnV0IHRoaXMgaXMgCj4gPiBzb21ldGhpbmcgeW91IG5lZWQgdG8gZG8gaWYgeW91 IHdhbnQgdGhlIFhlbiBQcm9qZWN0IHRvIHBhcnRpY2lwYXRlLgo+ID4KPiA+IGEpIFBsZWFzZSwg dXBkYXRlIAo+ID4gaHR0cDovL3dpa2kueGVucHJvamVjdC5vcmcvd2lraS9YZW5fRGV2ZWxvcG1l bnRfUHJvamVjdHMgdXJnZW50bHkgCj4gPiAodGhlc2UgbmVlZCB0byBiZSBpbiBnb29kIHNoYXBl ICpiZWZvcmUqIHRoZSBhcHBsaWNhdGlvbikuIFdoYXQgSSBuZWVkIAo+ID4geW91IHRvIGRvIGlz Ogo+ID4gYS4xKSBSZW1vdmUgaXRlbXMgdGhhdCBhcmUgZG9uZQo+ID4gYS4yKSBBZGQgbmV3IHdv cmsgaXRlbXMgOiB3ZSBvdWdodCB0byBoYXZlIGEgZmV3IHNleHkgdG9waWNzIG9uIHNheSAKPiA+ IFJlYWwtdGltZSwgbW9iaWxlIGFuZCBzb21lIG9mIHRoZSBvdGhlciBzZWdtZW50cyAoYXNzdW1p bmcgd2UgY2FuIGdldCBIVykKPiA+IGEuMykgQWxsIHByb2plY3QgcHJvcG9zYWxzIG5lZWQgdG8g YmUgcGVlciByZXZpZXdlZCAqYW5kKiBjbGVhciAuLi4gCj4gPiBUaGUgcGVlciByZXZpZXcgcHJv Y2VzcyBmb3IgcHJvamVjdHMgd2UgcHV0IGluIHBsYWNlIGxhc3QgeWVhciB3b3JrZWQgCj4gPiB3 ZWxsLCBieSB3aGljaCB3ZSBoYWQgcGFzdCBtZW50b3JzIHNpZ24gb2YgcHJvamVjdCBwcm9wb3Nh bHMgdGhhdCB3ZXJlIAo+ID4gaW4gZ29vZCBlbm91Z2ggc3RhdGUuCj4gPgo+ID4gYikgQW55b25l IHdobyBoYXMgc29tZSBrZXJuZWwvbGludXgvYnNkL2Rpc3Ryby9xZW11IHdvcmstaXRlbXMsIHNo b3VsZCAKPiA+IGdldCB0aGVzZSBsaXN0ZWQgb24gdGhlIHJlc3BlY3RpdmUgb3RoZXIgcHJvZ3Jh bXMuIEFuZCB3ZSBzaG91bGQgbGluayAKPiA+IHRvIHRoZXNlIGZyb20gb3VyIHByb2plY3QgcGFn ZS4KPiA+Cj4gPiBCZXN0IFJlZ2FyZHMKPiA+IExhcnMKPiA+IFAuUy46IEkgd2lsbCBhbHNvIHNl ZSB3aGV0aGVyIHdlIGNhbiBwYXJ0aWNpcGF0ZSBhcyBYZW4gUHJvamVjdCB1bmRlciAKPiA+IHRo ZSBMRiBHU29DIHByb2dyYW0sIGJ1dCBsYXN0IHllYXIgdGhlcmUgd2FzIHB1c2gtYmFjayBhbmQg SSBkb24ndCAKPiA+IGV4cGVjdCB0aGlzIHRvIGNoYW5nZQo+ID4KPiAKPiAKPiBfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1kZXZlbCBtYWlsaW5n IGxpc3QKPiBYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwo+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hl bi1kZXZlbAoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJv amVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0 aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iP-At; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3JM-00030u-4r for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:18:44 +0000 Received: from [85.158.143.35:15847] by server-2.bemta-4.messagelabs.com id 04/F0-10891-34842F25; Wed, 05 Feb 2014 14:18:43 +0000 X-Env-Sender: Ben.Guthro@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1391609921!3355349!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31880 invoked from network); 5 Feb 2014 14:18:42 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:18:42 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="100103481" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Feb 2014 14:18:41 +0000 Received: from FTLPEX01CL01.citrite.net ([169.254.4.32]) by FTLPEX01CL03.citrite.net ([169.254.1.150]) with mapi id 14.02.0342.004; Wed, 5 Feb 2014 09:18:40 -0500 From: Ben Guthro To: Ian Campbell , "lars.kurth@xen.org" , Roger Pau Monne , Dario Faggioli , Konrad Rzeszutek Wilk , Andrew Cooper , Paul Durrant , Santosh Jodh , "Ian Jackson" Thread-Topic: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Thread-Index: AQHPInvXBCUk6V9UM0G88s1y0zm8RZqmsyeN Date: Wed, 5 Feb 2014 14:18:40 +0000 Message-ID: References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org>, <1391609348.6497.178.camel@kazak.uk.xensource.com> In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.154.239] MIME-Version: 1.0 X-DLP: MIA1 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org ________________________________________ From: Ian Campbell Sent: Wednesday, February 05, 2014 9:09 AM To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 > Ben: > * dom0 kgdb support > > Is this for GSoC? This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here. That said, Fri is my last day working for Citrix (and consequently, on Xen) - and I'll be moving on to a Start-up company again, so someone else would need to sponsor this project. Naturally, I'll be available via my Non-Citrix email address (ben@guthro.net) Ben _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002ij-Ip; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3ed-0004yB-9b for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:40:43 +0000 Received: from [85.158.139.211:48402] by server-9.bemta-5.messagelabs.com id 66/76-11237-A6D42F25; Wed, 05 Feb 2014 14:40:42 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1391611240!1867900!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11462 invoked from network); 5 Feb 2014 14:40:41 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:40:41 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="100113523" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Feb 2014 14:40:14 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:40:13 -0500 Received: from andrewcoop.uk.xensource.com ([10.80.2.18]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1WB3e9-0006vT-OJ; Wed, 05 Feb 2014 14:40:13 +0000 Message-ID: <52F24D4D.7040004@citrix.com> Date: Wed, 5 Feb 2014 14:40:13 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: Ian Campbell References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> X-Enigmail-Version: 1.6 X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Konrad Rzeszutek Wilk , Dario Faggioli , Ian Jackson , Paul Durrant , Santosh Jodh , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 05/02/14 14:09, Ian Campbell wrote: > > Andy: > > * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA > allocations > > Sounds too hard for a GSoC to me. Would need fleshing out in any > case. Malcolm made a prototype for this on the first day of the Hackathon. It can disappear. > > * CPU/RAM/PCI diagram tool > > Does this not already exist somewhere? Not as far as I (or my ability to google) am aware. My furrowing into hwloc interacting with Xen and libxc is a start to all of this, but it is still very much in my copious free time and there is more than enough other work which could be done if someone were interested. ~Andrew _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iP-At; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3JM-00030u-4r for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:18:44 +0000 Received: from [85.158.143.35:15847] by server-2.bemta-4.messagelabs.com id 04/F0-10891-34842F25; Wed, 05 Feb 2014 14:18:43 +0000 X-Env-Sender: Ben.Guthro@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1391609921!3355349!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31880 invoked from network); 5 Feb 2014 14:18:42 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:18:42 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="100103481" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Feb 2014 14:18:41 +0000 Received: from FTLPEX01CL01.citrite.net ([169.254.4.32]) by FTLPEX01CL03.citrite.net ([169.254.1.150]) with mapi id 14.02.0342.004; Wed, 5 Feb 2014 09:18:40 -0500 From: Ben Guthro To: Ian Campbell , "lars.kurth@xen.org" , Roger Pau Monne , Dario Faggioli , Konrad Rzeszutek Wilk , Andrew Cooper , Paul Durrant , Santosh Jodh , "Ian Jackson" Thread-Topic: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Thread-Index: AQHPInvXBCUk6V9UM0G88s1y0zm8RZqmsyeN Date: Wed, 5 Feb 2014 14:18:40 +0000 Message-ID: References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org>, <1391609348.6497.178.camel@kazak.uk.xensource.com> In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.154.239] MIME-Version: 1.0 X-DLP: MIA1 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org ________________________________________ From: Ian Campbell Sent: Wednesday, February 05, 2014 9:09 AM To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 > Ben: > * dom0 kgdb support > > Is this for GSoC? This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here. That said, Fri is my last day working for Citrix (and consequently, on Xen) - and I'll be moving on to a Start-up company again, so someone else would need to sponsor this project. Naturally, I'll be available via my Non-Citrix email address (ben@guthro.net) Ben _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iU-Ch; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3Ty-0003jm-VJ for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:29:43 +0000 Received: from [85.158.143.35:31969] by server-3.bemta-4.messagelabs.com id 1F/A7-11539-6DA42F25; Wed, 05 Feb 2014 14:29:42 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1391610580!3359190!1 X-Originating-IP: [156.151.31.81] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU2LjE1MS4zMS44MSA9PiAyODgzMzk=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8287 invoked from network); 5 Feb 2014 14:29:41 -0000 Received: from userp1040.oracle.com (HELO userp1040.oracle.com) (156.151.31.81) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Feb 2014 14:29:41 -0000 Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s15ETZ0w031233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Feb 2014 14:29:36 GMT Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s15ETYNJ029718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Feb 2014 14:29:34 GMT Received: from abhmp0008.oracle.com (abhmp0008.oracle.com [141.146.116.14]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s15ETYpI029712; Wed, 5 Feb 2014 14:29:34 GMT Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 05 Feb 2014 06:29:33 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 66A531C0972; Wed, 5 Feb 2014 09:29:32 -0500 (EST) Date: Wed, 5 Feb 2014 09:29:32 -0500 From: Konrad Rzeszutek Wilk To: Ben Guthro Message-ID: <20140205142932.GA3946@phenom.dumpdata.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ian Campbell , Andrew Cooper , Dario Faggioli , "xen-devel@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , Santosh Jodh , Ian Jackson , "xen-api@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, Feb 05, 2014 at 02:18:40PM +0000, Ben Guthro wrote: > > ________________________________________ > From: Ian Campbell > Sent: Wednesday, February 05, 2014 9:09 AM > To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson > Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org > Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 > > > > Ben: > > * dom0 kgdb support > > > > Is this for GSoC? > > This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here. And it actually works! > > That said, Fri is my last day working for Citrix (and consequently, on Xen) - and I'll be moving on to a Start-up company again, so someone else would need to sponsor this project. > > Naturally, I'll be available via my Non-Citrix email address (ben@guthro.net) > > > Ben _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5n-0002jn-3u; Thu, 06 Feb 2014 17:50:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBT35-0002Vx-ND for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 17:47:39 +0000 Received: from [85.158.137.68:28028] by server-3.bemta-3.messagelabs.com id 17/A4-14520-ABAC3F25; Thu, 06 Feb 2014 17:47:38 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1391708856!140730!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29538 invoked from network); 6 Feb 2014 17:47:38 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 17:47:38 -0000 X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="98665806" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 06 Feb 2014 17:47:35 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server (TLS) id 14.2.342.4; Thu, 6 Feb 2014 12:47:35 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.176]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Thu, 6 Feb 2014 18:47:33 +0100 From: Paul Durrant To: Ian Campbell Thread-Topic: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Thread-Index: AQHPInvYpj3b21EIS0q8f9DE1KOLi5qoX58AgAAhFQD//++gAIAAEZ5w Date: Thu, 6 Feb 2014 17:47:32 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD022712E@AMSPEX01CL01.citrite.net> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD02270E9@AMSPEX01CL01.citrite.net> <1391708646.2162.12.camel@kazak.uk.xensource.com> In-Reply-To: <1391708646.2162.12.camel@kazak.uk.xensource.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.2.29] MIME-Version: 1.0 X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Konrad Rzeszutek Wilk , Andrew Cooper , Dario Faggioli , Ben Guthro , Santosh Jodh , "xen-api@lists.xen.org" , Ian Jackson , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBJYW4gQ2FtcGJlbGwNCj4gU2Vu dDogMDYgRmVicnVhcnkgMjAxNCAxNzo0NA0KPiBUbzogUGF1bCBEdXJyYW50DQo+IENjOiBTYW50 b3NoIEpvZGg7IGxhcnMua3VydGhAeGVuLm9yZzsgUm9nZXIgUGF1IE1vbm5lOyBEYXJpbyBGYWdn aW9saTsNCj4gS29ucmFkIFJ6ZXN6dXRlayBXaWxrOyBCZW4gR3V0aHJvOyBBbmRyZXcgQ29vcGVy OyBJYW4gSmFja3NvbjsgeGVuLQ0KPiBkZXZlbEBsaXN0cy54ZW4ub3JnOyB4ZW4tYXBpQGxpc3Rz Lnhlbi5vcmc7IG1pcmFnZW9zLQ0KPiBkZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZw0KPiBTdWJq ZWN0OiBSZTogW1hlbi1kZXZlbF0gUHJlcHBpbmcgZm9yIEdTT0MgMjAxNCBbVVJHRU5UXSAtIGRl YWRsaW5lIEZlYiAxNA0KPiAyMDE0DQo+IA0KPiBPbiBUaHUsIDIwMTQtMDItMDYgYXQgMTc6NDMg KzAwMDAsIFBhdWwgRHVycmFudCB3cm90ZToNCj4gPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t LS0tDQo+ID4gPiBGcm9tOiBTYW50b3NoIEpvZGgNCj4gPiA+IFNlbnQ6IDA2IEZlYnJ1YXJ5IDIw MTQgMTY6NDQNCj4gPiA+IFRvOiBJYW4gQ2FtcGJlbGw7IGxhcnMua3VydGhAeGVuLm9yZzsgUm9n ZXIgUGF1IE1vbm5lOyBEYXJpbyBGYWdnaW9saTsNCj4gPiA+IEtvbnJhZCBSemVzenV0ZWsgV2ls azsgQmVuIEd1dGhybzsgQW5kcmV3IENvb3BlcjsgUGF1bCBEdXJyYW50OyBJYW4NCj4gPiA+IEph Y2tzb24NCj4gPiA+IENjOiB4ZW4tZGV2ZWxAbGlzdHMueGVuLm9yZzsgeGVuLWFwaUBsaXN0cy54 ZW4ub3JnOyBtaXJhZ2Vvcy0NCj4gPiA+IGRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnDQo+ID4g PiBTdWJqZWN0OiBSRTogW1hlbi1kZXZlbF0gUHJlcHBpbmcgZm9yIEdTT0MgMjAxNCBbVVJHRU5U XSAtIGRlYWRsaW5lDQo+IEZlYiAxNA0KPiA+ID4gMjAxNA0KPiA+ID4NCj4gPiA+ID4NCj4gPiA+ ID4gU2FudG9zaDoNCj4gPiA+ID4NCj4gPiA+ID4gICAgICAgKiBLREQgKFdpbmRvd3MgRGVidWdn ZXIgU3R1YikgZW5oYW5jZW1lbnRzDQo+ID4gPiA+DQo+ID4gPiBbU2FudG9zaCBKb2RoXSBJIGJl bGlldmUgdGhpcyBpcyBzdGlsbCBhIGdvb2QgR1NPQyBwcm9qZWN0LiBIb3dldmVyLCBpbiBsaWdo dA0KPiBvZg0KPiA+ID4gbXkgbmV3IGRpcmVjdGlvbiwgSSBhbSBub3Qgc3VyZSBpZiBJIHdpbGwg YmUgYWJsZSB0byBtZW50b3IuIERvbuKAmXQga25vdyBpZg0KPiBQYXVsDQo+ID4gPiBvciBzb21l b25lIGVsc2Ugb24gdGhlIFdpbmRvd3MgdGVhbSB3b3VsZCB3YW50IHRvIHNwb25zb3IgdGhpcy4N Cj4gPiA+DQo+ID4NCj4gPiBZZXMsIGl0J3Mgc3RpbGwgYSB3b3J0aHkgcHJvamVjdC4gSSdkIGJl IGhhcHB5IHRvIHNwb25zb3IuDQo+IA0KPiBEbyB5b3UgbWVhbiAibWVudG9yIj8NCg0KWWVzLCB3 aGF0ZXZlciB0aGUgYXBwcm9wcmlhdGUgdGVybSBpcy4NCg0KPiANCj4gQ2FuIHlvdSB1cGRhdGUg aHRlIHByb2plY3Qgb24gdGhlIHdpa2kgcGxlYXNlLg0KPiANCg0KU3VyZS4NCg0KICBQYXVsDQoN Cj4gSWFuLg0KPiANCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhl bnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4v bGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002jZ-VU; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBSyr-000290-HU for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 17:43:17 +0000 Received: from [85.158.143.35:9355] by server-2.bemta-4.messagelabs.com id 34/B6-10891-4B9C3F25; Thu, 06 Feb 2014 17:43:16 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1391708594!3717225!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15507 invoked from network); 6 Feb 2014 17:43:16 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 17:43:16 -0000 X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="98664209" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 06 Feb 2014 17:43:14 +0000 Received: from AMSPEX01CL03.citrite.net (10.69.46.34) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server (TLS) id 14.2.342.4; Thu, 6 Feb 2014 12:43:13 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.176]) by AMSPEX01CL03.citrite.net ([10.69.46.34]) with mapi id 14.02.0342.004; Thu, 6 Feb 2014 18:43:12 +0100 From: Paul Durrant To: Santosh Jodh , Ian Campbell , "lars.kurth@xen.org" , "Roger Pau Monne" , Dario Faggioli , Konrad Rzeszutek Wilk , Ben Guthro , Andrew Cooper , Ian Jackson Thread-Topic: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Thread-Index: AQHPInvYpj3b21EIS0q8f9DE1KOLi5qoX58AgAAhFQA= Date: Thu, 6 Feb 2014 17:43:11 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD02270E9@AMSPEX01CL01.citrite.net> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> In-Reply-To: <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.2.29] MIME-Version: 1.0 X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBTYW50b3NoIEpvZGgNCj4gU2Vu dDogMDYgRmVicnVhcnkgMjAxNCAxNjo0NA0KPiBUbzogSWFuIENhbXBiZWxsOyBsYXJzLmt1cnRo QHhlbi5vcmc7IFJvZ2VyIFBhdSBNb25uZTsgRGFyaW8gRmFnZ2lvbGk7DQo+IEtvbnJhZCBSemVz enV0ZWsgV2lsazsgQmVuIEd1dGhybzsgQW5kcmV3IENvb3BlcjsgUGF1bCBEdXJyYW50OyBJYW4N Cj4gSmFja3Nvbg0KPiBDYzogeGVuLWRldmVsQGxpc3RzLnhlbi5vcmc7IHhlbi1hcGlAbGlzdHMu eGVuLm9yZzsgbWlyYWdlb3MtDQo+IGRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnDQo+IFN1Ympl Y3Q6IFJFOiBbWGVuLWRldmVsXSBQcmVwcGluZyBmb3IgR1NPQyAyMDE0IFtVUkdFTlRdIC0gZGVh ZGxpbmUgRmViIDE0DQo+IDIwMTQNCj4gDQo+ID4NCj4gPiBTYW50b3NoOg0KPiA+DQo+ID4gICAg ICAgKiBLREQgKFdpbmRvd3MgRGVidWdnZXIgU3R1YikgZW5oYW5jZW1lbnRzDQo+ID4NCj4gW1Nh bnRvc2ggSm9kaF0gSSBiZWxpZXZlIHRoaXMgaXMgc3RpbGwgYSBnb29kIEdTT0MgcHJvamVjdC4g SG93ZXZlciwgaW4gbGlnaHQgb2YNCj4gbXkgbmV3IGRpcmVjdGlvbiwgSSBhbSBub3Qgc3VyZSBp ZiBJIHdpbGwgYmUgYWJsZSB0byBtZW50b3IuIERvbuKAmXQga25vdyBpZiBQYXVsDQo+IG9yIHNv bWVvbmUgZWxzZSBvbiB0aGUgV2luZG93cyB0ZWFtIHdvdWxkIHdhbnQgdG8gc3BvbnNvciB0aGlz Lg0KPiANCg0KWWVzLCBpdCdzIHN0aWxsIGEgd29ydGh5IHByb2plY3QuIEknZCBiZSBoYXBweSB0 byBzcG9uc29yLg0KDQogIFBhdWwNCg0KPiBSZWdhcmRzLA0KPiBTYW50b3NoDQpfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWls aW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3Rz LnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002ie-Gp; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3ZK-00043h-Fz for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:35:14 +0000 Received: from [85.158.137.68:15564] by server-15.bemta-3.messagelabs.com id B8/48-19263-12C42F25; Wed, 05 Feb 2014 14:35:13 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1391610911!12416611!1 X-Originating-IP: [156.151.31.81] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU2LjE1MS4zMS44MSA9PiAyODgzMzk=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10412 invoked from network); 5 Feb 2014 14:35:12 -0000 Received: from userp1040.oracle.com (HELO userp1040.oracle.com) (156.151.31.81) by server-10.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Feb 2014 14:35:12 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s15EY6n4004448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Feb 2014 14:34:06 GMT Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s15EY5Mu020127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 5 Feb 2014 14:34:06 GMT Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s15EY4NJ006146; Wed, 5 Feb 2014 14:34:05 GMT Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 05 Feb 2014 06:34:04 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 0BD121C0972; Wed, 5 Feb 2014 09:34:03 -0500 (EST) Date: Wed, 5 Feb 2014 09:34:02 -0500 From: Konrad Rzeszutek Wilk To: Ian Campbell Message-ID: <20140205143402.GB3946@phenom.dumpdata.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Andrew Cooper , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , Santosh Jodh , "xen-api@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, Feb 05, 2014 at 02:09:08PM +0000, Ian Campbell wrote: > On Tue, 2014-01-28 at 13:54 +0000, Lars Kurth wrote: > > Hi all, > > I have not gotten any reply to this thread. I saw Wei Lui and Andr=E9s = > > Lagar-Cavilla make changes to the project list. Please go through the = > > items below and make changes as suggested. Otherwise, our chances to ge= t = > > into GSoC 2014 will be relatively slim. > = > Going through the list, people listed as technical contacts for projects > with GSoC =3D=3D yes (or unknown) are in the To line. Please reiterate yo= ur > interest in mentoring the project(s) and update or remove the entry as > necessary. > = > I skipped things added recently and I skipped "Xen Cloud Platform (XCP) > and XAPI projects", someone else can pick that up. > = > And to reiterate what Lars said: > = > > Add new work items : we ought to have a few sexy topics on say = > > Real-time, mobile and some of the other segments (assuming we can get > > HW) > [...] > > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should = > > get these listed on the respective other programs. And we should link = > > to these from our project page. > = > The list: > = > Pasi: > * Implement Xen PVSCSI support in xl/libxl toolstack > * Implement Xen PVUSB support in xl/libxl toolstack > = > Both have unanswered questions posed by Lars in January 2013. > = > Konrad: > * Block backend/frontend improvements > = > I suspect a bunch of these are done? (Also CC Roger, who may > have done them...) > = > Was in the list twice, they looked identical so I nuked one. > = > * Utilize Intel QuickPath on network and block path. > = > No comments etc, but sounds advanced for a GSoC student, plus > its unclear when such hardware became available, are they likely > to have it? It sounds like it might also be quite high end. > = > * perf working with Xen > = > Done/in progress by Boris I think > = > * PAT writecombine fixup > = > Did I see a fix for this go past? GSoC =3D=3D unknown? No. Still looking for a victi^H^H^Hvolunteer. > = > * Parallel xenwatch > = > Bit sparse on details, GSOC =3D=3D unknown That would still be nice. It came from talking to Matt from Amazon. He was saying that having only one xenwatch thread slows things down for a medium to big server with lots of guests. Making multiple xenwatch threads to process XenBus requests in parallel would be a good improvement. > = > * Microcode uploader implementation > = > Done I think? > = > * Integrating NUMA and Tmem > = > Lists Dan as co-maintainer -- Konrad do you want to propose this > to the new tmem guy (I've forgotten his name) Bob Liu. Yes, lets rope him in. > = > * Performance tools overhaul > = > Bit vague. And has some of this been done? I can't remember what that is. > = > * "Upstream bugs" > = > There were 4 of these, dating back to 2012, I don't think this > list is a good place to track bugs and it seems like at least > some of them are now obsolete. So I've nuked the lot. If they > are still relevant I think it would be best to get them into the > bug tracker. OK, lets nuke them. We could also add the: VCPUOP_register_vcpu_time_memory_area support in Linux upstream kernel. MSI multi-vector for Linux upstream kernel. Thought those are mostly just putting pieces together and repost them so no "new" development. > = > Ben: > * dom0 kgdb support > = > Is this for GSoC? > = > George: > = > * Introducing PowerClamp-like driver for Xen > = > I don't think this has been done? > = > Dario: > * NUMA effects on inter-VM communication and on multi-VM workloads > = > I think this was under way as part of the GNOME Outreach > program. In that case perhaps it needs updating to reflect what > has been done and what still needs to be done? > = > * Integrating NUMA and Tmem > = > Lists Dan as co-maintainer -- covered under Konrad's name above. > = > * Is Xen ready for the Real-Time/Embedded World? > = > Sounds a bit blue sky? Now that there is active interest in this > on ARM perhaps a few concrete projects could be proposed to > replace it? > = > Andy: > = > * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA > allocations > = > Sounds too hard for a GSoC to me. Would need fleshing out in any > case. > = > * CPU/RAM/PCI diagram tool > = > Does this not already exist somewhere? > = > Paul: > = > * HVM per-event-channel interrupts > = > Might be easier now that Windows PV drivers are opened up? > = > Roger: > * Refactor Linux hotplug scripts > = > You did some of this I think? > = > Ian C: > = > * XL to XCP VM motion > = > Perhaps this could be broadened into VM transport between XL and > other things too -- e.g. libvirt? > = > Stefano: > = > * VM Snapshots > = > Still a good project I think > = > George: > = > * Allowing guests to boot with a passed-through GPU as the primary > display > = > This seems like a bit of a rathole for a GSoC student to me... > = > * Advanced Scheduling Parameters > = > Still to do? > = > Santosh: > = > * KDD (Windows Debugger Stub) enhancements > = > Dave > = > * Create a tiny VM for easy load testing > = > Someone was looking at this I think? > = > Ian J: > = > * Testing PV and HVM installs of Debian using debian-installer > * Testing NetBSD > = > BSD is done I think, and I'm looking at Debian Installer stuff > myself. I've removed these. > = > = > Phew! > Ian. > = > = > = > > Lars > > = > > On 20/01/2014 09:18, Lars Kurth wrote: > > > Hi all, > > > > > > the GSoC application deadline is coming up : Feb 2014. If we want to = > > > have any chance of getting accepted this year, we ought to get our = > > > project list into good shape. The project list and how the project an= d = > > > menters present themselves has a bigger impact on whether we get = > > > accepted than the actual application. > > > > > > Also, I would like to add a mentor section this year: a short bio, = > > > what the mentor cares about and a picture. This will help make the = > > > project list more real. > > > > > > We have *4 weeks* to do this. The bar for GSoC has been getting = > > > increasingly high. I know, we are tied down with Xen 4.4, but this is = > > > something you need to do if you want the Xen Project to participate. > > > > > > a) Please, update = > > > http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently = > > > (these need to be in good shape *before* the application). What I nee= d = > > > you to do is: > > > a.1) Remove items that are done > > > a.2) Add new work items : we ought to have a few sexy topics on say = > > > Real-time, mobile and some of the other segments (assuming we can get= HW) > > > a.3) All project proposals need to be peer reviewed *and* clear ... = > > > The peer review process for projects we put in place last year worked = > > > well, by which we had past mentors sign of project proposals that wer= e = > > > in good enough state. > > > > > > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, shoul= d = > > > get these listed on the respective other programs. And we should link = > > > to these from our project page. > > > > > > Best Regards > > > Lars > > > P.S.: I will also see whether we can participate as Xen Project under = > > > the LF GSoC program, but last year there was push-back and I don't = > > > expect this to change > > > > > = > > = > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > = > = _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iZ-EV; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3VH-0003pp-Ca for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:31:03 +0000 Received: from [85.158.137.68:12052] by server-10.bemta-3.messagelabs.com id 88/A0-07302-62B42F25; Wed, 05 Feb 2014 14:31:02 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1391610660!13562168!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2121 invoked from network); 5 Feb 2014 14:31:01 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:31:01 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="100109328" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Feb 2014 14:30:59 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:30:58 -0500 Message-ID: <1391610656.6497.179.camel@kazak.uk.xensource.com> From: Ian Campbell To: Konrad Rzeszutek Wilk Date: Wed, 5 Feb 2014 14:30:56 +0000 In-Reply-To: <20140205142932.GA3946@phenom.dumpdata.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <20140205142932.GA3946@phenom.dumpdata.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Andrew Cooper , Dario Faggioli , Ben Guthro , Santosh Jodh , "xen-api@lists.xen.org" , Ian Jackson , "xen-devel@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, 2014-02-05 at 09:29 -0500, Konrad Rzeszutek Wilk wrote: > On Wed, Feb 05, 2014 at 02:18:40PM +0000, Ben Guthro wrote: > > > > ________________________________________ > > From: Ian Campbell > > Sent: Wednesday, February 05, 2014 9:09 AM > > To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson > > Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org > > Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 > > > > > > > Ben: > > > * dom0 kgdb support > > > > > > Is this for GSoC? > > > > This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here. > > And it actually works! OK, I'll nuke it from the list hten, thanks! > > > > That said, Fri is my last day working for Citrix (and consequently, > on Xen) - and I'll be moving on to a Start-up company again, Good luck! Ian. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002j8-SD; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBS3r-00081r-Ph for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 16:44:24 +0000 Received: from [85.158.137.68:3417] by server-6.bemta-3.messagelabs.com id 04/66-09180-7EBB3F25; Thu, 06 Feb 2014 16:44:23 +0000 X-Env-Sender: Santosh.Jodh@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1391705060!129988!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15882 invoked from network); 6 Feb 2014 16:44:22 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 16:44:22 -0000 X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="100520273" Received: from sjcpex01cl03.citrite.net ([10.216.14.145]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 06 Feb 2014 16:44:19 +0000 Received: from SJCPEX01CL01.citrite.net ([169.254.1.22]) by SJCPEX01CL03.citrite.net ([10.216.14.145]) with mapi id 14.02.0342.004; Thu, 6 Feb 2014 08:44:18 -0800 From: Santosh Jodh To: Ian Campbell , "lars.kurth@xen.org" , Roger Pau Monne , Dario Faggioli , Konrad Rzeszutek Wilk , Ben Guthro , Andrew Cooper , Paul Durrant , "Ian Jackson" Thread-Topic: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Thread-Index: AQHPInvYT66dFluJmUOzBzbhNQgKPZqob1hA Date: Thu, 6 Feb 2014 16:44:18 +0000 Message-ID: <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.2.168] MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org PiANCj4gU2FudG9zaDoNCj4gDQo+ICAgICAgICogS0REIChXaW5kb3dzIERlYnVnZ2VyIFN0dWIp IGVuaGFuY2VtZW50cw0KPiANCltTYW50b3NoIEpvZGhdIEkgYmVsaWV2ZSB0aGlzIGlzIHN0aWxs IGEgZ29vZCBHU09DIHByb2plY3QuIEhvd2V2ZXIsIGluIGxpZ2h0IG9mIG15IG5ldyBkaXJlY3Rp b24sIEkgYW0gbm90IHN1cmUgaWYgSSB3aWxsIGJlIGFibGUgdG8gbWVudG9yLiBEb27igJl0IGtu b3cgaWYgUGF1bCBvciBzb21lb25lIGVsc2Ugb24gdGhlIFdpbmRvd3MgdGVhbSB3b3VsZCB3YW50 IHRvIHNwb25zb3IgdGhpcy4NCg0KUmVnYXJkcywNClNhbnRvc2gNCl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlz dApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJv amVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iK-8Z; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3AA-0002Ts-Ac for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:09:14 +0000 Received: from [193.109.254.147:9910] by server-13.bemta-14.messagelabs.com id A2/4B-01226-90642F25; Wed, 05 Feb 2014 14:09:13 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-2.tower-27.messagelabs.com!1391609351!2187672!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12969 invoked from network); 5 Feb 2014 14:09:12 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:09:12 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="98207648" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Feb 2014 14:09:10 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:09:10 -0500 Message-ID: <1391609348.6497.178.camel@kazak.uk.xensource.com> From: Ian Campbell To: , Roger Pau Monne , "Dario Faggioli" , Konrad Rzeszutek Wilk , Ben Guthro , "Andrew Cooper" , Paul Durrant , Santosh Jodh , Ian Jackson Date: Wed, 5 Feb 2014 14:09:08 +0000 In-Reply-To: <52E7B6AF.3050604@xen.org> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gVHVlLCAyMDE0LTAxLTI4IGF0IDEzOjU0ICswMDAwLCBMYXJzIEt1cnRoIHdyb3RlOgo+IEhp IGFsbCwKPiBJIGhhdmUgbm90IGdvdHRlbiBhbnkgcmVwbHkgdG8gdGhpcyB0aHJlYWQuIEkgc2F3 IFdlaSBMdWkgYW5kIEFuZHLDqXMgCj4gTGFnYXItQ2F2aWxsYSBtYWtlIGNoYW5nZXMgdG8gdGhl IHByb2plY3QgbGlzdC4gUGxlYXNlIGdvIHRocm91Z2ggdGhlIAo+IGl0ZW1zIGJlbG93IGFuZCBt YWtlIGNoYW5nZXMgYXMgc3VnZ2VzdGVkLiBPdGhlcndpc2UsIG91ciBjaGFuY2VzIHRvIGdldCAK PiBpbnRvIEdTb0MgMjAxNCB3aWxsIGJlIHJlbGF0aXZlbHkgc2xpbS4KCkdvaW5nIHRocm91Z2gg dGhlIGxpc3QsIHBlb3BsZSBsaXN0ZWQgYXMgdGVjaG5pY2FsIGNvbnRhY3RzIGZvciBwcm9qZWN0 cwp3aXRoIEdTb0MgPT0geWVzIChvciB1bmtub3duKSBhcmUgaW4gdGhlIFRvIGxpbmUuIFBsZWFz ZSByZWl0ZXJhdGUgeW91cgppbnRlcmVzdCBpbiBtZW50b3JpbmcgdGhlIHByb2plY3QocykgYW5k IHVwZGF0ZSBvciByZW1vdmUgdGhlIGVudHJ5IGFzCm5lY2Vzc2FyeS4KCkkgc2tpcHBlZCB0aGlu Z3MgYWRkZWQgcmVjZW50bHkgYW5kIEkgc2tpcHBlZCAiWGVuIENsb3VkIFBsYXRmb3JtIChYQ1Ap CmFuZCBYQVBJIHByb2plY3RzIiwgc29tZW9uZSBlbHNlIGNhbiBwaWNrIHRoYXQgdXAuCgpBbmQg dG8gcmVpdGVyYXRlIHdoYXQgTGFycyBzYWlkOgoKPiBBZGQgbmV3IHdvcmsgaXRlbXMgOiB3ZSBv dWdodCB0byBoYXZlIGEgZmV3IHNleHkgdG9waWNzIG9uIHNheSAKPiBSZWFsLXRpbWUsIG1vYmls ZSBhbmQgc29tZSBvZiB0aGUgb3RoZXIgc2VnbWVudHMgKGFzc3VtaW5nIHdlIGNhbiBnZXQKPiBI VykKWy4uLl0KPiBiKSBBbnlvbmUgd2hvIGhhcyBzb21lIGtlcm5lbC9saW51eC9ic2QvZGlzdHJv L3FlbXUgd29yay1pdGVtcywgc2hvdWxkIAo+IGdldCB0aGVzZSBsaXN0ZWQgb24gdGhlIHJlc3Bl Y3RpdmUgb3RoZXIgcHJvZ3JhbXMuIEFuZCB3ZSBzaG91bGQgbGluayAKPiB0byB0aGVzZSBmcm9t IG91ciBwcm9qZWN0IHBhZ2UuCgpUaGUgbGlzdDoKClBhc2k6CiAgICAgICogSW1wbGVtZW50IFhl biBQVlNDU0kgc3VwcG9ydCBpbiB4bC9saWJ4bCB0b29sc3RhY2sKICAgICAgKiBJbXBsZW1lbnQg WGVuIFBWVVNCIHN1cHBvcnQgaW4geGwvbGlieGwgdG9vbHN0YWNrCgogICAgICAgIEJvdGggaGF2 ZSB1bmFuc3dlcmVkIHF1ZXN0aW9ucyBwb3NlZCBieSBMYXJzIGluIEphbnVhcnkgMjAxMy4KICAg ICAgICAKS29ucmFkOgogICAgICAqIEJsb2NrIGJhY2tlbmQvZnJvbnRlbmQgaW1wcm92ZW1lbnRz CgogICAgICAgIEkgc3VzcGVjdCBhIGJ1bmNoIG9mIHRoZXNlIGFyZSBkb25lPyAoQWxzbyBDQyBS b2dlciwgd2hvIG1heQogICAgICAgIGhhdmUgZG9uZSB0aGVtLi4uKQogICAgICAgIAogICAgICAg IFdhcyBpbiB0aGUgbGlzdCB0d2ljZSwgdGhleSBsb29rZWQgaWRlbnRpY2FsIHNvIEkgbnVrZWQg b25lLgogICAgICAgIAogICAgICAqIFV0aWxpemUgSW50ZWwgUXVpY2tQYXRoIG9uIG5ldHdvcmsg YW5kIGJsb2NrIHBhdGguCgogICAgICAgIE5vIGNvbW1lbnRzIGV0YywgYnV0IHNvdW5kcyBhZHZh bmNlZCBmb3IgYSBHU29DIHN0dWRlbnQsIHBsdXMKICAgICAgICBpdHMgdW5jbGVhciB3aGVuIHN1 Y2ggaGFyZHdhcmUgYmVjYW1lIGF2YWlsYWJsZSwgYXJlIHRoZXkgbGlrZWx5CiAgICAgICAgdG8g aGF2ZSBpdD8gSXQgc291bmRzIGxpa2UgaXQgbWlnaHQgYWxzbyBiZSBxdWl0ZSBoaWdoIGVuZC4K ICAgICAgICAKICAgICAgKiBwZXJmIHdvcmtpbmcgd2l0aCBYZW4KCiAgICAgICAgRG9uZS9pbiBw cm9ncmVzcyBieSBCb3JpcyBJIHRoaW5rCiAgICAgICAgCiAgICAgICogUEFUIHdyaXRlY29tYmlu ZSBmaXh1cAoKICAgICAgICBEaWQgSSBzZWUgYSBmaXggZm9yIHRoaXMgZ28gcGFzdD8gR1NvQyA9 PSB1bmtub3duPwogICAgICAgIAogICAgICAqIFBhcmFsbGVsIHhlbndhdGNoCgogICAgICAgIEJp dCBzcGFyc2Ugb24gZGV0YWlscywgR1NPQyA9PSB1bmtub3duCgogICAgICAqIE1pY3JvY29kZSB1 cGxvYWRlciBpbXBsZW1lbnRhdGlvbgogICAgICAgIAogICAgICAgIERvbmUgSSB0aGluaz8KCiAg ICAgICogSW50ZWdyYXRpbmcgTlVNQSBhbmQgVG1lbQogICAgICAgIAogICAgICAgIExpc3RzIERh biBhcyBjby1tYWludGFpbmVyIC0tIEtvbnJhZCBkbyB5b3Ugd2FudCB0byBwcm9wb3NlIHRoaXMK ICAgICAgICB0byB0aGUgbmV3IHRtZW0gZ3V5IChJJ3ZlIGZvcmdvdHRlbiBoaXMgbmFtZSkKICAg ICAgICAKICAgICAgKiBQZXJmb3JtYW5jZSB0b29scyBvdmVyaGF1bAoKICAgICAgICBCaXQgdmFn dWUuIEFuZCBoYXMgc29tZSBvZiB0aGlzIGJlZW4gZG9uZT8KCiAgICAgICogIlVwc3RyZWFtIGJ1 Z3MiCgogICAgICAgIFRoZXJlIHdlcmUgNCBvZiB0aGVzZSwgZGF0aW5nIGJhY2sgdG8gMjAxMiwg SSBkb24ndCB0aGluayB0aGlzCiAgICAgICAgbGlzdCBpcyBhIGdvb2QgcGxhY2UgdG8gdHJhY2sg YnVncyBhbmQgaXQgc2VlbXMgbGlrZSBhdCBsZWFzdAogICAgICAgIHNvbWUgb2YgdGhlbSBhcmUg bm93IG9ic29sZXRlLiBTbyBJJ3ZlIG51a2VkIHRoZSBsb3QuIElmIHRoZXkKICAgICAgICBhcmUg c3RpbGwgcmVsZXZhbnQgSSB0aGluayBpdCB3b3VsZCBiZSBiZXN0IHRvIGdldCB0aGVtIGludG8g dGhlCiAgICAgICAgYnVnIHRyYWNrZXIuCiAgICAgICAgCkJlbjoKICAgICAgKiBkb20wIGtnZGIg c3VwcG9ydAoKICAgICAgICBJcyB0aGlzIGZvciBHU29DPwoKR2VvcmdlOgoKICAgICAgKiBJbnRy b2R1Y2luZyBQb3dlckNsYW1wLWxpa2UgZHJpdmVyIGZvciBYZW4KCiAgICAgICAgSSBkb24ndCB0 aGluayB0aGlzIGhhcyBiZWVuIGRvbmU/CgpEYXJpbzoKICAgICAgKiBOVU1BIGVmZmVjdHMgb24g aW50ZXItVk0gY29tbXVuaWNhdGlvbiBhbmQgb24gbXVsdGktVk0gd29ya2xvYWRzCgogICAgICAg IEkgdGhpbmsgdGhpcyB3YXMgdW5kZXIgd2F5IGFzIHBhcnQgb2YgdGhlIEdOT01FIE91dHJlYWNo CiAgICAgICAgcHJvZ3JhbS4gSW4gdGhhdCBjYXNlIHBlcmhhcHMgaXQgbmVlZHMgdXBkYXRpbmcg dG8gcmVmbGVjdCB3aGF0CiAgICAgICAgaGFzIGJlZW4gZG9uZSBhbmQgd2hhdCBzdGlsbCBuZWVk cyB0byBiZSBkb25lPwogICAgICAgIAogICAgICAqIEludGVncmF0aW5nIE5VTUEgYW5kIFRtZW0K CiAgICAgICAgTGlzdHMgRGFuIGFzIGNvLW1haW50YWluZXIgLS0gY292ZXJlZCB1bmRlciBLb25y YWQncyBuYW1lIGFib3ZlLgogICAgICAgIAogICAgICAqIElzIFhlbiByZWFkeSBmb3IgdGhlIFJl YWwtVGltZS9FbWJlZGRlZCBXb3JsZD8KICAgICAgICAgICAgICAgIAogICAgICAgIFNvdW5kcyBh IGJpdCBibHVlIHNreT8gTm93IHRoYXQgdGhlcmUgaXMgYWN0aXZlIGludGVyZXN0IGluIHRoaXMK ICAgICAgICBvbiBBUk0gcGVyaGFwcyBhIGZldyBjb25jcmV0ZSBwcm9qZWN0cyBjb3VsZCBiZSBw cm9wb3NlZCB0bwogICAgICAgIHJlcGxhY2UgaXQ/CgpBbmR5OgoKICAgICAgKiBJT01NVSBjb250 cm9sIGZvciBTV0lPVExCLCB0byBhdm9pZCBkb20wIGNvcHkgb2YgYWxsID40SyBETUEKICAgICAg ICBhbGxvY2F0aW9ucwoKICAgICAgICBTb3VuZHMgdG9vIGhhcmQgZm9yIGEgR1NvQyB0byBtZS4g V291bGQgbmVlZCBmbGVzaGluZyBvdXQgaW4gYW55CiAgICAgICAgY2FzZS4KICAgICAgICAKICAg ICAgKiBDUFUvUkFNL1BDSSBkaWFncmFtIHRvb2wKCiAgICAgICAgRG9lcyB0aGlzIG5vdCBhbHJl YWR5IGV4aXN0IHNvbWV3aGVyZT8KICAgICAgICAKUGF1bDoKCiAgICAgICogSFZNIHBlci1ldmVu dC1jaGFubmVsIGludGVycnVwdHMKCiAgICAgICAgTWlnaHQgYmUgZWFzaWVyIG5vdyB0aGF0IFdp bmRvd3MgUFYgZHJpdmVycyBhcmUgb3BlbmVkIHVwPwoKUm9nZXI6CiAgICAgICogUmVmYWN0b3Ig TGludXggaG90cGx1ZyBzY3JpcHRzCgogICAgICAgIFlvdSBkaWQgc29tZSBvZiB0aGlzIEkgdGhp bms/CiAgICAgICAgCklhbiBDOgoKICAgICAgKiBYTCB0byBYQ1AgVk0gbW90aW9uCgogICAgICAg IFBlcmhhcHMgdGhpcyBjb3VsZCBiZSBicm9hZGVuZWQgaW50byBWTSB0cmFuc3BvcnQgYmV0d2Vl biBYTCBhbmQKICAgICAgICBvdGhlciB0aGluZ3MgdG9vIC0tIGUuZy4gbGlidmlydD8KClN0ZWZh bm86CgogICAgICAqIFZNIFNuYXBzaG90cwoKICAgICAgICBTdGlsbCBhIGdvb2QgcHJvamVjdCBJ IHRoaW5rCiAgICAgICAgCkdlb3JnZToKCiAgICAgICogQWxsb3dpbmcgZ3Vlc3RzIHRvIGJvb3Qg d2l0aCBhIHBhc3NlZC10aHJvdWdoIEdQVSBhcyB0aGUgcHJpbWFyeQogICAgICAgIGRpc3BsYXkK CiAgICAgICAgVGhpcyBzZWVtcyBsaWtlIGEgYml0IG9mIGEgcmF0aG9sZSBmb3IgYSBHU29DIHN0 dWRlbnQgdG8gbWUuLi4KICAgICAgICAKICAgICAgKiBBZHZhbmNlZCBTY2hlZHVsaW5nIFBhcmFt ZXRlcnMKICAgICAgICAKICAgICAgICBTdGlsbCB0byBkbz8KClNhbnRvc2g6CgogICAgICAqIEtE RCAoV2luZG93cyBEZWJ1Z2dlciBTdHViKSBlbmhhbmNlbWVudHMKICAgICAgICAKRGF2ZQoKICAg ICAgKiBDcmVhdGUgYSB0aW55IFZNIGZvciBlYXN5IGxvYWQgdGVzdGluZwoKICAgICAgICBTb21l b25lIHdhcyBsb29raW5nIGF0IHRoaXMgSSB0aGluaz8KICAgICAgICAKSWFuIEo6CgogICAgICAq IFRlc3RpbmcgUFYgYW5kIEhWTSBpbnN0YWxscyBvZiBEZWJpYW4gdXNpbmcgZGViaWFuLWluc3Rh bGxlcgogICAgICAqIFRlc3RpbmcgTmV0QlNECgogICAgICAgIEJTRCBpcyBkb25lIEkgdGhpbmss IGFuZCBJJ20gbG9va2luZyBhdCBEZWJpYW4gSW5zdGFsbGVyIHN0dWZmCiAgICAgICAgbXlzZWxm LiBJJ3ZlIHJlbW92ZWQgdGhlc2UuCgoKUGhldyEKSWFuLgoKCgo+IExhcnMKPiAKPiBPbiAyMC8w MS8yMDE0IDA5OjE4LCBMYXJzIEt1cnRoIHdyb3RlOgo+ID4gSGkgYWxsLAo+ID4KPiA+IHRoZSBH U29DIGFwcGxpY2F0aW9uIGRlYWRsaW5lIGlzIGNvbWluZyB1cCA6IEZlYiAyMDE0LiBJZiB3ZSB3 YW50IHRvIAo+ID4gaGF2ZSBhbnkgY2hhbmNlIG9mIGdldHRpbmcgYWNjZXB0ZWQgdGhpcyB5ZWFy LCB3ZSBvdWdodCB0byBnZXQgb3VyIAo+ID4gcHJvamVjdCBsaXN0IGludG8gZ29vZCBzaGFwZS4g VGhlIHByb2plY3QgbGlzdCBhbmQgaG93IHRoZSBwcm9qZWN0IGFuZCAKPiA+IG1lbnRlcnMgcHJl c2VudCB0aGVtc2VsdmVzIGhhcyBhIGJpZ2dlciBpbXBhY3Qgb24gd2hldGhlciB3ZSBnZXQgCj4g PiBhY2NlcHRlZCB0aGFuIHRoZSBhY3R1YWwgYXBwbGljYXRpb24uCj4gPgo+ID4gQWxzbywgSSB3 b3VsZCBsaWtlIHRvIGFkZCBhIG1lbnRvciBzZWN0aW9uIHRoaXMgeWVhcjogYSBzaG9ydCBiaW8s IAo+ID4gd2hhdCB0aGUgbWVudG9yIGNhcmVzIGFib3V0IGFuZCBhIHBpY3R1cmUuIFRoaXMgd2ls bCBoZWxwIG1ha2UgdGhlIAo+ID4gcHJvamVjdCBsaXN0IG1vcmUgcmVhbC4KPiA+Cj4gPiBXZSBo YXZlICo0IHdlZWtzKiB0byBkbyB0aGlzLiBUaGUgYmFyIGZvciBHU29DIGhhcyBiZWVuIGdldHRp bmcgCj4gPiBpbmNyZWFzaW5nbHkgaGlnaC4gSSBrbm93LCB3ZSBhcmUgdGllZCBkb3duIHdpdGgg WGVuIDQuNCwgYnV0IHRoaXMgaXMgCj4gPiBzb21ldGhpbmcgeW91IG5lZWQgdG8gZG8gaWYgeW91 IHdhbnQgdGhlIFhlbiBQcm9qZWN0IHRvIHBhcnRpY2lwYXRlLgo+ID4KPiA+IGEpIFBsZWFzZSwg dXBkYXRlIAo+ID4gaHR0cDovL3dpa2kueGVucHJvamVjdC5vcmcvd2lraS9YZW5fRGV2ZWxvcG1l bnRfUHJvamVjdHMgdXJnZW50bHkgCj4gPiAodGhlc2UgbmVlZCB0byBiZSBpbiBnb29kIHNoYXBl ICpiZWZvcmUqIHRoZSBhcHBsaWNhdGlvbikuIFdoYXQgSSBuZWVkIAo+ID4geW91IHRvIGRvIGlz Ogo+ID4gYS4xKSBSZW1vdmUgaXRlbXMgdGhhdCBhcmUgZG9uZQo+ID4gYS4yKSBBZGQgbmV3IHdv cmsgaXRlbXMgOiB3ZSBvdWdodCB0byBoYXZlIGEgZmV3IHNleHkgdG9waWNzIG9uIHNheSAKPiA+ IFJlYWwtdGltZSwgbW9iaWxlIGFuZCBzb21lIG9mIHRoZSBvdGhlciBzZWdtZW50cyAoYXNzdW1p bmcgd2UgY2FuIGdldCBIVykKPiA+IGEuMykgQWxsIHByb2plY3QgcHJvcG9zYWxzIG5lZWQgdG8g YmUgcGVlciByZXZpZXdlZCAqYW5kKiBjbGVhciAuLi4gCj4gPiBUaGUgcGVlciByZXZpZXcgcHJv Y2VzcyBmb3IgcHJvamVjdHMgd2UgcHV0IGluIHBsYWNlIGxhc3QgeWVhciB3b3JrZWQgCj4gPiB3 ZWxsLCBieSB3aGljaCB3ZSBoYWQgcGFzdCBtZW50b3JzIHNpZ24gb2YgcHJvamVjdCBwcm9wb3Nh bHMgdGhhdCB3ZXJlIAo+ID4gaW4gZ29vZCBlbm91Z2ggc3RhdGUuCj4gPgo+ID4gYikgQW55b25l IHdobyBoYXMgc29tZSBrZXJuZWwvbGludXgvYnNkL2Rpc3Ryby9xZW11IHdvcmstaXRlbXMsIHNo b3VsZCAKPiA+IGdldCB0aGVzZSBsaXN0ZWQgb24gdGhlIHJlc3BlY3RpdmUgb3RoZXIgcHJvZ3Jh bXMuIEFuZCB3ZSBzaG91bGQgbGluayAKPiA+IHRvIHRoZXNlIGZyb20gb3VyIHByb2plY3QgcGFn ZS4KPiA+Cj4gPiBCZXN0IFJlZ2FyZHMKPiA+IExhcnMKPiA+IFAuUy46IEkgd2lsbCBhbHNvIHNl ZSB3aGV0aGVyIHdlIGNhbiBwYXJ0aWNpcGF0ZSBhcyBYZW4gUHJvamVjdCB1bmRlciAKPiA+IHRo ZSBMRiBHU29DIHByb2dyYW0sIGJ1dCBsYXN0IHllYXIgdGhlcmUgd2FzIHB1c2gtYmFjayBhbmQg SSBkb24ndCAKPiA+IGV4cGVjdCB0aGlzIHRvIGNoYW5nZQo+ID4KPiAKPiAKPiBfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IFhlbi1kZXZlbCBtYWlsaW5n IGxpc3QKPiBYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwo+IGh0dHA6Ly9saXN0cy54ZW4ub3JnL3hl bi1kZXZlbAoKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f XwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJv amVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0 aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5n-0002jg-1l; Thu, 06 Feb 2014 17:50:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBSzz-0002F3-Qb for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 17:44:28 +0000 Received: from [193.109.254.147:34869] by server-11.bemta-14.messagelabs.com id B4/99-24604-BF9C3F25; Thu, 06 Feb 2014 17:44:27 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1391708664!2557418!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6830 invoked from network); 6 Feb 2014 17:44:26 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 17:44:26 -0000 X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="100540386" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 06 Feb 2014 17:44:08 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Thu, 6 Feb 2014 12:44:08 -0500 Message-ID: <1391708646.2162.12.camel@kazak.uk.xensource.com> From: Ian Campbell To: Paul Durrant Date: Thu, 6 Feb 2014 17:44:06 +0000 In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD02270E9@AMSPEX01CL01.citrite.net> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD02270E9@AMSPEX01CL01.citrite.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Konrad Rzeszutek Wilk , Andrew Cooper , Dario Faggioli , Ben Guthro , Santosh Jodh , "xen-api@lists.xen.org" , Ian Jackson , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gVGh1LCAyMDE0LTAyLTA2IGF0IDE3OjQzICswMDAwLCBQYXVsIER1cnJhbnQgd3JvdGU6Cj4g PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+ID4gRnJvbTogU2FudG9zaCBKb2RoCj4gPiBT ZW50OiAwNiBGZWJydWFyeSAyMDE0IDE2OjQ0Cj4gPiBUbzogSWFuIENhbXBiZWxsOyBsYXJzLmt1 cnRoQHhlbi5vcmc7IFJvZ2VyIFBhdSBNb25uZTsgRGFyaW8gRmFnZ2lvbGk7Cj4gPiBLb25yYWQg Unplc3p1dGVrIFdpbGs7IEJlbiBHdXRocm87IEFuZHJldyBDb29wZXI7IFBhdWwgRHVycmFudDsg SWFuCj4gPiBKYWNrc29uCj4gPiBDYzogeGVuLWRldmVsQGxpc3RzLnhlbi5vcmc7IHhlbi1hcGlA bGlzdHMueGVuLm9yZzsgbWlyYWdlb3MtCj4gPiBkZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwo+ ID4gU3ViamVjdDogUkU6IFtYZW4tZGV2ZWxdIFByZXBwaW5nIGZvciBHU09DIDIwMTQgW1VSR0VO VF0gLSBkZWFkbGluZSBGZWIgMTQKPiA+IDIwMTQKPiA+IAo+ID4gPgo+ID4gPiBTYW50b3NoOgo+ ID4gPgo+ID4gPiAgICAgICAqIEtERCAoV2luZG93cyBEZWJ1Z2dlciBTdHViKSBlbmhhbmNlbWVu dHMKPiA+ID4KPiA+IFtTYW50b3NoIEpvZGhdIEkgYmVsaWV2ZSB0aGlzIGlzIHN0aWxsIGEgZ29v ZCBHU09DIHByb2plY3QuIEhvd2V2ZXIsIGluIGxpZ2h0IG9mCj4gPiBteSBuZXcgZGlyZWN0aW9u LCBJIGFtIG5vdCBzdXJlIGlmIEkgd2lsbCBiZSBhYmxlIHRvIG1lbnRvci4gRG9u4oCZdCBrbm93 IGlmIFBhdWwKPiA+IG9yIHNvbWVvbmUgZWxzZSBvbiB0aGUgV2luZG93cyB0ZWFtIHdvdWxkIHdh bnQgdG8gc3BvbnNvciB0aGlzLgo+ID4gCj4gCj4gWWVzLCBpdCdzIHN0aWxsIGEgd29ydGh5IHBy b2plY3QuIEknZCBiZSBoYXBweSB0byBzcG9uc29yLgoKRG8geW91IG1lYW4gIm1lbnRvciI/CgpD YW4geW91IHVwZGF0ZSBodGUgcHJvamVjdCBvbiB0aGUgd2lraSBwbGVhc2UuCgpJYW4uCgoKCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRl dmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRw Oi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9z LWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iy-OX; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3mk-000691-Ta for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:49:07 +0000 Received: from [193.109.254.147:27633] by server-2.bemta-14.messagelabs.com id 0E/7E-01236-26F42F25; Wed, 05 Feb 2014 14:49:06 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1391611742!2237810!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5738 invoked from network); 5 Feb 2014 14:49:04 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:49:04 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="98225850" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Feb 2014 14:49:02 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:49:01 -0500 Received: from andrewcoop.uk.xensource.com ([10.80.2.18]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1WB3mf-00073Y-KG; Wed, 05 Feb 2014 14:49:01 +0000 Message-ID: <52F24F5D.7020207@citrix.com> Date: Wed, 5 Feb 2014 14:49:01 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: Ian Campbell References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <52F24D4D.7040004@citrix.com> <1391611558.23098.2.camel@kazak.uk.xensource.com> In-Reply-To: <1391611558.23098.2.camel@kazak.uk.xensource.com> X-Enigmail-Version: 1.6 X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Konrad Rzeszutek Wilk , Dario Faggioli , Ian Jackson , Paul Durrant , Santosh Jodh , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 05/02/14 14:45, Ian Campbell wrote: > On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote: >> On 05/02/14 14:09, Ian Campbell wrote: >>> Andy: >>> >>> * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA >>> allocations >>> >>> Sounds too hard for a GSoC to me. Would need fleshing out in any >>> case. >> Malcolm made a prototype for this on the first day of the Hackathon. It >> can disappear. > Removed. > >>> * CPU/RAM/PCI diagram tool >>> >>> Does this not already exist somewhere? >> Not as far as I (or my ability to google) am aware. >> >> My furrowing into hwloc interacting with Xen and libxc is a start to all >> of this, but it is still very much in my copious free time and there is >> more than enough other work which could be done if someone were interested. > OK, left in place. > > This could conceivably be done under another umbrella such as the Linux > one too, since it seems generic. > > Ian. > > For native Linux, hwloc kinda already does this already - certainly the CPU and PCI bits. Under Xen there are quite a few areas needing improvement, which will require active development work. ~Andrew _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002io-Kk; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3g5-0005Ba-4k for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:42:13 +0000 Received: from [193.109.254.147:46251] by server-4.bemta-14.messagelabs.com id D7/2C-32066-4CD42F25; Wed, 05 Feb 2014 14:42:12 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1391611330!2235902!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10120 invoked from network); 5 Feb 2014 14:42:11 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:42:11 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="100114587" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Feb 2014 14:42:10 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:42:09 -0500 Message-ID: <1391611327.6497.181.camel@kazak.uk.xensource.com> From: Ian Campbell To: Konrad Rzeszutek Wilk Date: Wed, 5 Feb 2014 14:42:07 +0000 In-Reply-To: <20140205143402.GB3946@phenom.dumpdata.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <20140205143402.GB3946@phenom.dumpdata.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Andrew Cooper , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , Santosh Jodh , "xen-api@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, 2014-02-05 at 09:34 -0500, Konrad Rzeszutek Wilk wrote: > > > > * Parallel xenwatch > > > > Bit sparse on details, GSOC == unknown > > That would still be nice. It came from talking to Matt from Amazon. He > was saying that having only one xenwatch thread slows things down for > a medium to big server with lots of guests. Making multiple > xenwatch threads to process XenBus requests in parallel would be > a good improvement. Would need to be careful about exposing cases of insufficient locking in the existing code. > > > > > * Microcode uploader implementation > > > > Done I think? > > Nuked > > * Performance tools overhaul > > > > Bit vague. And has some of this been done? > > I can't remember what that is. OK, I nuked it -- a new project can always be added if you remember what it was. > > > > * "Upstream bugs" > > > > There were 4 of these, dating back to 2012, I don't think this > > list is a good place to track bugs and it seems like at least > > some of them are now obsolete. So I've nuked the lot. If they > > are still relevant I think it would be best to get them into the > > bug tracker. > > OK, lets nuke them. Done. > > We could also add the: > > VCPUOP_register_vcpu_time_memory_area support in Linux upstream kernel. > > MSI multi-vector for Linux upstream kernel. > > Thought those are mostly just putting pieces together and repost them > so no "new" development. Not really suitable for this list then IMHO. Ian. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iU-Ch; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3Ty-0003jm-VJ for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:29:43 +0000 Received: from [85.158.143.35:31969] by server-3.bemta-4.messagelabs.com id 1F/A7-11539-6DA42F25; Wed, 05 Feb 2014 14:29:42 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1391610580!3359190!1 X-Originating-IP: [156.151.31.81] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU2LjE1MS4zMS44MSA9PiAyODgzMzk=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8287 invoked from network); 5 Feb 2014 14:29:41 -0000 Received: from userp1040.oracle.com (HELO userp1040.oracle.com) (156.151.31.81) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Feb 2014 14:29:41 -0000 Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s15ETZ0w031233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Feb 2014 14:29:36 GMT Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s15ETYNJ029718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Feb 2014 14:29:34 GMT Received: from abhmp0008.oracle.com (abhmp0008.oracle.com [141.146.116.14]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s15ETYpI029712; Wed, 5 Feb 2014 14:29:34 GMT Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 05 Feb 2014 06:29:33 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 66A531C0972; Wed, 5 Feb 2014 09:29:32 -0500 (EST) Date: Wed, 5 Feb 2014 09:29:32 -0500 From: Konrad Rzeszutek Wilk To: Ben Guthro Message-ID: <20140205142932.GA3946@phenom.dumpdata.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ian Campbell , Andrew Cooper , Dario Faggioli , "xen-devel@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , Santosh Jodh , Ian Jackson , "xen-api@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, Feb 05, 2014 at 02:18:40PM +0000, Ben Guthro wrote: > > ________________________________________ > From: Ian Campbell > Sent: Wednesday, February 05, 2014 9:09 AM > To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson > Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org > Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 > > > > Ben: > > * dom0 kgdb support > > > > Is this for GSoC? > > This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here. And it actually works! > > That said, Fri is my last day working for Citrix (and consequently, on Xen) - and I'll be moving on to a Start-up company again, so someone else would need to sponsor this project. > > Naturally, I'll be available via my Non-Citrix email address (ben@guthro.net) > > > Ben _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002ie-Gp; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3ZK-00043h-Fz for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:35:14 +0000 Received: from [85.158.137.68:15564] by server-15.bemta-3.messagelabs.com id B8/48-19263-12C42F25; Wed, 05 Feb 2014 14:35:13 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1391610911!12416611!1 X-Originating-IP: [156.151.31.81] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTU2LjE1MS4zMS44MSA9PiAyODgzMzk=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10412 invoked from network); 5 Feb 2014 14:35:12 -0000 Received: from userp1040.oracle.com (HELO userp1040.oracle.com) (156.151.31.81) by server-10.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Feb 2014 14:35:12 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s15EY6n4004448 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Feb 2014 14:34:06 GMT Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s15EY5Mu020127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 5 Feb 2014 14:34:06 GMT Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s15EY4NJ006146; Wed, 5 Feb 2014 14:34:05 GMT Received: from phenom.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 05 Feb 2014 06:34:04 -0800 Received: by phenom.dumpdata.com (Postfix, from userid 1000) id 0BD121C0972; Wed, 5 Feb 2014 09:34:03 -0500 (EST) Date: Wed, 5 Feb 2014 09:34:02 -0500 From: Konrad Rzeszutek Wilk To: Ian Campbell Message-ID: <20140205143402.GB3946@phenom.dumpdata.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Andrew Cooper , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , Santosh Jodh , "xen-api@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, Feb 05, 2014 at 02:09:08PM +0000, Ian Campbell wrote: > On Tue, 2014-01-28 at 13:54 +0000, Lars Kurth wrote: > > Hi all, > > I have not gotten any reply to this thread. I saw Wei Lui and Andr=E9s = > > Lagar-Cavilla make changes to the project list. Please go through the = > > items below and make changes as suggested. Otherwise, our chances to ge= t = > > into GSoC 2014 will be relatively slim. > = > Going through the list, people listed as technical contacts for projects > with GSoC =3D=3D yes (or unknown) are in the To line. Please reiterate yo= ur > interest in mentoring the project(s) and update or remove the entry as > necessary. > = > I skipped things added recently and I skipped "Xen Cloud Platform (XCP) > and XAPI projects", someone else can pick that up. > = > And to reiterate what Lars said: > = > > Add new work items : we ought to have a few sexy topics on say = > > Real-time, mobile and some of the other segments (assuming we can get > > HW) > [...] > > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should = > > get these listed on the respective other programs. And we should link = > > to these from our project page. > = > The list: > = > Pasi: > * Implement Xen PVSCSI support in xl/libxl toolstack > * Implement Xen PVUSB support in xl/libxl toolstack > = > Both have unanswered questions posed by Lars in January 2013. > = > Konrad: > * Block backend/frontend improvements > = > I suspect a bunch of these are done? (Also CC Roger, who may > have done them...) > = > Was in the list twice, they looked identical so I nuked one. > = > * Utilize Intel QuickPath on network and block path. > = > No comments etc, but sounds advanced for a GSoC student, plus > its unclear when such hardware became available, are they likely > to have it? It sounds like it might also be quite high end. > = > * perf working with Xen > = > Done/in progress by Boris I think > = > * PAT writecombine fixup > = > Did I see a fix for this go past? GSoC =3D=3D unknown? No. Still looking for a victi^H^H^Hvolunteer. > = > * Parallel xenwatch > = > Bit sparse on details, GSOC =3D=3D unknown That would still be nice. It came from talking to Matt from Amazon. He was saying that having only one xenwatch thread slows things down for a medium to big server with lots of guests. Making multiple xenwatch threads to process XenBus requests in parallel would be a good improvement. > = > * Microcode uploader implementation > = > Done I think? > = > * Integrating NUMA and Tmem > = > Lists Dan as co-maintainer -- Konrad do you want to propose this > to the new tmem guy (I've forgotten his name) Bob Liu. Yes, lets rope him in. > = > * Performance tools overhaul > = > Bit vague. And has some of this been done? I can't remember what that is. > = > * "Upstream bugs" > = > There were 4 of these, dating back to 2012, I don't think this > list is a good place to track bugs and it seems like at least > some of them are now obsolete. So I've nuked the lot. If they > are still relevant I think it would be best to get them into the > bug tracker. OK, lets nuke them. We could also add the: VCPUOP_register_vcpu_time_memory_area support in Linux upstream kernel. MSI multi-vector for Linux upstream kernel. Thought those are mostly just putting pieces together and repost them so no "new" development. > = > Ben: > * dom0 kgdb support > = > Is this for GSoC? > = > George: > = > * Introducing PowerClamp-like driver for Xen > = > I don't think this has been done? > = > Dario: > * NUMA effects on inter-VM communication and on multi-VM workloads > = > I think this was under way as part of the GNOME Outreach > program. In that case perhaps it needs updating to reflect what > has been done and what still needs to be done? > = > * Integrating NUMA and Tmem > = > Lists Dan as co-maintainer -- covered under Konrad's name above. > = > * Is Xen ready for the Real-Time/Embedded World? > = > Sounds a bit blue sky? Now that there is active interest in this > on ARM perhaps a few concrete projects could be proposed to > replace it? > = > Andy: > = > * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA > allocations > = > Sounds too hard for a GSoC to me. Would need fleshing out in any > case. > = > * CPU/RAM/PCI diagram tool > = > Does this not already exist somewhere? > = > Paul: > = > * HVM per-event-channel interrupts > = > Might be easier now that Windows PV drivers are opened up? > = > Roger: > * Refactor Linux hotplug scripts > = > You did some of this I think? > = > Ian C: > = > * XL to XCP VM motion > = > Perhaps this could be broadened into VM transport between XL and > other things too -- e.g. libvirt? > = > Stefano: > = > * VM Snapshots > = > Still a good project I think > = > George: > = > * Allowing guests to boot with a passed-through GPU as the primary > display > = > This seems like a bit of a rathole for a GSoC student to me... > = > * Advanced Scheduling Parameters > = > Still to do? > = > Santosh: > = > * KDD (Windows Debugger Stub) enhancements > = > Dave > = > * Create a tiny VM for easy load testing > = > Someone was looking at this I think? > = > Ian J: > = > * Testing PV and HVM installs of Debian using debian-installer > * Testing NetBSD > = > BSD is done I think, and I'm looking at Debian Installer stuff > myself. I've removed these. > = > = > Phew! > Ian. > = > = > = > > Lars > > = > > On 20/01/2014 09:18, Lars Kurth wrote: > > > Hi all, > > > > > > the GSoC application deadline is coming up : Feb 2014. If we want to = > > > have any chance of getting accepted this year, we ought to get our = > > > project list into good shape. The project list and how the project an= d = > > > menters present themselves has a bigger impact on whether we get = > > > accepted than the actual application. > > > > > > Also, I would like to add a mentor section this year: a short bio, = > > > what the mentor cares about and a picture. This will help make the = > > > project list more real. > > > > > > We have *4 weeks* to do this. The bar for GSoC has been getting = > > > increasingly high. I know, we are tied down with Xen 4.4, but this is = > > > something you need to do if you want the Xen Project to participate. > > > > > > a) Please, update = > > > http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently = > > > (these need to be in good shape *before* the application). What I nee= d = > > > you to do is: > > > a.1) Remove items that are done > > > a.2) Add new work items : we ought to have a few sexy topics on say = > > > Real-time, mobile and some of the other segments (assuming we can get= HW) > > > a.3) All project proposals need to be peer reviewed *and* clear ... = > > > The peer review process for projects we put in place last year worked = > > > well, by which we had past mentors sign of project proposals that wer= e = > > > in good enough state. > > > > > > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, shoul= d = > > > get these listed on the respective other programs. And we should link = > > > to these from our project page. > > > > > > Best Regards > > > Lars > > > P.S.: I will also see whether we can participate as Xen Project under = > > > the LF GSoC program, but last year there was push-back and I don't = > > > expect this to change > > > > > = > > = > > _______________________________________________ > > Xen-devel mailing list > > Xen-devel@lists.xen.org > > http://lists.xen.org/xen-devel > = > = _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iZ-EV; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3VH-0003pp-Ca for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:31:03 +0000 Received: from [85.158.137.68:12052] by server-10.bemta-3.messagelabs.com id 88/A0-07302-62B42F25; Wed, 05 Feb 2014 14:31:02 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1391610660!13562168!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2121 invoked from network); 5 Feb 2014 14:31:01 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:31:01 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="100109328" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Feb 2014 14:30:59 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:30:58 -0500 Message-ID: <1391610656.6497.179.camel@kazak.uk.xensource.com> From: Ian Campbell To: Konrad Rzeszutek Wilk Date: Wed, 5 Feb 2014 14:30:56 +0000 In-Reply-To: <20140205142932.GA3946@phenom.dumpdata.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <20140205142932.GA3946@phenom.dumpdata.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Andrew Cooper , Dario Faggioli , Ben Guthro , Santosh Jodh , "xen-api@lists.xen.org" , Ian Jackson , "xen-devel@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, 2014-02-05 at 09:29 -0500, Konrad Rzeszutek Wilk wrote: > On Wed, Feb 05, 2014 at 02:18:40PM +0000, Ben Guthro wrote: > > > > ________________________________________ > > From: Ian Campbell > > Sent: Wednesday, February 05, 2014 9:09 AM > > To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson > > Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org > > Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 > > > > > > > Ben: > > > * dom0 kgdb support > > > > > > Is this for GSoC? > > > > This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here. > > And it actually works! OK, I'll nuke it from the list hten, thanks! > > > > That said, Fri is my last day working for Citrix (and consequently, > on Xen) - and I'll be moving on to a Start-up company again, Good luck! Ian. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002jZ-VU; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBSyr-000290-HU for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 17:43:17 +0000 Received: from [85.158.143.35:9355] by server-2.bemta-4.messagelabs.com id 34/B6-10891-4B9C3F25; Thu, 06 Feb 2014 17:43:16 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1391708594!3717225!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15507 invoked from network); 6 Feb 2014 17:43:16 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 17:43:16 -0000 X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="98664209" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 06 Feb 2014 17:43:14 +0000 Received: from AMSPEX01CL03.citrite.net (10.69.46.34) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server (TLS) id 14.2.342.4; Thu, 6 Feb 2014 12:43:13 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.176]) by AMSPEX01CL03.citrite.net ([10.69.46.34]) with mapi id 14.02.0342.004; Thu, 6 Feb 2014 18:43:12 +0100 From: Paul Durrant To: Santosh Jodh , Ian Campbell , "lars.kurth@xen.org" , "Roger Pau Monne" , Dario Faggioli , Konrad Rzeszutek Wilk , Ben Guthro , Andrew Cooper , Ian Jackson Thread-Topic: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Thread-Index: AQHPInvYpj3b21EIS0q8f9DE1KOLi5qoX58AgAAhFQA= Date: Thu, 6 Feb 2014 17:43:11 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD02270E9@AMSPEX01CL01.citrite.net> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> In-Reply-To: <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.2.29] MIME-Version: 1.0 X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBTYW50b3NoIEpvZGgNCj4gU2Vu dDogMDYgRmVicnVhcnkgMjAxNCAxNjo0NA0KPiBUbzogSWFuIENhbXBiZWxsOyBsYXJzLmt1cnRo QHhlbi5vcmc7IFJvZ2VyIFBhdSBNb25uZTsgRGFyaW8gRmFnZ2lvbGk7DQo+IEtvbnJhZCBSemVz enV0ZWsgV2lsazsgQmVuIEd1dGhybzsgQW5kcmV3IENvb3BlcjsgUGF1bCBEdXJyYW50OyBJYW4N Cj4gSmFja3Nvbg0KPiBDYzogeGVuLWRldmVsQGxpc3RzLnhlbi5vcmc7IHhlbi1hcGlAbGlzdHMu eGVuLm9yZzsgbWlyYWdlb3MtDQo+IGRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnDQo+IFN1Ympl Y3Q6IFJFOiBbWGVuLWRldmVsXSBQcmVwcGluZyBmb3IgR1NPQyAyMDE0IFtVUkdFTlRdIC0gZGVh ZGxpbmUgRmViIDE0DQo+IDIwMTQNCj4gDQo+ID4NCj4gPiBTYW50b3NoOg0KPiA+DQo+ID4gICAg ICAgKiBLREQgKFdpbmRvd3MgRGVidWdnZXIgU3R1YikgZW5oYW5jZW1lbnRzDQo+ID4NCj4gW1Nh bnRvc2ggSm9kaF0gSSBiZWxpZXZlIHRoaXMgaXMgc3RpbGwgYSBnb29kIEdTT0MgcHJvamVjdC4g SG93ZXZlciwgaW4gbGlnaHQgb2YNCj4gbXkgbmV3IGRpcmVjdGlvbiwgSSBhbSBub3Qgc3VyZSBp ZiBJIHdpbGwgYmUgYWJsZSB0byBtZW50b3IuIERvbuKAmXQga25vdyBpZiBQYXVsDQo+IG9yIHNv bWVvbmUgZWxzZSBvbiB0aGUgV2luZG93cyB0ZWFtIHdvdWxkIHdhbnQgdG8gc3BvbnNvciB0aGlz Lg0KPiANCg0KWWVzLCBpdCdzIHN0aWxsIGEgd29ydGh5IHByb2plY3QuIEknZCBiZSBoYXBweSB0 byBzcG9uc29yLg0KDQogIFBhdWwNCg0KPiBSZWdhcmRzLA0KPiBTYW50b3NoDQpfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWls aW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3Rz LnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002j8-SD; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBS3r-00081r-Ph for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 16:44:24 +0000 Received: from [85.158.137.68:3417] by server-6.bemta-3.messagelabs.com id 04/66-09180-7EBB3F25; Thu, 06 Feb 2014 16:44:23 +0000 X-Env-Sender: Santosh.Jodh@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1391705060!129988!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15882 invoked from network); 6 Feb 2014 16:44:22 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 16:44:22 -0000 X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="100520273" Received: from sjcpex01cl03.citrite.net ([10.216.14.145]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 06 Feb 2014 16:44:19 +0000 Received: from SJCPEX01CL01.citrite.net ([169.254.1.22]) by SJCPEX01CL03.citrite.net ([10.216.14.145]) with mapi id 14.02.0342.004; Thu, 6 Feb 2014 08:44:18 -0800 From: Santosh Jodh To: Ian Campbell , "lars.kurth@xen.org" , Roger Pau Monne , Dario Faggioli , Konrad Rzeszutek Wilk , Ben Guthro , Andrew Cooper , Paul Durrant , "Ian Jackson" Thread-Topic: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 Thread-Index: AQHPInvYT66dFluJmUOzBzbhNQgKPZqob1hA Date: Thu, 6 Feb 2014 16:44:18 +0000 Message-ID: <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.2.168] MIME-Version: 1.0 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" , "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org PiANCj4gU2FudG9zaDoNCj4gDQo+ICAgICAgICogS0REIChXaW5kb3dzIERlYnVnZ2VyIFN0dWIp IGVuaGFuY2VtZW50cw0KPiANCltTYW50b3NoIEpvZGhdIEkgYmVsaWV2ZSB0aGlzIGlzIHN0aWxs IGEgZ29vZCBHU09DIHByb2plY3QuIEhvd2V2ZXIsIGluIGxpZ2h0IG9mIG15IG5ldyBkaXJlY3Rp b24sIEkgYW0gbm90IHN1cmUgaWYgSSB3aWxsIGJlIGFibGUgdG8gbWVudG9yLiBEb27igJl0IGtu b3cgaWYgUGF1bCBvciBzb21lb25lIGVsc2Ugb24gdGhlIFdpbmRvd3MgdGVhbSB3b3VsZCB3YW50 IHRvIHNwb25zb3IgdGhpcy4NCg0KUmVnYXJkcywNClNhbnRvc2gNCl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlz dApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRwOi8vbGlzdHMueGVucHJv amVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002iy-OX; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3mk-000691-Ta for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:49:07 +0000 Received: from [193.109.254.147:27633] by server-2.bemta-14.messagelabs.com id 0E/7E-01236-26F42F25; Wed, 05 Feb 2014 14:49:06 +0000 X-Env-Sender: Andrew.Cooper3@citrix.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1391611742!2237810!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5738 invoked from network); 5 Feb 2014 14:49:04 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:49:04 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="98225850" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Feb 2014 14:49:02 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:49:01 -0500 Received: from andrewcoop.uk.xensource.com ([10.80.2.18]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1WB3mf-00073Y-KG; Wed, 05 Feb 2014 14:49:01 +0000 Message-ID: <52F24F5D.7020207@citrix.com> Date: Wed, 5 Feb 2014 14:49:01 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10 MIME-Version: 1.0 To: Ian Campbell References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <52F24D4D.7040004@citrix.com> <1391611558.23098.2.camel@kazak.uk.xensource.com> In-Reply-To: <1391611558.23098.2.camel@kazak.uk.xensource.com> X-Enigmail-Version: 1.6 X-DLP: MIA2 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Konrad Rzeszutek Wilk , Dario Faggioli , Ian Jackson , Paul Durrant , Santosh Jodh , "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 05/02/14 14:45, Ian Campbell wrote: > On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote: >> On 05/02/14 14:09, Ian Campbell wrote: >>> Andy: >>> >>> * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA >>> allocations >>> >>> Sounds too hard for a GSoC to me. Would need fleshing out in any >>> case. >> Malcolm made a prototype for this on the first day of the Hackathon. It >> can disappear. > Removed. > >>> * CPU/RAM/PCI diagram tool >>> >>> Does this not already exist somewhere? >> Not as far as I (or my ability to google) am aware. >> >> My furrowing into hwloc interacting with Xen and libxc is a start to all >> of this, but it is still very much in my copious free time and there is >> more than enough other work which could be done if someone were interested. > OK, left in place. > > This could conceivably be done under another umbrella such as the Linux > one too, since it seems generic. > > Ian. > > For native Linux, hwloc kinda already does this already - certainly the CPU and PCI bits. Under Xen there are quite a few areas needing improvement, which will require active development work. ~Andrew _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5m-0002io-Kk; Thu, 06 Feb 2014 17:50:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WB3g5-0005Ba-4k for mirageos-devel@lists.xenproject.org; Wed, 05 Feb 2014 14:42:13 +0000 Received: from [193.109.254.147:46251] by server-4.bemta-14.messagelabs.com id D7/2C-32066-4CD42F25; Wed, 05 Feb 2014 14:42:12 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1391611330!2235902!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10120 invoked from network); 5 Feb 2014 14:42:11 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Feb 2014 14:42:11 -0000 X-IronPort-AV: E=Sophos;i="4.95,786,1384300800"; d="scan'208";a="100114587" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Feb 2014 14:42:10 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Wed, 5 Feb 2014 09:42:09 -0500 Message-ID: <1391611327.6497.181.camel@kazak.uk.xensource.com> From: Ian Campbell To: Konrad Rzeszutek Wilk Date: Wed, 5 Feb 2014 14:42:07 +0000 In-Reply-To: <20140205143402.GB3946@phenom.dumpdata.com> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <20140205143402.GB3946@phenom.dumpdata.com> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: Ben Guthro , mirageos-devel@lists.xenproject.org, Andrew Cooper , Dario Faggioli , Ian Jackson , "xen-devel@lists.xen.org" , Santosh Jodh , "xen-api@lists.xen.org" , Paul Durrant , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, 2014-02-05 at 09:34 -0500, Konrad Rzeszutek Wilk wrote: > > > > * Parallel xenwatch > > > > Bit sparse on details, GSOC == unknown > > That would still be nice. It came from talking to Matt from Amazon. He > was saying that having only one xenwatch thread slows things down for > a medium to big server with lots of guests. Making multiple > xenwatch threads to process XenBus requests in parallel would be > a good improvement. Would need to be careful about exposing cases of insufficient locking in the existing code. > > > > > * Microcode uploader implementation > > > > Done I think? > > Nuked > > * Performance tools overhaul > > > > Bit vague. And has some of this been done? > > I can't remember what that is. OK, I nuked it -- a new project can always be added if you remember what it was. > > > > * "Upstream bugs" > > > > There were 4 of these, dating back to 2012, I don't think this > > list is a good place to track bugs and it seems like at least > > some of them are now obsolete. So I've nuked the lot. If they > > are still relevant I think it would be best to get them into the > > bug tracker. > > OK, lets nuke them. Done. > > We could also add the: > > VCPUOP_register_vcpu_time_memory_area support in Linux upstream kernel. > > MSI multi-vector for Linux upstream kernel. > > Thought those are mostly just putting pieces together and repost them > so no "new" development. Not really suitable for this list then IMHO. Ian. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Feb 06 17:50:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 06 Feb 2014 17:50: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 1WBT5n-0002jg-1l; Thu, 06 Feb 2014 17:50:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WBSzz-0002F3-Qb for mirageos-devel@lists.xenproject.org; Thu, 06 Feb 2014 17:44:28 +0000 Received: from [193.109.254.147:34869] by server-11.bemta-14.messagelabs.com id B4/99-24604-BF9C3F25; Thu, 06 Feb 2014 17:44:27 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1391708664!2557418!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6830 invoked from network); 6 Feb 2014 17:44:26 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Feb 2014 17:44:26 -0000 X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="100540386" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 06 Feb 2014 17:44:08 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Thu, 6 Feb 2014 12:44:08 -0500 Message-ID: <1391708646.2162.12.camel@kazak.uk.xensource.com> From: Ian Campbell To: Paul Durrant Date: Thu, 6 Feb 2014 17:44:06 +0000 In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD02270E9@AMSPEX01CL01.citrite.net> References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org> <1391609348.6497.178.camel@kazak.uk.xensource.com> <722BF1F4E241B546BB147E89923C56DF15BB63D2@SJCPEX01CL01.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD02270E9@AMSPEX01CL01.citrite.net> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 X-Mailman-Approved-At: Thu, 06 Feb 2014 17:50:25 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Konrad Rzeszutek Wilk , Andrew Cooper , Dario Faggioli , Ben Guthro , Santosh Jodh , "xen-api@lists.xen.org" , Ian Jackson , "xen-devel@lists.xen.org" , Roger Pau Monne Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gVGh1LCAyMDE0LTAyLTA2IGF0IDE3OjQzICswMDAwLCBQYXVsIER1cnJhbnQgd3JvdGU6Cj4g PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQo+ID4gRnJvbTogU2FudG9zaCBKb2RoCj4gPiBT ZW50OiAwNiBGZWJydWFyeSAyMDE0IDE2OjQ0Cj4gPiBUbzogSWFuIENhbXBiZWxsOyBsYXJzLmt1 cnRoQHhlbi5vcmc7IFJvZ2VyIFBhdSBNb25uZTsgRGFyaW8gRmFnZ2lvbGk7Cj4gPiBLb25yYWQg Unplc3p1dGVrIFdpbGs7IEJlbiBHdXRocm87IEFuZHJldyBDb29wZXI7IFBhdWwgRHVycmFudDsg SWFuCj4gPiBKYWNrc29uCj4gPiBDYzogeGVuLWRldmVsQGxpc3RzLnhlbi5vcmc7IHhlbi1hcGlA bGlzdHMueGVuLm9yZzsgbWlyYWdlb3MtCj4gPiBkZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwo+ ID4gU3ViamVjdDogUkU6IFtYZW4tZGV2ZWxdIFByZXBwaW5nIGZvciBHU09DIDIwMTQgW1VSR0VO VF0gLSBkZWFkbGluZSBGZWIgMTQKPiA+IDIwMTQKPiA+IAo+ID4gPgo+ID4gPiBTYW50b3NoOgo+ ID4gPgo+ID4gPiAgICAgICAqIEtERCAoV2luZG93cyBEZWJ1Z2dlciBTdHViKSBlbmhhbmNlbWVu dHMKPiA+ID4KPiA+IFtTYW50b3NoIEpvZGhdIEkgYmVsaWV2ZSB0aGlzIGlzIHN0aWxsIGEgZ29v ZCBHU09DIHByb2plY3QuIEhvd2V2ZXIsIGluIGxpZ2h0IG9mCj4gPiBteSBuZXcgZGlyZWN0aW9u LCBJIGFtIG5vdCBzdXJlIGlmIEkgd2lsbCBiZSBhYmxlIHRvIG1lbnRvci4gRG9u4oCZdCBrbm93 IGlmIFBhdWwKPiA+IG9yIHNvbWVvbmUgZWxzZSBvbiB0aGUgV2luZG93cyB0ZWFtIHdvdWxkIHdh bnQgdG8gc3BvbnNvciB0aGlzLgo+ID4gCj4gCj4gWWVzLCBpdCdzIHN0aWxsIGEgd29ydGh5IHBy b2plY3QuIEknZCBiZSBoYXBweSB0byBzcG9uc29yLgoKRG8geW91IG1lYW4gIm1lbnRvciI/CgpD YW4geW91IHVwZGF0ZSBodGUgcHJvamVjdCBvbiB0aGUgd2lraSBwbGVhc2UuCgpJYW4uCgoKCl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9TLWRl dmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpodHRw Oi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFnZW9z LWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Sun Feb 09 18:12:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 09 Feb 2014 18:12: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 1WCYra-0005NT-2o; Sun, 09 Feb 2014 18:12:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCYrY-0005NO-Uk for mirageos-devel@lists.xenproject.org; Sun, 09 Feb 2014 18:12:17 +0000 Received: from [85.158.143.35:46097] by server-3.bemta-4.messagelabs.com id 7F/F9-11539-005C7F25; Sun, 09 Feb 2014 18:12:16 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-21.messagelabs.com!1391969535!4314647!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7698 invoked from network); 9 Feb 2014 18:12:15 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-21.messagelabs.com with SMTP; 9 Feb 2014 18:12:15 -0000 Received: (qmail 13782 invoked by uid 634); 9 Feb 2014 18:12:14 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 09 Feb 2014 18:12:14 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> Date: Sun, 9 Feb 2014 18:12:13 +0000 Message-Id: References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 20:20, Richard Mortier wrote: > > i will have a PR for mirage-skeleton ready soon (maybe this evening). have been working through trying to organise & update the samples as well as incorporate the extra ones from fosdem. i'll see if i can get balraj's examples in there too. > I've just merged your examples in after verifying that they all build on Unix and Xen. A couple of minor bugs cropped up: - We dont seem to include mirage-clock-unix by default, so the ethif example fails on Unix (but not Xen, where its an implicit dependency of the console). Thomas -- should mirage-clock-unix by unconditionally added, since it's not an explicit device driver at the moment? See my fixes here: https://github.com/mirage/mirage-skeleton/commit/95e826ce134f608f943364e212f7e8b083bbe7a0 - The stackv4 example used both the socket and direct backends, which obviously fails to build on Xen. I used Mirage.get_mode() to make the socket backend conditional on being compiled onto Unix. This exposed a small bug in the mirage command-line tool which I fixed here: https://github.com/mirage/mirage/pull/212 Other than that, just the mirage-www examples to update before releasing now. I've pushed a new 1.1.0 tag to reflect the last bugfix above. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 09 18:12:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 09 Feb 2014 18:12: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 1WCYra-0005NT-2o; Sun, 09 Feb 2014 18:12:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCYrY-0005NO-Uk for mirageos-devel@lists.xenproject.org; Sun, 09 Feb 2014 18:12:17 +0000 Received: from [85.158.143.35:46097] by server-3.bemta-4.messagelabs.com id 7F/F9-11539-005C7F25; Sun, 09 Feb 2014 18:12:16 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-21.messagelabs.com!1391969535!4314647!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7698 invoked from network); 9 Feb 2014 18:12:15 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-21.messagelabs.com with SMTP; 9 Feb 2014 18:12:15 -0000 Received: (qmail 13782 invoked by uid 634); 9 Feb 2014 18:12:14 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 09 Feb 2014 18:12:14 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> Date: Sun, 9 Feb 2014 18:12:13 +0000 Message-Id: References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 5 Feb 2014, at 20:20, Richard Mortier wrote: > > i will have a PR for mirage-skeleton ready soon (maybe this evening). have been working through trying to organise & update the samples as well as incorporate the extra ones from fosdem. i'll see if i can get balraj's examples in there too. > I've just merged your examples in after verifying that they all build on Unix and Xen. A couple of minor bugs cropped up: - We dont seem to include mirage-clock-unix by default, so the ethif example fails on Unix (but not Xen, where its an implicit dependency of the console). Thomas -- should mirage-clock-unix by unconditionally added, since it's not an explicit device driver at the moment? See my fixes here: https://github.com/mirage/mirage-skeleton/commit/95e826ce134f608f943364e212f7e8b083bbe7a0 - The stackv4 example used both the socket and direct backends, which obviously fails to build on Xen. I used Mirage.get_mode() to make the socket backend conditional on being compiled onto Unix. This exposed a small bug in the mirage command-line tool which I fixed here: https://github.com/mirage/mirage/pull/212 Other than that, just the mirage-www examples to update before releasing now. I've pushed a new 1.1.0 tag to reflect the last bugfix above. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 09 18:18:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 09 Feb 2014 18:18:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCYxA-0005P7-Hs; Sun, 09 Feb 2014 18:18:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCYx9-0005P2-Hh for mirageos-devel@lists.xenproject.org; Sun, 09 Feb 2014 18:18:03 +0000 Received: from [85.158.137.68:60659] by server-12.bemta-3.messagelabs.com id 0E/BC-01674-A56C7F25; Sun, 09 Feb 2014 18:18:02 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-15.tower-31.messagelabs.com!1391969881!667021!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32563 invoked from network); 9 Feb 2014 18:18:01 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-15.tower-31.messagelabs.com with SMTP; 9 Feb 2014 18:18:01 -0000 Received: (qmail 2740 invoked from network); 9 Feb 2014 18:18:20 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 9 Feb 2014 18:18:20 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 31613-10 for ; Sun, 9 Feb 2014 18:18:18 +0000 (GMT) Received: (qmail 2722 invoked by uid 599); 9 Feb 2014 18:18:18 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 09 Feb 2014 18:18:18 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WCYx4-0000on-Ea; Sun, 09 Feb 2014 18:17:58 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 9 Feb 2014 18:17:57 +0000 Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: Ac8lw0J3yVxgKHelSLGrvhFV/4rY5w== Message-ID: <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2014, at 18:12, Anil Madhavapeddy wrote: > On 5 Feb 2014, at 20:20, Richard Mortier wrote: >> >> i will have a PR for mirage-skeleton ready soon (maybe this evening). have been working through trying to organise & update the samples as well as incorporate the extra ones from fosdem. i'll see if i can get balraj's examples in there too. >> > > I've just merged your examples in after verifying that they all build on Unix and Xen. A couple of minor bugs cropped up: > > - We dont seem to include mirage-clock-unix by default, so the ethif example fails on Unix (but not Xen, where its an implicit dependency of the console). Thomas -- should mirage-clock-unix by unconditionally added, since it's not an explicit device driver at the moment? See my fixes here: https://github.com/mirage/mirage-skeleton/commit/95e826ce134f608f943364e212f7e8b083bbe7a0 ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) > - The stackv4 example used both the socket and direct backends, which obviously fails to build on Xen. I used Mirage.get_mode() to make the socket backend conditional on being compiled onto Unix. This exposed a small bug in the mirage command-line tool which I fixed here: https://github.com/mirage/mirage/pull/212 > > Other than that, just the mirage-www examples to update before releasing now. I've pushed a new 1.1.0 tag to reflect the last bugfix above. ack. i need to make sure the PR for my fixes to the generation of make-fatN-image.sh has been merged too... -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 09 18:18:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 09 Feb 2014 18:18:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCYxA-0005P7-Hs; Sun, 09 Feb 2014 18:18:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCYx9-0005P2-Hh for mirageos-devel@lists.xenproject.org; Sun, 09 Feb 2014 18:18:03 +0000 Received: from [85.158.137.68:60659] by server-12.bemta-3.messagelabs.com id 0E/BC-01674-A56C7F25; Sun, 09 Feb 2014 18:18:02 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-15.tower-31.messagelabs.com!1391969881!667021!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32563 invoked from network); 9 Feb 2014 18:18:01 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-15.tower-31.messagelabs.com with SMTP; 9 Feb 2014 18:18:01 -0000 Received: (qmail 2740 invoked from network); 9 Feb 2014 18:18:20 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 9 Feb 2014 18:18:20 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 31613-10 for ; Sun, 9 Feb 2014 18:18:18 +0000 (GMT) Received: (qmail 2722 invoked by uid 599); 9 Feb 2014 18:18:18 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 09 Feb 2014 18:18:18 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WCYx4-0000on-Ea; Sun, 09 Feb 2014 18:17:58 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 9 Feb 2014 18:17:57 +0000 Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: Ac8lw0J3yVxgKHelSLGrvhFV/4rY5w== Message-ID: <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2014, at 18:12, Anil Madhavapeddy wrote: > On 5 Feb 2014, at 20:20, Richard Mortier wrote: >> >> i will have a PR for mirage-skeleton ready soon (maybe this evening). have been working through trying to organise & update the samples as well as incorporate the extra ones from fosdem. i'll see if i can get balraj's examples in there too. >> > > I've just merged your examples in after verifying that they all build on Unix and Xen. A couple of minor bugs cropped up: > > - We dont seem to include mirage-clock-unix by default, so the ethif example fails on Unix (but not Xen, where its an implicit dependency of the console). Thomas -- should mirage-clock-unix by unconditionally added, since it's not an explicit device driver at the moment? See my fixes here: https://github.com/mirage/mirage-skeleton/commit/95e826ce134f608f943364e212f7e8b083bbe7a0 ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) > - The stackv4 example used both the socket and direct backends, which obviously fails to build on Xen. I used Mirage.get_mode() to make the socket backend conditional on being compiled onto Unix. This exposed a small bug in the mirage command-line tool which I fixed here: https://github.com/mirage/mirage/pull/212 > > Other than that, just the mirage-www examples to update before releasing now. I've pushed a new 1.1.0 tag to reflect the last bugfix above. ack. i need to make sure the PR for my fixes to the generation of make-fatN-image.sh has been merged too... -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 09 18:24:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 09 Feb 2014 18:24:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCZ3p-0005n5-5i; Sun, 09 Feb 2014 18:24:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCZ3n-0005n0-RX for mirageos-devel@lists.xenproject.org; Sun, 09 Feb 2014 18:24:56 +0000 Received: from [85.158.143.35:28202] by server-3.bemta-4.messagelabs.com id 6E/1E-11539-7F7C7F25; Sun, 09 Feb 2014 18:24:55 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1391970292!4295121!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27154 invoked from network); 9 Feb 2014 18:24:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-21.messagelabs.com with SMTP; 9 Feb 2014 18:24:52 -0000 Received: (qmail 26735 invoked by uid 634); 9 Feb 2014 18:24:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 09 Feb 2014 18:24:51 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> Date: Sun, 9 Feb 2014 18:24:52 +0000 Message-Id: <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2014, at 18:17, Richard Mortier wrote: > > On 9 Feb 2014, at 18:12, Anil Madhavapeddy wrote: > >> On 5 Feb 2014, at 20:20, Richard Mortier wrote: >>> >>> i will have a PR for mirage-skeleton ready soon (maybe this evening). have been working through trying to organise & update the samples as well as incorporate the extra ones from fosdem. i'll see if i can get balraj's examples in there too. >>> >> >> I've just merged your examples in after verifying that they all build on Unix and Xen. A couple of minor bugs cropped up: >> >> - We dont seem to include mirage-clock-unix by default, so the ethif example fails on Unix (but not Xen, where its an implicit dependency of the console). Thomas -- should mirage-clock-unix by unconditionally added, since it's not an explicit device driver at the moment? See my fixes here: https://github.com/mirage/mirage-skeleton/commit/95e826ce134f608f943364e212f7e8b083bbe7a0 > > ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. > >> - The stackv4 example used both the socket and direct backends, which obviously fails to build on Xen. I used Mirage.get_mode() to make the socket backend conditional on being compiled onto Unix. This exposed a small bug in the mirage command-line tool which I fixed here: https://github.com/mirage/mirage/pull/212 >> >> Other than that, just the mirage-www examples to update before releasing now. I've pushed a new 1.1.0 tag to reflect the last bugfix above. > > ack. i need to make sure the PR for my fixes to the generation of make-fatN-image.sh has been merged too... Woops, I did not merge that. Doing so now, and I'll slip the 1.1.0 tag again then. Is there a example of using this in mirage-skeleton? -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 09 18:24:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 09 Feb 2014 18:24:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCZ3p-0005n5-5i; Sun, 09 Feb 2014 18:24:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCZ3n-0005n0-RX for mirageos-devel@lists.xenproject.org; Sun, 09 Feb 2014 18:24:56 +0000 Received: from [85.158.143.35:28202] by server-3.bemta-4.messagelabs.com id 6E/1E-11539-7F7C7F25; Sun, 09 Feb 2014 18:24:55 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1391970292!4295121!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27154 invoked from network); 9 Feb 2014 18:24:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-21.messagelabs.com with SMTP; 9 Feb 2014 18:24:52 -0000 Received: (qmail 26735 invoked by uid 634); 9 Feb 2014 18:24:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 09 Feb 2014 18:24:51 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> Date: Sun, 9 Feb 2014 18:24:52 +0000 Message-Id: <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2014, at 18:17, Richard Mortier wrote: > > On 9 Feb 2014, at 18:12, Anil Madhavapeddy wrote: > >> On 5 Feb 2014, at 20:20, Richard Mortier wrote: >>> >>> i will have a PR for mirage-skeleton ready soon (maybe this evening). have been working through trying to organise & update the samples as well as incorporate the extra ones from fosdem. i'll see if i can get balraj's examples in there too. >>> >> >> I've just merged your examples in after verifying that they all build on Unix and Xen. A couple of minor bugs cropped up: >> >> - We dont seem to include mirage-clock-unix by default, so the ethif example fails on Unix (but not Xen, where its an implicit dependency of the console). Thomas -- should mirage-clock-unix by unconditionally added, since it's not an explicit device driver at the moment? See my fixes here: https://github.com/mirage/mirage-skeleton/commit/95e826ce134f608f943364e212f7e8b083bbe7a0 > > ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. > >> - The stackv4 example used both the socket and direct backends, which obviously fails to build on Xen. I used Mirage.get_mode() to make the socket backend conditional on being compiled onto Unix. This exposed a small bug in the mirage command-line tool which I fixed here: https://github.com/mirage/mirage/pull/212 >> >> Other than that, just the mirage-www examples to update before releasing now. I've pushed a new 1.1.0 tag to reflect the last bugfix above. > > ack. i need to make sure the PR for my fixes to the generation of make-fatN-image.sh has been merged too... Woops, I did not merge that. Doing so now, and I'll slip the 1.1.0 tag again then. Is there a example of using this in mirage-skeleton? -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 09 19:00:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 09 Feb 2014 19:00:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCZcX-0007Kr-UX; Sun, 09 Feb 2014 19:00:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCZcV-0007Km-VE for mirageos-devel@lists.xenproject.org; Sun, 09 Feb 2014 19:00:48 +0000 Received: from [85.158.143.35:28708] by server-3.bemta-4.messagelabs.com id C5/0B-11539-F50D7F25; Sun, 09 Feb 2014 19:00:47 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1391972446!4321748!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10956 invoked from network); 9 Feb 2014 19:00:46 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-14.tower-21.messagelabs.com with SMTP; 9 Feb 2014 19:00:46 -0000 Received: (qmail 20026 invoked from network); 9 Feb 2014 19:00:41 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 9 Feb 2014 19:00:41 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 18144-09 for ; Sun, 9 Feb 2014 19:00:41 +0000 (GMT) Received: (qmail 19994 invoked by uid 599); 9 Feb 2014 19:00:41 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 09 Feb 2014 19:00:41 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WCZcR-0001XB-VF; Sun, 09 Feb 2014 19:00:43 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 9 Feb 2014 19:00:42 +0000 Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: Ac8lyTsqcuEEbkqxT7qitACHzU80OA== Message-ID: References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> In-Reply-To: <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2014, at 18:24, Anil Madhavapeddy wrote: > On 9 Feb 2014, at 18:17, Richard Mortier wrote: > >> ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) > > Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. > > The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. this was after a "rm -rf ~/.opam" etc -- trying again from clean. >> ack. i need to make sure the PR for my fixes to the generation of make-fatN-image.sh has been merged too... > > Woops, I did not merge that. Doing so now, and I'll slip the 1.1.0 tag again then. :) > Is there a example of using this in mirage-skeleton? no not fixed the website or storage examples yet. currently focused on finally getting my website working on xen (it works on unix currently) so i can make it live. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Feb 09 19:00:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 09 Feb 2014 19:00:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCZcX-0007Kr-UX; Sun, 09 Feb 2014 19:00:49 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCZcV-0007Km-VE for mirageos-devel@lists.xenproject.org; Sun, 09 Feb 2014 19:00:48 +0000 Received: from [85.158.143.35:28708] by server-3.bemta-4.messagelabs.com id C5/0B-11539-F50D7F25; Sun, 09 Feb 2014 19:00:47 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1391972446!4321748!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10956 invoked from network); 9 Feb 2014 19:00:46 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-14.tower-21.messagelabs.com with SMTP; 9 Feb 2014 19:00:46 -0000 Received: (qmail 20026 invoked from network); 9 Feb 2014 19:00:41 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 9 Feb 2014 19:00:41 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 18144-09 for ; Sun, 9 Feb 2014 19:00:41 +0000 (GMT) Received: (qmail 19994 invoked by uid 599); 9 Feb 2014 19:00:41 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 09 Feb 2014 19:00:41 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1WCZcR-0001XB-VF; Sun, 09 Feb 2014 19:00:43 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 9 Feb 2014 19:00:42 +0000 Thread-Topic: [MirageOS-devel] Mirage 1.1.0 pull req Thread-Index: Ac8lyTsqcuEEbkqxT7qitACHzU80OA== Message-ID: References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> In-Reply-To: <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2014, at 18:24, Anil Madhavapeddy wrote: > On 9 Feb 2014, at 18:17, Richard Mortier wrote: > >> ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) > > Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. > > The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. this was after a "rm -rf ~/.opam" etc -- trying again from clean. >> ack. i need to make sure the PR for my fixes to the generation of make-fatN-image.sh has been merged too... > > Woops, I did not merge that. Doing so now, and I'll slip the 1.1.0 tag again then. :) > Is there a example of using this in mirage-skeleton? no not fixed the website or storage examples yet. currently focused on finally getting my website working on xen (it works on unix currently) so i can make it live. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 10:08:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 10:08: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 1WCnmj-0001ju-2d; Mon, 10 Feb 2014 10:08:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCnmh-0001jo-5w for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 10:08:15 +0000 Received: from [193.109.254.147:60196] by server-14.bemta-14.messagelabs.com id 42/D1-29228-E05A8F25; Mon, 10 Feb 2014 10:08:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1392026893!3211094!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3431 invoked from network); 10 Feb 2014 10:08:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-27.messagelabs.com with SMTP; 10 Feb 2014 10:08:13 -0000 Received: (qmail 32390 invoked by uid 634); 10 Feb 2014 10:08:12 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-102-120.in-addr.btopenworld.com (HELO [10.0.0.109]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 10 Feb 2014 10:08:11 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 10 Feb 2014 10:08:10 +0000 Message-Id: <94B21275-1A29-4487-B712-413758648B87@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2014, at 19:00, Richard Mortier wrote: > > On 9 Feb 2014, at 18:24, Anil Madhavapeddy wrote: > >> On 9 Feb 2014, at 18:17, Richard Mortier wrote: >> >>> ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) >> >> Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. >> >> The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. > > this was after a "rm -rf ~/.opam" etc -- trying again from clean. In that case, can you reproduce on Travis from a clean installation? That'd greatly help debug it. > >>> ack. i need to make sure the PR for my fixes to the generation of make-fatN-image.sh has been merged too... >> >> Woops, I did not merge that. Doing so now, and I'll slip the 1.1.0 tag again then. > > :) > >> Is there a example of using this in mirage-skeleton? > > no not fixed the website or storage examples yet. currently focused on finally getting my website working on xen (it works on unix currently) so i can make it live. Ack. I'd like to make a 'mir-homepage' binary that converts a directory right into a EC2-bootable (i.e. pvgrub) block device, so I'm planning on looking at it later this week. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 10:08:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 10:08: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 1WCnmj-0001ju-2d; Mon, 10 Feb 2014 10:08:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCnmh-0001jo-5w for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 10:08:15 +0000 Received: from [193.109.254.147:60196] by server-14.bemta-14.messagelabs.com id 42/D1-29228-E05A8F25; Mon, 10 Feb 2014 10:08:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1392026893!3211094!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3431 invoked from network); 10 Feb 2014 10:08:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-27.messagelabs.com with SMTP; 10 Feb 2014 10:08:13 -0000 Received: (qmail 32390 invoked by uid 634); 10 Feb 2014 10:08:12 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-102-120.in-addr.btopenworld.com (HELO [10.0.0.109]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 10 Feb 2014 10:08:11 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 10 Feb 2014 10:08:10 +0000 Message-Id: <94B21275-1A29-4487-B712-413758648B87@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Feb 2014, at 19:00, Richard Mortier wrote: > > On 9 Feb 2014, at 18:24, Anil Madhavapeddy wrote: > >> On 9 Feb 2014, at 18:17, Richard Mortier wrote: >> >>> ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) >> >> Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. >> >> The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. > > this was after a "rm -rf ~/.opam" etc -- trying again from clean. In that case, can you reproduce on Travis from a clean installation? That'd greatly help debug it. > >>> ack. i need to make sure the PR for my fixes to the generation of make-fatN-image.sh has been merged too... >> >> Woops, I did not merge that. Doing so now, and I'll slip the 1.1.0 tag again then. > > :) > >> Is there a example of using this in mirage-skeleton? > > no not fixed the website or storage examples yet. currently focused on finally getting my website working on xen (it works on unix currently) so i can make it live. Ack. I'd like to make a 'mir-homepage' binary that converts a directory right into a EC2-bootable (i.e. pvgrub) block device, so I'm planning on looking at it later this week. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 10:15:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 10:15:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCntQ-0002OU-Br; Mon, 10 Feb 2014 10:15:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCntP-0002OO-KN for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 10:15:11 +0000 Received: from [193.109.254.147:26725] by server-10.bemta-14.messagelabs.com id 9A/A1-10711-EA6A8F25; Mon, 10 Feb 2014 10:15:10 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1392027304!3181668!1 X-Originating-IP: [209.85.220.42] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11508 invoked from network); 10 Feb 2014 10:15:07 -0000 Received: from mail-pa0-f42.google.com (HELO mail-pa0-f42.google.com) (209.85.220.42) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2014 10:15:07 -0000 Received: by mail-pa0-f42.google.com with SMTP id kl14so6011673pab.29 for ; Mon, 10 Feb 2014 02:15:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hvaQYV7U9menatQI4/B7pLaj/6lgp3GDsJOJ1A83JlQ=; b=nxMEc9htftkVwJy9bbrnZ0E6HuKM/5Bl30FVUcR1NcIAJyEC06IO5X2bZPEg3Time0 zscpDYME5OkZxQPbblh5ExxlyLTN2R32yjdwQ6+HUX6vjreSTs3kYO5FxPpmfc2+BONc PHSP0vNwTbcnqSSSgRXa1j/nWn+tKJcGDsEoCSqT2m66D9ysX4plLaxH3uuBNlyGe6EI TArsuyK7sCyezH9z0cP2aujW0V3m/9WGKe2+wxBFrDyt0xIVQoku+C4DXDKgsXjp2iOu LFf7MIJ3HFI95vvZFvl2VHKWCjfFpO9dt0P69jMB9ltq73xBeAgjNWjmFpPxzWDqLatj OaPg== MIME-Version: 1.0 X-Received: by 10.66.158.132 with SMTP id wu4mr24918658pab.66.1392027303873; Mon, 10 Feb 2014 02:15:03 -0800 (PST) Received: by 10.70.55.132 with HTTP; Mon, 10 Feb 2014 02:15:03 -0800 (PST) In-Reply-To: <94B21275-1A29-4487-B712-413758648B87@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> <94B21275-1A29-4487-B712-413758648B87@recoil.org> Date: Mon, 10 Feb 2014 10:15:03 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2746777389202391689==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2746777389202391689== Content-Type: multipart/alternative; boundary=047d7bacc1a0f7126304f20a9cdf --047d7bacc1a0f7126304f20a9cdf Content-Type: text/plain; charset=ISO-8859-1 > > > Ack. I'd like to make a 'mir-homepage' binary that converts a directory > right into a EC2-bootable (i.e. pvgrub) block device, so I'm planning on > looking at it later this week. > For code that can create a grub-bootable image, see https://github.com/jonludlam/xen-testvm/pull/7 in particular https://github.com/djs55/xen-testvm/commit/1fa304b721d496597b800d41a604de692b344398 Cheers, Dave --047d7bacc1a0f7126304f20a9cdf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Ack. =A0I'd like to make a 'mir-homepage' binary that con= verts a directory right into a EC2-bootable (i.e. pvgrub) block device, so = I'm planning on looking at it later this week.

For code that can create a grub-bootable image, see

--047d7bacc1a0f7126304f20a9cdf-- --===============2746777389202391689== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2746777389202391689==-- From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 10:15:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 10:15:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCntQ-0002OU-Br; Mon, 10 Feb 2014 10:15:12 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCntP-0002OO-KN for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 10:15:11 +0000 Received: from [193.109.254.147:26725] by server-10.bemta-14.messagelabs.com id 9A/A1-10711-EA6A8F25; Mon, 10 Feb 2014 10:15:10 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1392027304!3181668!1 X-Originating-IP: [209.85.220.42] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11508 invoked from network); 10 Feb 2014 10:15:07 -0000 Received: from mail-pa0-f42.google.com (HELO mail-pa0-f42.google.com) (209.85.220.42) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 10 Feb 2014 10:15:07 -0000 Received: by mail-pa0-f42.google.com with SMTP id kl14so6011673pab.29 for ; Mon, 10 Feb 2014 02:15:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hvaQYV7U9menatQI4/B7pLaj/6lgp3GDsJOJ1A83JlQ=; b=nxMEc9htftkVwJy9bbrnZ0E6HuKM/5Bl30FVUcR1NcIAJyEC06IO5X2bZPEg3Time0 zscpDYME5OkZxQPbblh5ExxlyLTN2R32yjdwQ6+HUX6vjreSTs3kYO5FxPpmfc2+BONc PHSP0vNwTbcnqSSSgRXa1j/nWn+tKJcGDsEoCSqT2m66D9ysX4plLaxH3uuBNlyGe6EI TArsuyK7sCyezH9z0cP2aujW0V3m/9WGKe2+wxBFrDyt0xIVQoku+C4DXDKgsXjp2iOu LFf7MIJ3HFI95vvZFvl2VHKWCjfFpO9dt0P69jMB9ltq73xBeAgjNWjmFpPxzWDqLatj OaPg== MIME-Version: 1.0 X-Received: by 10.66.158.132 with SMTP id wu4mr24918658pab.66.1392027303873; Mon, 10 Feb 2014 02:15:03 -0800 (PST) Received: by 10.70.55.132 with HTTP; Mon, 10 Feb 2014 02:15:03 -0800 (PST) In-Reply-To: <94B21275-1A29-4487-B712-413758648B87@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> <94B21275-1A29-4487-B712-413758648B87@recoil.org> Date: Mon, 10 Feb 2014 10:15:03 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2746777389202391689==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2746777389202391689== Content-Type: multipart/alternative; boundary=047d7bacc1a0f7126304f20a9cdf --047d7bacc1a0f7126304f20a9cdf Content-Type: text/plain; charset=ISO-8859-1 > > > Ack. I'd like to make a 'mir-homepage' binary that converts a directory > right into a EC2-bootable (i.e. pvgrub) block device, so I'm planning on > looking at it later this week. > For code that can create a grub-bootable image, see https://github.com/jonludlam/xen-testvm/pull/7 in particular https://github.com/djs55/xen-testvm/commit/1fa304b721d496597b800d41a604de692b344398 Cheers, Dave --047d7bacc1a0f7126304f20a9cdf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable --047d7bacc1a0f7126304f20a9cdf-- --===============2746777389202391689== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2746777389202391689==-- From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 10:30:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 10:30: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 1WCo8b-0003XE-Pc; Mon, 10 Feb 2014 10:30:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCo8a-0003X9-PM for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 10:30:52 +0000 Received: from [85.158.143.35:32696] by server-2.bemta-4.messagelabs.com id 4B/75-10891-C5AA8F25; Mon, 10 Feb 2014 10:30:52 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1392028251!4441301!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23582 invoked from network); 10 Feb 2014 10:30:51 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-21.messagelabs.com with SMTP; 10 Feb 2014 10:30:51 -0000 Received: (qmail 21478 invoked by uid 634); 10 Feb 2014 10:30:50 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from host81-149-102-120.in-addr.btopenworld.com (HELO [10.0.0.109]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 10 Feb 2014 10:30:49 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 10 Feb 2014 10:30:49 +0000 Message-Id: <02AE776C-C431-4080-A7F5-F9D04D124FE4@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> <94B21275-1A29-4487-B712-413758648B87@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2324967168060265610==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2324967168060265610== Content-Type: multipart/alternative; boundary="Apple-Mail=_FC14781B-43AC-49E4-BC2C-2C117E47A29F" --Apple-Mail=_FC14781B-43AC-49E4-BC2C-2C117E47A29F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 10 Feb 2014, at 10:15, David Scott wrote: >=20 > Ack. I'd like to make a 'mir-homepage' binary that converts a = directory right into a EC2-bootable (i.e. pvgrub) block device, so I'm = planning on looking at it later this week. >=20 > For code that can create a grub-bootable image, see >=20 > https://github.com/jonludlam/xen-testvm/pull/7 >=20 > in particular >=20 > = https://github.com/djs55/xen-testvm/commit/1fa304b721d496597b800d41a604de6= 92b344398 Lovely, thanks. We now have=20 https://github.com/mirage/mirage/issues/214 that tracks this. cheers, Anil= --Apple-Mail=_FC14781B-43AC-49E4-BC2C-2C117E47A29F Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1 On 10 Feb 2014, at 10:15, David Scott <scott.dj@gmail.com> wrote:


Ack.  I'd like to make a 'mir-homepage' binary that converts a directory right into a EC2-bootable (i.e. pvgrub) block device, so I'm planning on looking at it later this week.

For code that can create a grub-bootable image, see


in particular


Lovely, thanks. We now have 

that tracks this.

cheers,
Anil
--Apple-Mail=_FC14781B-43AC-49E4-BC2C-2C117E47A29F-- --===============2324967168060265610== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2324967168060265610==-- From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 10:30:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 10:30: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 1WCo8b-0003XE-Pc; Mon, 10 Feb 2014 10:30:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCo8a-0003X9-PM for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 10:30:52 +0000 Received: from [85.158.143.35:32696] by server-2.bemta-4.messagelabs.com id 4B/75-10891-C5AA8F25; Mon, 10 Feb 2014 10:30:52 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1392028251!4441301!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23582 invoked from network); 10 Feb 2014 10:30:51 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-21.messagelabs.com with SMTP; 10 Feb 2014 10:30:51 -0000 Received: (qmail 21478 invoked by uid 634); 10 Feb 2014 10:30:50 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from host81-149-102-120.in-addr.btopenworld.com (HELO [10.0.0.109]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 10 Feb 2014 10:30:49 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 10 Feb 2014 10:30:49 +0000 Message-Id: <02AE776C-C431-4080-A7F5-F9D04D124FE4@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> <94B21275-1A29-4487-B712-413758648B87@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2324967168060265610==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2324967168060265610== Content-Type: multipart/alternative; boundary="Apple-Mail=_FC14781B-43AC-49E4-BC2C-2C117E47A29F" --Apple-Mail=_FC14781B-43AC-49E4-BC2C-2C117E47A29F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 10 Feb 2014, at 10:15, David Scott wrote: >=20 > Ack. I'd like to make a 'mir-homepage' binary that converts a = directory right into a EC2-bootable (i.e. pvgrub) block device, so I'm = planning on looking at it later this week. >=20 > For code that can create a grub-bootable image, see >=20 > https://github.com/jonludlam/xen-testvm/pull/7 >=20 > in particular >=20 > = https://github.com/djs55/xen-testvm/commit/1fa304b721d496597b800d41a604de6= 92b344398 Lovely, thanks. We now have=20 https://github.com/mirage/mirage/issues/214 that tracks this. cheers, Anil= --Apple-Mail=_FC14781B-43AC-49E4-BC2C-2C117E47A29F Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1 On 10 Feb 2014, at 10:15, David Scott <scott.dj@gmail.com> wrote:


Ack.  I'd like to make a 'mir-homepage' binary that converts a directory right into a EC2-bootable (i.e. pvgrub) block device, so I'm planning on looking at it later this week.

For code that can create a grub-bootable image, see


in particular


Lovely, thanks. We now have 

that tracks this.

cheers,
Anil
--Apple-Mail=_FC14781B-43AC-49E4-BC2C-2C117E47A29F-- --===============2324967168060265610== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2324967168060265610==-- From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 12:28:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 12:28: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 1WCpyR-0006PT-IG; Mon, 10 Feb 2014 12:28:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCpyQ-0006Oz-9Q for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 12:28:30 +0000 Received: from [85.158.139.211:8258] by server-7.bemta-5.messagelabs.com id 86/07-14867-DE5C8F25; Mon, 10 Feb 2014 12:28:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1392035308!2886480!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13754 invoked from network); 10 Feb 2014 12:28:28 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-206.messagelabs.com with SMTP; 10 Feb 2014 12:28:28 -0000 Received: (qmail 7272 invoked by uid 634); 10 Feb 2014 12:28:28 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 10 Feb 2014 12:28:25 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <94B21275-1A29-4487-B712-413758648B87@recoil.org> Date: Mon, 10 Feb 2014 12:28:25 +0000 Message-Id: <9F43DF1D-AA09-4B16-9D80-3772E5E6E519@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> <94B21275-1A29-4487-B712-413758648B87@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Feb 2014, at 10:08, Anil Madhavapeddy wrote: > On 9 Feb 2014, at 19:00, Richard Mortier wrote: > >> >> On 9 Feb 2014, at 18:24, Anil Madhavapeddy wrote: >> >>> On 9 Feb 2014, at 18:17, Richard Mortier wrote: >>> >>>> ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) >>> >>> Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. >>> >>> The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. >> >> this was after a "rm -rf ~/.opam" etc -- trying again from clean. > > In that case, can you reproduce on Travis from a clean installation? That'd greatly help debug it. I just pushed a fix to one bad dependency here: https://github.com/mirage/opam-repository/commit/f43c77cc8413fe9f0ec710cc893eb9031a56c641 Let me know if that fixes your problem... -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 12:28:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 12:28: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 1WCpyR-0006PT-IG; Mon, 10 Feb 2014 12:28:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCpyQ-0006Oz-9Q for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 12:28:30 +0000 Received: from [85.158.139.211:8258] by server-7.bemta-5.messagelabs.com id 86/07-14867-DE5C8F25; Mon, 10 Feb 2014 12:28:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1392035308!2886480!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13754 invoked from network); 10 Feb 2014 12:28:28 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-206.messagelabs.com with SMTP; 10 Feb 2014 12:28:28 -0000 Received: (qmail 7272 invoked by uid 634); 10 Feb 2014 12:28:28 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 10 Feb 2014 12:28:25 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <94B21275-1A29-4487-B712-413758648B87@recoil.org> Date: Mon, 10 Feb 2014 12:28:25 +0000 Message-Id: <9F43DF1D-AA09-4B16-9D80-3772E5E6E519@recoil.org> References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> <94B21275-1A29-4487-B712-413758648B87@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Feb 2014, at 10:08, Anil Madhavapeddy wrote: > On 9 Feb 2014, at 19:00, Richard Mortier wrote: > >> >> On 9 Feb 2014, at 18:24, Anil Madhavapeddy wrote: >> >>> On 9 Feb 2014, at 18:17, Richard Mortier wrote: >>> >>>> ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) >>> >>> Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. >>> >>> The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. >> >> this was after a "rm -rf ~/.opam" etc -- trying again from clean. > > In that case, can you reproduce on Travis from a clean installation? That'd greatly help debug it. I just pushed a fix to one bad dependency here: https://github.com/mirage/opam-repository/commit/f43c77cc8413fe9f0ec710cc893eb9031a56c641 Let me know if that fixes your problem... -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 14:05:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 14:05: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 1WCrUM-0004N2-2E; Mon, 10 Feb 2014 14:05:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCrUK-0004Mu-OI for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 14:05:32 +0000 Received: from [193.109.254.147:50221] by server-13.bemta-14.messagelabs.com id A9/8A-01226-CACD8F25; Mon, 10 Feb 2014 14:05:32 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1392041131!3281730!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8332 invoked from network); 10 Feb 2014 14:05:31 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-27.messagelabs.com with SMTP; 10 Feb 2014 14:05:31 -0000 Received: (qmail 5206 invoked by uid 634); 10 Feb 2014 14:05:30 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 10 Feb 2014 14:05:27 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <9F43DF1D-AA09-4B16-9D80-3772E5E6E519@recoil.org> Date: Mon, 10 Feb 2014 14:05:24 +0000 Message-Id: References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> <94B21275-1A29-4487-B712-413758648B87@recoil.org> <9F43DF1D-AA09-4B16-9D80-3772E5E6E519@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Feb 2014, at 12:28, Anil Madhavapeddy wrote: > > On 10 Feb 2014, at 10:08, Anil Madhavapeddy wrote: > >> On 9 Feb 2014, at 19:00, Richard Mortier wrote: >> >>> >>> On 9 Feb 2014, at 18:24, Anil Madhavapeddy wrote: >>> >>>> On 9 Feb 2014, at 18:17, Richard Mortier wrote: >>>> >>>>> ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) >>>> >>>> Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. >>>> >>>> The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. >>> >>> this was after a "rm -rf ~/.opam" etc -- trying again from clean. >> >> In that case, can you reproduce on Travis from a clean installation? That'd greatly help debug it. > > I just pushed a fix to one bad dependency here: > > https://github.com/mirage/opam-repository/commit/f43c77cc8413fe9f0ec710cc893eb9031a56c641 Ahh, I found the root cause of all these little build failures. I had accidentally released the cohttp-0.9.15 archive as 0.9.16. Re-released cohttp here: https://github.com/ocaml/opam-repository/pull/1660 And has been merged into the Mirage 1.1.x branch, and all is suddenly now compiling far more happily. I hadn't spotted this during development as my cohttp was pinned to my working branch :-) -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Feb 10 14:05:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 10 Feb 2014 14:05: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 1WCrUM-0004N2-2E; Mon, 10 Feb 2014 14:05:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WCrUK-0004Mu-OI for mirageos-devel@lists.xenproject.org; Mon, 10 Feb 2014 14:05:32 +0000 Received: from [193.109.254.147:50221] by server-13.bemta-14.messagelabs.com id A9/8A-01226-CACD8F25; Mon, 10 Feb 2014 14:05:32 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1392041131!3281730!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8332 invoked from network); 10 Feb 2014 14:05:31 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-27.messagelabs.com with SMTP; 10 Feb 2014 14:05:31 -0000 Received: (qmail 5206 invoked by uid 634); 10 Feb 2014 14:05:30 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 10 Feb 2014 14:05:27 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <9F43DF1D-AA09-4B16-9D80-3772E5E6E519@recoil.org> Date: Mon, 10 Feb 2014 14:05:24 +0000 Message-Id: References: <7A442DC1-50AF-47C3-ABDD-551A0A67EEFC@recoil.org> <0756518E-7FED-487A-BE67-905D4C7CFC7A@nottingham.ac.uk> <1B0874D1-5557-42C9-A241-340C88EA456F@nottingham.ac.uk> <5070B8FE-70CF-4D5C-B8BC-CD98A87CFDD3@recoil.org> <94B21275-1A29-4487-B712-413758648B87@recoil.org> <9F43DF1D-AA09-4B16-9D80-3772E5E6E519@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage 1.1.0 pull req X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Feb 2014, at 12:28, Anil Madhavapeddy wrote: > > On 10 Feb 2014, at 10:08, Anil Madhavapeddy wrote: > >> On 9 Feb 2014, at 19:00, Richard Mortier wrote: >> >>> >>> On 9 Feb 2014, at 18:24, Anil Madhavapeddy wrote: >>> >>>> On 9 Feb 2014, at 18:17, Richard Mortier wrote: >>>> >>>>> ack; it might be useful to write down (or collate) the assumptions we're making about package dependencies to check that we're coherent. i'm having problems at the moment trying to go from a clean opam install on xen to even being able to "mirage configure" my website -- there seem to be some weird package version incompatibilities. (eg., if mirage-types.1.0.0 is installed, the configure step downgrades to 0.5.0; but if mirage-types is not installed at all, it seems to install 1.1.0.) >>>> >>>> Be sure to `opam update -u` before attempting a compilation, as that will give you the latest package sets and upgrade all relevant packages. >>>> >>>> The "opam install" that is invoked by the unikernel build won't upgrade everything, hence the problems you're seeing. If it persists after an upgrade, we have a constraint problem. >>> >>> this was after a "rm -rf ~/.opam" etc -- trying again from clean. >> >> In that case, can you reproduce on Travis from a clean installation? That'd greatly help debug it. > > I just pushed a fix to one bad dependency here: > > https://github.com/mirage/opam-repository/commit/f43c77cc8413fe9f0ec710cc893eb9031a56c641 Ahh, I found the root cause of all these little build failures. I had accidentally released the cohttp-0.9.15 archive as 0.9.16. Re-released cohttp here: https://github.com/ocaml/opam-repository/pull/1660 And has been merged into the Mirage 1.1.x branch, and all is suddenly now compiling far more happily. I hadn't spotted this during development as my cohttp was pinned to my working branch :-) -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 11:51:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 11:51:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDBrr-0007dM-I2; Tue, 11 Feb 2014 11: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 1WDBrp-0007dH-Ep for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 11:51:10 +0000 Received: from [85.158.137.68:18073] by server-13.bemta-3.messagelabs.com id FB/4E-26923-CAE0AF25; Tue, 11 Feb 2014 11:51:08 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1392119465!1076788!1 X-Originating-IP: [209.85.192.181] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5403 invoked from network); 11 Feb 2014 11:51:07 -0000 Received: from mail-pd0-f181.google.com (HELO mail-pd0-f181.google.com) (209.85.192.181) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2014 11:51:07 -0000 Received: by mail-pd0-f181.google.com with SMTP id y10so7396404pdj.12 for ; Tue, 11 Feb 2014 03:51:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=RzYb+6kKgPVTRwyrLpzTbp6I7tYYvkxiBmv3p5IQa84=; b=F57Hmi9QoeCd1IP1peaXzIWGHfnPWQykc0K90hitj1iMu3L6G2LtpiNRPUSTRjB7M5 5NVrhfhfWYGmhx7JY6vu0YUClVg+1FtwGsPGpeLJkYVXsX+fd/HwL4786nv8v1Dci5al ygdrFIbnZfSBpDBzCa4rAnjbewtb+JLxbq0+MGVJFTAq1iLZ2BnFWxAb1DDhZSj2Bjtq OuwxwP7NEX1guqdNzY1+13tDO/yvAsdd6xTp4c0WT2Hf/W6GmwRp9mea/rj4GALRFcsh pUOZNIZZeMnx36+olJMcqcRczmJLJ8sHlbd4NEp65SVIbwUcdRK2QifwB1M2J6B7HdEE yjjA== MIME-Version: 1.0 X-Received: by 10.66.158.132 with SMTP id wu4mr32162599pab.66.1392119465419; Tue, 11 Feb 2014 03:51:05 -0800 (PST) Received: by 10.70.55.132 with HTTP; Tue, 11 Feb 2014 03:51:05 -0800 (PST) Date: Tue, 11 Feb 2014 11:51:05 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today (tuesday), 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3559746797494770054==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3559746797494770054== Content-Type: multipart/alternative; boundary=047d7bacc1a038abad04f22012f0 --047d7bacc1a038abad04f22012f0 Content-Type: text/plain; charset=ISO-8859-1 Let's meet today and discuss Mirage episode 1.1.0: the homepages strike back! 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817 United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Meeting ID: 591-890-401 -- Dave Scott --047d7bacc1a038abad04f22012f0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Let's meet today and discuss Mirage episode 1.1.0: the homepages strik= e back!
1. =A0Please joi= n my meeting.

2. =A0Use your microph= one and speakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0i= n using your telephone.

United Kingdom (toll-f= ree): 0 808 168 0209 United Kingdom:=A0+44 (0) 207 151 18= 17

United States (toll-fr= ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00= 17

Access Code: 591-890-4= 01
Audio PI= N: Shown after joining the meeting

Meeting ID: 591-890-40= 1

--
Dave Scott
--047d7bacc1a038abad04f22012f0-- --===============3559746797494770054== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3559746797494770054==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 11:51:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 11:51:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDBrr-0007dM-I2; Tue, 11 Feb 2014 11: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 1WDBrp-0007dH-Ep for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 11:51:10 +0000 Received: from [85.158.137.68:18073] by server-13.bemta-3.messagelabs.com id FB/4E-26923-CAE0AF25; Tue, 11 Feb 2014 11:51:08 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1392119465!1076788!1 X-Originating-IP: [209.85.192.181] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5403 invoked from network); 11 Feb 2014 11:51:07 -0000 Received: from mail-pd0-f181.google.com (HELO mail-pd0-f181.google.com) (209.85.192.181) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2014 11:51:07 -0000 Received: by mail-pd0-f181.google.com with SMTP id y10so7396404pdj.12 for ; Tue, 11 Feb 2014 03:51:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=RzYb+6kKgPVTRwyrLpzTbp6I7tYYvkxiBmv3p5IQa84=; b=F57Hmi9QoeCd1IP1peaXzIWGHfnPWQykc0K90hitj1iMu3L6G2LtpiNRPUSTRjB7M5 5NVrhfhfWYGmhx7JY6vu0YUClVg+1FtwGsPGpeLJkYVXsX+fd/HwL4786nv8v1Dci5al ygdrFIbnZfSBpDBzCa4rAnjbewtb+JLxbq0+MGVJFTAq1iLZ2BnFWxAb1DDhZSj2Bjtq OuwxwP7NEX1guqdNzY1+13tDO/yvAsdd6xTp4c0WT2Hf/W6GmwRp9mea/rj4GALRFcsh pUOZNIZZeMnx36+olJMcqcRczmJLJ8sHlbd4NEp65SVIbwUcdRK2QifwB1M2J6B7HdEE yjjA== MIME-Version: 1.0 X-Received: by 10.66.158.132 with SMTP id wu4mr32162599pab.66.1392119465419; Tue, 11 Feb 2014 03:51:05 -0800 (PST) Received: by 10.70.55.132 with HTTP; Tue, 11 Feb 2014 03:51:05 -0800 (PST) Date: Tue, 11 Feb 2014 11:51:05 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today (tuesday), 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3559746797494770054==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3559746797494770054== Content-Type: multipart/alternative; boundary=047d7bacc1a038abad04f22012f0 --047d7bacc1a038abad04f22012f0 Content-Type: text/plain; charset=ISO-8859-1 Let's meet today and discuss Mirage episode 1.1.0: the homepages strike back! 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817 United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Meeting ID: 591-890-401 -- Dave Scott --047d7bacc1a038abad04f22012f0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Let's meet today and discuss Mirage episode 1.1.0: the homepages strik= e back!
1. =A0Please joi= n my meeting.

2. =A0Use your microph= one and speakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0i= n using your telephone.

United Kingdom (toll-f= ree): 0 808 168 0209 United Kingdom:=A0+44 (0) 207 151 18= 17

United States (toll-fr= ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00= 17

Access Code: 591-890-4= 01
Audio PI= N: Shown after joining the meeting

Meeting ID: 591-890-40= 1

--
Dave Scott
--047d7bacc1a038abad04f22012f0-- --===============3559746797494770054== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3559746797494770054==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 11:53:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 11:53: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 1WDBu4-0007gD-TW; Tue, 11 Feb 2014 11:53:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDBu4-0007g8-Eb for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 11:53:28 +0000 Received: from [85.158.143.35:14891] by server-3.bemta-4.messagelabs.com id 29/89-11539-73F0AF25; Tue, 11 Feb 2014 11:53:27 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1392119606!4792106!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23390 invoked from network); 11 Feb 2014 11:53:27 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2014 11:53:27 -0000 Received: by mail-wi0-f170.google.com with SMTP id hi5so3920766wib.5 for ; Tue, 11 Feb 2014 03:53:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/+2A0XsQwp8y/UHBMqD1JARTfW95CFgsV9THyWDvh44=; b=f8nlDA4fPls3pBl5lHIahbrTEEYcPVfPM3r0IgXI0WpjojmHN1+0zR8dla8WOJakkO v20Wa6RyyWI0pra4kV1etv3UQp5mebiOBm7fCbk3McAvfQxjZktk4uiWNKdW7F2cSKEI Z69RxsIk/plmSuX+ZvUbD2sXlD1QG/l+AWoIaBYY4fRpyoQqaLgMatctvv6PWCQAT0rA cAMCtesn8fNg14zzlPUGbI3E4Vzuk5BpFRfxHb7AVkQAy9KJBIy4oZJlApmdZVExA3JM u35PplswbCW7V33Q2VO9u2CA2WQC9szac855p1Mc8UOcfGtQY/FFMZZUxi+uFLCqyP11 EwJA== X-Received: by 10.180.97.37 with SMTP id dx5mr14483814wib.53.1392119606530; Tue, 11 Feb 2014 03:53:26 -0800 (PST) Received: from [10.0.0.152] (host81-149-102-120.in-addr.btopenworld.com. [81.149.102.120]) by mx.google.com with ESMTPSA id hy8sm43474657wjb.2.2014.02.11.03.53.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Feb 2014 03:53:26 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Tue, 11 Feb 2014 11:53:24 +0000 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1510) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage weekly call today (tuesday), 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org fabulous! On 11 Feb 2014, at 11:51, David Scott wrote: > Let's meet today and discuss Mirage episode 1.1.0: the homepages strike back! > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. > > United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817 > > United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017 > > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > > Meeting ID: 591-890-401 > > -- > Dave Scott > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 11:53:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 11:53: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 1WDBu4-0007gD-TW; Tue, 11 Feb 2014 11:53:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDBu4-0007g8-Eb for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 11:53:28 +0000 Received: from [85.158.143.35:14891] by server-3.bemta-4.messagelabs.com id 29/89-11539-73F0AF25; Tue, 11 Feb 2014 11:53:27 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1392119606!4792106!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23390 invoked from network); 11 Feb 2014 11:53:27 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2014 11:53:27 -0000 Received: by mail-wi0-f170.google.com with SMTP id hi5so3920766wib.5 for ; Tue, 11 Feb 2014 03:53:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/+2A0XsQwp8y/UHBMqD1JARTfW95CFgsV9THyWDvh44=; b=f8nlDA4fPls3pBl5lHIahbrTEEYcPVfPM3r0IgXI0WpjojmHN1+0zR8dla8WOJakkO v20Wa6RyyWI0pra4kV1etv3UQp5mebiOBm7fCbk3McAvfQxjZktk4uiWNKdW7F2cSKEI Z69RxsIk/plmSuX+ZvUbD2sXlD1QG/l+AWoIaBYY4fRpyoQqaLgMatctvv6PWCQAT0rA cAMCtesn8fNg14zzlPUGbI3E4Vzuk5BpFRfxHb7AVkQAy9KJBIy4oZJlApmdZVExA3JM u35PplswbCW7V33Q2VO9u2CA2WQC9szac855p1Mc8UOcfGtQY/FFMZZUxi+uFLCqyP11 EwJA== X-Received: by 10.180.97.37 with SMTP id dx5mr14483814wib.53.1392119606530; Tue, 11 Feb 2014 03:53:26 -0800 (PST) Received: from [10.0.0.152] (host81-149-102-120.in-addr.btopenworld.com. [81.149.102.120]) by mx.google.com with ESMTPSA id hy8sm43474657wjb.2.2014.02.11.03.53.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Feb 2014 03:53:26 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Tue, 11 Feb 2014 11:53:24 +0000 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1510) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage weekly call today (tuesday), 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org fabulous! On 11 Feb 2014, at 11:51, David Scott wrote: > Let's meet today and discuss Mirage episode 1.1.0: the homepages strike back! > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. > > United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817 > > United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017 > > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > > Meeting ID: 591-890-401 > > -- > Dave Scott > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 18:58:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 18:58: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 1WDIWo-00011Q-MK; Tue, 11 Feb 2014 18:57:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDIWm-00011H-SX; Tue, 11 Feb 2014 18:57:53 +0000 Received: from [85.158.139.211:31072] by server-11.bemta-5.messagelabs.com id 65/F9-23886-0B27AF25; Tue, 11 Feb 2014 18:57:52 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1392145069!3206221!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRv bmVkOiBhYm91dC5tZS9kYXJpby5mYWdnaW9s\naSk=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16115 invoked from network); 11 Feb 2014 18:57:51 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2014 18:57:51 -0000 X-IronPort-AV: E=Sophos;i="4.95,826,1384300800"; d="asc'?scan'208";a="99894236" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 11 Feb 2014 18:57:43 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Tue, 11 Feb 2014 13:57:42 -0500 Message-ID: <1392145061.30734.59.camel@Solace> From: Dario Faggioli To: Anil Madhavapeddy Date: Tue, 11 Feb 2014 19:57:41 +0100 In-Reply-To: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <1386839335.14726.50.camel@Abyss> Organization: Citrix X-Mailer: Evolution 3.10.3 (3.10.3-1.fc20) MIME-Version: 1.0 X-DLP: MIA1 Cc: Lars Kurth , Amir Chaudhry , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6130408495551556607==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6130408495551556607== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Bet7cdrAAPvlHjkU4qz3" --=-Bet7cdrAAPvlHjkU4qz3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On gio, 2013-12-12 at 11:55 +0000, Anil Madhavapeddy wrote: > On 12 Dec 2013, at 09:08, Dario Faggioli wrot= e: > > > Just for clarity, these are intended for the Mirage blog, right? Or is > > it the Xen-Project blog that you're targeting (also)? >=20 > These are for the Mirage blog, but I would very much like to distill > them into summary documentation suitable for the Xen blog. The audiences > for both are fairly different -- the Mirage readers would want more of > the mechanics of the toolchain, whereas the Xen crowd probably care more > about the details of the protocols. >=20 > >=20 > > If the former, well, personally, I think it would be great to have most > > (if not all) of them in Xen's blog too. As Lars said, we often publish > > stuff sort of multiple time to amplify the effect. However, if we're > > worried that would mean too much information duplication, perhaps > > someone could write a summary, for instance, of the various posts in th= e > > 'Homepage' category for the Xen's blog? >=20 > Agreed -- I suggest we push these out to the Mirage blog over December > (the GitHub issue now has target dates on it for those who 'volunteered'= =20 > on the Mirage call), and then summarise for the Xen blog. >=20 Hey! I just found this old thread and realized that not much of what we were discussing has happened, at least when it comes to "distill them into summary documentation suitable for the Xen blog". =46rom the github issue cited earlier on the thread (https://github.com/mirage/mirage/issues/128) I can't tell exactly what went online on the Mirage blog, where should I check that? Do we have the material already for a post on the Xen Project's blog? Let us know, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-Bet7cdrAAPvlHjkU4qz3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlL6cqUACgkQk4XaBE3IOsSaEwCfUb2ODzNYI74tOzKBfU1jlkQD LtkAn3h6U9FNJAZBRR/u88fiM/aAsA7s =URRG -----END PGP SIGNATURE----- --=-Bet7cdrAAPvlHjkU4qz3-- --===============6130408495551556607== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6130408495551556607==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 18:58:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 18:58: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 1WDIWo-00011Q-MK; Tue, 11 Feb 2014 18:57:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDIWm-00011H-SX; Tue, 11 Feb 2014 18:57:53 +0000 Received: from [85.158.139.211:31072] by server-11.bemta-5.messagelabs.com id 65/F9-23886-0B27AF25; Tue, 11 Feb 2014 18:57:52 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1392145069!3206221!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRv bmVkOiBhYm91dC5tZS9kYXJpby5mYWdnaW9s\naSk=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16115 invoked from network); 11 Feb 2014 18:57:51 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Feb 2014 18:57:51 -0000 X-IronPort-AV: E=Sophos;i="4.95,826,1384300800"; d="asc'?scan'208";a="99894236" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 11 Feb 2014 18:57:43 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Tue, 11 Feb 2014 13:57:42 -0500 Message-ID: <1392145061.30734.59.camel@Solace> From: Dario Faggioli To: Anil Madhavapeddy Date: Tue, 11 Feb 2014 19:57:41 +0100 In-Reply-To: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <1386839335.14726.50.camel@Abyss> Organization: Citrix X-Mailer: Evolution 3.10.3 (3.10.3-1.fc20) MIME-Version: 1.0 X-DLP: MIA1 Cc: Lars Kurth , Amir Chaudhry , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6130408495551556607==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6130408495551556607== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Bet7cdrAAPvlHjkU4qz3" --=-Bet7cdrAAPvlHjkU4qz3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On gio, 2013-12-12 at 11:55 +0000, Anil Madhavapeddy wrote: > On 12 Dec 2013, at 09:08, Dario Faggioli wrot= e: > > > Just for clarity, these are intended for the Mirage blog, right? Or is > > it the Xen-Project blog that you're targeting (also)? >=20 > These are for the Mirage blog, but I would very much like to distill > them into summary documentation suitable for the Xen blog. The audiences > for both are fairly different -- the Mirage readers would want more of > the mechanics of the toolchain, whereas the Xen crowd probably care more > about the details of the protocols. >=20 > >=20 > > If the former, well, personally, I think it would be great to have most > > (if not all) of them in Xen's blog too. As Lars said, we often publish > > stuff sort of multiple time to amplify the effect. However, if we're > > worried that would mean too much information duplication, perhaps > > someone could write a summary, for instance, of the various posts in th= e > > 'Homepage' category for the Xen's blog? >=20 > Agreed -- I suggest we push these out to the Mirage blog over December > (the GitHub issue now has target dates on it for those who 'volunteered'= =20 > on the Mirage call), and then summarise for the Xen blog. >=20 Hey! I just found this old thread and realized that not much of what we were discussing has happened, at least when it comes to "distill them into summary documentation suitable for the Xen blog". =46rom the github issue cited earlier on the thread (https://github.com/mirage/mirage/issues/128) I can't tell exactly what went online on the Mirage blog, where should I check that? Do we have the material already for a post on the Xen Project's blog? Let us know, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-Bet7cdrAAPvlHjkU4qz3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlL6cqUACgkQk4XaBE3IOsSaEwCfUb2ODzNYI74tOzKBfU1jlkQD LtkAn3h6U9FNJAZBRR/u88fiM/aAsA7s =URRG -----END PGP SIGNATURE----- --=-Bet7cdrAAPvlHjkU4qz3-- --===============6130408495551556607== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6130408495551556607==-- From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 19:01:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 19:01: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 1WDIaV-0001Zq-Hi; Tue, 11 Feb 2014 19:01:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDIaU-0001Zd-NG for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 19:01:42 +0000 Received: from [85.158.143.35:40670] by server-1.bemta-4.messagelabs.com id 55/E7-31661-6937AF25; Tue, 11 Feb 2014 19:01:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-21.messagelabs.com!1392145300!4915476!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30377 invoked from network); 11 Feb 2014 19:01:40 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-21.messagelabs.com with SMTP; 11 Feb 2014 19:01:40 -0000 Received: (qmail 567 invoked by uid 634); 11 Feb 2014 19:01:40 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 11 Feb 2014 19:01:39 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <1392145061.30734.59.camel@Solace> Date: Tue, 11 Feb 2014 19:01:37 +0000 Message-Id: <484CB6F6-CB8B-45C7-AB06-60AA725B72DE@recoil.org> References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <1386839335.14726.50.camel@Abyss> <1392145061.30734.59.camel@Solace> To: Dario Faggioli X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Lars Kurth , Amir Chaudhry , Publicity list , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 Feb 2014, at 18:57, Dario Faggioli wrote: > On gio, 2013-12-12 at 11:55 +0000, Anil Madhavapeddy wrote: >> On 12 Dec 2013, at 09:08, Dario Faggioli wrote: >> >>> Just for clarity, these are intended for the Mirage blog, right? Or is >>> it the Xen-Project blog that you're targeting (also)? >> >> These are for the Mirage blog, but I would very much like to distill >> them into summary documentation suitable for the Xen blog. The audiences >> for both are fairly different -- the Mirage readers would want more of >> the mechanics of the toolchain, whereas the Xen crowd probably care more >> about the details of the protocols. >> >>> >>> If the former, well, personally, I think it would be great to have most >>> (if not all) of them in Xen's blog too. As Lars said, we often publish >>> stuff sort of multiple time to amplify the effect. However, if we're >>> worried that would mean too much information duplication, perhaps >>> someone could write a summary, for instance, of the various posts in the >>> 'Homepage' category for the Xen's blog? >> >> Agreed -- I suggest we push these out to the Mirage blog over December >> (the GitHub issue now has target dates on it for those who 'volunteered' >> on the Mirage call), and then summarise for the Xen blog. >> > Hey! > > I just found this old thread and realized that not much of what we were > discussing has happened, at least when it comes to "distill them into > summary documentation suitable for the Xen blog". > > From the github issue cited earlier on the thread > (https://github.com/mirage/mirage/issues/128) I can't tell exactly what > went online on the Mirage blog, where should I check that? Do we have > the material already for a post on the Xen Project's blog? A timely question! We have quite a few articles that have gone up now; the front page has a summary of recent updates; http://www.openmirage.org/ Some specific articles that may be of interest from the docs page: http://www.openmirage.org/docs/ - How Xen events work: http://openmirage.org/wiki/xen-events - How Xen suspend/resume works: http://openmirage.org/wiki/xen-suspend - Building custom disk backends: http://openmirage.org/wiki/xen-synthesize-virtual-disk - A walkthrough building a Hello World Xen kernel: http://openmirage.org/wiki/hello-world As for distilling these down to a Xen blog post, I'll defer to someone with a little more time than I have right now. I like the thinking though :-) -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 19:01:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 19:01: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 1WDIaV-0001Zq-Hi; Tue, 11 Feb 2014 19:01:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDIaU-0001Zd-NG for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 19:01:42 +0000 Received: from [85.158.143.35:40670] by server-1.bemta-4.messagelabs.com id 55/E7-31661-6937AF25; Tue, 11 Feb 2014 19:01:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-21.messagelabs.com!1392145300!4915476!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30377 invoked from network); 11 Feb 2014 19:01:40 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-21.messagelabs.com with SMTP; 11 Feb 2014 19:01:40 -0000 Received: (qmail 567 invoked by uid 634); 11 Feb 2014 19:01:40 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 11 Feb 2014 19:01:39 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <1392145061.30734.59.camel@Solace> Date: Tue, 11 Feb 2014 19:01:37 +0000 Message-Id: <484CB6F6-CB8B-45C7-AB06-60AA725B72DE@recoil.org> References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <1386839335.14726.50.camel@Abyss> <1392145061.30734.59.camel@Solace> To: Dario Faggioli X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Lars Kurth , Amir Chaudhry , Publicity list , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 Feb 2014, at 18:57, Dario Faggioli wrote: > On gio, 2013-12-12 at 11:55 +0000, Anil Madhavapeddy wrote: >> On 12 Dec 2013, at 09:08, Dario Faggioli wrote: >> >>> Just for clarity, these are intended for the Mirage blog, right? Or is >>> it the Xen-Project blog that you're targeting (also)? >> >> These are for the Mirage blog, but I would very much like to distill >> them into summary documentation suitable for the Xen blog. The audiences >> for both are fairly different -- the Mirage readers would want more of >> the mechanics of the toolchain, whereas the Xen crowd probably care more >> about the details of the protocols. >> >>> >>> If the former, well, personally, I think it would be great to have most >>> (if not all) of them in Xen's blog too. As Lars said, we often publish >>> stuff sort of multiple time to amplify the effect. However, if we're >>> worried that would mean too much information duplication, perhaps >>> someone could write a summary, for instance, of the various posts in the >>> 'Homepage' category for the Xen's blog? >> >> Agreed -- I suggest we push these out to the Mirage blog over December >> (the GitHub issue now has target dates on it for those who 'volunteered' >> on the Mirage call), and then summarise for the Xen blog. >> > Hey! > > I just found this old thread and realized that not much of what we were > discussing has happened, at least when it comes to "distill them into > summary documentation suitable for the Xen blog". > > From the github issue cited earlier on the thread > (https://github.com/mirage/mirage/issues/128) I can't tell exactly what > went online on the Mirage blog, where should I check that? Do we have > the material already for a post on the Xen Project's blog? A timely question! We have quite a few articles that have gone up now; the front page has a summary of recent updates; http://www.openmirage.org/ Some specific articles that may be of interest from the docs page: http://www.openmirage.org/docs/ - How Xen events work: http://openmirage.org/wiki/xen-events - How Xen suspend/resume works: http://openmirage.org/wiki/xen-suspend - Building custom disk backends: http://openmirage.org/wiki/xen-synthesize-virtual-disk - A walkthrough building a Hello World Xen kernel: http://openmirage.org/wiki/hello-world As for distilling these down to a Xen blog post, I'll defer to someone with a little more time than I have right now. I like the thinking though :-) -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 19:12:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 19:12:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDIkV-0002M3-Uz; Tue, 11 Feb 2014 19:12:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDIkT-0002Lq-Vq for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 19:12:03 +0000 Received: from [85.158.143.35:46600] by server-3.bemta-4.messagelabs.com id 61/EE-11539-1067AF25; Tue, 11 Feb 2014 19:12:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-21.messagelabs.com!1392145920!4915614!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22045 invoked from network); 11 Feb 2014 19:12:00 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-21.messagelabs.com with SMTP; 11 Feb 2014 19:12:00 -0000 Received: (qmail 17138 invoked by uid 634); 11 Feb 2014 19:12:00 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 11 Feb 2014 19:11:59 +0000 From: Anil Madhavapeddy Date: Tue, 11 Feb 2014 19:11:57 +0000 Message-Id: To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Publicity list Subject: [MirageOS-devel] Mirage 1.1.0 release: the eat-your-own-dogfood release X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm pleased to announce the release of Mirage OS 1.1.0. The latest packages have been uploaded to OPAM, so you can just run "opam update -u" to grab the sources. A summary of new features and fixes is available online at: http://openmirage.org/blog/mirage-1.1-released It can be summarised as follows, but please see the blog post for details. - functional combinators to express device drivers in configuration files -- a much more flexible and well-typed approach to assembling various combinations of an OS stack in a principled way. - a fully functorized TCP/IP stack that is modular enough to abstract the sockets API and the direct TCP/IP stack behind the same modular interface. This lets us swap between developing on a familiar Unix box and redeploying on Xen. - less magic in the build system to make upstream binary packaging easier. - over 30 libraries released into OPAM, ranging from protocol implementations to Xen libraries to database code. - a refreshed set of tutorials and hello world walkthroughs online at: http://openmirage.org/wiki/hello-world Our libraries have had contributions from a large number of people in this release; the Mirage website now installs *40* libraries from a clean build (see https://travis-ci.org/mirage/mirage-www/jobs/18672156 for a sample build log of the live website). I'd like to particularly thank David Sheets, Hugo Heuzard and Rudy Grinberg for their contributions to the network and web stacks, and Jon Ludlam for contributing to the Xen suspend/resume support. The focus of the development team is now to shift our personal homepages onto Mirage-hosted VMs, so expect a flurry of complaints and bugfixes as we are forced to use our own tools! As always, please report bugs to https://github.com/mirage/mirage/issues, or on the mailing list. -Anil, along with Thomas Gazagnaire, David Scott and Richard Mortier _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 19:12:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 19:12:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDIkV-0002M3-Uz; Tue, 11 Feb 2014 19:12:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDIkT-0002Lq-Vq for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 19:12:03 +0000 Received: from [85.158.143.35:46600] by server-3.bemta-4.messagelabs.com id 61/EE-11539-1067AF25; Tue, 11 Feb 2014 19:12:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-21.messagelabs.com!1392145920!4915614!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22045 invoked from network); 11 Feb 2014 19:12:00 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-21.messagelabs.com with SMTP; 11 Feb 2014 19:12:00 -0000 Received: (qmail 17138 invoked by uid 634); 11 Feb 2014 19:12:00 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 11 Feb 2014 19:11:59 +0000 From: Anil Madhavapeddy Date: Tue, 11 Feb 2014 19:11:57 +0000 Message-Id: To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Publicity list Subject: [MirageOS-devel] Mirage 1.1.0 release: the eat-your-own-dogfood release X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm pleased to announce the release of Mirage OS 1.1.0. The latest packages have been uploaded to OPAM, so you can just run "opam update -u" to grab the sources. A summary of new features and fixes is available online at: http://openmirage.org/blog/mirage-1.1-released It can be summarised as follows, but please see the blog post for details. - functional combinators to express device drivers in configuration files -- a much more flexible and well-typed approach to assembling various combinations of an OS stack in a principled way. - a fully functorized TCP/IP stack that is modular enough to abstract the sockets API and the direct TCP/IP stack behind the same modular interface. This lets us swap between developing on a familiar Unix box and redeploying on Xen. - less magic in the build system to make upstream binary packaging easier. - over 30 libraries released into OPAM, ranging from protocol implementations to Xen libraries to database code. - a refreshed set of tutorials and hello world walkthroughs online at: http://openmirage.org/wiki/hello-world Our libraries have had contributions from a large number of people in this release; the Mirage website now installs *40* libraries from a clean build (see https://travis-ci.org/mirage/mirage-www/jobs/18672156 for a sample build log of the live website). I'd like to particularly thank David Sheets, Hugo Heuzard and Rudy Grinberg for their contributions to the network and web stacks, and Jon Ludlam for contributing to the Xen suspend/resume support. The focus of the development team is now to shift our personal homepages onto Mirage-hosted VMs, so expect a flurry of complaints and bugfixes as we are forced to use our own tools! As always, please report bugs to https://github.com/mirage/mirage/issues, or on the mailing list. -Anil, along with Thomas Gazagnaire, David Scott and Richard Mortier _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 22:39:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 11 Feb 2014 22:39: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 1WDLzW-0005bH-2E; Tue, 11 Feb 2014 22:39:46 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1WDLzU-0005bC-9C for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 22:39:44 +0000 Received: from [85.158.139.211:58885] by server-11.bemta-5.messagelabs.com id 95/CB-23886-FA6AAF25; Tue, 11 Feb 2014 22:39:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-206.messagelabs.com!1392158382!3228692!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32275 invoked from network); 11 Feb 2014 22:39:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-206.messagelabs.com with SMTP; 11 Feb 2014 22:39:42 -0000 Received: (qmail 20791 invoked by uid 634); 11 Feb 2014 22:39:41 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 11 Feb 2014 22:39:41 +0000 From: Anil Madhavapeddy Message-Id: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org> Date: Tue, 11 Feb 2014 22:39:39 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] zurb responsive problem on mobiles X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Does anyone have any idea why the openmirage.org blog layout looks odd on a mobile device such as an iPhone? The columns don't expand to fill my iPhone due to the 
 code tags (with the latest blog post for example).  My CSS-fu isn't quite up there to figure out why though...

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 22:39:49 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 11 Feb 2014 22:39: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 1WDLzW-0005bH-2E; Tue, 11 Feb 2014 22:39:46 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDLzU-0005bC-9C
	for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 22:39:44 +0000
Received: from [85.158.139.211:58885] by server-11.bemta-5.messagelabs.com id
	95/CB-23886-FA6AAF25; Tue, 11 Feb 2014 22:39:43 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-2.tower-206.messagelabs.com!1392158382!3228692!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32275 invoked from network); 11 Feb 2014 22:39:42 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-2.tower-206.messagelabs.com with SMTP;
	11 Feb 2014 22:39:42 -0000
Received: (qmail 20791 invoked by uid 634); 11 Feb 2014 22:39:41 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 11 Feb 2014 22:39:41 +0000
From: Anil Madhavapeddy 
Message-Id: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
Date: Tue, 11 Feb 2014 22:39:39 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Does anyone have any idea why the openmirage.org blog layout looks odd on a mobile device such as an iPhone?

The columns don't expand to fill my iPhone due to the 
 code tags (with the latest blog post for example).  My CSS-fu isn't quite up there to figure out why though...

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 22:45:33 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 11 Feb 2014 22:45:33 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDM56-0005dF-N4; Tue, 11 Feb 2014 22:45:32 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDM55-0005dA-5y
	for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 22:45:31 +0000
Received: from [85.158.143.35:9850] by server-1.bemta-4.messagelabs.com id
	78/91-31661-A08AAF25; Tue, 11 Feb 2014 22:45:30 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-11.tower-21.messagelabs.com!1392158729!4933260!1
X-Originating-IP: [151.236.209.34]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31635 invoked from network); 11 Feb 2014 22:45:29 -0000
Received: from engine01-20433-9.icritical.com (HELO
	engine01-20433-9.icritical.com) (151.236.209.34)
	by server-11.tower-21.messagelabs.com with SMTP;
	11 Feb 2014 22:45:29 -0000
Received: (qmail 30036 invoked from network); 11 Feb 2014 22:45:22 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-9.icritical.com with SMTP; 11 Feb 2014 22:45:22 -0000
Received: from engine01-20433-9.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-9.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 29584-10 for ;
	Tue, 11 Feb 2014 22:45:22 +0000 (GMT)
Received: (qmail 30023 invoked by uid 599); 11 Feb 2014 22:45:22 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine01-20433-9.icritical.com (qpsmtpd/0.28) with ESMTP;
	Tue, 11 Feb 2014 22:45:22 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WDM51-0000HX-QN; Tue, 11 Feb 2014 22:45:27 +0000
From: Richard Mortier 
To: Anil Madhavapeddy 
Date: Tue, 11 Feb 2014 22:45:26 +0000
Thread-Topic: [MirageOS-devel] zurb responsive problem on mobiles
Thread-Index: Ac8nevUGVidckYtWRbG2jwE18Pw29A==
Message-ID: <5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
References: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
In-Reply-To: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-9.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 11 Feb 2014, at 22:39, Anil Madhavapeddy  wrote:

> Does anyone have any idea why the openmirage.org blog layout looks odd on a mobile device such as an iPhone?
> 
> The columns don't expand to fill my iPhone due to the 
 code tags (with the latest blog post for example).  My CSS-fu isn't quite up there to figure out why though...

only had a quick glance but: this is controlled by the small-N large-N etc classes isn't it?

the sidebar on the blog page is "small-6 large-3" following a div which is "small-12 large-9".

there are 12 columns, so this will overflow on small displays but fit nicely adjacent to blog posts on larger.

try making the aside "small-12 large-3"...?

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 22:45:33 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 11 Feb 2014 22:45:33 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDM56-0005dF-N4; Tue, 11 Feb 2014 22:45:32 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDM55-0005dA-5y
	for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 22:45:31 +0000
Received: from [85.158.143.35:9850] by server-1.bemta-4.messagelabs.com id
	78/91-31661-A08AAF25; Tue, 11 Feb 2014 22:45:30 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-11.tower-21.messagelabs.com!1392158729!4933260!1
X-Originating-IP: [151.236.209.34]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31635 invoked from network); 11 Feb 2014 22:45:29 -0000
Received: from engine01-20433-9.icritical.com (HELO
	engine01-20433-9.icritical.com) (151.236.209.34)
	by server-11.tower-21.messagelabs.com with SMTP;
	11 Feb 2014 22:45:29 -0000
Received: (qmail 30036 invoked from network); 11 Feb 2014 22:45:22 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-9.icritical.com with SMTP; 11 Feb 2014 22:45:22 -0000
Received: from engine01-20433-9.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-9.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 29584-10 for ;
	Tue, 11 Feb 2014 22:45:22 +0000 (GMT)
Received: (qmail 30023 invoked by uid 599); 11 Feb 2014 22:45:22 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine01-20433-9.icritical.com (qpsmtpd/0.28) with ESMTP;
	Tue, 11 Feb 2014 22:45:22 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WDM51-0000HX-QN; Tue, 11 Feb 2014 22:45:27 +0000
From: Richard Mortier 
To: Anil Madhavapeddy 
Date: Tue, 11 Feb 2014 22:45:26 +0000
Thread-Topic: [MirageOS-devel] zurb responsive problem on mobiles
Thread-Index: Ac8nevUGVidckYtWRbG2jwE18Pw29A==
Message-ID: <5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
References: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
In-Reply-To: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-9.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 11 Feb 2014, at 22:39, Anil Madhavapeddy  wrote:

> Does anyone have any idea why the openmirage.org blog layout looks odd on a mobile device such as an iPhone?
> 
> The columns don't expand to fill my iPhone due to the 
 code tags (with the latest blog post for example).  My CSS-fu isn't quite up there to figure out why though...

only had a quick glance but: this is controlled by the small-N large-N etc classes isn't it?

the sidebar on the blog page is "small-6 large-3" following a div which is "small-12 large-9".

there are 12 columns, so this will overflow on small displays but fit nicely adjacent to blog posts on larger.

try making the aside "small-12 large-3"...?

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 23:08:27 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 11 Feb 2014 23:08:27 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDMRG-0006SF-3f; Tue, 11 Feb 2014 23:08:26 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDMRE-0006SA-Rz
	for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 23:08:25 +0000
Received: from [85.158.139.211:28819] by server-7.bemta-5.messagelabs.com id
	19/2F-14867-86DAAF25; Tue, 11 Feb 2014 23:08:24 +0000
X-Env-Sender: amirmc@gmail.com
X-Msg-Ref: server-3.tower-206.messagelabs.com!1392160103!3273754!1
X-Originating-IP: [209.85.215.172]
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32438 invoked from network); 11 Feb 2014 23:08:23 -0000
Received: from mail-ea0-f172.google.com (HELO mail-ea0-f172.google.com)
	(209.85.215.172)
	by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	11 Feb 2014 23:08:23 -0000
Received: by mail-ea0-f172.google.com with SMTP id l9so3405290eaj.31
	for ;
	Tue, 11 Feb 2014 15:08:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=content-type:mime-version:subject:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to;
	bh=41Sp0DbkkF5TipYY7OfG5sqQh11iJleCAf8Khtm302U=;
	b=Z6Z8j55IcPwuLqbpAsnBcV11eiULiazSqrbdWGsp/4u/+zfvXCq6MIgpz56rSKOVx1
	5CgbXK8qizrOwqyixlFIV4yI1E7mjLgG+7ssYBZj1bcUEOmUurZz+RNrTDUFUGx4PO1U
	zHJw9rq+HiIFWEdpVKWrIMbT/Gav4HxuPG9dqedrKhpUxVL6hcUsrkEU72EH9jOCvfNP
	XEvQVGw0cvmEk0qvrKYJz6E7SIg3fxpTrK1iPJFZew1h2rq5fZoHOugjArzgGuRBqIbO
	d0kBkDuvotGLmb46wdhws47toEM4OUgRBbJEusUga55Xl/iR1d3A3brhZ8F31Zx8EpVO
	1UaA==
X-Received: by 10.14.223.71 with SMTP id u47mr6516181eep.89.1392160102812;
	Tue, 11 Feb 2014 15:08:22 -0800 (PST)
Received: from [192.168.0.3] (cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net.
	[86.6.155.105]) by mx.google.com with ESMTPSA id
	i43sm72998249eeu.13.2014.02.11.15.08.21 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 11 Feb 2014 15:08:22 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: <5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
Date: Tue, 11 Feb 2014 23:08:21 +0000
Message-Id: <0E25A163-D7CE-49ED-B2EF-ABBA4880902A@cam.ac.uk>
References: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
	<5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 11 Feb 2014, at 22:45, Richard Mortier  wrote:

> =

> On 11 Feb 2014, at 22:39, Anil Madhavapeddy  wrote:
> =

>> Does anyone have any idea why the openmirage.org blog layout looks odd o=
n a mobile device such as an iPhone?
>> =

>> The columns don't expand to fill my iPhone due to the 
 code tags (w=
ith the latest blog post for example).  My CSS-fu isn't quite up there to f=
igure out why though...
> =

> only had a quick glance but: this is controlled by the small-N large-N et=
c classes isn't it?
> =

> the sidebar on the blog page is "small-6 large-3" following a div which i=
s "small-12 large-9".
> =

> there are 12 columns, so this will overflow on small displays but fit nic=
ely adjacent to blog posts on larger.
> =

> try making the aside "small-12 large-3"=85?

I think that's one of the problems to fix but I'm not sure it'll fix the co=
de samples.  =


I'd try wrapping the 
 blocks in a 
 and see if that improves thing=
s.  I moved my jekyll-based site to Zurb a while ago and my code snippets a=
ppear to scale as expected.  They'reof the form 
 rather tha=
n just 
.  =


NB At the risk of stating the obvious, you can check how the site will look=
 on a phone by narrowing your browser window. =


AC


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 11 23:08:27 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 11 Feb 2014 23:08:27 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDMRG-0006SF-3f; Tue, 11 Feb 2014 23:08:26 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDMRE-0006SA-Rz
	for mirageos-devel@lists.xenproject.org; Tue, 11 Feb 2014 23:08:25 +0000
Received: from [85.158.139.211:28819] by server-7.bemta-5.messagelabs.com id
	19/2F-14867-86DAAF25; Tue, 11 Feb 2014 23:08:24 +0000
X-Env-Sender: amirmc@gmail.com
X-Msg-Ref: server-3.tower-206.messagelabs.com!1392160103!3273754!1
X-Originating-IP: [209.85.215.172]
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32438 invoked from network); 11 Feb 2014 23:08:23 -0000
Received: from mail-ea0-f172.google.com (HELO mail-ea0-f172.google.com)
	(209.85.215.172)
	by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	11 Feb 2014 23:08:23 -0000
Received: by mail-ea0-f172.google.com with SMTP id l9so3405290eaj.31
	for ;
	Tue, 11 Feb 2014 15:08:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=content-type:mime-version:subject:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to;
	bh=41Sp0DbkkF5TipYY7OfG5sqQh11iJleCAf8Khtm302U=;
	b=Z6Z8j55IcPwuLqbpAsnBcV11eiULiazSqrbdWGsp/4u/+zfvXCq6MIgpz56rSKOVx1
	5CgbXK8qizrOwqyixlFIV4yI1E7mjLgG+7ssYBZj1bcUEOmUurZz+RNrTDUFUGx4PO1U
	zHJw9rq+HiIFWEdpVKWrIMbT/Gav4HxuPG9dqedrKhpUxVL6hcUsrkEU72EH9jOCvfNP
	XEvQVGw0cvmEk0qvrKYJz6E7SIg3fxpTrK1iPJFZew1h2rq5fZoHOugjArzgGuRBqIbO
	d0kBkDuvotGLmb46wdhws47toEM4OUgRBbJEusUga55Xl/iR1d3A3brhZ8F31Zx8EpVO
	1UaA==
X-Received: by 10.14.223.71 with SMTP id u47mr6516181eep.89.1392160102812;
	Tue, 11 Feb 2014 15:08:22 -0800 (PST)
Received: from [192.168.0.3] (cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net.
	[86.6.155.105]) by mx.google.com with ESMTPSA id
	i43sm72998249eeu.13.2014.02.11.15.08.21 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 11 Feb 2014 15:08:22 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: <5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
Date: Tue, 11 Feb 2014 23:08:21 +0000
Message-Id: <0E25A163-D7CE-49ED-B2EF-ABBA4880902A@cam.ac.uk>
References: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
	<5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 11 Feb 2014, at 22:45, Richard Mortier  wrote:

> =

> On 11 Feb 2014, at 22:39, Anil Madhavapeddy  wrote:
> =

>> Does anyone have any idea why the openmirage.org blog layout looks odd o=
n a mobile device such as an iPhone?
>> =

>> The columns don't expand to fill my iPhone due to the 
 code tags (w=
ith the latest blog post for example).  My CSS-fu isn't quite up there to f=
igure out why though...
> =

> only had a quick glance but: this is controlled by the small-N large-N et=
c classes isn't it?
> =

> the sidebar on the blog page is "small-6 large-3" following a div which i=
s "small-12 large-9".
> =

> there are 12 columns, so this will overflow on small displays but fit nic=
ely adjacent to blog posts on larger.
> =

> try making the aside "small-12 large-3"=85?

I think that's one of the problems to fix but I'm not sure it'll fix the co=
de samples.  =


I'd try wrapping the 
 blocks in a 
 and see if that improves thing=
s.  I moved my jekyll-based site to Zurb a while ago and my code snippets a=
ppear to scale as expected.  They'reof the form 
 rather tha=
n just 
.  =


NB At the risk of stating the obvious, you can check how the site will look=
 on a phone by narrowing your browser window. =


AC


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 00:12:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 00:12: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 1WDNRW-0000tk-Tn; Wed, 12 Feb 2014 00:12:46 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDNRU-0000td-MT
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 00:12:44 +0000
Received: from [85.158.137.68:45891] by server-11.bemta-3.messagelabs.com id
	30/0D-04255-B7CBAF25; Wed, 12 Feb 2014 00:12:43 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-2.tower-31.messagelabs.com!1392163962!1217575!1
X-Originating-IP: [131.111.8.133]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16288 invoked from network); 12 Feb 2014 00:12:43 -0000
Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk)
	(131.111.8.133)
	by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 12 Feb 2014 00:12:43 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net
	([86.6.155.105]:64755 helo=[192.168.0.3])
	by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WDNRQ-0007U1-hh (Exim 4.82_3-c0e5623)
	(return-path ); Wed, 12 Feb 2014 00:12:40 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: <0E25A163-D7CE-49ED-B2EF-ABBA4880902A@cam.ac.uk>
Date: Wed, 12 Feb 2014 00:12:40 +0000
Message-Id: 
References: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
	<5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
	<0E25A163-D7CE-49ED-B2EF-ABBA4880902A@cam.ac.uk>
To: "mirageos-devel@lists.xenproject.org" 
X-Mailer: Apple Mail (2.1510)
Cc: Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 11 Feb 2014, at 23:08, Amir Chaudhry  wrote:

> =

> On 11 Feb 2014, at 22:45, Richard Mortier  wrote:
> =

>> =

>> On 11 Feb 2014, at 22:39, Anil Madhavapeddy  wrote:
>> =

>>> Does anyone have any idea why the openmirage.org blog layout looks odd =
on a mobile device such as an iPhone?
>>> =

>>> The columns don't expand to fill my iPhone due to the 
 code tags (=
with the latest blog post for example).  My CSS-fu isn't quite up there to =
figure out why though...
>> =

>> only had a quick glance but: this is controlled by the small-N large-N e=
tc classes isn't it?
>> =

>> the sidebar on the blog page is "small-6 large-3" following a div which =
is "small-12 large-9".
>> =

>> there are 12 columns, so this will overflow on small displays but fit ni=
cely adjacent to blog posts on larger.
>> =

>> try making the aside "small-12 large-3"=85?
> =

> I think that's one of the problems to fix but I'm not sure it'll fix the =
code samples.  =

> =

> I'd try wrapping the 
 blocks in a 
 and see if that improves thi=
ngs.  I moved my jekyll-based site to Zurb a while ago and my code snippets=
 appear to scale as expected.  They'reof the form 
 rather t=
han just 
.  =

> =

> NB At the risk of stating the obvious, you can check how the site will lo=
ok on a phone by narrowing your browser window. =



I tried taking the html and playing with it locally.  Wrapping in a 
 d=
oesn't make any difference.

For my code highlighting I'd simply copy/pasted what bootstrap had and look=
ing at the CSS, my `pre` has the following lines:
  word-break: break-all;
  word-wrap: break-word;

You can read the docs for each of these below but I think you'll only need =
the latter of the two.  Adding them will make the text run over multiple li=
nes but it won't look pretty (I don't think there's a sane way to fix that =
though).  =


I'm not sure if there's a better way but this should suffice for the time b=
eing.

https://developer.mozilla.org/en-US/docs/Web/CSS/word-break
https://developer.mozilla.org/en-US/docs/Web/CSS/word-wrap

ac
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 00:12:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 00:12: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 1WDNRW-0000tk-Tn; Wed, 12 Feb 2014 00:12:46 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDNRU-0000td-MT
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 00:12:44 +0000
Received: from [85.158.137.68:45891] by server-11.bemta-3.messagelabs.com id
	30/0D-04255-B7CBAF25; Wed, 12 Feb 2014 00:12:43 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-2.tower-31.messagelabs.com!1392163962!1217575!1
X-Originating-IP: [131.111.8.133]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16288 invoked from network); 12 Feb 2014 00:12:43 -0000
Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk)
	(131.111.8.133)
	by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 12 Feb 2014 00:12:43 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net
	([86.6.155.105]:64755 helo=[192.168.0.3])
	by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WDNRQ-0007U1-hh (Exim 4.82_3-c0e5623)
	(return-path ); Wed, 12 Feb 2014 00:12:40 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: <0E25A163-D7CE-49ED-B2EF-ABBA4880902A@cam.ac.uk>
Date: Wed, 12 Feb 2014 00:12:40 +0000
Message-Id: 
References: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
	<5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
	<0E25A163-D7CE-49ED-B2EF-ABBA4880902A@cam.ac.uk>
To: "mirageos-devel@lists.xenproject.org" 
X-Mailer: Apple Mail (2.1510)
Cc: Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 11 Feb 2014, at 23:08, Amir Chaudhry  wrote:

> =

> On 11 Feb 2014, at 22:45, Richard Mortier  wrote:
> =

>> =

>> On 11 Feb 2014, at 22:39, Anil Madhavapeddy  wrote:
>> =

>>> Does anyone have any idea why the openmirage.org blog layout looks odd =
on a mobile device such as an iPhone?
>>> =

>>> The columns don't expand to fill my iPhone due to the 
 code tags (=
with the latest blog post for example).  My CSS-fu isn't quite up there to =
figure out why though...
>> =

>> only had a quick glance but: this is controlled by the small-N large-N e=
tc classes isn't it?
>> =

>> the sidebar on the blog page is "small-6 large-3" following a div which =
is "small-12 large-9".
>> =

>> there are 12 columns, so this will overflow on small displays but fit ni=
cely adjacent to blog posts on larger.
>> =

>> try making the aside "small-12 large-3"=85?
> =

> I think that's one of the problems to fix but I'm not sure it'll fix the =
code samples.  =

> =

> I'd try wrapping the 
 blocks in a 
 and see if that improves thi=
ngs.  I moved my jekyll-based site to Zurb a while ago and my code snippets=
 appear to scale as expected.  They'reof the form 
 rather t=
han just 
.  =

> =

> NB At the risk of stating the obvious, you can check how the site will lo=
ok on a phone by narrowing your browser window. =



I tried taking the html and playing with it locally.  Wrapping in a 
 d=
oesn't make any difference.

For my code highlighting I'd simply copy/pasted what bootstrap had and look=
ing at the CSS, my `pre` has the following lines:
  word-break: break-all;
  word-wrap: break-word;

You can read the docs for each of these below but I think you'll only need =
the latter of the two.  Adding them will make the text run over multiple li=
nes but it won't look pretty (I don't think there's a sane way to fix that =
though).  =


I'm not sure if there's a better way but this should suffice for the time b=
eing.

https://developer.mozilla.org/en-US/docs/Web/CSS/word-break
https://developer.mozilla.org/en-US/docs/Web/CSS/word-wrap

ac
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 14:46:14 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 14:46:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDb4k-0002Yt-On; Wed, 12 Feb 2014 14:46:10 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDb4j-0002Yh-6L
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 14:46:09 +0000
Received: from [85.158.139.211:7763] by server-15.bemta-5.messagelabs.com id
	DC/4E-24395-0398BF25; Wed, 12 Feb 2014 14:46:08 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-11.tower-206.messagelabs.com!1392216366!3469518!1
X-Originating-IP: [74.125.82.179]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23704 invoked from network); 12 Feb 2014 14:46:07 -0000
Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com)
	(74.125.82.179)
	by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 14:46:07 -0000
Received: by mail-we0-f179.google.com with SMTP id q58so5921182wes.24
	for ;
	Wed, 12 Feb 2014 06:46:06 -0800 (PST)
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:to:mime-version;
	bh=eYNgHzbeqPhCo/ljkQR/YM2xNI1sL6/rYAjtg/UdUfs=;
	b=GpkcpKqUpbFzKuyVkVNvKL1IyIlT4+U5UbErZhSLHMICfQapsVfw2vNCB4GAAF85X/
	SZjMw5m67zEz14qc9f6JPFjSBHKep14Tms9BwDmloGFkcUvkCUWC9SP+hF9Sp0hrKgAI
	xOB4+Cyu/gxqiJsniDoUGxn78tAe2BAQnfDMzFYKfNqehYgL0EJiLpxXlnxWAeGNP+G2
	x8i2M1lGLsIcj73DDgk5GqQTAoBOMT06FsyQ6eXdUV+W/aDoci9YdSV36P0CpoN+STEF
	nffnj+sqNqcyRhX68DB8ynbSsGow/OO389tM/v4KEsYxOFvirncJyuMhDuD/ii5gkdXU
	/VHg==
X-Gm-Message-State: ALoCoQnfbiLX6CK9tOSpLdYewIuxVmmEO/eGh2cMByNSCIJyJRdLCIOih+oAS2DojiLZy92MCQor
X-Received: by 10.194.188.80 with SMTP id fy16mr1522102wjc.30.1392216366368;
	Wed, 12 Feb 2014 06:46:06 -0800 (PST)
Received: from [192.168.1.15] (212.44.45.208.ip.redstone-isp.net.
	[212.44.45.208])
	by mx.google.com with ESMTPSA id ev4sm6296082wib.1.2014.02.12.06.46.04
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 12 Feb 2014 06:46:05 -0800 (PST)
From: Julian Chesterfield 
Date: Wed, 12 Feb 2014 14:46:03 +0000
Message-Id: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Subject: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi there! Any pointers on the following error I'm getting when trying to build mirage-skeleton on a fresh build server? Ubuntu precise, 12.04.1 LTS.

Thanks!
Julian

root@Build-server:~/mirage-skeleton# opam list
Installed packages for system:
base-bigarray             base  Bigarray library distributed with the OCaml compiler
base-threads              base  Threads library distributed with the OCaml compiler
base-unix                 base  Unix library distributed with the OCaml compiler
cmdliner                 0.9.4  Declarative definition of command line interfaces for OCaml
cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage
cstruct                  1.0.1  access C structures via a camlp4 extension
fieldslib            109.20.03  Syntax extension to define first class values representing record fields, to get and set record fields, iterate and fold over all fields of a record and create new record v
io-page                  1.1.0  Allocate memory pages suitable for aligned I/O
ipaddr                   2.4.0  IP (and MAC) address representation library
lwt                      2.4.4  A cooperative threads library for OCaml
mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for Unix
mirage-console-unix      1.0.0  A Mirage-compatible Console library for Unix
mirage-http              1.1.0  Mirage HTTP client and server driver for Unix
mirage-net-unix          1.1.0  Ethernet network driver for Mirage, using tuntap
mirage-types             1.1.0  Module type definitions for Mirage-compatible applications
mirage-unix              1.1.0  Mirage OS library for Unix compilation
ocamlfind                1.4.0  A library manager for OCaml
ocplib-endian              0.4  Optimised functions to read and write int16/32/64 from strings and bigarrays, based on new primitives added in version 4.01.
optcomp                    1.5  Optional compilation with cpp-like directives
ounit                    2.0.0  Unit testing framework loosely based on HUnit. It is similar to JUnit, and other XUnit testing frameworks
re                       1.2.1  RE is a regular expression library for OCaml
sexplib              110.01.00  Library for serializing OCaml values to and from S-expressions
shared-memory-ring       1.0.0  Shared memory rings for RPC and bytestream communications.
ssl                      0.4.6  Bindings for the libssl
tcpip                    1.1.0  Userlevel TCP/IP stack
tuntap                   0.7.0  TUN/TAP bindings
type_conv            109.60.01  Library for building type-driven syntax extensions
uri                     1.3.13  RFC3986 URI parsing library


root@Build-server:~/mirage-skeleton# make all

.......<--All fine until

stackv4     + Executing: opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
stackv4      The following actions will be performed:
stackv4       - install type_conv.109.60.01 [required by mirage-http]
stackv4       - install ssl.0.4.6 [required by mirage-http]
stackv4       - install fieldslib.109.20.03 [required by mirage-http]
stackv4       - install sexplib.110.01.00 [required by mirage-http]
stackv4       - recompile lwt.2.4.4 [use ssl]
stackv4       - install uri.1.3.13 [required by mirage-http]
stackv4       - recompile cstruct.1.0.1 [use ssl]
stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 failed.
stackv4      
stackv4      ===== ERROR while recompiling mirage.1.1.0 =====
stackv4      # opam-version         1.1.1
stackv4      # os                   linux
stackv4      # command              make install
stackv4      # path                 /root/.opam/system/build/mirage.1.1.0
stackv4      # compiler             system (4.01.0)
stackv4      # exit-code            2
stackv4      # env-file             /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
stackv4      # stdout-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
stackv4      # stderr-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
stackv4      ### stdout ###
stackv4      # ...[truncated]
stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > lib/main.ml.depends
stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml
stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml
stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa lib/main.cmx -o lib/main.native
stackv4      # ./setup.bin -test
stackv4      # ./setup.bin -doc
stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'
stackv4      # make[1]: Entering directory `/root/.opam/system/build/mirage.1.1.0'
stackv4      # ./setup.bin -install
stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'
stackv4      ### stderr ###
stackv4      # ...[truncated]
stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi
stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx
stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
stackv4      # Installed /root/.opam/system/lib/mirage/META
stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage': Text file busy
stackv4      # E: Failure("Command ''cp' '/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' '/root/.opam/system/bin/mirage'' terminated with error code 1")
stackv4      # make[1]: *** [install] Error 1
stackv4      
stackv4      
stackv4      The former state can be restored with opam switch import -f "/root/.opam/system/backup/state-20140112143516.export"
stackv4      'opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' failed.
stackv4      tar.gz
stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
stackv4      Building uri.1.3.13:
stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
stackv4        ocaml setup.ml -build
stackv4        ocaml setup.ml -install
stackv4      Installing uri.1.3.13.
stackv4      
stackv4      =-=-= Installing cohttp.0.9.16 =-=-=
stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
stackv4      Building cohttp.0.9.16:
stackv4        make PREFIX=/root/.opam/system
stackv4        make PREFIX=/root/.opam/system install
stackv4      Installing cohttp.0.9.16.
stackv4      
stackv4      =-=-= Installing io-page.1.1.0 =-=-=
stackv4      Building io-page.1.1.0:
stackv4        make
stackv4        make install
stackv4      Installing io-page.1.1.0.
stackv4      
stackv4      =-=-= Installing shared-memory-ring.1.0.0 =-=-=
stackv4      Building shared-memory-ring.1.0.0:
stackv4        make all
stackv4        make install
stackv4      Installing shared-memory-ring.1.0.0.
stackv4      
stackv4      =-=-= Installing mirage-types.1.1.0 =-=-=
stackv4      Building mirage-types.1.1.0:
stackv4        make install-types
stackv4      Installing mirage-types.1.1.0.
stackv4      
stackv4      =-=-= Installing mirage.1.1.0 =-=-=
stackv4      Building mirage.1.1.0:
stackv4        ./configure --bindir /root/.opam/system/bin
stackv4        make
stackv4        make install
stackv4      Removing mirage.1.1.0.
stackv4        ./configure --bindir /root/.opam/system/bin
stackv4        make uninstall
stackv4      
stackv4      =-=-= Installing mirage-clock-unix.1.0.0 =-=-=
stackv4      Building mirage-clock-unix.1.0.0:
stackv4        make unix-build
stackv4        make unix-install
stackv4      Installing mirage-clock-unix.1.0.0.
stackv4      
stackv4      =-=-= Installing mirage-net-unix.1.1.0 =-=-=
stackv4      Building mirage-net-unix.1.1.0:
stackv4        make
stackv4        make install
stackv4      Installing mirage-net-unix.1.1.0.
stackv4      
stackv4      =-=-= Installing mirage-unix.1.1.0 =-=-=
stackv4      Building mirage-unix.1.1.0:
stackv4        make unix-build
stackv4        make unix-install PREFIX=/root/.opam/system
stackv4      Installing mirage-unix.1.1.0.
stackv4      
stackv4      =-=-= Installing mirage-console-unix.1.0.0 =-=-=
stackv4      Building mirage-console-unix.1.0.0:
stackv4        make unix-build
stackv4        make unix-install
stackv4      Installing mirage-console-unix.1.0.0.
stackv4      
stackv4      =-=-= Installing tcpip.1.1.0 =-=-=
stackv4      Building tcpip.1.1.0:
stackv4        make
stackv4        make install
stackv4      Installing tcpip.1.1.0.
stackv4      
stackv4      =-=-= Installing mirage-http.1.1.0 =-=-=
stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
stackv4      Building mirage-http.1.1.0:
stackv4        make
stackv4        make install
stackv4      Installing mirage-http.1.1.0.
stackv4      
[ERROR]      The command "opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exited with code 4.
make: *** [stackv4-configure] Error 1
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 14:46:14 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 14:46:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDb4k-0002Yt-On; Wed, 12 Feb 2014 14:46:10 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDb4j-0002Yh-6L
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 14:46:09 +0000
Received: from [85.158.139.211:7763] by server-15.bemta-5.messagelabs.com id
	DC/4E-24395-0398BF25; Wed, 12 Feb 2014 14:46:08 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-11.tower-206.messagelabs.com!1392216366!3469518!1
X-Originating-IP: [74.125.82.179]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23704 invoked from network); 12 Feb 2014 14:46:07 -0000
Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com)
	(74.125.82.179)
	by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 14:46:07 -0000
Received: by mail-we0-f179.google.com with SMTP id q58so5921182wes.24
	for ;
	Wed, 12 Feb 2014 06:46:06 -0800 (PST)
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:to:mime-version;
	bh=eYNgHzbeqPhCo/ljkQR/YM2xNI1sL6/rYAjtg/UdUfs=;
	b=GpkcpKqUpbFzKuyVkVNvKL1IyIlT4+U5UbErZhSLHMICfQapsVfw2vNCB4GAAF85X/
	SZjMw5m67zEz14qc9f6JPFjSBHKep14Tms9BwDmloGFkcUvkCUWC9SP+hF9Sp0hrKgAI
	xOB4+Cyu/gxqiJsniDoUGxn78tAe2BAQnfDMzFYKfNqehYgL0EJiLpxXlnxWAeGNP+G2
	x8i2M1lGLsIcj73DDgk5GqQTAoBOMT06FsyQ6eXdUV+W/aDoci9YdSV36P0CpoN+STEF
	nffnj+sqNqcyRhX68DB8ynbSsGow/OO389tM/v4KEsYxOFvirncJyuMhDuD/ii5gkdXU
	/VHg==
X-Gm-Message-State: ALoCoQnfbiLX6CK9tOSpLdYewIuxVmmEO/eGh2cMByNSCIJyJRdLCIOih+oAS2DojiLZy92MCQor
X-Received: by 10.194.188.80 with SMTP id fy16mr1522102wjc.30.1392216366368;
	Wed, 12 Feb 2014 06:46:06 -0800 (PST)
Received: from [192.168.1.15] (212.44.45.208.ip.redstone-isp.net.
	[212.44.45.208])
	by mx.google.com with ESMTPSA id ev4sm6296082wib.1.2014.02.12.06.46.04
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 12 Feb 2014 06:46:05 -0800 (PST)
From: Julian Chesterfield 
Date: Wed, 12 Feb 2014 14:46:03 +0000
Message-Id: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Subject: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi there! Any pointers on the following error I'm getting when trying to build mirage-skeleton on a fresh build server? Ubuntu precise, 12.04.1 LTS.

Thanks!
Julian

root@Build-server:~/mirage-skeleton# opam list
Installed packages for system:
base-bigarray             base  Bigarray library distributed with the OCaml compiler
base-threads              base  Threads library distributed with the OCaml compiler
base-unix                 base  Unix library distributed with the OCaml compiler
cmdliner                 0.9.4  Declarative definition of command line interfaces for OCaml
cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage
cstruct                  1.0.1  access C structures via a camlp4 extension
fieldslib            109.20.03  Syntax extension to define first class values representing record fields, to get and set record fields, iterate and fold over all fields of a record and create new record v
io-page                  1.1.0  Allocate memory pages suitable for aligned I/O
ipaddr                   2.4.0  IP (and MAC) address representation library
lwt                      2.4.4  A cooperative threads library for OCaml
mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for Unix
mirage-console-unix      1.0.0  A Mirage-compatible Console library for Unix
mirage-http              1.1.0  Mirage HTTP client and server driver for Unix
mirage-net-unix          1.1.0  Ethernet network driver for Mirage, using tuntap
mirage-types             1.1.0  Module type definitions for Mirage-compatible applications
mirage-unix              1.1.0  Mirage OS library for Unix compilation
ocamlfind                1.4.0  A library manager for OCaml
ocplib-endian              0.4  Optimised functions to read and write int16/32/64 from strings and bigarrays, based on new primitives added in version 4.01.
optcomp                    1.5  Optional compilation with cpp-like directives
ounit                    2.0.0  Unit testing framework loosely based on HUnit. It is similar to JUnit, and other XUnit testing frameworks
re                       1.2.1  RE is a regular expression library for OCaml
sexplib              110.01.00  Library for serializing OCaml values to and from S-expressions
shared-memory-ring       1.0.0  Shared memory rings for RPC and bytestream communications.
ssl                      0.4.6  Bindings for the libssl
tcpip                    1.1.0  Userlevel TCP/IP stack
tuntap                   0.7.0  TUN/TAP bindings
type_conv            109.60.01  Library for building type-driven syntax extensions
uri                     1.3.13  RFC3986 URI parsing library


root@Build-server:~/mirage-skeleton# make all

.......<--All fine until

stackv4     + Executing: opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
stackv4      The following actions will be performed:
stackv4       - install type_conv.109.60.01 [required by mirage-http]
stackv4       - install ssl.0.4.6 [required by mirage-http]
stackv4       - install fieldslib.109.20.03 [required by mirage-http]
stackv4       - install sexplib.110.01.00 [required by mirage-http]
stackv4       - recompile lwt.2.4.4 [use ssl]
stackv4       - install uri.1.3.13 [required by mirage-http]
stackv4       - recompile cstruct.1.0.1 [use ssl]
stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 failed.
stackv4      
stackv4      ===== ERROR while recompiling mirage.1.1.0 =====
stackv4      # opam-version         1.1.1
stackv4      # os                   linux
stackv4      # command              make install
stackv4      # path                 /root/.opam/system/build/mirage.1.1.0
stackv4      # compiler             system (4.01.0)
stackv4      # exit-code            2
stackv4      # env-file             /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
stackv4      # stdout-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
stackv4      # stderr-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
stackv4      ### stdout ###
stackv4      # ...[truncated]
stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > lib/main.ml.depends
stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml
stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml
stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa lib/main.cmx -o lib/main.native
stackv4      # ./setup.bin -test
stackv4      # ./setup.bin -doc
stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'
stackv4      # make[1]: Entering directory `/root/.opam/system/build/mirage.1.1.0'
stackv4      # ./setup.bin -install
stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'
stackv4      ### stderr ###
stackv4      # ...[truncated]
stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi
stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx
stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
stackv4      # Installed /root/.opam/system/lib/mirage/META
stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage': Text file busy
stackv4      # E: Failure("Command ''cp' '/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' '/root/.opam/system/bin/mirage'' terminated with error code 1")
stackv4      # make[1]: *** [install] Error 1
stackv4      
stackv4      
stackv4      The former state can be restored with opam switch import -f "/root/.opam/system/backup/state-20140112143516.export"
stackv4      'opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' failed.
stackv4      tar.gz
stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
stackv4      Building uri.1.3.13:
stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
stackv4        ocaml setup.ml -build
stackv4        ocaml setup.ml -install
stackv4      Installing uri.1.3.13.
stackv4      
stackv4      =-=-= Installing cohttp.0.9.16 =-=-=
stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
stackv4      Building cohttp.0.9.16:
stackv4        make PREFIX=/root/.opam/system
stackv4        make PREFIX=/root/.opam/system install
stackv4      Installing cohttp.0.9.16.
stackv4      
stackv4      =-=-= Installing io-page.1.1.0 =-=-=
stackv4      Building io-page.1.1.0:
stackv4        make
stackv4        make install
stackv4      Installing io-page.1.1.0.
stackv4      
stackv4      =-=-= Installing shared-memory-ring.1.0.0 =-=-=
stackv4      Building shared-memory-ring.1.0.0:
stackv4        make all
stackv4        make install
stackv4      Installing shared-memory-ring.1.0.0.
stackv4      
stackv4      =-=-= Installing mirage-types.1.1.0 =-=-=
stackv4      Building mirage-types.1.1.0:
stackv4        make install-types
stackv4      Installing mirage-types.1.1.0.
stackv4      
stackv4      =-=-= Installing mirage.1.1.0 =-=-=
stackv4      Building mirage.1.1.0:
stackv4        ./configure --bindir /root/.opam/system/bin
stackv4        make
stackv4        make install
stackv4      Removing mirage.1.1.0.
stackv4        ./configure --bindir /root/.opam/system/bin
stackv4        make uninstall
stackv4      
stackv4      =-=-= Installing mirage-clock-unix.1.0.0 =-=-=
stackv4      Building mirage-clock-unix.1.0.0:
stackv4        make unix-build
stackv4        make unix-install
stackv4      Installing mirage-clock-unix.1.0.0.
stackv4      
stackv4      =-=-= Installing mirage-net-unix.1.1.0 =-=-=
stackv4      Building mirage-net-unix.1.1.0:
stackv4        make
stackv4        make install
stackv4      Installing mirage-net-unix.1.1.0.
stackv4      
stackv4      =-=-= Installing mirage-unix.1.1.0 =-=-=
stackv4      Building mirage-unix.1.1.0:
stackv4        make unix-build
stackv4        make unix-install PREFIX=/root/.opam/system
stackv4      Installing mirage-unix.1.1.0.
stackv4      
stackv4      =-=-= Installing mirage-console-unix.1.0.0 =-=-=
stackv4      Building mirage-console-unix.1.0.0:
stackv4        make unix-build
stackv4        make unix-install
stackv4      Installing mirage-console-unix.1.0.0.
stackv4      
stackv4      =-=-= Installing tcpip.1.1.0 =-=-=
stackv4      Building tcpip.1.1.0:
stackv4        make
stackv4        make install
stackv4      Installing tcpip.1.1.0.
stackv4      
stackv4      =-=-= Installing mirage-http.1.1.0 =-=-=
stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
stackv4      Building mirage-http.1.1.0:
stackv4        make
stackv4        make install
stackv4      Installing mirage-http.1.1.0.
stackv4      
[ERROR]      The command "opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exited with code 4.
make: *** [stackv4-configure] Error 1
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 14:51:06 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 14:51: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 1WDb9W-0002zd-Jk; Wed, 12 Feb 2014 14:51:06 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDb9V-0002zV-Fi
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 14:51:05 +0000
Received: from [85.158.139.211:41546] by server-16.bemta-5.messagelabs.com id
	BE/8C-05060-85A8BF25; Wed, 12 Feb 2014 14:51:04 +0000
X-Env-Sender: thomas.gazagnaire@gmail.com
X-Msg-Ref: server-9.tower-206.messagelabs.com!1392216661!3417136!1
X-Originating-IP: [74.125.82.171]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG,
	ML_RADAR_SPEW_LINKS_14,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10177 invoked from network); 12 Feb 2014 14:51:02 -0000
Received: from mail-we0-f171.google.com (HELO mail-we0-f171.google.com)
	(74.125.82.171)
	by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 14:51:02 -0000
Received: by mail-we0-f171.google.com with SMTP id u56so6091953wes.16
	for ;
	Wed, 12 Feb 2014 06:51:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=content-type:mime-version:subject:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to;
	bh=K42ypAhJKAJsHJo3NMRlI3sGM3pv31OqzRMVEVHjFr8=;
	b=vsbzsYGRnRVuy7hIhOoUeNNPdSJbyiRNjg/swhi4SXpJ98ENUIqrnxyTUusQzxQ7CZ
	yAflytLHPoJj9X+jP8fXpyuoahiBc9tngMKjFRXK4P9uSd57Bc+YaAXWskGcqbd2e92q
	Fpg0GGfDosa8G17l8CTRbP4uF20d3XOb4tjm+l9eIjfw+OhJEAfZ+pzoG8Rn6HESPfzy
	RT1XXvTn6pppiwFROAWk5bwFxGL6u1vT8zWezHYoYcLeiFR1LTl6HiUMclgzXROjt6Am
	hhNOjNi0vYTnjLIN6tB6GDl9R3sk5j5RIZ+HX87ic6TYitPorvEtdq8se1wbZNVVDXj7
	7c7Q==
X-Received: by 10.180.38.41 with SMTP id d9mr2323934wik.9.1392216661682;
	Wed, 12 Feb 2014 06:51:01 -0800 (PST)
Received: from ?IPv6:2001:630:212:248:e1bd:d3ee:f718:29e5?
	([2001:630:212:248:e1bd:d3ee:f718:29e5])
	by mx.google.com with ESMTPSA id t5sm22735157wjw.15.2014.02.12.06.51.00
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 12 Feb 2014 06:51:00 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Gazagnaire 
In-Reply-To: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
Date: Wed, 12 Feb 2014 14:50:59 +0000
Message-Id: 
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
To: Julian Chesterfield 
X-Mailer: Apple Mail (2.1827)
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi Julian,

seems that you are mysteriously missing the 'mirage' package. Installing it first before running 'make' should do the trick.

Thomas


> Hi there! Any pointers on the following error I'm getting when trying to build mirage-skeleton on a fresh build server? Ubuntu precise, 12.04.1 LTS.
> 
> Thanks!
> Julian
> 
> root@Build-server:~/mirage-skeleton# opam list
> Installed packages for system:
> base-bigarray             base  Bigarray library distributed with the OCaml compiler
> base-threads              base  Threads library distributed with the OCaml compiler
> base-unix                 base  Unix library distributed with the OCaml compiler
> cmdliner                 0.9.4  Declarative definition of command line interfaces for OCaml
> cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage
> cstruct                  1.0.1  access C structures via a camlp4 extension
> fieldslib            109.20.03  Syntax extension to define first class values representing record fields, to get and set record fields, iterate and fold over all fields of a record and create new record v
> io-page                  1.1.0  Allocate memory pages suitable for aligned I/O
> ipaddr                   2.4.0  IP (and MAC) address representation library
> lwt                      2.4.4  A cooperative threads library for OCaml
> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for Unix
> mirage-console-unix      1.0.0  A Mirage-compatible Console library for Unix
> mirage-http              1.1.0  Mirage HTTP client and server driver for Unix
> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, using tuntap
> mirage-types             1.1.0  Module type definitions for Mirage-compatible applications
> mirage-unix              1.1.0  Mirage OS library for Unix compilation
> ocamlfind                1.4.0  A library manager for OCaml
> ocplib-endian              0.4  Optimised functions to read and write int16/32/64 from strings and bigarrays, based on new primitives added in version 4.01.
> optcomp                    1.5  Optional compilation with cpp-like directives
> ounit                    2.0.0  Unit testing framework loosely based on HUnit. It is similar to JUnit, and other XUnit testing frameworks
> re                       1.2.1  RE is a regular expression library for OCaml
> sexplib              110.01.00  Library for serializing OCaml values to and from S-expressions
> shared-memory-ring       1.0.0  Shared memory rings for RPC and bytestream communications.
> ssl                      0.4.6  Bindings for the libssl
> tcpip                    1.1.0  Userlevel TCP/IP stack
> tuntap                   0.7.0  TUN/TAP bindings
> type_conv            109.60.01  Library for building type-driven syntax extensions
> uri                     1.3.13  RFC3986 URI parsing library
> 
> 
> root@Build-server:~/mirage-skeleton# make all
> 
> .......<--All fine until
> 
> stackv4     + Executing: opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
> stackv4      The following actions will be performed:
> stackv4       - install type_conv.109.60.01 [required by mirage-http]
> stackv4       - install ssl.0.4.6 [required by mirage-http]
> stackv4       - install fieldslib.109.20.03 [required by mirage-http]
> stackv4       - install sexplib.110.01.00 [required by mirage-http]
> stackv4       - recompile lwt.2.4.4 [use ssl]
> stackv4       - install uri.1.3.13 [required by mirage-http]
> stackv4       - recompile cstruct.1.0.1 [use ssl]
> stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 failed.
> stackv4      
> stackv4      ===== ERROR while recompiling mirage.1.1.0 =====
> stackv4      # opam-version         1.1.1
> stackv4      # os                   linux
> stackv4      # command              make install
> stackv4      # path                 /root/.opam/system/build/mirage.1.1.0
> stackv4      # compiler             system (4.01.0)
> stackv4      # exit-code            2
> stackv4      # env-file             /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
> stackv4      # stdout-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
> stackv4      # stderr-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
> stackv4      ### stdout ###
> stackv4      # ...[truncated]
> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > lib/main.ml.depends
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa lib/main.cmx -o lib/main.native
> stackv4      # ./setup.bin -test
> stackv4      # ./setup.bin -doc
> stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'
> stackv4      # make[1]: Entering directory `/root/.opam/system/build/mirage.1.1.0'
> stackv4      # ./setup.bin -install
> stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'
> stackv4      ### stderr ###
> stackv4      # ...[truncated]
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/META
> stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage': Text file busy
> stackv4      # E: Failure("Command ''cp' '/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' '/root/.opam/system/bin/mirage'' terminated with error code 1")
> stackv4      # make[1]: *** [install] Error 1
> stackv4      
> stackv4      
> stackv4      The former state can be restored with opam switch import -f "/root/.opam/system/backup/state-20140112143516.export"
> stackv4      'opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' failed.
> stackv4      tar.gz
> stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
> stackv4      Building uri.1.3.13:
> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
> stackv4        ocaml setup.ml -build
> stackv4        ocaml setup.ml -install
> stackv4      Installing uri.1.3.13.
> stackv4      
> stackv4      =-=-= Installing cohttp.0.9.16 =-=-=
> stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Building cohttp.0.9.16:
> stackv4        make PREFIX=/root/.opam/system
> stackv4        make PREFIX=/root/.opam/system install
> stackv4      Installing cohttp.0.9.16.
> stackv4      
> stackv4      =-=-= Installing io-page.1.1.0 =-=-=
> stackv4      Building io-page.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing io-page.1.1.0.
> stackv4      
> stackv4      =-=-= Installing shared-memory-ring.1.0.0 =-=-=
> stackv4      Building shared-memory-ring.1.0.0:
> stackv4        make all
> stackv4        make install
> stackv4      Installing shared-memory-ring.1.0.0.
> stackv4      
> stackv4      =-=-= Installing mirage-types.1.1.0 =-=-=
> stackv4      Building mirage-types.1.1.0:
> stackv4        make install-types
> stackv4      Installing mirage-types.1.1.0.
> stackv4      
> stackv4      =-=-= Installing mirage.1.1.0 =-=-=
> stackv4      Building mirage.1.1.0:
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make
> stackv4        make install
> stackv4      Removing mirage.1.1.0.
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make uninstall
> stackv4      
> stackv4      =-=-= Installing mirage-clock-unix.1.0.0 =-=-=
> stackv4      Building mirage-clock-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-clock-unix.1.0.0.
> stackv4      
> stackv4      =-=-= Installing mirage-net-unix.1.1.0 =-=-=
> stackv4      Building mirage-net-unix.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-net-unix.1.1.0.
> stackv4      
> stackv4      =-=-= Installing mirage-unix.1.1.0 =-=-=
> stackv4      Building mirage-unix.1.1.0:
> stackv4        make unix-build
> stackv4        make unix-install PREFIX=/root/.opam/system
> stackv4      Installing mirage-unix.1.1.0.
> stackv4      
> stackv4      =-=-= Installing mirage-console-unix.1.0.0 =-=-=
> stackv4      Building mirage-console-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-console-unix.1.0.0.
> stackv4      
> stackv4      =-=-= Installing tcpip.1.1.0 =-=-=
> stackv4      Building tcpip.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing tcpip.1.1.0.
> stackv4      
> stackv4      =-=-= Installing mirage-http.1.1.0 =-=-=
> stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Building mirage-http.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-http.1.1.0.
> stackv4      
> [ERROR]      The command "opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exited with code 4.
> make: *** [stackv4-configure] Error 1
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 14:51:06 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 14:51: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 1WDb9W-0002zd-Jk; Wed, 12 Feb 2014 14:51:06 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDb9V-0002zV-Fi
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 14:51:05 +0000
Received: from [85.158.139.211:41546] by server-16.bemta-5.messagelabs.com id
	BE/8C-05060-85A8BF25; Wed, 12 Feb 2014 14:51:04 +0000
X-Env-Sender: thomas.gazagnaire@gmail.com
X-Msg-Ref: server-9.tower-206.messagelabs.com!1392216661!3417136!1
X-Originating-IP: [74.125.82.171]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG,
	ML_RADAR_SPEW_LINKS_14,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10177 invoked from network); 12 Feb 2014 14:51:02 -0000
Received: from mail-we0-f171.google.com (HELO mail-we0-f171.google.com)
	(74.125.82.171)
	by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 14:51:02 -0000
Received: by mail-we0-f171.google.com with SMTP id u56so6091953wes.16
	for ;
	Wed, 12 Feb 2014 06:51:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=content-type:mime-version:subject:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to;
	bh=K42ypAhJKAJsHJo3NMRlI3sGM3pv31OqzRMVEVHjFr8=;
	b=vsbzsYGRnRVuy7hIhOoUeNNPdSJbyiRNjg/swhi4SXpJ98ENUIqrnxyTUusQzxQ7CZ
	yAflytLHPoJj9X+jP8fXpyuoahiBc9tngMKjFRXK4P9uSd57Bc+YaAXWskGcqbd2e92q
	Fpg0GGfDosa8G17l8CTRbP4uF20d3XOb4tjm+l9eIjfw+OhJEAfZ+pzoG8Rn6HESPfzy
	RT1XXvTn6pppiwFROAWk5bwFxGL6u1vT8zWezHYoYcLeiFR1LTl6HiUMclgzXROjt6Am
	hhNOjNi0vYTnjLIN6tB6GDl9R3sk5j5RIZ+HX87ic6TYitPorvEtdq8se1wbZNVVDXj7
	7c7Q==
X-Received: by 10.180.38.41 with SMTP id d9mr2323934wik.9.1392216661682;
	Wed, 12 Feb 2014 06:51:01 -0800 (PST)
Received: from ?IPv6:2001:630:212:248:e1bd:d3ee:f718:29e5?
	([2001:630:212:248:e1bd:d3ee:f718:29e5])
	by mx.google.com with ESMTPSA id t5sm22735157wjw.15.2014.02.12.06.51.00
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 12 Feb 2014 06:51:00 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Gazagnaire 
In-Reply-To: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
Date: Wed, 12 Feb 2014 14:50:59 +0000
Message-Id: 
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
To: Julian Chesterfield 
X-Mailer: Apple Mail (2.1827)
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi Julian,

seems that you are mysteriously missing the 'mirage' package. Installing it first before running 'make' should do the trick.

Thomas


> Hi there! Any pointers on the following error I'm getting when trying to build mirage-skeleton on a fresh build server? Ubuntu precise, 12.04.1 LTS.
> 
> Thanks!
> Julian
> 
> root@Build-server:~/mirage-skeleton# opam list
> Installed packages for system:
> base-bigarray             base  Bigarray library distributed with the OCaml compiler
> base-threads              base  Threads library distributed with the OCaml compiler
> base-unix                 base  Unix library distributed with the OCaml compiler
> cmdliner                 0.9.4  Declarative definition of command line interfaces for OCaml
> cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage
> cstruct                  1.0.1  access C structures via a camlp4 extension
> fieldslib            109.20.03  Syntax extension to define first class values representing record fields, to get and set record fields, iterate and fold over all fields of a record and create new record v
> io-page                  1.1.0  Allocate memory pages suitable for aligned I/O
> ipaddr                   2.4.0  IP (and MAC) address representation library
> lwt                      2.4.4  A cooperative threads library for OCaml
> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for Unix
> mirage-console-unix      1.0.0  A Mirage-compatible Console library for Unix
> mirage-http              1.1.0  Mirage HTTP client and server driver for Unix
> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, using tuntap
> mirage-types             1.1.0  Module type definitions for Mirage-compatible applications
> mirage-unix              1.1.0  Mirage OS library for Unix compilation
> ocamlfind                1.4.0  A library manager for OCaml
> ocplib-endian              0.4  Optimised functions to read and write int16/32/64 from strings and bigarrays, based on new primitives added in version 4.01.
> optcomp                    1.5  Optional compilation with cpp-like directives
> ounit                    2.0.0  Unit testing framework loosely based on HUnit. It is similar to JUnit, and other XUnit testing frameworks
> re                       1.2.1  RE is a regular expression library for OCaml
> sexplib              110.01.00  Library for serializing OCaml values to and from S-expressions
> shared-memory-ring       1.0.0  Shared memory rings for RPC and bytestream communications.
> ssl                      0.4.6  Bindings for the libssl
> tcpip                    1.1.0  Userlevel TCP/IP stack
> tuntap                   0.7.0  TUN/TAP bindings
> type_conv            109.60.01  Library for building type-driven syntax extensions
> uri                     1.3.13  RFC3986 URI parsing library
> 
> 
> root@Build-server:~/mirage-skeleton# make all
> 
> .......<--All fine until
> 
> stackv4     + Executing: opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
> stackv4      The following actions will be performed:
> stackv4       - install type_conv.109.60.01 [required by mirage-http]
> stackv4       - install ssl.0.4.6 [required by mirage-http]
> stackv4       - install fieldslib.109.20.03 [required by mirage-http]
> stackv4       - install sexplib.110.01.00 [required by mirage-http]
> stackv4       - recompile lwt.2.4.4 [use ssl]
> stackv4       - install uri.1.3.13 [required by mirage-http]
> stackv4       - recompile cstruct.1.0.1 [use ssl]
> stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 failed.
> stackv4      
> stackv4      ===== ERROR while recompiling mirage.1.1.0 =====
> stackv4      # opam-version         1.1.1
> stackv4      # os                   linux
> stackv4      # command              make install
> stackv4      # path                 /root/.opam/system/build/mirage.1.1.0
> stackv4      # compiler             system (4.01.0)
> stackv4      # exit-code            2
> stackv4      # env-file             /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
> stackv4      # stdout-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
> stackv4      # stderr-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
> stackv4      ### stdout ###
> stackv4      # ...[truncated]
> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > lib/main.ml.depends
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa lib/main.cmx -o lib/main.native
> stackv4      # ./setup.bin -test
> stackv4      # ./setup.bin -doc
> stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'
> stackv4      # make[1]: Entering directory `/root/.opam/system/build/mirage.1.1.0'
> stackv4      # ./setup.bin -install
> stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'
> stackv4      ### stderr ###
> stackv4      # ...[truncated]
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/META
> stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage': Text file busy
> stackv4      # E: Failure("Command ''cp' '/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' '/root/.opam/system/bin/mirage'' terminated with error code 1")
> stackv4      # make[1]: *** [install] Error 1
> stackv4      
> stackv4      
> stackv4      The former state can be restored with opam switch import -f "/root/.opam/system/backup/state-20140112143516.export"
> stackv4      'opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' failed.
> stackv4      tar.gz
> stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
> stackv4      Building uri.1.3.13:
> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
> stackv4        ocaml setup.ml -build
> stackv4        ocaml setup.ml -install
> stackv4      Installing uri.1.3.13.
> stackv4      
> stackv4      =-=-= Installing cohttp.0.9.16 =-=-=
> stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Building cohttp.0.9.16:
> stackv4        make PREFIX=/root/.opam/system
> stackv4        make PREFIX=/root/.opam/system install
> stackv4      Installing cohttp.0.9.16.
> stackv4      
> stackv4      =-=-= Installing io-page.1.1.0 =-=-=
> stackv4      Building io-page.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing io-page.1.1.0.
> stackv4      
> stackv4      =-=-= Installing shared-memory-ring.1.0.0 =-=-=
> stackv4      Building shared-memory-ring.1.0.0:
> stackv4        make all
> stackv4        make install
> stackv4      Installing shared-memory-ring.1.0.0.
> stackv4      
> stackv4      =-=-= Installing mirage-types.1.1.0 =-=-=
> stackv4      Building mirage-types.1.1.0:
> stackv4        make install-types
> stackv4      Installing mirage-types.1.1.0.
> stackv4      
> stackv4      =-=-= Installing mirage.1.1.0 =-=-=
> stackv4      Building mirage.1.1.0:
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make
> stackv4        make install
> stackv4      Removing mirage.1.1.0.
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make uninstall
> stackv4      
> stackv4      =-=-= Installing mirage-clock-unix.1.0.0 =-=-=
> stackv4      Building mirage-clock-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-clock-unix.1.0.0.
> stackv4      
> stackv4      =-=-= Installing mirage-net-unix.1.1.0 =-=-=
> stackv4      Building mirage-net-unix.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-net-unix.1.1.0.
> stackv4      
> stackv4      =-=-= Installing mirage-unix.1.1.0 =-=-=
> stackv4      Building mirage-unix.1.1.0:
> stackv4        make unix-build
> stackv4        make unix-install PREFIX=/root/.opam/system
> stackv4      Installing mirage-unix.1.1.0.
> stackv4      
> stackv4      =-=-= Installing mirage-console-unix.1.0.0 =-=-=
> stackv4      Building mirage-console-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-console-unix.1.0.0.
> stackv4      
> stackv4      =-=-= Installing tcpip.1.1.0 =-=-=
> stackv4      Building tcpip.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing tcpip.1.1.0.
> stackv4      
> stackv4      =-=-= Installing mirage-http.1.1.0 =-=-=
> stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Building mirage-http.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-http.1.1.0.
> stackv4      
> [ERROR]      The command "opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exited with code 4.
> make: *** [stackv4-configure] Error 1
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 14:51:33 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 14:51:33 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDb9w-000323-Mi; Wed, 12 Feb 2014 14:51:32 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDb9v-00031t-6N
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 14:51:31 +0000
Received: from [85.158.139.211:2789] by server-17.bemta-5.messagelabs.com id
	53/07-31975-27A8BF25; Wed, 12 Feb 2014 14:51:30 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-5.tower-206.messagelabs.com!1392216689!3345755!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11774 invoked from network); 12 Feb 2014 14:51:29 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-5.tower-206.messagelabs.com with SMTP;
	12 Feb 2014 14:51:29 -0000
Received: (qmail 218 invoked by uid 634); 12 Feb 2014 14:51:29 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Wed, 12 Feb 2014 14:51:29 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: 
Date: Wed, 12 Feb 2014 14:51:28 +0000
Message-Id: <89B99EC2-CFBC-4EED-AF4E-9FBCEC470ED4@recoil.org>
References: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
	<5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
	<0E25A163-D7CE-49ED-B2EF-ABBA4880902A@cam.ac.uk>
	
To: Amir M Chaudhry 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 12 Feb 2014, at 00:12, Amir Chaudhry  wrote:
> 
> 
> I tried taking the html and playing with it locally.  Wrapping in a 
 doesn't make any difference.
> 
> For my code highlighting I'd simply copy/pasted what bootstrap had and looking at the CSS, my `pre` has the following lines:
>  word-break: break-all;
>  word-wrap: break-word;

Many thanks for tracking this down!  I've committed your fix and the blog renders fine on the iPhone again,  yay!

-anil

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 14:51:33 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 14:51:33 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDb9w-000323-Mi; Wed, 12 Feb 2014 14:51:32 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDb9v-00031t-6N
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 14:51:31 +0000
Received: from [85.158.139.211:2789] by server-17.bemta-5.messagelabs.com id
	53/07-31975-27A8BF25; Wed, 12 Feb 2014 14:51:30 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-5.tower-206.messagelabs.com!1392216689!3345755!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11774 invoked from network); 12 Feb 2014 14:51:29 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-5.tower-206.messagelabs.com with SMTP;
	12 Feb 2014 14:51:29 -0000
Received: (qmail 218 invoked by uid 634); 12 Feb 2014 14:51:29 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Wed, 12 Feb 2014 14:51:29 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: 
Date: Wed, 12 Feb 2014 14:51:28 +0000
Message-Id: <89B99EC2-CFBC-4EED-AF4E-9FBCEC470ED4@recoil.org>
References: <20E69C47-3CDA-4A16-A62B-9E95D65D6FD2@recoil.org>
	<5F206196-5265-4D56-8DC5-757D8E72EE11@nottingham.ac.uk>
	<0E25A163-D7CE-49ED-B2EF-ABBA4880902A@cam.ac.uk>
	
To: Amir M Chaudhry 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] zurb responsive problem on mobiles
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 12 Feb 2014, at 00:12, Amir Chaudhry  wrote:
> 
> 
> I tried taking the html and playing with it locally.  Wrapping in a 
 doesn't make any difference.
> 
> For my code highlighting I'd simply copy/pasted what bootstrap had and looking at the CSS, my `pre` has the following lines:
>  word-break: break-all;
>  word-wrap: break-word;

Many thanks for tracking this down!  I've committed your fix and the blog renders fine on the iPhone again,  yay!

-anil

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 14:52:21 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 14:52: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 1WDbAj-00038S-BG; Wed, 12 Feb 2014 14:52:21 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDbAh-000380-5D
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 14:52:19 +0000
Received: from [85.158.137.68:45846] by server-15.bemta-3.messagelabs.com id
	DB/8B-19263-2AA8BF25; Wed, 12 Feb 2014 14:52:18 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-12.tower-31.messagelabs.com!1392216734!387948!1
X-Originating-IP: [209.85.192.178]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6954 invoked from network); 12 Feb 2014 14:52:16 -0000
Received: from mail-pd0-f178.google.com (HELO mail-pd0-f178.google.com)
	(209.85.192.178)
	by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 14:52:16 -0000
Received: by mail-pd0-f178.google.com with SMTP id fp1so415331pdb.9
	for ;
	Wed, 12 Feb 2014 06:52:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=Szw47c1oSzfZ6ZCtqj3U/tgTzRelsOdjaXa9SWnvPs0=;
	b=hQMcg2TKzHsW1N+53bAZALy2VxLFtuibBlKU5/TYTczTDR/mwDSSJT57EFdeTB0/xE
	yktNAbE/kraHHUr4HwY+SsfNrXKChenIEJhIG0+zz93SXruCkmPTieTRC2ZSK/N+bDqW
	ez5Kph1/eHG52u/+x3PmJsgGBkrVrCwFZBQvocPAZxAuZG8pogbV/VrE3bv3PKmubzCp
	Cx9RqMfDEeTrBdaFaOCAWMBHBX/twQKy092VgS07tT934cLJscegJfI8x53ICB4e0ZE5
	vpkokLd7MIxw1NiwTHYoHii3TMwMh6zAz0P1rx4uf92AFYgmu3aVgJb9NH9DrvxNN05c
	4qlg==
MIME-Version: 1.0
X-Received: by 10.68.202.8 with SMTP id ke8mr52056952pbc.86.1392216734247;
	Wed, 12 Feb 2014 06:52:14 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Wed, 12 Feb 2014 06:52:14 -0800 (PST)
In-Reply-To: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
Date: Wed, 12 Feb 2014 14:52:14 +0000
Message-ID: 
From: David Scott 
To: Julian Chesterfield 
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1816144151470481823=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============1816144151470481823==
Content-Type: multipart/alternative; boundary=047d7b15a693e52f4204f236b7f8

--047d7b15a693e52f4204f236b7f8
Content-Type: text/plain; charset=ISO-8859-1

Hi,

The problem is triggered by the "mirage" command-line tool attempting to
replace its own binary:

> stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage':
Text file busy

As a workaround, try running "opam upgrade mirage" and then try "make all"
again -- by pre-upgrading mirage you should bypass the problem.

I had a quick scan through the mirage/mirage issues list on github and
couldn't spot this one. It's probably worth filing this as a bug so we
don't forget. Perhaps we could fix it by changing mirage/mirage opam
install to "mv mirage mirage.bak; cp newmirage mirage".

Cheers,
Dave


On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield <
julian.chesterfield@onapp.com> wrote:

> Hi there! Any pointers on the following error I'm getting when trying to
> build mirage-skeleton on a fresh build server? Ubuntu precise, 12.04.1 LTS.
>
> Thanks!
> Julian
>
> root@Build-server:~/mirage-skeleton# opam list
> Installed packages for system:
> base-bigarray             base  Bigarray library distributed with the
> OCaml compiler
> base-threads              base  Threads library distributed with the OCaml
> compiler
> base-unix                 base  Unix library distributed with the OCaml
> compiler
> cmdliner                 0.9.4  Declarative definition of command line
> interfaces for OCaml
> cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage
> cstruct                  1.0.1  access C structures via a camlp4 extension
> fieldslib            109.20.03  Syntax extension to define first class
> values representing record fields, to get and set record fields, iterate
> and fold over all fields of a record and create new record v
> io-page                  1.1.0  Allocate memory pages suitable for aligned
> I/O
> ipaddr                   2.4.0  IP (and MAC) address representation library
> lwt                      2.4.4  A cooperative threads library for OCaml
> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for Unix
> mirage-console-unix      1.0.0  A Mirage-compatible Console library for
> Unix
> mirage-http              1.1.0  Mirage HTTP client and server driver for
> Unix
> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, using
> tuntap
> mirage-types             1.1.0  Module type definitions for
> Mirage-compatible applications
> mirage-unix              1.1.0  Mirage OS library for Unix compilation
> ocamlfind                1.4.0  A library manager for OCaml
> ocplib-endian              0.4  Optimised functions to read and write
> int16/32/64 from strings and bigarrays, based on new primitives added in
> version 4.01.
> optcomp                    1.5  Optional compilation with cpp-like
> directives
> ounit                    2.0.0  Unit testing framework loosely based on
> HUnit. It is similar to JUnit, and other XUnit testing frameworks
> re                       1.2.1  RE is a regular expression library for
> OCaml
> sexplib              110.01.00  Library for serializing OCaml values to
> and from S-expressions
> shared-memory-ring       1.0.0  Shared memory rings for RPC and bytestream
> communications.
> ssl                      0.4.6  Bindings for the libssl
> tcpip                    1.1.0  Userlevel TCP/IP stack
> tuntap                   0.7.0  TUN/TAP bindings
> type_conv            109.60.01  Library for building type-driven syntax
> extensions
> uri                     1.3.13  RFC3986 URI parsing library
>
>
> root@Build-server:~/mirage-skeleton# make all
>
> .......<--All fine until
>
> stackv4     + Executing: opam install --yes mirage-clock-unix
> mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
> stackv4      The following actions will be performed:
> stackv4       - install type_conv.109.60.01 [required by mirage-http]
> stackv4       - install ssl.0.4.6 [required by mirage-http]
> stackv4       - install fieldslib.109.20.03 [required by mirage-http]
> stackv4       - install sexplib.110.01.00 [required by mirage-http]
> stackv4       - recompile lwt.2.4.4 [use ssl]
> stackv4       - install uri.1.3.13 [required by mirage-http]
> stackv4       - recompile cstruct.1.0.1 [use ssl]
> stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0
> failed.
> stackv4
> stackv4      ===== ERROR while recompiling mirage.1.1.0 =====
> stackv4      # opam-version         1.1.1
> stackv4      # os                   linux
> stackv4      # command              make install
> stackv4      # path                 /root/.opam/system/build/mirage.1.1.0
> stackv4      # compiler             system (4.01.0)
> stackv4      # exit-code            2
> stackv4      # env-file
> /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
> stackv4      # stdout-file
>  /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
> stackv4      # stderr-file
>  /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
> stackv4      ### stdout ###
> stackv4      # ...[truncated]
> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package cmdliner
> -package dynlink -package ipaddr -package lwt -package mirage-types
> -package mirage-types.lwt -package unix -modules lib/main.ml >
> lib/main.ml.depends
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot
> -bin-annot -principal -I lib -package cmdliner -package dynlink -package
> ipaddr -package lwt -package mirage-types -package mirage-types.lwt
> -package unix -I lib -o lib/main.cmo lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot
> -bin-annot -principal -I lib -package cmdliner -package dynlink -package
> ipaddr -package lwt -package mirage-types -package mirage-types.lwt
> -package unix -I lib -o lib/main.cmx lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg
> -package cmdliner -package dynlink -package ipaddr -package lwt -package
> mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa
> lib/main.cmx -o lib/main.native
> stackv4      # ./setup.bin -test
> stackv4      # ./setup.bin -doc
> stackv4      # make[1]: Leaving directory
> `/root/.opam/system/build/mirage.1.1.0'
> stackv4      # make[1]: Entering directory
> `/root/.opam/system/build/mirage.1.1.0'
> stackv4      # ./setup.bin -install
> stackv4      # make[1]: Leaving directory
> `/root/.opam/system/build/mirage.1.1.0'
> stackv4      ### stderr ###
> stackv4      # ...[truncated]
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/META
> stackv4      # cp: cannot create regular file
> `/root/.opam/system/bin/mirage': Text file busy
> stackv4      # E: Failure("Command ''cp'
> '/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native'
> '/root/.opam/system/bin/mirage'' terminated with error code 1")
> stackv4      # make[1]: *** [install] Error 1
> stackv4
> stackv4
> stackv4      The former state can be restored with opam switch import -f
> "/root/.opam/system/backup/state-20140112143516.export"
> stackv4      'opam install --yes mirage-clock-unix mirage-console-unix
> mirage-http mirage-net-unix mirage-unix tcpip' failed.
> stackv4      tar.gz
> stackv4      Downloading
> https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
> stackv4      Building uri.1.3.13:
> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
> stackv4        ocaml setup.ml -build
> stackv4        ocaml setup.ml -install
> stackv4      Installing uri.1.3.13.
> stackv4
> stackv4      =-=-= Installing cohttp.0.9.16 =-=-=
> stackv4      default    Downloading
> https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Downloading
> https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Building cohttp.0.9.16:
> stackv4        make PREFIX=/root/.opam/system
> stackv4        make PREFIX=/root/.opam/system install
> stackv4      Installing cohttp.0.9.16.
> stackv4
> stackv4      =-=-= Installing io-page.1.1.0 =-=-=
> stackv4      Building io-page.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing io-page.1.1.0.
> stackv4
> stackv4      =-=-= Installing shared-memory-ring.1.0.0 =-=-=
> stackv4      Building shared-memory-ring.1.0.0:
> stackv4        make all
> stackv4        make install
> stackv4      Installing shared-memory-ring.1.0.0.
> stackv4
> stackv4      =-=-= Installing mirage-types.1.1.0 =-=-=
> stackv4      Building mirage-types.1.1.0:
> stackv4        make install-types
> stackv4      Installing mirage-types.1.1.0.
> stackv4
> stackv4      =-=-= Installing mirage.1.1.0 =-=-=
> stackv4      Building mirage.1.1.0:
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make
> stackv4        make install
> stackv4      Removing mirage.1.1.0.
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make uninstall
> stackv4
> stackv4      =-=-= Installing mirage-clock-unix.1.0.0 =-=-=
> stackv4      Building mirage-clock-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-clock-unix.1.0.0.
> stackv4
> stackv4      =-=-= Installing mirage-net-unix.1.1.0 =-=-=
> stackv4      Building mirage-net-unix.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-net-unix.1.1.0.
> stackv4
> stackv4      =-=-= Installing mirage-unix.1.1.0 =-=-=
> stackv4      Building mirage-unix.1.1.0:
> stackv4        make unix-build
> stackv4        make unix-install PREFIX=/root/.opam/system
> stackv4      Installing mirage-unix.1.1.0.
> stackv4
> stackv4      =-=-= Installing mirage-console-unix.1.0.0 =-=-=
> stackv4      Building mirage-console-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-console-unix.1.0.0.
> stackv4
> stackv4      =-=-= Installing tcpip.1.1.0 =-=-=
> stackv4      Building tcpip.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing tcpip.1.1.0.
> stackv4
> stackv4      =-=-= Installing mirage-http.1.1.0 =-=-=
> stackv4      default    Downloading
> https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Downloading
> https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Building mirage-http.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-http.1.1.0.
> stackv4
> [ERROR]      The command "opam install --yes mirage-clock-unix
> mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exited
> with code 4.
> make: *** [stackv4-configure] Error 1
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>



-- 
Dave Scott

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


Hi,

The problem is triggered by the &qu=
ot;mirage" command-line tool attempting to replace its own binary:

> stackv4 =A0 =A0 =A0# cp: cannot create regular file `/root/.opa=
m/system/bin/mirage': Text file busy



=

As a workaround, try running "opam upgrade mirage" and then tr=
y "make all" again -- by pre-upgrading mirage you should bypass t=
he problem.



I h=
ad a quick scan through the mirage/mirage issues list on github and couldn&=
#39;t spot this one. It's probably worth filing this as a bug so we don=
't forget. Perhaps we could fix it by changing mirage/mirage opam insta=
ll to "mv mirage mirage.bak; cp newmirage mirage".



Che=
ers,
Dave




On Wed,=
 Feb 12, 2014 at 2:46 PM, Julian Chesterfield <julian.chesterf=
ield@onapp.com> wrote:


Hi there! Any pointers on the following erro=
r I'm getting when trying to build mirage-skeleton on a fresh build ser=
ver? Ubuntu precise, 12.04.1 LTS.




Thanks!

Julian



root@Build-server:~/mirage-skeleton# opam list

Installed packages for system:

base-bigarray =A0 =A0 =A0 =A0 =A0 =A0 base =A0Bigarray library distributed =
with the OCaml compiler

base-threads =A0 =A0 =A0 =A0 =A0 =A0 =A0base =A0Threads library distributed=
 with the OCaml compiler

base-unix =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 base =A0Unix library distributed =
with the OCaml compiler

cmdliner =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0.9.4 =A0Declarative definition of=
 command line interfaces for OCaml

cohttp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00.9.16 =A0HTTP library for Lwt, A=
sync and Mirage

cstruct =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.0.1 =A0access C structures via=
 a camlp4 extension

fieldslib =A0 =A0 =A0 =A0 =A0 =A0109.20.03 =A0Syntax extension to define fi=
rst class values representing record fields, to get and set record fields, =
iterate and fold over all fields of a record and create new record v

io-page =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.1.0 =A0Allocate memory pages s=
uitable for aligned I/O

ipaddr =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.4.0 =A0IP (and MAC) address re=
presentation library

lwt =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02.4.4 =A0A cooperative threa=
ds library for OCaml

mirage-clock-unix =A0 =A0 =A0 =A01.0.0 =A0A Mirage-compatible Clock library=
 for Unix

mirage-console-unix =A0 =A0 =A01.0.0 =A0A Mirage-compatible Console library=
 for Unix

mirage-http =A0 =A0 =A0 =A0 =A0 =A0 =A01.1.0 =A0Mirage HTTP client and serv=
er driver for Unix

mirage-net-unix =A0 =A0 =A0 =A0 =A01.1.0 =A0Ethernet network driver for Mir=
age, using tuntap

mirage-types =A0 =A0 =A0 =A0 =A0 =A0 1.1.0 =A0Module type definitions for M=
irage-compatible applications

mirage-unix =A0 =A0 =A0 =A0 =A0 =A0 =A01.1.0 =A0Mirage OS library for Unix =
compilation

ocamlfind =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.4.0 =A0A library manager for OCa=
ml

ocplib-endian =A0 =A0 =A0 =A0 =A0 =A0 =A00.4 =A0Optimised functions to read=
 and write int16/32/64 from strings and bigarrays, based on new primitives =
added in version 4.01.

optcomp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.5 =A0Optional compilation =
with cpp-like directives

ounit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02.0.0 =A0Unit testing framewor=
k loosely based on HUnit. It is similar to JUnit, and other XUnit testing f=
rameworks

re =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1.2.1 =A0RE is a regular exp=
ression library for OCaml

sexplib =A0 =A0 =A0 =A0 =A0 =A0 =A0110.01.00 =A0Library for serializing OCa=
ml values to and from S-expressions

shared-memory-ring =A0 =A0 =A0 1.0.0 =A0Shared memory rings for RPC and byt=
estream communications.

ssl =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00.4.6 =A0Bindings for the li=
bssl

tcpip =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.1.0 =A0Userlevel TCP/IP stac=
k

tuntap =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0.7.0 =A0TUN/TAP bindings

type_conv =A0 =A0 =A0 =A0 =A0 =A0109.60.01 =A0Library for building type-dri=
ven syntax extensions

uri =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1.3.13 =A0RFC3986 URI parsing l=
ibrary





root@Build-server:~/mirage-skeleton# make all



.......<--All fine until



stackv4 =A0 =A0 + Executing: opam install --yes mirage-clock-unix mirage-co=
nsole-unix mirage-http mirage-net-unix mirage-unix tcpip

stackv4 =A0 =A0 =A0The following actions will be performed:

stackv4 =A0 =A0 =A0 - install type_conv.109.60.01 [required by mirage-http]=


stackv4 =A0 =A0 =A0 - install ssl.0.4.6 [required by mirage-http]

stackv4 =A0 =A0 =A0 - install fieldslib.109.20.03 [required by mirage-http]=


stackv4 =A0 =A0 =A0 - install sexplib.110.01.00 [required by mirage-http]
stackv4 =A0 =A0 =A0 - recompile lwt.2.4.4 [use ssl]

stackv4 =A0 =A0 =A0 - install uri.1.3.13 [required by mirage-http]

stackv4 =A0 =A0 =A0 - recompile cstruct.1.0.1 [use ssl]

stackv4 =A0 =A0 =A0 - install cohttp[ERROR] The compilation of mirage.1.1.0=
 failed.

stackv4

stackv4 =A0 =A0 =A0=3D=3D=3D=3D=3D ERROR while recompiling mirage.1.1.0 =3D=
=3D=3D=3D=3D

stackv4 =A0 =A0 =A0# opam-version =A0 =A0 =A0 =A0 1.1.1

stackv4 =A0 =A0 =A0# os =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 linux

stackv4 =A0 =A0 =A0# command =A0 =A0 =A0 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0# path =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /root/.opam/syste=
m/build/mirage.1.1.0

stackv4 =A0 =A0 =A0# compiler =A0 =A0 =A0 =A0 =A0 =A0 system (4.01.0)

stackv4 =A0 =A0 =A0# exit-code =A0 =A0 =A0 =A0 =A0 =A02

stackv4 =A0 =A0 =A0# env-file =A0 =A0 =A0 =A0 =A0 =A0 /root/.opam/system/bu=
ild/mirage.1.1.0/mirage-17018-e0ba4f.env

stackv4 =A0 =A0 =A0# stdout-file =A0 =A0 =A0 =A0 =A0/root/.opam/system/buil=
d/mirage.1.1.0/mirage-17018-e0ba4f.out

stackv4 =A0 =A0 =A0# stderr-file =A0 =A0 =A0 =A0 =A0/root/.opam/system/buil=
d/mirage.1.1.0/mirage-17018-e0ba4f.err

stackv4 =A0 =A0 =A0### stdout ###

stackv4 =A0 =A0 =A0# ...[truncated]

stackv4 =A0 =A0 =A0# /root/.opam/system/bin/ocamlfind ocamldep -package cmd=
liner -package dynlink -package ipaddr -package lwt -package mirage-types -=
package mirage-types.lwt -package unix -modules lib/main.ml > lib/main.ml.depends


stackv4 =A0 =A0 =A0# /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot -=
bin-annot -principal -I lib -package cmdliner -package dynlink -package ipa=
ddr -package lwt -package mirage-types -package mirage-types.lwt -package u=
nix -I lib -o lib/main.cmo lib/main.ml


stackv4 =A0 =A0 =A0# /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot=
 -bin-annot -principal -I lib -package cmdliner -package dynlink -package i=
paddr -package lwt -package mirage-types -package mirage-types.lwt -package=
 unix -I lib -o lib/main.cmx lib/main.ml


stackv4 =A0 =A0 =A0# /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg =
-package cmdliner -package dynlink -package ipaddr -package lwt -package mi=
rage-types -package mirage-types.lwt -package unix lib/mirage.cmxa lib/main=
.cmx -o lib/main.native


stackv4 =A0 =A0 =A0# ./setup.bin -test

stackv4 =A0 =A0 =A0# ./setup.bin -doc

stackv4 =A0 =A0 =A0# make[1]: Leaving directory `/root/.opam/system/build/m=
irage.1.1.0'

stackv4 =A0 =A0 =A0# make[1]: Entering directory `/root/.opam/system/build/=
mirage.1.1.0'

stackv4 =A0 =A0 =A0# ./setup.bin -install

stackv4 =A0 =A0 =A0# make[1]: Leaving directory `/root/.opam/system/build/m=
irage.1.1.0'

stackv4 =A0 =A0 =A0### stderr ###

stackv4 =A0 =A0 =A0# ...[truncated]

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage.a

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage.cmxs
stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage_misc.cm=
i

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage.cmi

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage_misc.cm=
x

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage.cmx

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/META

stackv4 =A0 =A0 =A0# cp: cannot create regular file `/root/.opam/system/bin=
/mirage': Text file busy

stackv4 =A0 =A0 =A0# E: Failure("Command ''cp' '/root/=
.opam/system/build/mirage.1.1.0/_build/lib/main.native' '/root/.opa=
m/system/bin/mirage'' terminated with error code 1")

stackv4 =A0 =A0 =A0# make[1]: *** [install] Error 1

stackv4

stackv4

stackv4 =A0 =A0 =A0The former state can be restored with opam switch import=
 -f "/root/.opam/system/backup/state-20140112143516.export"

stackv4 =A0 =A0 =A0'opam install --yes mirage-clock-unix mirage-console=
-unix mirage-http mirage-net-unix mirage-unix tcpip' failed.

stackv4 =A0 =A0 =A0tar.gz

stackv4 =A0 =A0 =A0Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.=
tar.gz

stackv4 =A0 =A0 =A0Building uri.1.3.13:

stackv4 =A0 =A0 =A0 =A0ocaml =
setup.ml -configure --prefix /root/.opam/system

stackv4 =A0 =A0 =A0 =A0ocaml =
setup.ml -build

stackv4 =A0 =A0 =A0 =A0ocaml =
setup.ml -install

stackv4 =A0 =A0 =A0Installing uri.1.3.13.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing cohttp.0.9.16 =3D-=3D-=3D

stackv4 =A0 =A0 =A0default =A0 =A0Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+op=
am.tar.gz

stackv4 =A0 =A0 =A0Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+op=
am.tar.gz

stackv4 =A0 =A0 =A0Building cohttp.0.9.16:

stackv4 =A0 =A0 =A0 =A0make PREFIX=3D/root/.opam/system

stackv4 =A0 =A0 =A0 =A0make PREFIX=3D/root/.opam/system install

stackv4 =A0 =A0 =A0Installing cohttp.0.9.16.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing io-page.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0Building io-page.1.1.0:

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing io-page.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing shared-memory-ring.1.0.0 =3D-=3D-=
=3D

stackv4 =A0 =A0 =A0Building shared-memory-ring.1.0.0:

stackv4 =A0 =A0 =A0 =A0make all

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing shared-memory-ring.1.0.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-types.1.1.0 =3D-=3D-=3D
stackv4 =A0 =A0 =A0Building mirage-types.1.1.0:

stackv4 =A0 =A0 =A0 =A0make install-types

stackv4 =A0 =A0 =A0Installing mirage-types.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0Building mirage.1.1.0:

stackv4 =A0 =A0 =A0 =A0./configure --bindir /root/.opam/system/bin

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Removing mirage.1.1.0.

stackv4 =A0 =A0 =A0 =A0./configure --bindir /root/.opam/system/bin

stackv4 =A0 =A0 =A0 =A0make uninstall

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-clock-unix.1.0.0 =3D-=3D-=
=3D

stackv4 =A0 =A0 =A0Building mirage-clock-unix.1.0.0:

stackv4 =A0 =A0 =A0 =A0make unix-build

stackv4 =A0 =A0 =A0 =A0make unix-install

stackv4 =A0 =A0 =A0Installing mirage-clock-unix.1.0.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-net-unix.1.1.0 =3D-=3D-=3D=


stackv4 =A0 =A0 =A0Building mirage-net-unix.1.1.0:

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing mirage-net-unix.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-unix.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0Building mirage-unix.1.1.0:

stackv4 =A0 =A0 =A0 =A0make unix-build

stackv4 =A0 =A0 =A0 =A0make unix-install PREFIX=3D/root/.opam/system

stackv4 =A0 =A0 =A0Installing mirage-unix.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-console-unix.1.0.0 =3D-=3D=
-=3D

stackv4 =A0 =A0 =A0Building mirage-console-unix.1.0.0:

stackv4 =A0 =A0 =A0 =A0make unix-build

stackv4 =A0 =A0 =A0 =A0make unix-install

stackv4 =A0 =A0 =A0Installing mirage-console-unix.1.0.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0Building tcpip.1.1.0:

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing tcpip.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-http.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0default =A0 =A0Downloading https://opam.ocaml.org/archives/mirage-http.1.1.=
0+opam.tar.gz

stackv4 =A0 =A0 =A0Downloading https://opam.ocaml.org/archives/mirage-http.1.1.=
0+opam.tar.gz

stackv4 =A0 =A0 =A0Building mirage-http.1.1.0:

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing mirage-http.1.1.0.

stackv4

[ERROR] =A0 =A0 =A0The command "opam install --yes mirage-clock-unix m=
irage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exit=
ed with code 4.

make: *** [stackv4-configure] Error 1

_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists=
.xenproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo=
/mirageos-devel





-- 
Dave Scott



--047d7b15a693e52f4204f236b7f8--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============1816144151470481823==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 14:52:21 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 14:52: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 1WDbAj-00038S-BG; Wed, 12 Feb 2014 14:52:21 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDbAh-000380-5D
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 14:52:19 +0000
Received: from [85.158.137.68:45846] by server-15.bemta-3.messagelabs.com id
	DB/8B-19263-2AA8BF25; Wed, 12 Feb 2014 14:52:18 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-12.tower-31.messagelabs.com!1392216734!387948!1
X-Originating-IP: [209.85.192.178]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6954 invoked from network); 12 Feb 2014 14:52:16 -0000
Received: from mail-pd0-f178.google.com (HELO mail-pd0-f178.google.com)
	(209.85.192.178)
	by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 14:52:16 -0000
Received: by mail-pd0-f178.google.com with SMTP id fp1so415331pdb.9
	for ;
	Wed, 12 Feb 2014 06:52:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=Szw47c1oSzfZ6ZCtqj3U/tgTzRelsOdjaXa9SWnvPs0=;
	b=hQMcg2TKzHsW1N+53bAZALy2VxLFtuibBlKU5/TYTczTDR/mwDSSJT57EFdeTB0/xE
	yktNAbE/kraHHUr4HwY+SsfNrXKChenIEJhIG0+zz93SXruCkmPTieTRC2ZSK/N+bDqW
	ez5Kph1/eHG52u/+x3PmJsgGBkrVrCwFZBQvocPAZxAuZG8pogbV/VrE3bv3PKmubzCp
	Cx9RqMfDEeTrBdaFaOCAWMBHBX/twQKy092VgS07tT934cLJscegJfI8x53ICB4e0ZE5
	vpkokLd7MIxw1NiwTHYoHii3TMwMh6zAz0P1rx4uf92AFYgmu3aVgJb9NH9DrvxNN05c
	4qlg==
MIME-Version: 1.0
X-Received: by 10.68.202.8 with SMTP id ke8mr52056952pbc.86.1392216734247;
	Wed, 12 Feb 2014 06:52:14 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Wed, 12 Feb 2014 06:52:14 -0800 (PST)
In-Reply-To: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
Date: Wed, 12 Feb 2014 14:52:14 +0000
Message-ID: 
From: David Scott 
To: Julian Chesterfield 
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1816144151470481823=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============1816144151470481823==
Content-Type: multipart/alternative; boundary=047d7b15a693e52f4204f236b7f8

--047d7b15a693e52f4204f236b7f8
Content-Type: text/plain; charset=ISO-8859-1

Hi,

The problem is triggered by the "mirage" command-line tool attempting to
replace its own binary:

> stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage':
Text file busy

As a workaround, try running "opam upgrade mirage" and then try "make all"
again -- by pre-upgrading mirage you should bypass the problem.

I had a quick scan through the mirage/mirage issues list on github and
couldn't spot this one. It's probably worth filing this as a bug so we
don't forget. Perhaps we could fix it by changing mirage/mirage opam
install to "mv mirage mirage.bak; cp newmirage mirage".

Cheers,
Dave


On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield <
julian.chesterfield@onapp.com> wrote:

> Hi there! Any pointers on the following error I'm getting when trying to
> build mirage-skeleton on a fresh build server? Ubuntu precise, 12.04.1 LTS.
>
> Thanks!
> Julian
>
> root@Build-server:~/mirage-skeleton# opam list
> Installed packages for system:
> base-bigarray             base  Bigarray library distributed with the
> OCaml compiler
> base-threads              base  Threads library distributed with the OCaml
> compiler
> base-unix                 base  Unix library distributed with the OCaml
> compiler
> cmdliner                 0.9.4  Declarative definition of command line
> interfaces for OCaml
> cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage
> cstruct                  1.0.1  access C structures via a camlp4 extension
> fieldslib            109.20.03  Syntax extension to define first class
> values representing record fields, to get and set record fields, iterate
> and fold over all fields of a record and create new record v
> io-page                  1.1.0  Allocate memory pages suitable for aligned
> I/O
> ipaddr                   2.4.0  IP (and MAC) address representation library
> lwt                      2.4.4  A cooperative threads library for OCaml
> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for Unix
> mirage-console-unix      1.0.0  A Mirage-compatible Console library for
> Unix
> mirage-http              1.1.0  Mirage HTTP client and server driver for
> Unix
> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, using
> tuntap
> mirage-types             1.1.0  Module type definitions for
> Mirage-compatible applications
> mirage-unix              1.1.0  Mirage OS library for Unix compilation
> ocamlfind                1.4.0  A library manager for OCaml
> ocplib-endian              0.4  Optimised functions to read and write
> int16/32/64 from strings and bigarrays, based on new primitives added in
> version 4.01.
> optcomp                    1.5  Optional compilation with cpp-like
> directives
> ounit                    2.0.0  Unit testing framework loosely based on
> HUnit. It is similar to JUnit, and other XUnit testing frameworks
> re                       1.2.1  RE is a regular expression library for
> OCaml
> sexplib              110.01.00  Library for serializing OCaml values to
> and from S-expressions
> shared-memory-ring       1.0.0  Shared memory rings for RPC and bytestream
> communications.
> ssl                      0.4.6  Bindings for the libssl
> tcpip                    1.1.0  Userlevel TCP/IP stack
> tuntap                   0.7.0  TUN/TAP bindings
> type_conv            109.60.01  Library for building type-driven syntax
> extensions
> uri                     1.3.13  RFC3986 URI parsing library
>
>
> root@Build-server:~/mirage-skeleton# make all
>
> .......<--All fine until
>
> stackv4     + Executing: opam install --yes mirage-clock-unix
> mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
> stackv4      The following actions will be performed:
> stackv4       - install type_conv.109.60.01 [required by mirage-http]
> stackv4       - install ssl.0.4.6 [required by mirage-http]
> stackv4       - install fieldslib.109.20.03 [required by mirage-http]
> stackv4       - install sexplib.110.01.00 [required by mirage-http]
> stackv4       - recompile lwt.2.4.4 [use ssl]
> stackv4       - install uri.1.3.13 [required by mirage-http]
> stackv4       - recompile cstruct.1.0.1 [use ssl]
> stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0
> failed.
> stackv4
> stackv4      ===== ERROR while recompiling mirage.1.1.0 =====
> stackv4      # opam-version         1.1.1
> stackv4      # os                   linux
> stackv4      # command              make install
> stackv4      # path                 /root/.opam/system/build/mirage.1.1.0
> stackv4      # compiler             system (4.01.0)
> stackv4      # exit-code            2
> stackv4      # env-file
> /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
> stackv4      # stdout-file
>  /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
> stackv4      # stderr-file
>  /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
> stackv4      ### stdout ###
> stackv4      # ...[truncated]
> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package cmdliner
> -package dynlink -package ipaddr -package lwt -package mirage-types
> -package mirage-types.lwt -package unix -modules lib/main.ml >
> lib/main.ml.depends
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot
> -bin-annot -principal -I lib -package cmdliner -package dynlink -package
> ipaddr -package lwt -package mirage-types -package mirage-types.lwt
> -package unix -I lib -o lib/main.cmo lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot
> -bin-annot -principal -I lib -package cmdliner -package dynlink -package
> ipaddr -package lwt -package mirage-types -package mirage-types.lwt
> -package unix -I lib -o lib/main.cmx lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg
> -package cmdliner -package dynlink -package ipaddr -package lwt -package
> mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa
> lib/main.cmx -o lib/main.native
> stackv4      # ./setup.bin -test
> stackv4      # ./setup.bin -doc
> stackv4      # make[1]: Leaving directory
> `/root/.opam/system/build/mirage.1.1.0'
> stackv4      # make[1]: Entering directory
> `/root/.opam/system/build/mirage.1.1.0'
> stackv4      # ./setup.bin -install
> stackv4      # make[1]: Leaving directory
> `/root/.opam/system/build/mirage.1.1.0'
> stackv4      ### stderr ###
> stackv4      # ...[truncated]
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/META
> stackv4      # cp: cannot create regular file
> `/root/.opam/system/bin/mirage': Text file busy
> stackv4      # E: Failure("Command ''cp'
> '/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native'
> '/root/.opam/system/bin/mirage'' terminated with error code 1")
> stackv4      # make[1]: *** [install] Error 1
> stackv4
> stackv4
> stackv4      The former state can be restored with opam switch import -f
> "/root/.opam/system/backup/state-20140112143516.export"
> stackv4      'opam install --yes mirage-clock-unix mirage-console-unix
> mirage-http mirage-net-unix mirage-unix tcpip' failed.
> stackv4      tar.gz
> stackv4      Downloading
> https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
> stackv4      Building uri.1.3.13:
> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
> stackv4        ocaml setup.ml -build
> stackv4        ocaml setup.ml -install
> stackv4      Installing uri.1.3.13.
> stackv4
> stackv4      =-=-= Installing cohttp.0.9.16 =-=-=
> stackv4      default    Downloading
> https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Downloading
> https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Building cohttp.0.9.16:
> stackv4        make PREFIX=/root/.opam/system
> stackv4        make PREFIX=/root/.opam/system install
> stackv4      Installing cohttp.0.9.16.
> stackv4
> stackv4      =-=-= Installing io-page.1.1.0 =-=-=
> stackv4      Building io-page.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing io-page.1.1.0.
> stackv4
> stackv4      =-=-= Installing shared-memory-ring.1.0.0 =-=-=
> stackv4      Building shared-memory-ring.1.0.0:
> stackv4        make all
> stackv4        make install
> stackv4      Installing shared-memory-ring.1.0.0.
> stackv4
> stackv4      =-=-= Installing mirage-types.1.1.0 =-=-=
> stackv4      Building mirage-types.1.1.0:
> stackv4        make install-types
> stackv4      Installing mirage-types.1.1.0.
> stackv4
> stackv4      =-=-= Installing mirage.1.1.0 =-=-=
> stackv4      Building mirage.1.1.0:
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make
> stackv4        make install
> stackv4      Removing mirage.1.1.0.
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make uninstall
> stackv4
> stackv4      =-=-= Installing mirage-clock-unix.1.0.0 =-=-=
> stackv4      Building mirage-clock-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-clock-unix.1.0.0.
> stackv4
> stackv4      =-=-= Installing mirage-net-unix.1.1.0 =-=-=
> stackv4      Building mirage-net-unix.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-net-unix.1.1.0.
> stackv4
> stackv4      =-=-= Installing mirage-unix.1.1.0 =-=-=
> stackv4      Building mirage-unix.1.1.0:
> stackv4        make unix-build
> stackv4        make unix-install PREFIX=/root/.opam/system
> stackv4      Installing mirage-unix.1.1.0.
> stackv4
> stackv4      =-=-= Installing mirage-console-unix.1.0.0 =-=-=
> stackv4      Building mirage-console-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-console-unix.1.0.0.
> stackv4
> stackv4      =-=-= Installing tcpip.1.1.0 =-=-=
> stackv4      Building tcpip.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing tcpip.1.1.0.
> stackv4
> stackv4      =-=-= Installing mirage-http.1.1.0 =-=-=
> stackv4      default    Downloading
> https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Downloading
> https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Building mirage-http.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-http.1.1.0.
> stackv4
> [ERROR]      The command "opam install --yes mirage-clock-unix
> mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exited
> with code 4.
> make: *** [stackv4-configure] Error 1
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>



-- 
Dave Scott

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


Hi,

The problem is triggered by the &qu=
ot;mirage" command-line tool attempting to replace its own binary:

> stackv4 =A0 =A0 =A0# cp: cannot create regular file `/root/.opa=
m/system/bin/mirage': Text file busy



=

As a workaround, try running "opam upgrade mirage" and then tr=
y "make all" again -- by pre-upgrading mirage you should bypass t=
he problem.



I h=
ad a quick scan through the mirage/mirage issues list on github and couldn&=
#39;t spot this one. It's probably worth filing this as a bug so we don=
't forget. Perhaps we could fix it by changing mirage/mirage opam insta=
ll to "mv mirage mirage.bak; cp newmirage mirage".



Che=
ers,
Dave




On Wed,=
 Feb 12, 2014 at 2:46 PM, Julian Chesterfield <julian.chesterf=
ield@onapp.com> wrote:


Hi there! Any pointers on the following erro=
r I'm getting when trying to build mirage-skeleton on a fresh build ser=
ver? Ubuntu precise, 12.04.1 LTS.




Thanks!

Julian



root@Build-server:~/mirage-skeleton# opam list

Installed packages for system:

base-bigarray =A0 =A0 =A0 =A0 =A0 =A0 base =A0Bigarray library distributed =
with the OCaml compiler

base-threads =A0 =A0 =A0 =A0 =A0 =A0 =A0base =A0Threads library distributed=
 with the OCaml compiler

base-unix =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 base =A0Unix library distributed =
with the OCaml compiler

cmdliner =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0.9.4 =A0Declarative definition of=
 command line interfaces for OCaml

cohttp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00.9.16 =A0HTTP library for Lwt, A=
sync and Mirage

cstruct =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.0.1 =A0access C structures via=
 a camlp4 extension

fieldslib =A0 =A0 =A0 =A0 =A0 =A0109.20.03 =A0Syntax extension to define fi=
rst class values representing record fields, to get and set record fields, =
iterate and fold over all fields of a record and create new record v

io-page =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.1.0 =A0Allocate memory pages s=
uitable for aligned I/O

ipaddr =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2.4.0 =A0IP (and MAC) address re=
presentation library

lwt =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02.4.4 =A0A cooperative threa=
ds library for OCaml

mirage-clock-unix =A0 =A0 =A0 =A01.0.0 =A0A Mirage-compatible Clock library=
 for Unix

mirage-console-unix =A0 =A0 =A01.0.0 =A0A Mirage-compatible Console library=
 for Unix

mirage-http =A0 =A0 =A0 =A0 =A0 =A0 =A01.1.0 =A0Mirage HTTP client and serv=
er driver for Unix

mirage-net-unix =A0 =A0 =A0 =A0 =A01.1.0 =A0Ethernet network driver for Mir=
age, using tuntap

mirage-types =A0 =A0 =A0 =A0 =A0 =A0 1.1.0 =A0Module type definitions for M=
irage-compatible applications

mirage-unix =A0 =A0 =A0 =A0 =A0 =A0 =A01.1.0 =A0Mirage OS library for Unix =
compilation

ocamlfind =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.4.0 =A0A library manager for OCa=
ml

ocplib-endian =A0 =A0 =A0 =A0 =A0 =A0 =A00.4 =A0Optimised functions to read=
 and write int16/32/64 from strings and bigarrays, based on new primitives =
added in version 4.01.

optcomp =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.5 =A0Optional compilation =
with cpp-like directives

ounit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A02.0.0 =A0Unit testing framewor=
k loosely based on HUnit. It is similar to JUnit, and other XUnit testing f=
rameworks

re =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1.2.1 =A0RE is a regular exp=
ression library for OCaml

sexplib =A0 =A0 =A0 =A0 =A0 =A0 =A0110.01.00 =A0Library for serializing OCa=
ml values to and from S-expressions

shared-memory-ring =A0 =A0 =A0 1.0.0 =A0Shared memory rings for RPC and byt=
estream communications.

ssl =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00.4.6 =A0Bindings for the li=
bssl

tcpip =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01.1.0 =A0Userlevel TCP/IP stac=
k

tuntap =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 0.7.0 =A0TUN/TAP bindings

type_conv =A0 =A0 =A0 =A0 =A0 =A0109.60.01 =A0Library for building type-dri=
ven syntax extensions

uri =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1.3.13 =A0RFC3986 URI parsing l=
ibrary





root@Build-server:~/mirage-skeleton# make all



.......<--All fine until



stackv4 =A0 =A0 + Executing: opam install --yes mirage-clock-unix mirage-co=
nsole-unix mirage-http mirage-net-unix mirage-unix tcpip

stackv4 =A0 =A0 =A0The following actions will be performed:

stackv4 =A0 =A0 =A0 - install type_conv.109.60.01 [required by mirage-http]=


stackv4 =A0 =A0 =A0 - install ssl.0.4.6 [required by mirage-http]

stackv4 =A0 =A0 =A0 - install fieldslib.109.20.03 [required by mirage-http]=


stackv4 =A0 =A0 =A0 - install sexplib.110.01.00 [required by mirage-http]
stackv4 =A0 =A0 =A0 - recompile lwt.2.4.4 [use ssl]

stackv4 =A0 =A0 =A0 - install uri.1.3.13 [required by mirage-http]

stackv4 =A0 =A0 =A0 - recompile cstruct.1.0.1 [use ssl]

stackv4 =A0 =A0 =A0 - install cohttp[ERROR] The compilation of mirage.1.1.0=
 failed.

stackv4

stackv4 =A0 =A0 =A0=3D=3D=3D=3D=3D ERROR while recompiling mirage.1.1.0 =3D=
=3D=3D=3D=3D

stackv4 =A0 =A0 =A0# opam-version =A0 =A0 =A0 =A0 1.1.1

stackv4 =A0 =A0 =A0# os =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 linux

stackv4 =A0 =A0 =A0# command =A0 =A0 =A0 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0# path =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /root/.opam/syste=
m/build/mirage.1.1.0

stackv4 =A0 =A0 =A0# compiler =A0 =A0 =A0 =A0 =A0 =A0 system (4.01.0)

stackv4 =A0 =A0 =A0# exit-code =A0 =A0 =A0 =A0 =A0 =A02

stackv4 =A0 =A0 =A0# env-file =A0 =A0 =A0 =A0 =A0 =A0 /root/.opam/system/bu=
ild/mirage.1.1.0/mirage-17018-e0ba4f.env

stackv4 =A0 =A0 =A0# stdout-file =A0 =A0 =A0 =A0 =A0/root/.opam/system/buil=
d/mirage.1.1.0/mirage-17018-e0ba4f.out

stackv4 =A0 =A0 =A0# stderr-file =A0 =A0 =A0 =A0 =A0/root/.opam/system/buil=
d/mirage.1.1.0/mirage-17018-e0ba4f.err

stackv4 =A0 =A0 =A0### stdout ###

stackv4 =A0 =A0 =A0# ...[truncated]

stackv4 =A0 =A0 =A0# /root/.opam/system/bin/ocamlfind ocamldep -package cmd=
liner -package dynlink -package ipaddr -package lwt -package mirage-types -=
package mirage-types.lwt -package unix -modules lib/main.ml > lib/main.ml.depends


stackv4 =A0 =A0 =A0# /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot -=
bin-annot -principal -I lib -package cmdliner -package dynlink -package ipa=
ddr -package lwt -package mirage-types -package mirage-types.lwt -package u=
nix -I lib -o lib/main.cmo lib/main.ml


stackv4 =A0 =A0 =A0# /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot=
 -bin-annot -principal -I lib -package cmdliner -package dynlink -package i=
paddr -package lwt -package mirage-types -package mirage-types.lwt -package=
 unix -I lib -o lib/main.cmx lib/main.ml


stackv4 =A0 =A0 =A0# /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg =
-package cmdliner -package dynlink -package ipaddr -package lwt -package mi=
rage-types -package mirage-types.lwt -package unix lib/mirage.cmxa lib/main=
.cmx -o lib/main.native


stackv4 =A0 =A0 =A0# ./setup.bin -test

stackv4 =A0 =A0 =A0# ./setup.bin -doc

stackv4 =A0 =A0 =A0# make[1]: Leaving directory `/root/.opam/system/build/m=
irage.1.1.0'

stackv4 =A0 =A0 =A0# make[1]: Entering directory `/root/.opam/system/build/=
mirage.1.1.0'

stackv4 =A0 =A0 =A0# ./setup.bin -install

stackv4 =A0 =A0 =A0# make[1]: Leaving directory `/root/.opam/system/build/m=
irage.1.1.0'

stackv4 =A0 =A0 =A0### stderr ###

stackv4 =A0 =A0 =A0# ...[truncated]

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage.a

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage.cmxs
stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage_misc.cm=
i

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage.cmi

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage_misc.cm=
x

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/mirage.cmx

stackv4 =A0 =A0 =A0# Installed /root/.opam/system/lib/mirage/META

stackv4 =A0 =A0 =A0# cp: cannot create regular file `/root/.opam/system/bin=
/mirage': Text file busy

stackv4 =A0 =A0 =A0# E: Failure("Command ''cp' '/root/=
.opam/system/build/mirage.1.1.0/_build/lib/main.native' '/root/.opa=
m/system/bin/mirage'' terminated with error code 1")

stackv4 =A0 =A0 =A0# make[1]: *** [install] Error 1

stackv4

stackv4

stackv4 =A0 =A0 =A0The former state can be restored with opam switch import=
 -f "/root/.opam/system/backup/state-20140112143516.export"

stackv4 =A0 =A0 =A0'opam install --yes mirage-clock-unix mirage-console=
-unix mirage-http mirage-net-unix mirage-unix tcpip' failed.

stackv4 =A0 =A0 =A0tar.gz

stackv4 =A0 =A0 =A0Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.=
tar.gz

stackv4 =A0 =A0 =A0Building uri.1.3.13:

stackv4 =A0 =A0 =A0 =A0ocaml =
setup.ml -configure --prefix /root/.opam/system

stackv4 =A0 =A0 =A0 =A0ocaml =
setup.ml -build

stackv4 =A0 =A0 =A0 =A0ocaml =
setup.ml -install

stackv4 =A0 =A0 =A0Installing uri.1.3.13.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing cohttp.0.9.16 =3D-=3D-=3D

stackv4 =A0 =A0 =A0default =A0 =A0Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+op=
am.tar.gz

stackv4 =A0 =A0 =A0Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+op=
am.tar.gz

stackv4 =A0 =A0 =A0Building cohttp.0.9.16:

stackv4 =A0 =A0 =A0 =A0make PREFIX=3D/root/.opam/system

stackv4 =A0 =A0 =A0 =A0make PREFIX=3D/root/.opam/system install

stackv4 =A0 =A0 =A0Installing cohttp.0.9.16.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing io-page.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0Building io-page.1.1.0:

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing io-page.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing shared-memory-ring.1.0.0 =3D-=3D-=
=3D

stackv4 =A0 =A0 =A0Building shared-memory-ring.1.0.0:

stackv4 =A0 =A0 =A0 =A0make all

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing shared-memory-ring.1.0.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-types.1.1.0 =3D-=3D-=3D
stackv4 =A0 =A0 =A0Building mirage-types.1.1.0:

stackv4 =A0 =A0 =A0 =A0make install-types

stackv4 =A0 =A0 =A0Installing mirage-types.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0Building mirage.1.1.0:

stackv4 =A0 =A0 =A0 =A0./configure --bindir /root/.opam/system/bin

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Removing mirage.1.1.0.

stackv4 =A0 =A0 =A0 =A0./configure --bindir /root/.opam/system/bin

stackv4 =A0 =A0 =A0 =A0make uninstall

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-clock-unix.1.0.0 =3D-=3D-=
=3D

stackv4 =A0 =A0 =A0Building mirage-clock-unix.1.0.0:

stackv4 =A0 =A0 =A0 =A0make unix-build

stackv4 =A0 =A0 =A0 =A0make unix-install

stackv4 =A0 =A0 =A0Installing mirage-clock-unix.1.0.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-net-unix.1.1.0 =3D-=3D-=3D=


stackv4 =A0 =A0 =A0Building mirage-net-unix.1.1.0:

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing mirage-net-unix.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-unix.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0Building mirage-unix.1.1.0:

stackv4 =A0 =A0 =A0 =A0make unix-build

stackv4 =A0 =A0 =A0 =A0make unix-install PREFIX=3D/root/.opam/system

stackv4 =A0 =A0 =A0Installing mirage-unix.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-console-unix.1.0.0 =3D-=3D=
-=3D

stackv4 =A0 =A0 =A0Building mirage-console-unix.1.0.0:

stackv4 =A0 =A0 =A0 =A0make unix-build

stackv4 =A0 =A0 =A0 =A0make unix-install

stackv4 =A0 =A0 =A0Installing mirage-console-unix.1.0.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0Building tcpip.1.1.0:

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing tcpip.1.1.0.

stackv4

stackv4 =A0 =A0 =A0=3D-=3D-=3D Installing mirage-http.1.1.0 =3D-=3D-=3D

stackv4 =A0 =A0 =A0default =A0 =A0Downloading https://opam.ocaml.org/archives/mirage-http.1.1.=
0+opam.tar.gz

stackv4 =A0 =A0 =A0Downloading https://opam.ocaml.org/archives/mirage-http.1.1.=
0+opam.tar.gz

stackv4 =A0 =A0 =A0Building mirage-http.1.1.0:

stackv4 =A0 =A0 =A0 =A0make

stackv4 =A0 =A0 =A0 =A0make install

stackv4 =A0 =A0 =A0Installing mirage-http.1.1.0.

stackv4

[ERROR] =A0 =A0 =A0The command "opam install --yes mirage-clock-unix m=
irage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exit=
ed with code 4.

make: *** [stackv4-configure] Error 1

_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists=
.xenproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo=
/mirageos-devel





-- 
Dave Scott



--047d7b15a693e52f4204f236b7f8--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============1816144151470481823==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 15:37:24 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 15:37: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 1WDbsI-0005LK-NF; Wed, 12 Feb 2014 15:37:22 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDbsH-0005LA-3z
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 15:37:21 +0000
Received: from [85.158.139.211:28612] by server-15.bemta-5.messagelabs.com id
	E8/25-24395-0359BF25; Wed, 12 Feb 2014 15:37:20 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-3.tower-206.messagelabs.com!1392219438!3465164!1
X-Originating-IP: [74.125.82.172]
X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_23,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31851 invoked from network); 12 Feb 2014 15:37:18 -0000
Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com)
	(74.125.82.172)
	by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 15:37:18 -0000
Received: by mail-we0-f172.google.com with SMTP id p61so6193743wes.3
	for ;
	Wed, 12 Feb 2014 07:37:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:mime-version:content-type:from
	:in-reply-to:date:cc:message-id:references:to;
	bh=8QxcztRgcQS6Fht+WZszrWovBqXk7NJgvKs/sihFLH0=;
	b=b+I1ppmzJoUHAJy2M8AwHFFtbYT9IeEykYckGzqs9KEWTc5bJPXYahANgpjs6LtKR5
	3Oa2kU4922xcNayNrTnOvVSUkNI7o6Fj4oNECpQykRmsoNBqrphfdsO5TiCcuWiTh8CN
	4V+RVMMZGvYii8ruu/xwoGoaWrR1pb3vbcthmDnpoEfXLX26Fsi+sXuI5IKRhmwRKOfH
	x14kjcQjUBPXwgeEck9G+Ye+5peOLcl9KmqkAoHH4gfdw+6yIF6AO14yJfZ7UbiffGWS
	7gtv7lscB+xUYGj7q8/rF5IFDCv/WmWl24Y5DWjx/fKZH0N7+1kgHWNOCc4uzzIZ0lt/
	1JNw==
X-Gm-Message-State: ALoCoQkvumTSHqPEVQ48TopKPm0HN3mVfuYSye24ZxjJDyreePaDKXSR5mqqUGQpVFY3RHN2XxPA
X-Received: by 10.194.178.135 with SMTP id cy7mr1797839wjc.21.1392219438135;
	Wed, 12 Feb 2014 07:37:18 -0800 (PST)
Received: from [192.168.1.15] (212.44.45.208.ip.redstone-isp.net.
	[212.44.45.208])
	by mx.google.com with ESMTPSA id di9sm6613661wid.6.2014.02.12.07.37.15
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 12 Feb 2014 07:37:16 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
From: Julian Chesterfield 
In-Reply-To: 
Date: Wed, 12 Feb 2014 15:37:15 +0000
Message-Id: <32FF5EFD-2A33-4B09-8623-46965B1AF081@onapp.com>
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
	
To: David Scott 
X-Mailer: Apple Mail (2.1283)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4975618164352763796=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============4975618164352763796==
Content-Type: multipart/alternative; boundary="Apple-Mail=_01423CCF-7129-4FE7-B29F-722981EBDE11"


--Apple-Mail=_01423CCF-7129-4FE7-B29F-722981EBDE11
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Thanks for the swift replies :-) Running 'opam install mirage' before =
'make' did the trick.

- J

On 12 Feb 2014, at 14:52, David Scott wrote:

> Hi,
>=20
> The problem is triggered by the "mirage" command-line tool attempting =
to replace its own binary:
>=20
> > stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>=20
> As a workaround, try running "opam upgrade mirage" and then try "make =
all" again -- by pre-upgrading mirage you should bypass the problem.
>=20
> I had a quick scan through the mirage/mirage issues list on github and =
couldn't spot this one. It's probably worth filing this as a bug so we =
don't forget. Perhaps we could fix it by changing mirage/mirage opam =
install to "mv mirage mirage.bak; cp newmirage mirage".
>=20
> Cheers,
> Dave
>=20
>=20
> On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield =
 wrote:
> Hi there! Any pointers on the following error I'm getting when trying =
to build mirage-skeleton on a fresh build server? Ubuntu precise, =
12.04.1 LTS.
>=20
> Thanks!
> Julian
>=20
> root@Build-server:~/mirage-skeleton# opam list
> Installed packages for system:
> base-bigarray             base  Bigarray library distributed with the =
OCaml compiler
> base-threads              base  Threads library distributed with the =
OCaml compiler
> base-unix                 base  Unix library distributed with the =
OCaml compiler
> cmdliner                 0.9.4  Declarative definition of command line =
interfaces for OCaml
> cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage
> cstruct                  1.0.1  access C structures via a camlp4 =
extension
> fieldslib            109.20.03  Syntax extension to define first class =
values representing record fields, to get and set record fields, iterate =
and fold over all fields of a record and create new record v
> io-page                  1.1.0  Allocate memory pages suitable for =
aligned I/O
> ipaddr                   2.4.0  IP (and MAC) address representation =
library
> lwt                      2.4.4  A cooperative threads library for =
OCaml
> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for =
Unix
> mirage-console-unix      1.0.0  A Mirage-compatible Console library =
for Unix
> mirage-http              1.1.0  Mirage HTTP client and server driver =
for Unix
> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, =
using tuntap
> mirage-types             1.1.0  Module type definitions for =
Mirage-compatible applications
> mirage-unix              1.1.0  Mirage OS library for Unix compilation
> ocamlfind                1.4.0  A library manager for OCaml
> ocplib-endian              0.4  Optimised functions to read and write =
int16/32/64 from strings and bigarrays, based on new primitives added in =
version 4.01.
> optcomp                    1.5  Optional compilation with cpp-like =
directives
> ounit                    2.0.0  Unit testing framework loosely based =
on HUnit. It is similar to JUnit, and other XUnit testing frameworks
> re                       1.2.1  RE is a regular expression library for =
OCaml
> sexplib              110.01.00  Library for serializing OCaml values =
to and from S-expressions
> shared-memory-ring       1.0.0  Shared memory rings for RPC and =
bytestream communications.
> ssl                      0.4.6  Bindings for the libssl
> tcpip                    1.1.0  Userlevel TCP/IP stack
> tuntap                   0.7.0  TUN/TAP bindings
> type_conv            109.60.01  Library for building type-driven =
syntax extensions
> uri                     1.3.13  RFC3986 URI parsing library
>=20
>=20
> root@Build-server:~/mirage-skeleton# make all
>=20
> .......<--All fine until
>=20
> stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
> stackv4      The following actions will be performed:
> stackv4       - install type_conv.109.60.01 [required by mirage-http]
> stackv4       - install ssl.0.4.6 [required by mirage-http]
> stackv4       - install fieldslib.109.20.03 [required by mirage-http]
> stackv4       - install sexplib.110.01.00 [required by mirage-http]
> stackv4       - recompile lwt.2.4.4 [use ssl]
> stackv4       - install uri.1.3.13 [required by mirage-http]
> stackv4       - recompile cstruct.1.0.1 [use ssl]
> stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 =
failed.
> stackv4
> stackv4      =3D=3D=3D=3D=3D ERROR while recompiling mirage.1.1.0 =
=3D=3D=3D=3D=3D
> stackv4      # opam-version         1.1.1
> stackv4      # os                   linux
> stackv4      # command              make install
> stackv4      # path                 =
/root/.opam/system/build/mirage.1.1.0
> stackv4      # compiler             system (4.01.0)
> stackv4      # exit-code            2
> stackv4      # env-file             =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
> stackv4      # stdout-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
> stackv4      # stderr-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
> stackv4      ### stdout ###
> stackv4      # ...[truncated]
> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package =
cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules =
lib/main.ml > lib/main.ml.depends
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmo lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmx lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa =
lib/main.cmx -o lib/main.native
> stackv4      # ./setup.bin -test
> stackv4      # ./setup.bin -doc
> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
> stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'
> stackv4      # ./setup.bin -install
> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
> stackv4      ### stderr ###
> stackv4      # ...[truncated]
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/META
> stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
> stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")
> stackv4      # make[1]: *** [install] Error 1
> stackv4
> stackv4
> stackv4      The former state can be restored with opam switch import =
-f "/root/.opam/system/backup/state-20140112143516.export"
> stackv4      'opam install --yes mirage-clock-unix mirage-console-unix =
mirage-http mirage-net-unix mirage-unix tcpip' failed.
> stackv4      tar.gz
> stackv4      Downloading =
https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
> stackv4      Building uri.1.3.13:
> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
> stackv4        ocaml setup.ml -build
> stackv4        ocaml setup.ml -install
> stackv4      Installing uri.1.3.13.
> stackv4
> stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =3D-=3D-=3D
> stackv4      default    Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Building cohttp.0.9.16:
> stackv4        make PREFIX=3D/root/.opam/system
> stackv4        make PREFIX=3D/root/.opam/system install
> stackv4      Installing cohttp.0.9.16.
> stackv4
> stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =3D-=3D-=3D
> stackv4      Building io-page.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing io-page.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing shared-memory-ring.1.0.0 =3D-=3D-=3D=

> stackv4      Building shared-memory-ring.1.0.0:
> stackv4        make all
> stackv4        make install
> stackv4      Installing shared-memory-ring.1.0.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =3D-=3D-=3D
> stackv4      Building mirage-types.1.1.0:
> stackv4        make install-types
> stackv4      Installing mirage-types.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =3D-=3D-=3D
> stackv4      Building mirage.1.1.0:
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make
> stackv4        make install
> stackv4      Removing mirage.1.1.0.
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make uninstall
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-clock-unix.1.0.0 =3D-=3D-=3D
> stackv4      Building mirage-clock-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-clock-unix.1.0.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =3D-=3D-=3D
> stackv4      Building mirage-net-unix.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-net-unix.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =3D-=3D-=3D
> stackv4      Building mirage-unix.1.1.0:
> stackv4        make unix-build
> stackv4        make unix-install PREFIX=3D/root/.opam/system
> stackv4      Installing mirage-unix.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-console-unix.1.0.0 =3D-=3D-=3D=

> stackv4      Building mirage-console-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-console-unix.1.0.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D
> stackv4      Building tcpip.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing tcpip.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =3D-=3D-=3D
> stackv4      default    Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Building mirage-http.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-http.1.1.0.
> stackv4
> [ERROR]      The command "opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" =
exited with code 4.
> make: *** [stackv4-configure] Error 1
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>=20
>=20
>=20
> --=20
> Dave Scott


--Apple-Mail=_01423CCF-7129-4FE7-B29F-722981EBDE11
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1


Thanks for the swift replies :-) Running 'opam install mirage' before 'make' did the trick.

- J

On 12 Feb 2014, at 14:52, David Scott wrote:

Hi,

The problem is triggered by the "mirage" command-line tool attempting to replace its own binary:

> stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage': Text file busy



As a workaround, try running "opam upgrade mirage" and then try "make all" again -- by pre-upgrading mirage you should bypass the problem.



I had a quick scan through the mirage/mirage issues list on github and couldn't spot this one. It's probably worth filing this as a bug so we don't forget. Perhaps we could fix it by changing mirage/mirage opam install to "mv mirage mirage.bak; cp newmirage mirage".



Cheers,
Dave




On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield <julian.chesterfield@onapp.com> wrote:


Hi there! Any pointers on the following error I'm getting when trying to build mirage-skeleton on a fresh build server? Ubuntu precise, 12.04.1 LTS.




Thanks!

Julian



root@Build-server:~/mirage-skeleton# opam list

Installed packages for system:

base-bigarray             base  Bigarray library distributed with the OCaml compiler

base-threads              base  Threads library distributed with the OCaml compiler

base-unix                 base  Unix library distributed with the OCaml compiler

cmdliner                 0.9.4  Declarative definition of command line interfaces for OCaml

cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage

cstruct                  1.0.1  access C structures via a camlp4 extension

fieldslib            109.20.03  Syntax extension to define first class values representing record fields, to get and set record fields, iterate and fold over all fields of a record and create new record v

io-page                  1.1.0  Allocate memory pages suitable for aligned I/O

ipaddr                   2.4.0  IP (and MAC) address representation library

lwt                      2.4.4  A cooperative threads library for OCaml

mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for Unix

mirage-console-unix      1.0.0  A Mirage-compatible Console library for Unix

mirage-http              1.1.0  Mirage HTTP client and server driver for Unix

mirage-net-unix          1.1.0  Ethernet network driver for Mirage, using tuntap

mirage-types             1.1.0  Module type definitions for Mirage-compatible applications

mirage-unix              1.1.0  Mirage OS library for Unix compilation

ocamlfind                1.4.0  A library manager for OCaml

ocplib-endian              0.4  Optimised functions to read and write int16/32/64 from strings and bigarrays, based on new primitives added in version 4.01.

optcomp                    1.5  Optional compilation with cpp-like directives

ounit                    2.0.0  Unit testing framework loosely based on HUnit. It is similar to JUnit, and other XUnit testing frameworks

re                       1.2.1  RE is a regular expression library for OCaml

sexplib              110.01.00  Library for serializing OCaml values to and from S-expressions

shared-memory-ring       1.0.0  Shared memory rings for RPC and bytestream communications.

ssl                      0.4.6  Bindings for the libssl

tcpip                    1.1.0  Userlevel TCP/IP stack

tuntap                   0.7.0  TUN/TAP bindings

type_conv            109.60.01  Library for building type-driven syntax extensions

uri                     1.3.13  RFC3986 URI parsing library





root@Build-server:~/mirage-skeleton# make all



.......<--All fine until



stackv4     + Executing: opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip

stackv4      The following actions will be performed:

stackv4       - install type_conv.109.60.01 [required by mirage-http]

stackv4       - install ssl.0.4.6 [required by mirage-http]

stackv4       - install fieldslib.109.20.03 [required by mirage-http]

stackv4       - install sexplib.110.01.00 [required by mirage-http]

stackv4       - recompile lwt.2.4.4 [use ssl]

stackv4       - install uri.1.3.13 [required by mirage-http]

stackv4       - recompile cstruct.1.0.1 [use ssl]

stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 failed.

stackv4

stackv4      ===== ERROR while recompiling mirage.1.1.0 =====

stackv4      # opam-version         1.1.1

stackv4      # os                   linux

stackv4      # command              make install

stackv4      # path                 /root/.opam/system/build/mirage.1.1.0

stackv4      # compiler             system (4.01.0)

stackv4      # exit-code            2

stackv4      # env-file             /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env

stackv4      # stdout-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out

stackv4      # stderr-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err

stackv4      ### stdout ###

stackv4      # ...[truncated]

stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > lib/main.ml.depends


stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa lib/main.cmx -o lib/main.native


stackv4      # ./setup.bin -test

stackv4      # ./setup.bin -doc

stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'

stackv4      # make[1]: Entering directory `/root/.opam/system/build/mirage.1.1.0'

stackv4      # ./setup.bin -install

stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'

stackv4      ### stderr ###

stackv4      # ...[truncated]

stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a

stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs

stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi

stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi

stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx

stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx

stackv4      # Installed /root/.opam/system/lib/mirage/META

stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage': Text file busy

stackv4      # E: Failure("Command ''cp' '/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' '/root/.opam/system/bin/mirage'' terminated with error code 1")

stackv4      # make[1]: *** [install] Error 1

stackv4

stackv4

stackv4      The former state can be restored with opam switch import -f "/root/.opam/system/backup/state-20140112143516.export"

stackv4      'opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' failed.

stackv4      tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz

stackv4      Building uri.1.3.13:

stackv4        ocaml setup.ml -configure --prefix /root/.opam/system

stackv4        ocaml setup.ml -build

stackv4        ocaml setup.ml -install

stackv4      Installing uri.1.3.13.

stackv4

stackv4      =-=-= Installing cohttp.0.9.16 =-=-=

stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz

stackv4      Building cohttp.0.9.16:

stackv4        make PREFIX=/root/.opam/system

stackv4        make PREFIX=/root/.opam/system install

stackv4      Installing cohttp.0.9.16.

stackv4

stackv4      =-=-= Installing io-page.1.1.0 =-=-=

stackv4      Building io-page.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing io-page.1.1.0.

stackv4

stackv4      =-=-= Installing shared-memory-ring.1.0.0 =-=-=

stackv4      Building shared-memory-ring.1.0.0:

stackv4        make all

stackv4        make install

stackv4      Installing shared-memory-ring.1.0.0.

stackv4

stackv4      =-=-= Installing mirage-types.1.1.0 =-=-=

stackv4      Building mirage-types.1.1.0:

stackv4        make install-types

stackv4      Installing mirage-types.1.1.0.

stackv4

stackv4      =-=-= Installing mirage.1.1.0 =-=-=

stackv4      Building mirage.1.1.0:

stackv4        ./configure --bindir /root/.opam/system/bin

stackv4        make

stackv4        make install

stackv4      Removing mirage.1.1.0.

stackv4        ./configure --bindir /root/.opam/system/bin

stackv4        make uninstall

stackv4

stackv4      =-=-= Installing mirage-clock-unix.1.0.0 =-=-=

stackv4      Building mirage-clock-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-clock-unix.1.0.0.

stackv4

stackv4      =-=-= Installing mirage-net-unix.1.1.0 =-=-=

stackv4      Building mirage-net-unix.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-net-unix.1.1.0.

stackv4

stackv4      =-=-= Installing mirage-unix.1.1.0 =-=-=

stackv4      Building mirage-unix.1.1.0:

stackv4        make unix-build

stackv4        make unix-install PREFIX=/root/.opam/system

stackv4      Installing mirage-unix.1.1.0.

stackv4

stackv4      =-=-= Installing mirage-console-unix.1.0.0 =-=-=

stackv4      Building mirage-console-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-console-unix.1.0.0.

stackv4

stackv4      =-=-= Installing tcpip.1.1.0 =-=-=

stackv4      Building tcpip.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing tcpip.1.1.0.

stackv4

stackv4      =-=-= Installing mirage-http.1.1.0 =-=-=

stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz

stackv4      Building mirage-http.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-http.1.1.0.

stackv4

[ERROR]      The command "opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exited with code 4.

make: *** [stackv4-configure] Error 1

_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists.xenproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel





-- 
Dave Scott





--Apple-Mail=_01423CCF-7129-4FE7-B29F-722981EBDE11--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============4975618164352763796==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 15:37:24 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 15:37: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 1WDbsI-0005LK-NF; Wed, 12 Feb 2014 15:37:22 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDbsH-0005LA-3z
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 15:37:21 +0000
Received: from [85.158.139.211:28612] by server-15.bemta-5.messagelabs.com id
	E8/25-24395-0359BF25; Wed, 12 Feb 2014 15:37:20 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-3.tower-206.messagelabs.com!1392219438!3465164!1
X-Originating-IP: [74.125.82.172]
X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,ML_RADAR_SPEW_LINKS_23,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31851 invoked from network); 12 Feb 2014 15:37:18 -0000
Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com)
	(74.125.82.172)
	by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 15:37:18 -0000
Received: by mail-we0-f172.google.com with SMTP id p61so6193743wes.3
	for ;
	Wed, 12 Feb 2014 07:37:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:mime-version:content-type:from
	:in-reply-to:date:cc:message-id:references:to;
	bh=8QxcztRgcQS6Fht+WZszrWovBqXk7NJgvKs/sihFLH0=;
	b=b+I1ppmzJoUHAJy2M8AwHFFtbYT9IeEykYckGzqs9KEWTc5bJPXYahANgpjs6LtKR5
	3Oa2kU4922xcNayNrTnOvVSUkNI7o6Fj4oNECpQykRmsoNBqrphfdsO5TiCcuWiTh8CN
	4V+RVMMZGvYii8ruu/xwoGoaWrR1pb3vbcthmDnpoEfXLX26Fsi+sXuI5IKRhmwRKOfH
	x14kjcQjUBPXwgeEck9G+Ye+5peOLcl9KmqkAoHH4gfdw+6yIF6AO14yJfZ7UbiffGWS
	7gtv7lscB+xUYGj7q8/rF5IFDCv/WmWl24Y5DWjx/fKZH0N7+1kgHWNOCc4uzzIZ0lt/
	1JNw==
X-Gm-Message-State: ALoCoQkvumTSHqPEVQ48TopKPm0HN3mVfuYSye24ZxjJDyreePaDKXSR5mqqUGQpVFY3RHN2XxPA
X-Received: by 10.194.178.135 with SMTP id cy7mr1797839wjc.21.1392219438135;
	Wed, 12 Feb 2014 07:37:18 -0800 (PST)
Received: from [192.168.1.15] (212.44.45.208.ip.redstone-isp.net.
	[212.44.45.208])
	by mx.google.com with ESMTPSA id di9sm6613661wid.6.2014.02.12.07.37.15
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 12 Feb 2014 07:37:16 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
From: Julian Chesterfield 
In-Reply-To: 
Date: Wed, 12 Feb 2014 15:37:15 +0000
Message-Id: <32FF5EFD-2A33-4B09-8623-46965B1AF081@onapp.com>
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
	
To: David Scott 
X-Mailer: Apple Mail (2.1283)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4975618164352763796=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============4975618164352763796==
Content-Type: multipart/alternative; boundary="Apple-Mail=_01423CCF-7129-4FE7-B29F-722981EBDE11"


--Apple-Mail=_01423CCF-7129-4FE7-B29F-722981EBDE11
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Thanks for the swift replies :-) Running 'opam install mirage' before =
'make' did the trick.

- J

On 12 Feb 2014, at 14:52, David Scott wrote:

> Hi,
>=20
> The problem is triggered by the "mirage" command-line tool attempting =
to replace its own binary:
>=20
> > stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>=20
> As a workaround, try running "opam upgrade mirage" and then try "make =
all" again -- by pre-upgrading mirage you should bypass the problem.
>=20
> I had a quick scan through the mirage/mirage issues list on github and =
couldn't spot this one. It's probably worth filing this as a bug so we =
don't forget. Perhaps we could fix it by changing mirage/mirage opam =
install to "mv mirage mirage.bak; cp newmirage mirage".
>=20
> Cheers,
> Dave
>=20
>=20
> On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield =
 wrote:
> Hi there! Any pointers on the following error I'm getting when trying =
to build mirage-skeleton on a fresh build server? Ubuntu precise, =
12.04.1 LTS.
>=20
> Thanks!
> Julian
>=20
> root@Build-server:~/mirage-skeleton# opam list
> Installed packages for system:
> base-bigarray             base  Bigarray library distributed with the =
OCaml compiler
> base-threads              base  Threads library distributed with the =
OCaml compiler
> base-unix                 base  Unix library distributed with the =
OCaml compiler
> cmdliner                 0.9.4  Declarative definition of command line =
interfaces for OCaml
> cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage
> cstruct                  1.0.1  access C structures via a camlp4 =
extension
> fieldslib            109.20.03  Syntax extension to define first class =
values representing record fields, to get and set record fields, iterate =
and fold over all fields of a record and create new record v
> io-page                  1.1.0  Allocate memory pages suitable for =
aligned I/O
> ipaddr                   2.4.0  IP (and MAC) address representation =
library
> lwt                      2.4.4  A cooperative threads library for =
OCaml
> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for =
Unix
> mirage-console-unix      1.0.0  A Mirage-compatible Console library =
for Unix
> mirage-http              1.1.0  Mirage HTTP client and server driver =
for Unix
> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, =
using tuntap
> mirage-types             1.1.0  Module type definitions for =
Mirage-compatible applications
> mirage-unix              1.1.0  Mirage OS library for Unix compilation
> ocamlfind                1.4.0  A library manager for OCaml
> ocplib-endian              0.4  Optimised functions to read and write =
int16/32/64 from strings and bigarrays, based on new primitives added in =
version 4.01.
> optcomp                    1.5  Optional compilation with cpp-like =
directives
> ounit                    2.0.0  Unit testing framework loosely based =
on HUnit. It is similar to JUnit, and other XUnit testing frameworks
> re                       1.2.1  RE is a regular expression library for =
OCaml
> sexplib              110.01.00  Library for serializing OCaml values =
to and from S-expressions
> shared-memory-ring       1.0.0  Shared memory rings for RPC and =
bytestream communications.
> ssl                      0.4.6  Bindings for the libssl
> tcpip                    1.1.0  Userlevel TCP/IP stack
> tuntap                   0.7.0  TUN/TAP bindings
> type_conv            109.60.01  Library for building type-driven =
syntax extensions
> uri                     1.3.13  RFC3986 URI parsing library
>=20
>=20
> root@Build-server:~/mirage-skeleton# make all
>=20
> .......<--All fine until
>=20
> stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
> stackv4      The following actions will be performed:
> stackv4       - install type_conv.109.60.01 [required by mirage-http]
> stackv4       - install ssl.0.4.6 [required by mirage-http]
> stackv4       - install fieldslib.109.20.03 [required by mirage-http]
> stackv4       - install sexplib.110.01.00 [required by mirage-http]
> stackv4       - recompile lwt.2.4.4 [use ssl]
> stackv4       - install uri.1.3.13 [required by mirage-http]
> stackv4       - recompile cstruct.1.0.1 [use ssl]
> stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 =
failed.
> stackv4
> stackv4      =3D=3D=3D=3D=3D ERROR while recompiling mirage.1.1.0 =
=3D=3D=3D=3D=3D
> stackv4      # opam-version         1.1.1
> stackv4      # os                   linux
> stackv4      # command              make install
> stackv4      # path                 =
/root/.opam/system/build/mirage.1.1.0
> stackv4      # compiler             system (4.01.0)
> stackv4      # exit-code            2
> stackv4      # env-file             =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
> stackv4      # stdout-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
> stackv4      # stderr-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
> stackv4      ### stdout ###
> stackv4      # ...[truncated]
> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package =
cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules =
lib/main.ml > lib/main.ml.depends
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmo lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmx lib/main.ml
> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa =
lib/main.cmx -o lib/main.native
> stackv4      # ./setup.bin -test
> stackv4      # ./setup.bin -doc
> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
> stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'
> stackv4      # ./setup.bin -install
> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
> stackv4      ### stderr ###
> stackv4      # ...[truncated]
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
> stackv4      # Installed /root/.opam/system/lib/mirage/META
> stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
> stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")
> stackv4      # make[1]: *** [install] Error 1
> stackv4
> stackv4
> stackv4      The former state can be restored with opam switch import =
-f "/root/.opam/system/backup/state-20140112143516.export"
> stackv4      'opam install --yes mirage-clock-unix mirage-console-unix =
mirage-http mirage-net-unix mirage-unix tcpip' failed.
> stackv4      tar.gz
> stackv4      Downloading =
https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
> stackv4      Building uri.1.3.13:
> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
> stackv4        ocaml setup.ml -build
> stackv4        ocaml setup.ml -install
> stackv4      Installing uri.1.3.13.
> stackv4
> stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =3D-=3D-=3D
> stackv4      default    Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
> stackv4      Building cohttp.0.9.16:
> stackv4        make PREFIX=3D/root/.opam/system
> stackv4        make PREFIX=3D/root/.opam/system install
> stackv4      Installing cohttp.0.9.16.
> stackv4
> stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =3D-=3D-=3D
> stackv4      Building io-page.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing io-page.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing shared-memory-ring.1.0.0 =3D-=3D-=3D=

> stackv4      Building shared-memory-ring.1.0.0:
> stackv4        make all
> stackv4        make install
> stackv4      Installing shared-memory-ring.1.0.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =3D-=3D-=3D
> stackv4      Building mirage-types.1.1.0:
> stackv4        make install-types
> stackv4      Installing mirage-types.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =3D-=3D-=3D
> stackv4      Building mirage.1.1.0:
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make
> stackv4        make install
> stackv4      Removing mirage.1.1.0.
> stackv4        ./configure --bindir /root/.opam/system/bin
> stackv4        make uninstall
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-clock-unix.1.0.0 =3D-=3D-=3D
> stackv4      Building mirage-clock-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-clock-unix.1.0.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =3D-=3D-=3D
> stackv4      Building mirage-net-unix.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-net-unix.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =3D-=3D-=3D
> stackv4      Building mirage-unix.1.1.0:
> stackv4        make unix-build
> stackv4        make unix-install PREFIX=3D/root/.opam/system
> stackv4      Installing mirage-unix.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-console-unix.1.0.0 =3D-=3D-=3D=

> stackv4      Building mirage-console-unix.1.0.0:
> stackv4        make unix-build
> stackv4        make unix-install
> stackv4      Installing mirage-console-unix.1.0.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D
> stackv4      Building tcpip.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing tcpip.1.1.0.
> stackv4
> stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =3D-=3D-=3D
> stackv4      default    Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
> stackv4      Building mirage-http.1.1.0:
> stackv4        make
> stackv4        make install
> stackv4      Installing mirage-http.1.1.0.
> stackv4
> [ERROR]      The command "opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" =
exited with code 4.
> make: *** [stackv4-configure] Error 1
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>=20
>=20
>=20
> --=20
> Dave Scott


--Apple-Mail=_01423CCF-7129-4FE7-B29F-722981EBDE11
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1


Thanks for the swift replies :-) Running 'opam install mirage' before 'make' did the trick.

- J

On 12 Feb 2014, at 14:52, David Scott wrote:

Hi,

The problem is triggered by the "mirage" command-line tool attempting to replace its own binary:

> stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage': Text file busy



As a workaround, try running "opam upgrade mirage" and then try "make all" again -- by pre-upgrading mirage you should bypass the problem.



I had a quick scan through the mirage/mirage issues list on github and couldn't spot this one. It's probably worth filing this as a bug so we don't forget. Perhaps we could fix it by changing mirage/mirage opam install to "mv mirage mirage.bak; cp newmirage mirage".



Cheers,
Dave




On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield <julian.chesterfield@onapp.com> wrote:


Hi there! Any pointers on the following error I'm getting when trying to build mirage-skeleton on a fresh build server? Ubuntu precise, 12.04.1 LTS.




Thanks!

Julian



root@Build-server:~/mirage-skeleton# opam list

Installed packages for system:

base-bigarray             base  Bigarray library distributed with the OCaml compiler

base-threads              base  Threads library distributed with the OCaml compiler

base-unix                 base  Unix library distributed with the OCaml compiler

cmdliner                 0.9.4  Declarative definition of command line interfaces for OCaml

cohttp                  0.9.16  HTTP library for Lwt, Async and Mirage

cstruct                  1.0.1  access C structures via a camlp4 extension

fieldslib            109.20.03  Syntax extension to define first class values representing record fields, to get and set record fields, iterate and fold over all fields of a record and create new record v

io-page                  1.1.0  Allocate memory pages suitable for aligned I/O

ipaddr                   2.4.0  IP (and MAC) address representation library

lwt                      2.4.4  A cooperative threads library for OCaml

mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for Unix

mirage-console-unix      1.0.0  A Mirage-compatible Console library for Unix

mirage-http              1.1.0  Mirage HTTP client and server driver for Unix

mirage-net-unix          1.1.0  Ethernet network driver for Mirage, using tuntap

mirage-types             1.1.0  Module type definitions for Mirage-compatible applications

mirage-unix              1.1.0  Mirage OS library for Unix compilation

ocamlfind                1.4.0  A library manager for OCaml

ocplib-endian              0.4  Optimised functions to read and write int16/32/64 from strings and bigarrays, based on new primitives added in version 4.01.

optcomp                    1.5  Optional compilation with cpp-like directives

ounit                    2.0.0  Unit testing framework loosely based on HUnit. It is similar to JUnit, and other XUnit testing frameworks

re                       1.2.1  RE is a regular expression library for OCaml

sexplib              110.01.00  Library for serializing OCaml values to and from S-expressions

shared-memory-ring       1.0.0  Shared memory rings for RPC and bytestream communications.

ssl                      0.4.6  Bindings for the libssl

tcpip                    1.1.0  Userlevel TCP/IP stack

tuntap                   0.7.0  TUN/TAP bindings

type_conv            109.60.01  Library for building type-driven syntax extensions

uri                     1.3.13  RFC3986 URI parsing library





root@Build-server:~/mirage-skeleton# make all



.......<--All fine until



stackv4     + Executing: opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip

stackv4      The following actions will be performed:

stackv4       - install type_conv.109.60.01 [required by mirage-http]

stackv4       - install ssl.0.4.6 [required by mirage-http]

stackv4       - install fieldslib.109.20.03 [required by mirage-http]

stackv4       - install sexplib.110.01.00 [required by mirage-http]

stackv4       - recompile lwt.2.4.4 [use ssl]

stackv4       - install uri.1.3.13 [required by mirage-http]

stackv4       - recompile cstruct.1.0.1 [use ssl]

stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 failed.

stackv4

stackv4      ===== ERROR while recompiling mirage.1.1.0 =====

stackv4      # opam-version         1.1.1

stackv4      # os                   linux

stackv4      # command              make install

stackv4      # path                 /root/.opam/system/build/mirage.1.1.0

stackv4      # compiler             system (4.01.0)

stackv4      # exit-code            2

stackv4      # env-file             /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env

stackv4      # stdout-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out

stackv4      # stderr-file          /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err

stackv4      ### stdout ###

stackv4      # ...[truncated]

stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > lib/main.ml.depends


stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot -bin-annot -principal -I lib -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg -package cmdliner -package dynlink -package ipaddr -package lwt -package mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa lib/main.cmx -o lib/main.native


stackv4      # ./setup.bin -test

stackv4      # ./setup.bin -doc

stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'

stackv4      # make[1]: Entering directory `/root/.opam/system/build/mirage.1.1.0'

stackv4      # ./setup.bin -install

stackv4      # make[1]: Leaving directory `/root/.opam/system/build/mirage.1.1.0'

stackv4      ### stderr ###

stackv4      # ...[truncated]

stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a

stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs

stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmi

stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi

stackv4      # Installed /root/.opam/system/lib/mirage/mirage_misc.cmx

stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx

stackv4      # Installed /root/.opam/system/lib/mirage/META

stackv4      # cp: cannot create regular file `/root/.opam/system/bin/mirage': Text file busy

stackv4      # E: Failure("Command ''cp' '/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' '/root/.opam/system/bin/mirage'' terminated with error code 1")

stackv4      # make[1]: *** [install] Error 1

stackv4

stackv4

stackv4      The former state can be restored with opam switch import -f "/root/.opam/system/backup/state-20140112143516.export"

stackv4      'opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' failed.

stackv4      tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz

stackv4      Building uri.1.3.13:

stackv4        ocaml setup.ml -configure --prefix /root/.opam/system

stackv4        ocaml setup.ml -build

stackv4        ocaml setup.ml -install

stackv4      Installing uri.1.3.13.

stackv4

stackv4      =-=-= Installing cohttp.0.9.16 =-=-=

stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz

stackv4      Building cohttp.0.9.16:

stackv4        make PREFIX=/root/.opam/system

stackv4        make PREFIX=/root/.opam/system install

stackv4      Installing cohttp.0.9.16.

stackv4

stackv4      =-=-= Installing io-page.1.1.0 =-=-=

stackv4      Building io-page.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing io-page.1.1.0.

stackv4

stackv4      =-=-= Installing shared-memory-ring.1.0.0 =-=-=

stackv4      Building shared-memory-ring.1.0.0:

stackv4        make all

stackv4        make install

stackv4      Installing shared-memory-ring.1.0.0.

stackv4

stackv4      =-=-= Installing mirage-types.1.1.0 =-=-=

stackv4      Building mirage-types.1.1.0:

stackv4        make install-types

stackv4      Installing mirage-types.1.1.0.

stackv4

stackv4      =-=-= Installing mirage.1.1.0 =-=-=

stackv4      Building mirage.1.1.0:

stackv4        ./configure --bindir /root/.opam/system/bin

stackv4        make

stackv4        make install

stackv4      Removing mirage.1.1.0.

stackv4        ./configure --bindir /root/.opam/system/bin

stackv4        make uninstall

stackv4

stackv4      =-=-= Installing mirage-clock-unix.1.0.0 =-=-=

stackv4      Building mirage-clock-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-clock-unix.1.0.0.

stackv4

stackv4      =-=-= Installing mirage-net-unix.1.1.0 =-=-=

stackv4      Building mirage-net-unix.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-net-unix.1.1.0.

stackv4

stackv4      =-=-= Installing mirage-unix.1.1.0 =-=-=

stackv4      Building mirage-unix.1.1.0:

stackv4        make unix-build

stackv4        make unix-install PREFIX=/root/.opam/system

stackv4      Installing mirage-unix.1.1.0.

stackv4

stackv4      =-=-= Installing mirage-console-unix.1.0.0 =-=-=

stackv4      Building mirage-console-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-console-unix.1.0.0.

stackv4

stackv4      =-=-= Installing tcpip.1.1.0 =-=-=

stackv4      Building tcpip.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing tcpip.1.1.0.

stackv4

stackv4      =-=-= Installing mirage-http.1.1.0 =-=-=

stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz

stackv4      Building mirage-http.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-http.1.1.0.

stackv4

[ERROR]      The command "opam install --yes mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" exited with code 4.

make: *** [stackv4-configure] Error 1

_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists.xenproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel





-- 
Dave Scott





--Apple-Mail=_01423CCF-7129-4FE7-B29F-722981EBDE11--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============4975618164352763796==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 15:54:19 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 15:54:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDc8d-0005z9-GM; Wed, 12 Feb 2014 15:54:15 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDc8c-0005z4-FQ
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 15:54:14 +0000
Received: from [85.158.143.35:7240] by server-1.bemta-4.messagelabs.com id
	24/20-31661-5299BF25; Wed, 12 Feb 2014 15:54:13 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-6.tower-21.messagelabs.com!1392220451!5170057!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=1.3 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,MIME_QP_LONG_LINE,ML_RADAR_SPEW_LINKS_23,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20994 invoked from network); 12 Feb 2014 15:54:11 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-6.tower-21.messagelabs.com with SMTP;
	12 Feb 2014 15:54:11 -0000
Received: (qmail 7456 invoked by uid 634); 12 Feb 2014 15:54:11 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED,HTML_MESSAGE
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Wed, 12 Feb 2014 15:54:08 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <32FF5EFD-2A33-4B09-8623-46965B1AF081@onapp.com>
Date: Wed, 12 Feb 2014 15:54:07 +0000
Message-Id: 
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
	
	<32FF5EFD-2A33-4B09-8623-46965B1AF081@onapp.com>
To: Julian Chesterfield 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2435632594641850326=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============2435632594641850326==
Content-Type: multipart/alternative; boundary="Apple-Mail=_B951D3EE-A89E-4C8A-A42C-44749AB67CAD"


--Apple-Mail=_B951D3EE-A89E-4C8A-A42C-44749AB67CAD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

I've proposed a possible fix here, although it's not the cleanest.

https://github.com/ocaml/opam-repository/pull/1673

-anil

On 12 Feb 2014, at 15:37, Julian Chesterfield =
 wrote:

> Thanks for the swift replies :-) Running 'opam install mirage' before =
'make' did the trick.
>=20
> - J
>=20
> On 12 Feb 2014, at 14:52, David Scott wrote:
>=20
>> Hi,
>>=20
>> The problem is triggered by the "mirage" command-line tool attempting =
to replace its own binary:
>>=20
>> > stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>>=20
>> As a workaround, try running "opam upgrade mirage" and then try "make =
all" again -- by pre-upgrading mirage you should bypass the problem.
>>=20
>> I had a quick scan through the mirage/mirage issues list on github =
and couldn't spot this one. It's probably worth filing this as a bug so =
we don't forget. Perhaps we could fix it by changing mirage/mirage opam =
install to "mv mirage mirage.bak; cp newmirage mirage".
>>=20
>> Cheers,
>> Dave
>>=20
>>=20
>> On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield =
 wrote:
>> Hi there! Any pointers on the following error I'm getting when trying =
to build mirage-skeleton on a fresh build server? Ubuntu precise, =
12.04.1 LTS.
>>=20
>> Thanks!
>> Julian
>>=20
>> root@Build-server:~/mirage-skeleton# opam list
>> Installed packages for system:
>> base-bigarray             base  Bigarray library distributed with the =
OCaml compiler
>> base-threads              base  Threads library distributed with the =
OCaml compiler
>> base-unix                 base  Unix library distributed with the =
OCaml compiler
>> cmdliner                 0.9.4  Declarative definition of command =
line interfaces for OCaml
>> cohttp                  0.9.16  HTTP library for Lwt, Async and =
Mirage
>> cstruct                  1.0.1  access C structures via a camlp4 =
extension
>> fieldslib            109.20.03  Syntax extension to define first =
class values representing record fields, to get and set record fields, =
iterate and fold over all fields of a record and create new record v
>> io-page                  1.1.0  Allocate memory pages suitable for =
aligned I/O
>> ipaddr                   2.4.0  IP (and MAC) address representation =
library
>> lwt                      2.4.4  A cooperative threads library for =
OCaml
>> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for =
Unix
>> mirage-console-unix      1.0.0  A Mirage-compatible Console library =
for Unix
>> mirage-http              1.1.0  Mirage HTTP client and server driver =
for Unix
>> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, =
using tuntap
>> mirage-types             1.1.0  Module type definitions for =
Mirage-compatible applications
>> mirage-unix              1.1.0  Mirage OS library for Unix =
compilation
>> ocamlfind                1.4.0  A library manager for OCaml
>> ocplib-endian              0.4  Optimised functions to read and write =
int16/32/64 from strings and bigarrays, based on new primitives added in =
version 4.01.
>> optcomp                    1.5  Optional compilation with cpp-like =
directives
>> ounit                    2.0.0  Unit testing framework loosely based =
on HUnit. It is similar to JUnit, and other XUnit testing frameworks
>> re                       1.2.1  RE is a regular expression library =
for OCaml
>> sexplib              110.01.00  Library for serializing OCaml values =
to and from S-expressions
>> shared-memory-ring       1.0.0  Shared memory rings for RPC and =
bytestream communications.
>> ssl                      0.4.6  Bindings for the libssl
>> tcpip                    1.1.0  Userlevel TCP/IP stack
>> tuntap                   0.7.0  TUN/TAP bindings
>> type_conv            109.60.01  Library for building type-driven =
syntax extensions
>> uri                     1.3.13  RFC3986 URI parsing library
>>=20
>>=20
>> root@Build-server:~/mirage-skeleton# make all
>>=20
>> .......<--All fine until
>>=20
>> stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
>> stackv4      The following actions will be performed:
>> stackv4       - install type_conv.109.60.01 [required by mirage-http]
>> stackv4       - install ssl.0.4.6 [required by mirage-http]
>> stackv4       - install fieldslib.109.20.03 [required by mirage-http]
>> stackv4       - install sexplib.110.01.00 [required by mirage-http]
>> stackv4       - recompile lwt.2.4.4 [use ssl]
>> stackv4       - install uri.1.3.13 [required by mirage-http]
>> stackv4       - recompile cstruct.1.0.1 [use ssl]
>> stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 =
failed.
>> stackv4
>> stackv4      =3D=3D=3D=3D=3D ERROR while recompiling mirage.1.1.0 =
=3D=3D=3D=3D=3D
>> stackv4      # opam-version         1.1.1
>> stackv4      # os                   linux
>> stackv4      # command              make install
>> stackv4      # path                 =
/root/.opam/system/build/mirage.1.1.0
>> stackv4      # compiler             system (4.01.0)
>> stackv4      # exit-code            2
>> stackv4      # env-file             =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
>> stackv4      # stdout-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
>> stackv4      # stderr-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
>> stackv4      ### stdout ###
>> stackv4      # ...[truncated]
>> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package =
cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules =
lib/main.ml > lib/main.ml.depends
>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmo lib/main.ml
>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmx lib/main.ml
>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa =
lib/main.cmx -o lib/main.native
>> stackv4      # ./setup.bin -test
>> stackv4      # ./setup.bin -doc
>> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
>> stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'
>> stackv4      # ./setup.bin -install
>> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
>> stackv4      ### stderr ###
>> stackv4      # ...[truncated]
>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
>> stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmi
>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
>> stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmx
>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
>> stackv4      # Installed /root/.opam/system/lib/mirage/META
>> stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>> stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")
>> stackv4      # make[1]: *** [install] Error 1
>> stackv4
>> stackv4
>> stackv4      The former state can be restored with opam switch import =
-f "/root/.opam/system/backup/state-20140112143516.export"
>> stackv4      'opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' =
failed.
>> stackv4      tar.gz
>> stackv4      Downloading =
https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
>> stackv4      Building uri.1.3.13:
>> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
>> stackv4        ocaml setup.ml -build
>> stackv4        ocaml setup.ml -install
>> stackv4      Installing uri.1.3.13.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =3D-=3D-=3D
>> stackv4      default    Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
>> stackv4      Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
>> stackv4      Building cohttp.0.9.16:
>> stackv4        make PREFIX=3D/root/.opam/system
>> stackv4        make PREFIX=3D/root/.opam/system install
>> stackv4      Installing cohttp.0.9.16.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =3D-=3D-=3D
>> stackv4      Building io-page.1.1.0:
>> stackv4        make
>> stackv4        make install
>> stackv4      Installing io-page.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing shared-memory-ring.1.0.0 =3D-=3D-=3D=

>> stackv4      Building shared-memory-ring.1.0.0:
>> stackv4        make all
>> stackv4        make install
>> stackv4      Installing shared-memory-ring.1.0.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =3D-=3D-=3D
>> stackv4      Building mirage-types.1.1.0:
>> stackv4        make install-types
>> stackv4      Installing mirage-types.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =3D-=3D-=3D
>> stackv4      Building mirage.1.1.0:
>> stackv4        ./configure --bindir /root/.opam/system/bin
>> stackv4        make
>> stackv4        make install
>> stackv4      Removing mirage.1.1.0.
>> stackv4        ./configure --bindir /root/.opam/system/bin
>> stackv4        make uninstall
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-clock-unix.1.0.0 =3D-=3D-=3D=

>> stackv4      Building mirage-clock-unix.1.0.0:
>> stackv4        make unix-build
>> stackv4        make unix-install
>> stackv4      Installing mirage-clock-unix.1.0.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =3D-=3D-=3D
>> stackv4      Building mirage-net-unix.1.1.0:
>> stackv4        make
>> stackv4        make install
>> stackv4      Installing mirage-net-unix.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =3D-=3D-=3D
>> stackv4      Building mirage-unix.1.1.0:
>> stackv4        make unix-build
>> stackv4        make unix-install PREFIX=3D/root/.opam/system
>> stackv4      Installing mirage-unix.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-console-unix.1.0.0 =3D-=3D-=3D=

>> stackv4      Building mirage-console-unix.1.0.0:
>> stackv4        make unix-build
>> stackv4        make unix-install
>> stackv4      Installing mirage-console-unix.1.0.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D
>> stackv4      Building tcpip.1.1.0:
>> stackv4        make
>> stackv4        make install
>> stackv4      Installing tcpip.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =3D-=3D-=3D
>> stackv4      default    Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
>> stackv4      Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
>> stackv4      Building mirage-http.1.1.0:
>> stackv4        make
>> stackv4        make install
>> stackv4      Installing mirage-http.1.1.0.
>> stackv4
>> [ERROR]      The command "opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" =
exited with code 4.
>> make: *** [stackv4-configure] Error 1
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>>=20
>>=20
>>=20
>> --=20
>> Dave Scott
>=20
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_B951D3EE-A89E-4C8A-A42C-44749AB67CAD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

I've =
proposed a possible fix here, although it's not the =
cleanest.


-anil

On 12 Feb 2014, at 15:37, Julian Chesterfield =
<julian.chesterfield@onapp.co=
m> wrote:

Thanks for the =
swift replies :-) Running 'opam install mirage' before 'make' did the =
trick.

- J

On 12 Feb 2014, =
at 14:52, David Scott wrote:

Hi,

The problem is triggered by the =
"mirage" command-line tool attempting to replace its own =
binary:

> stackv4 =
     # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file =
busy



As a =
workaround, try running "opam upgrade mirage" and then try "make all" =
again -- by pre-upgrading mirage you should bypass the =
problem.



I had a =
quick scan through the mirage/mirage issues list on github and couldn't =
spot this one. It's probably worth filing this as a bug so we don't =
forget. Perhaps we could fix it by changing mirage/mirage opam install =
to "mv mirage mirage.bak; cp newmirage mirage".



Cheers,
=

Dave




On =
Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield <julian.chesterfield@onapp.com> =
wrote:


Hi there! Any pointers =
on the following error I'm getting when trying to build mirage-skeleton =
on a fresh build server? Ubuntu precise, 12.04.1 LTS.




Thanks!

Julian



root@Build-server:~/mirage-skeleton# opam list

Installed packages for system:

base-bigarray             base =
 Bigarray library distributed with the OCaml compiler

base-threads              base =
 Threads library distributed with the OCaml compiler

base-unix                 base =
 Unix library distributed with the OCaml compiler

cmdliner                 0.9.4 =
 Declarative definition of command line interfaces for OCaml

cohttp                 =
 0.9.16  HTTP library for Lwt, Async and Mirage

cstruct                 =
 1.0.1  access C structures via a camlp4 extension

fieldslib            109.20.03 =
 Syntax extension to define first class values representing record =
fields, to get and set record fields, iterate and fold over all fields =
of a record and create new record v

io-page                 =
 1.1.0  Allocate memory pages suitable for aligned I/O

ipaddr                   =
2.4.0  IP (and MAC) address representation library

lwt                   =
   2.4.4  A cooperative threads library for OCaml

mirage-clock-unix        1.0.0  A =
Mirage-compatible Clock library for Unix

mirage-console-unix      1.0.0  A Mirage-compatible =
Console library for Unix

mirage-http              1.1.0 =
 Mirage HTTP client and server driver for Unix

mirage-net-unix          1.1.0  Ethernet =
network driver for Mirage, using tuntap

mirage-types             1.1.0 =
 Module type definitions for Mirage-compatible applications

mirage-unix              1.1.0 =
 Mirage OS library for Unix compilation

ocamlfind                1.4.0 =
 A library manager for OCaml

ocplib-endian              0.4 =
 Optimised functions to read and write int16/32/64 from strings and =
bigarrays, based on new primitives added in version 4.01.

optcomp                   =
 1.5  Optional compilation with cpp-like directives

ounit                   =
 2.0.0  Unit testing framework loosely based on HUnit. It is =
similar to JUnit, and other XUnit testing frameworks

re                     =
  1.2.1  RE is a regular expression library for OCaml

sexplib              110.01.00 =
 Library for serializing OCaml values to and from S-expressions

shared-memory-ring       1.0.0  Shared memory rings =
for RPC and bytestream communications.

ssl                   =
   0.4.6  Bindings for the libssl

tcpip                   =
 1.1.0  Userlevel TCP/IP stack

tuntap                   =
0.7.0  TUN/TAP bindings

type_conv            109.60.01 =
 Library for building type-driven syntax extensions

uri                   =
  1.3.13  RFC3986 URI parsing library





root@Build-server:~/mirage-skeleton# make all



.......<--All fine until



stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip

stackv4      The following actions will be performed:

stackv4       - install type_conv.109.60.01 [required by =
mirage-http]

stackv4       - install ssl.0.4.6 [required by =
mirage-http]

stackv4       - install fieldslib.109.20.03 [required by =
mirage-http]

stackv4       - install sexplib.110.01.00 [required by =
mirage-http]

stackv4       - recompile lwt.2.4.4 [use ssl]

stackv4       - install uri.1.3.13 [required by =
mirage-http]

stackv4       - recompile cstruct.1.0.1 [use ssl]

stackv4       - install cohttp[ERROR] The compilation of =
mirage.1.1.0 failed.

stackv4

stackv4      =3D=3D=3D=3D=3D ERROR while recompiling =
mirage.1.1.0 =3D=3D=3D=3D=3D

stackv4      # opam-version         =
1.1.1

stackv4      # os           =
        linux

stackv4      # command           =
   make install

stackv4      # path           =
      /root/.opam/system/build/mirage.1.1.0

stackv4      # compiler         =
    system (4.01.0)

stackv4      # exit-code         =
   2

stackv4      # env-file         =
    =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env

stackv4      # stdout-file         =
 /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out

stackv4      # stderr-file         =
 /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err

stackv4      ### stdout ###

stackv4      # ...[truncated]

stackv4      # /root/.opam/system/bin/ocamlfind ocamldep =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > =
lib/main.ml.depends


stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c =
-g -annot -bin-annot -principal -I lib -package cmdliner -package =
dynlink -package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt =
-c -g -annot -bin-annot -principal -I lib -package cmdliner -package =
dynlink -package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt =
-g -linkpkg -package cmdliner -package dynlink -package ipaddr -package =
lwt -package mirage-types -package mirage-types.lwt -package unix =
lib/mirage.cmxa lib/main.cmx -o lib/main.native


stackv4      # ./setup.bin -test

stackv4      # ./setup.bin -doc

stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      # ./setup.bin -install

stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      ### stderr ###

stackv4      # ...[truncated]

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.a

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmxs

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmi

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmi

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmx

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmx

stackv4      # Installed =
/root/.opam/system/lib/mirage/META

stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy

stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")

stackv4      # make[1]: *** [install] Error 1

stackv4

stackv4

stackv4      The former state can be restored with opam =
switch import -f =
"/root/.opam/system/backup/state-20140112143516.export"

stackv4      'opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' =
failed.

stackv4      tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
stackv4      Building uri.1.3.13:

stackv4        ocaml setup.ml -configure --prefix =
/root/.opam/system

stackv4        ocaml setup.ml -build

stackv4        ocaml setup.ml -install

stackv4      Installing uri.1.3.13.

stackv4

stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =
=3D-=3D-=3D

stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.g=
z

stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.g=
z

stackv4      Building cohttp.0.9.16:

stackv4        make PREFIX=3D/root/.opam/system

stackv4        make PREFIX=3D/root/.opam/system =
install

stackv4      Installing cohttp.0.9.16.

stackv4

stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =
=3D-=3D-=3D

stackv4      Building io-page.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing io-page.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing =
shared-memory-ring.1.0.0 =3D-=3D-=3D

stackv4      Building shared-memory-ring.1.0.0:

stackv4        make all

stackv4        make install

stackv4      Installing shared-memory-ring.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-types.1.1.0:

stackv4        make install-types

stackv4      Installing mirage-types.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage.1.1.0:

stackv4        ./configure --bindir =
/root/.opam/system/bin

stackv4        make

stackv4        make install

stackv4      Removing mirage.1.1.0.

stackv4        ./configure --bindir =
/root/.opam/system/bin

stackv4        make uninstall

stackv4

stackv4      =3D-=3D-=3D Installing =
mirage-clock-unix.1.0.0 =3D-=3D-=3D

stackv4      Building mirage-clock-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-clock-unix.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-net-unix.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-net-unix.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-unix.1.1.0:

stackv4        make unix-build

stackv4        make unix-install =
PREFIX=3D/root/.opam/system

stackv4      Installing mirage-unix.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing =
mirage-console-unix.1.0.0 =3D-=3D-=3D

stackv4      Building mirage-console-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-console-unix.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D=


stackv4      Building tcpip.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing tcpip.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =
=3D-=3D-=3D

stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.t=
ar.gz

stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.t=
ar.gz

stackv4      Building mirage-http.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-http.1.1.0.

stackv4

[ERROR]      The command "opam install --yes =
mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix =
mirage-unix tcpip" exited with code 4.

make: *** [stackv4-configure] Error 1

_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists.x=
enproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir=
ageos-devel





-- 
Dave =
Scott


=


_____________________________________________=
__
MirageOS-devel mailing list
MirageOS-devel@lists.x=
enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/=
mirageos-devel

=

--Apple-Mail=_B951D3EE-A89E-4C8A-A42C-44749AB67CAD--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============2435632594641850326==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 12 15:54:19 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 12 Feb 2014 15:54:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDc8d-0005z9-GM; Wed, 12 Feb 2014 15:54:15 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDc8c-0005z4-FQ
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 15:54:14 +0000
Received: from [85.158.143.35:7240] by server-1.bemta-4.messagelabs.com id
	24/20-31661-5299BF25; Wed, 12 Feb 2014 15:54:13 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-6.tower-21.messagelabs.com!1392220451!5170057!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=1.3 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,MIME_QP_LONG_LINE,ML_RADAR_SPEW_LINKS_23,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20994 invoked from network); 12 Feb 2014 15:54:11 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-6.tower-21.messagelabs.com with SMTP;
	12 Feb 2014 15:54:11 -0000
Received: (qmail 7456 invoked by uid 634); 12 Feb 2014 15:54:11 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED,HTML_MESSAGE
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Wed, 12 Feb 2014 15:54:08 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <32FF5EFD-2A33-4B09-8623-46965B1AF081@onapp.com>
Date: Wed, 12 Feb 2014 15:54:07 +0000
Message-Id: 
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
	
	<32FF5EFD-2A33-4B09-8623-46965B1AF081@onapp.com>
To: Julian Chesterfield 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2435632594641850326=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============2435632594641850326==
Content-Type: multipart/alternative; boundary="Apple-Mail=_B951D3EE-A89E-4C8A-A42C-44749AB67CAD"


--Apple-Mail=_B951D3EE-A89E-4C8A-A42C-44749AB67CAD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

I've proposed a possible fix here, although it's not the cleanest.

https://github.com/ocaml/opam-repository/pull/1673

-anil

On 12 Feb 2014, at 15:37, Julian Chesterfield =
 wrote:

> Thanks for the swift replies :-) Running 'opam install mirage' before =
'make' did the trick.
>=20
> - J
>=20
> On 12 Feb 2014, at 14:52, David Scott wrote:
>=20
>> Hi,
>>=20
>> The problem is triggered by the "mirage" command-line tool attempting =
to replace its own binary:
>>=20
>> > stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>>=20
>> As a workaround, try running "opam upgrade mirage" and then try "make =
all" again -- by pre-upgrading mirage you should bypass the problem.
>>=20
>> I had a quick scan through the mirage/mirage issues list on github =
and couldn't spot this one. It's probably worth filing this as a bug so =
we don't forget. Perhaps we could fix it by changing mirage/mirage opam =
install to "mv mirage mirage.bak; cp newmirage mirage".
>>=20
>> Cheers,
>> Dave
>>=20
>>=20
>> On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield =
 wrote:
>> Hi there! Any pointers on the following error I'm getting when trying =
to build mirage-skeleton on a fresh build server? Ubuntu precise, =
12.04.1 LTS.
>>=20
>> Thanks!
>> Julian
>>=20
>> root@Build-server:~/mirage-skeleton# opam list
>> Installed packages for system:
>> base-bigarray             base  Bigarray library distributed with the =
OCaml compiler
>> base-threads              base  Threads library distributed with the =
OCaml compiler
>> base-unix                 base  Unix library distributed with the =
OCaml compiler
>> cmdliner                 0.9.4  Declarative definition of command =
line interfaces for OCaml
>> cohttp                  0.9.16  HTTP library for Lwt, Async and =
Mirage
>> cstruct                  1.0.1  access C structures via a camlp4 =
extension
>> fieldslib            109.20.03  Syntax extension to define first =
class values representing record fields, to get and set record fields, =
iterate and fold over all fields of a record and create new record v
>> io-page                  1.1.0  Allocate memory pages suitable for =
aligned I/O
>> ipaddr                   2.4.0  IP (and MAC) address representation =
library
>> lwt                      2.4.4  A cooperative threads library for =
OCaml
>> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library for =
Unix
>> mirage-console-unix      1.0.0  A Mirage-compatible Console library =
for Unix
>> mirage-http              1.1.0  Mirage HTTP client and server driver =
for Unix
>> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, =
using tuntap
>> mirage-types             1.1.0  Module type definitions for =
Mirage-compatible applications
>> mirage-unix              1.1.0  Mirage OS library for Unix =
compilation
>> ocamlfind                1.4.0  A library manager for OCaml
>> ocplib-endian              0.4  Optimised functions to read and write =
int16/32/64 from strings and bigarrays, based on new primitives added in =
version 4.01.
>> optcomp                    1.5  Optional compilation with cpp-like =
directives
>> ounit                    2.0.0  Unit testing framework loosely based =
on HUnit. It is similar to JUnit, and other XUnit testing frameworks
>> re                       1.2.1  RE is a regular expression library =
for OCaml
>> sexplib              110.01.00  Library for serializing OCaml values =
to and from S-expressions
>> shared-memory-ring       1.0.0  Shared memory rings for RPC and =
bytestream communications.
>> ssl                      0.4.6  Bindings for the libssl
>> tcpip                    1.1.0  Userlevel TCP/IP stack
>> tuntap                   0.7.0  TUN/TAP bindings
>> type_conv            109.60.01  Library for building type-driven =
syntax extensions
>> uri                     1.3.13  RFC3986 URI parsing library
>>=20
>>=20
>> root@Build-server:~/mirage-skeleton# make all
>>=20
>> .......<--All fine until
>>=20
>> stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
>> stackv4      The following actions will be performed:
>> stackv4       - install type_conv.109.60.01 [required by mirage-http]
>> stackv4       - install ssl.0.4.6 [required by mirage-http]
>> stackv4       - install fieldslib.109.20.03 [required by mirage-http]
>> stackv4       - install sexplib.110.01.00 [required by mirage-http]
>> stackv4       - recompile lwt.2.4.4 [use ssl]
>> stackv4       - install uri.1.3.13 [required by mirage-http]
>> stackv4       - recompile cstruct.1.0.1 [use ssl]
>> stackv4       - install cohttp[ERROR] The compilation of mirage.1.1.0 =
failed.
>> stackv4
>> stackv4      =3D=3D=3D=3D=3D ERROR while recompiling mirage.1.1.0 =
=3D=3D=3D=3D=3D
>> stackv4      # opam-version         1.1.1
>> stackv4      # os                   linux
>> stackv4      # command              make install
>> stackv4      # path                 =
/root/.opam/system/build/mirage.1.1.0
>> stackv4      # compiler             system (4.01.0)
>> stackv4      # exit-code            2
>> stackv4      # env-file             =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
>> stackv4      # stdout-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
>> stackv4      # stderr-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
>> stackv4      ### stdout ###
>> stackv4      # ...[truncated]
>> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package =
cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules =
lib/main.ml > lib/main.ml.depends
>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmo lib/main.ml
>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmx lib/main.ml
>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa =
lib/main.cmx -o lib/main.native
>> stackv4      # ./setup.bin -test
>> stackv4      # ./setup.bin -doc
>> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
>> stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'
>> stackv4      # ./setup.bin -install
>> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
>> stackv4      ### stderr ###
>> stackv4      # ...[truncated]
>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
>> stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmi
>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
>> stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmx
>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
>> stackv4      # Installed /root/.opam/system/lib/mirage/META
>> stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>> stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")
>> stackv4      # make[1]: *** [install] Error 1
>> stackv4
>> stackv4
>> stackv4      The former state can be restored with opam switch import =
-f "/root/.opam/system/backup/state-20140112143516.export"
>> stackv4      'opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' =
failed.
>> stackv4      tar.gz
>> stackv4      Downloading =
https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
>> stackv4      Building uri.1.3.13:
>> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
>> stackv4        ocaml setup.ml -build
>> stackv4        ocaml setup.ml -install
>> stackv4      Installing uri.1.3.13.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =3D-=3D-=3D
>> stackv4      default    Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
>> stackv4      Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
>> stackv4      Building cohttp.0.9.16:
>> stackv4        make PREFIX=3D/root/.opam/system
>> stackv4        make PREFIX=3D/root/.opam/system install
>> stackv4      Installing cohttp.0.9.16.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =3D-=3D-=3D
>> stackv4      Building io-page.1.1.0:
>> stackv4        make
>> stackv4        make install
>> stackv4      Installing io-page.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing shared-memory-ring.1.0.0 =3D-=3D-=3D=

>> stackv4      Building shared-memory-ring.1.0.0:
>> stackv4        make all
>> stackv4        make install
>> stackv4      Installing shared-memory-ring.1.0.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =3D-=3D-=3D
>> stackv4      Building mirage-types.1.1.0:
>> stackv4        make install-types
>> stackv4      Installing mirage-types.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =3D-=3D-=3D
>> stackv4      Building mirage.1.1.0:
>> stackv4        ./configure --bindir /root/.opam/system/bin
>> stackv4        make
>> stackv4        make install
>> stackv4      Removing mirage.1.1.0.
>> stackv4        ./configure --bindir /root/.opam/system/bin
>> stackv4        make uninstall
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-clock-unix.1.0.0 =3D-=3D-=3D=

>> stackv4      Building mirage-clock-unix.1.0.0:
>> stackv4        make unix-build
>> stackv4        make unix-install
>> stackv4      Installing mirage-clock-unix.1.0.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =3D-=3D-=3D
>> stackv4      Building mirage-net-unix.1.1.0:
>> stackv4        make
>> stackv4        make install
>> stackv4      Installing mirage-net-unix.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =3D-=3D-=3D
>> stackv4      Building mirage-unix.1.1.0:
>> stackv4        make unix-build
>> stackv4        make unix-install PREFIX=3D/root/.opam/system
>> stackv4      Installing mirage-unix.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-console-unix.1.0.0 =3D-=3D-=3D=

>> stackv4      Building mirage-console-unix.1.0.0:
>> stackv4        make unix-build
>> stackv4        make unix-install
>> stackv4      Installing mirage-console-unix.1.0.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D
>> stackv4      Building tcpip.1.1.0:
>> stackv4        make
>> stackv4        make install
>> stackv4      Installing tcpip.1.1.0.
>> stackv4
>> stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =3D-=3D-=3D
>> stackv4      default    Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
>> stackv4      Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
>> stackv4      Building mirage-http.1.1.0:
>> stackv4        make
>> stackv4        make install
>> stackv4      Installing mirage-http.1.1.0.
>> stackv4
>> [ERROR]      The command "opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" =
exited with code 4.
>> make: *** [stackv4-configure] Error 1
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>>=20
>>=20
>>=20
>> --=20
>> Dave Scott
>=20
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_B951D3EE-A89E-4C8A-A42C-44749AB67CAD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

I've =
proposed a possible fix here, although it's not the =
cleanest.


-anil

On 12 Feb 2014, at 15:37, Julian Chesterfield =
<julian.chesterfield@onapp.co=
m> wrote:

Thanks for the =
swift replies :-) Running 'opam install mirage' before 'make' did the =
trick.

- J

On 12 Feb 2014, =
at 14:52, David Scott wrote:

Hi,

The problem is triggered by the =
"mirage" command-line tool attempting to replace its own =
binary:

> stackv4 =
     # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file =
busy



As a =
workaround, try running "opam upgrade mirage" and then try "make all" =
again -- by pre-upgrading mirage you should bypass the =
problem.



I had a =
quick scan through the mirage/mirage issues list on github and couldn't =
spot this one. It's probably worth filing this as a bug so we don't =
forget. Perhaps we could fix it by changing mirage/mirage opam install =
to "mv mirage mirage.bak; cp newmirage mirage".



Cheers,
=

Dave




On =
Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield <julian.chesterfield@onapp.com> =
wrote:


Hi there! Any pointers =
on the following error I'm getting when trying to build mirage-skeleton =
on a fresh build server? Ubuntu precise, 12.04.1 LTS.




Thanks!

Julian



root@Build-server:~/mirage-skeleton# opam list

Installed packages for system:

base-bigarray             base =
 Bigarray library distributed with the OCaml compiler

base-threads              base =
 Threads library distributed with the OCaml compiler

base-unix                 base =
 Unix library distributed with the OCaml compiler

cmdliner                 0.9.4 =
 Declarative definition of command line interfaces for OCaml

cohttp                 =
 0.9.16  HTTP library for Lwt, Async and Mirage

cstruct                 =
 1.0.1  access C structures via a camlp4 extension

fieldslib            109.20.03 =
 Syntax extension to define first class values representing record =
fields, to get and set record fields, iterate and fold over all fields =
of a record and create new record v

io-page                 =
 1.1.0  Allocate memory pages suitable for aligned I/O

ipaddr                   =
2.4.0  IP (and MAC) address representation library

lwt                   =
   2.4.4  A cooperative threads library for OCaml

mirage-clock-unix        1.0.0  A =
Mirage-compatible Clock library for Unix

mirage-console-unix      1.0.0  A Mirage-compatible =
Console library for Unix

mirage-http              1.1.0 =
 Mirage HTTP client and server driver for Unix

mirage-net-unix          1.1.0  Ethernet =
network driver for Mirage, using tuntap

mirage-types             1.1.0 =
 Module type definitions for Mirage-compatible applications

mirage-unix              1.1.0 =
 Mirage OS library for Unix compilation

ocamlfind                1.4.0 =
 A library manager for OCaml

ocplib-endian              0.4 =
 Optimised functions to read and write int16/32/64 from strings and =
bigarrays, based on new primitives added in version 4.01.

optcomp                   =
 1.5  Optional compilation with cpp-like directives

ounit                   =
 2.0.0  Unit testing framework loosely based on HUnit. It is =
similar to JUnit, and other XUnit testing frameworks

re                     =
  1.2.1  RE is a regular expression library for OCaml

sexplib              110.01.00 =
 Library for serializing OCaml values to and from S-expressions

shared-memory-ring       1.0.0  Shared memory rings =
for RPC and bytestream communications.

ssl                   =
   0.4.6  Bindings for the libssl

tcpip                   =
 1.1.0  Userlevel TCP/IP stack

tuntap                   =
0.7.0  TUN/TAP bindings

type_conv            109.60.01 =
 Library for building type-driven syntax extensions

uri                   =
  1.3.13  RFC3986 URI parsing library





root@Build-server:~/mirage-skeleton# make all



.......<--All fine until



stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip

stackv4      The following actions will be performed:

stackv4       - install type_conv.109.60.01 [required by =
mirage-http]

stackv4       - install ssl.0.4.6 [required by =
mirage-http]

stackv4       - install fieldslib.109.20.03 [required by =
mirage-http]

stackv4       - install sexplib.110.01.00 [required by =
mirage-http]

stackv4       - recompile lwt.2.4.4 [use ssl]

stackv4       - install uri.1.3.13 [required by =
mirage-http]

stackv4       - recompile cstruct.1.0.1 [use ssl]

stackv4       - install cohttp[ERROR] The compilation of =
mirage.1.1.0 failed.

stackv4

stackv4      =3D=3D=3D=3D=3D ERROR while recompiling =
mirage.1.1.0 =3D=3D=3D=3D=3D

stackv4      # opam-version         =
1.1.1

stackv4      # os           =
        linux

stackv4      # command           =
   make install

stackv4      # path           =
      /root/.opam/system/build/mirage.1.1.0

stackv4      # compiler         =
    system (4.01.0)

stackv4      # exit-code         =
   2

stackv4      # env-file         =
    =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env

stackv4      # stdout-file         =
 /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out

stackv4      # stderr-file         =
 /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err

stackv4      ### stdout ###

stackv4      # ...[truncated]

stackv4      # /root/.opam/system/bin/ocamlfind ocamldep =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > =
lib/main.ml.depends


stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c =
-g -annot -bin-annot -principal -I lib -package cmdliner -package =
dynlink -package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt =
-c -g -annot -bin-annot -principal -I lib -package cmdliner -package =
dynlink -package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt =
-g -linkpkg -package cmdliner -package dynlink -package ipaddr -package =
lwt -package mirage-types -package mirage-types.lwt -package unix =
lib/mirage.cmxa lib/main.cmx -o lib/main.native


stackv4      # ./setup.bin -test

stackv4      # ./setup.bin -doc

stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      # ./setup.bin -install

stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      ### stderr ###

stackv4      # ...[truncated]

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.a

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmxs

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmi

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmi

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmx

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmx

stackv4      # Installed =
/root/.opam/system/lib/mirage/META

stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy

stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")

stackv4      # make[1]: *** [install] Error 1

stackv4

stackv4

stackv4      The former state can be restored with opam =
switch import -f =
"/root/.opam/system/backup/state-20140112143516.export"

stackv4      'opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' =
failed.

stackv4      tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
stackv4      Building uri.1.3.13:

stackv4        ocaml setup.ml -configure --prefix =
/root/.opam/system

stackv4        ocaml setup.ml -build

stackv4        ocaml setup.ml -install

stackv4      Installing uri.1.3.13.

stackv4

stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =
=3D-=3D-=3D

stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.g=
z

stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.g=
z

stackv4      Building cohttp.0.9.16:

stackv4        make PREFIX=3D/root/.opam/system

stackv4        make PREFIX=3D/root/.opam/system =
install

stackv4      Installing cohttp.0.9.16.

stackv4

stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =
=3D-=3D-=3D

stackv4      Building io-page.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing io-page.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing =
shared-memory-ring.1.0.0 =3D-=3D-=3D

stackv4      Building shared-memory-ring.1.0.0:

stackv4        make all

stackv4        make install

stackv4      Installing shared-memory-ring.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-types.1.1.0:

stackv4        make install-types

stackv4      Installing mirage-types.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage.1.1.0:

stackv4        ./configure --bindir =
/root/.opam/system/bin

stackv4        make

stackv4        make install

stackv4      Removing mirage.1.1.0.

stackv4        ./configure --bindir =
/root/.opam/system/bin

stackv4        make uninstall

stackv4

stackv4      =3D-=3D-=3D Installing =
mirage-clock-unix.1.0.0 =3D-=3D-=3D

stackv4      Building mirage-clock-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-clock-unix.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-net-unix.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-net-unix.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-unix.1.1.0:

stackv4        make unix-build

stackv4        make unix-install =
PREFIX=3D/root/.opam/system

stackv4      Installing mirage-unix.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing =
mirage-console-unix.1.0.0 =3D-=3D-=3D

stackv4      Building mirage-console-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-console-unix.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D=


stackv4      Building tcpip.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing tcpip.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =
=3D-=3D-=3D

stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.t=
ar.gz

stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.t=
ar.gz

stackv4      Building mirage-http.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-http.1.1.0.

stackv4

[ERROR]      The command "opam install --yes =
mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix =
mirage-unix tcpip" exited with code 4.

make: *** [stackv4-configure] Error 1

_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists.x=
enproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir=
ageos-devel





-- 
Dave =
Scott


=


_____________________________________________=
__
MirageOS-devel mailing list
MirageOS-devel@lists.x=
enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/=
mirageos-devel

=

--Apple-Mail=_B951D3EE-A89E-4C8A-A42C-44749AB67CAD--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============2435632594641850326==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 14:51:29 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 14:51:29 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDxdN-0008Fv-NU; Thu, 13 Feb 2014 14:51:25 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDxdL-0008Ff-H9
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 14:51:24 +0000
Received: from [85.158.139.211:16970] by server-14.bemta-5.messagelabs.com id
	68/A3-27598-AEBDCF25; Thu, 13 Feb 2014 14:51:22 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-8.tower-206.messagelabs.com!1392303080!3715605!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=1.3 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,MIME_QP_LONG_LINE,ML_RADAR_SPEW_LINKS_23,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29315 invoked from network); 13 Feb 2014 14:51:20 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-8.tower-206.messagelabs.com with SMTP;
	13 Feb 2014 14:51:20 -0000
Received: (qmail 28297 invoked by uid 634); 13 Feb 2014 14:51:19 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED,HTML_MESSAGE
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 13 Feb 2014 14:51:17 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: 
Date: Thu, 13 Feb 2014 14:51:16 +0000
Message-Id: <972CBBCC-A8C0-43C9-A464-C4DEDFAC37D6@recoil.org>
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
	
	<32FF5EFD-2A33-4B09-8623-46965B1AF081@onapp.com>
	
To: Julian Chesterfield 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5165804725907381231=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============5165804725907381231==
Content-Type: multipart/alternative; boundary="Apple-Mail=_69CC14BA-D1D9-40E0-B84C-AA2690B4D893"


--Apple-Mail=_69CC14BA-D1D9-40E0-B84C-AA2690B4D893
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

A cleaned up version has been merged now, so please let me know if you =
see any more "text file busy" errors.

-anil

On 12 Feb 2014, at 15:54, Anil Madhavapeddy  wrote:

> I've proposed a possible fix here, although it's not the cleanest.
>=20
> https://github.com/ocaml/opam-repository/pull/1673
>=20
> -anil
>=20
> On 12 Feb 2014, at 15:37, Julian Chesterfield =
 wrote:
>=20
>> Thanks for the swift replies :-) Running 'opam install mirage' before =
'make' did the trick.
>>=20
>> - J
>>=20
>> On 12 Feb 2014, at 14:52, David Scott wrote:
>>=20
>>> Hi,
>>>=20
>>> The problem is triggered by the "mirage" command-line tool =
attempting to replace its own binary:
>>>=20
>>> > stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>>>=20
>>> As a workaround, try running "opam upgrade mirage" and then try =
"make all" again -- by pre-upgrading mirage you should bypass the =
problem.
>>>=20
>>> I had a quick scan through the mirage/mirage issues list on github =
and couldn't spot this one. It's probably worth filing this as a bug so =
we don't forget. Perhaps we could fix it by changing mirage/mirage opam =
install to "mv mirage mirage.bak; cp newmirage mirage".
>>>=20
>>> Cheers,
>>> Dave
>>>=20
>>>=20
>>> On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield =
 wrote:
>>> Hi there! Any pointers on the following error I'm getting when =
trying to build mirage-skeleton on a fresh build server? Ubuntu precise, =
12.04.1 LTS.
>>>=20
>>> Thanks!
>>> Julian
>>>=20
>>> root@Build-server:~/mirage-skeleton# opam list
>>> Installed packages for system:
>>> base-bigarray             base  Bigarray library distributed with =
the OCaml compiler
>>> base-threads              base  Threads library distributed with the =
OCaml compiler
>>> base-unix                 base  Unix library distributed with the =
OCaml compiler
>>> cmdliner                 0.9.4  Declarative definition of command =
line interfaces for OCaml
>>> cohttp                  0.9.16  HTTP library for Lwt, Async and =
Mirage
>>> cstruct                  1.0.1  access C structures via a camlp4 =
extension
>>> fieldslib            109.20.03  Syntax extension to define first =
class values representing record fields, to get and set record fields, =
iterate and fold over all fields of a record and create new record v
>>> io-page                  1.1.0  Allocate memory pages suitable for =
aligned I/O
>>> ipaddr                   2.4.0  IP (and MAC) address representation =
library
>>> lwt                      2.4.4  A cooperative threads library for =
OCaml
>>> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library =
for Unix
>>> mirage-console-unix      1.0.0  A Mirage-compatible Console library =
for Unix
>>> mirage-http              1.1.0  Mirage HTTP client and server driver =
for Unix
>>> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, =
using tuntap
>>> mirage-types             1.1.0  Module type definitions for =
Mirage-compatible applications
>>> mirage-unix              1.1.0  Mirage OS library for Unix =
compilation
>>> ocamlfind                1.4.0  A library manager for OCaml
>>> ocplib-endian              0.4  Optimised functions to read and =
write int16/32/64 from strings and bigarrays, based on new primitives =
added in version 4.01.
>>> optcomp                    1.5  Optional compilation with cpp-like =
directives
>>> ounit                    2.0.0  Unit testing framework loosely based =
on HUnit. It is similar to JUnit, and other XUnit testing frameworks
>>> re                       1.2.1  RE is a regular expression library =
for OCaml
>>> sexplib              110.01.00  Library for serializing OCaml values =
to and from S-expressions
>>> shared-memory-ring       1.0.0  Shared memory rings for RPC and =
bytestream communications.
>>> ssl                      0.4.6  Bindings for the libssl
>>> tcpip                    1.1.0  Userlevel TCP/IP stack
>>> tuntap                   0.7.0  TUN/TAP bindings
>>> type_conv            109.60.01  Library for building type-driven =
syntax extensions
>>> uri                     1.3.13  RFC3986 URI parsing library
>>>=20
>>>=20
>>> root@Build-server:~/mirage-skeleton# make all
>>>=20
>>> .......<--All fine until
>>>=20
>>> stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
>>> stackv4      The following actions will be performed:
>>> stackv4       - install type_conv.109.60.01 [required by =
mirage-http]
>>> stackv4       - install ssl.0.4.6 [required by mirage-http]
>>> stackv4       - install fieldslib.109.20.03 [required by =
mirage-http]
>>> stackv4       - install sexplib.110.01.00 [required by mirage-http]
>>> stackv4       - recompile lwt.2.4.4 [use ssl]
>>> stackv4       - install uri.1.3.13 [required by mirage-http]
>>> stackv4       - recompile cstruct.1.0.1 [use ssl]
>>> stackv4       - install cohttp[ERROR] The compilation of =
mirage.1.1.0 failed.
>>> stackv4
>>> stackv4      =3D=3D=3D=3D=3D ERROR while recompiling mirage.1.1.0 =
=3D=3D=3D=3D=3D
>>> stackv4      # opam-version         1.1.1
>>> stackv4      # os                   linux
>>> stackv4      # command              make install
>>> stackv4      # path                 =
/root/.opam/system/build/mirage.1.1.0
>>> stackv4      # compiler             system (4.01.0)
>>> stackv4      # exit-code            2
>>> stackv4      # env-file             =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
>>> stackv4      # stdout-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
>>> stackv4      # stderr-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
>>> stackv4      ### stdout ###
>>> stackv4      # ...[truncated]
>>> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package =
cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules =
lib/main.ml > lib/main.ml.depends
>>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmo lib/main.ml
>>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g =
-annot -bin-annot -principal -I lib -package cmdliner -package dynlink =
-package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml
>>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa =
lib/main.cmx -o lib/main.native
>>> stackv4      # ./setup.bin -test
>>> stackv4      # ./setup.bin -doc
>>> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
>>> stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'
>>> stackv4      # ./setup.bin -install
>>> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
>>> stackv4      ### stderr ###
>>> stackv4      # ...[truncated]
>>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
>>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
>>> stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmi
>>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
>>> stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmx
>>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
>>> stackv4      # Installed /root/.opam/system/lib/mirage/META
>>> stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>>> stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")
>>> stackv4      # make[1]: *** [install] Error 1
>>> stackv4
>>> stackv4
>>> stackv4      The former state can be restored with opam switch =
import -f "/root/.opam/system/backup/state-20140112143516.export"
>>> stackv4      'opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' =
failed.
>>> stackv4      tar.gz
>>> stackv4      Downloading =
https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
>>> stackv4      Building uri.1.3.13:
>>> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
>>> stackv4        ocaml setup.ml -build
>>> stackv4        ocaml setup.ml -install
>>> stackv4      Installing uri.1.3.13.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =3D-=3D-=3D
>>> stackv4      default    Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
>>> stackv4      Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
>>> stackv4      Building cohttp.0.9.16:
>>> stackv4        make PREFIX=3D/root/.opam/system
>>> stackv4        make PREFIX=3D/root/.opam/system install
>>> stackv4      Installing cohttp.0.9.16.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =3D-=3D-=3D
>>> stackv4      Building io-page.1.1.0:
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Installing io-page.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing shared-memory-ring.1.0.0 =3D-=3D-=3D=

>>> stackv4      Building shared-memory-ring.1.0.0:
>>> stackv4        make all
>>> stackv4        make install
>>> stackv4      Installing shared-memory-ring.1.0.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =3D-=3D-=3D
>>> stackv4      Building mirage-types.1.1.0:
>>> stackv4        make install-types
>>> stackv4      Installing mirage-types.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =3D-=3D-=3D
>>> stackv4      Building mirage.1.1.0:
>>> stackv4        ./configure --bindir /root/.opam/system/bin
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Removing mirage.1.1.0.
>>> stackv4        ./configure --bindir /root/.opam/system/bin
>>> stackv4        make uninstall
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-clock-unix.1.0.0 =3D-=3D-=3D=

>>> stackv4      Building mirage-clock-unix.1.0.0:
>>> stackv4        make unix-build
>>> stackv4        make unix-install
>>> stackv4      Installing mirage-clock-unix.1.0.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =3D-=3D-=3D
>>> stackv4      Building mirage-net-unix.1.1.0:
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Installing mirage-net-unix.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =3D-=3D-=3D
>>> stackv4      Building mirage-unix.1.1.0:
>>> stackv4        make unix-build
>>> stackv4        make unix-install PREFIX=3D/root/.opam/system
>>> stackv4      Installing mirage-unix.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-console-unix.1.0.0 =3D-=3D-=
=3D
>>> stackv4      Building mirage-console-unix.1.0.0:
>>> stackv4        make unix-build
>>> stackv4        make unix-install
>>> stackv4      Installing mirage-console-unix.1.0.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D
>>> stackv4      Building tcpip.1.1.0:
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Installing tcpip.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =3D-=3D-=3D
>>> stackv4      default    Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
>>> stackv4      Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
>>> stackv4      Building mirage-http.1.1.0:
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Installing mirage-http.1.1.0.
>>> stackv4
>>> [ERROR]      The command "opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" =
exited with code 4.
>>> make: *** [stackv4-configure] Error 1
>>> _______________________________________________
>>> MirageOS-devel mailing list
>>> MirageOS-devel@lists.xenproject.org
>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>>>=20
>>>=20
>>>=20
>>> --=20
>>> Dave Scott
>>=20
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>=20
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_69CC14BA-D1D9-40E0-B84C-AA2690B4D893
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

A =
cleaned up version has been merged now, so please let me know if you see =
any more "text file busy" =
errors.

-anil

On 12 Feb 2014, =
at 15:54, Anil Madhavapeddy <anil@recoil.org> wrote:

I've =
proposed a possible fix here, although it's not the =
cleanest.


-anil

On 12 Feb 2014, at 15:37, Julian Chesterfield =
<julian.chesterfield@onapp.co=
m> wrote:

Thanks for the =
swift replies :-) Running 'opam install mirage' before 'make' did the =
trick.

- J

On 12 Feb 2014, =
at 14:52, David Scott wrote:

Hi,

The problem is triggered by the =
"mirage" command-line tool attempting to replace its own =
binary:

> stackv4 =
     # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file =
busy



As a =
workaround, try running "opam upgrade mirage" and then try "make all" =
again -- by pre-upgrading mirage you should bypass the =
problem.



I had a =
quick scan through the mirage/mirage issues list on github and couldn't =
spot this one. It's probably worth filing this as a bug so we don't =
forget. Perhaps we could fix it by changing mirage/mirage opam install =
to "mv mirage mirage.bak; cp newmirage mirage".



Cheers,
=

Dave




On =
Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield <julian.chesterfield@onapp.com> =
wrote:


Hi there! Any pointers =
on the following error I'm getting when trying to build mirage-skeleton =
on a fresh build server? Ubuntu precise, 12.04.1 LTS.




Thanks!

Julian



root@Build-server:~/mirage-skeleton# opam list

Installed packages for system:

base-bigarray             base =
 Bigarray library distributed with the OCaml compiler

base-threads              base =
 Threads library distributed with the OCaml compiler

base-unix                 base =
 Unix library distributed with the OCaml compiler

cmdliner                 0.9.4 =
 Declarative definition of command line interfaces for OCaml

cohttp                 =
 0.9.16  HTTP library for Lwt, Async and Mirage

cstruct                 =
 1.0.1  access C structures via a camlp4 extension

fieldslib            109.20.03 =
 Syntax extension to define first class values representing record =
fields, to get and set record fields, iterate and fold over all fields =
of a record and create new record v

io-page                 =
 1.1.0  Allocate memory pages suitable for aligned I/O

ipaddr                   =
2.4.0  IP (and MAC) address representation library

lwt                   =
   2.4.4  A cooperative threads library for OCaml

mirage-clock-unix        1.0.0  A =
Mirage-compatible Clock library for Unix

mirage-console-unix      1.0.0  A Mirage-compatible =
Console library for Unix

mirage-http              1.1.0 =
 Mirage HTTP client and server driver for Unix

mirage-net-unix          1.1.0  Ethernet =
network driver for Mirage, using tuntap

mirage-types             1.1.0 =
 Module type definitions for Mirage-compatible applications

mirage-unix              1.1.0 =
 Mirage OS library for Unix compilation

ocamlfind                1.4.0 =
 A library manager for OCaml

ocplib-endian              0.4 =
 Optimised functions to read and write int16/32/64 from strings and =
bigarrays, based on new primitives added in version 4.01.

optcomp                   =
 1.5  Optional compilation with cpp-like directives

ounit                   =
 2.0.0  Unit testing framework loosely based on HUnit. It is =
similar to JUnit, and other XUnit testing frameworks

re                     =
  1.2.1  RE is a regular expression library for OCaml

sexplib              110.01.00 =
 Library for serializing OCaml values to and from S-expressions

shared-memory-ring       1.0.0  Shared memory rings =
for RPC and bytestream communications.

ssl                   =
   0.4.6  Bindings for the libssl

tcpip                   =
 1.1.0  Userlevel TCP/IP stack

tuntap                   =
0.7.0  TUN/TAP bindings

type_conv            109.60.01 =
 Library for building type-driven syntax extensions

uri                   =
  1.3.13  RFC3986 URI parsing library





root@Build-server:~/mirage-skeleton# make all



.......<--All fine until



stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip

stackv4      The following actions will be performed:

stackv4       - install type_conv.109.60.01 [required by =
mirage-http]

stackv4       - install ssl.0.4.6 [required by =
mirage-http]

stackv4       - install fieldslib.109.20.03 [required by =
mirage-http]

stackv4       - install sexplib.110.01.00 [required by =
mirage-http]

stackv4       - recompile lwt.2.4.4 [use ssl]

stackv4       - install uri.1.3.13 [required by =
mirage-http]

stackv4       - recompile cstruct.1.0.1 [use ssl]

stackv4       - install cohttp[ERROR] The compilation of =
mirage.1.1.0 failed.

stackv4

stackv4      =3D=3D=3D=3D=3D ERROR while recompiling =
mirage.1.1.0 =3D=3D=3D=3D=3D

stackv4      # opam-version         =
1.1.1

stackv4      # os           =
        linux

stackv4      # command           =
   make install

stackv4      # path           =
      /root/.opam/system/build/mirage.1.1.0

stackv4      # compiler         =
    system (4.01.0)

stackv4      # exit-code         =
   2

stackv4      # env-file         =
    =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env

stackv4      # stdout-file         =
 /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out

stackv4      # stderr-file         =
 /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err

stackv4      ### stdout ###

stackv4      # ...[truncated]

stackv4      # /root/.opam/system/bin/ocamlfind ocamldep =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > =
lib/main.ml.depends


stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c =
-g -annot -bin-annot -principal -I lib -package cmdliner -package =
dynlink -package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt =
-c -g -annot -bin-annot -principal -I lib -package cmdliner -package =
dynlink -package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt =
-g -linkpkg -package cmdliner -package dynlink -package ipaddr -package =
lwt -package mirage-types -package mirage-types.lwt -package unix =
lib/mirage.cmxa lib/main.cmx -o lib/main.native


stackv4      # ./setup.bin -test

stackv4      # ./setup.bin -doc

stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      # ./setup.bin -install

stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      ### stderr ###

stackv4      # ...[truncated]

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.a

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmxs

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmi

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmi

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmx

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmx

stackv4      # Installed =
/root/.opam/system/lib/mirage/META

stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy

stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")

stackv4      # make[1]: *** [install] Error 1

stackv4

stackv4

stackv4      The former state can be restored with opam =
switch import -f =
"/root/.opam/system/backup/state-20140112143516.export"

stackv4      'opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' =
failed.

stackv4      tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
stackv4      Building uri.1.3.13:

stackv4        ocaml setup.ml -configure --prefix =
/root/.opam/system

stackv4        ocaml setup.ml -build

stackv4        ocaml setup.ml -install

stackv4      Installing uri.1.3.13.

stackv4

stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =
=3D-=3D-=3D

stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.g=
z

stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.g=
z

stackv4      Building cohttp.0.9.16:

stackv4        make PREFIX=3D/root/.opam/system

stackv4        make PREFIX=3D/root/.opam/system =
install

stackv4      Installing cohttp.0.9.16.

stackv4

stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =
=3D-=3D-=3D

stackv4      Building io-page.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing io-page.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing =
shared-memory-ring.1.0.0 =3D-=3D-=3D

stackv4      Building shared-memory-ring.1.0.0:

stackv4        make all

stackv4        make install

stackv4      Installing shared-memory-ring.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-types.1.1.0:

stackv4        make install-types

stackv4      Installing mirage-types.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage.1.1.0:

stackv4        ./configure --bindir =
/root/.opam/system/bin

stackv4        make

stackv4        make install

stackv4      Removing mirage.1.1.0.

stackv4        ./configure --bindir =
/root/.opam/system/bin

stackv4        make uninstall

stackv4

stackv4      =3D-=3D-=3D Installing =
mirage-clock-unix.1.0.0 =3D-=3D-=3D

stackv4      Building mirage-clock-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-clock-unix.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-net-unix.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-net-unix.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-unix.1.1.0:

stackv4        make unix-build

stackv4        make unix-install =
PREFIX=3D/root/.opam/system

stackv4      Installing mirage-unix.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing =
mirage-console-unix.1.0.0 =3D-=3D-=3D

stackv4      Building mirage-console-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-console-unix.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D=


stackv4      Building tcpip.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing tcpip.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =
=3D-=3D-=3D

stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.t=
ar.gz

stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.t=
ar.gz

stackv4      Building mirage-http.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-http.1.1.0.

stackv4

[ERROR]      The command "opam install --yes =
mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix =
mirage-unix tcpip" exited with code 4.

make: *** [stackv4-configure] Error 1

_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists.x=
enproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir=
ageos-devel





-- 
Dave =
Scott


=


_____________________________________________=
__
MirageOS-devel mailing list
MirageOS-devel@lists.x=
enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel=


___________________________________=
____________
MirageOS-devel mailing list
MirageOS-devel@lists.x=
enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/=
mirageos-devel

=

--Apple-Mail=_69CC14BA-D1D9-40E0-B84C-AA2690B4D893--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============5165804725907381231==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 14:51:29 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 14:51:29 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDxdN-0008Fv-NU; Thu, 13 Feb 2014 14:51:25 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDxdL-0008Ff-H9
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 14:51:24 +0000
Received: from [85.158.139.211:16970] by server-14.bemta-5.messagelabs.com id
	68/A3-27598-AEBDCF25; Thu, 13 Feb 2014 14:51:22 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-8.tower-206.messagelabs.com!1392303080!3715605!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=1.3 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_40_50,HTML_MESSAGE,MIME_QP_LONG_LINE,ML_RADAR_SPEW_LINKS_23,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29315 invoked from network); 13 Feb 2014 14:51:20 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-8.tower-206.messagelabs.com with SMTP;
	13 Feb 2014 14:51:20 -0000
Received: (qmail 28297 invoked by uid 634); 13 Feb 2014 14:51:19 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED,HTML_MESSAGE
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 13 Feb 2014 14:51:17 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: 
Date: Thu, 13 Feb 2014 14:51:16 +0000
Message-Id: <972CBBCC-A8C0-43C9-A464-C4DEDFAC37D6@recoil.org>
References: <20DCE145-7156-46F7-AA2F-1EAEA303E032@onapp.com>
	
	<32FF5EFD-2A33-4B09-8623-46965B1AF081@onapp.com>
	
To: Julian Chesterfield 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problems building mirage-skeleton stackv4
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5165804725907381231=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============5165804725907381231==
Content-Type: multipart/alternative; boundary="Apple-Mail=_69CC14BA-D1D9-40E0-B84C-AA2690B4D893"


--Apple-Mail=_69CC14BA-D1D9-40E0-B84C-AA2690B4D893
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

A cleaned up version has been merged now, so please let me know if you =
see any more "text file busy" errors.

-anil

On 12 Feb 2014, at 15:54, Anil Madhavapeddy  wrote:

> I've proposed a possible fix here, although it's not the cleanest.
>=20
> https://github.com/ocaml/opam-repository/pull/1673
>=20
> -anil
>=20
> On 12 Feb 2014, at 15:37, Julian Chesterfield =
 wrote:
>=20
>> Thanks for the swift replies :-) Running 'opam install mirage' before =
'make' did the trick.
>>=20
>> - J
>>=20
>> On 12 Feb 2014, at 14:52, David Scott wrote:
>>=20
>>> Hi,
>>>=20
>>> The problem is triggered by the "mirage" command-line tool =
attempting to replace its own binary:
>>>=20
>>> > stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>>>=20
>>> As a workaround, try running "opam upgrade mirage" and then try =
"make all" again -- by pre-upgrading mirage you should bypass the =
problem.
>>>=20
>>> I had a quick scan through the mirage/mirage issues list on github =
and couldn't spot this one. It's probably worth filing this as a bug so =
we don't forget. Perhaps we could fix it by changing mirage/mirage opam =
install to "mv mirage mirage.bak; cp newmirage mirage".
>>>=20
>>> Cheers,
>>> Dave
>>>=20
>>>=20
>>> On Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield =
 wrote:
>>> Hi there! Any pointers on the following error I'm getting when =
trying to build mirage-skeleton on a fresh build server? Ubuntu precise, =
12.04.1 LTS.
>>>=20
>>> Thanks!
>>> Julian
>>>=20
>>> root@Build-server:~/mirage-skeleton# opam list
>>> Installed packages for system:
>>> base-bigarray             base  Bigarray library distributed with =
the OCaml compiler
>>> base-threads              base  Threads library distributed with the =
OCaml compiler
>>> base-unix                 base  Unix library distributed with the =
OCaml compiler
>>> cmdliner                 0.9.4  Declarative definition of command =
line interfaces for OCaml
>>> cohttp                  0.9.16  HTTP library for Lwt, Async and =
Mirage
>>> cstruct                  1.0.1  access C structures via a camlp4 =
extension
>>> fieldslib            109.20.03  Syntax extension to define first =
class values representing record fields, to get and set record fields, =
iterate and fold over all fields of a record and create new record v
>>> io-page                  1.1.0  Allocate memory pages suitable for =
aligned I/O
>>> ipaddr                   2.4.0  IP (and MAC) address representation =
library
>>> lwt                      2.4.4  A cooperative threads library for =
OCaml
>>> mirage-clock-unix        1.0.0  A Mirage-compatible Clock library =
for Unix
>>> mirage-console-unix      1.0.0  A Mirage-compatible Console library =
for Unix
>>> mirage-http              1.1.0  Mirage HTTP client and server driver =
for Unix
>>> mirage-net-unix          1.1.0  Ethernet network driver for Mirage, =
using tuntap
>>> mirage-types             1.1.0  Module type definitions for =
Mirage-compatible applications
>>> mirage-unix              1.1.0  Mirage OS library for Unix =
compilation
>>> ocamlfind                1.4.0  A library manager for OCaml
>>> ocplib-endian              0.4  Optimised functions to read and =
write int16/32/64 from strings and bigarrays, based on new primitives =
added in version 4.01.
>>> optcomp                    1.5  Optional compilation with cpp-like =
directives
>>> ounit                    2.0.0  Unit testing framework loosely based =
on HUnit. It is similar to JUnit, and other XUnit testing frameworks
>>> re                       1.2.1  RE is a regular expression library =
for OCaml
>>> sexplib              110.01.00  Library for serializing OCaml values =
to and from S-expressions
>>> shared-memory-ring       1.0.0  Shared memory rings for RPC and =
bytestream communications.
>>> ssl                      0.4.6  Bindings for the libssl
>>> tcpip                    1.1.0  Userlevel TCP/IP stack
>>> tuntap                   0.7.0  TUN/TAP bindings
>>> type_conv            109.60.01  Library for building type-driven =
syntax extensions
>>> uri                     1.3.13  RFC3986 URI parsing library
>>>=20
>>>=20
>>> root@Build-server:~/mirage-skeleton# make all
>>>=20
>>> .......<--All fine until
>>>=20
>>> stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip
>>> stackv4      The following actions will be performed:
>>> stackv4       - install type_conv.109.60.01 [required by =
mirage-http]
>>> stackv4       - install ssl.0.4.6 [required by mirage-http]
>>> stackv4       - install fieldslib.109.20.03 [required by =
mirage-http]
>>> stackv4       - install sexplib.110.01.00 [required by mirage-http]
>>> stackv4       - recompile lwt.2.4.4 [use ssl]
>>> stackv4       - install uri.1.3.13 [required by mirage-http]
>>> stackv4       - recompile cstruct.1.0.1 [use ssl]
>>> stackv4       - install cohttp[ERROR] The compilation of =
mirage.1.1.0 failed.
>>> stackv4
>>> stackv4      =3D=3D=3D=3D=3D ERROR while recompiling mirage.1.1.0 =
=3D=3D=3D=3D=3D
>>> stackv4      # opam-version         1.1.1
>>> stackv4      # os                   linux
>>> stackv4      # command              make install
>>> stackv4      # path                 =
/root/.opam/system/build/mirage.1.1.0
>>> stackv4      # compiler             system (4.01.0)
>>> stackv4      # exit-code            2
>>> stackv4      # env-file             =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env
>>> stackv4      # stdout-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out
>>> stackv4      # stderr-file          =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err
>>> stackv4      ### stdout ###
>>> stackv4      # ...[truncated]
>>> stackv4      # /root/.opam/system/bin/ocamlfind ocamldep -package =
cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules =
lib/main.ml > lib/main.ml.depends
>>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c -g -annot =
-bin-annot -principal -I lib -package cmdliner -package dynlink -package =
ipaddr -package lwt -package mirage-types -package mirage-types.lwt =
-package unix -I lib -o lib/main.cmo lib/main.ml
>>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -c -g =
-annot -bin-annot -principal -I lib -package cmdliner -package dynlink =
-package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml
>>> stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt -g -linkpkg =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix lib/mirage.cmxa =
lib/main.cmx -o lib/main.native
>>> stackv4      # ./setup.bin -test
>>> stackv4      # ./setup.bin -doc
>>> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
>>> stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'
>>> stackv4      # ./setup.bin -install
>>> stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'
>>> stackv4      ### stderr ###
>>> stackv4      # ...[truncated]
>>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.a
>>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmxs
>>> stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmi
>>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmi
>>> stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmx
>>> stackv4      # Installed /root/.opam/system/lib/mirage/mirage.cmx
>>> stackv4      # Installed /root/.opam/system/lib/mirage/META
>>> stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy
>>> stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")
>>> stackv4      # make[1]: *** [install] Error 1
>>> stackv4
>>> stackv4
>>> stackv4      The former state can be restored with opam switch =
import -f "/root/.opam/system/backup/state-20140112143516.export"
>>> stackv4      'opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' =
failed.
>>> stackv4      tar.gz
>>> stackv4      Downloading =
https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
>>> stackv4      Building uri.1.3.13:
>>> stackv4        ocaml setup.ml -configure --prefix /root/.opam/system
>>> stackv4        ocaml setup.ml -build
>>> stackv4        ocaml setup.ml -install
>>> stackv4      Installing uri.1.3.13.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =3D-=3D-=3D
>>> stackv4      default    Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
>>> stackv4      Downloading =
https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.gz
>>> stackv4      Building cohttp.0.9.16:
>>> stackv4        make PREFIX=3D/root/.opam/system
>>> stackv4        make PREFIX=3D/root/.opam/system install
>>> stackv4      Installing cohttp.0.9.16.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =3D-=3D-=3D
>>> stackv4      Building io-page.1.1.0:
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Installing io-page.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing shared-memory-ring.1.0.0 =3D-=3D-=3D=

>>> stackv4      Building shared-memory-ring.1.0.0:
>>> stackv4        make all
>>> stackv4        make install
>>> stackv4      Installing shared-memory-ring.1.0.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =3D-=3D-=3D
>>> stackv4      Building mirage-types.1.1.0:
>>> stackv4        make install-types
>>> stackv4      Installing mirage-types.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =3D-=3D-=3D
>>> stackv4      Building mirage.1.1.0:
>>> stackv4        ./configure --bindir /root/.opam/system/bin
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Removing mirage.1.1.0.
>>> stackv4        ./configure --bindir /root/.opam/system/bin
>>> stackv4        make uninstall
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-clock-unix.1.0.0 =3D-=3D-=3D=

>>> stackv4      Building mirage-clock-unix.1.0.0:
>>> stackv4        make unix-build
>>> stackv4        make unix-install
>>> stackv4      Installing mirage-clock-unix.1.0.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =3D-=3D-=3D
>>> stackv4      Building mirage-net-unix.1.1.0:
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Installing mirage-net-unix.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =3D-=3D-=3D
>>> stackv4      Building mirage-unix.1.1.0:
>>> stackv4        make unix-build
>>> stackv4        make unix-install PREFIX=3D/root/.opam/system
>>> stackv4      Installing mirage-unix.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-console-unix.1.0.0 =3D-=3D-=
=3D
>>> stackv4      Building mirage-console-unix.1.0.0:
>>> stackv4        make unix-build
>>> stackv4        make unix-install
>>> stackv4      Installing mirage-console-unix.1.0.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D
>>> stackv4      Building tcpip.1.1.0:
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Installing tcpip.1.1.0.
>>> stackv4
>>> stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =3D-=3D-=3D
>>> stackv4      default    Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
>>> stackv4      Downloading =
https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.tar.gz
>>> stackv4      Building mirage-http.1.1.0:
>>> stackv4        make
>>> stackv4        make install
>>> stackv4      Installing mirage-http.1.1.0.
>>> stackv4
>>> [ERROR]      The command "opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip" =
exited with code 4.
>>> make: *** [stackv4-configure] Error 1
>>> _______________________________________________
>>> MirageOS-devel mailing list
>>> MirageOS-devel@lists.xenproject.org
>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>>>=20
>>>=20
>>>=20
>>> --=20
>>> Dave Scott
>>=20
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>=20
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_69CC14BA-D1D9-40E0-B84C-AA2690B4D893
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

A =
cleaned up version has been merged now, so please let me know if you see =
any more "text file busy" =
errors.

-anil

On 12 Feb 2014, =
at 15:54, Anil Madhavapeddy <anil@recoil.org> wrote:

I've =
proposed a possible fix here, although it's not the =
cleanest.


-anil

On 12 Feb 2014, at 15:37, Julian Chesterfield =
<julian.chesterfield@onapp.co=
m> wrote:

Thanks for the =
swift replies :-) Running 'opam install mirage' before 'make' did the =
trick.

- J

On 12 Feb 2014, =
at 14:52, David Scott wrote:

Hi,

The problem is triggered by the =
"mirage" command-line tool attempting to replace its own =
binary:

> stackv4 =
     # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file =
busy



As a =
workaround, try running "opam upgrade mirage" and then try "make all" =
again -- by pre-upgrading mirage you should bypass the =
problem.



I had a =
quick scan through the mirage/mirage issues list on github and couldn't =
spot this one. It's probably worth filing this as a bug so we don't =
forget. Perhaps we could fix it by changing mirage/mirage opam install =
to "mv mirage mirage.bak; cp newmirage mirage".



Cheers,
=

Dave




On =
Wed, Feb 12, 2014 at 2:46 PM, Julian Chesterfield <julian.chesterfield@onapp.com> =
wrote:


Hi there! Any pointers =
on the following error I'm getting when trying to build mirage-skeleton =
on a fresh build server? Ubuntu precise, 12.04.1 LTS.




Thanks!

Julian



root@Build-server:~/mirage-skeleton# opam list

Installed packages for system:

base-bigarray             base =
 Bigarray library distributed with the OCaml compiler

base-threads              base =
 Threads library distributed with the OCaml compiler

base-unix                 base =
 Unix library distributed with the OCaml compiler

cmdliner                 0.9.4 =
 Declarative definition of command line interfaces for OCaml

cohttp                 =
 0.9.16  HTTP library for Lwt, Async and Mirage

cstruct                 =
 1.0.1  access C structures via a camlp4 extension

fieldslib            109.20.03 =
 Syntax extension to define first class values representing record =
fields, to get and set record fields, iterate and fold over all fields =
of a record and create new record v

io-page                 =
 1.1.0  Allocate memory pages suitable for aligned I/O

ipaddr                   =
2.4.0  IP (and MAC) address representation library

lwt                   =
   2.4.4  A cooperative threads library for OCaml

mirage-clock-unix        1.0.0  A =
Mirage-compatible Clock library for Unix

mirage-console-unix      1.0.0  A Mirage-compatible =
Console library for Unix

mirage-http              1.1.0 =
 Mirage HTTP client and server driver for Unix

mirage-net-unix          1.1.0  Ethernet =
network driver for Mirage, using tuntap

mirage-types             1.1.0 =
 Module type definitions for Mirage-compatible applications

mirage-unix              1.1.0 =
 Mirage OS library for Unix compilation

ocamlfind                1.4.0 =
 A library manager for OCaml

ocplib-endian              0.4 =
 Optimised functions to read and write int16/32/64 from strings and =
bigarrays, based on new primitives added in version 4.01.

optcomp                   =
 1.5  Optional compilation with cpp-like directives

ounit                   =
 2.0.0  Unit testing framework loosely based on HUnit. It is =
similar to JUnit, and other XUnit testing frameworks

re                     =
  1.2.1  RE is a regular expression library for OCaml

sexplib              110.01.00 =
 Library for serializing OCaml values to and from S-expressions

shared-memory-ring       1.0.0  Shared memory rings =
for RPC and bytestream communications.

ssl                   =
   0.4.6  Bindings for the libssl

tcpip                   =
 1.1.0  Userlevel TCP/IP stack

tuntap                   =
0.7.0  TUN/TAP bindings

type_conv            109.60.01 =
 Library for building type-driven syntax extensions

uri                   =
  1.3.13  RFC3986 URI parsing library





root@Build-server:~/mirage-skeleton# make all



.......<--All fine until



stackv4     + Executing: opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip

stackv4      The following actions will be performed:

stackv4       - install type_conv.109.60.01 [required by =
mirage-http]

stackv4       - install ssl.0.4.6 [required by =
mirage-http]

stackv4       - install fieldslib.109.20.03 [required by =
mirage-http]

stackv4       - install sexplib.110.01.00 [required by =
mirage-http]

stackv4       - recompile lwt.2.4.4 [use ssl]

stackv4       - install uri.1.3.13 [required by =
mirage-http]

stackv4       - recompile cstruct.1.0.1 [use ssl]

stackv4       - install cohttp[ERROR] The compilation of =
mirage.1.1.0 failed.

stackv4

stackv4      =3D=3D=3D=3D=3D ERROR while recompiling =
mirage.1.1.0 =3D=3D=3D=3D=3D

stackv4      # opam-version         =
1.1.1

stackv4      # os           =
        linux

stackv4      # command           =
   make install

stackv4      # path           =
      /root/.opam/system/build/mirage.1.1.0

stackv4      # compiler         =
    system (4.01.0)

stackv4      # exit-code         =
   2

stackv4      # env-file         =
    =
/root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.env

stackv4      # stdout-file         =
 /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.out

stackv4      # stderr-file         =
 /root/.opam/system/build/mirage.1.1.0/mirage-17018-e0ba4f.err

stackv4      ### stdout ###

stackv4      # ...[truncated]

stackv4      # /root/.opam/system/bin/ocamlfind ocamldep =
-package cmdliner -package dynlink -package ipaddr -package lwt -package =
mirage-types -package mirage-types.lwt -package unix -modules lib/main.ml > =
lib/main.ml.depends


stackv4      # /root/.opam/system/bin/ocamlfind ocamlc -c =
-g -annot -bin-annot -principal -I lib -package cmdliner -package =
dynlink -package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmo lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt =
-c -g -annot -bin-annot -principal -I lib -package cmdliner -package =
dynlink -package ipaddr -package lwt -package mirage-types -package =
mirage-types.lwt -package unix -I lib -o lib/main.cmx lib/main.ml


stackv4      # /root/.opam/system/bin/ocamlfind ocamlopt =
-g -linkpkg -package cmdliner -package dynlink -package ipaddr -package =
lwt -package mirage-types -package mirage-types.lwt -package unix =
lib/mirage.cmxa lib/main.cmx -o lib/main.native


stackv4      # ./setup.bin -test

stackv4      # ./setup.bin -doc

stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      # make[1]: Entering directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      # ./setup.bin -install

stackv4      # make[1]: Leaving directory =
`/root/.opam/system/build/mirage.1.1.0'

stackv4      ### stderr ###

stackv4      # ...[truncated]

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.a

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmxs

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmi

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmi

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage_misc.cmx

stackv4      # Installed =
/root/.opam/system/lib/mirage/mirage.cmx

stackv4      # Installed =
/root/.opam/system/lib/mirage/META

stackv4      # cp: cannot create regular file =
`/root/.opam/system/bin/mirage': Text file busy

stackv4      # E: Failure("Command ''cp' =
'/root/.opam/system/build/mirage.1.1.0/_build/lib/main.native' =
'/root/.opam/system/bin/mirage'' terminated with error code 1")

stackv4      # make[1]: *** [install] Error 1

stackv4

stackv4

stackv4      The former state can be restored with opam =
switch import -f =
"/root/.opam/system/backup/state-20140112143516.export"

stackv4      'opam install --yes mirage-clock-unix =
mirage-console-unix mirage-http mirage-net-unix mirage-unix tcpip' =
failed.

stackv4      tar.gz

stackv4      Downloading https://opam.ocaml.org/archives/uri.1.3.13+opam.tar.gz
stackv4      Building uri.1.3.13:

stackv4        ocaml setup.ml -configure --prefix =
/root/.opam/system

stackv4        ocaml setup.ml -build

stackv4        ocaml setup.ml -install

stackv4      Installing uri.1.3.13.

stackv4

stackv4      =3D-=3D-=3D Installing cohttp.0.9.16 =
=3D-=3D-=3D

stackv4      default    Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.g=
z

stackv4      Downloading https://opam.ocaml.org/archives/cohttp.0.9.16+opam.tar.g=
z

stackv4      Building cohttp.0.9.16:

stackv4        make PREFIX=3D/root/.opam/system

stackv4        make PREFIX=3D/root/.opam/system =
install

stackv4      Installing cohttp.0.9.16.

stackv4

stackv4      =3D-=3D-=3D Installing io-page.1.1.0 =
=3D-=3D-=3D

stackv4      Building io-page.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing io-page.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing =
shared-memory-ring.1.0.0 =3D-=3D-=3D

stackv4      Building shared-memory-ring.1.0.0:

stackv4        make all

stackv4        make install

stackv4      Installing shared-memory-ring.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-types.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-types.1.1.0:

stackv4        make install-types

stackv4      Installing mirage-types.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage.1.1.0:

stackv4        ./configure --bindir =
/root/.opam/system/bin

stackv4        make

stackv4        make install

stackv4      Removing mirage.1.1.0.

stackv4        ./configure --bindir =
/root/.opam/system/bin

stackv4        make uninstall

stackv4

stackv4      =3D-=3D-=3D Installing =
mirage-clock-unix.1.0.0 =3D-=3D-=3D

stackv4      Building mirage-clock-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-clock-unix.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-net-unix.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-net-unix.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-net-unix.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-unix.1.1.0 =
=3D-=3D-=3D

stackv4      Building mirage-unix.1.1.0:

stackv4        make unix-build

stackv4        make unix-install =
PREFIX=3D/root/.opam/system

stackv4      Installing mirage-unix.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing =
mirage-console-unix.1.0.0 =3D-=3D-=3D

stackv4      Building mirage-console-unix.1.0.0:

stackv4        make unix-build

stackv4        make unix-install

stackv4      Installing mirage-console-unix.1.0.0.

stackv4

stackv4      =3D-=3D-=3D Installing tcpip.1.1.0 =3D-=3D-=3D=


stackv4      Building tcpip.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing tcpip.1.1.0.

stackv4

stackv4      =3D-=3D-=3D Installing mirage-http.1.1.0 =
=3D-=3D-=3D

stackv4      default    Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.t=
ar.gz

stackv4      Downloading https://opam.ocaml.org/archives/mirage-http.1.1.0+opam.t=
ar.gz

stackv4      Building mirage-http.1.1.0:

stackv4        make

stackv4        make install

stackv4      Installing mirage-http.1.1.0.

stackv4

[ERROR]      The command "opam install --yes =
mirage-clock-unix mirage-console-unix mirage-http mirage-net-unix =
mirage-unix tcpip" exited with code 4.

make: *** [stackv4-configure] Error 1

_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists.x=
enproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir=
ageos-devel





-- 
Dave =
Scott


=


_____________________________________________=
__
MirageOS-devel mailing list
MirageOS-devel@lists.x=
enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel=


___________________________________=
____________
MirageOS-devel mailing list
MirageOS-devel@lists.x=
enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/=
mirageos-devel

=

--Apple-Mail=_69CC14BA-D1D9-40E0-B84C-AA2690B4D893--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============5165804725907381231==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 14:53:34 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 14:53: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 1WDxfS-0008Jw-0Y; Thu, 13 Feb 2014 14:53:34 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDxfQ-0008Jp-QR
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 14:53:33 +0000
Received: from [85.158.139.211:59564] by server-17.bemta-5.messagelabs.com id
	12/F3-31975-B6CDCF25; Thu, 13 Feb 2014 14:53:31 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-5.tower-206.messagelabs.com!1392303210!3621745!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13922 invoked from network); 13 Feb 2014 14:53:31 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-5.tower-206.messagelabs.com with SMTP;
	13 Feb 2014 14:53:31 -0000
Received: (qmail 22021 invoked by uid 634); 13 Feb 2014 14:53:30 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 13 Feb 2014 14:53:30 +0000
From: Anil Madhavapeddy 
Date: Thu, 13 Feb 2014 14:53:29 +0000
References: 
To: mirageos-devel@lists.xenproject.org
Message-Id: 
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] Fwd: [compiler-hacking] OCaml compiler hacking
	session
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org



Begin forwarded message:

> From: Jeremy Yallop 
> Subject: [compiler-hacking] OCaml compiler hacking session
> Date: 11 February 2014 18:36:09 GMT
> To: "cl-ocamllabs-staff@lists.cam.ac.uk" , "cl-mirage@lists.cam.ac.uk List" , cam-compiler-hacking@lists.ocaml.org
> 
> It's time for the fourth Cambridge OCaml compiler-hacking session!
> We'll be meeting in the Computer Lab again next Tuesday evening.
> 
> If you're planning to come along, it'd be helpful if you could
> indicate interest via Doodle:
> 
>    http://doodle.com/5tk8rs5k3mh82qqx
> 
> and sign up to the mailing list to receive updates:
> 
>    http://lists.ocaml.org/listinfo/cam-compiler-hacking
> 
> Where: Room FW11, Computer Laboratory, Madingley Road
>       Directions to the building: http://www.cl.cam.ac.uk/directions/
>       Room plan:
> http://www.cl.cam.ac.uk/research/dtg/openroommap/static/?s=FW11&labels=1
> 
> When: 6pm, Tuesday 18th February
> 
> Who: anyone interested in improving OCaml. Knowledge of OCaml
> programming will obviously be helpful, but prior experience of working
> on OCaml internals isn't necessary.
> 
> What: fixing bugs, implementing new features, learning about OCaml internals
> 
> Wiki: https://github.com/ocamllabs/compiler-hacking/wiki
> 
> We're defining "compiler" pretty broadly, to include anything that's
> part of the standard distribution, which means at least the standard
> library, runtime, tools (ocamldep, ocamllex, ocamlyacc, etc.),
> ocamlbuild, the documentation, and the compiler itself. We'll have
> suggestions for mini-projects for various levels of experience, but
> feel free to come along and work on whatever you fancy.
> 
> We'll also be ordering pizza, so if you want to be counted for food
> you should aim to arrive by 6.30pm.
> _______________________________________________
> Cam-compiler-hacking mailing list
> Cam-compiler-hacking@lists.ocaml.org
> http://lists.ocaml.org/listinfo/cam-compiler-hacking
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 14:53:34 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 14:53: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 1WDxfS-0008Jw-0Y; Thu, 13 Feb 2014 14:53:34 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDxfQ-0008Jp-QR
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 14:53:33 +0000
Received: from [85.158.139.211:59564] by server-17.bemta-5.messagelabs.com id
	12/F3-31975-B6CDCF25; Thu, 13 Feb 2014 14:53:31 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-5.tower-206.messagelabs.com!1392303210!3621745!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13922 invoked from network); 13 Feb 2014 14:53:31 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-5.tower-206.messagelabs.com with SMTP;
	13 Feb 2014 14:53:31 -0000
Received: (qmail 22021 invoked by uid 634); 13 Feb 2014 14:53:30 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 13 Feb 2014 14:53:30 +0000
From: Anil Madhavapeddy 
Date: Thu, 13 Feb 2014 14:53:29 +0000
References: 
To: mirageos-devel@lists.xenproject.org
Message-Id: 
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] Fwd: [compiler-hacking] OCaml compiler hacking
	session
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org



Begin forwarded message:

> From: Jeremy Yallop 
> Subject: [compiler-hacking] OCaml compiler hacking session
> Date: 11 February 2014 18:36:09 GMT
> To: "cl-ocamllabs-staff@lists.cam.ac.uk" , "cl-mirage@lists.cam.ac.uk List" , cam-compiler-hacking@lists.ocaml.org
> 
> It's time for the fourth Cambridge OCaml compiler-hacking session!
> We'll be meeting in the Computer Lab again next Tuesday evening.
> 
> If you're planning to come along, it'd be helpful if you could
> indicate interest via Doodle:
> 
>    http://doodle.com/5tk8rs5k3mh82qqx
> 
> and sign up to the mailing list to receive updates:
> 
>    http://lists.ocaml.org/listinfo/cam-compiler-hacking
> 
> Where: Room FW11, Computer Laboratory, Madingley Road
>       Directions to the building: http://www.cl.cam.ac.uk/directions/
>       Room plan:
> http://www.cl.cam.ac.uk/research/dtg/openroommap/static/?s=FW11&labels=1
> 
> When: 6pm, Tuesday 18th February
> 
> Who: anyone interested in improving OCaml. Knowledge of OCaml
> programming will obviously be helpful, but prior experience of working
> on OCaml internals isn't necessary.
> 
> What: fixing bugs, implementing new features, learning about OCaml internals
> 
> Wiki: https://github.com/ocamllabs/compiler-hacking/wiki
> 
> We're defining "compiler" pretty broadly, to include anything that's
> part of the standard distribution, which means at least the standard
> library, runtime, tools (ocamldep, ocamllex, ocamlyacc, etc.),
> ocamlbuild, the documentation, and the compiler itself. We'll have
> suggestions for mini-projects for various levels of experience, but
> feel free to come along and work on whatever you fancy.
> 
> We'll also be ordering pizza, so if you want to be counted for food
> you should aim to arrive by 6.30pm.
> _______________________________________________
> Cam-compiler-hacking mailing list
> Cam-compiler-hacking@lists.ocaml.org
> http://lists.ocaml.org/listinfo/cam-compiler-hacking
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:11:35 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:11: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 1WDysv-0004R2-2R; Thu, 13 Feb 2014 16:11:33 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDyst-0004Ql-P3
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:11:32 +0000
Received: from [193.109.254.147:49283] by server-5.bemta-14.messagelabs.com id
	D2/91-16688-3BEECF25; Thu, 13 Feb 2014 16:11:31 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1392307887!4154076!1
X-Originating-IP: [209.85.192.178]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_SEX,HTML_20_30,
	HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24663 invoked from network); 13 Feb 2014 16:11:29 -0000
Received: from mail-pd0-f178.google.com (HELO mail-pd0-f178.google.com)
	(209.85.192.178)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 16:11:29 -0000
Received: by mail-pd0-f178.google.com with SMTP id fp1so2016245pdb.9
	for ;
	Thu, 13 Feb 2014 08:11:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=l4q+OojFnRmbuTjY5oVmgFxE0xUQZ0oQjJWFX6YSNwk=;
	b=G889E7CdC4fVg3KEAey8o4Ym6tEwmrEiKp2JrCQjrEp75Nka/+BaCknNm/BmKLrqpj
	mfYbIP/DbTXa3CHLbVCHz6v/Ym8aoXtYexisIG7m5l7LdzLVx7X8TKM0tWV/xVooNS7S
	lTGQ9fOi8hf21QFFIOfm+qpxP+a2LlBIiOQhD6YHzZPAfp7Cp1/5aV4PyUzzy7lxKZEV
	N0Yk+i78Qo4lXAYh9An7uc768icZRYzIDnlbjAbkU5lOsJ625XpVfghsLgxBFykQbrai
	xzGspFLDTeBVwzJ9qrCIls9hRZg19Qt7jv4Nwewie5ulkLLAfzJUvZav77yGOy5ypEMd
	aO7Q==
MIME-Version: 1.0
X-Received: by 10.66.26.176 with SMTP id m16mr2705853pag.142.1392307887578;
	Thu, 13 Feb 2014 08:11:27 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Thu, 13 Feb 2014 08:11:27 -0800 (PST)
In-Reply-To: <52DCE9FA.6010400@xen.org>
References: <52DCE9FA.6010400@xen.org>
Date: Thu, 13 Feb 2014 16:11:27 +0000
Message-ID: 
From: David Scott 
To: lars.kurth@xen.org
Cc: "xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org"
	,
	"xen-devel@lists.xen.org" 
Subject: Re: [MirageOS-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb
 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3300953338641096782=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============3300953338641096782==
Content-Type: multipart/alternative; boundary=bcaec52994530ea31d04f24bf19a

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

Hi,

I did a tidy-up of the Mirage/XAPI projects at the bottom. I've deleted
some old projects after speaking with their technical contacts (in
particular Jon Ludlam and Jonathan Davies) and I've deleted the networking
one at the end since that work is in progress anyway.

I've had a stab at classifying them as 'GSoC'-friendly or not, mainly based
on difficulty.

Are we still planning to add a Mentor section with photos and bios?

Cheers,
Dave


On Mon, Jan 20, 2014 at 9:18 AM, Lars Kurth  wrote:

> Hi all,
>
> the GSoC application deadline is coming up : Feb 2014. If we want to have
> any chance of getting accepted this year, we ought to get our project list
> into good shape. The project list and how the project and menters present
> themselves has a bigger impact on whether we get accepted than the actual
> application.
>
> Also, I would like to add a mentor section this year: a short bio, what
> the mentor cares about and a picture. This will help make the project list
> more real.
>
> We have *4 weeks* to do this. The bar for GSoC has been getting
> increasingly high. I know, we are tied down with Xen 4.4, but this is
> something you need to do if you want the Xen Project to participate.
>
> a) Please, update http://wiki.xenproject.org/wiki/Xen_Development_Projectsurgently (these need to be in good shape *before* the application). What I
> need you to do is:
> a.1) Remove items that are done
> a.2) Add new work items : we ought to have a few sexy topics on say
> Real-time, mobile and some of the other segments (assuming we can get HW)
> a.3) All project proposals need to be peer reviewed *and* clear ... The
> peer review process for projects we put in place last year worked well, by
> which we had past mentors sign of project proposals that were in good
> enough state.
>
> b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should get
> these listed on the respective other programs. And we should link to these
> from our project page.
>
> Best Regards
> Lars
> P.S.: I will also see whether we can participate as Xen Project under the
> LF GSoC program, but last year there was push-back and I don't expect this
> to change
>
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>



-- 
Dave Scott

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


Hi,

I did a tidy-up of the Mirage/XAPI =
projects at the bottom. I've deleted some old projects after speaking w=
ith their technical contacts (in particular Jon Ludlam and Jonathan Davies)=
 and I've deleted the networking one at the end since that work is in p=
rogress anyway.



I've had a stab at classifying them as 'GSoC=
9;-friendly or not, mainly based on difficulty.

Ar=
e we still planning to add a Mentor section with photos and bios?



Cheers,
Dave


On Mon, Jan 20, 2014 at 9:18 AM, L=
ars Kurth <lars.kurth@xen.org> wrote:


Hi all,



the GSoC application deadline is coming up : Feb 2014. If we want to have a=
ny chance of getting accepted this year, we ought to get our project list i=
nto good shape. The project list and how the project and menters present th=
emselves has a bigger impact on whether we get accepted than the actual app=
lication.




Also, I would like to add a mentor section this year: a short bio, what the=
 mentor cares about and a picture. This will help make the project list mor=
e real.



We have *4 weeks* to do this. The bar for GSoC has been getting increasingl=
y high. I know, we are tied down with Xen 4.4, but this is something you ne=
ed to do if you want the Xen Project to participate.



a) Please, update http://wiki.xenproject.org/wiki/Xen_De=
velopment_Projects urgently (these need to be in good shape *before* th=
e application). What I need you to do is:


a.1) Remove items that are done

a.2) Add new work items : we ought to have a few sexy topics on say Real-ti=
me, mobile and some of the other segments (assuming we can get HW)

a.3) All project proposals need to be peer reviewed *and* clear ... The pee=
r review process for projects we put in place last year worked well, by whi=
ch we had past mentors sign of project proposals that were in good enough s=
tate.




b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should get =
these listed on the respective other programs. And we should link to these =
from our project page.



Best Regards

Lars

P.S.: I will also see whether we can participate as Xen Project under the L=
F GSoC program, but last year there was push-back and I don't expect th=
is to change





_______________________________________________

MirageOS-devel mailing list

Mi=
rageOS-devel@lists.xenproject.org

http://lists.xenproject.org/cgi-bin/mailman/l=
istinfo/mirageos-devel





-- 
Dave Scott



--bcaec52994530ea31d04f24bf19a--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============3300953338641096782==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:11:35 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:11: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 1WDysv-0004R2-2R; Thu, 13 Feb 2014 16:11:33 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDyst-0004Ql-P3
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:11:32 +0000
Received: from [193.109.254.147:49283] by server-5.bemta-14.messagelabs.com id
	D2/91-16688-3BEECF25; Thu, 13 Feb 2014 16:11:31 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1392307887!4154076!1
X-Originating-IP: [209.85.192.178]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_SEX,HTML_20_30,
	HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24663 invoked from network); 13 Feb 2014 16:11:29 -0000
Received: from mail-pd0-f178.google.com (HELO mail-pd0-f178.google.com)
	(209.85.192.178)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 16:11:29 -0000
Received: by mail-pd0-f178.google.com with SMTP id fp1so2016245pdb.9
	for ;
	Thu, 13 Feb 2014 08:11:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=l4q+OojFnRmbuTjY5oVmgFxE0xUQZ0oQjJWFX6YSNwk=;
	b=G889E7CdC4fVg3KEAey8o4Ym6tEwmrEiKp2JrCQjrEp75Nka/+BaCknNm/BmKLrqpj
	mfYbIP/DbTXa3CHLbVCHz6v/Ym8aoXtYexisIG7m5l7LdzLVx7X8TKM0tWV/xVooNS7S
	lTGQ9fOi8hf21QFFIOfm+qpxP+a2LlBIiOQhD6YHzZPAfp7Cp1/5aV4PyUzzy7lxKZEV
	N0Yk+i78Qo4lXAYh9An7uc768icZRYzIDnlbjAbkU5lOsJ625XpVfghsLgxBFykQbrai
	xzGspFLDTeBVwzJ9qrCIls9hRZg19Qt7jv4Nwewie5ulkLLAfzJUvZav77yGOy5ypEMd
	aO7Q==
MIME-Version: 1.0
X-Received: by 10.66.26.176 with SMTP id m16mr2705853pag.142.1392307887578;
	Thu, 13 Feb 2014 08:11:27 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Thu, 13 Feb 2014 08:11:27 -0800 (PST)
In-Reply-To: <52DCE9FA.6010400@xen.org>
References: <52DCE9FA.6010400@xen.org>
Date: Thu, 13 Feb 2014 16:11:27 +0000
Message-ID: 
From: David Scott 
To: lars.kurth@xen.org
Cc: "xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org"
	,
	"xen-devel@lists.xen.org" 
Subject: Re: [MirageOS-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb
 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3300953338641096782=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============3300953338641096782==
Content-Type: multipart/alternative; boundary=bcaec52994530ea31d04f24bf19a

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

Hi,

I did a tidy-up of the Mirage/XAPI projects at the bottom. I've deleted
some old projects after speaking with their technical contacts (in
particular Jon Ludlam and Jonathan Davies) and I've deleted the networking
one at the end since that work is in progress anyway.

I've had a stab at classifying them as 'GSoC'-friendly or not, mainly based
on difficulty.

Are we still planning to add a Mentor section with photos and bios?

Cheers,
Dave


On Mon, Jan 20, 2014 at 9:18 AM, Lars Kurth  wrote:

> Hi all,
>
> the GSoC application deadline is coming up : Feb 2014. If we want to have
> any chance of getting accepted this year, we ought to get our project list
> into good shape. The project list and how the project and menters present
> themselves has a bigger impact on whether we get accepted than the actual
> application.
>
> Also, I would like to add a mentor section this year: a short bio, what
> the mentor cares about and a picture. This will help make the project list
> more real.
>
> We have *4 weeks* to do this. The bar for GSoC has been getting
> increasingly high. I know, we are tied down with Xen 4.4, but this is
> something you need to do if you want the Xen Project to participate.
>
> a) Please, update http://wiki.xenproject.org/wiki/Xen_Development_Projectsurgently (these need to be in good shape *before* the application). What I
> need you to do is:
> a.1) Remove items that are done
> a.2) Add new work items : we ought to have a few sexy topics on say
> Real-time, mobile and some of the other segments (assuming we can get HW)
> a.3) All project proposals need to be peer reviewed *and* clear ... The
> peer review process for projects we put in place last year worked well, by
> which we had past mentors sign of project proposals that were in good
> enough state.
>
> b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should get
> these listed on the respective other programs. And we should link to these
> from our project page.
>
> Best Regards
> Lars
> P.S.: I will also see whether we can participate as Xen Project under the
> LF GSoC program, but last year there was push-back and I don't expect this
> to change
>
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>



-- 
Dave Scott

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


Hi,

I did a tidy-up of the Mirage/XAPI =
projects at the bottom. I've deleted some old projects after speaking w=
ith their technical contacts (in particular Jon Ludlam and Jonathan Davies)=
 and I've deleted the networking one at the end since that work is in p=
rogress anyway.



I've had a stab at classifying them as 'GSoC=
9;-friendly or not, mainly based on difficulty.

Ar=
e we still planning to add a Mentor section with photos and bios?



Cheers,
Dave


On Mon, Jan 20, 2014 at 9:18 AM, L=
ars Kurth <lars.kurth@xen.org> wrote:


Hi all,



the GSoC application deadline is coming up : Feb 2014. If we want to have a=
ny chance of getting accepted this year, we ought to get our project list i=
nto good shape. The project list and how the project and menters present th=
emselves has a bigger impact on whether we get accepted than the actual app=
lication.




Also, I would like to add a mentor section this year: a short bio, what the=
 mentor cares about and a picture. This will help make the project list mor=
e real.



We have *4 weeks* to do this. The bar for GSoC has been getting increasingl=
y high. I know, we are tied down with Xen 4.4, but this is something you ne=
ed to do if you want the Xen Project to participate.



a) Please, update http://wiki.xenproject.org/wiki/Xen_De=
velopment_Projects urgently (these need to be in good shape *before* th=
e application). What I need you to do is:


a.1) Remove items that are done

a.2) Add new work items : we ought to have a few sexy topics on say Real-ti=
me, mobile and some of the other segments (assuming we can get HW)

a.3) All project proposals need to be peer reviewed *and* clear ... The pee=
r review process for projects we put in place last year worked well, by whi=
ch we had past mentors sign of project proposals that were in good enough s=
tate.




b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should get =
these listed on the respective other programs. And we should link to these =
from our project page.



Best Regards

Lars

P.S.: I will also see whether we can participate as Xen Project under the L=
F GSoC program, but last year there was push-back and I don't expect th=
is to change





_______________________________________________

MirageOS-devel mailing list

Mi=
rageOS-devel@lists.xenproject.org

http://lists.xenproject.org/cgi-bin/mailman/l=
istinfo/mirageos-devel





-- 
Dave Scott



--bcaec52994530ea31d04f24bf19a--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============3300953338641096782==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:12:12 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:12:12 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDytY-0004WP-Fc; Thu, 13 Feb 2014 16: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 1WDytX-0004Vx-A4
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:12:11 +0000
Received: from [85.158.137.68:28884] by server-1.bemta-3.messagelabs.com id
	88/0B-17293-ADEECF25; Thu, 13 Feb 2014 16:12:10 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-12.tower-31.messagelabs.com!1392307927!691592!1
X-Originating-IP: [209.85.215.179]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24375 invoked from network); 13 Feb 2014 16:12:07 -0000
Received: from mail-ea0-f179.google.com (HELO mail-ea0-f179.google.com)
	(209.85.215.179)
	by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 16:12:07 -0000
Received: by mail-ea0-f179.google.com with SMTP id q10so4619579ead.10
	for ;
	Thu, 13 Feb 2014 08:12:07 -0800 (PST)
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:to:mime-version;
	bh=kxyzXxBesbfagr2xOquushRXvu7pxoYJGKFnfxD0sxw=;
	b=kBKsCK+uLx7HBLNLbFw/hKur7UTSNYwfy2QjJAI3D8b/iz1FtkJHpttJ8Ze1wwixnc
	EfpDYzqo9fCQDt/t8G27uAYGq00bFhDyCrrHr3UTmSBhkdeil3qz79kFHY9/wO9KQn3/
	ipoY0jYUsnaqECpFHDueggjVOVr2FYFlndcMCVP8oXpXZUO+rvZfXwPjX1hQiR0wgAHB
	tPWvaSa3V33ulqxq5tJe2WKckBnj8MPfOxiUF6vY6iM8SJV89XwRGoI2bc69xWw1OouF
	4+tiOd2HAhPMX9IUPEU2bLul3VnbzqEAmoAMAdKeuQsVHU/+iIsgJg5XecXk4pwL8CUr
	AcWw==
X-Gm-Message-State: ALoCoQmF+huM5dIz+W0i5zmcYA0dwIBgg8B8zceYoLFCGdmWCsyB4AAmVkxwYdP+MQqPuUr9UItb
X-Received: by 10.14.110.68 with SMTP id t44mr2865867eeg.74.1392307927332;
	Thu, 13 Feb 2014 08:12:07 -0800 (PST)
Received: from [10.0.3.30] ([62.205.6.170])
	by mx.google.com with ESMTPSA id j41sm8525874eey.15.2014.02.13.08.12.03
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 13 Feb 2014 08:12:05 -0800 (PST)
From: Julian Chesterfield 
Date: Thu, 13 Feb 2014 16:12:04 +0000
Message-Id: 
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Subject: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi,

Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.

- J
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:12:12 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:12:12 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDytY-0004WP-Fc; Thu, 13 Feb 2014 16: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 1WDytX-0004Vx-A4
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:12:11 +0000
Received: from [85.158.137.68:28884] by server-1.bemta-3.messagelabs.com id
	88/0B-17293-ADEECF25; Thu, 13 Feb 2014 16:12:10 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-12.tower-31.messagelabs.com!1392307927!691592!1
X-Originating-IP: [209.85.215.179]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24375 invoked from network); 13 Feb 2014 16:12:07 -0000
Received: from mail-ea0-f179.google.com (HELO mail-ea0-f179.google.com)
	(209.85.215.179)
	by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 16:12:07 -0000
Received: by mail-ea0-f179.google.com with SMTP id q10so4619579ead.10
	for ;
	Thu, 13 Feb 2014 08:12:07 -0800 (PST)
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:to:mime-version;
	bh=kxyzXxBesbfagr2xOquushRXvu7pxoYJGKFnfxD0sxw=;
	b=kBKsCK+uLx7HBLNLbFw/hKur7UTSNYwfy2QjJAI3D8b/iz1FtkJHpttJ8Ze1wwixnc
	EfpDYzqo9fCQDt/t8G27uAYGq00bFhDyCrrHr3UTmSBhkdeil3qz79kFHY9/wO9KQn3/
	ipoY0jYUsnaqECpFHDueggjVOVr2FYFlndcMCVP8oXpXZUO+rvZfXwPjX1hQiR0wgAHB
	tPWvaSa3V33ulqxq5tJe2WKckBnj8MPfOxiUF6vY6iM8SJV89XwRGoI2bc69xWw1OouF
	4+tiOd2HAhPMX9IUPEU2bLul3VnbzqEAmoAMAdKeuQsVHU/+iIsgJg5XecXk4pwL8CUr
	AcWw==
X-Gm-Message-State: ALoCoQmF+huM5dIz+W0i5zmcYA0dwIBgg8B8zceYoLFCGdmWCsyB4AAmVkxwYdP+MQqPuUr9UItb
X-Received: by 10.14.110.68 with SMTP id t44mr2865867eeg.74.1392307927332;
	Thu, 13 Feb 2014 08:12:07 -0800 (PST)
Received: from [10.0.3.30] ([62.205.6.170])
	by mx.google.com with ESMTPSA id j41sm8525874eey.15.2014.02.13.08.12.03
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 13 Feb 2014 08:12:05 -0800 (PST)
From: Julian Chesterfield 
Date: Thu, 13 Feb 2014 16:12:04 +0000
Message-Id: 
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Subject: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi,

Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.

- J
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:25:44 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:25: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 1WDz6c-0005Bw-Jf; Thu, 13 Feb 2014 16:25:42 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDz6b-0005Bn-UN
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:25:42 +0000
Received: from [85.158.137.68:31411] by server-10.bemta-3.messagelabs.com id
	DB/FF-07302-502FCF25; Thu, 13 Feb 2014 16:25:41 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-11.tower-31.messagelabs.com!1392308740!1703039!1
X-Originating-IP: [131.111.8.132]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24251 invoked from network); 13 Feb 2014 16:25:40 -0000
Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk)
	(131.111.8.132)
	by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 13 Feb 2014 16:25:40 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from dhcp-172-17-183-177.eduroam.lapwing.private.cam.ac.uk
	([172.17.183.177]:60522)
	by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WDz6a-00006E-0W (Exim 4.82_3-c0e5623)
	(return-path ); Thu, 13 Feb 2014 16:25:40 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: 
Date: Thu, 13 Feb 2014 16:25:39 +0000
Message-Id: <2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
References: 
To: Julian Chesterfield 
X-Mailer: Apple Mail (2.1510)
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

It sounds like what you're after is the ability to make your own custom site based on html files. Am I right?  

I don't think there are any instructions for how to adapt the mirage-www site but the more general case is something we're working towards.  It's the kind of thing I need before I can begin migrating my existing sites [1] and there's also an issue on the tracker about it [2].

[1] http://lists.xenproject.org/archives/html/mirageos-devel/2014-01/msg00014.html
[2] https://github.com/mirage/mirage/issues/214

Amir

On 13 Feb 2014, at 16:12, Julian Chesterfield  wrote:

> Hi,
> 
> Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.
> 
> - J
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:25:44 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:25: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 1WDz6c-0005Bw-Jf; Thu, 13 Feb 2014 16:25:42 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDz6b-0005Bn-UN
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:25:42 +0000
Received: from [85.158.137.68:31411] by server-10.bemta-3.messagelabs.com id
	DB/FF-07302-502FCF25; Thu, 13 Feb 2014 16:25:41 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-11.tower-31.messagelabs.com!1392308740!1703039!1
X-Originating-IP: [131.111.8.132]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24251 invoked from network); 13 Feb 2014 16:25:40 -0000
Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk)
	(131.111.8.132)
	by server-11.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 13 Feb 2014 16:25:40 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from dhcp-172-17-183-177.eduroam.lapwing.private.cam.ac.uk
	([172.17.183.177]:60522)
	by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WDz6a-00006E-0W (Exim 4.82_3-c0e5623)
	(return-path ); Thu, 13 Feb 2014 16:25:40 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: 
Date: Thu, 13 Feb 2014 16:25:39 +0000
Message-Id: <2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
References: 
To: Julian Chesterfield 
X-Mailer: Apple Mail (2.1510)
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

It sounds like what you're after is the ability to make your own custom site based on html files. Am I right?  

I don't think there are any instructions for how to adapt the mirage-www site but the more general case is something we're working towards.  It's the kind of thing I need before I can begin migrating my existing sites [1] and there's also an issue on the tracker about it [2].

[1] http://lists.xenproject.org/archives/html/mirageos-devel/2014-01/msg00014.html
[2] https://github.com/mirage/mirage/issues/214

Amir

On 13 Feb 2014, at 16:12, Julian Chesterfield  wrote:

> Hi,
> 
> Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.
> 
> - J
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:34:16 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:34:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDzEt-0005tw-WB; Thu, 13 Feb 2014 16:34:15 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDzEs-0005tr-PW
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:34:14 +0000
Received: from [85.158.139.211:19157] by server-6.bemta-5.messagelabs.com id
	26/A8-14342-604FCF25; Thu, 13 Feb 2014 16:34:14 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-5.tower-206.messagelabs.com!1392309252!3649924!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5517 invoked from network); 13 Feb 2014 16:34:12 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-5.tower-206.messagelabs.com with SMTP;
	13 Feb 2014 16:34:12 -0000
Received: (qmail 20591 invoked by uid 634); 13 Feb 2014 16:34:12 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 13 Feb 2014 16:34:08 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
Date: Thu, 13 Feb 2014 16:34:06 +0000
Message-Id: <4D959CB8-BBA9-4A61-9C25-17D9D9FB5C13@recoil.org>
References: 
	<2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
To: Amir M Chaudhry 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Julian, I've put a quick example of a static website into this pull request:
https://github.com/mirage/mirage-skeleton/pull/28

Just cd static_website, put your files into htdocs/, and let me know it goes (see the README.md; you can build it with DHCP which is probably what you want).

-anil

On 13 Feb 2014, at 16:25, Amir Chaudhry  wrote:

> It sounds like what you're after is the ability to make your own custom site based on html files. Am I right?  
> 
> I don't think there are any instructions for how to adapt the mirage-www site but the more general case is something we're working towards.  It's the kind of thing I need before I can begin migrating my existing sites [1] and there's also an issue on the tracker about it [2].
> 
> [1] http://lists.xenproject.org/archives/html/mirageos-devel/2014-01/msg00014.html
> [2] https://github.com/mirage/mirage/issues/214
> 
> Amir
> 
> On 13 Feb 2014, at 16:12, Julian Chesterfield  wrote:
> 
>> Hi,
>> 
>> Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.
>> 
>> - J
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:34:16 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:34:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDzEt-0005tw-WB; Thu, 13 Feb 2014 16:34:15 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDzEs-0005tr-PW
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:34:14 +0000
Received: from [85.158.139.211:19157] by server-6.bemta-5.messagelabs.com id
	26/A8-14342-604FCF25; Thu, 13 Feb 2014 16:34:14 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-5.tower-206.messagelabs.com!1392309252!3649924!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5517 invoked from network); 13 Feb 2014 16:34:12 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-5.tower-206.messagelabs.com with SMTP;
	13 Feb 2014 16:34:12 -0000
Received: (qmail 20591 invoked by uid 634); 13 Feb 2014 16:34:12 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 13 Feb 2014 16:34:08 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
Date: Thu, 13 Feb 2014 16:34:06 +0000
Message-Id: <4D959CB8-BBA9-4A61-9C25-17D9D9FB5C13@recoil.org>
References: 
	<2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
To: Amir M Chaudhry 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Julian, I've put a quick example of a static website into this pull request:
https://github.com/mirage/mirage-skeleton/pull/28

Just cd static_website, put your files into htdocs/, and let me know it goes (see the README.md; you can build it with DHCP which is probably what you want).

-anil

On 13 Feb 2014, at 16:25, Amir Chaudhry  wrote:

> It sounds like what you're after is the ability to make your own custom site based on html files. Am I right?  
> 
> I don't think there are any instructions for how to adapt the mirage-www site but the more general case is something we're working towards.  It's the kind of thing I need before I can begin migrating my existing sites [1] and there's also an issue on the tracker about it [2].
> 
> [1] http://lists.xenproject.org/archives/html/mirageos-devel/2014-01/msg00014.html
> [2] https://github.com/mirage/mirage/issues/214
> 
> Amir
> 
> On 13 Feb 2014, at 16:12, Julian Chesterfield  wrote:
> 
>> Hi,
>> 
>> Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.
>> 
>> - J
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:34:25 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:34: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 1WDzF3-0005ur-29; Thu, 13 Feb 2014 16:34:25 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDzF2-0005uh-H8
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:34:24 +0000
Received: from [85.158.139.211:30483] by server-12.bemta-5.messagelabs.com id
	D1/E4-15415-F04FCF25; Thu, 13 Feb 2014 16:34:23 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-10.tower-206.messagelabs.com!1392309262!3722466!1
X-Originating-IP: [93.95.15.169]
X-SpamReason: No, hits=1.0 required=7.0 tests=BODY_RANDOM_LONG,
	MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8565 invoked from network); 13 Feb 2014 16:34:23 -0000
Received: from engine01-20433-1.icritical.com (HELO
	engine01-20433-1.icritical.com) (93.95.15.169)
	by server-10.tower-206.messagelabs.com with SMTP;
	13 Feb 2014 16:34:23 -0000
Received: (qmail 3665 invoked from network); 13 Feb 2014 16:34:19 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-1.icritical.com with SMTP; 13 Feb 2014 16:34:19 -0000
Received: from engine01-20433-1.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 03425-06 for ;
	Thu, 13 Feb 2014 16:34:19 +0000 (GMT)
Received: (qmail 829 invoked by uid 599); 13 Feb 2014 16:31:52 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP;
	Thu, 13 Feb 2014 16:31:52 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WDzC9-0003DG-0G; Thu, 13 Feb 2014 16:31:25 +0000
From: Richard Mortier 
To: Amir Chaudhry , Julian Chesterfield
	
Date: Thu, 13 Feb 2014 16:31:23 +0000
Thread-Topic: [MirageOS-devel] Building a custom web hosting mirage image
Thread-Index: Ac8o2Qjv9GaXKtjhTAqUiXD9HaMm7w==
Message-ID: 
References: 
	<2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
In-Reply-To: <2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

there's a mirage-skeleton "static_website" example too which needs updating.

the short answer is probably that, as well as changing content, you need to update the relevant .ml file that points to the content (so iirc, src/wiki.ml has a list that indexes all the wiki entries, src/blog.ml has a list that indexes all the blog entries, etc)

On 13 Feb 2014, at 16:25, Amir Chaudhry  wrote:

> It sounds like what you're after is the ability to make your own custom site based on html files. Am I right?  
> 
> I don't think there are any instructions for how to adapt the mirage-www site but the more general case is something we're working towards.  It's the kind of thing I need before I can begin migrating my existing sites [1] and there's also an issue on the tracker about it [2].
> 
> [1] http://lists.xenproject.org/archives/html/mirageos-devel/2014-01/msg00014.html
> [2] https://github.com/mirage/mirage/issues/214
> 
> Amir
> 
> On 13 Feb 2014, at 16:12, Julian Chesterfield  wrote:
> 
>> Hi,
>> 
>> Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.
>> 
>> - J
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 16:34:25 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 16:34: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 1WDzF3-0005ur-29; Thu, 13 Feb 2014 16:34:25 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WDzF2-0005uh-H8
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 16:34:24 +0000
Received: from [85.158.139.211:30483] by server-12.bemta-5.messagelabs.com id
	D1/E4-15415-F04FCF25; Thu, 13 Feb 2014 16:34:23 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-10.tower-206.messagelabs.com!1392309262!3722466!1
X-Originating-IP: [93.95.15.169]
X-SpamReason: No, hits=1.0 required=7.0 tests=BODY_RANDOM_LONG,
	MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8565 invoked from network); 13 Feb 2014 16:34:23 -0000
Received: from engine01-20433-1.icritical.com (HELO
	engine01-20433-1.icritical.com) (93.95.15.169)
	by server-10.tower-206.messagelabs.com with SMTP;
	13 Feb 2014 16:34:23 -0000
Received: (qmail 3665 invoked from network); 13 Feb 2014 16:34:19 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-1.icritical.com with SMTP; 13 Feb 2014 16:34:19 -0000
Received: from engine01-20433-1.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 03425-06 for ;
	Thu, 13 Feb 2014 16:34:19 +0000 (GMT)
Received: (qmail 829 invoked by uid 599); 13 Feb 2014 16:31:52 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP;
	Thu, 13 Feb 2014 16:31:52 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WDzC9-0003DG-0G; Thu, 13 Feb 2014 16:31:25 +0000
From: Richard Mortier 
To: Amir Chaudhry , Julian Chesterfield
	
Date: Thu, 13 Feb 2014 16:31:23 +0000
Thread-Topic: [MirageOS-devel] Building a custom web hosting mirage image
Thread-Index: Ac8o2Qjv9GaXKtjhTAqUiXD9HaMm7w==
Message-ID: 
References: 
	<2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
In-Reply-To: <2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

there's a mirage-skeleton "static_website" example too which needs updating.

the short answer is probably that, as well as changing content, you need to update the relevant .ml file that points to the content (so iirc, src/wiki.ml has a list that indexes all the wiki entries, src/blog.ml has a list that indexes all the blog entries, etc)

On 13 Feb 2014, at 16:25, Amir Chaudhry  wrote:

> It sounds like what you're after is the ability to make your own custom site based on html files. Am I right?  
> 
> I don't think there are any instructions for how to adapt the mirage-www site but the more general case is something we're working towards.  It's the kind of thing I need before I can begin migrating my existing sites [1] and there's also an issue on the tracker about it [2].
> 
> [1] http://lists.xenproject.org/archives/html/mirageos-devel/2014-01/msg00014.html
> [2] https://github.com/mirage/mirage/issues/214
> 
> Amir
> 
> On 13 Feb 2014, at 16:12, Julian Chesterfield  wrote:
> 
>> Hi,
>> 
>> Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.
>> 
>> - J
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 17:09:24 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 17:09: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 1WDzmt-0007ai-8p; Thu, 13 Feb 2014 17:09:23 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDzmr-0007aU-Po
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 17:09:22 +0000
Received: from [85.158.137.68:41242] by server-8.bemta-3.messagelabs.com id
	96/1D-16039-04CFCF25; Thu, 13 Feb 2014 17:09:20 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-3.tower-31.messagelabs.com!1392311359!1724564!1
X-Originating-IP: [74.125.83.49]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21994 invoked from network); 13 Feb 2014 17:09:19 -0000
Received: from mail-ee0-f49.google.com (HELO mail-ee0-f49.google.com)
	(74.125.83.49)
	by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 17:09:19 -0000
Received: by mail-ee0-f49.google.com with SMTP id d17so5129174eek.22
	for ;
	Thu, 13 Feb 2014 09:09:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:mime-version:content-type:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id:references
	:to; bh=mOv7zv0gsIZ1MuTqGaywdVPWe/yUsb2Q+FKQch0t7hs=;
	b=bUhNgc5UoL1FdN4kOIynsRA9YoW3mbbR81kM4oNK8mjnzv+LXwWssAaEGLTYsjj00R
	bgk/0mkbCUWjCdOlYYAysbTZEAwI6hg73FjPdRiifzfHvNPZYYDIb/2oxKjrmQkMn3rT
	j80GxJ/3eZWBPpM6Ro4BnGm61IPIOKpTrkJ4CgbhahCbLA/2kIyo/qWqIl2Y0khyWBzX
	FImfcEtaX27dg8NIkZ+t4urdQm5BFsRE8r3mW6VuxbKSkf0vIj4ZHlETE6AjIlATu0ct
	Szfu3j3yyVhvTR1HrBLleEFdiS6BQPuE59KTYwwYuGJy6Iu0xaywA/5Kh50YsLf3d1Mg
	u8tA==
X-Gm-Message-State: ALoCoQl6jz3uIiW7JRzF7sINFv/0GdCMGGadVhg61/rI/NNIncMwjqXqufbyqg3J7TkUpVKGvMPB
X-Received: by 10.15.63.6 with SMTP id l6mr722233eex.112.1392311359063;
	Thu, 13 Feb 2014 09:09:19 -0800 (PST)
Received: from [10.0.3.30] ([62.205.6.170])
	by mx.google.com with ESMTPSA id f45sm9075017eeg.5.2014.02.13.09.09.16
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 13 Feb 2014 09:09:17 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
From: Julian Chesterfield 
In-Reply-To: <4D959CB8-BBA9-4A61-9C25-17D9D9FB5C13@recoil.org>
Date: Thu, 13 Feb 2014 17:09:16 +0000
Message-Id: 
References: 
	<2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
	<4D959CB8-BBA9-4A61-9C25-17D9D9FB5C13@recoil.org>
To: Anil Madhavapeddy 
X-Mailer: Apple Mail (2.1283)
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Yep, that is working:

http://212.44.45.219:8080

So the missing link is the .ml as Richard pointed out. Thanks Guys!

- J

On 13 Feb 2014, at 16:34, Anil Madhavapeddy wrote:

> Julian, I've put a quick example of a static website into this pull request:
> https://github.com/mirage/mirage-skeleton/pull/28
> 
> Just cd static_website, put your files into htdocs/, and let me know it goes (see the README.md; you can build it with DHCP which is probably what you want).
> 
> -anil
> 
> On 13 Feb 2014, at 16:25, Amir Chaudhry  wrote:
> 
>> It sounds like what you're after is the ability to make your own custom site based on html files. Am I right?  
>> 
>> I don't think there are any instructions for how to adapt the mirage-www site but the more general case is something we're working towards.  It's the kind of thing I need before I can begin migrating my existing sites [1] and there's also an issue on the tracker about it [2].
>> 
>> [1] http://lists.xenproject.org/archives/html/mirageos-devel/2014-01/msg00014.html
>> [2] https://github.com/mirage/mirage/issues/214
>> 
>> Amir
>> 
>> On 13 Feb 2014, at 16:12, Julian Chesterfield  wrote:
>> 
>>> Hi,
>>> 
>>> Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.
>>> 
>>> - J
>>> _______________________________________________
>>> MirageOS-devel mailing list
>>> MirageOS-devel@lists.xenproject.org
>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
>> 
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 17:09:24 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 17:09: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 1WDzmt-0007ai-8p; Thu, 13 Feb 2014 17:09:23 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDzmr-0007aU-Po
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 17:09:22 +0000
Received: from [85.158.137.68:41242] by server-8.bemta-3.messagelabs.com id
	96/1D-16039-04CFCF25; Thu, 13 Feb 2014 17:09:20 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-3.tower-31.messagelabs.com!1392311359!1724564!1
X-Originating-IP: [74.125.83.49]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21994 invoked from network); 13 Feb 2014 17:09:19 -0000
Received: from mail-ee0-f49.google.com (HELO mail-ee0-f49.google.com)
	(74.125.83.49)
	by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 17:09:19 -0000
Received: by mail-ee0-f49.google.com with SMTP id d17so5129174eek.22
	for ;
	Thu, 13 Feb 2014 09:09:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:mime-version:content-type:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id:references
	:to; bh=mOv7zv0gsIZ1MuTqGaywdVPWe/yUsb2Q+FKQch0t7hs=;
	b=bUhNgc5UoL1FdN4kOIynsRA9YoW3mbbR81kM4oNK8mjnzv+LXwWssAaEGLTYsjj00R
	bgk/0mkbCUWjCdOlYYAysbTZEAwI6hg73FjPdRiifzfHvNPZYYDIb/2oxKjrmQkMn3rT
	j80GxJ/3eZWBPpM6Ro4BnGm61IPIOKpTrkJ4CgbhahCbLA/2kIyo/qWqIl2Y0khyWBzX
	FImfcEtaX27dg8NIkZ+t4urdQm5BFsRE8r3mW6VuxbKSkf0vIj4ZHlETE6AjIlATu0ct
	Szfu3j3yyVhvTR1HrBLleEFdiS6BQPuE59KTYwwYuGJy6Iu0xaywA/5Kh50YsLf3d1Mg
	u8tA==
X-Gm-Message-State: ALoCoQl6jz3uIiW7JRzF7sINFv/0GdCMGGadVhg61/rI/NNIncMwjqXqufbyqg3J7TkUpVKGvMPB
X-Received: by 10.15.63.6 with SMTP id l6mr722233eex.112.1392311359063;
	Thu, 13 Feb 2014 09:09:19 -0800 (PST)
Received: from [10.0.3.30] ([62.205.6.170])
	by mx.google.com with ESMTPSA id f45sm9075017eeg.5.2014.02.13.09.09.16
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 13 Feb 2014 09:09:17 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
From: Julian Chesterfield 
In-Reply-To: <4D959CB8-BBA9-4A61-9C25-17D9D9FB5C13@recoil.org>
Date: Thu, 13 Feb 2014 17:09:16 +0000
Message-Id: 
References: 
	<2E0B8504-CFEE-4663-806B-74C5C7E3310A@cam.ac.uk>
	<4D959CB8-BBA9-4A61-9C25-17D9D9FB5C13@recoil.org>
To: Anil Madhavapeddy 
X-Mailer: Apple Mail (2.1283)
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Building a custom web hosting mirage image
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Yep, that is working:

http://212.44.45.219:8080

So the missing link is the .ml as Richard pointed out. Thanks Guys!

- J

On 13 Feb 2014, at 16:34, Anil Madhavapeddy wrote:

> Julian, I've put a quick example of a static website into this pull request:
> https://github.com/mirage/mirage-skeleton/pull/28
> 
> Just cd static_website, put your files into htdocs/, and let me know it goes (see the README.md; you can build it with DHCP which is probably what you want).
> 
> -anil
> 
> On 13 Feb 2014, at 16:25, Amir Chaudhry  wrote:
> 
>> It sounds like what you're after is the ability to make your own custom site based on html files. Am I right?  
>> 
>> I don't think there are any instructions for how to adapt the mirage-www site but the more general case is something we're working towards.  It's the kind of thing I need before I can begin migrating my existing sites [1] and there's also an issue on the tracker about it [2].
>> 
>> [1] http://lists.xenproject.org/archives/html/mirageos-devel/2014-01/msg00014.html
>> [2] https://github.com/mirage/mirage/issues/214
>> 
>> Amir
>> 
>> On 13 Feb 2014, at 16:12, Julian Chesterfield  wrote:
>> 
>>> Hi,
>>> 
>>> Are there any instructions on how to configure custom html content and build a mirage-www xen image? I've tried removing the files and tmpl directory contents in the mirage-www repo and replacing with a simple html file but the image fails to boot.
>>> 
>>> - J
>>> _______________________________________________
>>> MirageOS-devel mailing list
>>> MirageOS-devel@lists.xenproject.org
>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
>> 
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 19:41:21 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 19:41: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 1WE29s-0005U2-DJ; Thu, 13 Feb 2014 19:41:16 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WE29r-0005Tp-6j
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 19:41:15 +0000
Received: from [85.158.143.35:19370] by server-3.bemta-4.messagelabs.com id
	EF/E9-11539-ADF1DF25; Thu, 13 Feb 2014 19:41:14 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-2.tower-21.messagelabs.com!1392320472!5528260!1
X-Originating-IP: [209.85.216.179]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26162 invoked from network); 13 Feb 2014 19:41:13 -0000
Received: from mail-qc0-f179.google.com (HELO mail-qc0-f179.google.com)
	(209.85.216.179)
	by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 19:41:13 -0000
Received: by mail-qc0-f179.google.com with SMTP id e16so18861145qcx.10
	for ;
	Thu, 13 Feb 2014 11:41:12 -0800 (PST)
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=lYAYpFKhl6joCCiGXpFeqvMXEmxZf/t9Vro3uQGMLZ4=;
	b=vXCzvU1pNOUDLc4I0sh9SDZas2q1FTiApq78sCD1HLxU6nbb29eZe5mp7xUlS1xek6
	5jFaSc2ZeDOjt/sTOdQQlAvjjfCWHe2eqOnPwvJgN/nF4wG5mZHKWB41pRhF7KEMo1V2
	iYv47AlshuhpgE4JcR7STIG4txuCANjRKv7BR5V2Ige7C/jAWG1YX7Z0pQlimr0DWcLR
	94w1jGnrnwBnyU4dareBHWVD2jSL30SlJDFNUT6vA8Gwl44pBNFkBUp7LwUfvfMYhYUj
	QT2p4mkG8tlkzD6UlHZOgCpM/EBjaKb9vm2rQLGbr3rirsfWqbPK+VRMsfcFIDQDBrbQ
	R3pA==
X-Received: by 10.140.38.168 with SMTP id t37mr5368745qgt.33.1392320472454;
	Thu, 13 Feb 2014 11:41:12 -0800 (PST)
Received: from [172.16.26.11] ([63.110.51.11])
	by mx.google.com with ESMTPSA id u4sm8144320qai.21.2014.02.13.11.41.10
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 13 Feb 2014 11:41:11 -0800 (PST)
Message-ID: <52FD1FD5.9040009@xen.org>
Date: Thu, 13 Feb 2014 19:41:09 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: David Scott 
References: <52DCE9FA.6010400@xen.org>
	
In-Reply-To: 
Cc: "xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org"
	,
	"xen-devel@lists.xen.org" 
Subject: Re: [MirageOS-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb
 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 13/02/2014 16:11, David Scott wrote:
> Hi,
>
> I did a tidy-up of the Mirage/XAPI projects at the bottom. I've 
> deleted some old projects after speaking with their technical contacts 
> (in particular Jon Ludlam and Jonathan Davies) and I've deleted the 
> networking one at the end since that work is in progress anyway.
Thank you!
>
> I've had a stab at classifying them as 'GSoC'-friendly or not, mainly 
> based on difficulty.
>
> Are we still planning to add a Mentor section with photos and bios?
>
Too late now.

I will take the page and clone it and put in the application this 
afternoon pacific time

Regards
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 13 19:41:21 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 13 Feb 2014 19:41: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 1WE29s-0005U2-DJ; Thu, 13 Feb 2014 19:41:16 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WE29r-0005Tp-6j
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 19:41:15 +0000
Received: from [85.158.143.35:19370] by server-3.bemta-4.messagelabs.com id
	EF/E9-11539-ADF1DF25; Thu, 13 Feb 2014 19:41:14 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-2.tower-21.messagelabs.com!1392320472!5528260!1
X-Originating-IP: [209.85.216.179]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26162 invoked from network); 13 Feb 2014 19:41:13 -0000
Received: from mail-qc0-f179.google.com (HELO mail-qc0-f179.google.com)
	(209.85.216.179)
	by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 19:41:13 -0000
Received: by mail-qc0-f179.google.com with SMTP id e16so18861145qcx.10
	for ;
	Thu, 13 Feb 2014 11:41:12 -0800 (PST)
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=lYAYpFKhl6joCCiGXpFeqvMXEmxZf/t9Vro3uQGMLZ4=;
	b=vXCzvU1pNOUDLc4I0sh9SDZas2q1FTiApq78sCD1HLxU6nbb29eZe5mp7xUlS1xek6
	5jFaSc2ZeDOjt/sTOdQQlAvjjfCWHe2eqOnPwvJgN/nF4wG5mZHKWB41pRhF7KEMo1V2
	iYv47AlshuhpgE4JcR7STIG4txuCANjRKv7BR5V2Ige7C/jAWG1YX7Z0pQlimr0DWcLR
	94w1jGnrnwBnyU4dareBHWVD2jSL30SlJDFNUT6vA8Gwl44pBNFkBUp7LwUfvfMYhYUj
	QT2p4mkG8tlkzD6UlHZOgCpM/EBjaKb9vm2rQLGbr3rirsfWqbPK+VRMsfcFIDQDBrbQ
	R3pA==
X-Received: by 10.140.38.168 with SMTP id t37mr5368745qgt.33.1392320472454;
	Thu, 13 Feb 2014 11:41:12 -0800 (PST)
Received: from [172.16.26.11] ([63.110.51.11])
	by mx.google.com with ESMTPSA id u4sm8144320qai.21.2014.02.13.11.41.10
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 13 Feb 2014 11:41:11 -0800 (PST)
Message-ID: <52FD1FD5.9040009@xen.org>
Date: Thu, 13 Feb 2014 19:41:09 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: David Scott 
References: <52DCE9FA.6010400@xen.org>
	
In-Reply-To: 
Cc: "xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org"
	,
	"xen-devel@lists.xen.org" 
Subject: Re: [MirageOS-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb
 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 13/02/2014 16:11, David Scott wrote:
> Hi,
>
> I did a tidy-up of the Mirage/XAPI projects at the bottom. I've 
> deleted some old projects after speaking with their technical contacts 
> (in particular Jon Ludlam and Jonathan Davies) and I've deleted the 
> networking one at the end since that work is in progress anyway.
Thank you!
>
> I've had a stab at classifying them as 'GSoC'-friendly or not, mainly 
> based on difficulty.
>
> Are we still planning to add a Mentor section with photos and bios?
>
Too late now.

I will take the page and clone it and put in the application this 
afternoon pacific time

Regards
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 01:36:04 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 01:36:04 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WE7hB-0002d2-9f; Fri, 14 Feb 2014 01:36:01 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WE7h9-0002cp-6P
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 01:35:59 +0000
Received: from [85.158.137.68:37858] by server-15.bemta-3.messagelabs.com id
	5D/ED-19263-EF27DF25; Fri, 14 Feb 2014 01:35:58 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-11.tower-31.messagelabs.com!1392341755!1778654!1
X-Originating-IP: [209.85.220.52]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32354 invoked from network); 14 Feb 2014 01:35:57 -0000
Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com)
	(209.85.220.52)
	by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Feb 2014 01:35:57 -0000
Received: by mail-pa0-f52.google.com with SMTP id bj1so11550640pad.25
	for ;
	Thu, 13 Feb 2014 17:35:55 -0800 (PST)
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=s7tKFqavVPB1HV7+b4u2snGpZHWFX57OK5rpk3WFAaU=;
	b=c8gDqDnmdm96tLE1xu33LtEQ1jEEEOLegH8XjuCV/HQiQ+QmYgCWFPq0YUvt6fo9/h
	fTzcTNfjqn8KjXu4NZ9lFQoZl5H1+AW6CftHRNcwUGOLSoPk3GqDa9nCkQHdKaatfDRu
	6KLdqf8YeoH6ahL9EqFMLxjCUctG1gwu+8EpnWjra2qk7UxVvtxhUAW2sXsvVB/YqpV2
	QCAdPNqUgp7Ppp9PRWK5jdEJsG9f67uG9f1mTNqu82zcR5V+qIGI1JLy+I4I0KBDM8Bo
	VFoPFRkMLM2cxaqhwzpQtgloA530N2+YnsfsFfTy4d3VWAd8GjVt57nDVPhmSVruv3w/
	opVA==
X-Received: by 10.68.183.228 with SMTP id ep4mr5396873pbc.67.1392341755249;
	Thu, 13 Feb 2014 17:35:55 -0800 (PST)
Received: from [172.16.25.10] ([128.177.190.114])
	by mx.google.com with ESMTPSA id
	si6sm27460169pab.19.2014.02.13.17.35.53 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 13 Feb 2014 17:35:54 -0800 (PST)
Message-ID: <52FD72F8.107@xen.org>
Date: Fri, 14 Feb 2014 01:35:52 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: xen-devel@lists.xen.org, "xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org" 
References: <52DCE9FA.6010400@xen.org>
	<52E7B6AF.3050604@xen.org>	<1391609348.6497.178.camel@kazak.uk.xensource.com>	<52F24D4D.7040004@citrix.com>	<1391611558.23098.2.camel@kazak.uk.xensource.com>	<52F24F5D.7020207@citrix.com>
	<1391611929.23098.6.camel@kazak.uk.xensource.com>
In-Reply-To: <1391611929.23098.6.camel@kazak.uk.xensource.com>
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi all,

I created http://wiki.xen.org/wiki/GSoc_2014 based on the project list

Unless you guys step up, I will move all projects that have no
* level of difficulty
* skills needed
* outcomes
into http://wiki.xen.org/wiki/GSoc_2014#List_of_projects_that_need_more_work

I made a start on this and will do more on the weekend and/or monday. I 
will also sort, such that easy projects come first.

I am about to submit the application in the next two hours

Regards

On 05/02/2014 14:52, Ian Campbell wrote:
> (trimming cc, most people are presumably not interested)
>
> On Wed, 2014-02-05 at 14:49 +0000, Andrew Cooper wrote:
>> On 05/02/14 14:45, Ian Campbell wrote:
>>> On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote:
>>>> On 05/02/14 14:09, Ian Campbell wrote:
>>>>> Andy:
>>>>>
>>>>>        * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
>>>>>          allocations
>>>>>
>>>>>          Sounds too hard for a GSoC to me. Would need fleshing out in any
>>>>>          case.
>>>> Malcolm made a prototype for this on the first day of the Hackathon.  It
>>>> can disappear.
>>> Removed.
>>>
>>>>>        * CPU/RAM/PCI diagram tool
>>>>>
>>>>>          Does this not already exist somewhere?
>>>> Not as far as I (or my ability to google) am aware.
>>>>
>>>> My furrowing into hwloc interacting with Xen and libxc is a start to all
>>>> of this, but it is still very much in my copious free time and there is
>>>> more than enough other work which could be done if someone were interested.
>>> OK, left in place.
>>>
>>> This could conceivably be done under another umbrella such as the Linux
>>> one too, since it seems generic.
>>>
>>> Ian.
>>>
>>>
>> For native Linux, hwloc kinda already does this already - certainly the
>> CPU and PCI bits.
> That's what I meant by "does this not alreayd exist somewhere". So it
> sounds like extending hwloc is the right answer, the blurb should
> reflect this and list the specific things which it is lacking.
>
> Can you update the description please?
>
>>    Under Xen there are quite a few areas needing
>> improvement, which will require active development work.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 01:36:04 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 01:36:04 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WE7hB-0002d2-9f; Fri, 14 Feb 2014 01:36:01 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WE7h9-0002cp-6P
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 01:35:59 +0000
Received: from [85.158.137.68:37858] by server-15.bemta-3.messagelabs.com id
	5D/ED-19263-EF27DF25; Fri, 14 Feb 2014 01:35:58 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-11.tower-31.messagelabs.com!1392341755!1778654!1
X-Originating-IP: [209.85.220.52]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32354 invoked from network); 14 Feb 2014 01:35:57 -0000
Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com)
	(209.85.220.52)
	by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Feb 2014 01:35:57 -0000
Received: by mail-pa0-f52.google.com with SMTP id bj1so11550640pad.25
	for ;
	Thu, 13 Feb 2014 17:35:55 -0800 (PST)
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=s7tKFqavVPB1HV7+b4u2snGpZHWFX57OK5rpk3WFAaU=;
	b=c8gDqDnmdm96tLE1xu33LtEQ1jEEEOLegH8XjuCV/HQiQ+QmYgCWFPq0YUvt6fo9/h
	fTzcTNfjqn8KjXu4NZ9lFQoZl5H1+AW6CftHRNcwUGOLSoPk3GqDa9nCkQHdKaatfDRu
	6KLdqf8YeoH6ahL9EqFMLxjCUctG1gwu+8EpnWjra2qk7UxVvtxhUAW2sXsvVB/YqpV2
	QCAdPNqUgp7Ppp9PRWK5jdEJsG9f67uG9f1mTNqu82zcR5V+qIGI1JLy+I4I0KBDM8Bo
	VFoPFRkMLM2cxaqhwzpQtgloA530N2+YnsfsFfTy4d3VWAd8GjVt57nDVPhmSVruv3w/
	opVA==
X-Received: by 10.68.183.228 with SMTP id ep4mr5396873pbc.67.1392341755249;
	Thu, 13 Feb 2014 17:35:55 -0800 (PST)
Received: from [172.16.25.10] ([128.177.190.114])
	by mx.google.com with ESMTPSA id
	si6sm27460169pab.19.2014.02.13.17.35.53 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 13 Feb 2014 17:35:54 -0800 (PST)
Message-ID: <52FD72F8.107@xen.org>
Date: Fri, 14 Feb 2014 01:35:52 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: xen-devel@lists.xen.org, "xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org" 
References: <52DCE9FA.6010400@xen.org>
	<52E7B6AF.3050604@xen.org>	<1391609348.6497.178.camel@kazak.uk.xensource.com>	<52F24D4D.7040004@citrix.com>	<1391611558.23098.2.camel@kazak.uk.xensource.com>	<52F24F5D.7020207@citrix.com>
	<1391611929.23098.6.camel@kazak.uk.xensource.com>
In-Reply-To: <1391611929.23098.6.camel@kazak.uk.xensource.com>
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi all,

I created http://wiki.xen.org/wiki/GSoc_2014 based on the project list

Unless you guys step up, I will move all projects that have no
* level of difficulty
* skills needed
* outcomes
into http://wiki.xen.org/wiki/GSoc_2014#List_of_projects_that_need_more_work

I made a start on this and will do more on the weekend and/or monday. I 
will also sort, such that easy projects come first.

I am about to submit the application in the next two hours

Regards

On 05/02/2014 14:52, Ian Campbell wrote:
> (trimming cc, most people are presumably not interested)
>
> On Wed, 2014-02-05 at 14:49 +0000, Andrew Cooper wrote:
>> On 05/02/14 14:45, Ian Campbell wrote:
>>> On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote:
>>>> On 05/02/14 14:09, Ian Campbell wrote:
>>>>> Andy:
>>>>>
>>>>>        * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
>>>>>          allocations
>>>>>
>>>>>          Sounds too hard for a GSoC to me. Would need fleshing out in any
>>>>>          case.
>>>> Malcolm made a prototype for this on the first day of the Hackathon.  It
>>>> can disappear.
>>> Removed.
>>>
>>>>>        * CPU/RAM/PCI diagram tool
>>>>>
>>>>>          Does this not already exist somewhere?
>>>> Not as far as I (or my ability to google) am aware.
>>>>
>>>> My furrowing into hwloc interacting with Xen and libxc is a start to all
>>>> of this, but it is still very much in my copious free time and there is
>>>> more than enough other work which could be done if someone were interested.
>>> OK, left in place.
>>>
>>> This could conceivably be done under another umbrella such as the Linux
>>> one too, since it seems generic.
>>>
>>> Ian.
>>>
>>>
>> For native Linux, hwloc kinda already does this already - certainly the
>> CPU and PCI bits.
> That's what I meant by "does this not alreayd exist somewhere". So it
> sounds like extending hwloc is the right answer, the blurb should
> reflect this and list the specific things which it is lacking.
>
> Can you update the description please?
>
>>    Under Xen there are quite a few areas needing
>> improvement, which will require active development work.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 15:56:05 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 15:56:05 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEL7R-0000oc-3d; Fri, 14 Feb 2014 15:56:01 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEL7P-0000oU-Uo
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 15:56:00 +0000
Received: from [85.158.139.211:37659] by server-8.bemta-5.messagelabs.com id
	DE/75-05298-F8C3EF25; Fri, 14 Feb 2014 15:55:59 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-6.tower-206.messagelabs.com!1392393358!3968764!1
X-Originating-IP: [131.111.8.133]
X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31016 invoked from network); 14 Feb 2014 15:55:58 -0000
Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk)
	(131.111.8.133)
	by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 14 Feb 2014 15:55:58 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from dab-rcn1-h-83-10.dab.02.net ([82.132.247.248]:44096
	helo=[10.145.110.83])
	by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WEL7H-0003qI-hf (Exim 4.82_3-c0e5623) for
	mirageos-devel@lists.xenproject.org
	(return-path ); Fri, 14 Feb 2014 15:55:58 +0000
From: Amir Chaudhry 
X-Mailer: iPhone Mail (11B554a)
Message-Id: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
Date: Fri, 14 Feb 2014 15:55:41 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (1.0)
Subject: [MirageOS-devel] Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi folks,

I (perhaps foolishly) thought I could play with mirage-skeleton on the train today and made sure to update repos and packages.  Just now had a facepalm moment when I saw 'Installing OPAM packages' in the terminal while trying out the static_website stuff. 

Is there an easy way I can keep a local copy of all the things I might need? I get the feeling that opam-in-box (and a way to keep it up-to-date)  is what I'm after.

I'm just trying to figure out if I missed an obvious solution so if this isn't possible yet, that's fine. 

Best wishes,
Amir

--
sent via mobile
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 15:56:05 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 15:56:05 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEL7R-0000oc-3d; Fri, 14 Feb 2014 15:56:01 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEL7P-0000oU-Uo
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 15:56:00 +0000
Received: from [85.158.139.211:37659] by server-8.bemta-5.messagelabs.com id
	DE/75-05298-F8C3EF25; Fri, 14 Feb 2014 15:55:59 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-6.tower-206.messagelabs.com!1392393358!3968764!1
X-Originating-IP: [131.111.8.133]
X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31016 invoked from network); 14 Feb 2014 15:55:58 -0000
Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk)
	(131.111.8.133)
	by server-6.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 14 Feb 2014 15:55:58 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from dab-rcn1-h-83-10.dab.02.net ([82.132.247.248]:44096
	helo=[10.145.110.83])
	by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WEL7H-0003qI-hf (Exim 4.82_3-c0e5623) for
	mirageos-devel@lists.xenproject.org
	(return-path ); Fri, 14 Feb 2014 15:55:58 +0000
From: Amir Chaudhry 
X-Mailer: iPhone Mail (11B554a)
Message-Id: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
Date: Fri, 14 Feb 2014 15:55:41 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (1.0)
Subject: [MirageOS-devel] Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi folks,

I (perhaps foolishly) thought I could play with mirage-skeleton on the train today and made sure to update repos and packages.  Just now had a facepalm moment when I saw 'Installing OPAM packages' in the terminal while trying out the static_website stuff. 

Is there an easy way I can keep a local copy of all the things I might need? I get the feeling that opam-in-box (and a way to keep it up-to-date)  is what I'm after.

I'm just trying to figure out if I missed an obvious solution so if this isn't possible yet, that's fine. 

Best wishes,
Amir

--
sent via mobile
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 16:18:54 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 16:18: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 1WELTZ-0001nj-FK; Fri, 14 Feb 2014 16:18:53 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WELTY-0001na-Gx
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 16:18:52 +0000
Received: from [193.109.254.147:45500] by server-12.bemta-14.messagelabs.com
	id 60/D1-17220-BE14EF25; Fri, 14 Feb 2014 16:18:51 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-14.tower-27.messagelabs.com!1392394731!4416502!1
X-Originating-IP: [93.95.15.171]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogOTMuOTUuMTUuMTcxID0+IDQyMTM=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6358 invoked from network); 14 Feb 2014 16:18:51 -0000
Received: from engine05-20433-5.icritical.com (HELO
	engine05-20433-5.icritical.com) (93.95.15.171)
	by server-14.tower-27.messagelabs.com with SMTP;
	14 Feb 2014 16:18:51 -0000
Received: (qmail 13360 invoked from network); 14 Feb 2014 16:18:43 -0000
Received: from localhost (127.0.0.1)
	by engine05-20433-5.icritical.com with SMTP; 14 Feb 2014 16:18:43 -0000
Received: from engine05-20433-5.icritical.com ([127.0.0.1])
	by localhost (engine05-20433-5.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 12919-08 for ;
	Fri, 14 Feb 2014 16:18:40 +0000 (GMT)
Received: (qmail 10643 invoked by uid 599); 14 Feb 2014 16:12:09 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine05-20433-5.icritical.com (qpsmtpd/0.28) with ESMTP;
	Fri, 14 Feb 2014 16:12:09 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WELN7-0003hQ-GN
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 16:12:13 +0000
From: Richard Mortier 
To: Amir Chaudhry 
Date: Fri, 14 Feb 2014 16:12:11 +0000
Thread-Topic: [MirageOS-devel] Offline use of mirage?
Thread-Index: Ac8pn4TinPhdUdHrS4SYn5wKSQjeVw==
Message-ID: <52A06E28-8F01-44CE-8206-50BC4FAF8A19@nottingham.ac.uk>
References: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
In-Reply-To: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine05-20433-5.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 14 Feb 2014, at 15:55, Amir Chaudhry  wrote:

> I (perhaps foolishly) thought I could play with mirage-skeleton on the train today and made sure to update repos and packages.  Just now had a facepalm moment when I saw 'Installing OPAM packages' in the terminal while trying out the static_website stuff. 

:)

> Is there an easy way I can keep a local copy of all the things I might need? I get the feeling that opam-in-box (and a way to keep it up-to-date)  is what I'm after.

i think there's an issue on github to which one of the responses is to have some way to pull a bunch of packages locally. (i hit this problem on the way to fosdem.)

> I'm just trying to figure out if I missed an obvious solution so if this isn't possible yet, that's fine. 

fwiw i've also just about got the vagrant runes organised to use virtualbox to build a debian wheezy box, install xen, opam, and mirage. which at least makes some of the dev setup more repeatable.

(though if anyone can tell me what to do to get current vbox guest additions installed on xen on wheezy, i'd be grateful. just getting build failures currently.)

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 16:18:54 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 16:18: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 1WELTZ-0001nj-FK; Fri, 14 Feb 2014 16:18:53 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WELTY-0001na-Gx
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 16:18:52 +0000
Received: from [193.109.254.147:45500] by server-12.bemta-14.messagelabs.com
	id 60/D1-17220-BE14EF25; Fri, 14 Feb 2014 16:18:51 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-14.tower-27.messagelabs.com!1392394731!4416502!1
X-Originating-IP: [93.95.15.171]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogOTMuOTUuMTUuMTcxID0+IDQyMTM=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6358 invoked from network); 14 Feb 2014 16:18:51 -0000
Received: from engine05-20433-5.icritical.com (HELO
	engine05-20433-5.icritical.com) (93.95.15.171)
	by server-14.tower-27.messagelabs.com with SMTP;
	14 Feb 2014 16:18:51 -0000
Received: (qmail 13360 invoked from network); 14 Feb 2014 16:18:43 -0000
Received: from localhost (127.0.0.1)
	by engine05-20433-5.icritical.com with SMTP; 14 Feb 2014 16:18:43 -0000
Received: from engine05-20433-5.icritical.com ([127.0.0.1])
	by localhost (engine05-20433-5.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 12919-08 for ;
	Fri, 14 Feb 2014 16:18:40 +0000 (GMT)
Received: (qmail 10643 invoked by uid 599); 14 Feb 2014 16:12:09 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine05-20433-5.icritical.com (qpsmtpd/0.28) with ESMTP;
	Fri, 14 Feb 2014 16:12:09 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WELN7-0003hQ-GN
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 16:12:13 +0000
From: Richard Mortier 
To: Amir Chaudhry 
Date: Fri, 14 Feb 2014 16:12:11 +0000
Thread-Topic: [MirageOS-devel] Offline use of mirage?
Thread-Index: Ac8pn4TinPhdUdHrS4SYn5wKSQjeVw==
Message-ID: <52A06E28-8F01-44CE-8206-50BC4FAF8A19@nottingham.ac.uk>
References: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
In-Reply-To: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine05-20433-5.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 14 Feb 2014, at 15:55, Amir Chaudhry  wrote:

> I (perhaps foolishly) thought I could play with mirage-skeleton on the train today and made sure to update repos and packages.  Just now had a facepalm moment when I saw 'Installing OPAM packages' in the terminal while trying out the static_website stuff. 

:)

> Is there an easy way I can keep a local copy of all the things I might need? I get the feeling that opam-in-box (and a way to keep it up-to-date)  is what I'm after.

i think there's an issue on github to which one of the responses is to have some way to pull a bunch of packages locally. (i hit this problem on the way to fosdem.)

> I'm just trying to figure out if I missed an obvious solution so if this isn't possible yet, that's fine. 

fwiw i've also just about got the vagrant runes organised to use virtualbox to build a debian wheezy box, install xen, opam, and mirage. which at least makes some of the dev setup more repeatable.

(though if anyone can tell me what to do to get current vbox guest additions installed on xen on wheezy, i'd be grateful. just getting build failures currently.)

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 16:22:35 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 16:22: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 1WELX9-0001ss-9l; Fri, 14 Feb 2014 16:22:35 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WELX7-0001sm-DZ
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 16:22:33 +0000
Received: from [85.158.139.211:32682] by server-17.bemta-5.messagelabs.com id
	BC/C5-31975-8C24EF25; Fri, 14 Feb 2014 16:22:32 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-16.tower-206.messagelabs.com!1392394952!3999906!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25800 invoked from network); 14 Feb 2014 16:22:32 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-16.tower-206.messagelabs.com with SMTP;
	14 Feb 2014 16:22:32 -0000
Received: (qmail 6363 invoked by uid 634); 14 Feb 2014 16:22:31 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Fri, 14 Feb 2014 16:22:31 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
Date: Fri, 14 Feb 2014 16:22:29 +0000
Message-Id: <743FED91-38B8-48D4-AA27-B9DB350B028A@recoil.org>
References: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
To: Amir M Chaudhry 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: opam-devel ,
	mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 14 Feb 2014, at 15:55, Amir Chaudhry  wrote:

> Hi folks,
> 
> I (perhaps foolishly) thought I could play with mirage-skeleton on the train today and made sure to update repos and packages.  Just now had a facepalm moment when I saw 'Installing OPAM packages' in the terminal while trying out the static_website stuff. 
> 
> Is there an easy way I can keep a local copy of all the things I might need? I get the feeling that opam-in-box (and a way to keep it up-to-date)  is what I'm after.
> 
> I'm just trying to figure out if I missed an obvious solution so if this isn't possible yet, that's fine. 

Mort made the same request recently as well.  It's possible to do this by using "opam-admin make" to build a local version of the repository and using that as your remote.

For this to work, though, we'll need to come up with a list of all the packages that will be needed to pass to `opam-admin make`.  I notice that "opam-admin make --help" tells me this:

       -r, --recursive
           Recurse among the transitive dependencies.

       --resolve
           A more advanced version of `--recursive': will attempt to resolve
           your installation with all dependencies in the best way possible
           and build the archives accordingly.

CCing opam-devel: what on earth does the latter entry mean? :-)  What's the downside of using --resolve for everything instead of -r?  If there's none, why not get rid of -r entirely?

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 16:22:35 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 16:22: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 1WELX9-0001ss-9l; Fri, 14 Feb 2014 16:22:35 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WELX7-0001sm-DZ
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 16:22:33 +0000
Received: from [85.158.139.211:32682] by server-17.bemta-5.messagelabs.com id
	BC/C5-31975-8C24EF25; Fri, 14 Feb 2014 16:22:32 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-16.tower-206.messagelabs.com!1392394952!3999906!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25800 invoked from network); 14 Feb 2014 16:22:32 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-16.tower-206.messagelabs.com with SMTP;
	14 Feb 2014 16:22:32 -0000
Received: (qmail 6363 invoked by uid 634); 14 Feb 2014 16:22:31 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Fri, 14 Feb 2014 16:22:31 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
Date: Fri, 14 Feb 2014 16:22:29 +0000
Message-Id: <743FED91-38B8-48D4-AA27-B9DB350B028A@recoil.org>
References: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
To: Amir M Chaudhry 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: opam-devel ,
	mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 14 Feb 2014, at 15:55, Amir Chaudhry  wrote:

> Hi folks,
> 
> I (perhaps foolishly) thought I could play with mirage-skeleton on the train today and made sure to update repos and packages.  Just now had a facepalm moment when I saw 'Installing OPAM packages' in the terminal while trying out the static_website stuff. 
> 
> Is there an easy way I can keep a local copy of all the things I might need? I get the feeling that opam-in-box (and a way to keep it up-to-date)  is what I'm after.
> 
> I'm just trying to figure out if I missed an obvious solution so if this isn't possible yet, that's fine. 

Mort made the same request recently as well.  It's possible to do this by using "opam-admin make" to build a local version of the repository and using that as your remote.

For this to work, though, we'll need to come up with a list of all the packages that will be needed to pass to `opam-admin make`.  I notice that "opam-admin make --help" tells me this:

       -r, --recursive
           Recurse among the transitive dependencies.

       --resolve
           A more advanced version of `--recursive': will attempt to resolve
           your installation with all dependencies in the best way possible
           and build the archives accordingly.

CCing opam-devel: what on earth does the latter entry mean? :-)  What's the downside of using --resolve for everything instead of -r?  If there's none, why not get rid of -r entirely?

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 16:44:55 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 16:44: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 1WELsj-0002PR-AH; Fri, 14 Feb 2014 16:44:53 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WELsi-0002PJ-Nh; Fri, 14 Feb 2014 16:44:52 +0000
Received: from [193.109.254.147:9366] by server-11.bemta-14.messagelabs.com id
	2A/88-24604-3084EF25; Fri, 14 Feb 2014 16:44:51 +0000
X-Env-Sender: dario.faggioli@citrix.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1392396279!4428764!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n,
	ML_RADAR_SPEW_LINKS_8, spamassassin: ,
	async_handler: YXN5bmNfZGVsYXk6IDcwNTYzNDkgKHRpbWVvdXQp\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29228 invoked from network); 14 Feb 2014 16:44:40 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Feb 2014 16:44:40 -0000
X-IronPort-AV: E=Sophos;i="4.95,845,1384300800"; 
	d="asc'?scan'208";a="100843627"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 14 Feb 2014 16:44:39 +0000
Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com
	(10.13.107.79) with Microsoft SMTP Server id 14.2.342.4;
	Fri, 14 Feb 2014 11:44:38 -0500
Message-ID: <1392396276.32038.313.camel@Solace>
From: Dario Faggioli 
To: Anil Madhavapeddy 
Date: Fri, 14 Feb 2014 17:44:36 +0100
In-Reply-To: <484CB6F6-CB8B-45C7-AB06-60AA725B72DE@recoil.org>
References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com>
	
	
	<1386839335.14726.50.camel@Abyss>
	
	<1392145061.30734.59.camel@Solace>
	<484CB6F6-CB8B-45C7-AB06-60AA725B72DE@recoil.org>
Organization: Citrix
X-Mailer: Evolution 3.10.3 (3.10.3-1.fc20) 
MIME-Version: 1.0
X-DLP: MIA2
Cc: Lars Kurth , Amir Chaudhry ,
	Publicity list ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for
 openmirage.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1343352839140733297=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============1343352839140733297==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="=-99xTVm1Eg3CZmgdXkzoq"

--=-99xTVm1Eg3CZmgdXkzoq
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On mar, 2014-02-11 at 19:01 +0000, Anil Madhavapeddy wrote:
> A timely question!  We have quite a few articles that have gone up now;
> the front page has a summary of recent updates; http://www.openmirage.org=
/
>=20
Terrific!

> Some specific articles that may be of interest from the docs page:
> http://www.openmirage.org/docs/
>=20
> - How Xen events work: http://openmirage.org/wiki/xen-events
> - How Xen suspend/resume works: http://openmirage.org/wiki/xen-suspend
> - Building custom disk backends: http://openmirage.org/wiki/xen-synthesiz=
e-virtual-disk
> - A walkthrough building a Hello World Xen kernel: http://openmirage.org/=
wiki/hello-world
>=20
Right, some of them, I saw, some other I missed... I'll have a look.
Thanks for the complete set of pointers.

> As for distilling these down to a Xen blog post, I'll defer to someone wi=
th a little more time than I have right now.  I like the thinking though :-=
)
>=20
You mean you like the thinking behind, 'distilling these into summary
doc...'? Well, I bit you do, since it's you that said it, earlier in the
thread. :-D :-D

As per actually doing such distilling, I'll have a look at the articles
and then provide my view, by pinging again this thread. Will this be
fine, or is there someone in particular I should be talking to?

Thanks and Regards,
Dario

--=20
<> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


--=-99xTVm1Eg3CZmgdXkzoq
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEABECAAYFAlL+R/QACgkQk4XaBE3IOsSwpQCdEkLO2s1w+F73gKB0UjbeYBPa
bH0AnRMIaeU2sEH33Iigpv5MbswfJUNU
=Br9S
-----END PGP SIGNATURE-----

--=-99xTVm1Eg3CZmgdXkzoq--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============1343352839140733297==--


From mirageos-devel-bounces@lists.xenproject.org Fri Feb 14 16:44:55 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 14 Feb 2014 16:44: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 1WELsj-0002PR-AH; Fri, 14 Feb 2014 16:44:53 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WELsi-0002PJ-Nh; Fri, 14 Feb 2014 16:44:52 +0000
Received: from [193.109.254.147:9366] by server-11.bemta-14.messagelabs.com id
	2A/88-24604-3084EF25; Fri, 14 Feb 2014 16:44:51 +0000
X-Env-Sender: dario.faggioli@citrix.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1392396279!4428764!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n,
	ML_RADAR_SPEW_LINKS_8, spamassassin: ,
	async_handler: YXN5bmNfZGVsYXk6IDcwNTYzNDkgKHRpbWVvdXQp\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29228 invoked from network); 14 Feb 2014 16:44:40 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Feb 2014 16:44:40 -0000
X-IronPort-AV: E=Sophos;i="4.95,845,1384300800"; 
	d="asc'?scan'208";a="100843627"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 14 Feb 2014 16:44:39 +0000
Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com
	(10.13.107.79) with Microsoft SMTP Server id 14.2.342.4;
	Fri, 14 Feb 2014 11:44:38 -0500
Message-ID: <1392396276.32038.313.camel@Solace>
From: Dario Faggioli 
To: Anil Madhavapeddy 
Date: Fri, 14 Feb 2014 17:44:36 +0100
In-Reply-To: <484CB6F6-CB8B-45C7-AB06-60AA725B72DE@recoil.org>
References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com>
	
	
	<1386839335.14726.50.camel@Abyss>
	
	<1392145061.30734.59.camel@Solace>
	<484CB6F6-CB8B-45C7-AB06-60AA725B72DE@recoil.org>
Organization: Citrix
X-Mailer: Evolution 3.10.3 (3.10.3-1.fc20) 
MIME-Version: 1.0
X-DLP: MIA2
Cc: Lars Kurth , Amir Chaudhry ,
	Publicity list ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for
 openmirage.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============1343352839140733297=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============1343352839140733297==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="=-99xTVm1Eg3CZmgdXkzoq"

--=-99xTVm1Eg3CZmgdXkzoq
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On mar, 2014-02-11 at 19:01 +0000, Anil Madhavapeddy wrote:
> A timely question!  We have quite a few articles that have gone up now;
> the front page has a summary of recent updates; http://www.openmirage.org=
/
>=20
Terrific!

> Some specific articles that may be of interest from the docs page:
> http://www.openmirage.org/docs/
>=20
> - How Xen events work: http://openmirage.org/wiki/xen-events
> - How Xen suspend/resume works: http://openmirage.org/wiki/xen-suspend
> - Building custom disk backends: http://openmirage.org/wiki/xen-synthesiz=
e-virtual-disk
> - A walkthrough building a Hello World Xen kernel: http://openmirage.org/=
wiki/hello-world
>=20
Right, some of them, I saw, some other I missed... I'll have a look.
Thanks for the complete set of pointers.

> As for distilling these down to a Xen blog post, I'll defer to someone wi=
th a little more time than I have right now.  I like the thinking though :-=
)
>=20
You mean you like the thinking behind, 'distilling these into summary
doc...'? Well, I bit you do, since it's you that said it, earlier in the
thread. :-D :-D

As per actually doing such distilling, I'll have a look at the articles
and then provide my view, by pinging again this thread. Will this be
fine, or is there someone in particular I should be talking to?

Thanks and Regards,
Dario

--=20
<> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


--=-99xTVm1Eg3CZmgdXkzoq
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEABECAAYFAlL+R/QACgkQk4XaBE3IOsSwpQCdEkLO2s1w+F73gKB0UjbeYBPa
bH0AnRMIaeU2sEH33Iigpv5MbswfJUNU
=Br9S
-----END PGP SIGNATURE-----

--=-99xTVm1Eg3CZmgdXkzoq--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============1343352839140733297==--


From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 11:52:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 11:52: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 1WEdnZ-0005EI-BD; Sat, 15 Feb 2014 11:52:45 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDcoD-00080j-4A
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 16:37:13 +0000
Received: from [85.158.143.35:57745] by server-3.bemta-4.messagelabs.com id
	48/CA-11539-733ABF25; Wed, 12 Feb 2014 16:37:11 +0000
X-Env-Sender: roger.pau@citrix.com
X-Msg-Ref: server-11.tower-21.messagelabs.com!1392223029!5163498!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5982 invoked from network); 12 Feb 2014 16:37:10 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 16:37:10 -0000
X-IronPort-AV: E=Sophos;i="4.95,833,1384300800"; d="scan'208";a="100180313"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 12 Feb 2014 16:37:09 +0000
Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80)
	with Microsoft SMTP Server id 14.2.342.4;
	Wed, 12 Feb 2014 11:37:08 -0500
Message-ID: <52FBA331.9040004@citrix.com>
Date: Wed, 12 Feb 2014 17:37:05 +0100
From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ian Campbell , , Dario
	Faggioli , Konrad Rzeszutek Wilk
	, Ben Guthro , Andrew
	Cooper ,
	Paul Durrant , 
	Santosh Jodh , Ian Jackson
	
References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org>
	<1391609348.6497.178.camel@kazak.uk.xensource.com>
In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com>
X-Enigmail-Version: 1.6
X-DLP: MIA1
X-Mailman-Approved-At: Sat, 15 Feb 2014 11:52:44 +0000
Cc: "xen-api@lists.xen.org" ,
	mirageos-devel@lists.xenproject.org,
	"xen-devel@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 05/02/14 15:09, Ian Campbell wrote:
> Roger:
>       * Refactor Linux hotplug scripts
> 
>         You did some of this I think?

No, I've added a block-iscsi script, but I did not refactor the other
ones. It is still valid, however, I'm not sure it's attractive from a
GSoC point of view. I'm going to leave it anyway in case someone is
interested.


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 11:52:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 11:52: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 1WEdnZ-0005EN-D1; Sat, 15 Feb 2014 11:52:45 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDzqh-0007qu-KJ
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 17:13:19 +0000
Received: from [193.109.254.147:33989] by server-4.bemta-14.messagelabs.com id
	84/D8-32066-E2DFCF25; Thu, 13 Feb 2014 17:13:18 +0000
X-Env-Sender: Ian.Jackson@citrix.com
X-Msg-Ref: server-5.tower-27.messagelabs.com!1392311597!4167658!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1121 invoked from network); 13 Feb 2014 17:13:18 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 17:13:18 -0000
X-IronPort-AV: E=Sophos;i="4.95,839,1384300800"; d="scan'208";a="100525256"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 13 Feb 2014 17:13:16 +0000
Received: from norwich.cam.xci-test.com (10.80.248.129) by
	smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id
	14.2.342.4; Thu, 13 Feb 2014 12:13:16 -0500
Received: from mariner.cam.xci-test.com ([10.80.2.22]
	helo=mariner.uk.xensource.com)	by norwich.cam.xci-test.com with esmtp
	(Exim
	4.72)	(envelope-from )	id 1WDzqe-0001Sp-73;
	Thu, 13 Feb 2014 17:13:16 +0000
Received: from iwj by mariner.uk.xensource.com with local (Exim 4.80)
	(envelope-from )	id 1WDzqd-0004uh-Vs;
	Thu, 13 Feb 2014 17:13:16 +0000
From: Ian Jackson 
MIME-Version: 1.0
Message-ID: <21244.64811.826482.435714@mariner.uk.xensource.com>
Date: Thu, 13 Feb 2014 17:13:15 +0000
To: Roger Pau =?iso-8859-1?Q?Monn=E9?= 
In-Reply-To: <52FBA331.9040004@citrix.com>
References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org>
	<1391609348.6497.178.camel@kazak.uk.xensource.com>
	<52FBA331.9040004@citrix.com>
X-Mailer: VM 8.1.0 under 23.4.1 (i486-pc-linux-gnu)
X-DLP: MIA1
X-Mailman-Approved-At: Sat, 15 Feb 2014 11:52:44 +0000
Cc: Ben Guthro ,
	Ian Campbell ,
	Konrad Rzeszutek Wilk ,
	Andrew Cooper ,
	Dario Faggioli ,
	"xen-devel@lists.xen.org" ,
	mirageos-devel@lists.xenproject.org,
	Santosh Jodh ,
	Paul Durrant ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Roger Pau Monn=E9 writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] =
- deadline Feb 14 2014"):
> On 05/02/14 15:09, Ian Campbell wrote:
> > Roger:
> >       * Refactor Linux hotplug scripts
> > =

> >         You did some of this I think?
> =

> No, I've added a block-iscsi script, but I did not refactor the other
> ones. It is still valid, however, I'm not sure it's attractive from a
> GSoC point of view. I'm going to leave it anyway in case someone is
> interested.

Who is actually submitting our GSOC application ?

Ian.

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 11:52:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 11:52: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 1WEdnZ-0005ES-Em; Sat, 15 Feb 2014 11:52:45 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEMCz-00030P-DU
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 17:05:49 +0000
Received: from [85.158.143.35:44634] by server-3.bemta-4.messagelabs.com id
	95/23-11539-CEC4EF25; Fri, 14 Feb 2014 17:05:48 +0000
X-Env-Sender: gesbert@antislash.info
X-Msg-Ref: server-3.tower-21.messagelabs.com!1392397547!5769082!1
X-Originating-IP: [212.227.17.10]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	QmFkIElQOiAyMTIuMjI3LjE3LjEwID0+IDY3OTMx\n,sa_preprocessor: 
	QmFkIElQOiAyMTIuMjI3LjE3LjEwID0+IDY3OTMx\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11444 invoked from network); 14 Feb 2014 17:05:48 -0000
Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de)
	(212.227.17.10)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Feb 2014 17:05:48 -0000
Received: from agaric.localnet (jua06-3-88-189-115-104.fbx.proxad.net
	[88.189.115.104])
	by mrelayeu.kundenserver.de (node=mreue104) with ESMTP (Nemesis)
	id 0LwZRP-1V6tdl3BOR-018KRt; Fri, 14 Feb 2014 18:05:39 +0100
From: Louis Gesbert 
To: opam-devel@lists.ocaml.org
Date: Fri, 14 Feb 2014 18:05:36 +0100
Message-ID: <1471768.hqMcl0LVWx@agaric>
User-Agent: KMail/4.11.5 (Linux/3.12-1-amd64; KDE/4.11.3; x86_64; ; )
In-Reply-To: <743FED91-38B8-48D4-AA27-B9DB350B028A@recoil.org>
References: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
	<743FED91-38B8-48D4-AA27-B9DB350B028A@recoil.org>
MIME-Version: 1.0
X-Provags-ID: V02:K0:uQHNlw3FGterhb/dovK/Pgwm75yzwKFxfbBXGc8ZOGT
	JXRRVCnRUYhDSx8nbJrMPg7c6UzrJ/MoY7G4Curcz8hF5cXx3C
	TKKpVePz3j2dDHFD4YV52g3U5Wv8CUE2JAtKpPEYaHmxcnGpU0
	5VnoCJsAYCVQnqWUqCmW4JMY7Lm7vp1F2Npd40p9Fo0zlmTM46
	b4S3vbBAMJLKcI4klu4j6pTiYq8A38zmEIzG+G12ytxICaaHHe
	ojrI+Ld4c82RCLSX/0Hgy3uiZnicioMAKTG91ofmLkWXsMYCD6
	qvguOWgsCEsjcbPJDHdVIdugBIDdf8h5Diu6dds9vHlPM7z6Lj
	VL+FmzdvZZmoGYIEsqaY=
X-Mailman-Approved-At: Sat, 15 Feb 2014 11:52:44 +0000
Cc: mirageos-devel@lists.xenproject.org, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] [opam-devel]  Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


> For this to work, though, we'll need to come up with a list of all the packages that will be needed to pass to `opam-admin make`.  I notice that "opam-admin make --help" tells me this:
> 
>        -r, --recursive
>            Recurse among the transitive dependencies.
> 
>        --resolve
>            A more advanced version of `--recursive': will attempt to resolve
>            your installation with all dependencies in the best way possible
>            and build the archives accordingly.
> 
> CCing opam-devel: what on earth does the latter entry mean? :-)  What's the downside of using --resolve for everything instead of -r?  If there's none, why not get rid of -r entirely?

True, `--recursive` is mostly here for historical reasons. It will actually download _all_ versions of the dependencies. `--resolve` is a bit less predictable but will give you one usable snapshot of the universe.

I've nothing against removing `--recursive`, it's probably not used.

A nice addition would be the ability to prune the repository of unneeded package definitions : for now it keeps them all, just downloads a subset of the archives. That wouldn't be difficult.


--
Louis


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 11:52:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 11:52: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 1WEdnZ-0005ES-Em; Sat, 15 Feb 2014 11:52:45 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEMCz-00030P-DU
	for mirageos-devel@lists.xenproject.org; Fri, 14 Feb 2014 17:05:49 +0000
Received: from [85.158.143.35:44634] by server-3.bemta-4.messagelabs.com id
	95/23-11539-CEC4EF25; Fri, 14 Feb 2014 17:05:48 +0000
X-Env-Sender: gesbert@antislash.info
X-Msg-Ref: server-3.tower-21.messagelabs.com!1392397547!5769082!1
X-Originating-IP: [212.227.17.10]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	QmFkIElQOiAyMTIuMjI3LjE3LjEwID0+IDY3OTMx\n,sa_preprocessor: 
	QmFkIElQOiAyMTIuMjI3LjE3LjEwID0+IDY3OTMx\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11444 invoked from network); 14 Feb 2014 17:05:48 -0000
Received: from moutng.kundenserver.de (HELO moutng.kundenserver.de)
	(212.227.17.10)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Feb 2014 17:05:48 -0000
Received: from agaric.localnet (jua06-3-88-189-115-104.fbx.proxad.net
	[88.189.115.104])
	by mrelayeu.kundenserver.de (node=mreue104) with ESMTP (Nemesis)
	id 0LwZRP-1V6tdl3BOR-018KRt; Fri, 14 Feb 2014 18:05:39 +0100
From: Louis Gesbert 
To: opam-devel@lists.ocaml.org
Date: Fri, 14 Feb 2014 18:05:36 +0100
Message-ID: <1471768.hqMcl0LVWx@agaric>
User-Agent: KMail/4.11.5 (Linux/3.12-1-amd64; KDE/4.11.3; x86_64; ; )
In-Reply-To: <743FED91-38B8-48D4-AA27-B9DB350B028A@recoil.org>
References: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
	<743FED91-38B8-48D4-AA27-B9DB350B028A@recoil.org>
MIME-Version: 1.0
X-Provags-ID: V02:K0:uQHNlw3FGterhb/dovK/Pgwm75yzwKFxfbBXGc8ZOGT
	JXRRVCnRUYhDSx8nbJrMPg7c6UzrJ/MoY7G4Curcz8hF5cXx3C
	TKKpVePz3j2dDHFD4YV52g3U5Wv8CUE2JAtKpPEYaHmxcnGpU0
	5VnoCJsAYCVQnqWUqCmW4JMY7Lm7vp1F2Npd40p9Fo0zlmTM46
	b4S3vbBAMJLKcI4klu4j6pTiYq8A38zmEIzG+G12ytxICaaHHe
	ojrI+Ld4c82RCLSX/0Hgy3uiZnicioMAKTG91ofmLkWXsMYCD6
	qvguOWgsCEsjcbPJDHdVIdugBIDdf8h5Diu6dds9vHlPM7z6Lj
	VL+FmzdvZZmoGYIEsqaY=
X-Mailman-Approved-At: Sat, 15 Feb 2014 11:52:44 +0000
Cc: mirageos-devel@lists.xenproject.org, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] [opam-devel]  Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


> For this to work, though, we'll need to come up with a list of all the packages that will be needed to pass to `opam-admin make`.  I notice that "opam-admin make --help" tells me this:
> 
>        -r, --recursive
>            Recurse among the transitive dependencies.
> 
>        --resolve
>            A more advanced version of `--recursive': will attempt to resolve
>            your installation with all dependencies in the best way possible
>            and build the archives accordingly.
> 
> CCing opam-devel: what on earth does the latter entry mean? :-)  What's the downside of using --resolve for everything instead of -r?  If there's none, why not get rid of -r entirely?

True, `--recursive` is mostly here for historical reasons. It will actually download _all_ versions of the dependencies. `--resolve` is a bit less predictable but will give you one usable snapshot of the universe.

I've nothing against removing `--recursive`, it's probably not used.

A nice addition would be the ability to prune the repository of unneeded package definitions : for now it keeps them all, just downloads a subset of the archives. That wouldn't be difficult.


--
Louis


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 11:52:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 11:52: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 1WEdnZ-0005EN-D1; Sat, 15 Feb 2014 11:52:45 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDzqh-0007qu-KJ
	for mirageos-devel@lists.xenproject.org; Thu, 13 Feb 2014 17:13:19 +0000
Received: from [193.109.254.147:33989] by server-4.bemta-14.messagelabs.com id
	84/D8-32066-E2DFCF25; Thu, 13 Feb 2014 17:13:18 +0000
X-Env-Sender: Ian.Jackson@citrix.com
X-Msg-Ref: server-5.tower-27.messagelabs.com!1392311597!4167658!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1121 invoked from network); 13 Feb 2014 17:13:18 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	13 Feb 2014 17:13:18 -0000
X-IronPort-AV: E=Sophos;i="4.95,839,1384300800"; d="scan'208";a="100525256"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 13 Feb 2014 17:13:16 +0000
Received: from norwich.cam.xci-test.com (10.80.248.129) by
	smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id
	14.2.342.4; Thu, 13 Feb 2014 12:13:16 -0500
Received: from mariner.cam.xci-test.com ([10.80.2.22]
	helo=mariner.uk.xensource.com)	by norwich.cam.xci-test.com with esmtp
	(Exim
	4.72)	(envelope-from )	id 1WDzqe-0001Sp-73;
	Thu, 13 Feb 2014 17:13:16 +0000
Received: from iwj by mariner.uk.xensource.com with local (Exim 4.80)
	(envelope-from )	id 1WDzqd-0004uh-Vs;
	Thu, 13 Feb 2014 17:13:16 +0000
From: Ian Jackson 
MIME-Version: 1.0
Message-ID: <21244.64811.826482.435714@mariner.uk.xensource.com>
Date: Thu, 13 Feb 2014 17:13:15 +0000
To: Roger Pau =?iso-8859-1?Q?Monn=E9?= 
In-Reply-To: <52FBA331.9040004@citrix.com>
References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org>
	<1391609348.6497.178.camel@kazak.uk.xensource.com>
	<52FBA331.9040004@citrix.com>
X-Mailer: VM 8.1.0 under 23.4.1 (i486-pc-linux-gnu)
X-DLP: MIA1
X-Mailman-Approved-At: Sat, 15 Feb 2014 11:52:44 +0000
Cc: Ben Guthro ,
	Ian Campbell ,
	Konrad Rzeszutek Wilk ,
	Andrew Cooper ,
	Dario Faggioli ,
	"xen-devel@lists.xen.org" ,
	mirageos-devel@lists.xenproject.org,
	Santosh Jodh ,
	Paul Durrant ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Roger Pau Monn=E9 writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] =
- deadline Feb 14 2014"):
> On 05/02/14 15:09, Ian Campbell wrote:
> > Roger:
> >       * Refactor Linux hotplug scripts
> > =

> >         You did some of this I think?
> =

> No, I've added a block-iscsi script, but I did not refactor the other
> ones. It is still valid, however, I'm not sure it's attractive from a
> GSoC point of view. I'm going to leave it anyway in case someone is
> interested.

Who is actually submitting our GSOC application ?

Ian.

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 11:52:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 11:52: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 1WEdnZ-0005EI-BD; Sat, 15 Feb 2014 11:52:45 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WDcoD-00080j-4A
	for mirageos-devel@lists.xenproject.org; Wed, 12 Feb 2014 16:37:13 +0000
Received: from [85.158.143.35:57745] by server-3.bemta-4.messagelabs.com id
	48/CA-11539-733ABF25; Wed, 12 Feb 2014 16:37:11 +0000
X-Env-Sender: roger.pau@citrix.com
X-Msg-Ref: server-11.tower-21.messagelabs.com!1392223029!5163498!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5982 invoked from network); 12 Feb 2014 16:37:10 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	12 Feb 2014 16:37:10 -0000
X-IronPort-AV: E=Sophos;i="4.95,833,1384300800"; d="scan'208";a="100180313"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 12 Feb 2014 16:37:09 +0000
Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80)
	with Microsoft SMTP Server id 14.2.342.4;
	Wed, 12 Feb 2014 11:37:08 -0500
Message-ID: <52FBA331.9040004@citrix.com>
Date: Wed, 12 Feb 2014 17:37:05 +0100
From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ian Campbell , , Dario
	Faggioli , Konrad Rzeszutek Wilk
	, Ben Guthro , Andrew
	Cooper ,
	Paul Durrant , 
	Santosh Jodh , Ian Jackson
	
References: <52DCE9FA.6010400@xen.org> <52E7B6AF.3050604@xen.org>
	<1391609348.6497.178.camel@kazak.uk.xensource.com>
In-Reply-To: <1391609348.6497.178.camel@kazak.uk.xensource.com>
X-Enigmail-Version: 1.6
X-DLP: MIA1
X-Mailman-Approved-At: Sat, 15 Feb 2014 11:52:44 +0000
Cc: "xen-api@lists.xen.org" ,
	mirageos-devel@lists.xenproject.org,
	"xen-devel@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 05/02/14 15:09, Ian Campbell wrote:
> Roger:
>       * Refactor Linux hotplug scripts
> 
>         You did some of this I think?

No, I've added a block-iscsi script, but I did not refactor the other
ones. It is still valid, however, I'm not sure it's attractive from a
GSoC point of view. I'm going to leave it anyway in case someone is
interested.


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 12:00:01 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 12:00:01 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEdub-0005JT-1q; Sat, 15 Feb 2014 12:00:01 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEduZ-0005JO-UD
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 12:00:00 +0000
Received: from [85.158.137.68:31223] by server-15.bemta-3.messagelabs.com id
	BC/D1-19263-FB65FF25; Sat, 15 Feb 2014 11:59:59 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-2.tower-31.messagelabs.com!1392465598!487026!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15589 invoked from network); 15 Feb 2014 11:59:58 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-2.tower-31.messagelabs.com with SMTP;
	15 Feb 2014 11:59:58 -0000
Received: (qmail 13421 invoked by uid 634); 15 Feb 2014 11:59:57 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sat, 15 Feb 2014 11:59:53 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <1471768.hqMcl0LVWx@agaric>
Date: Sat, 15 Feb 2014 11:59:51 +0000
Message-Id: <338CF19F-F175-4E2E-B593-A72AA4C32BDA@recoil.org>
References: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
	<743FED91-38B8-48D4-AA27-B9DB350B028A@recoil.org>
	<1471768.hqMcl0LVWx@agaric>
To: Louis Gesbert 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: opam-devel ,
	mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] [opam-devel]  Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 14 Feb 2014, at 17:05, Louis Gesbert  wrote:

> 
>> For this to work, though, we'll need to come up with a list of all the packages that will be needed to pass to `opam-admin make`.  I notice that "opam-admin make --help" tells me this:
>> 
>>       -r, --recursive
>>           Recurse among the transitive dependencies.
>> 
>>       --resolve
>>           A more advanced version of `--recursive': will attempt to resolve
>>           your installation with all dependencies in the best way possible
>>           and build the archives accordingly.
>> 
>> CCing opam-devel: what on earth does the latter entry mean? :-)  What's the downside of using --resolve for everything instead of -r?  If there's none, why not get rid of -r entirely?
> 
> True, `--recursive` is mostly here for historical reasons. It will actually download _all_ versions of the dependencies. `--resolve` is a bit less predictable but will give you one usable snapshot of the universe.
> 
> I've nothing against removing `--recursive`, it's probably not used.
> 
> A nice addition would be the ability to prune the repository of unneeded package definitions : for now it keeps them all, just downloads a subset of the archives. That wouldn't be difficult.

Thanks for clarifying this!  It sounds like `--resolve` (with just one version per package) would work fine for our needs to use Mirage offline.  I've sent a pull request to OPAM to (hopefully) clarify the man page wording.

https://github.com/ocaml/opam/pull/1178

-a


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 12:00:01 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 12:00:01 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEdub-0005JT-1q; Sat, 15 Feb 2014 12:00:01 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEduZ-0005JO-UD
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 12:00:00 +0000
Received: from [85.158.137.68:31223] by server-15.bemta-3.messagelabs.com id
	BC/D1-19263-FB65FF25; Sat, 15 Feb 2014 11:59:59 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-2.tower-31.messagelabs.com!1392465598!487026!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15589 invoked from network); 15 Feb 2014 11:59:58 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-2.tower-31.messagelabs.com with SMTP;
	15 Feb 2014 11:59:58 -0000
Received: (qmail 13421 invoked by uid 634); 15 Feb 2014 11:59:57 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sat, 15 Feb 2014 11:59:53 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <1471768.hqMcl0LVWx@agaric>
Date: Sat, 15 Feb 2014 11:59:51 +0000
Message-Id: <338CF19F-F175-4E2E-B593-A72AA4C32BDA@recoil.org>
References: <33CB1DF5-F2E7-4B10-AE0A-4C21CB1CE043@cam.ac.uk>
	<743FED91-38B8-48D4-AA27-B9DB350B028A@recoil.org>
	<1471768.hqMcl0LVWx@agaric>
To: Louis Gesbert 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: opam-devel ,
	mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] [opam-devel]  Offline use of mirage?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 14 Feb 2014, at 17:05, Louis Gesbert  wrote:

> 
>> For this to work, though, we'll need to come up with a list of all the packages that will be needed to pass to `opam-admin make`.  I notice that "opam-admin make --help" tells me this:
>> 
>>       -r, --recursive
>>           Recurse among the transitive dependencies.
>> 
>>       --resolve
>>           A more advanced version of `--recursive': will attempt to resolve
>>           your installation with all dependencies in the best way possible
>>           and build the archives accordingly.
>> 
>> CCing opam-devel: what on earth does the latter entry mean? :-)  What's the downside of using --resolve for everything instead of -r?  If there's none, why not get rid of -r entirely?
> 
> True, `--recursive` is mostly here for historical reasons. It will actually download _all_ versions of the dependencies. `--resolve` is a bit less predictable but will give you one usable snapshot of the universe.
> 
> I've nothing against removing `--recursive`, it's probably not used.
> 
> A nice addition would be the ability to prune the repository of unneeded package definitions : for now it keeps them all, just downloads a subset of the archives. That wouldn't be difficult.

Thanks for clarifying this!  It sounds like `--resolve` (with just one version per package) would work fine for our needs to use Mirage offline.  I've sent a pull request to OPAM to (hopefully) clarify the man page wording.

https://github.com/ocaml/opam/pull/1178

-a


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 12:03:10 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 12:03:10 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEdxd-0005Tk-Hy; Sat, 15 Feb 2014 12:03:09 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEdxc-0005TX-CM
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 12:03:08 +0000
Received: from [85.158.137.68:61280] by server-4.bemta-3.messagelabs.com id
	80/F4-04858-B775FF25; Sat, 15 Feb 2014 12:03:07 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-10.tower-31.messagelabs.com!1392465786!518077!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26810 invoked from network); 15 Feb 2014 12:03:06 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-10.tower-31.messagelabs.com with SMTP;
	15 Feb 2014 12:03:06 -0000
Received: (qmail 20654 invoked by uid 634); 15 Feb 2014 12:03:06 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sat, 15 Feb 2014 12:03:06 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <1392396276.32038.313.camel@Solace>
Date: Sat, 15 Feb 2014 12:03:04 +0000
Message-Id: <2C33CD07-81EB-4C4D-8C5C-641AD38F7D72@recoil.org>
References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com>
	
	
	<1386839335.14726.50.camel@Abyss>
	
	<1392145061.30734.59.camel@Solace>
	<484CB6F6-CB8B-45C7-AB06-60AA725B72DE@recoil.org>
	<1392396276.32038.313.camel@Solace>
To: Dario Faggioli 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Lars Kurth , Amir Chaudhry ,
	Publicity list ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for
	openmirage.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 14 Feb 2014, at 16:44, Dario Faggioli  wrote:
> 
>> As for distilling these down to a Xen blog post, I'll defer to someone with a little more time than I have right now.  I like the thinking though :-)
>> 
> You mean you like the thinking behind, 'distilling these into summary
> doc...'? Well, I bit you do, since it's you that said it, earlier in the
> thread. :-D :-D
> 
> As per actually doing such distilling, I'll have a look at the articles
> and then provide my view, by pinging again this thread. Will this be
> fine, or is there someone in particular I should be talking to?
> 

This thread's just fine -- Dave, Jon and I definitely want to continue to
write these little blog posts to explain individual libraries as we find
time, as it's very helpful way to code review portions of Mirage as well.

This is especially true now that the basic libraries structures have
settled down in Mirage 1.1.x, thanks to Dave's splitting up of the Xen
libxc bits into fully parallel installable bits.

I'm currently working on rebasing our fork of MiniOS back to upstream Xen,
using ocaml-ctypes for the glue bindings.  This is both in hope of a future
ARM MiniOS, but also to make the 'how a VM boots' part of Mirage much easier
to explain and to support HVM booting.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 12:03:10 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 12:03:10 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEdxd-0005Tk-Hy; Sat, 15 Feb 2014 12:03:09 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEdxc-0005TX-CM
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 12:03:08 +0000
Received: from [85.158.137.68:61280] by server-4.bemta-3.messagelabs.com id
	80/F4-04858-B775FF25; Sat, 15 Feb 2014 12:03:07 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-10.tower-31.messagelabs.com!1392465786!518077!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26810 invoked from network); 15 Feb 2014 12:03:06 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-10.tower-31.messagelabs.com with SMTP;
	15 Feb 2014 12:03:06 -0000
Received: (qmail 20654 invoked by uid 634); 15 Feb 2014 12:03:06 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sat, 15 Feb 2014 12:03:06 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <1392396276.32038.313.camel@Solace>
Date: Sat, 15 Feb 2014 12:03:04 +0000
Message-Id: <2C33CD07-81EB-4C4D-8C5C-641AD38F7D72@recoil.org>
References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com>
	
	
	<1386839335.14726.50.camel@Abyss>
	
	<1392145061.30734.59.camel@Solace>
	<484CB6F6-CB8B-45C7-AB06-60AA725B72DE@recoil.org>
	<1392396276.32038.313.camel@Solace>
To: Dario Faggioli 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Lars Kurth , Amir Chaudhry ,
	Publicity list ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for
	openmirage.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 14 Feb 2014, at 16:44, Dario Faggioli  wrote:
> 
>> As for distilling these down to a Xen blog post, I'll defer to someone with a little more time than I have right now.  I like the thinking though :-)
>> 
> You mean you like the thinking behind, 'distilling these into summary
> doc...'? Well, I bit you do, since it's you that said it, earlier in the
> thread. :-D :-D
> 
> As per actually doing such distilling, I'll have a look at the articles
> and then provide my view, by pinging again this thread. Will this be
> fine, or is there someone in particular I should be talking to?
> 

This thread's just fine -- Dave, Jon and I definitely want to continue to
write these little blog posts to explain individual libraries as we find
time, as it's very helpful way to code review portions of Mirage as well.

This is especially true now that the basic libraries structures have
settled down in Mirage 1.1.x, thanks to Dave's splitting up of the Xen
libxc bits into fully parallel installable bits.

I'm currently working on rebasing our fork of MiniOS back to upstream Xen,
using ocaml-ctypes for the glue bindings.  This is both in hope of a future
ARM MiniOS, but also to make the 'how a VM boots' part of Mirage much easier
to explain and to support HVM booting.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 16:05:59 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 16:05:59 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEhka-00075b-Bj; Sat, 15 Feb 2014 16:05:56 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEhkZ-00075W-8n
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 16:05:55 +0000
Received: from [193.109.254.147:20567] by server-13.bemta-14.messagelabs.com
	id D4/72-01226-2609FF25; Sat, 15 Feb 2014 16:05:54 +0000
X-Env-Sender: hannes@mehnert.org
X-Msg-Ref: server-4.tower-27.messagelabs.com!1392480353!810578!1
X-Originating-IP: [213.73.89.199]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18384 invoked from network); 15 Feb 2014 16:05:53 -0000
Received: from mail.h3q.com (HELO mail.h3q.com) (213.73.89.199)
	by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 15 Feb 2014 16:05:53 -0000
Received: (qmail 46810 invoked from network); 15 Feb 2014 16:05:51 -0000
Received: from mail.h3q.com (HELO mail.h3q.com) (hannes)
	by mail.h3q.com with CAMELLIA256-SHA encrypted SMTP;
	15 Feb 2014 16:05:51 -0000
Message-ID: <52FF9063.4060408@mehnert.org>
Date: Sat, 15 Feb 2014 16:05:55 +0000
From: Hannes Mehnert 
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "mirageos-devel@lists.xenproject.org" 
Subject: [MirageOS-devel] mirage-tcpip Fin/Fin-Ack
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hey,

first of all: thanks for your great work on mirage. It is an awesome
project.

While writing some mirage code, I discovered that the TCP layer sends
a duplicate ack after a fin (which is fin + ack):

client --SYN-(seq=0)-> mirage
mirage --SYN-ACK-(seq=0,ack=1)-> client
client --ACK-(seq=1,ack=1)-> mirage
client --data-(seq=1,len=7)-> mirage
mirage --FIN-ACK-(seq=1,ack=8)-> client
mirage --ACK-(seq=2,ack=8)-> client
client --ACK-(seq=8,ack=2)-> mirage
client --FIN-ACK-(seq=8,ack=2)-> mirage
mirage --ACK-(seq=2,ack=9)-> client


This happens already with the network-skeleton/network code, running
on unix (FreeBSD) with a tap interface. I've uploaded a pcap file with
the tcp connection to https://berlin.ccc.de/~hannes/mirage-network.pcap .

Unfortunately I wasn't able to spot the piece of code responsible for
sending the duplicated ack.


Any ideas on this issue?

Hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBCQAGBQJS/5BjAAoJELyJZYjffCjut2kQALsAIFUa722YpORNLDCj059T
TjnyWgnXM8pXhTX7sKRJ4E60ke0uC4FGxowwm6TSZ36iUPibKcoBkURDisinsxmE
U5uu3fJoJipcxmS0FTtap6eQ9RcfoOAV3Y+LmLw6w9C2je3uFAgg/VVUZLFqOTvZ
AsrUiUu6C5ET23ajogBZyvYKtxU26KWrdkTI7zjCY8Xc6gQgTuDIcg31Y+bm+p53
U9leqKMWDhrcaHOTgNt2tSTAeBYX46lNc+A79PgJhor5FLPCB39cDaKuw/gBs71k
+d92uTfDIW3Ehcm2/ecmzYhuM/zXR41IHcqqhlM/woXJfK3t6tdEbv4azV/LlE6z
nPitFGIdS4cPefiZKtEj+a4Nost8xj2HtVZpsqlFa+mEe8diNU7K6sEIlJzO5p8f
KkkmiqNxgttLFBskIMmRUseWl506ckvY7TXoUg4kcU6OAF+0jBmj0XmJgf/5Lrfq
i5i2yrXggosI06Fu6fWdAKZs7BqiSmqsRkgl8fSkN4i4jvzRTCXWUqrM+eydl19n
UbRPflr5mRiUwxkqAO3Qib9iTJSv5fuiy1dqar+Vo67v8BCD3vaYhmLqP+vtuMwx
7FTL4jTD3mdqvwqHAlZ7GBRcfPJuscOdTWNuXE0yHkFg6yrwra1XSrNmx7kGVeue
zxEwFzoL4QA86lHlb4tj
=Q41d
-----END PGP SIGNATURE-----

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 16:05:59 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 16:05:59 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEhka-00075b-Bj; Sat, 15 Feb 2014 16:05:56 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WEhkZ-00075W-8n
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 16:05:55 +0000
Received: from [193.109.254.147:20567] by server-13.bemta-14.messagelabs.com
	id D4/72-01226-2609FF25; Sat, 15 Feb 2014 16:05:54 +0000
X-Env-Sender: hannes@mehnert.org
X-Msg-Ref: server-4.tower-27.messagelabs.com!1392480353!810578!1
X-Originating-IP: [213.73.89.199]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18384 invoked from network); 15 Feb 2014 16:05:53 -0000
Received: from mail.h3q.com (HELO mail.h3q.com) (213.73.89.199)
	by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 15 Feb 2014 16:05:53 -0000
Received: (qmail 46810 invoked from network); 15 Feb 2014 16:05:51 -0000
Received: from mail.h3q.com (HELO mail.h3q.com) (hannes)
	by mail.h3q.com with CAMELLIA256-SHA encrypted SMTP;
	15 Feb 2014 16:05:51 -0000
Message-ID: <52FF9063.4060408@mehnert.org>
Date: Sat, 15 Feb 2014 16:05:55 +0000
From: Hannes Mehnert 
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "mirageos-devel@lists.xenproject.org" 
Subject: [MirageOS-devel] mirage-tcpip Fin/Fin-Ack
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hey,

first of all: thanks for your great work on mirage. It is an awesome
project.

While writing some mirage code, I discovered that the TCP layer sends
a duplicate ack after a fin (which is fin + ack):

client --SYN-(seq=0)-> mirage
mirage --SYN-ACK-(seq=0,ack=1)-> client
client --ACK-(seq=1,ack=1)-> mirage
client --data-(seq=1,len=7)-> mirage
mirage --FIN-ACK-(seq=1,ack=8)-> client
mirage --ACK-(seq=2,ack=8)-> client
client --ACK-(seq=8,ack=2)-> mirage
client --FIN-ACK-(seq=8,ack=2)-> mirage
mirage --ACK-(seq=2,ack=9)-> client


This happens already with the network-skeleton/network code, running
on unix (FreeBSD) with a tap interface. I've uploaded a pcap file with
the tcp connection to https://berlin.ccc.de/~hannes/mirage-network.pcap .

Unfortunately I wasn't able to spot the piece of code responsible for
sending the duplicated ack.


Any ideas on this issue?

Hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBCQAGBQJS/5BjAAoJELyJZYjffCjut2kQALsAIFUa722YpORNLDCj059T
TjnyWgnXM8pXhTX7sKRJ4E60ke0uC4FGxowwm6TSZ36iUPibKcoBkURDisinsxmE
U5uu3fJoJipcxmS0FTtap6eQ9RcfoOAV3Y+LmLw6w9C2je3uFAgg/VVUZLFqOTvZ
AsrUiUu6C5ET23ajogBZyvYKtxU26KWrdkTI7zjCY8Xc6gQgTuDIcg31Y+bm+p53
U9leqKMWDhrcaHOTgNt2tSTAeBYX46lNc+A79PgJhor5FLPCB39cDaKuw/gBs71k
+d92uTfDIW3Ehcm2/ecmzYhuM/zXR41IHcqqhlM/woXJfK3t6tdEbv4azV/LlE6z
nPitFGIdS4cPefiZKtEj+a4Nost8xj2HtVZpsqlFa+mEe8diNU7K6sEIlJzO5p8f
KkkmiqNxgttLFBskIMmRUseWl506ckvY7TXoUg4kcU6OAF+0jBmj0XmJgf/5Lrfq
i5i2yrXggosI06Fu6fWdAKZs7BqiSmqsRkgl8fSkN4i4jvzRTCXWUqrM+eydl19n
UbRPflr5mRiUwxkqAO3Qib9iTJSv5fuiy1dqar+Vo67v8BCD3vaYhmLqP+vtuMwx
7FTL4jTD3mdqvwqHAlZ7GBRcfPJuscOdTWNuXE0yHkFg6yrwra1XSrNmx7kGVeue
zxEwFzoL4QA86lHlb4tj
=Q41d
-----END PGP SIGNATURE-----

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 21:45:37 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 21:45: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 1WEn3G-0000pH-4l; Sat, 15 Feb 2014 21:45:34 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEn3E-0000pC-SN
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 21:45:33 +0000
Received: from [85.158.139.211:60208] by server-17.bemta-5.messagelabs.com id
	DA/E4-31975-CFFDFF25; Sat, 15 Feb 2014 21:45:32 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-11.tower-206.messagelabs.com!1392500731!4177848!1
X-Originating-IP: [93.95.15.169]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24941 invoked from network); 15 Feb 2014 21:45:31 -0000
Received: from engine01-20433-1.icritical.com (HELO
	engine01-20433-1.icritical.com) (93.95.15.169)
	by server-11.tower-206.messagelabs.com with SMTP;
	15 Feb 2014 21:45:31 -0000
Received: (qmail 31577 invoked from network); 15 Feb 2014 21:45:33 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-1.icritical.com with SMTP; 15 Feb 2014 21:45:33 -0000
Received: from engine01-20433-1.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 31441-01 for ;
	Sat, 15 Feb 2014 21:45:32 +0000 (GMT)
Received: (qmail 31546 invoked by uid 599); 15 Feb 2014 21:45:32 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP;
	Sat, 15 Feb 2014 21:45:32 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WEn3A-0005Sv-P7
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 21:45:28 +0000
From: Richard Mortier 
To: "mirageos-devel@lists.xenproject.org" 
Date: Sat, 15 Feb 2014 21:45:27 +0000
Thread-Topic: xen on virtualbox for development
Thread-Index: Ac8qlz1xj51ZTWIOTMWb27fysVAuKw==
Message-ID: <4BB4F85D-7E19-4C4E-BDB0-4E04895EE76F@nottingham.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com
Subject: [MirageOS-devel] xen on virtualbox for development
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

hi all;

fwiw i've collated some runes for building a virtualbox VM on OSX that installs and configures opam and mirage in a debian wheezy xen dom0 using vagrant and veewee. (as i understood on the last mirage call that this is the "recommended" xen configuration for mirage -- someone tell me otherwise if i've got this wrong!)

i thought they might be of some use for others who also wish to test mirage xen vms on their local machines but who can't boot to xen directly. the vagrant and veewee installation runes are probably OSX specific, but i'd hope that most of the vm setup would be applicable to any virtualbox install. i've successfully run most of the mirage-skeleton samples under this config.

runes at 

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 15 21:45:37 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 15 Feb 2014 21:45: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 1WEn3G-0000pH-4l; Sat, 15 Feb 2014 21:45:34 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WEn3E-0000pC-SN
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 21:45:33 +0000
Received: from [85.158.139.211:60208] by server-17.bemta-5.messagelabs.com id
	DA/E4-31975-CFFDFF25; Sat, 15 Feb 2014 21:45:32 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-11.tower-206.messagelabs.com!1392500731!4177848!1
X-Originating-IP: [93.95.15.169]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24941 invoked from network); 15 Feb 2014 21:45:31 -0000
Received: from engine01-20433-1.icritical.com (HELO
	engine01-20433-1.icritical.com) (93.95.15.169)
	by server-11.tower-206.messagelabs.com with SMTP;
	15 Feb 2014 21:45:31 -0000
Received: (qmail 31577 invoked from network); 15 Feb 2014 21:45:33 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-1.icritical.com with SMTP; 15 Feb 2014 21:45:33 -0000
Received: from engine01-20433-1.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 31441-01 for ;
	Sat, 15 Feb 2014 21:45:32 +0000 (GMT)
Received: (qmail 31546 invoked by uid 599); 15 Feb 2014 21:45:32 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP;
	Sat, 15 Feb 2014 21:45:32 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WEn3A-0005Sv-P7
	for mirageos-devel@lists.xenproject.org; Sat, 15 Feb 2014 21:45:28 +0000
From: Richard Mortier 
To: "mirageos-devel@lists.xenproject.org" 
Date: Sat, 15 Feb 2014 21:45:27 +0000
Thread-Topic: xen on virtualbox for development
Thread-Index: Ac8qlz1xj51ZTWIOTMWb27fysVAuKw==
Message-ID: <4BB4F85D-7E19-4C4E-BDB0-4E04895EE76F@nottingham.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com
Subject: [MirageOS-devel] xen on virtualbox for development
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

hi all;

fwiw i've collated some runes for building a virtualbox VM on OSX that installs and configures opam and mirage in a debian wheezy xen dom0 using vagrant and veewee. (as i understood on the last mirage call that this is the "recommended" xen configuration for mirage -- someone tell me otherwise if i've got this wrong!)

i thought they might be of some use for others who also wish to test mirage xen vms on their local machines but who can't boot to xen directly. the vagrant and veewee installation runes are probably OSX specific, but i'd hope that most of the vm setup would be applicable to any virtualbox install. i've successfully run most of the mirage-skeleton samples under this config.

runes at 

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 16 22:25:07 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 16 Feb 2014 22:25: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 1WFA8y-00012Y-RZ; Sun, 16 Feb 2014 22:25:00 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFA8x-00012S-Bm
	for mirageos-devel@lists.xenproject.org; Sun, 16 Feb 2014 22:24:59 +0000
Received: from [85.158.143.35:48338] by server-1.bemta-4.messagelabs.com id
	1C/02-31661-ABA31035; Sun, 16 Feb 2014 22:24:58 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-7.tower-21.messagelabs.com!1392589497!6069714!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21586 invoked from network); 16 Feb 2014 22:24:57 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-7.tower-21.messagelabs.com with SMTP;
	16 Feb 2014 22:24:57 -0000
Received: (qmail 20518 invoked by uid 634); 16 Feb 2014 22:24:57 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sun, 16 Feb 2014 22:24:56 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <4BB4F85D-7E19-4C4E-BDB0-4E04895EE76F@nottingham.ac.uk>
Date: Sun, 16 Feb 2014 22:24:55 +0000
Message-Id: 
References: <4BB4F85D-7E19-4C4E-BDB0-4E04895EE76F@nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] xen on virtualbox for development
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Nice!  Could you move the repo over to mirage/mirage-vagrant-vms, and I'll merge in the OPAM doc stuff as well?

-a

On 15 Feb 2014, at 21:45, Richard Mortier  wrote:

> hi all;
> 
> fwiw i've collated some runes for building a virtualbox VM on OSX that installs and configures opam and mirage in a debian wheezy xen dom0 using vagrant and veewee. (as i understood on the last mirage call that this is the "recommended" xen configuration for mirage -- someone tell me otherwise if i've got this wrong!)
> 
> i thought they might be of some use for others who also wish to test mirage xen vms on their local machines but who can't boot to xen directly. the vagrant and veewee installation runes are probably OSX specific, but i'd hope that most of the vm setup would be applicable to any virtualbox install. i've successfully run most of the mirage-skeleton samples under this config.
> 
> runes at 
> 
> -- 
> Cheers,
> 
> R.
> 
> 
> 
> 
> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.
> 
> 
> 
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 16 22:25:07 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 16 Feb 2014 22:25: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 1WFA8y-00012Y-RZ; Sun, 16 Feb 2014 22:25:00 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFA8x-00012S-Bm
	for mirageos-devel@lists.xenproject.org; Sun, 16 Feb 2014 22:24:59 +0000
Received: from [85.158.143.35:48338] by server-1.bemta-4.messagelabs.com id
	1C/02-31661-ABA31035; Sun, 16 Feb 2014 22:24:58 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-7.tower-21.messagelabs.com!1392589497!6069714!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21586 invoked from network); 16 Feb 2014 22:24:57 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-7.tower-21.messagelabs.com with SMTP;
	16 Feb 2014 22:24:57 -0000
Received: (qmail 20518 invoked by uid 634); 16 Feb 2014 22:24:57 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sun, 16 Feb 2014 22:24:56 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <4BB4F85D-7E19-4C4E-BDB0-4E04895EE76F@nottingham.ac.uk>
Date: Sun, 16 Feb 2014 22:24:55 +0000
Message-Id: 
References: <4BB4F85D-7E19-4C4E-BDB0-4E04895EE76F@nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] xen on virtualbox for development
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Nice!  Could you move the repo over to mirage/mirage-vagrant-vms, and I'll merge in the OPAM doc stuff as well?

-a

On 15 Feb 2014, at 21:45, Richard Mortier  wrote:

> hi all;
> 
> fwiw i've collated some runes for building a virtualbox VM on OSX that installs and configures opam and mirage in a debian wheezy xen dom0 using vagrant and veewee. (as i understood on the last mirage call that this is the "recommended" xen configuration for mirage -- someone tell me otherwise if i've got this wrong!)
> 
> i thought they might be of some use for others who also wish to test mirage xen vms on their local machines but who can't boot to xen directly. the vagrant and veewee installation runes are probably OSX specific, but i'd hope that most of the vm setup would be applicable to any virtualbox install. i've successfully run most of the mirage-skeleton samples under this config.
> 
> runes at 
> 
> -- 
> Cheers,
> 
> R.
> 
> 
> 
> 
> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.
> 
> 
> 
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 16 22:37:32 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 16 Feb 2014 22:37: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 1WFAL3-000173-Qn; Sun, 16 Feb 2014 22:37:29 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFAL2-00016y-Ef
	for mirageos-devel@lists.xenproject.org; Sun, 16 Feb 2014 22:37:28 +0000
Received: from [85.158.139.211:62346] by server-16.bemta-5.messagelabs.com id
	2A/11-05060-7AD31035; Sun, 16 Feb 2014 22:37:27 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-7.tower-206.messagelabs.com!1392590246!4282225!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7380 invoked from network); 16 Feb 2014 22:37:26 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-7.tower-206.messagelabs.com with SMTP;
	16 Feb 2014 22:37:26 -0000
Received: (qmail 21847 invoked by uid 634); 16 Feb 2014 22:37:26 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sun, 16 Feb 2014 22:37:22 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <52FF9063.4060408@mehnert.org>
Date: Sun, 16 Feb 2014 22:37:19 +0000
Message-Id: 
References: <52FF9063.4060408@mehnert.org>
To: Hannes Mehnert 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Balraj Singh ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage-tcpip Fin/Fin-Ack
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 15 Feb 2014, at 16:05, Hannes Mehnert  wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA384
> 
> Hey,
> 
> first of all: thanks for your great work on mirage. It is an awesome
> project.
> 
> While writing some mirage code, I discovered that the TCP layer sends
> a duplicate ack after a fin (which is fin + ack):
> 
> client --SYN-(seq=0)-> mirage
> mirage --SYN-ACK-(seq=0,ack=1)-> client
> client --ACK-(seq=1,ack=1)-> mirage
> client --data-(seq=1,len=7)-> mirage
> mirage --FIN-ACK-(seq=1,ack=8)-> client
> mirage --ACK-(seq=2,ack=8)-> client
> client --ACK-(seq=8,ack=2)-> mirage
> client --FIN-ACK-(seq=8,ack=2)-> mirage
> mirage --ACK-(seq=2,ack=9)-> client
> 
> 
> This happens already with the network-skeleton/network code, running
> on unix (FreeBSD) with a tap interface. I've uploaded a pcap file with
> the tcp connection to https://berlin.ccc.de/~hannes/mirage-network.pcap .
> 
> Unfortunately I wasn't able to spot the piece of code responsible for
> sending the duplicated ack.

I'll need to do a bit more digging here to pin this down, as the duplicate
ACK code has bounced between Balraj and me in recent months. 

-anil


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 16 22:37:32 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 16 Feb 2014 22:37: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 1WFAL3-000173-Qn; Sun, 16 Feb 2014 22:37:29 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFAL2-00016y-Ef
	for mirageos-devel@lists.xenproject.org; Sun, 16 Feb 2014 22:37:28 +0000
Received: from [85.158.139.211:62346] by server-16.bemta-5.messagelabs.com id
	2A/11-05060-7AD31035; Sun, 16 Feb 2014 22:37:27 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-7.tower-206.messagelabs.com!1392590246!4282225!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7380 invoked from network); 16 Feb 2014 22:37:26 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-7.tower-206.messagelabs.com with SMTP;
	16 Feb 2014 22:37:26 -0000
Received: (qmail 21847 invoked by uid 634); 16 Feb 2014 22:37:26 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sun, 16 Feb 2014 22:37:22 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <52FF9063.4060408@mehnert.org>
Date: Sun, 16 Feb 2014 22:37:19 +0000
Message-Id: 
References: <52FF9063.4060408@mehnert.org>
To: Hannes Mehnert 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Balraj Singh ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage-tcpip Fin/Fin-Ack
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 15 Feb 2014, at 16:05, Hannes Mehnert  wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA384
> 
> Hey,
> 
> first of all: thanks for your great work on mirage. It is an awesome
> project.
> 
> While writing some mirage code, I discovered that the TCP layer sends
> a duplicate ack after a fin (which is fin + ack):
> 
> client --SYN-(seq=0)-> mirage
> mirage --SYN-ACK-(seq=0,ack=1)-> client
> client --ACK-(seq=1,ack=1)-> mirage
> client --data-(seq=1,len=7)-> mirage
> mirage --FIN-ACK-(seq=1,ack=8)-> client
> mirage --ACK-(seq=2,ack=8)-> client
> client --ACK-(seq=8,ack=2)-> mirage
> client --FIN-ACK-(seq=8,ack=2)-> mirage
> mirage --ACK-(seq=2,ack=9)-> client
> 
> 
> This happens already with the network-skeleton/network code, running
> on unix (FreeBSD) with a tap interface. I've uploaded a pcap file with
> the tcp connection to https://berlin.ccc.de/~hannes/mirage-network.pcap .
> 
> Unfortunately I wasn't able to spot the piece of code responsible for
> sending the duplicated ack.

I'll need to do a bit more digging here to pin this down, as the duplicate
ACK code has bounced between Balraj and me in recent months. 

-anil


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 16 23:14:20 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 16 Feb 2014 23:14:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFAuf-0001S8-9t; Sun, 16 Feb 2014 23:14:17 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFAlc-0001PQ-Fz
	for mirageos-devel@lists.xenproject.org; Sun, 16 Feb 2014 23:04:56 +0000
Received: from [85.158.139.211:14099] by server-17.bemta-5.messagelabs.com id
	B3/7E-31975-71441035; Sun, 16 Feb 2014 23:04:55 +0000
X-Env-Sender: balraj885@gmail.com
X-Msg-Ref: server-6.tower-206.messagelabs.com!1392591894!4244748!1
X-Originating-IP: [209.85.217.170]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7136 invoked from network); 16 Feb 2014 23:04:54 -0000
Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com)
	(209.85.217.170)
	by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	16 Feb 2014 23:04:54 -0000
Received: by mail-lb0-f170.google.com with SMTP id u14so10881544lbd.1
	for ;
	Sun, 16 Feb 2014 15:04:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date:message-id:subject
	:from:to:cc:content-type;
	bh=dinIkQQwGOLVd9lFrGijqAoGH8XPgI4D3Jc9UEYvbmc=;
	b=lHcvXMefITFMlJ77sR1CE53enD28sxRKEDa4qDW0r6+hfbMuzbXUBNBA1n6a86rLso
	GKSfOG4/QR6oXaCfKgcEBozyy0VI1MTXyg8v66Jaiuk4CcDhs9D6uOBU+FF4ZKVDdSE/
	OmHiJxlcNuzSIwh0zSfnjF5n1T89cue19Sn6TKNb8ibHpzXQWFroCMVdwbwHlxoEJA1t
	I5hjfqXJFnoRCtLX0rbOJGj3OypRfw2X6UKdurBKOX62JIaZB3IQmIdss8iahpCx7fNx
	xn0qlscNCs8rFvi/nliS2yQ+J8Gj8x63nQmPfDPHXIbswmb4zl9i3gcpA4jHGCzVcTuc
	oZqw==
MIME-Version: 1.0
X-Received: by 10.152.6.199 with SMTP id d7mr15383935laa.22.1392591893966;
	Sun, 16 Feb 2014 15:04:53 -0800 (PST)
Received: by 10.112.34.206 with HTTP; Sun, 16 Feb 2014 15:04:53 -0800 (PST)
In-Reply-To: 
References: <52FF9063.4060408@mehnert.org>
	
Date: Sun, 16 Feb 2014 23:04:53 +0000
X-Google-Sender-Auth: XGKXb_xkRYF3RAJ-RhZc4Y9Lhzg
Message-ID: 
From: Balraj Singh 
To: Anil Madhavapeddy 
X-Mailman-Approved-At: Sun, 16 Feb 2014 23:14:00 +0000
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage-tcpip Fin/Fin-Ack
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7403933424762767513=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============7403933424762767513==
Content-Type: multipart/alternative; boundary=089e013d1d9628358004f28e1113

--089e013d1d9628358004f28e1113
Content-Type: text/plain; charset=ISO-8859-1

Many thanks for this.  I know about this extra ACK at the end.  It comes
from an interaction of the teardown machinery with the normal ACK
mechanism.  A quick attempt to fix it occasionally caused an ack to not be
sent, which was much worse.  So for the moment I have left it like this
thinking of it as a mild annoyance, but harmless.  Will work on a fix
shortly.

Balraj

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


Many thanks for this. =A0I know about this extra ACK at th=
e end. =A0It comes from an interaction of the teardown machinery with the n=
ormal ACK mechanism. =A0A quick attempt to fix it occasionally caused an ac=
k to not be sent, which was much worse. =A0So for the moment I have left it=
 like this thinking of it as a mild annoyance, but harmless. =A0Will work o=
n a fix shortly.


Balraj


--089e013d1d9628358004f28e1113--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============7403933424762767513==--


From mirageos-devel-bounces@lists.xenproject.org Sun Feb 16 23:14:20 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 16 Feb 2014 23:14:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFAuf-0001S8-9t; Sun, 16 Feb 2014 23:14:17 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFAlc-0001PQ-Fz
	for mirageos-devel@lists.xenproject.org; Sun, 16 Feb 2014 23:04:56 +0000
Received: from [85.158.139.211:14099] by server-17.bemta-5.messagelabs.com id
	B3/7E-31975-71441035; Sun, 16 Feb 2014 23:04:55 +0000
X-Env-Sender: balraj885@gmail.com
X-Msg-Ref: server-6.tower-206.messagelabs.com!1392591894!4244748!1
X-Originating-IP: [209.85.217.170]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE,
	RCVD_BY_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7136 invoked from network); 16 Feb 2014 23:04:54 -0000
Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com)
	(209.85.217.170)
	by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	16 Feb 2014 23:04:54 -0000
Received: by mail-lb0-f170.google.com with SMTP id u14so10881544lbd.1
	for ;
	Sun, 16 Feb 2014 15:04:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date:message-id:subject
	:from:to:cc:content-type;
	bh=dinIkQQwGOLVd9lFrGijqAoGH8XPgI4D3Jc9UEYvbmc=;
	b=lHcvXMefITFMlJ77sR1CE53enD28sxRKEDa4qDW0r6+hfbMuzbXUBNBA1n6a86rLso
	GKSfOG4/QR6oXaCfKgcEBozyy0VI1MTXyg8v66Jaiuk4CcDhs9D6uOBU+FF4ZKVDdSE/
	OmHiJxlcNuzSIwh0zSfnjF5n1T89cue19Sn6TKNb8ibHpzXQWFroCMVdwbwHlxoEJA1t
	I5hjfqXJFnoRCtLX0rbOJGj3OypRfw2X6UKdurBKOX62JIaZB3IQmIdss8iahpCx7fNx
	xn0qlscNCs8rFvi/nliS2yQ+J8Gj8x63nQmPfDPHXIbswmb4zl9i3gcpA4jHGCzVcTuc
	oZqw==
MIME-Version: 1.0
X-Received: by 10.152.6.199 with SMTP id d7mr15383935laa.22.1392591893966;
	Sun, 16 Feb 2014 15:04:53 -0800 (PST)
Received: by 10.112.34.206 with HTTP; Sun, 16 Feb 2014 15:04:53 -0800 (PST)
In-Reply-To: 
References: <52FF9063.4060408@mehnert.org>
	
Date: Sun, 16 Feb 2014 23:04:53 +0000
X-Google-Sender-Auth: XGKXb_xkRYF3RAJ-RhZc4Y9Lhzg
Message-ID: 
From: Balraj Singh 
To: Anil Madhavapeddy 
X-Mailman-Approved-At: Sun, 16 Feb 2014 23:14:00 +0000
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage-tcpip Fin/Fin-Ack
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============7403933424762767513=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============7403933424762767513==
Content-Type: multipart/alternative; boundary=089e013d1d9628358004f28e1113

--089e013d1d9628358004f28e1113
Content-Type: text/plain; charset=ISO-8859-1

Many thanks for this.  I know about this extra ACK at the end.  It comes
from an interaction of the teardown machinery with the normal ACK
mechanism.  A quick attempt to fix it occasionally caused an ack to not be
sent, which was much worse.  So for the moment I have left it like this
thinking of it as a mild annoyance, but harmless.  Will work on a fix
shortly.

Balraj

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


Many thanks for this. =A0I know about this extra ACK at th=
e end. =A0It comes from an interaction of the teardown machinery with the n=
ormal ACK mechanism. =A0A quick attempt to fix it occasionally caused an ac=
k to not be sent, which was much worse. =A0So for the moment I have left it=
 like this thinking of it as a mild annoyance, but harmless. =A0Will work o=
n a fix shortly.


Balraj


--089e013d1d9628358004f28e1113--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============7403933424762767513==--


From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 11:28:27 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 11:28:27 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFMN4-0004H9-G7; Mon, 17 Feb 2014 11:28:22 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFMN2-0004H4-V2
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 11:28:21 +0000
Received: from [85.158.137.68:28132] by server-10.bemta-3.messagelabs.com id
	07/D2-07302-452F1035; Mon, 17 Feb 2014 11:28:20 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-6.tower-31.messagelabs.com!1392636499!2333269!1
X-Originating-IP: [93.95.15.169]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13357 invoked from network); 17 Feb 2014 11:28:19 -0000
Received: from engine01-20433-1.icritical.com (HELO
	engine01-20433-1.icritical.com) (93.95.15.169)
	by server-6.tower-31.messagelabs.com with SMTP;
	17 Feb 2014 11:28:19 -0000
Received: (qmail 29241 invoked from network); 17 Feb 2014 11:28:27 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-1.icritical.com with SMTP; 17 Feb 2014 11:28:27 -0000
Received: from engine01-20433-1.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 29020-06 for ;
	Mon, 17 Feb 2014 11:28:26 +0000 (GMT)
Received: (qmail 26980 invoked by uid 599); 17 Feb 2014 11:26:23 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP;
	Mon, 17 Feb 2014 11:26:23 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WFML2-00010Q-ED; Mon, 17 Feb 2014 11:26:16 +0000
From: Richard Mortier 
To: Anil Madhavapeddy 
Date: Mon, 17 Feb 2014 11:26:16 +0000
Thread-Topic: [MirageOS-devel] xen on virtualbox for development
Thread-Index: Ac8r0xIDwp8yl/8NR4+hHODIgQZZMg==
Message-ID: 
References: <4BB4F85D-7E19-4C4E-BDB0-4E04895EE76F@nottingham.ac.uk>
	
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] xen on virtualbox for development
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

done -- mirage/mirage-vagrant-vms it is.


On 16 Feb 2014, at 22:24, Anil Madhavapeddy  wrote:

> Nice!  Could you move the repo over to mirage/mirage-vagrant-vms, and I'll merge in the OPAM doc stuff as well?
> 
> -a
> 
> On 15 Feb 2014, at 21:45, Richard Mortier  wrote:
> 
>> hi all;
>> 
>> fwiw i've collated some runes for building a virtualbox VM on OSX that installs and configures opam and mirage in a debian wheezy xen dom0 using vagrant and veewee. (as i understood on the last mirage call that this is the "recommended" xen configuration for mirage -- someone tell me otherwise if i've got this wrong!)
>> 
>> i thought they might be of some use for others who also wish to test mirage xen vms on their local machines but who can't boot to xen directly. the vagrant and veewee installation runes are probably OSX specific, but i'd hope that most of the vm setup would be applicable to any virtualbox install. i've successfully run most of the mirage-skeleton samples under this config.
>> 
>> runes at 
>> 
>> -- 
>> Cheers,
>> 
>> R.
>> 
>> 
>> 
>> 
>> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
>> 
>> This message has been checked for viruses but the contents of an attachment
>> may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
> 


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 11:28:27 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 11:28:27 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFMN4-0004H9-G7; Mon, 17 Feb 2014 11:28:22 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFMN2-0004H4-V2
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 11:28:21 +0000
Received: from [85.158.137.68:28132] by server-10.bemta-3.messagelabs.com id
	07/D2-07302-452F1035; Mon, 17 Feb 2014 11:28:20 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-6.tower-31.messagelabs.com!1392636499!2333269!1
X-Originating-IP: [93.95.15.169]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13357 invoked from network); 17 Feb 2014 11:28:19 -0000
Received: from engine01-20433-1.icritical.com (HELO
	engine01-20433-1.icritical.com) (93.95.15.169)
	by server-6.tower-31.messagelabs.com with SMTP;
	17 Feb 2014 11:28:19 -0000
Received: (qmail 29241 invoked from network); 17 Feb 2014 11:28:27 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-1.icritical.com with SMTP; 17 Feb 2014 11:28:27 -0000
Received: from engine01-20433-1.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 29020-06 for ;
	Mon, 17 Feb 2014 11:28:26 +0000 (GMT)
Received: (qmail 26980 invoked by uid 599); 17 Feb 2014 11:26:23 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP;
	Mon, 17 Feb 2014 11:26:23 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WFML2-00010Q-ED; Mon, 17 Feb 2014 11:26:16 +0000
From: Richard Mortier 
To: Anil Madhavapeddy 
Date: Mon, 17 Feb 2014 11:26:16 +0000
Thread-Topic: [MirageOS-devel] xen on virtualbox for development
Thread-Index: Ac8r0xIDwp8yl/8NR4+hHODIgQZZMg==
Message-ID: 
References: <4BB4F85D-7E19-4C4E-BDB0-4E04895EE76F@nottingham.ac.uk>
	
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] xen on virtualbox for development
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

done -- mirage/mirage-vagrant-vms it is.


On 16 Feb 2014, at 22:24, Anil Madhavapeddy  wrote:

> Nice!  Could you move the repo over to mirage/mirage-vagrant-vms, and I'll merge in the OPAM doc stuff as well?
> 
> -a
> 
> On 15 Feb 2014, at 21:45, Richard Mortier  wrote:
> 
>> hi all;
>> 
>> fwiw i've collated some runes for building a virtualbox VM on OSX that installs and configures opam and mirage in a debian wheezy xen dom0 using vagrant and veewee. (as i understood on the last mirage call that this is the "recommended" xen configuration for mirage -- someone tell me otherwise if i've got this wrong!)
>> 
>> i thought they might be of some use for others who also wish to test mirage xen vms on their local machines but who can't boot to xen directly. the vagrant and veewee installation runes are probably OSX specific, but i'd hope that most of the vm setup would be applicable to any virtualbox install. i've successfully run most of the mirage-skeleton samples under this config.
>> 
>> runes at 
>> 
>> -- 
>> Cheers,
>> 
>> R.
>> 
>> 
>> 
>> 
>> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
>> 
>> This message has been checked for viruses but the contents of an attachment
>> may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
> 


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 15:46:24 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 15:46: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 1WFQOg-0004QA-Uh; Mon, 17 Feb 2014 15:46:18 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFQIF-000488-8Y
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 15:39:39 +0000
Received: from [193.109.254.147:32810] by server-7.bemta-14.messagelabs.com id
	1B/49-23424-A3D22035; Mon, 17 Feb 2014 15:39:38 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-15.tower-27.messagelabs.com!1392651577!4871967!1
X-Originating-IP: [74.125.82.47]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16144 invoked from network); 17 Feb 2014 15:39:37 -0000
Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com)
	(74.125.82.47)
	by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Feb 2014 15:39:37 -0000
Received: by mail-wg0-f47.google.com with SMTP id k14so2346702wgh.26
	for ;
	Mon, 17 Feb 2014 07:39:37 -0800 (PST)
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=2+96d+0AA/vEERDIWnR/W4Bk/Ndo9AZDzFVMz9We0o4=;
	b=MCTeM5zrEpNJD2Q6iQ7588fM+ePm/b3bBnu7JwmMKhW0972AbJrnxqnrsvEwmamTdX
	L1ZB1gXucHtt8iWn6W9kPXPvDyRGSKEyS8A1S/cF0oPZ46vq80ahcbCmFxBGfvpK0fp5
	FRgj/WC2TEwb6lxICi5zN8vkp5F/ZOlzc1hJ+BdaGVqH0aH1BHf4v7pg3zO6eVqI5bl8
	+ddq0NaWPIqllORDhvg+NQW7dgULA8fQuGxKDRR5hbBnnTEh2A8uu7+FZTR22BjNkBKG
	oKFb0Io9sc/AfnFvSVsK8GIjLHRLttoOJbHUZu082WSAzhciuvPokrWXo75GmYDjhFMT
	mvxg==
X-Received: by 10.194.123.201 with SMTP id mc9mr13897417wjb.43.1392651577179; 
	Mon, 17 Feb 2014 07:39:37 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id
	q15sm37788675wjw.18.2014.02.17.07.39.35 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 17 Feb 2014 07:39:36 -0800 (PST)
Message-ID: <53022D35.8050704@xen.org>
Date: Mon, 17 Feb 2014 15:39:33 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ian Jackson , =?ISO-8859-1?Q?Roger_Pau_?=
	=?ISO-8859-1?Q?Monn=E9?= 
References: <52DCE9FA.6010400@xen.org>	<52E7B6AF.3050604@xen.org>	<1391609348.6497.178.camel@kazak.uk.xensource.com>	<52FBA331.9040004@citrix.com>
	<21244.64811.826482.435714@mariner.uk.xensource.com>
In-Reply-To: <21244.64811.826482.435714@mariner.uk.xensource.com>
X-Mailman-Approved-At: Mon, 17 Feb 2014 15:46:18 +0000
Cc: Ben Guthro ,
	Ian Campbell ,
	Konrad Rzeszutek Wilk ,
	Andrew Cooper ,
	Dario Faggioli ,
	"xen-devel@lists.xen.org" ,
	mirageos-devel@lists.xenproject.org,
	Paul Durrant ,
	Santosh Jodh ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi all,

I just combed through the list of projects, and to be honest most can be =

improved.

Please put yourself into the shoes of someone who
a) is a student and
b) has not worked on Xen before.
* If you use acronyms, please point to the definitions.
* If you refer to specs, please link to the specs.
* If you refer to a location to the code, why not link to it.
c) breaking down the project into more manageable chunks will also help

Anyway, Google is reviewing applications this week. Changes to the =

project page that are made this week will still make an impact. Accepted =

orgs are announced on the 24th.

Regards
Lars

On 13/02/2014 17:13, Ian Jackson wrote:
> Roger Pau Monn=E9 writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT=
] - deadline Feb 14 2014"):
>> On 05/02/14 15:09, Ian Campbell wrote:
>>> Roger:
>>>        * Refactor Linux hotplug scripts
>>>
>>>          You did some of this I think?
>> No, I've added a block-iscsi script, but I did not refactor the other
>> ones. It is still valid, however, I'm not sure it's attractive from a
>> GSoC point of view. I'm going to leave it anyway in case someone is
>> interested.
> Who is actually submitting our GSOC application ?
>
> Ian.


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 15:46:24 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 15:46: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 1WFQOg-0004Q1-Sm; Mon, 17 Feb 2014 15:46:18 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFPvO-0003BR-Lu
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 15:16:02 +0000
Received: from [85.158.143.35:57731] by server-1.bemta-4.messagelabs.com id
	41/F4-31661-1B722035; Mon, 17 Feb 2014 15:16:01 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-14.tower-21.messagelabs.com!1392650161!6284584!1
X-Originating-IP: [74.125.82.179]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6074 invoked from network); 17 Feb 2014 15:16:01 -0000
Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com)
	(74.125.82.179)
	by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Feb 2014 15:16:01 -0000
Received: by mail-we0-f179.google.com with SMTP id q58so10612898wes.38
	for ;
	Mon, 17 Feb 2014 07:16:00 -0800 (PST)
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=Pjmmfni50TU1RJp2sPwWZVgmYyOg26wWIPfZ/xJ6rqk=;
	b=oTQsde3pQ/mopyJqBTlx29xIneuYKZIgD7pOhJnPGL48FEOk7Dd6gVwFKPDezFQHfB
	KxB/7NZ0CReqNFTvHVkW8o8Qi56s4i9i+8sH+znhdUaJ2utdMb5Hg2VoivLkrp49p+Bi
	GfPRe3q59+nD/zAtuhXo27+NwFkmZLKfoCkZ5HQOq+nGa8klQXF7F4cgFht8VjLhWoqG
	8AQ6Ef/vePfcO+GnBYCqmmOunLPs97DAnNhHkxseNtyvoVqxOhsMQjTRoux/U7UYrh92
	mCnRsPbXX75R7qkuTQ2VL24L1ReLlblC9bOGsG3EFR9phV97aNN5tjR4glUcASGoBQBI
	SQmg==
X-Received: by 10.194.82.105 with SMTP id h9mr2586871wjy.52.1392650160432;
	Mon, 17 Feb 2014 07:16:00 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id j9sm37622567wjz.13.2014.02.17.07.15.58
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 17 Feb 2014 07:15:59 -0800 (PST)
Message-ID: <530227AE.2090609@xen.org>
Date: Mon, 17 Feb 2014 15:15:58 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ian Jackson , =?ISO-8859-1?Q?Roger_Pau_?=
	=?ISO-8859-1?Q?Monn=E9?= 
References: <52DCE9FA.6010400@xen.org>	<52E7B6AF.3050604@xen.org>	<1391609348.6497.178.camel@kazak.uk.xensource.com>	<52FBA331.9040004@citrix.com>
	<21244.64811.826482.435714@mariner.uk.xensource.com>
In-Reply-To: <21244.64811.826482.435714@mariner.uk.xensource.com>
X-Mailman-Approved-At: Mon, 17 Feb 2014 15:46:18 +0000
Cc: Ben Guthro ,
	Ian Campbell ,
	Konrad Rzeszutek Wilk ,
	Andrew Cooper ,
	Dario Faggioli ,
	"xen-devel@lists.xen.org" ,
	mirageos-devel@lists.xenproject.org,
	Paul Durrant ,
	Santosh Jodh ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 13/02/2014 17:13, Ian Jackson wrote:
> Roger Pau Monn=E9 writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT=
] - deadline Feb 14 2014"):
>> On 05/02/14 15:09, Ian Campbell wrote:
>>> Roger:
>>>        * Refactor Linux hotplug scripts
>>>
>>>          You did some of this I think?
>> No, I've added a block-iscsi script, but I did not refactor the other
>> ones. It is still valid, however, I'm not sure it's attractive from a
>> GSoC point of view. I'm going to leave it anyway in case someone is
>> interested.
> Who is actually submitting our GSOC application ?
>
> Ian.
I have submitted it.  Please continue working on and refining =

http://wiki.xen.org/wiki/GSoc_2014
If you feel that a project should be moved into =

http://wiki.xen.org/wiki/GSoc_2014#List_of_peer_reviewed_Projects please =

do so

Regards
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 15:46:24 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 15:46: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 1WFQOg-0004QA-Uh; Mon, 17 Feb 2014 15:46:18 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFQIF-000488-8Y
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 15:39:39 +0000
Received: from [193.109.254.147:32810] by server-7.bemta-14.messagelabs.com id
	1B/49-23424-A3D22035; Mon, 17 Feb 2014 15:39:38 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-15.tower-27.messagelabs.com!1392651577!4871967!1
X-Originating-IP: [74.125.82.47]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16144 invoked from network); 17 Feb 2014 15:39:37 -0000
Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com)
	(74.125.82.47)
	by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Feb 2014 15:39:37 -0000
Received: by mail-wg0-f47.google.com with SMTP id k14so2346702wgh.26
	for ;
	Mon, 17 Feb 2014 07:39:37 -0800 (PST)
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=2+96d+0AA/vEERDIWnR/W4Bk/Ndo9AZDzFVMz9We0o4=;
	b=MCTeM5zrEpNJD2Q6iQ7588fM+ePm/b3bBnu7JwmMKhW0972AbJrnxqnrsvEwmamTdX
	L1ZB1gXucHtt8iWn6W9kPXPvDyRGSKEyS8A1S/cF0oPZ46vq80ahcbCmFxBGfvpK0fp5
	FRgj/WC2TEwb6lxICi5zN8vkp5F/ZOlzc1hJ+BdaGVqH0aH1BHf4v7pg3zO6eVqI5bl8
	+ddq0NaWPIqllORDhvg+NQW7dgULA8fQuGxKDRR5hbBnnTEh2A8uu7+FZTR22BjNkBKG
	oKFb0Io9sc/AfnFvSVsK8GIjLHRLttoOJbHUZu082WSAzhciuvPokrWXo75GmYDjhFMT
	mvxg==
X-Received: by 10.194.123.201 with SMTP id mc9mr13897417wjb.43.1392651577179; 
	Mon, 17 Feb 2014 07:39:37 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id
	q15sm37788675wjw.18.2014.02.17.07.39.35 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 17 Feb 2014 07:39:36 -0800 (PST)
Message-ID: <53022D35.8050704@xen.org>
Date: Mon, 17 Feb 2014 15:39:33 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ian Jackson , =?ISO-8859-1?Q?Roger_Pau_?=
	=?ISO-8859-1?Q?Monn=E9?= 
References: <52DCE9FA.6010400@xen.org>	<52E7B6AF.3050604@xen.org>	<1391609348.6497.178.camel@kazak.uk.xensource.com>	<52FBA331.9040004@citrix.com>
	<21244.64811.826482.435714@mariner.uk.xensource.com>
In-Reply-To: <21244.64811.826482.435714@mariner.uk.xensource.com>
X-Mailman-Approved-At: Mon, 17 Feb 2014 15:46:18 +0000
Cc: Ben Guthro ,
	Ian Campbell ,
	Konrad Rzeszutek Wilk ,
	Andrew Cooper ,
	Dario Faggioli ,
	"xen-devel@lists.xen.org" ,
	mirageos-devel@lists.xenproject.org,
	Paul Durrant ,
	Santosh Jodh ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi all,

I just combed through the list of projects, and to be honest most can be =

improved.

Please put yourself into the shoes of someone who
a) is a student and
b) has not worked on Xen before.
* If you use acronyms, please point to the definitions.
* If you refer to specs, please link to the specs.
* If you refer to a location to the code, why not link to it.
c) breaking down the project into more manageable chunks will also help

Anyway, Google is reviewing applications this week. Changes to the =

project page that are made this week will still make an impact. Accepted =

orgs are announced on the 24th.

Regards
Lars

On 13/02/2014 17:13, Ian Jackson wrote:
> Roger Pau Monn=E9 writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT=
] - deadline Feb 14 2014"):
>> On 05/02/14 15:09, Ian Campbell wrote:
>>> Roger:
>>>        * Refactor Linux hotplug scripts
>>>
>>>          You did some of this I think?
>> No, I've added a block-iscsi script, but I did not refactor the other
>> ones. It is still valid, however, I'm not sure it's attractive from a
>> GSoC point of view. I'm going to leave it anyway in case someone is
>> interested.
> Who is actually submitting our GSOC application ?
>
> Ian.


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 15:46:24 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 15:46: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 1WFQOg-0004Q1-Sm; Mon, 17 Feb 2014 15:46:18 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFPvO-0003BR-Lu
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 15:16:02 +0000
Received: from [85.158.143.35:57731] by server-1.bemta-4.messagelabs.com id
	41/F4-31661-1B722035; Mon, 17 Feb 2014 15:16:01 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-14.tower-21.messagelabs.com!1392650161!6284584!1
X-Originating-IP: [74.125.82.179]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6074 invoked from network); 17 Feb 2014 15:16:01 -0000
Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com)
	(74.125.82.179)
	by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Feb 2014 15:16:01 -0000
Received: by mail-we0-f179.google.com with SMTP id q58so10612898wes.38
	for ;
	Mon, 17 Feb 2014 07:16:00 -0800 (PST)
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=Pjmmfni50TU1RJp2sPwWZVgmYyOg26wWIPfZ/xJ6rqk=;
	b=oTQsde3pQ/mopyJqBTlx29xIneuYKZIgD7pOhJnPGL48FEOk7Dd6gVwFKPDezFQHfB
	KxB/7NZ0CReqNFTvHVkW8o8Qi56s4i9i+8sH+znhdUaJ2utdMb5Hg2VoivLkrp49p+Bi
	GfPRe3q59+nD/zAtuhXo27+NwFkmZLKfoCkZ5HQOq+nGa8klQXF7F4cgFht8VjLhWoqG
	8AQ6Ef/vePfcO+GnBYCqmmOunLPs97DAnNhHkxseNtyvoVqxOhsMQjTRoux/U7UYrh92
	mCnRsPbXX75R7qkuTQ2VL24L1ReLlblC9bOGsG3EFR9phV97aNN5tjR4glUcASGoBQBI
	SQmg==
X-Received: by 10.194.82.105 with SMTP id h9mr2586871wjy.52.1392650160432;
	Mon, 17 Feb 2014 07:16:00 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id j9sm37622567wjz.13.2014.02.17.07.15.58
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 17 Feb 2014 07:15:59 -0800 (PST)
Message-ID: <530227AE.2090609@xen.org>
Date: Mon, 17 Feb 2014 15:15:58 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ian Jackson , =?ISO-8859-1?Q?Roger_Pau_?=
	=?ISO-8859-1?Q?Monn=E9?= 
References: <52DCE9FA.6010400@xen.org>	<52E7B6AF.3050604@xen.org>	<1391609348.6497.178.camel@kazak.uk.xensource.com>	<52FBA331.9040004@citrix.com>
	<21244.64811.826482.435714@mariner.uk.xensource.com>
In-Reply-To: <21244.64811.826482.435714@mariner.uk.xensource.com>
X-Mailman-Approved-At: Mon, 17 Feb 2014 15:46:18 +0000
Cc: Ben Guthro ,
	Ian Campbell ,
	Konrad Rzeszutek Wilk ,
	Andrew Cooper ,
	Dario Faggioli ,
	"xen-devel@lists.xen.org" ,
	mirageos-devel@lists.xenproject.org,
	Paul Durrant ,
	Santosh Jodh ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] Prepping for GSOC 2014 [URGENT] -
 deadline Feb 14 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 13/02/2014 17:13, Ian Jackson wrote:
> Roger Pau Monn=E9 writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT=
] - deadline Feb 14 2014"):
>> On 05/02/14 15:09, Ian Campbell wrote:
>>> Roger:
>>>        * Refactor Linux hotplug scripts
>>>
>>>          You did some of this I think?
>> No, I've added a block-iscsi script, but I did not refactor the other
>> ones. It is still valid, however, I'm not sure it's attractive from a
>> GSoC point of view. I'm going to leave it anyway in case someone is
>> interested.
> Who is actually submitting our GSOC application ?
>
> Ian.
I have submitted it.  Please continue working on and refining =

http://wiki.xen.org/wiki/GSoc_2014
If you feel that a project should be moved into =

http://wiki.xen.org/wiki/GSoc_2014#List_of_peer_reviewed_Projects please =

do so

Regards
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 15:46:57 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 15:46:57 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFQPJ-0004SK-1h; Mon, 17 Feb 2014 15:46:57 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFQ7U-0003iZ-7C
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 15:28:32 +0000
Received: from [85.158.143.35:50390] by server-1.bemta-4.messagelabs.com id
	04/3C-31661-F9A22035; Mon, 17 Feb 2014 15:28:31 +0000
X-Env-Sender: yallop@gmail.com
X-Msg-Ref: server-12.tower-21.messagelabs.com!1392650909!6285599!1
X-Originating-IP: [209.85.216.46]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25409 invoked from network); 17 Feb 2014 15:28:30 -0000
Received: from mail-qa0-f46.google.com (HELO mail-qa0-f46.google.com)
	(209.85.216.46)
	by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Feb 2014 15:28:30 -0000
Received: by mail-qa0-f46.google.com with SMTP id k15so8647989qaq.33
	for ;
	Mon, 17 Feb 2014 07:28:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=UpIgl1MnXSYEWhfzegsANszHQQAvfaeJxqB0D488dL0=;
	b=CUP9zbBYjRkt+XbLrdFvyUtgeDqaNVTK1RBxkPDR9lNk7tTqC95EjRalR7C+IxF4pV
	/L4qDB4B/KVCxMuQu0fuYEEmhWZ2J5QeSYof+aGSSUBnPdVCu6BQzvIwnf8lq1Yjhv/K
	cjJ2es0YFmQDu0v+00z2N6dUUY/edXmWeUSEB4W4AVdYfEhzPMFABWLUsvbNPKxoJwrm
	ZL4BGbXkpB6ridC5KDKVDbImqylZiMjdQKS5bmYdfybUXgvnvu3gN6CNws3K72aHOnXn
	V3wO1vNvo4ALj6Wpl57Vj/ntmBmGImJXHyOf6+/IgNp0Sv+KiYyafe92u0/cuj+IOQ1f
	PwxQ==
MIME-Version: 1.0
X-Received: by 10.140.94.214 with SMTP id g80mr33540971qge.19.1392650909282;
	Mon, 17 Feb 2014 07:28:29 -0800 (PST)
Received: by 10.229.131.65 with HTTP; Mon, 17 Feb 2014 07:28:29 -0800 (PST)
In-Reply-To: 
References: 
Date: Mon, 17 Feb 2014 15:28:29 +0000
Message-ID: 
From: Jeremy Yallop 
To: "cl-ocamllabs-staff@lists.cam.ac.uk" , 
	cam-compiler-hacking@lists.ocaml.org, mirageos-devel@lists.xenproject.org
X-Mailman-Approved-At: Mon, 17 Feb 2014 15:46:55 +0000
Subject: Re: [MirageOS-devel] OCaml compiler hacking session
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Reminder: the OCaml compiler hacking session will take place from 6pm
tomorrow in FW11.  If you're planning to come along, please add your
name to the list:

    http://doodle.com/5tk8rs5k3mh82qqx

On 11 February 2014 18:36, Jeremy Yallop  wrote:
> It's time for the fourth Cambridge OCaml compiler-hacking session!
> We'll be meeting in the Computer Lab again next Tuesday evening.
>
> If you're planning to come along, it'd be helpful if you could
> indicate interest via Doodle:
>
>     http://doodle.com/5tk8rs5k3mh82qqx
>
> and sign up to the mailing list to receive updates:
>
>     http://lists.ocaml.org/listinfo/cam-compiler-hacking
>
> Where: Room FW11, Computer Laboratory, Madingley Road
>        Directions to the building: http://www.cl.cam.ac.uk/directions/
>        Room plan:
> http://www.cl.cam.ac.uk/research/dtg/openroommap/static/?s=FW11&labels=1
>
> When: 6pm, Tuesday 18th February
>
> Who: anyone interested in improving OCaml. Knowledge of OCaml
> programming will obviously be helpful, but prior experience of working
> on OCaml internals isn't necessary.
>
> What: fixing bugs, implementing new features, learning about OCaml internals
>
> Wiki: https://github.com/ocamllabs/compiler-hacking/wiki
>
> We're defining "compiler" pretty broadly, to include anything that's
> part of the standard distribution, which means at least the standard
> library, runtime, tools (ocamldep, ocamllex, ocamlyacc, etc.),
> ocamlbuild, the documentation, and the compiler itself. We'll have
> suggestions for mini-projects for various levels of experience, but
> feel free to come along and work on whatever you fancy.
>
> We'll also be ordering pizza, so if you want to be counted for food
> you should aim to arrive by 6.30pm.

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 15:46:57 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 15:46:57 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFQPJ-0004SK-1h; Mon, 17 Feb 2014 15:46:57 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFQ7U-0003iZ-7C
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 15:28:32 +0000
Received: from [85.158.143.35:50390] by server-1.bemta-4.messagelabs.com id
	04/3C-31661-F9A22035; Mon, 17 Feb 2014 15:28:31 +0000
X-Env-Sender: yallop@gmail.com
X-Msg-Ref: server-12.tower-21.messagelabs.com!1392650909!6285599!1
X-Originating-IP: [209.85.216.46]
X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25409 invoked from network); 17 Feb 2014 15:28:30 -0000
Received: from mail-qa0-f46.google.com (HELO mail-qa0-f46.google.com)
	(209.85.216.46)
	by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Feb 2014 15:28:30 -0000
Received: by mail-qa0-f46.google.com with SMTP id k15so8647989qaq.33
	for ;
	Mon, 17 Feb 2014 07:28:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=UpIgl1MnXSYEWhfzegsANszHQQAvfaeJxqB0D488dL0=;
	b=CUP9zbBYjRkt+XbLrdFvyUtgeDqaNVTK1RBxkPDR9lNk7tTqC95EjRalR7C+IxF4pV
	/L4qDB4B/KVCxMuQu0fuYEEmhWZ2J5QeSYof+aGSSUBnPdVCu6BQzvIwnf8lq1Yjhv/K
	cjJ2es0YFmQDu0v+00z2N6dUUY/edXmWeUSEB4W4AVdYfEhzPMFABWLUsvbNPKxoJwrm
	ZL4BGbXkpB6ridC5KDKVDbImqylZiMjdQKS5bmYdfybUXgvnvu3gN6CNws3K72aHOnXn
	V3wO1vNvo4ALj6Wpl57Vj/ntmBmGImJXHyOf6+/IgNp0Sv+KiYyafe92u0/cuj+IOQ1f
	PwxQ==
MIME-Version: 1.0
X-Received: by 10.140.94.214 with SMTP id g80mr33540971qge.19.1392650909282;
	Mon, 17 Feb 2014 07:28:29 -0800 (PST)
Received: by 10.229.131.65 with HTTP; Mon, 17 Feb 2014 07:28:29 -0800 (PST)
In-Reply-To: 
References: 
Date: Mon, 17 Feb 2014 15:28:29 +0000
Message-ID: 
From: Jeremy Yallop 
To: "cl-ocamllabs-staff@lists.cam.ac.uk" , 
	cam-compiler-hacking@lists.ocaml.org, mirageos-devel@lists.xenproject.org
X-Mailman-Approved-At: Mon, 17 Feb 2014 15:46:55 +0000
Subject: Re: [MirageOS-devel] OCaml compiler hacking session
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Reminder: the OCaml compiler hacking session will take place from 6pm
tomorrow in FW11.  If you're planning to come along, please add your
name to the list:

    http://doodle.com/5tk8rs5k3mh82qqx

On 11 February 2014 18:36, Jeremy Yallop  wrote:
> It's time for the fourth Cambridge OCaml compiler-hacking session!
> We'll be meeting in the Computer Lab again next Tuesday evening.
>
> If you're planning to come along, it'd be helpful if you could
> indicate interest via Doodle:
>
>     http://doodle.com/5tk8rs5k3mh82qqx
>
> and sign up to the mailing list to receive updates:
>
>     http://lists.ocaml.org/listinfo/cam-compiler-hacking
>
> Where: Room FW11, Computer Laboratory, Madingley Road
>        Directions to the building: http://www.cl.cam.ac.uk/directions/
>        Room plan:
> http://www.cl.cam.ac.uk/research/dtg/openroommap/static/?s=FW11&labels=1
>
> When: 6pm, Tuesday 18th February
>
> Who: anyone interested in improving OCaml. Knowledge of OCaml
> programming will obviously be helpful, but prior experience of working
> on OCaml internals isn't necessary.
>
> What: fixing bugs, implementing new features, learning about OCaml internals
>
> Wiki: https://github.com/ocamllabs/compiler-hacking/wiki
>
> We're defining "compiler" pretty broadly, to include anything that's
> part of the standard distribution, which means at least the standard
> library, runtime, tools (ocamldep, ocamllex, ocamlyacc, etc.),
> ocamlbuild, the documentation, and the compiler itself. We'll have
> suggestions for mini-projects for various levels of experience, but
> feel free to come along and work on whatever you fancy.
>
> We'll also be ordering pizza, so if you want to be counted for food
> you should aim to arrive by 6.30pm.

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 18:05:11 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 18:05: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 1WFSZ2-0002Wd-Qb; Mon, 17 Feb 2014 18:05:08 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFSZ2-0002WI-22
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 18:05:08 +0000
Received: from [85.158.137.68:27863] by server-5.bemta-3.messagelabs.com id
	58/F3-04712-35F42035; Mon, 17 Feb 2014 18:05:07 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-7.tower-31.messagelabs.com!1392660306!2450628!1
X-Originating-IP: [131.111.8.142]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32657 invoked from network); 17 Feb 2014 18:05:06 -0000
Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk)
	(131.111.8.142)
	by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 17 Feb 2014 18:05:06 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from host86-174-95-65.range86-174.btcentralplus.com
	([86.174.95.65]:59075 helo=amirmacbook.home)
	by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WFSYz-0007EV-8E (Exim 4.82_3-c0e5623)
	(return-path ); Mon, 17 Feb 2014 18:05:05 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: <1386756731.30271.22.camel@kazak.uk.xensource.com>
Date: Mon, 17 Feb 2014 18:05:04 +0000
Message-Id: <637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi Lars,

I'm curious about where things stand with the testing for the Xen project. =
 I've gone through the wg-test-framework archives and tried to catchup with=
 minutes. I'm wondering when the next set will be posted (from the meeting =
on the 13th).

Having a testing setup for Xen would be really useful for Mirage.  Since we=
're having more people try out our tutorials and knowing the state of thing=
s in different environments would help us catch issues quicker.

Thanks,
Amir


On 11 Dec 2013, at 10:12, Ian Campbell  wrote:

> On Tue, 2013-12-10 at 18:29 +0000, Lars Kurth wrote:
>> Ian,
>> =

>> I think that is a good assessment and thanks for pointing out some gaps =

>> in my understanding.
> =

> No problem.
> =

>> So to summarize:
>> * We have some local test suites which could be run, but are probably =

>> not as they are poorly documented
> =

> More documentation is always good. adding a top level script or make
> target to actually run them in a trivial way would IMHO be even more
> valuable in the short term.
> =

> Having that target/script be easily extensible to other suites would be
> a must as well since we have some but not many of these sorts of tests.
> =

>> * We expect people to do some targetted local testing (presumably =

>> performed in a manual manner) of the features they developed and of =

>> those which may be impacted. Bt we don't actually always know whether =

>> they do.
> =

> It's occasionally obvious that someone hasn't tested (or sometimes even
> compiled) their patches, but for the most part it does appear that
> people are actually doing this bit and I think it is well understood as
> an expectation in all development environments (i.e. OSS communities but
> also commercial settings etc), not just ours.
> =

> (as well as a common understanding that it's expected there's probably
> some element of not wanting to look stupid by posting patches which
> don't compile, or haven't been tested)
> =

>> * osstest (or system testing in general) is *extremely* valuable
>> * building out the infrastructure for system testing (aka number and =

>> diversity of boxes) would be extremely valuable - this really means =

>> funding hardware, hosting and sysadmin time
>> * It might also be worth considering spending some money kickstarting =

>> the actual tests (i.e. fleshing out the suites)
>> * *Test on demand* would be a nice long term goal
>> * Some members of the community are intending to make OSSTest more =

>> accessible by improving docs and sharing their experience
>> * At a minimum it ought to be possible to allow access to any employee =

>> of, a project member, since we have the opportunity through the =

>> membership, process to put whatever paperwork and agreements (acceptable =

>> use etc) in place.
> =

> Ack to all that.
> =

> Ian.
> =

>> =

>> Lars
>> =

>> On 09/12/2013 13:20, Ian Campbell wrote:
>>> On Tue, 2013-11-26 at 13:21 +0000, Lars Kurth wrote:
>>>> Hi all,
>>>> =

>>>> you probably have all heard by now that the Xen Project Advisory Board
>>>> (a group of vendors who provide funds to the Xen Project that are
>>>> intended to be used for the good of the community) recently created the
>>>> Test Framework Working
>>>> Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontains more
>>>> information about the group. The working group had its first meeting a
>>>> few weeks ago and one of the actions I had was to kick off a thread on
>>>> development lists to figure out what would help the developer communit=
y.
>>>> =

>>>> I was planning to kick off this thread with some questions and options,
>>>> which reflect some discussions I had with individuals in the community,
>>>> various meetings (WG and AB meetings), etc. which I condensed into a
>>>> picture.
>>>> =

>>>> This reflects my personal opinion (not a Citrix opinion) and is merely
>>>> intended to get a discussion going. Feel free to pick it apart: I won=
=92t
>>>> be upset.
>>>> =

>>>> First, I wanted to clear up a few misconceptions that I have heard from
>>>> a few people:
>>>> =

>>>> * The Advisory Board has funds that can be used to create an
>>>> independently hosted test infrastructure to help the developer
>>>> community. However, funds are limited. Thus, it is important that we do
>>>> what is right for the Xen community in the short term and the longer
>>>> term. Otherwise, we will burn funds that could be used to help the Xen
>>>> community in other ways.
>>>> * The Test Framework Working Group is made up of people employed by
>>>> vendors who have some experience in testing.
>>>> * There is no intention to prescribe a test environment that you then
>>>> have to use. Advisory Board members made clear to me that they want to
>>>> make sure that what we end up with a solution that works for you.
>>>> * At the Xen Developer Summit two different solutions for system testi=
ng
>>>> were presented. The intention was to explain what is there and what we
>>>> can use going forward. A presentation on OSSTest which runs regularly
>>>> today was given. And one for XenRT, for which there is a plan to get a
>>>> small 3 box system up and running that can be used for you to look at.
>>>> Citrix volunteered to set this up at its own cost.
>>>> * Just to be clear: what works for you may be one of these, none of
>>>> these, both of them, =85
>>>> * There may also be different answers in the short and the long run.
>>>> * At the end of the day, different community members will have differe=
nt
>>>> views. Also the Advisory Board members who provide the funds, will also
>>>> have specific interests that they will push for. Thus, in all
>>>> likelihood, we will have to find a good enough compromise.
>>>> * The vast majority of Advisory Board members care about the Hypervisor
>>>> (and not so much about XAPI and Mirage OS). Thus, it is likely that the
>>>> focus of the test system would be the Hypervisor.
>>>> =

>>>> So let me try and condense some of the arguments and opinions I heard
>>>> and information that is around. This list may be incomplete.
>>>> =

>>>> =3D=3D Work Flow =3D=3D
>>>> =

>>>> I added this section, because some members of the community and the
>>>> working group had prior experience with attempts to introduce a test
>>>> infrastructure for an open source community in the past, and these may
>>>> not have worked as well as hoped. I made up some of the terminology.
>>>> =

>>>> *Local testing*: the basic idea here is for a developer to write their
>>> [...]
>>> =

>>> We have a small amount of local test suites in the tree (e.g. vif and
>>> disk config parsing have little test suites) but it could do with tying
>>> together with some infrastructure into something which is simple to run
>>> (currently it requires an installed Xen system and there is no one
>>> single way to run something).
>>> =

>>> As you correctly suggest there is a limit to how much local testing can
>>> cover in terms of elapsed time, available resources, the configurations
>>> which can be reasonably set up, running on real hardware etc. IMHO This
>>> could benefit from an enthusiastic (or press-ganged by their
>>> manager ;-)) community member putting some time into tying it all
>>> together into something which we can ask people to run before submitting
>>> with a straight face.
>>> =

>>> =

>>>> *System testing*: both OSSTest and XenRT are essentially system test
>>> [...]
>>> =

>>> I think most people use "system testing" to mean testing of the
>>> integrated whole, as opposed to e.g. unit testing. The current
>>> "automated test" which we have covers some aspects of both whole system
>>> and unit testing.
>>> =

>>> Anyway, terminology aside, the existing osstest stuff is *extremely*
>>> valuable IMHO, and the system testing has been very useful over the
>>> majority of the lifetime of the xen project, at least as long as I've
>>> been involved. The main limitation is the amount of resources dedicated
>>> to it, in terms of hardware (and its location within citrix
>>> infrastructure doesn't help here) and test coverage.
>>> =

>>> Even with its current set of tests and limited hardware it already tests
>>> far more than we could ever realistically ask people to do locally
>>> before submitting and it catches real issues on real hardware.
>>> =

>>> Any local test stuff should obviously be integrated into the system
>>> tests as a step as well.
>>> =

>>> I notice that your description of system test omits the targeted local
>>> testing which we expect contributors to do before submitting a patch --
>>> by targeted I mean you are changing $FOO therefore you should be trying
>>> $FOO! And if you think you might have an impact on $BAR you should be
>>> testing that too. I just mention it because your description seemed to
>>> imply (inadvertently I expect) that there was no testing at all between
>>> writing the code and the system tests running, which is not quite
>>> accurate.
>>> =

>>> IMHO both local and system test are valuable. I think the local testing
>>> situation can be improved by people working within the community to do
>>> the work (in particular building out the infrastructure), whereas the
>>> system testing side of things would benefit greatly from any resourcing
>>> which the AB can provide in terms of hardware, hosting and sysadmin time
>>> etc. There is no doubt in my mind that this would be beneficial to the
>>> community in both the short and long term.
>>> =

>>> It might also be worth considering spending some money kickstarting the
>>> actual tests (i.e. fleshing out the suites) in both cases, but I think
>>> ultimately I think this needs to be driven by community member (AB or
>>> otherwise) who care about particular functionality making sure the tests
>>> exist, probably by writing them. So in terms of budget I think that
>>> would be secondary to sorting out the hosting etc
>>> =

>>>> *Test on demand:* this would be a mixture between local testing and
>>> [...]
>>> =

>>> I think it would be nice long term goal to aim for this but short term
>>> the other two types of testing are more important.
>>> =

>>>> IMHO, this would be a nice mid to long-term goal,
>>>> assuming it could be made to work with the funds we have.
>>> Heh, I should read right to the end ;-)
>>> =

>>>> =3D=3D OSSTest =3D=3D
>>>> =

>>>> What runs now and thus easiest to get started on
>>>> =

>>>> More Info
>>>> *http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-os=
stest/
>>>> *http://blog.xen.org/index.php/2013/09/30/osstest-standalone-mode-step=
-by-step/
>>>> *http://www.youtube.com/watch?v=3DJxTFZIwZzJ8
>>>> =

>>>> Problems:
>>>> * Runs on Citrix premises (thus general access is an issue)
>>>> * Ian Jackson is acting as sys-admin in his spare time. But, the
>>>> Advisory Board could provide resource to fix this
>>>> * Basic test coverage
>>>> * Not a lot of documentation right now (which is a bit of a barrier to
>>>> adoption)
>>>> =

>>>> Risks
>>>> * Not well understood (maybe you guys can fill the gaps)
>>> This is slowly changing, Wei, Roger and myself have all done development
>>> with osstest and contributed (or are in the process of doing so) new
>>> bits of testing. I think Dario and Anthony have played with it too.
>>> There is certainly more which could be done here in terms of
>>> documentation. I at least was planning to make this part of my focus on
>>> future documentation and/or test days.
>>> =

>>> I think all of the above applies equally to XenRT, either system is
>>> going to have a learning curve and is going to need documentation for
>>> the community etc.
>>> =

>>>> =3D=3D XenRT =3D=3D
>>>> =

>>>> Used by Citrix for XenServer testing. Tarballs have been made available
>>>> by Citrix under a BSD license. But the code has not been put into live
>>>> repos: my understanding is that Citrix would do this, if the Xen
>>>> community believes this is valuable.
>>>> =

>>>> More Info
>>>> *http://wiki.xenproject.org/wiki/Getting_Started_with_XenRT
>>>> *http://www.youtube.com/watch?v=3Ds11_Iw7AI_U
>>>> =

>>>> Problems:
>>>> * No publicly accessible demo instance (this is being worked on =96 to=
 be
>>>> hosted on a small test bed at http://osuosl.org/ =96 work sponsored by=
 Citrix)
>>>> * Currently does not yet support =93xl=94 (a =93xl=94 connector is bei=
ng worked
>>>> on =96 sponsored by Citrix)
>>>> * Code not in yet public repo
>>>> =

>>>> Potentially Interesting Properties:
>>>> * Very large test coverage (including performance, security and other
>>>> tests). Most of them should work once an =93xl=94 connector is in place
>>> I think that's rather optimistic. I would expect that a reasonable
>>> proportion of the interesting tests will require features of xapi to
>>> work, e.g. pools of hosts, storage management, networking etc and/or
>>> require some amount of reworking to function with xl.
>>> =

>>>> * Been in production at scale for a long time: thus well understood
>>>> * XenRT has a lot of provisioning functionality and supports a
>>>> distributed architecture: aka the ability to manage machines in
>>>> different locations (data centres). The detail is abstracted away from
>>>> users. This creates some interesting possibilities. For example:
>>>> ** Hardware Vendors on the Advisory Board could provide hardware to the
>>>> community on their site (assuming that these can be hosted outside a
>>>> firewall). Some HW vendors on the AB indicated that this would indeed =
be
>>>> doable.
>>>> ** This would open up the opportunity to make available cutting edge or
>>>> =93unusual=94 HW for testing to the community.
>>>> ** It would also mean that machines that would be expensive to ship and
>>>> host by the project, could be hosted on premise by AB vendors
>>>> * XenRT has the capability to =93inject=94 some test code on the fly (=
i.e.
>>>> the test code is attached to a job that is submitted).
>>>> * I checked this with the XenRT devs and the *Test on demand* approach
>>>> should be relatively easy to implement, but does not exist.
>>>> =

>>>> I do not know what of the above would apply to OSSTest.
>>> I think it is all equally doable for either.
>>> =

>>>> Risks
>>>> * Complexity
>>>> * The cost of supporting such a system may be too high
>>>> * Not in use by the community today
>>>> * Not clear whether a *local test* version of XenRT is feasible
>>>> =

>>>> =3D=3D Support and Ownership =3D=3D
>>>> =

>>>> Whatever solution we go for, needs to be properly funded and looked
>>>> after.
>>> From the remainder of the paragraph I think you are talking specifically
>>> about hiring a test person here I think?
>>> =

>>> I think this is essential, the current testing is done on a shoe string
>>> and that is one of its main limiting factors.
>>> =

>>>>  This is understood and the intention would be for the Xen Project
>>>> (aka Advisory Board) to fund a Linux Foundation employee to do this on
>>>> behalf of the Xen Project: this is a bit like Greg KH and others being
>>>> LF employees working on the kernel. Some vendors on the Advisory Board
>>>> indicated that providing Colo/hosting space and HW would be possible in
>>>> principle, which could help keeping the cost manageable.
>>> We should certainly be taking them up on those offers IMHO.
>>> =

>>>> =3D=3D Access =3D=3D
>>>> =

>>>> Any central system, has of course the issue of access control and
>>>> managing users. This is obviously a barrier to entry (if we do not have
>>>> also a local test mechanism). Am wondering how other FOSS communities
>>>> handle this. This should certainly be the job of the Test Framework
>>>> owner (see above).
>>> At a minimum it ought to be possible to allow access to any employee of
>>> a project member, since we have the opportunity through the membership
>>> process to put whatever paperwork and agreements (acceptable use etc) in
>>> place.
>>> =

>>> Unfettered access for anyone who rocks up and asks is a bit trickier.
>>> I'm quite happy to let that be the framework owner's problem ;-)
>>> =

>>> Ian.
>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>> =

> =

> =

> =



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 17 18:05:11 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 17 Feb 2014 18:05: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 1WFSZ2-0002Wd-Qb; Mon, 17 Feb 2014 18:05:08 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFSZ2-0002WI-22
	for mirageos-devel@lists.xenproject.org; Mon, 17 Feb 2014 18:05:08 +0000
Received: from [85.158.137.68:27863] by server-5.bemta-3.messagelabs.com id
	58/F3-04712-35F42035; Mon, 17 Feb 2014 18:05:07 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-7.tower-31.messagelabs.com!1392660306!2450628!1
X-Originating-IP: [131.111.8.142]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32657 invoked from network); 17 Feb 2014 18:05:06 -0000
Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk)
	(131.111.8.142)
	by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 17 Feb 2014 18:05:06 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from host86-174-95-65.range86-174.btcentralplus.com
	([86.174.95.65]:59075 helo=amirmacbook.home)
	by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WFSYz-0007EV-8E (Exim 4.82_3-c0e5623)
	(return-path ); Mon, 17 Feb 2014 18:05:05 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: <1386756731.30271.22.camel@kazak.uk.xensource.com>
Date: Mon, 17 Feb 2014 18:05:04 +0000
Message-Id: <637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi Lars,

I'm curious about where things stand with the testing for the Xen project. =
 I've gone through the wg-test-framework archives and tried to catchup with=
 minutes. I'm wondering when the next set will be posted (from the meeting =
on the 13th).

Having a testing setup for Xen would be really useful for Mirage.  Since we=
're having more people try out our tutorials and knowing the state of thing=
s in different environments would help us catch issues quicker.

Thanks,
Amir


On 11 Dec 2013, at 10:12, Ian Campbell  wrote:

> On Tue, 2013-12-10 at 18:29 +0000, Lars Kurth wrote:
>> Ian,
>> =

>> I think that is a good assessment and thanks for pointing out some gaps =

>> in my understanding.
> =

> No problem.
> =

>> So to summarize:
>> * We have some local test suites which could be run, but are probably =

>> not as they are poorly documented
> =

> More documentation is always good. adding a top level script or make
> target to actually run them in a trivial way would IMHO be even more
> valuable in the short term.
> =

> Having that target/script be easily extensible to other suites would be
> a must as well since we have some but not many of these sorts of tests.
> =

>> * We expect people to do some targetted local testing (presumably =

>> performed in a manual manner) of the features they developed and of =

>> those which may be impacted. Bt we don't actually always know whether =

>> they do.
> =

> It's occasionally obvious that someone hasn't tested (or sometimes even
> compiled) their patches, but for the most part it does appear that
> people are actually doing this bit and I think it is well understood as
> an expectation in all development environments (i.e. OSS communities but
> also commercial settings etc), not just ours.
> =

> (as well as a common understanding that it's expected there's probably
> some element of not wanting to look stupid by posting patches which
> don't compile, or haven't been tested)
> =

>> * osstest (or system testing in general) is *extremely* valuable
>> * building out the infrastructure for system testing (aka number and =

>> diversity of boxes) would be extremely valuable - this really means =

>> funding hardware, hosting and sysadmin time
>> * It might also be worth considering spending some money kickstarting =

>> the actual tests (i.e. fleshing out the suites)
>> * *Test on demand* would be a nice long term goal
>> * Some members of the community are intending to make OSSTest more =

>> accessible by improving docs and sharing their experience
>> * At a minimum it ought to be possible to allow access to any employee =

>> of, a project member, since we have the opportunity through the =

>> membership, process to put whatever paperwork and agreements (acceptable =

>> use etc) in place.
> =

> Ack to all that.
> =

> Ian.
> =

>> =

>> Lars
>> =

>> On 09/12/2013 13:20, Ian Campbell wrote:
>>> On Tue, 2013-11-26 at 13:21 +0000, Lars Kurth wrote:
>>>> Hi all,
>>>> =

>>>> you probably have all heard by now that the Xen Project Advisory Board
>>>> (a group of vendors who provide funds to the Xen Project that are
>>>> intended to be used for the good of the community) recently created the
>>>> Test Framework Working
>>>> Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontains more
>>>> information about the group. The working group had its first meeting a
>>>> few weeks ago and one of the actions I had was to kick off a thread on
>>>> development lists to figure out what would help the developer communit=
y.
>>>> =

>>>> I was planning to kick off this thread with some questions and options,
>>>> which reflect some discussions I had with individuals in the community,
>>>> various meetings (WG and AB meetings), etc. which I condensed into a
>>>> picture.
>>>> =

>>>> This reflects my personal opinion (not a Citrix opinion) and is merely
>>>> intended to get a discussion going. Feel free to pick it apart: I won=
=92t
>>>> be upset.
>>>> =

>>>> First, I wanted to clear up a few misconceptions that I have heard from
>>>> a few people:
>>>> =

>>>> * The Advisory Board has funds that can be used to create an
>>>> independently hosted test infrastructure to help the developer
>>>> community. However, funds are limited. Thus, it is important that we do
>>>> what is right for the Xen community in the short term and the longer
>>>> term. Otherwise, we will burn funds that could be used to help the Xen
>>>> community in other ways.
>>>> * The Test Framework Working Group is made up of people employed by
>>>> vendors who have some experience in testing.
>>>> * There is no intention to prescribe a test environment that you then
>>>> have to use. Advisory Board members made clear to me that they want to
>>>> make sure that what we end up with a solution that works for you.
>>>> * At the Xen Developer Summit two different solutions for system testi=
ng
>>>> were presented. The intention was to explain what is there and what we
>>>> can use going forward. A presentation on OSSTest which runs regularly
>>>> today was given. And one for XenRT, for which there is a plan to get a
>>>> small 3 box system up and running that can be used for you to look at.
>>>> Citrix volunteered to set this up at its own cost.
>>>> * Just to be clear: what works for you may be one of these, none of
>>>> these, both of them, =85
>>>> * There may also be different answers in the short and the long run.
>>>> * At the end of the day, different community members will have differe=
nt
>>>> views. Also the Advisory Board members who provide the funds, will also
>>>> have specific interests that they will push for. Thus, in all
>>>> likelihood, we will have to find a good enough compromise.
>>>> * The vast majority of Advisory Board members care about the Hypervisor
>>>> (and not so much about XAPI and Mirage OS). Thus, it is likely that the
>>>> focus of the test system would be the Hypervisor.
>>>> =

>>>> So let me try and condense some of the arguments and opinions I heard
>>>> and information that is around. This list may be incomplete.
>>>> =

>>>> =3D=3D Work Flow =3D=3D
>>>> =

>>>> I added this section, because some members of the community and the
>>>> working group had prior experience with attempts to introduce a test
>>>> infrastructure for an open source community in the past, and these may
>>>> not have worked as well as hoped. I made up some of the terminology.
>>>> =

>>>> *Local testing*: the basic idea here is for a developer to write their
>>> [...]
>>> =

>>> We have a small amount of local test suites in the tree (e.g. vif and
>>> disk config parsing have little test suites) but it could do with tying
>>> together with some infrastructure into something which is simple to run
>>> (currently it requires an installed Xen system and there is no one
>>> single way to run something).
>>> =

>>> As you correctly suggest there is a limit to how much local testing can
>>> cover in terms of elapsed time, available resources, the configurations
>>> which can be reasonably set up, running on real hardware etc. IMHO This
>>> could benefit from an enthusiastic (or press-ganged by their
>>> manager ;-)) community member putting some time into tying it all
>>> together into something which we can ask people to run before submitting
>>> with a straight face.
>>> =

>>> =

>>>> *System testing*: both OSSTest and XenRT are essentially system test
>>> [...]
>>> =

>>> I think most people use "system testing" to mean testing of the
>>> integrated whole, as opposed to e.g. unit testing. The current
>>> "automated test" which we have covers some aspects of both whole system
>>> and unit testing.
>>> =

>>> Anyway, terminology aside, the existing osstest stuff is *extremely*
>>> valuable IMHO, and the system testing has been very useful over the
>>> majority of the lifetime of the xen project, at least as long as I've
>>> been involved. The main limitation is the amount of resources dedicated
>>> to it, in terms of hardware (and its location within citrix
>>> infrastructure doesn't help here) and test coverage.
>>> =

>>> Even with its current set of tests and limited hardware it already tests
>>> far more than we could ever realistically ask people to do locally
>>> before submitting and it catches real issues on real hardware.
>>> =

>>> Any local test stuff should obviously be integrated into the system
>>> tests as a step as well.
>>> =

>>> I notice that your description of system test omits the targeted local
>>> testing which we expect contributors to do before submitting a patch --
>>> by targeted I mean you are changing $FOO therefore you should be trying
>>> $FOO! And if you think you might have an impact on $BAR you should be
>>> testing that too. I just mention it because your description seemed to
>>> imply (inadvertently I expect) that there was no testing at all between
>>> writing the code and the system tests running, which is not quite
>>> accurate.
>>> =

>>> IMHO both local and system test are valuable. I think the local testing
>>> situation can be improved by people working within the community to do
>>> the work (in particular building out the infrastructure), whereas the
>>> system testing side of things would benefit greatly from any resourcing
>>> which the AB can provide in terms of hardware, hosting and sysadmin time
>>> etc. There is no doubt in my mind that this would be beneficial to the
>>> community in both the short and long term.
>>> =

>>> It might also be worth considering spending some money kickstarting the
>>> actual tests (i.e. fleshing out the suites) in both cases, but I think
>>> ultimately I think this needs to be driven by community member (AB or
>>> otherwise) who care about particular functionality making sure the tests
>>> exist, probably by writing them. So in terms of budget I think that
>>> would be secondary to sorting out the hosting etc
>>> =

>>>> *Test on demand:* this would be a mixture between local testing and
>>> [...]
>>> =

>>> I think it would be nice long term goal to aim for this but short term
>>> the other two types of testing are more important.
>>> =

>>>> IMHO, this would be a nice mid to long-term goal,
>>>> assuming it could be made to work with the funds we have.
>>> Heh, I should read right to the end ;-)
>>> =

>>>> =3D=3D OSSTest =3D=3D
>>>> =

>>>> What runs now and thus easiest to get started on
>>>> =

>>>> More Info
>>>> *http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-os=
stest/
>>>> *http://blog.xen.org/index.php/2013/09/30/osstest-standalone-mode-step=
-by-step/
>>>> *http://www.youtube.com/watch?v=3DJxTFZIwZzJ8
>>>> =

>>>> Problems:
>>>> * Runs on Citrix premises (thus general access is an issue)
>>>> * Ian Jackson is acting as sys-admin in his spare time. But, the
>>>> Advisory Board could provide resource to fix this
>>>> * Basic test coverage
>>>> * Not a lot of documentation right now (which is a bit of a barrier to
>>>> adoption)
>>>> =

>>>> Risks
>>>> * Not well understood (maybe you guys can fill the gaps)
>>> This is slowly changing, Wei, Roger and myself have all done development
>>> with osstest and contributed (or are in the process of doing so) new
>>> bits of testing. I think Dario and Anthony have played with it too.
>>> There is certainly more which could be done here in terms of
>>> documentation. I at least was planning to make this part of my focus on
>>> future documentation and/or test days.
>>> =

>>> I think all of the above applies equally to XenRT, either system is
>>> going to have a learning curve and is going to need documentation for
>>> the community etc.
>>> =

>>>> =3D=3D XenRT =3D=3D
>>>> =

>>>> Used by Citrix for XenServer testing. Tarballs have been made available
>>>> by Citrix under a BSD license. But the code has not been put into live
>>>> repos: my understanding is that Citrix would do this, if the Xen
>>>> community believes this is valuable.
>>>> =

>>>> More Info
>>>> *http://wiki.xenproject.org/wiki/Getting_Started_with_XenRT
>>>> *http://www.youtube.com/watch?v=3Ds11_Iw7AI_U
>>>> =

>>>> Problems:
>>>> * No publicly accessible demo instance (this is being worked on =96 to=
 be
>>>> hosted on a small test bed at http://osuosl.org/ =96 work sponsored by=
 Citrix)
>>>> * Currently does not yet support =93xl=94 (a =93xl=94 connector is bei=
ng worked
>>>> on =96 sponsored by Citrix)
>>>> * Code not in yet public repo
>>>> =

>>>> Potentially Interesting Properties:
>>>> * Very large test coverage (including performance, security and other
>>>> tests). Most of them should work once an =93xl=94 connector is in place
>>> I think that's rather optimistic. I would expect that a reasonable
>>> proportion of the interesting tests will require features of xapi to
>>> work, e.g. pools of hosts, storage management, networking etc and/or
>>> require some amount of reworking to function with xl.
>>> =

>>>> * Been in production at scale for a long time: thus well understood
>>>> * XenRT has a lot of provisioning functionality and supports a
>>>> distributed architecture: aka the ability to manage machines in
>>>> different locations (data centres). The detail is abstracted away from
>>>> users. This creates some interesting possibilities. For example:
>>>> ** Hardware Vendors on the Advisory Board could provide hardware to the
>>>> community on their site (assuming that these can be hosted outside a
>>>> firewall). Some HW vendors on the AB indicated that this would indeed =
be
>>>> doable.
>>>> ** This would open up the opportunity to make available cutting edge or
>>>> =93unusual=94 HW for testing to the community.
>>>> ** It would also mean that machines that would be expensive to ship and
>>>> host by the project, could be hosted on premise by AB vendors
>>>> * XenRT has the capability to =93inject=94 some test code on the fly (=
i.e.
>>>> the test code is attached to a job that is submitted).
>>>> * I checked this with the XenRT devs and the *Test on demand* approach
>>>> should be relatively easy to implement, but does not exist.
>>>> =

>>>> I do not know what of the above would apply to OSSTest.
>>> I think it is all equally doable for either.
>>> =

>>>> Risks
>>>> * Complexity
>>>> * The cost of supporting such a system may be too high
>>>> * Not in use by the community today
>>>> * Not clear whether a *local test* version of XenRT is feasible
>>>> =

>>>> =3D=3D Support and Ownership =3D=3D
>>>> =

>>>> Whatever solution we go for, needs to be properly funded and looked
>>>> after.
>>> From the remainder of the paragraph I think you are talking specifically
>>> about hiring a test person here I think?
>>> =

>>> I think this is essential, the current testing is done on a shoe string
>>> and that is one of its main limiting factors.
>>> =

>>>>  This is understood and the intention would be for the Xen Project
>>>> (aka Advisory Board) to fund a Linux Foundation employee to do this on
>>>> behalf of the Xen Project: this is a bit like Greg KH and others being
>>>> LF employees working on the kernel. Some vendors on the Advisory Board
>>>> indicated that providing Colo/hosting space and HW would be possible in
>>>> principle, which could help keeping the cost manageable.
>>> We should certainly be taking them up on those offers IMHO.
>>> =

>>>> =3D=3D Access =3D=3D
>>>> =

>>>> Any central system, has of course the issue of access control and
>>>> managing users. This is obviously a barrier to entry (if we do not have
>>>> also a local test mechanism). Am wondering how other FOSS communities
>>>> handle this. This should certainly be the job of the Test Framework
>>>> owner (see above).
>>> At a minimum it ought to be possible to allow access to any employee of
>>> a project member, since we have the opportunity through the membership
>>> process to put whatever paperwork and agreements (acceptable use etc) in
>>> place.
>>> =

>>> Unfettered access for anyone who rocks up and asks is a bit trickier.
>>> I'm quite happy to let that be the framework owner's problem ;-)
>>> =

>>> Ian.
>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>>> =

>> =

> =

> =

> =



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 09:12:44 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 09:12: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 1WFgjI-0005R8-J0; Tue, 18 Feb 2014 09:12:40 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFgjG-0005R3-K5
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 09:12:39 +0000
Received: from [85.158.143.35:38951] by server-1.bemta-4.messagelabs.com id
	EE/FB-31661-50423035; Tue, 18 Feb 2014 09:12:37 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1392714756!6445536!1
X-Originating-IP: [209.85.212.170]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	ML_RADAR_SPEW_LINKS_23,RCVD_ILLEGAL_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25767 invoked from network); 18 Feb 2014 09:12:36 -0000
Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com)
	(209.85.212.170)
	by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 09:12:36 -0000
Received: by mail-wi0-f170.google.com with SMTP id hi5so3170720wib.5
	for ;
	Tue, 18 Feb 2014 01:12:36 -0800 (PST)
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=xCMuofvPQHJw4eh1CmC8rF5j4/LPeKZdX9yEj9KFFaY=;
	b=KD4aqSuymmyCaxNKElx4qI7P1TOFsb9lLgmBLZr5vE/KPV8136HwXL6GjPoEDB8lqe
	fAV8bzUh0Z6OPmc6UevSCC54Y5M0LBW3vFyg/ij1RlWhS1+Df9DngbU6GmJFxwuVJyes
	XF3rU4e/54QALaWeKLVibkH707Z8wggQW6aaVSeKvSnbWXv2ii0x+HTbCx6rVKluyt32
	X41Y431SjK/Ezw+enZonQxZU2lWxYLKAvREJZu7Y2YgyWxfKFQ9gLEY6fprs9a7dkH3q
	A7qZ9xnarvcAqvSZVTFkD8iVfJbjeek/4CSIQcTBFZrKjImYvlGRtIJRyesjf5tCezln
	XUYA==
X-Received: by 10.194.85.75 with SMTP id f11mr7390202wjz.47.1392714756013;
	Tue, 18 Feb 2014 01:12:36 -0800 (PST)
Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id
	ha1sm43713120wjc.23.2014.02.18.01.12.33 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 18 Feb 2014 01:12:35 -0800 (PST)
Message-ID: <53032400.10104@xen.org>
Date: Tue, 18 Feb 2014 09:12:32 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Amir Chaudhry 
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
	<637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
In-Reply-To: <637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Amir,
there was good progress at the last meeting (which was on Thursday). I =

still have to write up the minutes, which with a bit of luck I will be =

able to do today
Lars

On 17/02/2014 18:05, Amir Chaudhry wrote:
> Hi Lars,
>
> I'm curious about where things stand with the testing for the Xen project=
.  I've gone through the wg-test-framework archives and tried to catchup wi=
th minutes. I'm wondering when the next set will be posted (from the meetin=
g on the 13th).
>
> Having a testing setup for Xen would be really useful for Mirage.  Since =
we're having more people try out our tutorials and knowing the state of thi=
ngs in different environments would help us catch issues quicker.
>
> Thanks,
> Amir
>
>
> On 11 Dec 2013, at 10:12, Ian Campbell  wrote:
>
>> On Tue, 2013-12-10 at 18:29 +0000, Lars Kurth wrote:
>>> Ian,
>>>
>>> I think that is a good assessment and thanks for pointing out some gaps
>>> in my understanding.
>> No problem.
>>
>>> So to summarize:
>>> * We have some local test suites which could be run, but are probably
>>> not as they are poorly documented
>> More documentation is always good. adding a top level script or make
>> target to actually run them in a trivial way would IMHO be even more
>> valuable in the short term.
>>
>> Having that target/script be easily extensible to other suites would be
>> a must as well since we have some but not many of these sorts of tests.
>>
>>> * We expect people to do some targetted local testing (presumably
>>> performed in a manual manner) of the features they developed and of
>>> those which may be impacted. Bt we don't actually always know whether
>>> they do.
>> It's occasionally obvious that someone hasn't tested (or sometimes even
>> compiled) their patches, but for the most part it does appear that
>> people are actually doing this bit and I think it is well understood as
>> an expectation in all development environments (i.e. OSS communities but
>> also commercial settings etc), not just ours.
>>
>> (as well as a common understanding that it's expected there's probably
>> some element of not wanting to look stupid by posting patches which
>> don't compile, or haven't been tested)
>>
>>> * osstest (or system testing in general) is *extremely* valuable
>>> * building out the infrastructure for system testing (aka number and
>>> diversity of boxes) would be extremely valuable - this really means
>>> funding hardware, hosting and sysadmin time
>>> * It might also be worth considering spending some money kickstarting
>>> the actual tests (i.e. fleshing out the suites)
>>> * *Test on demand* would be a nice long term goal
>>> * Some members of the community are intending to make OSSTest more
>>> accessible by improving docs and sharing their experience
>>> * At a minimum it ought to be possible to allow access to any employee
>>> of, a project member, since we have the opportunity through the
>>> membership, process to put whatever paperwork and agreements (acceptable
>>> use etc) in place.
>> Ack to all that.
>>
>> Ian.
>>
>>> Lars
>>>
>>> On 09/12/2013 13:20, Ian Campbell wrote:
>>>> On Tue, 2013-11-26 at 13:21 +0000, Lars Kurth wrote:
>>>>> Hi all,
>>>>>
>>>>> you probably have all heard by now that the Xen Project Advisory Board
>>>>> (a group of vendors who provide funds to the Xen Project that are
>>>>> intended to be used for the good of the community) recently created t=
he
>>>>> Test Framework Working
>>>>> Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontains mo=
re
>>>>> information about the group. The working group had its first meeting a
>>>>> few weeks ago and one of the actions I had was to kick off a thread on
>>>>> development lists to figure out what would help the developer communi=
ty.
>>>>>
>>>>> I was planning to kick off this thread with some questions and option=
s,
>>>>> which reflect some discussions I had with individuals in the communit=
y,
>>>>> various meetings (WG and AB meetings), etc. which I condensed into a
>>>>> picture.
>>>>>
>>>>> This reflects my personal opinion (not a Citrix opinion) and is merely
>>>>> intended to get a discussion going. Feel free to pick it apart: I won=
=92t
>>>>> be upset.
>>>>>
>>>>> First, I wanted to clear up a few misconceptions that I have heard fr=
om
>>>>> a few people:
>>>>>
>>>>> * The Advisory Board has funds that can be used to create an
>>>>> independently hosted test infrastructure to help the developer
>>>>> community. However, funds are limited. Thus, it is important that we =
do
>>>>> what is right for the Xen community in the short term and the longer
>>>>> term. Otherwise, we will burn funds that could be used to help the Xen
>>>>> community in other ways.
>>>>> * The Test Framework Working Group is made up of people employed by
>>>>> vendors who have some experience in testing.
>>>>> * There is no intention to prescribe a test environment that you then
>>>>> have to use. Advisory Board members made clear to me that they want to
>>>>> make sure that what we end up with a solution that works for you.
>>>>> * At the Xen Developer Summit two different solutions for system test=
ing
>>>>> were presented. The intention was to explain what is there and what we
>>>>> can use going forward. A presentation on OSSTest which runs regularly
>>>>> today was given. And one for XenRT, for which there is a plan to get a
>>>>> small 3 box system up and running that can be used for you to look at.
>>>>> Citrix volunteered to set this up at its own cost.
>>>>> * Just to be clear: what works for you may be one of these, none of
>>>>> these, both of them, =85
>>>>> * There may also be different answers in the short and the long run.
>>>>> * At the end of the day, different community members will have differ=
ent
>>>>> views. Also the Advisory Board members who provide the funds, will al=
so
>>>>> have specific interests that they will push for. Thus, in all
>>>>> likelihood, we will have to find a good enough compromise.
>>>>> * The vast majority of Advisory Board members care about the Hypervis=
or
>>>>> (and not so much about XAPI and Mirage OS). Thus, it is likely that t=
he
>>>>> focus of the test system would be the Hypervisor.
>>>>>
>>>>> So let me try and condense some of the arguments and opinions I heard
>>>>> and information that is around. This list may be incomplete.
>>>>>
>>>>> =3D=3D Work Flow =3D=3D
>>>>>
>>>>> I added this section, because some members of the community and the
>>>>> working group had prior experience with attempts to introduce a test
>>>>> infrastructure for an open source community in the past, and these may
>>>>> not have worked as well as hoped. I made up some of the terminology.
>>>>>
>>>>> *Local testing*: the basic idea here is for a developer to write their
>>>> [...]
>>>>
>>>> We have a small amount of local test suites in the tree (e.g. vif and
>>>> disk config parsing have little test suites) but it could do with tying
>>>> together with some infrastructure into something which is simple to run
>>>> (currently it requires an installed Xen system and there is no one
>>>> single way to run something).
>>>>
>>>> As you correctly suggest there is a limit to how much local testing can
>>>> cover in terms of elapsed time, available resources, the configurations
>>>> which can be reasonably set up, running on real hardware etc. IMHO This
>>>> could benefit from an enthusiastic (or press-ganged by their
>>>> manager ;-)) community member putting some time into tying it all
>>>> together into something which we can ask people to run before submitti=
ng
>>>> with a straight face.
>>>>
>>>>
>>>>> *System testing*: both OSSTest and XenRT are essentially system test
>>>> [...]
>>>>
>>>> I think most people use "system testing" to mean testing of the
>>>> integrated whole, as opposed to e.g. unit testing. The current
>>>> "automated test" which we have covers some aspects of both whole system
>>>> and unit testing.
>>>>
>>>> Anyway, terminology aside, the existing osstest stuff is *extremely*
>>>> valuable IMHO, and the system testing has been very useful over the
>>>> majority of the lifetime of the xen project, at least as long as I've
>>>> been involved. The main limitation is the amount of resources dedicated
>>>> to it, in terms of hardware (and its location within citrix
>>>> infrastructure doesn't help here) and test coverage.
>>>>
>>>> Even with its current set of tests and limited hardware it already tes=
ts
>>>> far more than we could ever realistically ask people to do locally
>>>> before submitting and it catches real issues on real hardware.
>>>>
>>>> Any local test stuff should obviously be integrated into the system
>>>> tests as a step as well.
>>>>
>>>> I notice that your description of system test omits the targeted local
>>>> testing which we expect contributors to do before submitting a patch --
>>>> by targeted I mean you are changing $FOO therefore you should be trying
>>>> $FOO! And if you think you might have an impact on $BAR you should be
>>>> testing that too. I just mention it because your description seemed to
>>>> imply (inadvertently I expect) that there was no testing at all between
>>>> writing the code and the system tests running, which is not quite
>>>> accurate.
>>>>
>>>> IMHO both local and system test are valuable. I think the local testing
>>>> situation can be improved by people working within the community to do
>>>> the work (in particular building out the infrastructure), whereas the
>>>> system testing side of things would benefit greatly from any resourcing
>>>> which the AB can provide in terms of hardware, hosting and sysadmin ti=
me
>>>> etc. There is no doubt in my mind that this would be beneficial to the
>>>> community in both the short and long term.
>>>>
>>>> It might also be worth considering spending some money kickstarting the
>>>> actual tests (i.e. fleshing out the suites) in both cases, but I think
>>>> ultimately I think this needs to be driven by community member (AB or
>>>> otherwise) who care about particular functionality making sure the tes=
ts
>>>> exist, probably by writing them. So in terms of budget I think that
>>>> would be secondary to sorting out the hosting etc
>>>>
>>>>> *Test on demand:* this would be a mixture between local testing and
>>>> [...]
>>>>
>>>> I think it would be nice long term goal to aim for this but short term
>>>> the other two types of testing are more important.
>>>>
>>>>> IMHO, this would be a nice mid to long-term goal,
>>>>> assuming it could be made to work with the funds we have.
>>>> Heh, I should read right to the end ;-)
>>>>
>>>>> =3D=3D OSSTest =3D=3D
>>>>>
>>>>> What runs now and thus easiest to get started on
>>>>>
>>>>> More Info
>>>>> *http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-o=
sstest/
>>>>> *http://blog.xen.org/index.php/2013/09/30/osstest-standalone-mode-ste=
p-by-step/
>>>>> *http://www.youtube.com/watch?v=3DJxTFZIwZzJ8
>>>>>
>>>>> Problems:
>>>>> * Runs on Citrix premises (thus general access is an issue)
>>>>> * Ian Jackson is acting as sys-admin in his spare time. But, the
>>>>> Advisory Board could provide resource to fix this
>>>>> * Basic test coverage
>>>>> * Not a lot of documentation right now (which is a bit of a barrier to
>>>>> adoption)
>>>>>
>>>>> Risks
>>>>> * Not well understood (maybe you guys can fill the gaps)
>>>> This is slowly changing, Wei, Roger and myself have all done developme=
nt
>>>> with osstest and contributed (or are in the process of doing so) new
>>>> bits of testing. I think Dario and Anthony have played with it too.
>>>> There is certainly more which could be done here in terms of
>>>> documentation. I at least was planning to make this part of my focus on
>>>> future documentation and/or test days.
>>>>
>>>> I think all of the above applies equally to XenRT, either system is
>>>> going to have a learning curve and is going to need documentation for
>>>> the community etc.
>>>>
>>>>> =3D=3D XenRT =3D=3D
>>>>>
>>>>> Used by Citrix for XenServer testing. Tarballs have been made availab=
le
>>>>> by Citrix under a BSD license. But the code has not been put into live
>>>>> repos: my understanding is that Citrix would do this, if the Xen
>>>>> community believes this is valuable.
>>>>>
>>>>> More Info
>>>>> *http://wiki.xenproject.org/wiki/Getting_Started_with_XenRT
>>>>> *http://www.youtube.com/watch?v=3Ds11_Iw7AI_U
>>>>>
>>>>> Problems:
>>>>> * No publicly accessible demo instance (this is being worked on =96 t=
o be
>>>>> hosted on a small test bed at http://osuosl.org/ =96 work sponsored b=
y Citrix)
>>>>> * Currently does not yet support =93xl=94 (a =93xl=94 connector is be=
ing worked
>>>>> on =96 sponsored by Citrix)
>>>>> * Code not in yet public repo
>>>>>
>>>>> Potentially Interesting Properties:
>>>>> * Very large test coverage (including performance, security and other
>>>>> tests). Most of them should work once an =93xl=94 connector is in pla=
ce
>>>> I think that's rather optimistic. I would expect that a reasonable
>>>> proportion of the interesting tests will require features of xapi to
>>>> work, e.g. pools of hosts, storage management, networking etc and/or
>>>> require some amount of reworking to function with xl.
>>>>
>>>>> * Been in production at scale for a long time: thus well understood
>>>>> * XenRT has a lot of provisioning functionality and supports a
>>>>> distributed architecture: aka the ability to manage machines in
>>>>> different locations (data centres). The detail is abstracted away from
>>>>> users. This creates some interesting possibilities. For example:
>>>>> ** Hardware Vendors on the Advisory Board could provide hardware to t=
he
>>>>> community on their site (assuming that these can be hosted outside a
>>>>> firewall). Some HW vendors on the AB indicated that this would indeed=
 be
>>>>> doable.
>>>>> ** This would open up the opportunity to make available cutting edge =
or
>>>>> =93unusual=94 HW for testing to the community.
>>>>> ** It would also mean that machines that would be expensive to ship a=
nd
>>>>> host by the project, could be hosted on premise by AB vendors
>>>>> * XenRT has the capability to =93inject=94 some test code on the fly =
(i.e.
>>>>> the test code is attached to a job that is submitted).
>>>>> * I checked this with the XenRT devs and the *Test on demand* approach
>>>>> should be relatively easy to implement, but does not exist.
>>>>>
>>>>> I do not know what of the above would apply to OSSTest.
>>>> I think it is all equally doable for either.
>>>>
>>>>> Risks
>>>>> * Complexity
>>>>> * The cost of supporting such a system may be too high
>>>>> * Not in use by the community today
>>>>> * Not clear whether a *local test* version of XenRT is feasible
>>>>>
>>>>> =3D=3D Support and Ownership =3D=3D
>>>>>
>>>>> Whatever solution we go for, needs to be properly funded and looked
>>>>> after.
>>>>  From the remainder of the paragraph I think you are talking specifica=
lly
>>>> about hiring a test person here I think?
>>>>
>>>> I think this is essential, the current testing is done on a shoe string
>>>> and that is one of its main limiting factors.
>>>>
>>>>>   This is understood and the intention would be for the Xen Project
>>>>> (aka Advisory Board) to fund a Linux Foundation employee to do this on
>>>>> behalf of the Xen Project: this is a bit like Greg KH and others being
>>>>> LF employees working on the kernel. Some vendors on the Advisory Board
>>>>> indicated that providing Colo/hosting space and HW would be possible =
in
>>>>> principle, which could help keeping the cost manageable.
>>>> We should certainly be taking them up on those offers IMHO.
>>>>
>>>>> =3D=3D Access =3D=3D
>>>>>
>>>>> Any central system, has of course the issue of access control and
>>>>> managing users. This is obviously a barrier to entry (if we do not ha=
ve
>>>>> also a local test mechanism). Am wondering how other FOSS communities
>>>>> handle this. This should certainly be the job of the Test Framework
>>>>> owner (see above).
>>>> At a minimum it ought to be possible to allow access to any employee of
>>>> a project member, since we have the opportunity through the membership
>>>> process to put whatever paperwork and agreements (acceptable use etc) =
in
>>>> place.
>>>>
>>>> Unfettered access for anyone who rocks up and asks is a bit trickier.
>>>> I'm quite happy to let that be the framework owner's problem ;-)
>>>>
>>>> Ian.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 09:12:44 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 09:12: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 1WFgjI-0005R8-J0; Tue, 18 Feb 2014 09:12:40 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFgjG-0005R3-K5
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 09:12:39 +0000
Received: from [85.158.143.35:38951] by server-1.bemta-4.messagelabs.com id
	EE/FB-31661-50423035; Tue, 18 Feb 2014 09:12:37 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1392714756!6445536!1
X-Originating-IP: [209.85.212.170]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	ML_RADAR_SPEW_LINKS_23,RCVD_ILLEGAL_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25767 invoked from network); 18 Feb 2014 09:12:36 -0000
Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com)
	(209.85.212.170)
	by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 09:12:36 -0000
Received: by mail-wi0-f170.google.com with SMTP id hi5so3170720wib.5
	for ;
	Tue, 18 Feb 2014 01:12:36 -0800 (PST)
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=xCMuofvPQHJw4eh1CmC8rF5j4/LPeKZdX9yEj9KFFaY=;
	b=KD4aqSuymmyCaxNKElx4qI7P1TOFsb9lLgmBLZr5vE/KPV8136HwXL6GjPoEDB8lqe
	fAV8bzUh0Z6OPmc6UevSCC54Y5M0LBW3vFyg/ij1RlWhS1+Df9DngbU6GmJFxwuVJyes
	XF3rU4e/54QALaWeKLVibkH707Z8wggQW6aaVSeKvSnbWXv2ii0x+HTbCx6rVKluyt32
	X41Y431SjK/Ezw+enZonQxZU2lWxYLKAvREJZu7Y2YgyWxfKFQ9gLEY6fprs9a7dkH3q
	A7qZ9xnarvcAqvSZVTFkD8iVfJbjeek/4CSIQcTBFZrKjImYvlGRtIJRyesjf5tCezln
	XUYA==
X-Received: by 10.194.85.75 with SMTP id f11mr7390202wjz.47.1392714756013;
	Tue, 18 Feb 2014 01:12:36 -0800 (PST)
Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id
	ha1sm43713120wjc.23.2014.02.18.01.12.33 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 18 Feb 2014 01:12:35 -0800 (PST)
Message-ID: <53032400.10104@xen.org>
Date: Tue, 18 Feb 2014 09:12:32 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Amir Chaudhry 
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
	<637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
In-Reply-To: <637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Amir,
there was good progress at the last meeting (which was on Thursday). I =

still have to write up the minutes, which with a bit of luck I will be =

able to do today
Lars

On 17/02/2014 18:05, Amir Chaudhry wrote:
> Hi Lars,
>
> I'm curious about where things stand with the testing for the Xen project=
.  I've gone through the wg-test-framework archives and tried to catchup wi=
th minutes. I'm wondering when the next set will be posted (from the meetin=
g on the 13th).
>
> Having a testing setup for Xen would be really useful for Mirage.  Since =
we're having more people try out our tutorials and knowing the state of thi=
ngs in different environments would help us catch issues quicker.
>
> Thanks,
> Amir
>
>
> On 11 Dec 2013, at 10:12, Ian Campbell  wrote:
>
>> On Tue, 2013-12-10 at 18:29 +0000, Lars Kurth wrote:
>>> Ian,
>>>
>>> I think that is a good assessment and thanks for pointing out some gaps
>>> in my understanding.
>> No problem.
>>
>>> So to summarize:
>>> * We have some local test suites which could be run, but are probably
>>> not as they are poorly documented
>> More documentation is always good. adding a top level script or make
>> target to actually run them in a trivial way would IMHO be even more
>> valuable in the short term.
>>
>> Having that target/script be easily extensible to other suites would be
>> a must as well since we have some but not many of these sorts of tests.
>>
>>> * We expect people to do some targetted local testing (presumably
>>> performed in a manual manner) of the features they developed and of
>>> those which may be impacted. Bt we don't actually always know whether
>>> they do.
>> It's occasionally obvious that someone hasn't tested (or sometimes even
>> compiled) their patches, but for the most part it does appear that
>> people are actually doing this bit and I think it is well understood as
>> an expectation in all development environments (i.e. OSS communities but
>> also commercial settings etc), not just ours.
>>
>> (as well as a common understanding that it's expected there's probably
>> some element of not wanting to look stupid by posting patches which
>> don't compile, or haven't been tested)
>>
>>> * osstest (or system testing in general) is *extremely* valuable
>>> * building out the infrastructure for system testing (aka number and
>>> diversity of boxes) would be extremely valuable - this really means
>>> funding hardware, hosting and sysadmin time
>>> * It might also be worth considering spending some money kickstarting
>>> the actual tests (i.e. fleshing out the suites)
>>> * *Test on demand* would be a nice long term goal
>>> * Some members of the community are intending to make OSSTest more
>>> accessible by improving docs and sharing their experience
>>> * At a minimum it ought to be possible to allow access to any employee
>>> of, a project member, since we have the opportunity through the
>>> membership, process to put whatever paperwork and agreements (acceptable
>>> use etc) in place.
>> Ack to all that.
>>
>> Ian.
>>
>>> Lars
>>>
>>> On 09/12/2013 13:20, Ian Campbell wrote:
>>>> On Tue, 2013-11-26 at 13:21 +0000, Lars Kurth wrote:
>>>>> Hi all,
>>>>>
>>>>> you probably have all heard by now that the Xen Project Advisory Board
>>>>> (a group of vendors who provide funds to the Xen Project that are
>>>>> intended to be used for the good of the community) recently created t=
he
>>>>> Test Framework Working
>>>>> Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontains mo=
re
>>>>> information about the group. The working group had its first meeting a
>>>>> few weeks ago and one of the actions I had was to kick off a thread on
>>>>> development lists to figure out what would help the developer communi=
ty.
>>>>>
>>>>> I was planning to kick off this thread with some questions and option=
s,
>>>>> which reflect some discussions I had with individuals in the communit=
y,
>>>>> various meetings (WG and AB meetings), etc. which I condensed into a
>>>>> picture.
>>>>>
>>>>> This reflects my personal opinion (not a Citrix opinion) and is merely
>>>>> intended to get a discussion going. Feel free to pick it apart: I won=
=92t
>>>>> be upset.
>>>>>
>>>>> First, I wanted to clear up a few misconceptions that I have heard fr=
om
>>>>> a few people:
>>>>>
>>>>> * The Advisory Board has funds that can be used to create an
>>>>> independently hosted test infrastructure to help the developer
>>>>> community. However, funds are limited. Thus, it is important that we =
do
>>>>> what is right for the Xen community in the short term and the longer
>>>>> term. Otherwise, we will burn funds that could be used to help the Xen
>>>>> community in other ways.
>>>>> * The Test Framework Working Group is made up of people employed by
>>>>> vendors who have some experience in testing.
>>>>> * There is no intention to prescribe a test environment that you then
>>>>> have to use. Advisory Board members made clear to me that they want to
>>>>> make sure that what we end up with a solution that works for you.
>>>>> * At the Xen Developer Summit two different solutions for system test=
ing
>>>>> were presented. The intention was to explain what is there and what we
>>>>> can use going forward. A presentation on OSSTest which runs regularly
>>>>> today was given. And one for XenRT, for which there is a plan to get a
>>>>> small 3 box system up and running that can be used for you to look at.
>>>>> Citrix volunteered to set this up at its own cost.
>>>>> * Just to be clear: what works for you may be one of these, none of
>>>>> these, both of them, =85
>>>>> * There may also be different answers in the short and the long run.
>>>>> * At the end of the day, different community members will have differ=
ent
>>>>> views. Also the Advisory Board members who provide the funds, will al=
so
>>>>> have specific interests that they will push for. Thus, in all
>>>>> likelihood, we will have to find a good enough compromise.
>>>>> * The vast majority of Advisory Board members care about the Hypervis=
or
>>>>> (and not so much about XAPI and Mirage OS). Thus, it is likely that t=
he
>>>>> focus of the test system would be the Hypervisor.
>>>>>
>>>>> So let me try and condense some of the arguments and opinions I heard
>>>>> and information that is around. This list may be incomplete.
>>>>>
>>>>> =3D=3D Work Flow =3D=3D
>>>>>
>>>>> I added this section, because some members of the community and the
>>>>> working group had prior experience with attempts to introduce a test
>>>>> infrastructure for an open source community in the past, and these may
>>>>> not have worked as well as hoped. I made up some of the terminology.
>>>>>
>>>>> *Local testing*: the basic idea here is for a developer to write their
>>>> [...]
>>>>
>>>> We have a small amount of local test suites in the tree (e.g. vif and
>>>> disk config parsing have little test suites) but it could do with tying
>>>> together with some infrastructure into something which is simple to run
>>>> (currently it requires an installed Xen system and there is no one
>>>> single way to run something).
>>>>
>>>> As you correctly suggest there is a limit to how much local testing can
>>>> cover in terms of elapsed time, available resources, the configurations
>>>> which can be reasonably set up, running on real hardware etc. IMHO This
>>>> could benefit from an enthusiastic (or press-ganged by their
>>>> manager ;-)) community member putting some time into tying it all
>>>> together into something which we can ask people to run before submitti=
ng
>>>> with a straight face.
>>>>
>>>>
>>>>> *System testing*: both OSSTest and XenRT are essentially system test
>>>> [...]
>>>>
>>>> I think most people use "system testing" to mean testing of the
>>>> integrated whole, as opposed to e.g. unit testing. The current
>>>> "automated test" which we have covers some aspects of both whole system
>>>> and unit testing.
>>>>
>>>> Anyway, terminology aside, the existing osstest stuff is *extremely*
>>>> valuable IMHO, and the system testing has been very useful over the
>>>> majority of the lifetime of the xen project, at least as long as I've
>>>> been involved. The main limitation is the amount of resources dedicated
>>>> to it, in terms of hardware (and its location within citrix
>>>> infrastructure doesn't help here) and test coverage.
>>>>
>>>> Even with its current set of tests and limited hardware it already tes=
ts
>>>> far more than we could ever realistically ask people to do locally
>>>> before submitting and it catches real issues on real hardware.
>>>>
>>>> Any local test stuff should obviously be integrated into the system
>>>> tests as a step as well.
>>>>
>>>> I notice that your description of system test omits the targeted local
>>>> testing which we expect contributors to do before submitting a patch --
>>>> by targeted I mean you are changing $FOO therefore you should be trying
>>>> $FOO! And if you think you might have an impact on $BAR you should be
>>>> testing that too. I just mention it because your description seemed to
>>>> imply (inadvertently I expect) that there was no testing at all between
>>>> writing the code and the system tests running, which is not quite
>>>> accurate.
>>>>
>>>> IMHO both local and system test are valuable. I think the local testing
>>>> situation can be improved by people working within the community to do
>>>> the work (in particular building out the infrastructure), whereas the
>>>> system testing side of things would benefit greatly from any resourcing
>>>> which the AB can provide in terms of hardware, hosting and sysadmin ti=
me
>>>> etc. There is no doubt in my mind that this would be beneficial to the
>>>> community in both the short and long term.
>>>>
>>>> It might also be worth considering spending some money kickstarting the
>>>> actual tests (i.e. fleshing out the suites) in both cases, but I think
>>>> ultimately I think this needs to be driven by community member (AB or
>>>> otherwise) who care about particular functionality making sure the tes=
ts
>>>> exist, probably by writing them. So in terms of budget I think that
>>>> would be secondary to sorting out the hosting etc
>>>>
>>>>> *Test on demand:* this would be a mixture between local testing and
>>>> [...]
>>>>
>>>> I think it would be nice long term goal to aim for this but short term
>>>> the other two types of testing are more important.
>>>>
>>>>> IMHO, this would be a nice mid to long-term goal,
>>>>> assuming it could be made to work with the funds we have.
>>>> Heh, I should read right to the end ;-)
>>>>
>>>>> =3D=3D OSSTest =3D=3D
>>>>>
>>>>> What runs now and thus easiest to get started on
>>>>>
>>>>> More Info
>>>>> *http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-o=
sstest/
>>>>> *http://blog.xen.org/index.php/2013/09/30/osstest-standalone-mode-ste=
p-by-step/
>>>>> *http://www.youtube.com/watch?v=3DJxTFZIwZzJ8
>>>>>
>>>>> Problems:
>>>>> * Runs on Citrix premises (thus general access is an issue)
>>>>> * Ian Jackson is acting as sys-admin in his spare time. But, the
>>>>> Advisory Board could provide resource to fix this
>>>>> * Basic test coverage
>>>>> * Not a lot of documentation right now (which is a bit of a barrier to
>>>>> adoption)
>>>>>
>>>>> Risks
>>>>> * Not well understood (maybe you guys can fill the gaps)
>>>> This is slowly changing, Wei, Roger and myself have all done developme=
nt
>>>> with osstest and contributed (or are in the process of doing so) new
>>>> bits of testing. I think Dario and Anthony have played with it too.
>>>> There is certainly more which could be done here in terms of
>>>> documentation. I at least was planning to make this part of my focus on
>>>> future documentation and/or test days.
>>>>
>>>> I think all of the above applies equally to XenRT, either system is
>>>> going to have a learning curve and is going to need documentation for
>>>> the community etc.
>>>>
>>>>> =3D=3D XenRT =3D=3D
>>>>>
>>>>> Used by Citrix for XenServer testing. Tarballs have been made availab=
le
>>>>> by Citrix under a BSD license. But the code has not been put into live
>>>>> repos: my understanding is that Citrix would do this, if the Xen
>>>>> community believes this is valuable.
>>>>>
>>>>> More Info
>>>>> *http://wiki.xenproject.org/wiki/Getting_Started_with_XenRT
>>>>> *http://www.youtube.com/watch?v=3Ds11_Iw7AI_U
>>>>>
>>>>> Problems:
>>>>> * No publicly accessible demo instance (this is being worked on =96 t=
o be
>>>>> hosted on a small test bed at http://osuosl.org/ =96 work sponsored b=
y Citrix)
>>>>> * Currently does not yet support =93xl=94 (a =93xl=94 connector is be=
ing worked
>>>>> on =96 sponsored by Citrix)
>>>>> * Code not in yet public repo
>>>>>
>>>>> Potentially Interesting Properties:
>>>>> * Very large test coverage (including performance, security and other
>>>>> tests). Most of them should work once an =93xl=94 connector is in pla=
ce
>>>> I think that's rather optimistic. I would expect that a reasonable
>>>> proportion of the interesting tests will require features of xapi to
>>>> work, e.g. pools of hosts, storage management, networking etc and/or
>>>> require some amount of reworking to function with xl.
>>>>
>>>>> * Been in production at scale for a long time: thus well understood
>>>>> * XenRT has a lot of provisioning functionality and supports a
>>>>> distributed architecture: aka the ability to manage machines in
>>>>> different locations (data centres). The detail is abstracted away from
>>>>> users. This creates some interesting possibilities. For example:
>>>>> ** Hardware Vendors on the Advisory Board could provide hardware to t=
he
>>>>> community on their site (assuming that these can be hosted outside a
>>>>> firewall). Some HW vendors on the AB indicated that this would indeed=
 be
>>>>> doable.
>>>>> ** This would open up the opportunity to make available cutting edge =
or
>>>>> =93unusual=94 HW for testing to the community.
>>>>> ** It would also mean that machines that would be expensive to ship a=
nd
>>>>> host by the project, could be hosted on premise by AB vendors
>>>>> * XenRT has the capability to =93inject=94 some test code on the fly =
(i.e.
>>>>> the test code is attached to a job that is submitted).
>>>>> * I checked this with the XenRT devs and the *Test on demand* approach
>>>>> should be relatively easy to implement, but does not exist.
>>>>>
>>>>> I do not know what of the above would apply to OSSTest.
>>>> I think it is all equally doable for either.
>>>>
>>>>> Risks
>>>>> * Complexity
>>>>> * The cost of supporting such a system may be too high
>>>>> * Not in use by the community today
>>>>> * Not clear whether a *local test* version of XenRT is feasible
>>>>>
>>>>> =3D=3D Support and Ownership =3D=3D
>>>>>
>>>>> Whatever solution we go for, needs to be properly funded and looked
>>>>> after.
>>>>  From the remainder of the paragraph I think you are talking specifica=
lly
>>>> about hiring a test person here I think?
>>>>
>>>> I think this is essential, the current testing is done on a shoe string
>>>> and that is one of its main limiting factors.
>>>>
>>>>>   This is understood and the intention would be for the Xen Project
>>>>> (aka Advisory Board) to fund a Linux Foundation employee to do this on
>>>>> behalf of the Xen Project: this is a bit like Greg KH and others being
>>>>> LF employees working on the kernel. Some vendors on the Advisory Board
>>>>> indicated that providing Colo/hosting space and HW would be possible =
in
>>>>> principle, which could help keeping the cost manageable.
>>>> We should certainly be taking them up on those offers IMHO.
>>>>
>>>>> =3D=3D Access =3D=3D
>>>>>
>>>>> Any central system, has of course the issue of access control and
>>>>> managing users. This is obviously a barrier to entry (if we do not ha=
ve
>>>>> also a local test mechanism). Am wondering how other FOSS communities
>>>>> handle this. This should certainly be the job of the Test Framework
>>>>> owner (see above).
>>>> At a minimum it ought to be possible to allow access to any employee of
>>>> a project member, since we have the opportunity through the membership
>>>> process to put whatever paperwork and agreements (acceptable use etc) =
in
>>>> place.
>>>>
>>>> Unfettered access for anyone who rocks up and asks is a bit trickier.
>>>> I'm quite happy to let that be the framework owner's problem ;-)
>>>>
>>>> Ian.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 12:06:00 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 12:06: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 1WFjQy-0003li-1o; Tue, 18 Feb 2014 12:05:56 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFjQx-0003ld-Dg
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 12:05:55 +0000
Received: from [193.109.254.147:4116] by server-4.bemta-14.messagelabs.com id
	3A/FB-32066-2AC43035; Tue, 18 Feb 2014 12:05:54 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-16.tower-27.messagelabs.com!1392725151!5080859!1
X-Originating-IP: [209.85.220.45]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17197 invoked from network); 18 Feb 2014 12:05:53 -0000
Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com)
	(209.85.220.45)
	by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 12:05:53 -0000
Received: by mail-pa0-f45.google.com with SMTP id lf10so16524215pab.18
	for ;
	Tue, 18 Feb 2014 04:05:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=yFs4eBUflxMpq0SMzFFeW5uv4bw6/JMxOjpjAsRowb4=;
	b=rdNvTFXOFFd3IPmfbE76ih+6oMnpydYbEGea2uzMf03fhXlsM8ejnTq2Ll/Pctuo26
	RImPxmCJhXaRi0PzIT++R/XB61twB6vWhcRvVXJ9q+4gd23Mrb6ibVi1ZHClXK4zczh+
	DzX9+Tj2CyYsYmd8gfUcOZkyVlIYgZkyJRY5ylQAXNt/Ub5VDA4tDPrWoOJtqA6nCRZw
	IWTpk6Kr9qWMUd2ItjXK2UbEPqkeXrEYGmeYzUueQOtBYExlNhNgDWDdkULrQV+EK0Z/
	nmDtbl4Pa6WE4LkktUPGaGEzEflFMCzI2ECfjNQBukbBhUcOzL6ZsNwze7r91sKCzING
	L4gg==
MIME-Version: 1.0
X-Received: by 10.66.139.100 with SMTP id qx4mr10053947pab.141.1392725151136; 
	Tue, 18 Feb 2014 04:05:51 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Tue, 18 Feb 2014 04:05:51 -0800 (PST)
Date: Tue, 18 Feb 2014 12:05:51 +0000
Message-ID: 
From: David Scott 
To: "mirageos-devel@lists.xenproject.org" 
Subject: [MirageOS-devel] multiple block devices under xen
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8875737177495699081=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============8875737177495699081==
Content-Type: multipart/alternative; boundary=001a113315dee73fcd04f2ad176d

--001a113315dee73fcd04f2ad176d
Content-Type: text/plain; charset=ISO-8859-1

In last week's call I promised to email some notes on creating Mirage apps
with multiple block devices under xen.

Background
----------

When a disk is added to a VM (under Xen, KVM, any hypervisor) it's like
plugging in a PCI device into a physical box -- a disk will appear in some
kind of numbered "slot" on a "bus". In xen the "slot" number is the name of
the directory in xenstore (/local/domain//device/vbd/) and the
in-guest blkfront driver manages the "bus". From the point of view of
Mirage, or Windows with the Citrix PV drivers, the slot number can be any
unique integer: the devices will be enumerated and associated with the slot
numbers. Windows will then look for partition labels and volumes inside the
disks which means that everything still works even if you change the slot
numbers. Mirage should probably do this too, but I've not written this code
yet.

>From the Linux perspective, the *convention* is that the "slot" number is
the device node (major-number << 8 || minor-number): blkback will use this
to create this kernel device. Next, udev (or something similar) will
trigger and actually create a named device node. This is an old convention
which dates back to the early days of xen when it was common to create
device nodes which pretended to be the individual partitions of SCSI disks.
These days the modern twist is to stick to device numbers which correspond
to the special /dev/xvd[a-z] devices: 51712, 51768 etc -- this is what you
see inside a regular Linux guest.

Note that it doesn't really matter what the disk is made of: it could be a
file in /tmp, an iSCSI LUN or a Ceph block device, in all cases it will
just appear as a disk in a slot on a bus. In general the VM won't be able
to find out where the physical disk came from.

Xen disk support
----------------

Xen supports different backing disk formats (e.g. raw, qcow2, vhd) and
"backend types" (e.g. via kernel blkback, via userspace tapdisk, via
userspace qemu). I recommend keeping it simple and sticking to raw format.
The "backend type" which is simplest (and will give you the least amount of
trouble) is kernel blkback (also known as "phy"). The only snag is that
blkback can only read from block devices itself i.e. LVM volumes, real
disks or loopback devices.

You can create a raw (sparse) disk file like so:

dd if=/dev/zero of=disk.raw bs=1M seek=16 count=0

and then create a loop device like so:

sudo losetup /dev/loop0 disk.raw

(where /dev/loop0 is any free loop device. Note the total number of loop
devices is determined at module load time, it's not dynamic unfortunately
(last time I checked anyway))

Whatever you do, don't mix I/O to the /dev/loop device with I/O to the file
-- it won't be coherent. For example if you modify disk.raw you'll still
see stale cached data if you read /dev/loop0.

To attach /dev/loop0 to your VM with slot 51712 ( == /dev/xvda) and
/dev/loop1 to your VM with slot 51768 (== /dev/xvdb) you would write:

>>>>
# The disk configuration is defined here:
# http://xenbits.xen.org/docs/4.3-testing/misc/xl-disk-configuration.txt
# An example would look like:
disk = [ '/dev/loop0,,xvda', '/dev/loop1,,xvdb' ]
<<<<

I'm not sure what other strings you can write other than 'xvda' 'xvdb' etc
-- using the Linux devices is awkward if you're not actually running Linux.
For reference, an OCaml module to convert between them works like this:

>>>>
utop # #require "mirage-block-xen";;
utop # Device_number.(to_linux_device (of_disk_number false 0))
;;
- : string = "xvda"
utop # Device_number.(to_xenstore_key (of_disk_number false 0))
;;
- : int = 51712
<<<<

Mirage
------

When we write the config.ml for a mirage app we define our block devices
like this:

>>>>
let block = {
  Block.name = "myfile";
  filename   = "./disk.raw";
  read_only  = false;
}

let () = Job.register [
    "Block_test.Main", [Driver.console; Driver.Block block]
  ]
<<<<

The generated code will call 'Block.connect "./disk.raw"' and expect the
block device backed by "./disk.raw" to be opened. This is fine in userspace
where you can simply open the file directly, but with a hypervisor you have
to present the file as a block device, and somehow link this block device
to the original filename.

The simplest thing to do is to modify the filename to

  filename = "51712"

The [Block.connect "51712"] will interpret the string as the slot number,
and open the device.

This is obviously not ideal. Perhaps in future we can:
* make "mirage" generate an .xl config file which references the file
(rather than a block device) and rely on the hotplug scripts to manage the
loop device. This should work, but since there are more moving parts, may
be flaky on your particular distro.
* make "Block.connect" take some kind of volume label rather than a device
id, so mirage-block-{unix,xen} can cope with disks being presented in any
order on the bus

HTH!

-- 
Dave Scott

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


In last week's call I promised to email some notes on =
creating Mirage apps with multiple block devices under xen.

<=
div>Background
----------

When a disk is=
 added to a VM (under Xen, KVM, any hypervisor) it's like plugging in a=
 PCI device into a physical box -- a disk will appear in some kind of numbe=
red "slot" on a "bus". In xen the "slot" numb=
er is the name of the directory in xenstore (/local/domain/<domid>/de=
vice/vbd/<slot>) and the in-guest blkfront driver manages the "b=
us". From the point of view of Mirage, or Windows with the Citrix PV d=
rivers, the slot number can be any unique integer: the devices will be enum=
erated and associated with the slot numbers. Windows will then look for par=
tition labels and volumes inside the disks which means that everything stil=
l works even if you change the slot numbers. Mirage should probably do this=
 too, but I've not written this code yet.



From the Linux perspective, the *convention* is that th=
e "slot" number is the device node (major-number << 8 || mi=
nor-number): blkback will use this to create this kernel device. Next, udev=
 (or something similar) will trigger and actually create a named device nod=
e. This is an old convention which dates back to the early days of xen when=
 it was common to create device nodes which pretended to be the individual =
partitions of SCSI disks. These days the modern twist is to stick to device=
 numbers which correspond to the special /dev/xvd[a-z] devices: 51712, 5176=
8 etc -- this is what you see inside a regular Linux guest.



Note that it doesn't really matter what the disk is=
 made of: it could be a file in /tmp, an iSCSI LUN or a Ceph block device, =
in all cases it will just appear as a disk in a slot on a bus. In general t=
he VM won't be able to find out where the physical disk came from.


Xen disk support
----------------
<=
br>
Xen supports different backing disk formats (e.g. raw, qcow2,=
 vhd) and "backend types" (e.g. via kernel blkback, via userspace=
 tapdisk, via userspace qemu). I recommend keeping it simple and sticking t=
o raw format. The "backend type" which is simplest (and will give=
 you the least amount of trouble) is kernel blkback (also known as "ph=
y"). The only snag is that blkback can only read from block devices it=
self i.e. LVM volumes, real disks or loopback devices.



You can create a raw (sparse) disk file like so:
<=
div>
dd if=3D/dev/zero of=3Ddisk.raw bs=3D1M seek=3D16 count=
=3D0

and then create a loop device like so:
<=
div>


sudo losetup /dev/loop0 disk.raw

(where=
 /dev/loop0 is any free loop device. Note the total number of loop devices =
is determined at module load time, it's not dynamic unfortunately (last=
 time I checked anyway))



Whatever you do, don't mix I/O to the /dev/loop dev=
ice with I/O to the file -- it won't be coherent. For example if you mo=
dify disk.raw you'll still see stale cached data if you read /dev/loop0=
.



To attach /dev/loop0 to your VM with slot 51712 ( =3D=
=3D /dev/xvda) and /dev/loop1 to your VM with slot 51768 (=3D=3D /dev/xvdb)=
 you would write:

>>>>
=
# The disk configuration is defined here:


# An example would look like:
disk =3D [=
 '/dev/loop0,,xvda', '/dev/loop1,,xvdb' ]


<<<<

I'm not sure what =
other strings you can write other than 'xvda' 'xvdb' etc --=
 using the Linux devices is awkward if you're not actually running Linu=
x. For reference, an OCaml module to convert between them works like this:<=
/div>


>>>>
utop # #require "m=
irage-block-xen";;
utop # Device_number.(to_linux=
_device (of_disk_number false 0))
;;
- : string =3D &qu=
ot;xvda"=A0


utop # Device_number.(to_xenstore_key (of_disk_number false=
 0))
;;
- : int =3D 51712
<<<&=
lt;

Mirage
------



When we write the config.ml for a mir=
age app we define our block devices like this:

>=
;>>>
let block =3D {
=A0 Block.name =3D &=
quot;myfile";


=A0 filename =A0 =3D "./disk.raw";
=A0 read_only =
=A0=3D false;
}

let () =3D Job.register =
[
=A0 =A0 "Block_test.Main", [Driver.console; Driver.Bl=
ock block]


=A0 ]
<<<<

Th=
e generated code will call 'Block.connect "./disk.raw"' a=
nd expect the block device backed by "./disk.raw" to be opened. T=
his is fine in userspace where you can simply open the file directly, but w=
ith a hypervisor you have to present the file as a block device, and someho=
w link this block device to the original filename.



The simplest thing to do is to modify the filename to

=A0 filename =3D "51712"

The [Block.connect "51712"] will interpret the string as=
 the slot number, and open the device.



This is obviously not ideal. Perhaps in future we can:<=
/div>
* make "mirage" generate an .xl config file which refer=
ences the file (rather than a block device) and rely on the hotplug scripts=
 to manage the loop device. This should work, but since there are more movi=
ng parts, may be flaky on your particular distro.


* make "Block.connect" take some kind of volume label rather=
 than a device id, so mirage-block-{unix,xen} can cope with disks being pre=
sented in any order on the bus
=A0
HTH!



-- 
Dave Scott



--001a113315dee73fcd04f2ad176d--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============8875737177495699081==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 12:06:00 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 12:06: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 1WFjQy-0003li-1o; Tue, 18 Feb 2014 12:05:56 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFjQx-0003ld-Dg
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 12:05:55 +0000
Received: from [193.109.254.147:4116] by server-4.bemta-14.messagelabs.com id
	3A/FB-32066-2AC43035; Tue, 18 Feb 2014 12:05:54 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-16.tower-27.messagelabs.com!1392725151!5080859!1
X-Originating-IP: [209.85.220.45]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17197 invoked from network); 18 Feb 2014 12:05:53 -0000
Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com)
	(209.85.220.45)
	by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 12:05:53 -0000
Received: by mail-pa0-f45.google.com with SMTP id lf10so16524215pab.18
	for ;
	Tue, 18 Feb 2014 04:05:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=yFs4eBUflxMpq0SMzFFeW5uv4bw6/JMxOjpjAsRowb4=;
	b=rdNvTFXOFFd3IPmfbE76ih+6oMnpydYbEGea2uzMf03fhXlsM8ejnTq2Ll/Pctuo26
	RImPxmCJhXaRi0PzIT++R/XB61twB6vWhcRvVXJ9q+4gd23Mrb6ibVi1ZHClXK4zczh+
	DzX9+Tj2CyYsYmd8gfUcOZkyVlIYgZkyJRY5ylQAXNt/Ub5VDA4tDPrWoOJtqA6nCRZw
	IWTpk6Kr9qWMUd2ItjXK2UbEPqkeXrEYGmeYzUueQOtBYExlNhNgDWDdkULrQV+EK0Z/
	nmDtbl4Pa6WE4LkktUPGaGEzEflFMCzI2ECfjNQBukbBhUcOzL6ZsNwze7r91sKCzING
	L4gg==
MIME-Version: 1.0
X-Received: by 10.66.139.100 with SMTP id qx4mr10053947pab.141.1392725151136; 
	Tue, 18 Feb 2014 04:05:51 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Tue, 18 Feb 2014 04:05:51 -0800 (PST)
Date: Tue, 18 Feb 2014 12:05:51 +0000
Message-ID: 
From: David Scott 
To: "mirageos-devel@lists.xenproject.org" 
Subject: [MirageOS-devel] multiple block devices under xen
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8875737177495699081=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============8875737177495699081==
Content-Type: multipart/alternative; boundary=001a113315dee73fcd04f2ad176d

--001a113315dee73fcd04f2ad176d
Content-Type: text/plain; charset=ISO-8859-1

In last week's call I promised to email some notes on creating Mirage apps
with multiple block devices under xen.

Background
----------

When a disk is added to a VM (under Xen, KVM, any hypervisor) it's like
plugging in a PCI device into a physical box -- a disk will appear in some
kind of numbered "slot" on a "bus". In xen the "slot" number is the name of
the directory in xenstore (/local/domain//device/vbd/) and the
in-guest blkfront driver manages the "bus". From the point of view of
Mirage, or Windows with the Citrix PV drivers, the slot number can be any
unique integer: the devices will be enumerated and associated with the slot
numbers. Windows will then look for partition labels and volumes inside the
disks which means that everything still works even if you change the slot
numbers. Mirage should probably do this too, but I've not written this code
yet.

>From the Linux perspective, the *convention* is that the "slot" number is
the device node (major-number << 8 || minor-number): blkback will use this
to create this kernel device. Next, udev (or something similar) will
trigger and actually create a named device node. This is an old convention
which dates back to the early days of xen when it was common to create
device nodes which pretended to be the individual partitions of SCSI disks.
These days the modern twist is to stick to device numbers which correspond
to the special /dev/xvd[a-z] devices: 51712, 51768 etc -- this is what you
see inside a regular Linux guest.

Note that it doesn't really matter what the disk is made of: it could be a
file in /tmp, an iSCSI LUN or a Ceph block device, in all cases it will
just appear as a disk in a slot on a bus. In general the VM won't be able
to find out where the physical disk came from.

Xen disk support
----------------

Xen supports different backing disk formats (e.g. raw, qcow2, vhd) and
"backend types" (e.g. via kernel blkback, via userspace tapdisk, via
userspace qemu). I recommend keeping it simple and sticking to raw format.
The "backend type" which is simplest (and will give you the least amount of
trouble) is kernel blkback (also known as "phy"). The only snag is that
blkback can only read from block devices itself i.e. LVM volumes, real
disks or loopback devices.

You can create a raw (sparse) disk file like so:

dd if=/dev/zero of=disk.raw bs=1M seek=16 count=0

and then create a loop device like so:

sudo losetup /dev/loop0 disk.raw

(where /dev/loop0 is any free loop device. Note the total number of loop
devices is determined at module load time, it's not dynamic unfortunately
(last time I checked anyway))

Whatever you do, don't mix I/O to the /dev/loop device with I/O to the file
-- it won't be coherent. For example if you modify disk.raw you'll still
see stale cached data if you read /dev/loop0.

To attach /dev/loop0 to your VM with slot 51712 ( == /dev/xvda) and
/dev/loop1 to your VM with slot 51768 (== /dev/xvdb) you would write:

>>>>
# The disk configuration is defined here:
# http://xenbits.xen.org/docs/4.3-testing/misc/xl-disk-configuration.txt
# An example would look like:
disk = [ '/dev/loop0,,xvda', '/dev/loop1,,xvdb' ]
<<<<

I'm not sure what other strings you can write other than 'xvda' 'xvdb' etc
-- using the Linux devices is awkward if you're not actually running Linux.
For reference, an OCaml module to convert between them works like this:

>>>>
utop # #require "mirage-block-xen";;
utop # Device_number.(to_linux_device (of_disk_number false 0))
;;
- : string = "xvda"
utop # Device_number.(to_xenstore_key (of_disk_number false 0))
;;
- : int = 51712
<<<<

Mirage
------

When we write the config.ml for a mirage app we define our block devices
like this:

>>>>
let block = {
  Block.name = "myfile";
  filename   = "./disk.raw";
  read_only  = false;
}

let () = Job.register [
    "Block_test.Main", [Driver.console; Driver.Block block]
  ]
<<<<

The generated code will call 'Block.connect "./disk.raw"' and expect the
block device backed by "./disk.raw" to be opened. This is fine in userspace
where you can simply open the file directly, but with a hypervisor you have
to present the file as a block device, and somehow link this block device
to the original filename.

The simplest thing to do is to modify the filename to

  filename = "51712"

The [Block.connect "51712"] will interpret the string as the slot number,
and open the device.

This is obviously not ideal. Perhaps in future we can:
* make "mirage" generate an .xl config file which references the file
(rather than a block device) and rely on the hotplug scripts to manage the
loop device. This should work, but since there are more moving parts, may
be flaky on your particular distro.
* make "Block.connect" take some kind of volume label rather than a device
id, so mirage-block-{unix,xen} can cope with disks being presented in any
order on the bus

HTH!

-- 
Dave Scott

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


In last week's call I promised to email some notes on =
creating Mirage apps with multiple block devices under xen.

<=
div>Background
----------

When a disk is=
 added to a VM (under Xen, KVM, any hypervisor) it's like plugging in a=
 PCI device into a physical box -- a disk will appear in some kind of numbe=
red "slot" on a "bus". In xen the "slot" numb=
er is the name of the directory in xenstore (/local/domain/<domid>/de=
vice/vbd/<slot>) and the in-guest blkfront driver manages the "b=
us". From the point of view of Mirage, or Windows with the Citrix PV d=
rivers, the slot number can be any unique integer: the devices will be enum=
erated and associated with the slot numbers. Windows will then look for par=
tition labels and volumes inside the disks which means that everything stil=
l works even if you change the slot numbers. Mirage should probably do this=
 too, but I've not written this code yet.



From the Linux perspective, the *convention* is that th=
e "slot" number is the device node (major-number << 8 || mi=
nor-number): blkback will use this to create this kernel device. Next, udev=
 (or something similar) will trigger and actually create a named device nod=
e. This is an old convention which dates back to the early days of xen when=
 it was common to create device nodes which pretended to be the individual =
partitions of SCSI disks. These days the modern twist is to stick to device=
 numbers which correspond to the special /dev/xvd[a-z] devices: 51712, 5176=
8 etc -- this is what you see inside a regular Linux guest.



Note that it doesn't really matter what the disk is=
 made of: it could be a file in /tmp, an iSCSI LUN or a Ceph block device, =
in all cases it will just appear as a disk in a slot on a bus. In general t=
he VM won't be able to find out where the physical disk came from.


Xen disk support
----------------
<=
br>
Xen supports different backing disk formats (e.g. raw, qcow2,=
 vhd) and "backend types" (e.g. via kernel blkback, via userspace=
 tapdisk, via userspace qemu). I recommend keeping it simple and sticking t=
o raw format. The "backend type" which is simplest (and will give=
 you the least amount of trouble) is kernel blkback (also known as "ph=
y"). The only snag is that blkback can only read from block devices it=
self i.e. LVM volumes, real disks or loopback devices.



You can create a raw (sparse) disk file like so:
<=
div>
dd if=3D/dev/zero of=3Ddisk.raw bs=3D1M seek=3D16 count=
=3D0

and then create a loop device like so:
<=
div>


sudo losetup /dev/loop0 disk.raw

(where=
 /dev/loop0 is any free loop device. Note the total number of loop devices =
is determined at module load time, it's not dynamic unfortunately (last=
 time I checked anyway))



Whatever you do, don't mix I/O to the /dev/loop dev=
ice with I/O to the file -- it won't be coherent. For example if you mo=
dify disk.raw you'll still see stale cached data if you read /dev/loop0=
.



To attach /dev/loop0 to your VM with slot 51712 ( =3D=
=3D /dev/xvda) and /dev/loop1 to your VM with slot 51768 (=3D=3D /dev/xvdb)=
 you would write:

>>>>
=
# The disk configuration is defined here:


# An example would look like:
disk =3D [=
 '/dev/loop0,,xvda', '/dev/loop1,,xvdb' ]


<<<<

I'm not sure what =
other strings you can write other than 'xvda' 'xvdb' etc --=
 using the Linux devices is awkward if you're not actually running Linu=
x. For reference, an OCaml module to convert between them works like this:<=
/div>


>>>>
utop # #require "m=
irage-block-xen";;
utop # Device_number.(to_linux=
_device (of_disk_number false 0))
;;
- : string =3D &qu=
ot;xvda"=A0


utop # Device_number.(to_xenstore_key (of_disk_number false=
 0))
;;
- : int =3D 51712
<<<&=
lt;

Mirage
------



When we write the config.ml for a mir=
age app we define our block devices like this:

>=
;>>>
let block =3D {
=A0 Block.name =3D &=
quot;myfile";


=A0 filename =A0 =3D "./disk.raw";
=A0 read_only =
=A0=3D false;
}

let () =3D Job.register =
[
=A0 =A0 "Block_test.Main", [Driver.console; Driver.Bl=
ock block]


=A0 ]
<<<<

Th=
e generated code will call 'Block.connect "./disk.raw"' a=
nd expect the block device backed by "./disk.raw" to be opened. T=
his is fine in userspace where you can simply open the file directly, but w=
ith a hypervisor you have to present the file as a block device, and someho=
w link this block device to the original filename.



The simplest thing to do is to modify the filename to

=A0 filename =3D "51712"

The [Block.connect "51712"] will interpret the string as=
 the slot number, and open the device.



This is obviously not ideal. Perhaps in future we can:<=
/div>
* make "mirage" generate an .xl config file which refer=
ences the file (rather than a block device) and rely on the hotplug scripts=
 to manage the loop device. This should work, but since there are more movi=
ng parts, may be flaky on your particular distro.


* make "Block.connect" take some kind of volume label rather=
 than a device id, so mirage-block-{unix,xen} can cope with disks being pre=
sented in any order on the bus
=A0
HTH!



-- 
Dave Scott



--001a113315dee73fcd04f2ad176d--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============8875737177495699081==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 12:10:22 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 12:10: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 1WFjVG-0003pQ-3y; Tue, 18 Feb 2014 12:10:22 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFjVF-0003pK-3S
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 12:10:21 +0000
Received: from [85.158.137.68:28472] by server-16.bemta-3.messagelabs.com id
	F7/7D-29917-CAD43035; Tue, 18 Feb 2014 12:10:20 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-5.tower-31.messagelabs.com!1392725419!1364407!1
X-Originating-IP: [209.85.212.179]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18417 invoked from network); 18 Feb 2014 12:10:19 -0000
Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com)
	(209.85.212.179)
	by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 12:10:19 -0000
Received: by mail-wi0-f179.google.com with SMTP id hn9so3394970wib.6
	for ;
	Tue, 18 Feb 2014 04:10:19 -0800 (PST)
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=J+bWIVBwhlgT9bYuMNPfkVmCHZAmOKvmSW32qe3mbco=;
	b=EpsspNwUxfIm7LjGQwSIDtU5TZzUBld+c1fqynM8FBG5rG5yOAybfqzQdAmXVrmnu3
	ppSdX29JYY3EkDtTxJ9V4VuoTee/r6nAg9naVySrr2V9f/4QGr6sWak1R1VAxVMxc76d
	AMzmFnvl4S+JU1zqxfCPts5yJyOxmRspXWtbLB3qVG1T+T6EpiSx9cH7UG6WzYUME4cJ
	/ttfE7hZ510fRm1bs4cPg0JMQadZ3aqTgrYeRC34hCwdRd4WNTkkdM14MleSgIa+rEJx
	05Yk/CyAFHA7Ex9Pye9ec4LUibu6RpWmV972E6ugs7saiR3nTTUmyq7nbqwdb6zJ6j/B
	sStg==
X-Received: by 10.180.205.130 with SMTP id lg2mr17359085wic.59.1392725419263; 
	Tue, 18 Feb 2014 04:10:19 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id ee5sm19346462wib.8.2014.02.18.04.10.18
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 18 Feb 2014 04:10:18 -0800 (PST)
Message-ID: <53034DA9.3050807@xen.org>
Date: Tue, 18 Feb 2014 12:10:17 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Amir Chaudhry 
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
	<637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
In-Reply-To: <637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Minutes are up : 
http://lists.xenproject.org/archives/html/wg-test-framework/2014-02/msg00004.html
However, I think Mirage would need to engage with Ian as community rep 
and Mirage support woul dbe under long term goals I would assume
Lars

On 17/02/2014 18:05, Amir Chaudhry wrote:
> Hi Lars,
>
> I'm curious about where things stand with the testing for the Xen project.  I've gone through the wg-test-framework archives and tried to catchup with minutes. I'm wondering when the next set will be posted (from the meeting on the 13th).
>
> Having a testing setup for Xen would be really useful for Mirage.  Since we're having more people try out our tutorials and knowing the state of things in different environments would help us catch issues quicker.
>
> Thanks,
> Amir
>
>


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 12:10:22 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 12:10: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 1WFjVG-0003pQ-3y; Tue, 18 Feb 2014 12:10:22 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFjVF-0003pK-3S
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 12:10:21 +0000
Received: from [85.158.137.68:28472] by server-16.bemta-3.messagelabs.com id
	F7/7D-29917-CAD43035; Tue, 18 Feb 2014 12:10:20 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-5.tower-31.messagelabs.com!1392725419!1364407!1
X-Originating-IP: [209.85.212.179]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18417 invoked from network); 18 Feb 2014 12:10:19 -0000
Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com)
	(209.85.212.179)
	by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 12:10:19 -0000
Received: by mail-wi0-f179.google.com with SMTP id hn9so3394970wib.6
	for ;
	Tue, 18 Feb 2014 04:10:19 -0800 (PST)
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=J+bWIVBwhlgT9bYuMNPfkVmCHZAmOKvmSW32qe3mbco=;
	b=EpsspNwUxfIm7LjGQwSIDtU5TZzUBld+c1fqynM8FBG5rG5yOAybfqzQdAmXVrmnu3
	ppSdX29JYY3EkDtTxJ9V4VuoTee/r6nAg9naVySrr2V9f/4QGr6sWak1R1VAxVMxc76d
	AMzmFnvl4S+JU1zqxfCPts5yJyOxmRspXWtbLB3qVG1T+T6EpiSx9cH7UG6WzYUME4cJ
	/ttfE7hZ510fRm1bs4cPg0JMQadZ3aqTgrYeRC34hCwdRd4WNTkkdM14MleSgIa+rEJx
	05Yk/CyAFHA7Ex9Pye9ec4LUibu6RpWmV972E6ugs7saiR3nTTUmyq7nbqwdb6zJ6j/B
	sStg==
X-Received: by 10.180.205.130 with SMTP id lg2mr17359085wic.59.1392725419263; 
	Tue, 18 Feb 2014 04:10:19 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id ee5sm19346462wib.8.2014.02.18.04.10.18
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 18 Feb 2014 04:10:18 -0800 (PST)
Message-ID: <53034DA9.3050807@xen.org>
Date: Tue, 18 Feb 2014 12:10:17 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Amir Chaudhry 
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
	<637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
In-Reply-To: <637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Minutes are up : 
http://lists.xenproject.org/archives/html/wg-test-framework/2014-02/msg00004.html
However, I think Mirage would need to engage with Ian as community rep 
and Mirage support woul dbe under long term goals I would assume
Lars

On 17/02/2014 18:05, Amir Chaudhry wrote:
> Hi Lars,
>
> I'm curious about where things stand with the testing for the Xen project.  I've gone through the wg-test-framework archives and tried to catchup with minutes. I'm wondering when the next set will be posted (from the meeting on the 13th).
>
> Having a testing setup for Xen would be really useful for Mirage.  Since we're having more people try out our tutorials and knowing the state of things in different environments would help us catch issues quicker.
>
> Thanks,
> Amir
>
>


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 12:19:03 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 12:19: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 1WFjdd-0004Ky-2u; Tue, 18 Feb 2014 12:19:01 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFjdb-0004Kk-AT
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 12:18:59 +0000
Received: from [85.158.139.211:9882] by server-2.bemta-5.messagelabs.com id
	FF/C8-23037-2BF43035; Tue, 18 Feb 2014 12:18:58 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-4.tower-206.messagelabs.com!1392725937!4654873!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32090 invoked from network); 18 Feb 2014 12:18:57 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-4.tower-206.messagelabs.com with SMTP;
	18 Feb 2014 12:18:57 -0000
Received: (qmail 22787 invoked by uid 634); 18 Feb 2014 12:18:57 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 18 Feb 2014 12:18:56 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <53034DA9.3050807@xen.org>
Date: Tue, 18 Feb 2014 12:18:54 +0000
Message-Id: <93000E7C-4FA9-4AE6-8462-2899921A9191@recoil.org>
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
	<637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
	<53034DA9.3050807@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Ian Campbell ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

[+CC Ian Campbell]

Our specific need is actually pretty short term -- we can easily build a number of 'unit test' kernels that do simple activities such as boot, write to xenstore, attach a net/block front, and verify basic health conditions (such as whether the backend moves to the connected state).

Distro support for a lot of this seems to be in a variable state across the board.  For instance, we'd like to have a known-good configuration for Debian, Ubuntu, Fedora and CentOS in terms of which toolchain to use (xl, xm, libvirt in particular) and what configurations to recommend to users installing Xen.  Debian stable is still on XM for instance, with an unclear story on libvirt support, whereas Ubuntu appears to have problems with xl and starting up blktap.

More structured unit tests that run on all these platforms would be extremely useful to highlight issues early, and Mirage provides an easy way to build these tests (see https://github.com/mirage/mirage-skeleton for a growing number).

We don't really have the resources to maintain the sysadmin infrastructure for these tests, but can certainly help with triaging failures.  The biggest blocker for new users of Mirage that I've talked to (often unfamiliar with both OCaml and Xen) has usually been getting to a working Xen installation, so I'd like to have a few recommended setups as soon as possible. 

cheers,
Anil

On 18 Feb 2014, at 12:10, Lars Kurth  wrote:

> Minutes are up : http://lists.xenproject.org/archives/html/wg-test-framework/2014-02/msg00004.html
> However, I think Mirage would need to engage with Ian as community rep and Mirage support woul dbe under long term goals I would assume
> Lars
> 
> On 17/02/2014 18:05, Amir Chaudhry wrote:
>> Hi Lars,
>> 
>> I'm curious about where things stand with the testing for the Xen project.  I've gone through the wg-test-framework archives and tried to catchup with minutes. I'm wondering when the next set will be posted (from the meeting on the 13th).
>> 
>> Having a testing setup for Xen would be really useful for Mirage.  Since we're having more people try out our tutorials and knowing the state of things in different environments would help us catch issues quicker.
>> 
>> Thanks,
>> Amir
>> 
>> 
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 12:19:03 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 12:19: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 1WFjdd-0004Ky-2u; Tue, 18 Feb 2014 12:19:01 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFjdb-0004Kk-AT
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 12:18:59 +0000
Received: from [85.158.139.211:9882] by server-2.bemta-5.messagelabs.com id
	FF/C8-23037-2BF43035; Tue, 18 Feb 2014 12:18:58 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-4.tower-206.messagelabs.com!1392725937!4654873!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32090 invoked from network); 18 Feb 2014 12:18:57 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-4.tower-206.messagelabs.com with SMTP;
	18 Feb 2014 12:18:57 -0000
Received: (qmail 22787 invoked by uid 634); 18 Feb 2014 12:18:57 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 18 Feb 2014 12:18:56 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <53034DA9.3050807@xen.org>
Date: Tue, 18 Feb 2014 12:18:54 +0000
Message-Id: <93000E7C-4FA9-4AE6-8462-2899921A9191@recoil.org>
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
	<637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
	<53034DA9.3050807@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Ian Campbell ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

[+CC Ian Campbell]

Our specific need is actually pretty short term -- we can easily build a number of 'unit test' kernels that do simple activities such as boot, write to xenstore, attach a net/block front, and verify basic health conditions (such as whether the backend moves to the connected state).

Distro support for a lot of this seems to be in a variable state across the board.  For instance, we'd like to have a known-good configuration for Debian, Ubuntu, Fedora and CentOS in terms of which toolchain to use (xl, xm, libvirt in particular) and what configurations to recommend to users installing Xen.  Debian stable is still on XM for instance, with an unclear story on libvirt support, whereas Ubuntu appears to have problems with xl and starting up blktap.

More structured unit tests that run on all these platforms would be extremely useful to highlight issues early, and Mirage provides an easy way to build these tests (see https://github.com/mirage/mirage-skeleton for a growing number).

We don't really have the resources to maintain the sysadmin infrastructure for these tests, but can certainly help with triaging failures.  The biggest blocker for new users of Mirage that I've talked to (often unfamiliar with both OCaml and Xen) has usually been getting to a working Xen installation, so I'd like to have a few recommended setups as soon as possible. 

cheers,
Anil

On 18 Feb 2014, at 12:10, Lars Kurth  wrote:

> Minutes are up : http://lists.xenproject.org/archives/html/wg-test-framework/2014-02/msg00004.html
> However, I think Mirage would need to engage with Ian as community rep and Mirage support woul dbe under long term goals I would assume
> Lars
> 
> On 17/02/2014 18:05, Amir Chaudhry wrote:
>> Hi Lars,
>> 
>> I'm curious about where things stand with the testing for the Xen project.  I've gone through the wg-test-framework archives and tried to catchup with minutes. I'm wondering when the next set will be posted (from the meeting on the 13th).
>> 
>> Having a testing setup for Xen would be really useful for Mirage.  Since we're having more people try out our tutorials and knowing the state of things in different environments would help us catch issues quicker.
>> 
>> Thanks,
>> Amir
>> 
>> 
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 12:25:28 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 12:25: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 1WFjjr-0004Zn-NA; Tue, 18 Feb 2014 12:25:27 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFjjq-0004Zi-C9
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 12:25:26 +0000
Received: from [85.158.139.211:10229] by server-7.bemta-5.messagelabs.com id
	1F/45-14867-53153035; Tue, 18 Feb 2014 12:25:25 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-13.tower-206.messagelabs.com!1392726323!4655796!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1899 invoked from network); 18 Feb 2014 12:25:24 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 12:25:24 -0000
X-IronPort-AV: E=Sophos;i="4.97,501,1389744000"; d="scan'208";a="103446684"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 18 Feb 2014 12:25:22 +0000
Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL02.citrite.net
	(10.13.107.79) with Microsoft SMTP Server id 14.2.342.4;
	Tue, 18 Feb 2014 07:25:21 -0500
Message-ID: <1392726320.11080.53.camel@kazak.uk.xensource.com>
From: Ian Campbell 
To: Anil Madhavapeddy 
Date: Tue, 18 Feb 2014 12:25:20 +0000
In-Reply-To: <93000E7C-4FA9-4AE6-8462-2899921A9191@recoil.org>
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
	<637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
	<53034DA9.3050807@xen.org>
	<93000E7C-4FA9-4AE6-8462-2899921A9191@recoil.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA1
Cc: Ian Jackson ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On Tue, 2014-02-18 at 12:18 +0000, Anil Madhavapeddy wrote:
> [+CC Ian Campbell]

Ian Jackson is the communioty WG member. Adding another CC ;-)

> 
> Our specific need is actually pretty short term -- we can easily build a number of 'unit test' kernels that do simple activities such as boot, write to xenstore, attach a net/block front, and verify basic health conditions (such as whether the backend moves to the connected state).
> 
> Distro support for a lot of this seems to be in a variable state across the board.  For instance, we'd like to have a known-good configuration for Debian, Ubuntu, Fedora and CentOS in terms of which toolchain to use (xl, xm, libvirt in particular) and what configurations to recommend to users installing Xen.  Debian stable is still on XM for instance, with an unclear story on libvirt support, whereas Ubuntu appears to have problems with xl and starting up blktap.
> 
> More structured unit tests that run on all these platforms would be extremely useful to highlight issues early, and Mirage provides an easy way to build these tests (see https://github.com/mirage/mirage-skeleton for a growing number).
> 
> We don't really have the resources to maintain the sysadmin infrastructure for these tests, but can certainly help with triaging failures.  The biggest blocker for new users of Mirage that I've talked to (often unfamiliar with both OCaml and Xen) has usually been getting to a working Xen installation, so I'd like to have a few recommended setups as soon as possible. 
> 
> cheers,
> Anil
> 
> On 18 Feb 2014, at 12:10, Lars Kurth  wrote:
> 
> > Minutes are up : http://lists.xenproject.org/archives/html/wg-test-framework/2014-02/msg00004.html
> > However, I think Mirage would need to engage with Ian as community rep and Mirage support woul dbe under long term goals I would assume
> > Lars
> > 
> > On 17/02/2014 18:05, Amir Chaudhry wrote:
> >> Hi Lars,
> >> 
> >> I'm curious about where things stand with the testing for the Xen project.  I've gone through the wg-test-framework archives and tried to catchup with minutes. I'm wondering when the next set will be posted (from the meeting on the 13th).
> >> 
> >> Having a testing setup for Xen would be really useful for Mirage.  Since we're having more people try out our tutorials and knowing the state of things in different environments would help us catch issues quicker.
> >> 
> >> Thanks,
> >> Amir
> >> 
> >> 
> > 
> > 
> > _______________________________________________
> > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenproject.org
> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> > 
> 



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 12:25:28 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 12:25: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 1WFjjr-0004Zn-NA; Tue, 18 Feb 2014 12:25:27 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFjjq-0004Zi-C9
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 12:25:26 +0000
Received: from [85.158.139.211:10229] by server-7.bemta-5.messagelabs.com id
	1F/45-14867-53153035; Tue, 18 Feb 2014 12:25:25 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-13.tower-206.messagelabs.com!1392726323!4655796!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1899 invoked from network); 18 Feb 2014 12:25:24 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 12:25:24 -0000
X-IronPort-AV: E=Sophos;i="4.97,501,1389744000"; d="scan'208";a="103446684"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 18 Feb 2014 12:25:22 +0000
Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL02.citrite.net
	(10.13.107.79) with Microsoft SMTP Server id 14.2.342.4;
	Tue, 18 Feb 2014 07:25:21 -0500
Message-ID: <1392726320.11080.53.camel@kazak.uk.xensource.com>
From: Ian Campbell 
To: Anil Madhavapeddy 
Date: Tue, 18 Feb 2014 12:25:20 +0000
In-Reply-To: <93000E7C-4FA9-4AE6-8462-2899921A9191@recoil.org>
References: <5294A073.9000209@xen.org>
	<1386595227.30459.21.camel@kazak.uk.xensource.com>
	<52A75DA6.4020201@xen.org>
	<1386756731.30271.22.camel@kazak.uk.xensource.com>
	<637BBCE1-3781-467A-B1B9-830250CA16F3@cam.ac.uk>
	<53034DA9.3050807@xen.org>
	<93000E7C-4FA9-4AE6-8462-2899921A9191@recoil.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA1
Cc: Ian Jackson ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Testing for the Xen Project
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On Tue, 2014-02-18 at 12:18 +0000, Anil Madhavapeddy wrote:
> [+CC Ian Campbell]

Ian Jackson is the communioty WG member. Adding another CC ;-)

> 
> Our specific need is actually pretty short term -- we can easily build a number of 'unit test' kernels that do simple activities such as boot, write to xenstore, attach a net/block front, and verify basic health conditions (such as whether the backend moves to the connected state).
> 
> Distro support for a lot of this seems to be in a variable state across the board.  For instance, we'd like to have a known-good configuration for Debian, Ubuntu, Fedora and CentOS in terms of which toolchain to use (xl, xm, libvirt in particular) and what configurations to recommend to users installing Xen.  Debian stable is still on XM for instance, with an unclear story on libvirt support, whereas Ubuntu appears to have problems with xl and starting up blktap.
> 
> More structured unit tests that run on all these platforms would be extremely useful to highlight issues early, and Mirage provides an easy way to build these tests (see https://github.com/mirage/mirage-skeleton for a growing number).
> 
> We don't really have the resources to maintain the sysadmin infrastructure for these tests, but can certainly help with triaging failures.  The biggest blocker for new users of Mirage that I've talked to (often unfamiliar with both OCaml and Xen) has usually been getting to a working Xen installation, so I'd like to have a few recommended setups as soon as possible. 
> 
> cheers,
> Anil
> 
> On 18 Feb 2014, at 12:10, Lars Kurth  wrote:
> 
> > Minutes are up : http://lists.xenproject.org/archives/html/wg-test-framework/2014-02/msg00004.html
> > However, I think Mirage would need to engage with Ian as community rep and Mirage support woul dbe under long term goals I would assume
> > Lars
> > 
> > On 17/02/2014 18:05, Amir Chaudhry wrote:
> >> Hi Lars,
> >> 
> >> I'm curious about where things stand with the testing for the Xen project.  I've gone through the wg-test-framework archives and tried to catchup with minutes. I'm wondering when the next set will be posted (from the meeting on the 13th).
> >> 
> >> Having a testing setup for Xen would be really useful for Mirage.  Since we're having more people try out our tutorials and knowing the state of things in different environments would help us catch issues quicker.
> >> 
> >> Thanks,
> >> Amir
> >> 
> >> 
> > 
> > 
> > _______________________________________________
> > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenproject.org
> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> > 
> 



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 13:30:42 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 13:30: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 1WFkkw-0007Xy-JE; Tue, 18 Feb 2014 13:30:38 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFkkv-0007Xt-6u
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 13:30:37 +0000
Received: from [85.158.137.68:34389] by server-2.bemta-3.messagelabs.com id
	CD/64-06531-C7063035; Tue, 18 Feb 2014 13:30:36 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-4.tower-31.messagelabs.com!1392730234!1374059!1
X-Originating-IP: [209.85.220.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27634 invoked from network); 18 Feb 2014 13:30:35 -0000
Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com)
	(209.85.220.173)
	by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 13:30:35 -0000
Received: by mail-vc0-f173.google.com with SMTP id ld13so12973643vcb.18
	for ;
	Tue, 18 Feb 2014 05:30:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=HnYCcMSXEBuf3W4l+gTTE33HbdWhZhDzrz3d+xHsUaQ=;
	b=I43axmEFTfuX4C+SPo5PFBX9fYPtGsMDDnWzhAtuOw5wbBGhEWCwtCPdGWTHgJkur/
	zVYnWnq67fEB4ZZkSG2Ked3DmwCF1QeBRRmVoXV8zt6u2IT7r2V8HihZlLUWGsYU20VQ
	IFJX60PQnlVJEKABQsyewJUXzu6yPjk4+wOMj37zJsSnAQlmX12js9dRXwU8OuT8NM7b
	SM7C/ihn1vFGvzIZbSofOA4J3HJjbe/ufR0gZJ08pVGqHJRIeChqFkz9ewvGrFAFMIWB
	AH0NNWlc6orUmlYtowDMlxR2hcVbKf09Ll3rpnGdX5jXJ6JVX3eSQwmFT6BJljd8iRLd
	JAdQ==
MIME-Version: 1.0
X-Received: by 10.52.101.135 with SMTP id fg7mr5232695vdb.17.1392730233256;
	Tue, 18 Feb 2014 05:30:33 -0800 (PST)
Received: by 10.52.109.2 with HTTP; Tue, 18 Feb 2014 05:30:33 -0800 (PST)
Date: Tue, 18 Feb 2014 13:30:33 +0000
Message-ID: 
From: David Scott 
To: "mirageos-devel@lists.xenproject.org" 
Subject: [MirageOS-devel] mirage weekly call today (tue) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6600205514602735785=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============6600205514602735785==
Content-Type: multipart/alternative; boundary=bcaec5469505d23df004f2ae4637

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

The agenda is:
* homepage progress (all)
* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)
* status of SSL bindings (anil)
* AOB

Feel free to send other agenda items to me before the meeting. Amir has
kindly offered to take minutes, provided the agenda is clearly stated
before the meeting.

1.  Please join my meeting.
https://www1.gotomeeting.com/join/591890401

2.  Use your microphone and speakers (VoIP) - a headset is recommended.
 Or, call in using your telephone.

United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151
1817

United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017

Access Code: 591-890-401
Audio PIN: Shown after joining the meeting

Meeting ID: 591-890-401

-- 
Dave Scott

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


The agenda is:
* homepage progress (all)

* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)

* status of SSL bindings (anil)
* AOB


Feel free to send other agenda items to me before the meeting. Amir has kin=
dly offered to take minutes, provided the agenda is clearly stated before t=
he meeting.


1. =A0=
Please join my meeting.



2. =A0Use your microph=
one and speakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0i=
n using your telephone.



United Kingdom (toll-f=
ree): 0 808 168 0209 United Kingdom:=A0+44 (0) 207 151 18=
17



United States (toll-fr=
ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00=
17



Access Code: 591-890-4=
01
Audio PI=
N: Shown after joining the meeting



Meeting ID: 591-890-40=
1

-- 
Dave Scott



--bcaec5469505d23df004f2ae4637--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============6600205514602735785==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 13:30:42 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 13:30: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 1WFkkw-0007Xy-JE; Tue, 18 Feb 2014 13:30:38 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFkkv-0007Xt-6u
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 13:30:37 +0000
Received: from [85.158.137.68:34389] by server-2.bemta-3.messagelabs.com id
	CD/64-06531-C7063035; Tue, 18 Feb 2014 13:30:36 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-4.tower-31.messagelabs.com!1392730234!1374059!1
X-Originating-IP: [209.85.220.173]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27634 invoked from network); 18 Feb 2014 13:30:35 -0000
Received: from mail-vc0-f173.google.com (HELO mail-vc0-f173.google.com)
	(209.85.220.173)
	by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 13:30:35 -0000
Received: by mail-vc0-f173.google.com with SMTP id ld13so12973643vcb.18
	for ;
	Tue, 18 Feb 2014 05:30:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=HnYCcMSXEBuf3W4l+gTTE33HbdWhZhDzrz3d+xHsUaQ=;
	b=I43axmEFTfuX4C+SPo5PFBX9fYPtGsMDDnWzhAtuOw5wbBGhEWCwtCPdGWTHgJkur/
	zVYnWnq67fEB4ZZkSG2Ked3DmwCF1QeBRRmVoXV8zt6u2IT7r2V8HihZlLUWGsYU20VQ
	IFJX60PQnlVJEKABQsyewJUXzu6yPjk4+wOMj37zJsSnAQlmX12js9dRXwU8OuT8NM7b
	SM7C/ihn1vFGvzIZbSofOA4J3HJjbe/ufR0gZJ08pVGqHJRIeChqFkz9ewvGrFAFMIWB
	AH0NNWlc6orUmlYtowDMlxR2hcVbKf09Ll3rpnGdX5jXJ6JVX3eSQwmFT6BJljd8iRLd
	JAdQ==
MIME-Version: 1.0
X-Received: by 10.52.101.135 with SMTP id fg7mr5232695vdb.17.1392730233256;
	Tue, 18 Feb 2014 05:30:33 -0800 (PST)
Received: by 10.52.109.2 with HTTP; Tue, 18 Feb 2014 05:30:33 -0800 (PST)
Date: Tue, 18 Feb 2014 13:30:33 +0000
Message-ID: 
From: David Scott 
To: "mirageos-devel@lists.xenproject.org" 
Subject: [MirageOS-devel] mirage weekly call today (tue) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6600205514602735785=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============6600205514602735785==
Content-Type: multipart/alternative; boundary=bcaec5469505d23df004f2ae4637

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

The agenda is:
* homepage progress (all)
* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)
* status of SSL bindings (anil)
* AOB

Feel free to send other agenda items to me before the meeting. Amir has
kindly offered to take minutes, provided the agenda is clearly stated
before the meeting.

1.  Please join my meeting.
https://www1.gotomeeting.com/join/591890401

2.  Use your microphone and speakers (VoIP) - a headset is recommended.
 Or, call in using your telephone.

United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151
1817

United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017

Access Code: 591-890-401
Audio PIN: Shown after joining the meeting

Meeting ID: 591-890-401

-- 
Dave Scott

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


The agenda is:
* homepage progress (all)

* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)

* status of SSL bindings (anil)
* AOB


Feel free to send other agenda items to me before the meeting. Amir has kin=
dly offered to take minutes, provided the agenda is clearly stated before t=
he meeting.


1. =A0=
Please join my meeting.



2. =A0Use your microph=
one and speakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0i=
n using your telephone.



United Kingdom (toll-f=
ree): 0 808 168 0209 United Kingdom:=A0+44 (0) 207 151 18=
17



United States (toll-fr=
ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00=
17



Access Code: 591-890-4=
01
Audio PI=
N: Shown after joining the meeting



Meeting ID: 591-890-40=
1

-- 
Dave Scott



--bcaec5469505d23df004f2ae4637--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============6600205514602735785==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 13:44:32 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 13:44: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 1WFkyM-0007t7-Sl; Tue, 18 Feb 2014 13:44:30 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFkyK-0007t2-OB
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 13:44:29 +0000
Received: from [193.109.254.147:18573] by server-16.bemta-14.messagelabs.com
	id 63/BF-21945-CB363035; Tue, 18 Feb 2014 13:44:28 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-9.tower-27.messagelabs.com!1392731066!1152243!1
X-Originating-IP: [131.111.8.132]
X-SpamReason: No, hits=0.5 required=7.0 tests=HTML_60_70,HTML_MESSAGE,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5675 invoked from network); 18 Feb 2014 13:44:26 -0000
Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk)
	(131.111.8.132)
	by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 18 Feb 2014 13:44:26 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from [217.144.151.62] (port=64934 helo=[172.17.16.166])
	by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WFkxL-0006l8-1X (Exim 4.82_3-c0e5623)
	(return-path ); Tue, 18 Feb 2014 13:43:27 +0000
References: 
Mime-Version: 1.0 (1.0)
In-Reply-To: 
Message-Id: 
X-Mailer: iPhone Mail (11B554a)
From: Amir Chaudhry 
Date: Tue, 18 Feb 2014 13:43:27 +0000
To: David Scott 
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage weekly call today (tue) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5767641530058786823=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============5767641530058786823==
Content-Type: multipart/alternative;
	boundary=Apple-Mail-D3D12796-5C06-4431-BCE2-FB39EF26338A
Content-Transfer-Encoding: 7bit


--Apple-Mail-D3D12796-5C06-4431-BCE2-FB39EF26338A
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

(Inline)

Best wishes,
Amir

--
sent via mobile

> On 18 Feb 2014, at 13:30, David Scott  wrote:
>=20
> The agenda is:
> * homepage progress (all)
> * irminsule storage (thomas)
> * tcp stack (anil)
> * vchan (anil)
> * status of SSL bindings (anil)
> * AOB

Love that we have an agenda! Thank you!

>=20
> Feel free to send other agenda items to me before the meeting. Amir has ki=
ndly offered to take minutes, provided the agenda is clearly stated before t=
he meeting.

Yes, I did & would be happy to but unfortunately I'm gonna be on a train whe=
n the call happens today. Will def do this from next week.=20

AC

>=20
> 1.  Please join my meeting.
> https://www1.gotomeeting.com/join/591890401
>=20
> 2.  Use your microphone and speakers (VoIP) - a headset is recommended.  O=
r, call in using your telephone.
>=20
> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151=
 1817
>=20
> United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017=

>=20
> Access Code: 591-890-401
> Audio PIN: Shown after joining the meeting
>=20
> Meeting ID: 591-890-401
>=20
> --=20
> Dave Scott
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--Apple-Mail-D3D12796-5C06-4431-BCE2-FB39EF26338A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit


(Inline)

Best wishes,
Amir

--
sent via mobile

On 18 Feb 2014, at 13:30, David Scott <scott.dj@gmail.com> wrote:

The agenda is:
* homepage progress (all)

* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)

* status of SSL bindings (anil)
* AOB

Love that we have an agenda! Thank you!



Feel free to send other agenda items to me before the meeting. Amir has kindly offered to take minutes, provided the agenda is clearly stated before the meeting.

Yes, I did & would be happy to but unfortunately I'm gonna be on a train when the call happens today. Will def do this from next week. 

AC



1.  Please join my meeting.



2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, call in using your telephone.



United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817



United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017



Access Code: 591-890-401
Audio PIN: Shown after joining the meeting



Meeting ID: 591-890-401

-- 
Dave Scott



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--Apple-Mail-D3D12796-5C06-4431-BCE2-FB39EF26338A--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============5767641530058786823==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 13:44:32 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 13:44: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 1WFkyM-0007t7-Sl; Tue, 18 Feb 2014 13:44:30 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFkyK-0007t2-OB
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 13:44:29 +0000
Received: from [193.109.254.147:18573] by server-16.bemta-14.messagelabs.com
	id 63/BF-21945-CB363035; Tue, 18 Feb 2014 13:44:28 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-9.tower-27.messagelabs.com!1392731066!1152243!1
X-Originating-IP: [131.111.8.132]
X-SpamReason: No, hits=0.5 required=7.0 tests=HTML_60_70,HTML_MESSAGE,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5675 invoked from network); 18 Feb 2014 13:44:26 -0000
Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk)
	(131.111.8.132)
	by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 18 Feb 2014 13:44:26 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from [217.144.151.62] (port=64934 helo=[172.17.16.166])
	by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WFkxL-0006l8-1X (Exim 4.82_3-c0e5623)
	(return-path ); Tue, 18 Feb 2014 13:43:27 +0000
References: 
Mime-Version: 1.0 (1.0)
In-Reply-To: 
Message-Id: 
X-Mailer: iPhone Mail (11B554a)
From: Amir Chaudhry 
Date: Tue, 18 Feb 2014 13:43:27 +0000
To: David Scott 
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage weekly call today (tue) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5767641530058786823=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============5767641530058786823==
Content-Type: multipart/alternative;
	boundary=Apple-Mail-D3D12796-5C06-4431-BCE2-FB39EF26338A
Content-Transfer-Encoding: 7bit


--Apple-Mail-D3D12796-5C06-4431-BCE2-FB39EF26338A
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

(Inline)

Best wishes,
Amir

--
sent via mobile

> On 18 Feb 2014, at 13:30, David Scott  wrote:
>=20
> The agenda is:
> * homepage progress (all)
> * irminsule storage (thomas)
> * tcp stack (anil)
> * vchan (anil)
> * status of SSL bindings (anil)
> * AOB

Love that we have an agenda! Thank you!

>=20
> Feel free to send other agenda items to me before the meeting. Amir has ki=
ndly offered to take minutes, provided the agenda is clearly stated before t=
he meeting.

Yes, I did & would be happy to but unfortunately I'm gonna be on a train whe=
n the call happens today. Will def do this from next week.=20

AC

>=20
> 1.  Please join my meeting.
> https://www1.gotomeeting.com/join/591890401
>=20
> 2.  Use your microphone and speakers (VoIP) - a headset is recommended.  O=
r, call in using your telephone.
>=20
> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151=
 1817
>=20
> United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017=

>=20
> Access Code: 591-890-401
> Audio PIN: Shown after joining the meeting
>=20
> Meeting ID: 591-890-401
>=20
> --=20
> Dave Scott
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--Apple-Mail-D3D12796-5C06-4431-BCE2-FB39EF26338A
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit


(Inline)

Best wishes,
Amir

--
sent via mobile

On 18 Feb 2014, at 13:30, David Scott <scott.dj@gmail.com> wrote:

The agenda is:
* homepage progress (all)

* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)

* status of SSL bindings (anil)
* AOB

Love that we have an agenda! Thank you!



Feel free to send other agenda items to me before the meeting. Amir has kindly offered to take minutes, provided the agenda is clearly stated before the meeting.

Yes, I did & would be happy to but unfortunately I'm gonna be on a train when the call happens today. Will def do this from next week. 

AC



1.  Please join my meeting.



2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, call in using your telephone.



United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817



United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017



Access Code: 591-890-401
Audio PIN: Shown after joining the meeting



Meeting ID: 591-890-401

-- 
Dave Scott



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--Apple-Mail-D3D12796-5C06-4431-BCE2-FB39EF26338A--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============5767641530058786823==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 14:35:20 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 14:35:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFllW-0000nr-Gy; Tue, 18 Feb 2014 14:35:18 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFllU-0000nm-B5
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 14:35:16 +0000
Received: from [193.109.254.147:60348] by server-12.bemta-14.messagelabs.com
	id EF/3D-17220-3AF63035; Tue, 18 Feb 2014 14:35:15 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-10.tower-27.messagelabs.com!1392734115!5188140!1
X-Originating-IP: [195.62.217.152]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTIgPT4gMTY3OTY=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28372 invoked from network); 18 Feb 2014 14:35:15 -0000
Received: from engine04-20433-4.icritical.com (HELO
	engine04-20433-4.icritical.com) (195.62.217.152)
	by server-10.tower-27.messagelabs.com with SMTP;
	18 Feb 2014 14:35:15 -0000
Received: (qmail 7460 invoked from network); 18 Feb 2014 14:35:14 -0000
Received: from localhost (127.0.0.1)
	by engine04-20433-4.icritical.com with SMTP; 18 Feb 2014 14:35:14 -0000
Received: from engine04-20433-4.icritical.com ([127.0.0.1])
	by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 07345-06 for ;
	Tue, 18 Feb 2014 14:35:14 +0000 (GMT)
Received: (qmail 6234 invoked by uid 599); 18 Feb 2014 14:33:50 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP;
	Tue, 18 Feb 2014 14:33:50 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WFlk0-0004P5-4Q; Tue, 18 Feb 2014 14:33:44 +0000
From: Richard Mortier 
To: David Scott 
Date: Tue, 18 Feb 2014 14:33:20 +0000
Thread-Topic: [MirageOS-devel] multiple block devices under xen
Thread-Index: Ac8stmzawwwrRIwRSLm7/TMvs0f9Ww==
Message-ID: <42A50E2A-D290-4501-897C-AFEFB50B4C30@nottingham.ac.uk>
References: 
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] multiple block devices under xen
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

thanks dave!  a couple of questions inline as i start to try this out...

On 18 Feb 2014, at 12:05, David Scott  wrote:

> Background
> ----------
> 
> When a disk is added to a VM (under Xen, KVM, any hypervisor) it's like plugging in a PCI device into a physical box -- a disk will appear in some kind of numbered "slot" on a "bus". In xen the "slot" number is the name of the directory in xenstore (/local/domain//device/vbd/) 

just because i'm still a bit fuzzy on this -- what about when i'm not running xenstore?  (or am i always running xenstore, i just haven't realised yet?)

> From the Linux perspective, the *convention* is that the "slot" number is the device node (major-number << 8 || minor-number):

...and from below (and a bit of googling), /dev/xvdN has major number 202 and minor number (N-'a')*16, right?  is that (the major/minor numbering of xvd devices) also convention or standard?

> Xen disk support
> ----------------
> 
> ...and then create a loop device like so:
> 
> sudo losetup /dev/loop0 disk.raw
> 
> (where /dev/loop0 is any free loop device. Note the total number of loop devices is determined at module load time, it's not dynamic unfortunately (last time I checked anyway))

is there an easy way to find out what this is?  (whether from CLI or programmatically.)

> Whatever you do, don't mix I/O to the /dev/loop device with I/O to the file -- it won't be coherent. 

presumably this is unlikely to happen by accident in a mirage vm?

[snip details]

ok, so in summary the current recommendation is to:

+ create a FAT file image (done by mirage) and mount it as a loopback device 
	$ sudo losetup /dev/loopN fat.img

+ write a Xen config file that hotplugs loopback devices as physical block devices
	disk = [ '/dev/loop0,,xvda', ... ]

+ write a mirage config file that uses the block device node number as a name
	let block = { Block.name = "51712"; filename = "fat.img"; read_only = false; }

...and then hopefully everything will line up, with the Block.filename value used when running the mirage unikernel as a UNIX process, and the Block.name value being interpreted as the appropriate device node when running as a Xen VM (assuming the Xen config file has indicated to plug the loopback device as the xvdN device correctly)?

> This is obviously not ideal. Perhaps in future we can:
> * make "mirage" generate an .xl config file which references the file (rather than a block device) and rely on the hotplug scripts to manage the loop device. This should work, but since there are more moving parts, may be flaky on your particular distro.
> * make "Block.connect" take some kind of volume label rather than a device id, so mirage-block-{unix,xen} can cope with disks being presented in any order on the bus

both would be nice i think -- but hopefully the info above (assuming i have it straight now) will be enough to get going! :)


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 14:35:20 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 14:35:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFllW-0000nr-Gy; Tue, 18 Feb 2014 14:35:18 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFllU-0000nm-B5
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 14:35:16 +0000
Received: from [193.109.254.147:60348] by server-12.bemta-14.messagelabs.com
	id EF/3D-17220-3AF63035; Tue, 18 Feb 2014 14:35:15 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-10.tower-27.messagelabs.com!1392734115!5188140!1
X-Originating-IP: [195.62.217.152]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTIgPT4gMTY3OTY=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28372 invoked from network); 18 Feb 2014 14:35:15 -0000
Received: from engine04-20433-4.icritical.com (HELO
	engine04-20433-4.icritical.com) (195.62.217.152)
	by server-10.tower-27.messagelabs.com with SMTP;
	18 Feb 2014 14:35:15 -0000
Received: (qmail 7460 invoked from network); 18 Feb 2014 14:35:14 -0000
Received: from localhost (127.0.0.1)
	by engine04-20433-4.icritical.com with SMTP; 18 Feb 2014 14:35:14 -0000
Received: from engine04-20433-4.icritical.com ([127.0.0.1])
	by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 07345-06 for ;
	Tue, 18 Feb 2014 14:35:14 +0000 (GMT)
Received: (qmail 6234 invoked by uid 599); 18 Feb 2014 14:33:50 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP;
	Tue, 18 Feb 2014 14:33:50 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WFlk0-0004P5-4Q; Tue, 18 Feb 2014 14:33:44 +0000
From: Richard Mortier 
To: David Scott 
Date: Tue, 18 Feb 2014 14:33:20 +0000
Thread-Topic: [MirageOS-devel] multiple block devices under xen
Thread-Index: Ac8stmzawwwrRIwRSLm7/TMvs0f9Ww==
Message-ID: <42A50E2A-D290-4501-897C-AFEFB50B4C30@nottingham.ac.uk>
References: 
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] multiple block devices under xen
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

thanks dave!  a couple of questions inline as i start to try this out...

On 18 Feb 2014, at 12:05, David Scott  wrote:

> Background
> ----------
> 
> When a disk is added to a VM (under Xen, KVM, any hypervisor) it's like plugging in a PCI device into a physical box -- a disk will appear in some kind of numbered "slot" on a "bus". In xen the "slot" number is the name of the directory in xenstore (/local/domain//device/vbd/) 

just because i'm still a bit fuzzy on this -- what about when i'm not running xenstore?  (or am i always running xenstore, i just haven't realised yet?)

> From the Linux perspective, the *convention* is that the "slot" number is the device node (major-number << 8 || minor-number):

...and from below (and a bit of googling), /dev/xvdN has major number 202 and minor number (N-'a')*16, right?  is that (the major/minor numbering of xvd devices) also convention or standard?

> Xen disk support
> ----------------
> 
> ...and then create a loop device like so:
> 
> sudo losetup /dev/loop0 disk.raw
> 
> (where /dev/loop0 is any free loop device. Note the total number of loop devices is determined at module load time, it's not dynamic unfortunately (last time I checked anyway))

is there an easy way to find out what this is?  (whether from CLI or programmatically.)

> Whatever you do, don't mix I/O to the /dev/loop device with I/O to the file -- it won't be coherent. 

presumably this is unlikely to happen by accident in a mirage vm?

[snip details]

ok, so in summary the current recommendation is to:

+ create a FAT file image (done by mirage) and mount it as a loopback device 
	$ sudo losetup /dev/loopN fat.img

+ write a Xen config file that hotplugs loopback devices as physical block devices
	disk = [ '/dev/loop0,,xvda', ... ]

+ write a mirage config file that uses the block device node number as a name
	let block = { Block.name = "51712"; filename = "fat.img"; read_only = false; }

...and then hopefully everything will line up, with the Block.filename value used when running the mirage unikernel as a UNIX process, and the Block.name value being interpreted as the appropriate device node when running as a Xen VM (assuming the Xen config file has indicated to plug the loopback device as the xvdN device correctly)?

> This is obviously not ideal. Perhaps in future we can:
> * make "mirage" generate an .xl config file which references the file (rather than a block device) and rely on the hotplug scripts to manage the loop device. This should work, but since there are more moving parts, may be flaky on your particular distro.
> * make "Block.connect" take some kind of volume label rather than a device id, so mirage-block-{unix,xen} can cope with disks being presented in any order on the bus

both would be nice i think -- but hopefully the info above (assuming i have it straight now) will be enough to get going! :)


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 16:14:00 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 16:14: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 1WFnIw-00058s-7z; Tue, 18 Feb 2014 16:13:54 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFnIt-00058n-HZ
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 16:13:51 +0000
Received: from [85.158.139.211:24334] by server-14.bemta-5.messagelabs.com id
	22/1D-27598-EB683035; Tue, 18 Feb 2014 16:13:50 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-4.tower-206.messagelabs.com!1392740029!4719738!1
X-Originating-IP: [74.125.82.175]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4662 invoked from network); 18 Feb 2014 16:13:49 -0000
Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com)
	(74.125.82.175)
	by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 16:13:49 -0000
Received: by mail-we0-f175.google.com with SMTP id q59so11951889wes.34
	for ;
	Tue, 18 Feb 2014 08:13:49 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:mime-version:content-type:from
	:in-reply-to:date:cc:message-id:references:to;
	bh=XxCU97IF5q66wVNpl02PjDMwBIPLUWL2+S3P+Gbzrcg=;
	b=NCsV9aZMSUh0EEG9Xb/KC1Rpo5JkAOMNiAfpqWn7Rff0Vgv55IspgtEPgg0tCIUdDK
	E5gnRO5GFcu7X3dp942SE8pRqvh/u60KIBQoDo1DxJpR96osNd2JMKPRMAO5lJ9l5ue9
	U2eDzX6FVYVG8aFdi0HW10UEJ5pqqETSIATd+cfhPvh9spLdHlf3hpD0fecFDw4l7C+t
	dTteJy0YjDaZrvuN0zbN6DZAvo8kxhHSmzVoyIftzNEyBd0pzUyKW7ekkRPbGg0DoAoJ
	Tvt+pXTe5KySmmu3vHiEmau9MzhbqpVYZoM7SSr0/rTKK4epv8vN1i89LrW/uESsw7jy
	Bc+w==
X-Gm-Message-State: ALoCoQmep7CK3K59c2QZ0ggTthvrBP0fgwnkUbGmN0Ej8PWdH1lSIzwTdvcWizDMaJvGuf/UTA7F
X-Received: by 10.180.12.115 with SMTP id x19mr18892968wib.19.1392740029097;
	Tue, 18 Feb 2014 08:13:49 -0800 (PST)
Received: from [192.168.1.15] (212.44.45.208.ip.redstone-isp.net.
	[212.44.45.208])
	by mx.google.com with ESMTPSA id fb6sm43362030wib.2.2014.02.18.08.13.45
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 18 Feb 2014 08:13:46 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
From: Julian Chesterfield 
In-Reply-To: 
Date: Tue, 18 Feb 2014 16:13:45 +0000
Message-Id: <07F4E5E3-0B70-4159-8070-FAAF12A72B45@onapp.com>
References: 
	
To: Amir Chaudhry 
X-Mailer: Apple Mail (2.1283)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage weekly call today (tue) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2648954004589644483=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============2648954004589644483==
Content-Type: multipart/alternative; boundary="Apple-Mail=_701E3076-F102-4AA5-9338-570BCB750D23"


--Apple-Mail=_701E3076-F102-4AA5-9338-570BCB750D23
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Did the call already finish? Not seeing anyone on the bridge.

- J

On 18 Feb 2014, at 13:43, Amir Chaudhry wrote:

> (Inline)
>=20
> Best wishes,
> Amir
>=20
> --
> sent via mobile
>=20
> On 18 Feb 2014, at 13:30, David Scott  wrote:
>=20
>> The agenda is:
>> * homepage progress (all)
>> * irminsule storage (thomas)
>> * tcp stack (anil)
>> * vchan (anil)
>> * status of SSL bindings (anil)
>> * AOB
>=20
> Love that we have an agenda! Thank you!
>=20
>>=20
>> Feel free to send other agenda items to me before the meeting. Amir =
has kindly offered to take minutes, provided the agenda is clearly =
stated before the meeting.
>=20
> Yes, I did & would be happy to but unfortunately I'm gonna be on a =
train when the call happens today. Will def do this from next week.=20
>=20
> AC
>=20
>>=20
>> 1.  Please join my meeting.
>> https://www1.gotomeeting.com/join/591890401
>>=20
>> 2.  Use your microphone and speakers (VoIP) - a headset is =
recommended.  Or, call in using your telephone.
>>=20
>> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) =
207 151 1817
>>=20
>> United States (toll-free): 1 877 309 2070 United States: +1 (626) =
521-0017
>>=20
>> Access Code: 591-890-401
>> Audio PIN: Shown after joining the meeting
>>=20
>> Meeting ID: 591-890-401
>>=20
>> --=20
>> Dave Scott
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_701E3076-F102-4AA5-9338-570BCB750D23
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii


Did the call already finish? Not seeing anyone on the bridge.

- J

On 18 Feb 2014, at 13:43, Amir Chaudhry wrote:

(Inline)

Best wishes,
Amir

--
sent via mobile

On 18 Feb 2014, at 13:30, David Scott <scott.dj@gmail.com> wrote:

The agenda is:
* homepage progress (all)

* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)

* status of SSL bindings (anil)
* AOB

Love that we have an agenda! Thank you!



Feel free to send other agenda items to me before the meeting. Amir has kindly offered to take minutes, provided the agenda is clearly stated before the meeting.

Yes, I did & would be happy to but unfortunately I'm gonna be on a train when the call happens today. Will def do this from next week. 

AC



1.  Please join my meeting.



2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, call in using your telephone.



United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817



United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017



Access Code: 591-890-401
Audio PIN: Shown after joining the meeting



Meeting ID: 591-890-401

-- 
Dave Scott



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_701E3076-F102-4AA5-9338-570BCB750D23--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============2648954004589644483==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 16:14:00 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 16:14: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 1WFnIw-00058s-7z; Tue, 18 Feb 2014 16:13:54 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFnIt-00058n-HZ
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 16:13:51 +0000
Received: from [85.158.139.211:24334] by server-14.bemta-5.messagelabs.com id
	22/1D-27598-EB683035; Tue, 18 Feb 2014 16:13:50 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-4.tower-206.messagelabs.com!1392740029!4719738!1
X-Originating-IP: [74.125.82.175]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4662 invoked from network); 18 Feb 2014 16:13:49 -0000
Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com)
	(74.125.82.175)
	by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 16:13:49 -0000
Received: by mail-we0-f175.google.com with SMTP id q59so11951889wes.34
	for ;
	Tue, 18 Feb 2014 08:13:49 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:mime-version:content-type:from
	:in-reply-to:date:cc:message-id:references:to;
	bh=XxCU97IF5q66wVNpl02PjDMwBIPLUWL2+S3P+Gbzrcg=;
	b=NCsV9aZMSUh0EEG9Xb/KC1Rpo5JkAOMNiAfpqWn7Rff0Vgv55IspgtEPgg0tCIUdDK
	E5gnRO5GFcu7X3dp942SE8pRqvh/u60KIBQoDo1DxJpR96osNd2JMKPRMAO5lJ9l5ue9
	U2eDzX6FVYVG8aFdi0HW10UEJ5pqqETSIATd+cfhPvh9spLdHlf3hpD0fecFDw4l7C+t
	dTteJy0YjDaZrvuN0zbN6DZAvo8kxhHSmzVoyIftzNEyBd0pzUyKW7ekkRPbGg0DoAoJ
	Tvt+pXTe5KySmmu3vHiEmau9MzhbqpVYZoM7SSr0/rTKK4epv8vN1i89LrW/uESsw7jy
	Bc+w==
X-Gm-Message-State: ALoCoQmep7CK3K59c2QZ0ggTthvrBP0fgwnkUbGmN0Ej8PWdH1lSIzwTdvcWizDMaJvGuf/UTA7F
X-Received: by 10.180.12.115 with SMTP id x19mr18892968wib.19.1392740029097;
	Tue, 18 Feb 2014 08:13:49 -0800 (PST)
Received: from [192.168.1.15] (212.44.45.208.ip.redstone-isp.net.
	[212.44.45.208])
	by mx.google.com with ESMTPSA id fb6sm43362030wib.2.2014.02.18.08.13.45
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 18 Feb 2014 08:13:46 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
From: Julian Chesterfield 
In-Reply-To: 
Date: Tue, 18 Feb 2014 16:13:45 +0000
Message-Id: <07F4E5E3-0B70-4159-8070-FAAF12A72B45@onapp.com>
References: 
	
To: Amir Chaudhry 
X-Mailer: Apple Mail (2.1283)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage weekly call today (tue) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2648954004589644483=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============2648954004589644483==
Content-Type: multipart/alternative; boundary="Apple-Mail=_701E3076-F102-4AA5-9338-570BCB750D23"


--Apple-Mail=_701E3076-F102-4AA5-9338-570BCB750D23
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Did the call already finish? Not seeing anyone on the bridge.

- J

On 18 Feb 2014, at 13:43, Amir Chaudhry wrote:

> (Inline)
>=20
> Best wishes,
> Amir
>=20
> --
> sent via mobile
>=20
> On 18 Feb 2014, at 13:30, David Scott  wrote:
>=20
>> The agenda is:
>> * homepage progress (all)
>> * irminsule storage (thomas)
>> * tcp stack (anil)
>> * vchan (anil)
>> * status of SSL bindings (anil)
>> * AOB
>=20
> Love that we have an agenda! Thank you!
>=20
>>=20
>> Feel free to send other agenda items to me before the meeting. Amir =
has kindly offered to take minutes, provided the agenda is clearly =
stated before the meeting.
>=20
> Yes, I did & would be happy to but unfortunately I'm gonna be on a =
train when the call happens today. Will def do this from next week.=20
>=20
> AC
>=20
>>=20
>> 1.  Please join my meeting.
>> https://www1.gotomeeting.com/join/591890401
>>=20
>> 2.  Use your microphone and speakers (VoIP) - a headset is =
recommended.  Or, call in using your telephone.
>>=20
>> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) =
207 151 1817
>>=20
>> United States (toll-free): 1 877 309 2070 United States: +1 (626) =
521-0017
>>=20
>> Access Code: 591-890-401
>> Audio PIN: Shown after joining the meeting
>>=20
>> Meeting ID: 591-890-401
>>=20
>> --=20
>> Dave Scott
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_701E3076-F102-4AA5-9338-570BCB750D23
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii


Did the call already finish? Not seeing anyone on the bridge.

- J

On 18 Feb 2014, at 13:43, Amir Chaudhry wrote:

(Inline)

Best wishes,
Amir

--
sent via mobile

On 18 Feb 2014, at 13:30, David Scott <scott.dj@gmail.com> wrote:

The agenda is:
* homepage progress (all)

* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)

* status of SSL bindings (anil)
* AOB

Love that we have an agenda! Thank you!



Feel free to send other agenda items to me before the meeting. Amir has kindly offered to take minutes, provided the agenda is clearly stated before the meeting.

Yes, I did & would be happy to but unfortunately I'm gonna be on a train when the call happens today. Will def do this from next week. 

AC



1.  Please join my meeting.



2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, call in using your telephone.



United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817



United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017



Access Code: 591-890-401
Audio PIN: Shown after joining the meeting



Meeting ID: 591-890-401

-- 
Dave Scott



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_701E3076-F102-4AA5-9338-570BCB750D23--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============2648954004589644483==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 16:19:35 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 16:19: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 1WFnOR-0005OK-9e; Tue, 18 Feb 2014 16:19:35 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFnOP-0005OE-Jl
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 16:19:33 +0000
Received: from [85.158.139.211:41134] by server-13.bemta-5.messagelabs.com id
	31/01-18801-41883035; Tue, 18 Feb 2014 16:19:32 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-2.tower-206.messagelabs.com!1392740369!4676107!1
X-Originating-IP: [209.85.160.51]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16029 invoked from network); 18 Feb 2014 16:19:31 -0000
Received: from mail-pb0-f51.google.com (HELO mail-pb0-f51.google.com)
	(209.85.160.51)
	by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 16:19:31 -0000
Received: by mail-pb0-f51.google.com with SMTP id un15so16999245pbc.10
	for ;
	Tue, 18 Feb 2014 08:19:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=kM00u0jWmck0q+NyOnh0rQkQA73VBe8tt8MvQC3VbhA=;
	b=ZKTBR0zCIlhRyeBsvtzE/8hJZsx8AgTaGV9mMo8kpIl2q0V+yo2gAty0P1eXxm17GE
	oDlCy+4N4DUSof20chqy6uf0IM+dSK5xwJWFPJii92mCCIsErfgVjo8OmFgFQflDgjb7
	Z2MpfA2KGPiRn5u9nDLta2tdyJH2VmSrZRDb+rER3/cDIQb1JSmnIrJZmsc6MPgxW5D9
	FKDbQA+EfxzuJndamGdzg9LKoOWZKe3ikjZ6WjortOJaLffHDAzejfbqDObtWhIzguvB
	YeRyzb5gLmLoRgdHGgwOGxBr/Jrz7ZAw+QxIjqd5FFYPc1veHVb7+9qD5LojwjOQT/tb
	nwQg==
MIME-Version: 1.0
X-Received: by 10.68.255.101 with SMTP id ap5mr33925409pbd.41.1392740369081;
	Tue, 18 Feb 2014 08:19:29 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Tue, 18 Feb 2014 08:19:28 -0800 (PST)
In-Reply-To: <07F4E5E3-0B70-4159-8070-FAAF12A72B45@onapp.com>
References: 
	
	<07F4E5E3-0B70-4159-8070-FAAF12A72B45@onapp.com>
Date: Tue, 18 Feb 2014 16:19:28 +0000
Message-ID: 
From: David Scott 
To: Julian Chesterfield 
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage weekly call today (tue) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0725043752108523381=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============0725043752108523381==
Content-Type: multipart/alternative; boundary=047d7b5da02df6ae0604f2b0a2bc

--047d7b5da02df6ae0604f2b0a2bc
Content-Type: text/plain; charset=ISO-8859-1

A bit of a problem with the bridge -- can you join with VoIP audio?


On Tue, Feb 18, 2014 at 4:13 PM, Julian Chesterfield <
julian.chesterfield@onapp.com> wrote:

> Did the call already finish? Not seeing anyone on the bridge.
>
> - J
>
> On 18 Feb 2014, at 13:43, Amir Chaudhry wrote:
>
> (Inline)
>
> Best wishes,
> Amir
>
> --
> sent via mobile
>
> On 18 Feb 2014, at 13:30, David Scott  wrote:
>
> The agenda is:
> * homepage progress (all)
> * irminsule storage (thomas)
> * tcp stack (anil)
> * vchan (anil)
> * status of SSL bindings (anil)
> * AOB
>
>
> Love that we have an agenda! Thank you!
>
>
> Feel free to send other agenda items to me before the meeting. Amir has
> kindly offered to take minutes, provided the agenda is clearly stated
> before the meeting.
>
>
> Yes, I did & would be happy to but unfortunately I'm gonna be on a train
> when the call happens today. Will def do this from next week.
>
> AC
>
>
> 1.  Please join my meeting.
> https://www1.gotomeeting.com/join/591890401
>
> 2.  Use your microphone and speakers (VoIP) - a headset is recommended.
>  Or, call in using your telephone.
>
> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207
> 151 1817
>
> United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017
>
> Access Code: 591-890-401
> Audio PIN: Shown after joining the meeting
>
> Meeting ID: 591-890-401
>
> --
> Dave Scott
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>
>
>


-- 
Dave Scott

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


A bit of a problem with the bridge -- can you join with Vo=
IP audio?


On Tue, Feb 18, 2014 at 4:13 PM, Julian Chesterfield &l=
t;julian=
.chesterfield@onapp.com> wrote:


Did=
 the call already finish? Not seeing anyone on the bridge.


- J

=
On 18 Feb 2014, at 13:43, Amir Chaudhry wrote:

(Inline)

Best wishes,
Amir


--
sent via mobile

On 18 Feb 2=
014, at 13:30, David Scott <scott.dj@gmail.com> wrote:



The agenda is:
* homepage progress (all)


* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)


* status of SSL bindings (anil)
* AOB

Love that we have an agenda! Thank you!





Feel free to send other agenda items to me before the meeting. Amir has kin=
dly offered to take minutes, provided the agenda is clearly stated before t=
he meeting.

Yes, I did &a=
mp; would be happy to but unfortunately I'm gonna be on a train when th=
e call happens today. Will def do this from next week.=A0



AC



1. =A0=
Please join my meeting.




2. =A0Use your microph=
one and speakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0in using you=
r telephone.




United Kingdom (toll-f=
ree): 0 808 168 0209 United Kingdom:=A0+44 (0) 207 151 18=
17




United States (toll-fr=
ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00=
17




Access Code: 591-890-4=
01
Audio PI=
N: Shown after joining the meeting




Meeting ID: 591-890-40=
1

-- 
Dave Scott



___________________=
____________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org

http://lists.xenproject.org/cgi-bin/mailman/li=
stinfo/mirageos-devel
______________=
_________________________________

MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mi=
rageos-devel






-- 
Dave Scott



--047d7b5da02df6ae0604f2b0a2bc--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============0725043752108523381==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 16:19:35 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 16:19: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 1WFnOR-0005OK-9e; Tue, 18 Feb 2014 16:19:35 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WFnOP-0005OE-Jl
	for mirageos-devel@lists.xenproject.org; Tue, 18 Feb 2014 16:19:33 +0000
Received: from [85.158.139.211:41134] by server-13.bemta-5.messagelabs.com id
	31/01-18801-41883035; Tue, 18 Feb 2014 16:19:32 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-2.tower-206.messagelabs.com!1392740369!4676107!1
X-Originating-IP: [209.85.160.51]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16029 invoked from network); 18 Feb 2014 16:19:31 -0000
Received: from mail-pb0-f51.google.com (HELO mail-pb0-f51.google.com)
	(209.85.160.51)
	by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 16:19:31 -0000
Received: by mail-pb0-f51.google.com with SMTP id un15so16999245pbc.10
	for ;
	Tue, 18 Feb 2014 08:19:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=kM00u0jWmck0q+NyOnh0rQkQA73VBe8tt8MvQC3VbhA=;
	b=ZKTBR0zCIlhRyeBsvtzE/8hJZsx8AgTaGV9mMo8kpIl2q0V+yo2gAty0P1eXxm17GE
	oDlCy+4N4DUSof20chqy6uf0IM+dSK5xwJWFPJii92mCCIsErfgVjo8OmFgFQflDgjb7
	Z2MpfA2KGPiRn5u9nDLta2tdyJH2VmSrZRDb+rER3/cDIQb1JSmnIrJZmsc6MPgxW5D9
	FKDbQA+EfxzuJndamGdzg9LKoOWZKe3ikjZ6WjortOJaLffHDAzejfbqDObtWhIzguvB
	YeRyzb5gLmLoRgdHGgwOGxBr/Jrz7ZAw+QxIjqd5FFYPc1veHVb7+9qD5LojwjOQT/tb
	nwQg==
MIME-Version: 1.0
X-Received: by 10.68.255.101 with SMTP id ap5mr33925409pbd.41.1392740369081;
	Tue, 18 Feb 2014 08:19:29 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Tue, 18 Feb 2014 08:19:28 -0800 (PST)
In-Reply-To: <07F4E5E3-0B70-4159-8070-FAAF12A72B45@onapp.com>
References: 
	
	<07F4E5E3-0B70-4159-8070-FAAF12A72B45@onapp.com>
Date: Tue, 18 Feb 2014 16:19:28 +0000
Message-ID: 
From: David Scott 
To: Julian Chesterfield 
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] mirage weekly call today (tue) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0725043752108523381=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============0725043752108523381==
Content-Type: multipart/alternative; boundary=047d7b5da02df6ae0604f2b0a2bc

--047d7b5da02df6ae0604f2b0a2bc
Content-Type: text/plain; charset=ISO-8859-1

A bit of a problem with the bridge -- can you join with VoIP audio?


On Tue, Feb 18, 2014 at 4:13 PM, Julian Chesterfield <
julian.chesterfield@onapp.com> wrote:

> Did the call already finish? Not seeing anyone on the bridge.
>
> - J
>
> On 18 Feb 2014, at 13:43, Amir Chaudhry wrote:
>
> (Inline)
>
> Best wishes,
> Amir
>
> --
> sent via mobile
>
> On 18 Feb 2014, at 13:30, David Scott  wrote:
>
> The agenda is:
> * homepage progress (all)
> * irminsule storage (thomas)
> * tcp stack (anil)
> * vchan (anil)
> * status of SSL bindings (anil)
> * AOB
>
>
> Love that we have an agenda! Thank you!
>
>
> Feel free to send other agenda items to me before the meeting. Amir has
> kindly offered to take minutes, provided the agenda is clearly stated
> before the meeting.
>
>
> Yes, I did & would be happy to but unfortunately I'm gonna be on a train
> when the call happens today. Will def do this from next week.
>
> AC
>
>
> 1.  Please join my meeting.
> https://www1.gotomeeting.com/join/591890401
>
> 2.  Use your microphone and speakers (VoIP) - a headset is recommended.
>  Or, call in using your telephone.
>
> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207
> 151 1817
>
> United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017
>
> Access Code: 591-890-401
> Audio PIN: Shown after joining the meeting
>
> Meeting ID: 591-890-401
>
> --
> Dave Scott
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>
>
>


-- 
Dave Scott

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


A bit of a problem with the bridge -- can you join with Vo=
IP audio?


On Tue, Feb 18, 2014 at 4:13 PM, Julian Chesterfield &l=
t;julian=
.chesterfield@onapp.com> wrote:


Did=
 the call already finish? Not seeing anyone on the bridge.


- J

=
On 18 Feb 2014, at 13:43, Amir Chaudhry wrote:

(Inline)

Best wishes,
Amir


--
sent via mobile

On 18 Feb 2=
014, at 13:30, David Scott <scott.dj@gmail.com> wrote:



The agenda is:
* homepage progress (all)


* irminsule storage (thomas)
* tcp stack (anil)
* vchan (anil)


* status of SSL bindings (anil)
* AOB

Love that we have an agenda! Thank you!





Feel free to send other agenda items to me before the meeting. Amir has kin=
dly offered to take minutes, provided the agenda is clearly stated before t=
he meeting.

Yes, I did &a=
mp; would be happy to but unfortunately I'm gonna be on a train when th=
e call happens today. Will def do this from next week.=A0



AC



1. =A0=
Please join my meeting.




2. =A0Use your microph=
one and speakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0in using you=
r telephone.




United Kingdom (toll-f=
ree): 0 808 168 0209 United Kingdom:=A0+44 (0) 207 151 18=
17




United States (toll-fr=
ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00=
17




Access Code: 591-890-4=
01
Audio PI=
N: Shown after joining the meeting




Meeting ID: 591-890-40=
1

-- 
Dave Scott



___________________=
____________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org

http://lists.xenproject.org/cgi-bin/mailman/li=
stinfo/mirageos-devel
______________=
_________________________________

MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mi=
rageos-devel






-- 
Dave Scott


--047d7b5da02df6ae0604f2b0a2bc--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============0725043752108523381==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 19:24:17 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 19:24: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 1WFqH7-000409-Vt; Tue, 18 Feb 2014 19:24:13 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFqH7-0003zt-00; Tue, 18 Feb 2014 19:24:13 +0000
Received: from [85.158.139.211:50313] by server-5.bemta-5.messagelabs.com id
	20/B7-32749-B53B3035; Tue, 18 Feb 2014 19:24:11 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-16.tower-206.messagelabs.com!1392751450!4748890!1
X-Originating-IP: [209.85.212.174]
X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29856 invoked from network); 18 Feb 2014 19:24:10 -0000
Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com)
	(209.85.212.174)
	by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 19:24:10 -0000
Received: by mail-wi0-f174.google.com with SMTP id f8so3875596wiw.13
	for ; Tue, 18 Feb 2014 11:24:10 -0800 (PST)
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:content-type;
	bh=zb+75VTz8KNu8ns3sKUK6FqunaGbFyTC2osIf/AKci8=;
	b=LOC/hL0AZg+c/jQ+S6KOC2nAur7ayPuPw2KHXKxt3XsM/9PHsXcKJEVCE+L0saABSf
	Q2cT5QFpC4Mm7aVkX+M2D7jTZctuvlfKIP6nCNON/tqpi84FrWStltczLh7qcEPRk81T
	NitHEbrWGxE53ZqO0+xAlPtwvcpUtaK6UBilKlCM24nRA2ThUzVWpSkwEjQPgNVBbGZR
	MjHHpYDm+1IgM+e5pugPdEf/r9gZePO6h7Id2q9AqsCeDtEtpQ4z2mvq0ZvdPywNxrgM
	GAOXm6kuvUHRVh/+RGxHh1Ju8//6dK4lfjOVVMxGK2wr144khRX76wofC34xeOlB0dAs
	3Kcg==
X-Received: by 10.180.79.7 with SMTP id f7mr19692981wix.20.1392751450307;
	Tue, 18 Feb 2014 11:24:10 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id j9sm47703189wjz.13.2014.02.18.11.24.08
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 18 Feb 2014 11:24:09 -0800 (PST)
Message-ID: <5303B34E.5000702@xen.org>
Date: Tue, 18 Feb 2014 19:23:58 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org"
	, 
	Russell Pavlicek , 
	Tim Mackey 
Cc: xen-users@lists.xenproject.org
Subject: [MirageOS-devel] [Vote] Proposal: Moving XCP binaries to
	XenServer.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6203917824096685361=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============6203917824096685361==
Content-Type: multipart/alternative;
 boundary="------------060701020901020602030902"

This is a multi-part message in MIME format.
--------------060701020901020602030902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

I wanted to propose to move the legacy XCP binaries from XenProject.org 
to XenServer.org. With XenServer being fully open source and XCP 
basically being a variant of XenServer, it would make a lot more sense 
to keep all these binaries with XenServer.org. The fact that we have XCP 
and XenServer.org in two different places has led to:

* fragmentation of the XCP user community
* it is also a constant source of confusion in the user community

In a nutshell many people don't know whether they should go to 
XenServer.org to ask XCP related questions or whether to ask them on 
XenProject.org. As a result many questions remain unanswered. Russell 
and me spend a lot of our time, pointing people to the right place 
and/or cross-posting. I was hoping things would get better over time, 
but they have not improved.

When the Xen Project was created, there was no real alternative but to 
keep XCP as part of the Xen Project. With XenServer being fully open 
source, and being established, there is no reason why we can't clean up 
some of the confusion. In my opinion we really should do this.

This proposal does *not* affect the XAPI project : the XAPI project 
would continue to develop the XAPI toolstack as part of the Xen Project 
(and deliver source "releases"). In fact, I would also propose to make 
the xapi mailing list a developer mailing list. This fits much better 
with how the Hypervisor and MirageOS projects are run and creates an 
overall cleaner and easier to understand model for the Xen Project.

I have in principle agreement from:
* The Xen Project Advisory Board and the Linux Foundation (which is 
needed as I am proposing to move assets out of XenProject.org)
* Citrix to take on XCP as part of XenProject.org
* Citrix to provide resources to migrate content and redirect URLs from 
xxx.XenProject.org to XenServer.org such that people wont be impacted. 
This part is quite important. People who would come to download or find 
information about XCP, are basically encouraged to ask XCP related 
questions on XenProject.org. If they are redirected to the right place 
in XenServer.org, that does mean that they are redirected to the site 
where they should ask questions.
* I may be able to get some resources to have the wiki cleaned up too 
and do some redirects there too (another source of ongoing confusion)

== Who and how to vote? ==

As this is not an entirely project local decision, I propose that 
according to http://xenproject.org/governance.html
- Members of all developer mailing lists (including the user lists) on 
Xenproject.org can review the proposal and voice an opinion
- Maintainers of*all mature*projects and the Xenproject.org community 
manager are allowed to vote : these are maintainers of xen-devel and xen-api

You would vote by replying "+1"
If you don't care vote "0"
If you object, vote "-1", which must include an alternative proposal or 
a detailed explanation of the reasons for the negative vote.

Please vote by Feb 25th

Best Regards
Lars

--------------060701020901020602030902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    Hi all,

    

    I wanted to propose to move the legacy XCP binaries from
    XenProject.org to XenServer.org. With XenServer being fully open
    source and XCP basically being a variant of XenServer, it would make
    a lot more sense to keep all these binaries with XenServer.org. The
    fact that we have XCP and XenServer.org in two different places has
    led to:

    

    * fragmentation of the XCP user community 

    * it is also a constant source of confusion in the user community

    

    In a nutshell many people don't know whether they should go to
    XenServer.org to ask XCP related questions or whether to ask them on
    XenProject.org. As a result many questions remain unanswered.
    Russell and me spend a lot of our time, pointing people to the right
    place and/or cross-posting. I was hoping things would get better
    over time, but they have not improved.

    

    When the Xen Project was created, there was no real alternative but
    to keep XCP as part of the Xen Project. With XenServer being fully
    open source, and being established, there is no reason why we can't
    clean up some of the confusion. In my opinion we really should do
    this.

    

    This proposal does *not* affect the XAPI project : the XAPI project
    would continue to develop the XAPI toolstack as part of the Xen
    Project (and deliver source "releases"). In fact, I would also
    propose to make the xapi mailing list a developer mailing list. This
    fits much better with how the Hypervisor and MirageOS projects are
    run and creates an overall cleaner and easier to understand model
    for the Xen Project. 

    

    I have in principle agreement from:

    * The Xen Project Advisory Board and the Linux Foundation (which is
    needed as I am proposing to move assets out of XenProject.org)

    * Citrix to take on XCP as part of XenProject.org

    * Citrix to provide resources to migrate content and redirect URLs
    from xxx.XenProject.org to XenServer.org such that people wont be
    impacted. This part is quite important. People who would come to
    download or find information about XCP, are basically encouraged to
    ask XCP related questions on XenProject.org. If they are redirected
    to the right place in XenServer.org, that does mean that they are
    redirected to the site where they should ask questions. 

    * I may be able to get some resources to have the wiki cleaned up
    too and do some redirects there too (another source of ongoing
    confusion)

    

    == Who and how to vote? ==

    

    As this is not an entirely project local decision, I propose that
    according to http://xenproject.org/governance.html

    - Members of all developer mailing lists (including the user lists)
    on Xenproject.org can review the proposal and voice an opinion

    
    - Maintainers of all mature projects and the
    Xenproject.org community manager are allowed to vote : these are
    maintainers of xen-devel and xen-api

    

    You would vote by replying "+1"

    If you don't care vote "0"

    If you object, vote "-1", which must include an alternative proposal
    or a detailed explanation of the reasons for the negative vote.

    

    Please vote by Feb 25th 

    

    Best Regards

    Lars

  


--------------060701020901020602030902--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============6203917824096685361==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 18 19:24:17 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 18 Feb 2014 19:24: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 1WFqH7-000409-Vt; Tue, 18 Feb 2014 19:24:13 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WFqH7-0003zt-00; Tue, 18 Feb 2014 19:24:13 +0000
Received: from [85.158.139.211:50313] by server-5.bemta-5.messagelabs.com id
	20/B7-32749-B53B3035; Tue, 18 Feb 2014 19:24:11 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-16.tower-206.messagelabs.com!1392751450!4748890!1
X-Originating-IP: [209.85.212.174]
X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29856 invoked from network); 18 Feb 2014 19:24:10 -0000
Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com)
	(209.85.212.174)
	by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	18 Feb 2014 19:24:10 -0000
Received: by mail-wi0-f174.google.com with SMTP id f8so3875596wiw.13
	for ; Tue, 18 Feb 2014 11:24:10 -0800 (PST)
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:content-type;
	bh=zb+75VTz8KNu8ns3sKUK6FqunaGbFyTC2osIf/AKci8=;
	b=LOC/hL0AZg+c/jQ+S6KOC2nAur7ayPuPw2KHXKxt3XsM/9PHsXcKJEVCE+L0saABSf
	Q2cT5QFpC4Mm7aVkX+M2D7jTZctuvlfKIP6nCNON/tqpi84FrWStltczLh7qcEPRk81T
	NitHEbrWGxE53ZqO0+xAlPtwvcpUtaK6UBilKlCM24nRA2ThUzVWpSkwEjQPgNVBbGZR
	MjHHpYDm+1IgM+e5pugPdEf/r9gZePO6h7Id2q9AqsCeDtEtpQ4z2mvq0ZvdPywNxrgM
	GAOXm6kuvUHRVh/+RGxHh1Ju8//6dK4lfjOVVMxGK2wr144khRX76wofC34xeOlB0dAs
	3Kcg==
X-Received: by 10.180.79.7 with SMTP id f7mr19692981wix.20.1392751450307;
	Tue, 18 Feb 2014 11:24:10 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id j9sm47703189wjz.13.2014.02.18.11.24.08
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 18 Feb 2014 11:24:09 -0800 (PST)
Message-ID: <5303B34E.5000702@xen.org>
Date: Tue, 18 Feb 2014 19:23:58 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org"
	, 
	Russell Pavlicek , 
	Tim Mackey 
Cc: xen-users@lists.xenproject.org
Subject: [MirageOS-devel] [Vote] Proposal: Moving XCP binaries to
	XenServer.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6203917824096685361=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============6203917824096685361==
Content-Type: multipart/alternative;
 boundary="------------060701020901020602030902"

This is a multi-part message in MIME format.
--------------060701020901020602030902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

I wanted to propose to move the legacy XCP binaries from XenProject.org 
to XenServer.org. With XenServer being fully open source and XCP 
basically being a variant of XenServer, it would make a lot more sense 
to keep all these binaries with XenServer.org. The fact that we have XCP 
and XenServer.org in two different places has led to:

* fragmentation of the XCP user community
* it is also a constant source of confusion in the user community

In a nutshell many people don't know whether they should go to 
XenServer.org to ask XCP related questions or whether to ask them on 
XenProject.org. As a result many questions remain unanswered. Russell 
and me spend a lot of our time, pointing people to the right place 
and/or cross-posting. I was hoping things would get better over time, 
but they have not improved.

When the Xen Project was created, there was no real alternative but to 
keep XCP as part of the Xen Project. With XenServer being fully open 
source, and being established, there is no reason why we can't clean up 
some of the confusion. In my opinion we really should do this.

This proposal does *not* affect the XAPI project : the XAPI project 
would continue to develop the XAPI toolstack as part of the Xen Project 
(and deliver source "releases"). In fact, I would also propose to make 
the xapi mailing list a developer mailing list. This fits much better 
with how the Hypervisor and MirageOS projects are run and creates an 
overall cleaner and easier to understand model for the Xen Project.

I have in principle agreement from:
* The Xen Project Advisory Board and the Linux Foundation (which is 
needed as I am proposing to move assets out of XenProject.org)
* Citrix to take on XCP as part of XenProject.org
* Citrix to provide resources to migrate content and redirect URLs from 
xxx.XenProject.org to XenServer.org such that people wont be impacted. 
This part is quite important. People who would come to download or find 
information about XCP, are basically encouraged to ask XCP related 
questions on XenProject.org. If they are redirected to the right place 
in XenServer.org, that does mean that they are redirected to the site 
where they should ask questions.
* I may be able to get some resources to have the wiki cleaned up too 
and do some redirects there too (another source of ongoing confusion)

== Who and how to vote? ==

As this is not an entirely project local decision, I propose that 
according to http://xenproject.org/governance.html
- Members of all developer mailing lists (including the user lists) on 
Xenproject.org can review the proposal and voice an opinion
- Maintainers of*all mature*projects and the Xenproject.org community 
manager are allowed to vote : these are maintainers of xen-devel and xen-api

You would vote by replying "+1"
If you don't care vote "0"
If you object, vote "-1", which must include an alternative proposal or 
a detailed explanation of the reasons for the negative vote.

Please vote by Feb 25th

Best Regards
Lars

--------------060701020901020602030902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    Hi all,

    

    I wanted to propose to move the legacy XCP binaries from
    XenProject.org to XenServer.org. With XenServer being fully open
    source and XCP basically being a variant of XenServer, it would make
    a lot more sense to keep all these binaries with XenServer.org. The
    fact that we have XCP and XenServer.org in two different places has
    led to:

    

    * fragmentation of the XCP user community 

    * it is also a constant source of confusion in the user community

    

    In a nutshell many people don't know whether they should go to
    XenServer.org to ask XCP related questions or whether to ask them on
    XenProject.org. As a result many questions remain unanswered.
    Russell and me spend a lot of our time, pointing people to the right
    place and/or cross-posting. I was hoping things would get better
    over time, but they have not improved.

    

    When the Xen Project was created, there was no real alternative but
    to keep XCP as part of the Xen Project. With XenServer being fully
    open source, and being established, there is no reason why we can't
    clean up some of the confusion. In my opinion we really should do
    this.

    

    This proposal does *not* affect the XAPI project : the XAPI project
    would continue to develop the XAPI toolstack as part of the Xen
    Project (and deliver source "releases"). In fact, I would also
    propose to make the xapi mailing list a developer mailing list. This
    fits much better with how the Hypervisor and MirageOS projects are
    run and creates an overall cleaner and easier to understand model
    for the Xen Project. 

    

    I have in principle agreement from:

    * The Xen Project Advisory Board and the Linux Foundation (which is
    needed as I am proposing to move assets out of XenProject.org)

    * Citrix to take on XCP as part of XenProject.org

    * Citrix to provide resources to migrate content and redirect URLs
    from xxx.XenProject.org to XenServer.org such that people wont be
    impacted. This part is quite important. People who would come to
    download or find information about XCP, are basically encouraged to
    ask XCP related questions on XenProject.org. If they are redirected
    to the right place in XenServer.org, that does mean that they are
    redirected to the site where they should ask questions. 

    * I may be able to get some resources to have the wiki cleaned up
    too and do some redirects there too (another source of ongoing
    confusion)

    

    == Who and how to vote? ==

    

    As this is not an entirely project local decision, I propose that
    according to http://xenproject.org/governance.html

    - Members of all developer mailing lists (including the user lists)
    on Xenproject.org can review the proposal and voice an opinion

    
    - Maintainers of all mature projects and the
    Xenproject.org community manager are allowed to vote : these are
    maintainers of xen-devel and xen-api

    

    You would vote by replying "+1"

    If you don't care vote "0"

    If you object, vote "-1", which must include an alternative proposal
    or a detailed explanation of the reasons for the negative vote.

    

    Please vote by Feb 25th 

    

    Best Regards

    Lars

  


--------------060701020901020602030902--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============6203917824096685361==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 19 10:41:37 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 19 Feb 2014 10:41: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 1WG4aq-0002Ih-7F; Wed, 19 Feb 2014 10:41:32 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WG4ap-0002IY-AV; Wed, 19 Feb 2014 10:41:31 +0000
Received: from [85.158.139.211:65322] by server-8.bemta-5.messagelabs.com id
	F3/F4-05298-A5A84035; Wed, 19 Feb 2014 10:41:30 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-5.tower-206.messagelabs.com!1392806488!334015!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19873 invoked from network); 19 Feb 2014 10:41:29 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	19 Feb 2014 10:41:29 -0000
X-IronPort-AV: E=Sophos;i="4.97,504,1389744000"; d="scan'208";a="103843415"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 19 Feb 2014 10:41:27 +0000
Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL03.citrite.net
	(10.13.107.80) with Microsoft SMTP Server id 14.2.342.4;
	Wed, 19 Feb 2014 05:41:27 -0500
Message-ID: <1392806485.23084.125.camel@kazak.uk.xensource.com>
From: Ian Campbell 
To: 
Date: Wed, 19 Feb 2014 10:41:25 +0000
In-Reply-To: <5303B34E.5000702@xen.org>
References: <5303B34E.5000702@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA2
Cc: Tim Mackey ,
	"mirageos-devel@lists.xenproject.org"
	, xen-users@lists.xenproject.org,
	Russell Pavlicek ,
	"xen-devel@lists.xen.org" ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] [Vote] Proposal: Moving XCP
 binaries to XenServer.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On Tue, 2014-02-18 at 19:23 +0000, Lars Kurth wrote:
> Hi all,
> 
> I wanted to propose to move the legacy XCP binaries from
> XenProject.org to XenServer.org. With XenServer being fully open
> source and XCP basically being a variant of XenServer, it would make a
> lot more sense to keep all these binaries with XenServer.org. The fact
> that we have XCP and XenServer.org in two different places has led to:
> 
> * fragmentation of the XCP user community 
> * it is also a constant source of confusion in the user community
> 
> In a nutshell many people don't know whether they should go to
> XenServer.org to ask XCP related questions or whether to ask them on
> XenProject.org. As a result many questions remain unanswered. Russell
> and me spend a lot of our time, pointing people to the right place
> and/or cross-posting.

As do I, from xen-users@ -> xen-api@xenproject/xs-devel@xenserver.

>  I was hoping things would get better over time, but they have not
> improved.
> 
> When the Xen Project was created, there was no real alternative but to
> keep XCP as part of the Xen Project. With XenServer being fully open
> source, and being established, there is no reason why we can't clean
> up some of the confusion. In my opinion we really should do this.
> 
> This proposal does *not* affect the XAPI project : the XAPI project
> would continue to develop the XAPI toolstack as part of the Xen
> Project (and deliver source "releases"). In fact, I would also propose
> to make the xapi mailing list a developer mailing list. This fits much
> better with how the Hypervisor and MirageOS projects are run and
> creates an overall cleaner and easier to understand model for the Xen
> Project. 

If xen-api@ becomes a devel focused list then what would be the
appropriate place to redirect user requests to? xs-devel@xenserver.org?
What about for xapi users who are not based on xenserver?

> == Who and how to vote? ==
> 
> As this is not an entirely project local decision, I propose that
> according to http://xenproject.org/governance.html
> - Members of all developer mailing lists (including the user lists) on
> Xenproject.org can review the proposal and voice an opinion
> - Maintainers of all mature projects and the Xenproject.org community
> manager are allowed to vote : these are maintainers of xen-devel and
> xen-api
> 
> You would vote by replying "+1"

+1 

> If you don't care vote "0"
> If you object, vote "-1", which must include an alternative proposal
> or a detailed explanation of the reasons for the negative vote.
> 
> Please vote by Feb 25th 
> 
> Best Regards
> Lars
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 19 10:41:37 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 19 Feb 2014 10:41: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 1WG4aq-0002Ih-7F; Wed, 19 Feb 2014 10:41:32 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WG4ap-0002IY-AV; Wed, 19 Feb 2014 10:41:31 +0000
Received: from [85.158.139.211:65322] by server-8.bemta-5.messagelabs.com id
	F3/F4-05298-A5A84035; Wed, 19 Feb 2014 10:41:30 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-5.tower-206.messagelabs.com!1392806488!334015!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19873 invoked from network); 19 Feb 2014 10:41:29 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	19 Feb 2014 10:41:29 -0000
X-IronPort-AV: E=Sophos;i="4.97,504,1389744000"; d="scan'208";a="103843415"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 19 Feb 2014 10:41:27 +0000
Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL03.citrite.net
	(10.13.107.80) with Microsoft SMTP Server id 14.2.342.4;
	Wed, 19 Feb 2014 05:41:27 -0500
Message-ID: <1392806485.23084.125.camel@kazak.uk.xensource.com>
From: Ian Campbell 
To: 
Date: Wed, 19 Feb 2014 10:41:25 +0000
In-Reply-To: <5303B34E.5000702@xen.org>
References: <5303B34E.5000702@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.4.4-3 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA2
Cc: Tim Mackey ,
	"mirageos-devel@lists.xenproject.org"
	, xen-users@lists.xenproject.org,
	Russell Pavlicek ,
	"xen-devel@lists.xen.org" ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] [Vote] Proposal: Moving XCP
 binaries to XenServer.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On Tue, 2014-02-18 at 19:23 +0000, Lars Kurth wrote:
> Hi all,
> 
> I wanted to propose to move the legacy XCP binaries from
> XenProject.org to XenServer.org. With XenServer being fully open
> source and XCP basically being a variant of XenServer, it would make a
> lot more sense to keep all these binaries with XenServer.org. The fact
> that we have XCP and XenServer.org in two different places has led to:
> 
> * fragmentation of the XCP user community 
> * it is also a constant source of confusion in the user community
> 
> In a nutshell many people don't know whether they should go to
> XenServer.org to ask XCP related questions or whether to ask them on
> XenProject.org. As a result many questions remain unanswered. Russell
> and me spend a lot of our time, pointing people to the right place
> and/or cross-posting.

As do I, from xen-users@ -> xen-api@xenproject/xs-devel@xenserver.

>  I was hoping things would get better over time, but they have not
> improved.
> 
> When the Xen Project was created, there was no real alternative but to
> keep XCP as part of the Xen Project. With XenServer being fully open
> source, and being established, there is no reason why we can't clean
> up some of the confusion. In my opinion we really should do this.
> 
> This proposal does *not* affect the XAPI project : the XAPI project
> would continue to develop the XAPI toolstack as part of the Xen
> Project (and deliver source "releases"). In fact, I would also propose
> to make the xapi mailing list a developer mailing list. This fits much
> better with how the Hypervisor and MirageOS projects are run and
> creates an overall cleaner and easier to understand model for the Xen
> Project. 

If xen-api@ becomes a devel focused list then what would be the
appropriate place to redirect user requests to? xs-devel@xenserver.org?
What about for xapi users who are not based on xenserver?

> == Who and how to vote? ==
> 
> As this is not an entirely project local decision, I propose that
> according to http://xenproject.org/governance.html
> - Members of all developer mailing lists (including the user lists) on
> Xenproject.org can review the proposal and voice an opinion
> - Maintainers of all mature projects and the Xenproject.org community
> manager are allowed to vote : these are maintainers of xen-devel and
> xen-api
> 
> You would vote by replying "+1"

+1 

> If you don't care vote "0"
> If you object, vote "-1", which must include an alternative proposal
> or a detailed explanation of the reasons for the negative vote.
> 
> Please vote by Feb 25th 
> 
> Best Regards
> Lars
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel



_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 19 14:39:20 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 19 Feb 2014 14:39:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WG8Is-0004zI-VB; Wed, 19 Feb 2014 14:39:14 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WG8Ir-0004yt-Kc; Wed, 19 Feb 2014 14:39:13 +0000
Received: from [193.109.254.147:17014] by server-11.bemta-14.messagelabs.com
	id 79/9F-24604-012C4035; Wed, 19 Feb 2014 14:39:12 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1392820752!1681882!1
X-Originating-IP: [74.125.83.49]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2821 invoked from network); 19 Feb 2014 14:39:12 -0000
Received: from mail-ee0-f49.google.com (HELO mail-ee0-f49.google.com)
	(74.125.83.49)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	19 Feb 2014 14:39:12 -0000
Received: by mail-ee0-f49.google.com with SMTP id d17so275352eek.36
	for ; Wed, 19 Feb 2014 06:39:11 -0800 (PST)
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=jyBcNstFs7/WXjku9BmwT6oQenNzNO0F8mtIRscQ2GE=;
	b=v/qOBULxVvw+ETh+Yo0teoOOEvJWdjcuachF8o6YpuwZ0PMuQh97ySHGv/PkaQOsVD
	nEN7KsAdMPQNrRJuYq/hafto9K48B3EuLsLq5QiaLWszV9pgvoO7xu0di6ykVEujAZn6
	5ky5MYO520mZ9zfjvGoJiB7oL6g1kZgwhj6RtlF3CyFe6avDU6gkKEK3DRQM7LfyDG0y
	cWcyi5LZ5ZeWMEpoFDgrPjipMM2oxXJAOJEj9S43VToHzp3R00BFhVHPrshtQOs6QntR
	9eEzkUHC9TDXoL8m8zKuvovxRpKdVeDhXNT5w1W9uJZ1Upd4FE9GG9KCjFytV4VPQluX
	bdXA==
X-Received: by 10.14.194.193 with SMTP id m41mr3750007een.76.1392820751899;
	Wed, 19 Feb 2014 06:39:11 -0800 (PST)
Received: from [172.16.25.10] ([185.25.64.249])
	by mx.google.com with ESMTPSA id x2sm1429317eeo.8.2014.02.19.06.39.10
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 19 Feb 2014 06:39:11 -0800 (PST)
Message-ID: <5304C20D.3070509@xen.org>
Date: Wed, 19 Feb 2014 14:39:09 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ian Campbell 
References: <5303B34E.5000702@xen.org>
	<1392806485.23084.125.camel@kazak.uk.xensource.com>
In-Reply-To: <1392806485.23084.125.camel@kazak.uk.xensource.com>
Cc: Tim Mackey ,
	"mirageos-devel@lists.xenproject.org"
	, xen-users@lists.xenproject.org,
	Russell Pavlicek ,
	"xen-devel@lists.xen.org" ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] [Vote] Proposal: Moving XCP
	binaries to XenServer.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 19/02/2014 10:41, Ian Campbell wrote:
> On Tue, 2014-02-18 at 19:23 +0000, Lars Kurth wrote:
>> Hi all,
>> ...
>> This proposal does *not* affect the XAPI project : the XAPI project
>> would continue to develop the XAPI toolstack as part of the Xen
>> Project (and deliver source "releases"). In fact, I would also propose
>> to make the xapi mailing list a developer mailing list. This fits much
>> better with how the Hypervisor and MirageOS projects are run and
>> creates an overall cleaner and easier to understand model for the Xen
>> Project.
> If xen-api@ becomes a devel focused list then what would be the
> appropriate place to redirect user requests to? xs-devel@xenserver.org?
> What about for xapi users who are not based on xenserver?
Good point. This was just a side-topic that is not really part of this 
proposal.

Lars


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 19 14:39:20 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 19 Feb 2014 14:39:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WG8Is-0004zI-VB; Wed, 19 Feb 2014 14:39:14 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WG8Ir-0004yt-Kc; Wed, 19 Feb 2014 14:39:13 +0000
Received: from [193.109.254.147:17014] by server-11.bemta-14.messagelabs.com
	id 79/9F-24604-012C4035; Wed, 19 Feb 2014 14:39:12 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1392820752!1681882!1
X-Originating-IP: [74.125.83.49]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2821 invoked from network); 19 Feb 2014 14:39:12 -0000
Received: from mail-ee0-f49.google.com (HELO mail-ee0-f49.google.com)
	(74.125.83.49)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	19 Feb 2014 14:39:12 -0000
Received: by mail-ee0-f49.google.com with SMTP id d17so275352eek.36
	for ; Wed, 19 Feb 2014 06:39:11 -0800 (PST)
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=jyBcNstFs7/WXjku9BmwT6oQenNzNO0F8mtIRscQ2GE=;
	b=v/qOBULxVvw+ETh+Yo0teoOOEvJWdjcuachF8o6YpuwZ0PMuQh97ySHGv/PkaQOsVD
	nEN7KsAdMPQNrRJuYq/hafto9K48B3EuLsLq5QiaLWszV9pgvoO7xu0di6ykVEujAZn6
	5ky5MYO520mZ9zfjvGoJiB7oL6g1kZgwhj6RtlF3CyFe6avDU6gkKEK3DRQM7LfyDG0y
	cWcyi5LZ5ZeWMEpoFDgrPjipMM2oxXJAOJEj9S43VToHzp3R00BFhVHPrshtQOs6QntR
	9eEzkUHC9TDXoL8m8zKuvovxRpKdVeDhXNT5w1W9uJZ1Upd4FE9GG9KCjFytV4VPQluX
	bdXA==
X-Received: by 10.14.194.193 with SMTP id m41mr3750007een.76.1392820751899;
	Wed, 19 Feb 2014 06:39:11 -0800 (PST)
Received: from [172.16.25.10] ([185.25.64.249])
	by mx.google.com with ESMTPSA id x2sm1429317eeo.8.2014.02.19.06.39.10
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 19 Feb 2014 06:39:11 -0800 (PST)
Message-ID: <5304C20D.3070509@xen.org>
Date: Wed, 19 Feb 2014 14:39:09 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ian Campbell 
References: <5303B34E.5000702@xen.org>
	<1392806485.23084.125.camel@kazak.uk.xensource.com>
In-Reply-To: <1392806485.23084.125.camel@kazak.uk.xensource.com>
Cc: Tim Mackey ,
	"mirageos-devel@lists.xenproject.org"
	, xen-users@lists.xenproject.org,
	Russell Pavlicek ,
	"xen-devel@lists.xen.org" ,
	"xen-api@lists.xen.org" 
Subject: Re: [MirageOS-devel] [Xen-devel] [Vote] Proposal: Moving XCP
	binaries to XenServer.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 19/02/2014 10:41, Ian Campbell wrote:
> On Tue, 2014-02-18 at 19:23 +0000, Lars Kurth wrote:
>> Hi all,
>> ...
>> This proposal does *not* affect the XAPI project : the XAPI project
>> would continue to develop the XAPI toolstack as part of the Xen
>> Project (and deliver source "releases"). In fact, I would also propose
>> to make the xapi mailing list a developer mailing list. This fits much
>> better with how the Hypervisor and MirageOS projects are run and
>> creates an overall cleaner and easier to understand model for the Xen
>> Project.
> If xen-api@ becomes a devel focused list then what would be the
> appropriate place to redirect user requests to? xs-devel@xenserver.org?
> What about for xapi users who are not based on xenserver?
Good point. This was just a side-topic that is not really part of this 
proposal.

Lars


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 11:14:36 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 11:14: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 1WGRaI-0000yv-1o; Thu, 20 Feb 2014 11:14:30 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGRaH-0000yk-AQ
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 11:14:29 +0000
Received: from [193.109.254.147:14295] by server-3.bemta-14.messagelabs.com id
	AE/4D-00432-493E5035; Thu, 20 Feb 2014 11:14:28 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-10.tower-27.messagelabs.com!1392894867!5682088!1
X-Originating-IP: [209.85.212.170]
X-SpamReason: No, hits=0.8 required=7.0 tests=HTML_90_100,HTML_MESSAGE,
	RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30739 invoked from network); 20 Feb 2014 11:14:27 -0000
Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com)
	(209.85.212.170)
	by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	20 Feb 2014 11:14:27 -0000
Received: by mail-wi0-f170.google.com with SMTP id hi5so493090wib.5
	for ;
	Thu, 20 Feb 2014 03:14:27 -0800 (PST)
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=hoeOm05UMJHrSp0hzIjI07KAneSs01mA6wVTUZx6rw4=;
	b=sJLSoQVV0a6vc4lFci+4eMxHiI0twhXM8m9q2tMRo17TRspIUOoIkaQWugs4bPnP8F
	Fvd6NYcHBE5KQKiaPcI/QyljrPM94Nj9HoEHJEeP8BfvxHndrTO2M2DZcdNUBY4Invsv
	5MdCZxNzYNYjGpQA2Xv/BcEBQ+u6Yh0qpOB6ofcDUtQ2MJWWH4hVHQOtWA77X3JGL0V9
	xiJZPkiU2nt3UpodPjyCH7HcE+H2MNTJmvSnT2uoq0H1nTxayrsY5qFYlOk3RYxhex5U
	+HXACU1woLRh+baEh4xcVKMV1YehUcvZy+5vlk6fr4RwaXIpCiCstUw8xCF7bFCOlhaq
	o5vQ==
X-Received: by 10.194.92.199 with SMTP id co7mr1481061wjb.14.1392894867249;
	Thu, 20 Feb 2014 03:14:27 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id q2sm8075334wjq.0.2014.02.20.03.14.25
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 20 Feb 2014 03:14:26 -0800 (PST)
Message-ID: <5305E391.8020406@xen.org>
Date: Thu, 20 Feb 2014 11:14:25 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "mirageos-devel@lists.xenproject.org"
	, 
	Russell Pavlicek 
Subject: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0825088726193626547=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============0825088726193626547==
Content-Type: multipart/alternative;
 boundary="------------070808040805070002000300"

This is a multi-part message in MIME format.
--------------070808040805070002000300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Guys,
when you spin out a new release, can you please coordinate with Russell 
and me
If I look at http://xenproject.org/developers/teams/mirage-os.html and 
http://xenproject.org/downloads/mirage-os-archives.html these are now 
out-of-date
Regards
Lars


--------------070808040805070002000300
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    
    
Guys, 

      when you spin out a new release, can you please coordinate with
      Russell and me

      If I look at 
      http://xenproject.org/developers/teams/mirage-os.html and
      http://xenproject.org/downloads/mirage-os-archives.html these are
      now out-of-date

      Regards

      Lars

    
    
    
    
    
    
    
    
    
  


--------------070808040805070002000300--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============0825088726193626547==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 11:14:36 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 11:14: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 1WGRaI-0000yv-1o; Thu, 20 Feb 2014 11:14:30 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGRaH-0000yk-AQ
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 11:14:29 +0000
Received: from [193.109.254.147:14295] by server-3.bemta-14.messagelabs.com id
	AE/4D-00432-493E5035; Thu, 20 Feb 2014 11:14:28 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-10.tower-27.messagelabs.com!1392894867!5682088!1
X-Originating-IP: [209.85.212.170]
X-SpamReason: No, hits=0.8 required=7.0 tests=HTML_90_100,HTML_MESSAGE,
	RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30739 invoked from network); 20 Feb 2014 11:14:27 -0000
Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com)
	(209.85.212.170)
	by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	20 Feb 2014 11:14:27 -0000
Received: by mail-wi0-f170.google.com with SMTP id hi5so493090wib.5
	for ;
	Thu, 20 Feb 2014 03:14:27 -0800 (PST)
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=hoeOm05UMJHrSp0hzIjI07KAneSs01mA6wVTUZx6rw4=;
	b=sJLSoQVV0a6vc4lFci+4eMxHiI0twhXM8m9q2tMRo17TRspIUOoIkaQWugs4bPnP8F
	Fvd6NYcHBE5KQKiaPcI/QyljrPM94Nj9HoEHJEeP8BfvxHndrTO2M2DZcdNUBY4Invsv
	5MdCZxNzYNYjGpQA2Xv/BcEBQ+u6Yh0qpOB6ofcDUtQ2MJWWH4hVHQOtWA77X3JGL0V9
	xiJZPkiU2nt3UpodPjyCH7HcE+H2MNTJmvSnT2uoq0H1nTxayrsY5qFYlOk3RYxhex5U
	+HXACU1woLRh+baEh4xcVKMV1YehUcvZy+5vlk6fr4RwaXIpCiCstUw8xCF7bFCOlhaq
	o5vQ==
X-Received: by 10.194.92.199 with SMTP id co7mr1481061wjb.14.1392894867249;
	Thu, 20 Feb 2014 03:14:27 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id q2sm8075334wjq.0.2014.02.20.03.14.25
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 20 Feb 2014 03:14:26 -0800 (PST)
Message-ID: <5305E391.8020406@xen.org>
Date: Thu, 20 Feb 2014 11:14:25 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "mirageos-devel@lists.xenproject.org"
	, 
	Russell Pavlicek 
Subject: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0825088726193626547=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============0825088726193626547==
Content-Type: multipart/alternative;
 boundary="------------070808040805070002000300"

This is a multi-part message in MIME format.
--------------070808040805070002000300
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Guys,
when you spin out a new release, can you please coordinate with Russell 
and me
If I look at http://xenproject.org/developers/teams/mirage-os.html and 
http://xenproject.org/downloads/mirage-os-archives.html these are now 
out-of-date
Regards
Lars


--------------070808040805070002000300
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    
    
Guys, 

      when you spin out a new release, can you please coordinate with
      Russell and me

      If I look at 
      http://xenproject.org/developers/teams/mirage-os.html and
      http://xenproject.org/downloads/mirage-os-archives.html these are
      now out-of-date

      Regards

      Lars

    
    
    
    
    
    
    
    
    
  


--------------070808040805070002000300--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============0825088726193626547==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 11:45:32 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 11:45: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 1WGS4I-0002TB-Uy; Thu, 20 Feb 2014 11:45:30 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGS4H-0002T4-94
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 11:45:29 +0000
Received: from [193.109.254.147:28744] by server-12.bemta-14.messagelabs.com
	id BD/CC-17220-8DAE5035; Thu, 20 Feb 2014 11:45:28 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-11.tower-27.messagelabs.com!1392896727!377356!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17722 invoked from network); 20 Feb 2014 11:45:27 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-11.tower-27.messagelabs.com with SMTP;
	20 Feb 2014 11:45:27 -0000
Received: (qmail 27790 invoked by uid 634); 20 Feb 2014 11:45:27 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 20 Feb 2014 11:45:26 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <5305E391.8020406@xen.org>
Date: Thu, 20 Feb 2014 11:45:26 +0000
Message-Id: 
References: <5305E391.8020406@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Russell Pavlicek ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 20 Feb 2014, at 11:14, Lars Kurth  wrote:

> Guys, 
> when you spin out a new release, can you please coordinate with Russell and me
> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
> Regards
> Lars

Good point -- will do for future releases!

-anil


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 11:45:32 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 11:45: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 1WGS4I-0002TB-Uy; Thu, 20 Feb 2014 11:45:30 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGS4H-0002T4-94
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 11:45:29 +0000
Received: from [193.109.254.147:28744] by server-12.bemta-14.messagelabs.com
	id BD/CC-17220-8DAE5035; Thu, 20 Feb 2014 11:45:28 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-11.tower-27.messagelabs.com!1392896727!377356!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17722 invoked from network); 20 Feb 2014 11:45:27 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-11.tower-27.messagelabs.com with SMTP;
	20 Feb 2014 11:45:27 -0000
Received: (qmail 27790 invoked by uid 634); 20 Feb 2014 11:45:27 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 20 Feb 2014 11:45:26 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <5305E391.8020406@xen.org>
Date: Thu, 20 Feb 2014 11:45:26 +0000
Message-Id: 
References: <5305E391.8020406@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Russell Pavlicek ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 20 Feb 2014, at 11:14, Lars Kurth  wrote:

> Guys, 
> when you spin out a new release, can you please coordinate with Russell and me
> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
> Regards
> Lars

Good point -- will do for future releases!

-anil


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 15:23:25 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 15:23: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 1WGVT4-00017k-Oz; Thu, 20 Feb 2014 15:23:18 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGVT3-00017f-PC
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 15:23:18 +0000
Received: from [85.158.137.68:10989] by server-8.bemta-3.messagelabs.com id
	C0/4B-16039-3ED16035; Thu, 20 Feb 2014 15:23:15 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-8.tower-31.messagelabs.com!1392909793!3166520!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3636 invoked from network); 20 Feb 2014 15:23:13 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-8.tower-31.messagelabs.com with SMTP;
	20 Feb 2014 15:23:13 -0000
Received: (qmail 7825 invoked by uid 634); 20 Feb 2014 15:23:13 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED,HTML_MESSAGE
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 20 Feb 2014 15:23:11 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: 
Date: Thu, 20 Feb 2014 15:23:11 +0000
Message-Id: <712A14F8-B14A-4812-99B8-1C8ADBC8B82D@recoil.org>
References: 
	
	<092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org>
	<1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk>
	<0B0524FA-4837-4A59-91C7-CA1C279DCCCD@cam.ac.uk>
	
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] openmirage.org issue tracker?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6311280756273664887=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============6311280756273664887==
Content-Type: multipart/alternative; boundary="Apple-Mail=_B30E77C7-70E6-409B-8025-AFEC539EE112"


--Apple-Mail=_B30E77C7-70E6-409B-8025-AFEC539EE112
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

We've pretty much settled on https://github.com/mirage/mirage/issues =
now, which is shown on http://openmirage.org/community/ -- is that =
enough to link from the right places on xenproject.org, Lars?

-anil

On 11 Dec 2013, at 10:10, Lars Kurth  wrote:

> Hi all,
> once you decided how to do this, could you create a page on the xen =
project or your own wiki? I can then link to it from the relevant =
places.
> Regards
> Lars
>=20
>=20
> On Tue, Dec 10, 2013 at 11:52 AM, Amir Chaudhry  =
wrote:
>=20
> On 10 Dec 2013, at 11:25, Richard Mortier =
 wrote:
>=20
> >
> > On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote:
> >
> >> On 10 Dec 2013, at 09:39, Richard Mortier =
 wrote:
> >>
> >>> but that was only the latest discussion on the matter that i =
remember -- anil, any further thoughts on that? :)
> >>
> >> Good timing for this question -- I've been looking at how other =
projects do this, and there's a real mix of approaches.  My inclination =
is to focus all the issues in mirage/mirage, and use the label/milestone =
system to prioritise issues.
> >>
> >> This works well for libraries that are clearly 'mirage', but less =
so for ones like cohttp that are used in a number of different contexts.
> >
> > issue referencing will make that ok won't it?  (or are there limits =
to how references can work?)
>=20
> Also worth remembering that GitHub has a useful overview page for =
organisations so you can see all issues across all repos.  Annoyingly, =
it only shows you the overview for the subset of repos you have =
push/pull access to -- so it's more useful for admins (also it took me =
20mins to find that damn page).
>=20
> https://github.com/organizations/mirage/dashboard/issues
>=20
> Amir
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>=20
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_B30E77C7-70E6-409B-8025-AFEC539EE112
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

We've =
pretty much settled on https://github.com/mirage=
/mirage/issues now, which is shown on http://openmirage.org/community/=
 -- is that enough to link from the right places on xenproject.org, =
Lars?

-anil

On 11 Dec 2013, =
at 10:10, Lars Kurth <lars.kurth.xen@gmail.com> =
wrote:

Hi all,
once you decided how to do =
this, could you create a page on the xen project or your own wiki? I can =
then link to it from the relevant =
places.
Regards
Lars



On Tue, Dec 10, 2013 at 11:52 AM, =
Amir Chaudhry <amc79@cam.ac.uk> wrote:




On 10 Dec 2013, at 11:25, Richard Mortier <Richard.Mortier@nottingha=
m.ac.uk> wrote:



>

> On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote:

>

>> On 10 Dec 2013, at 09:39, Richard Mortier <Richard.Mortier@nottingha=
m.ac.uk> wrote:

>>

>>> but that was only the latest discussion on the matter that =
i remember -- anil, any further thoughts on that? :)

>>

>> Good timing for this question -- I've been looking at how other =
projects do this, and there's a real mix of approaches.  My =
inclination is to focus all the issues in mirage/mirage, and use the =
label/milestone system to prioritise issues.


>>

>> This works well for libraries that are clearly 'mirage', but =
less so for ones like cohttp that are used in a number of different =
contexts.

>

> issue referencing will make that ok won't it?  (or are there =
limits to how references can work?)




Also worth remembering that GitHub has a useful overview page for =
organisations so you can see all issues across all repos. =
 Annoyingly, it only shows you the overview for the subset of repos =
you have push/pull access to -- so it's more useful for admins (also it =
took me 20mins to find that damn page).




https://github.com/organizations/mirage/dashboard/issues=




Amir


_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists.x=
enproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir=
ageos-devel




_______________________________________________
MirageOS-devel =
mailing list
MirageOS-devel@lists.x=
enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/=
mirageos-devel

=

--Apple-Mail=_B30E77C7-70E6-409B-8025-AFEC539EE112--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============6311280756273664887==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 15:23:25 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 15:23: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 1WGVT4-00017k-Oz; Thu, 20 Feb 2014 15:23:18 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGVT3-00017f-PC
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 15:23:18 +0000
Received: from [85.158.137.68:10989] by server-8.bemta-3.messagelabs.com id
	C0/4B-16039-3ED16035; Thu, 20 Feb 2014 15:23:15 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-8.tower-31.messagelabs.com!1392909793!3166520!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3636 invoked from network); 20 Feb 2014 15:23:13 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-8.tower-31.messagelabs.com with SMTP;
	20 Feb 2014 15:23:13 -0000
Received: (qmail 7825 invoked by uid 634); 20 Feb 2014 15:23:13 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED,HTML_MESSAGE
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 20 Feb 2014 15:23:11 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: 
Date: Thu, 20 Feb 2014 15:23:11 +0000
Message-Id: <712A14F8-B14A-4812-99B8-1C8ADBC8B82D@recoil.org>
References: 
	
	<092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org>
	<1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk>
	<0B0524FA-4837-4A59-91C7-CA1C279DCCCD@cam.ac.uk>
	
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] openmirage.org issue tracker?
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6311280756273664887=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


--===============6311280756273664887==
Content-Type: multipart/alternative; boundary="Apple-Mail=_B30E77C7-70E6-409B-8025-AFEC539EE112"


--Apple-Mail=_B30E77C7-70E6-409B-8025-AFEC539EE112
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

We've pretty much settled on https://github.com/mirage/mirage/issues =
now, which is shown on http://openmirage.org/community/ -- is that =
enough to link from the right places on xenproject.org, Lars?

-anil

On 11 Dec 2013, at 10:10, Lars Kurth  wrote:

> Hi all,
> once you decided how to do this, could you create a page on the xen =
project or your own wiki? I can then link to it from the relevant =
places.
> Regards
> Lars
>=20
>=20
> On Tue, Dec 10, 2013 at 11:52 AM, Amir Chaudhry  =
wrote:
>=20
> On 10 Dec 2013, at 11:25, Richard Mortier =
 wrote:
>=20
> >
> > On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote:
> >
> >> On 10 Dec 2013, at 09:39, Richard Mortier =
 wrote:
> >>
> >>> but that was only the latest discussion on the matter that i =
remember -- anil, any further thoughts on that? :)
> >>
> >> Good timing for this question -- I've been looking at how other =
projects do this, and there's a real mix of approaches.  My inclination =
is to focus all the issues in mirage/mirage, and use the label/milestone =
system to prioritise issues.
> >>
> >> This works well for libraries that are clearly 'mirage', but less =
so for ones like cohttp that are used in a number of different contexts.
> >
> > issue referencing will make that ok won't it?  (or are there limits =
to how references can work?)
>=20
> Also worth remembering that GitHub has a useful overview page for =
organisations so you can see all issues across all repos.  Annoyingly, =
it only shows you the overview for the subset of repos you have =
push/pull access to -- so it's more useful for admins (also it took me =
20mins to find that damn page).
>=20
> https://github.com/organizations/mirage/dashboard/issues
>=20
> Amir
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>=20
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


--Apple-Mail=_B30E77C7-70E6-409B-8025-AFEC539EE112
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

We've =
pretty much settled on https://github.com/mirage=
/mirage/issues now, which is shown on http://openmirage.org/community/=
 -- is that enough to link from the right places on xenproject.org, =
Lars?

-anil

On 11 Dec 2013, =
at 10:10, Lars Kurth <lars.kurth.xen@gmail.com> =
wrote:

Hi all,
once you decided how to do =
this, could you create a page on the xen project or your own wiki? I can =
then link to it from the relevant =
places.
Regards
Lars



On Tue, Dec 10, 2013 at 11:52 AM, =
Amir Chaudhry <amc79@cam.ac.uk> wrote:




On 10 Dec 2013, at 11:25, Richard Mortier <Richard.Mortier@nottingha=
m.ac.uk> wrote:



>

> On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote:

>

>> On 10 Dec 2013, at 09:39, Richard Mortier <Richard.Mortier@nottingha=
m.ac.uk> wrote:

>>

>>> but that was only the latest discussion on the matter that =
i remember -- anil, any further thoughts on that? :)

>>

>> Good timing for this question -- I've been looking at how other =
projects do this, and there's a real mix of approaches.  My =
inclination is to focus all the issues in mirage/mirage, and use the =
label/milestone system to prioritise issues.


>>

>> This works well for libraries that are clearly 'mirage', but =
less so for ones like cohttp that are used in a number of different =
contexts.

>

> issue referencing will make that ok won't it?  (or are there =
limits to how references can work?)




Also worth remembering that GitHub has a useful overview page for =
organisations so you can see all issues across all repos. =
 Annoyingly, it only shows you the overview for the subset of repos =
you have push/pull access to -- so it's more useful for admins (also it =
took me 20mins to find that damn page).




https://github.com/organizations/mirage/dashboard/issues=




Amir


_______________________________________________

MirageOS-devel mailing list

MirageOS-devel@lists.x=
enproject.org

http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir=
ageos-devel




_______________________________________________
MirageOS-devel =
mailing list
MirageOS-devel@lists.x=
enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/=
mirageos-devel

=

--Apple-Mail=_B30E77C7-70E6-409B-8025-AFEC539EE112--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============6311280756273664887==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 18:22:12 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 18:22:12 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WGYG6-0001YO-HB; Thu, 20 Feb 2014 18:22:06 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGYG5-0001YH-9v
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 18:22:05 +0000
Received: from [85.158.143.35:2549] by server-3.bemta-4.messagelabs.com id
	76/19-11539-CC746035; Thu, 20 Feb 2014 18:22:04 +0000
X-Env-Sender: amirmc@gmail.com
X-Msg-Ref: server-3.tower-21.messagelabs.com!1392920523!7179925!1
X-Originating-IP: [74.125.82.47]
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5960 invoked from network); 20 Feb 2014 18:22:04 -0000
Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com)
	(74.125.82.47)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	20 Feb 2014 18:22:04 -0000
Received: by mail-wg0-f47.google.com with SMTP id k14so1764992wgh.14
	for ;
	Thu, 20 Feb 2014 10:22:03 -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:message-id:date
	:to:mime-version;
	bh=OFI7+Y1IsBdbHosGAuBmKTLEjzuKVRcDuKcf6pXFtZ8=;
	b=0ZwQqgvlb50ed5JgCZT2dPEaWmmvjmudMi1S7gOiBk3/T7mc7Ft9hUkgk25GC+EauX
	vvVJBKh0Kg97cBQWNfy0vncM5OghsM05gCB3hoABysQmJueEDgtjg1Fld2Az3z7GCXKl
	Z1FmlLLQXGve107EYf+QP1radgyjdtZT7OJ7GM1BEEUbxlqtpL3zPtc1ahk0s7SwMUCk
	0pXSgWmQDFguig8jOcuI16/ddb4Eu4Qa4CVxi879dxUa3d7SGCaybv5stMUUbMKFO114
	JgqjZEkpIW0yaoG7d1CHJo7edI43KtyCtUxoofOe4oPsMuVqFjODPZRN4zTVm3P7M+RW
	VO9g==
X-Received: by 10.180.13.5 with SMTP id d5mr3833345wic.54.1392920523436;
	Thu, 20 Feb 2014 10:22:03 -0800 (PST)
Received: from dhcp-172-17-157-4.eduroam.lapwing.private.cam.ac.uk
	(global-1-26.nat.csx.cam.ac.uk. [131.111.184.26])
	by mx.google.com with ESMTPSA id uq2sm10801936wjc.5.2014.02.20.10.22.02
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 20 Feb 2014 10:22:03 -0800 (PST)
From: Amir Chaudhry 
Message-Id: 
Date: Thu, 20 Feb 2014 18:22:02 +0000
To: "mirageos-devel@lists.xenproject.org" 
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [MirageOS-devel] Using Irminsule
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

I'm aware this isn't the right list but I'm guessing it's the right crowd.

I've just gone through Thomas' Irminsule walkthough [1], and it's only now that Ive started to appreciate how useful this could be.  Is there somewhere I can begin using the git backend (would presumably help with bug reports)?  I know Thomas' going to be away so he can't answer this but I'm curious to hear if other folks have tried anything.

Amir

[1] http://samoht.github.io/irminsule/
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 18:22:12 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 18:22:12 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WGYG6-0001YO-HB; Thu, 20 Feb 2014 18:22:06 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGYG5-0001YH-9v
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 18:22:05 +0000
Received: from [85.158.143.35:2549] by server-3.bemta-4.messagelabs.com id
	76/19-11539-CC746035; Thu, 20 Feb 2014 18:22:04 +0000
X-Env-Sender: amirmc@gmail.com
X-Msg-Ref: server-3.tower-21.messagelabs.com!1392920523!7179925!1
X-Originating-IP: [74.125.82.47]
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5960 invoked from network); 20 Feb 2014 18:22:04 -0000
Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com)
	(74.125.82.47)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	20 Feb 2014 18:22:04 -0000
Received: by mail-wg0-f47.google.com with SMTP id k14so1764992wgh.14
	for ;
	Thu, 20 Feb 2014 10:22:03 -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:message-id:date
	:to:mime-version;
	bh=OFI7+Y1IsBdbHosGAuBmKTLEjzuKVRcDuKcf6pXFtZ8=;
	b=0ZwQqgvlb50ed5JgCZT2dPEaWmmvjmudMi1S7gOiBk3/T7mc7Ft9hUkgk25GC+EauX
	vvVJBKh0Kg97cBQWNfy0vncM5OghsM05gCB3hoABysQmJueEDgtjg1Fld2Az3z7GCXKl
	Z1FmlLLQXGve107EYf+QP1radgyjdtZT7OJ7GM1BEEUbxlqtpL3zPtc1ahk0s7SwMUCk
	0pXSgWmQDFguig8jOcuI16/ddb4Eu4Qa4CVxi879dxUa3d7SGCaybv5stMUUbMKFO114
	JgqjZEkpIW0yaoG7d1CHJo7edI43KtyCtUxoofOe4oPsMuVqFjODPZRN4zTVm3P7M+RW
	VO9g==
X-Received: by 10.180.13.5 with SMTP id d5mr3833345wic.54.1392920523436;
	Thu, 20 Feb 2014 10:22:03 -0800 (PST)
Received: from dhcp-172-17-157-4.eduroam.lapwing.private.cam.ac.uk
	(global-1-26.nat.csx.cam.ac.uk. [131.111.184.26])
	by mx.google.com with ESMTPSA id uq2sm10801936wjc.5.2014.02.20.10.22.02
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 20 Feb 2014 10:22:03 -0800 (PST)
From: Amir Chaudhry 
Message-Id: 
Date: Thu, 20 Feb 2014 18:22:02 +0000
To: "mirageos-devel@lists.xenproject.org" 
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [MirageOS-devel] Using Irminsule
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

I'm aware this isn't the right list but I'm guessing it's the right crowd.

I've just gone through Thomas' Irminsule walkthough [1], and it's only now that Ive started to appreciate how useful this could be.  Is there somewhere I can begin using the git backend (would presumably help with bug reports)?  I know Thomas' going to be away so he can't answer this but I'm curious to hear if other folks have tried anything.

Amir

[1] http://samoht.github.io/irminsule/
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 21:04:51 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 21:04:51 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WGanU-0007bx-BK; Thu, 20 Feb 2014 21:04:44 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGanT-0007bs-3P
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 21:04:43 +0000
Received: from [85.158.137.68:53959] by server-6.bemta-3.messagelabs.com id
	8C/25-09180-9ED66035; Thu, 20 Feb 2014 21:04:41 +0000
X-Env-Sender: thomas.gazagnaire@gmail.com
X-Msg-Ref: server-13.tower-31.messagelabs.com!1392930280!1971276!1
X-Originating-IP: [74.125.82.49]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32088 invoked from network); 20 Feb 2014 21:04:40 -0000
Received: from mail-wg0-f49.google.com (HELO mail-wg0-f49.google.com)
	(74.125.82.49)
	by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	20 Feb 2014 21:04:40 -0000
Received: by mail-wg0-f49.google.com with SMTP id y10so1872385wgg.4
	for ;
	Thu, 20 Feb 2014 13:04:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to;
	bh=qpicTVZrg/oVLctqCAhR3P8hHyxXA5GhrCCWEwqb1oQ=;
	b=h5JKg8vGxCdd/X4fsmEas4/xlhu9Av6+H/bMZDNODr55+QH7zpLgaoWBP14r/UD89N
	IzKLN8043o9KfA98E6KuAzDcv24AP9GLEJU3tpKgNFqXcpH/HIl+50VM43eUNvobQ5gk
	F2T3XMCFDwl7x9+zReKTCSZIMIkh0Wv4QED8I0dHhuB+Ri/8q9jwapP+9FsZh1Ozhvet
	chRKehqKtsVxjrCtSB2VQBQFSf9yGMlHpqJlqrlE40jy7I2eORMGdjUaGCGzipSkcMFm
	vIQ26OIuA4EbnTytwc7ae255P6Wrheo3yLlatjsRLvBsW5Ruo7NDxXmu6nY3/fAASm0J
	lYyQ==
X-Received: by 10.194.2.168 with SMTP id 8mr4105270wjv.8.1392930277780;
	Thu, 20 Feb 2014 13:04:37 -0800 (PST)
Received: from [192.168.0.6] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net.
	[213.106.112.122]) by mx.google.com with ESMTPSA id
	xt1sm11702107wjb.17.2014.02.20.13.04.33 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 20 Feb 2014 13:04:34 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Gazagnaire 
In-Reply-To: 
Date: Thu, 20 Feb 2014 21:04:32 +0000
Message-Id: <8C9B621C-A3F2-4EA1-B873-37E176728BEF@gazagnaire.org>
References: 
To: Amir Chaudhry 
X-Mailer: Apple Mail (2.1827)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Using Irminsule
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

> I've just gone through Thomas' Irminsule walkthough [1], and it's only now that Ive started to appreciate how useful this could be.  Is there somewhere I can begin using the git backend (would presumably help with bug reports)?  I know Thomas' going to be away so he can't answer this but I'm curious to hear if other folks have tried anything.

You can use the Git backend by either passing the `-g` option to `irmin init` or use the API directly, see https://github.com/samoht/irminsule/blob/master/examples/git_store.ml for instance.

Thomas


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 20 21:04:51 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 20 Feb 2014 21:04:51 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WGanU-0007bx-BK; Thu, 20 Feb 2014 21:04:44 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGanT-0007bs-3P
	for mirageos-devel@lists.xenproject.org; Thu, 20 Feb 2014 21:04:43 +0000
Received: from [85.158.137.68:53959] by server-6.bemta-3.messagelabs.com id
	8C/25-09180-9ED66035; Thu, 20 Feb 2014 21:04:41 +0000
X-Env-Sender: thomas.gazagnaire@gmail.com
X-Msg-Ref: server-13.tower-31.messagelabs.com!1392930280!1971276!1
X-Originating-IP: [74.125.82.49]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32088 invoked from network); 20 Feb 2014 21:04:40 -0000
Received: from mail-wg0-f49.google.com (HELO mail-wg0-f49.google.com)
	(74.125.82.49)
	by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	20 Feb 2014 21:04:40 -0000
Received: by mail-wg0-f49.google.com with SMTP id y10so1872385wgg.4
	for ;
	Thu, 20 Feb 2014 13:04:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to;
	bh=qpicTVZrg/oVLctqCAhR3P8hHyxXA5GhrCCWEwqb1oQ=;
	b=h5JKg8vGxCdd/X4fsmEas4/xlhu9Av6+H/bMZDNODr55+QH7zpLgaoWBP14r/UD89N
	IzKLN8043o9KfA98E6KuAzDcv24AP9GLEJU3tpKgNFqXcpH/HIl+50VM43eUNvobQ5gk
	F2T3XMCFDwl7x9+zReKTCSZIMIkh0Wv4QED8I0dHhuB+Ri/8q9jwapP+9FsZh1Ozhvet
	chRKehqKtsVxjrCtSB2VQBQFSf9yGMlHpqJlqrlE40jy7I2eORMGdjUaGCGzipSkcMFm
	vIQ26OIuA4EbnTytwc7ae255P6Wrheo3yLlatjsRLvBsW5Ruo7NDxXmu6nY3/fAASm0J
	lYyQ==
X-Received: by 10.194.2.168 with SMTP id 8mr4105270wjv.8.1392930277780;
	Thu, 20 Feb 2014 13:04:37 -0800 (PST)
Received: from [192.168.0.6] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net.
	[213.106.112.122]) by mx.google.com with ESMTPSA id
	xt1sm11702107wjb.17.2014.02.20.13.04.33 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 20 Feb 2014 13:04:34 -0800 (PST)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Thomas Gazagnaire 
In-Reply-To: 
Date: Thu, 20 Feb 2014 21:04:32 +0000
Message-Id: <8C9B621C-A3F2-4EA1-B873-37E176728BEF@gazagnaire.org>
References: 
To: Amir Chaudhry 
X-Mailer: Apple Mail (2.1827)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Using Irminsule
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

> I've just gone through Thomas' Irminsule walkthough [1], and it's only now that Ive started to appreciate how useful this could be.  Is there somewhere I can begin using the git backend (would presumably help with bug reports)?  I know Thomas' going to be away so he can't answer this but I'm curious to hear if other folks have tried anything.

You can use the Git backend by either passing the `-g` option to `irmin init` or use the API directly, see https://github.com/samoht/irminsule/blob/master/examples/git_store.ml for instance.

Thomas


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 10:11:36 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 10:11: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 1WGn4u-0006nG-2u; Fri, 21 Feb 2014 10:11:32 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGn4s-0006n3-ML
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 10:11:30 +0000
Received: from [85.158.137.68:49442] by server-13.bemta-3.messagelabs.com id
	EE/F0-26923-15627035; Fri, 21 Feb 2014 10:11:29 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-2.tower-31.messagelabs.com!1392977489!1769558!1
X-Originating-IP: [74.125.82.175]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32008 invoked from network); 21 Feb 2014 10:11:29 -0000
Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com)
	(74.125.82.175)
	by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	21 Feb 2014 10:11:29 -0000
Received: by mail-we0-f175.google.com with SMTP id q59so2398449wes.34
	for ;
	Fri, 21 Feb 2014 02:11:28 -0800 (PST)
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=yckXeBUpiMm6VD9toLVH077PDhRV+Xmn8780mzWEiy8=;
	b=h2MS4kB3146FYR/ZIDQ2jblpwT6VbzrDtZfAgVq7+eusZr1yPGdrsQKyHUPIqA+Xv2
	aXDEmdCyfdEPTeLfLIfdhvEIYkXBNag9zUGlIAKvbOzbQzlIGLysHfBMLSPWRohYcExt
	c1tH6IkzyMYOeRAVVT2md5/M/i1W1ImFF8byfxC6L6lnaDbOFVYeQi2qFVrxv54aPQkk
	irfOJFOZynXl+vny3zC43i01tVUHPk7g6IMZsLL2c42ns8/2nQkXIWWuRO6Bxx+dn8oW
	qtxcnBxXLDPOZkHwilqGZaGCe6edvIKwWiQAfAIU9EwrihhQutxFZ3DyUPFb/d+Pknde
	CQKw==
X-Received: by 10.194.175.66 with SMTP id by2mr5964193wjc.59.1392977488750;
	Fri, 21 Feb 2014 02:11:28 -0800 (PST)
Received: from [172.16.26.11] ([2.122.219.75])
	by mx.google.com with ESMTPSA id t6sm6415741wix.4.2014.02.21.02.11.27
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Fri, 21 Feb 2014 02:11:27 -0800 (PST)
Message-ID: <5307264E.5060108@xen.org>
Date: Fri, 21 Feb 2014 10:11:26 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Anil Madhavapeddy 
References: <5305E391.8020406@xen.org>
	
In-Reply-To: 
Cc: Russell Pavlicek ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 20/02/2014 11:45, Anil Madhavapeddy wrote:
> On 20 Feb 2014, at 11:14, Lars Kurth  wrote:
>
>> Guys,
>> when you spin out a new release, can you please coordinate with Russell and me
>> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
>> Regards
>> Lars
> Good point -- will do for future releases!
>
> -anil
>
Or we can re-label the 1.0 release 1.x ... As far as I understand OPAM 
picks up the latest versions anyway.
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 10:11:36 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 10:11: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 1WGn4u-0006nG-2u; Fri, 21 Feb 2014 10:11:32 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGn4s-0006n3-ML
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 10:11:30 +0000
Received: from [85.158.137.68:49442] by server-13.bemta-3.messagelabs.com id
	EE/F0-26923-15627035; Fri, 21 Feb 2014 10:11:29 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-2.tower-31.messagelabs.com!1392977489!1769558!1
X-Originating-IP: [74.125.82.175]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32008 invoked from network); 21 Feb 2014 10:11:29 -0000
Received: from mail-we0-f175.google.com (HELO mail-we0-f175.google.com)
	(74.125.82.175)
	by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	21 Feb 2014 10:11:29 -0000
Received: by mail-we0-f175.google.com with SMTP id q59so2398449wes.34
	for ;
	Fri, 21 Feb 2014 02:11:28 -0800 (PST)
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=yckXeBUpiMm6VD9toLVH077PDhRV+Xmn8780mzWEiy8=;
	b=h2MS4kB3146FYR/ZIDQ2jblpwT6VbzrDtZfAgVq7+eusZr1yPGdrsQKyHUPIqA+Xv2
	aXDEmdCyfdEPTeLfLIfdhvEIYkXBNag9zUGlIAKvbOzbQzlIGLysHfBMLSPWRohYcExt
	c1tH6IkzyMYOeRAVVT2md5/M/i1W1ImFF8byfxC6L6lnaDbOFVYeQi2qFVrxv54aPQkk
	irfOJFOZynXl+vny3zC43i01tVUHPk7g6IMZsLL2c42ns8/2nQkXIWWuRO6Bxx+dn8oW
	qtxcnBxXLDPOZkHwilqGZaGCe6edvIKwWiQAfAIU9EwrihhQutxFZ3DyUPFb/d+Pknde
	CQKw==
X-Received: by 10.194.175.66 with SMTP id by2mr5964193wjc.59.1392977488750;
	Fri, 21 Feb 2014 02:11:28 -0800 (PST)
Received: from [172.16.26.11] ([2.122.219.75])
	by mx.google.com with ESMTPSA id t6sm6415741wix.4.2014.02.21.02.11.27
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Fri, 21 Feb 2014 02:11:27 -0800 (PST)
Message-ID: <5307264E.5060108@xen.org>
Date: Fri, 21 Feb 2014 10:11:26 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Anil Madhavapeddy 
References: <5305E391.8020406@xen.org>
	
In-Reply-To: 
Cc: Russell Pavlicek ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 20/02/2014 11:45, Anil Madhavapeddy wrote:
> On 20 Feb 2014, at 11:14, Lars Kurth  wrote:
>
>> Guys,
>> when you spin out a new release, can you please coordinate with Russell and me
>> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
>> Regards
>> Lars
> Good point -- will do for future releases!
>
> -anil
>
Or we can re-label the 1.0 release 1.x ... As far as I understand OPAM 
picks up the latest versions anyway.
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 10:14:05 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 10:14:05 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WGn7N-0006si-Aw; Fri, 21 Feb 2014 10:14:05 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGn7L-0006sa-Gh
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 10:14:03 +0000
Received: from [85.158.137.68:15871] by server-17.bemta-3.messagelabs.com id
	1D/DA-22569-AE627035; Fri, 21 Feb 2014 10:14:02 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-16.tower-31.messagelabs.com!1392977641!2027285!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20151 invoked from network); 21 Feb 2014 10:14:02 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-16.tower-31.messagelabs.com with SMTP;
	21 Feb 2014 10:14:02 -0000
Received: (qmail 3951 invoked by uid 634); 21 Feb 2014 10:14:01 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.62]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Fri, 21 Feb 2014 10:14:01 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <5307264E.5060108@xen.org>
Date: Fri, 21 Feb 2014 10:13:58 +0000
Message-Id: 
References: <5305E391.8020406@xen.org>
	
	<5307264E.5060108@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Russell Pavlicek ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 21 Feb 2014, at 10:11, Lars Kurth  wrote:

> On 20/02/2014 11:45, Anil Madhavapeddy wrote:
>> On 20 Feb 2014, at 11:14, Lars Kurth  wrote:
>> 
>>> Guys,
>>> when you spin out a new release, can you please coordinate with Russell and me
>>> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
>>> Regards
>>> Lars
>> Good point -- will do for future releases!
>> 
>> -anil
>> 
> Or we can re-label the 1.0 release 1.x ... As far as I understand OPAM picks up the latest versions anyway.
> Lar

That's right -- although older versions can still be installed by manually picking the right version number.  We're likely to release a point release 1.1.1 shortly as well, so it could just be 1.1.x to signify that the user should just get the latest point release via OPAM.

-anil


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 10:14:05 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 10:14:05 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WGn7N-0006si-Aw; Fri, 21 Feb 2014 10:14:05 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGn7L-0006sa-Gh
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 10:14:03 +0000
Received: from [85.158.137.68:15871] by server-17.bemta-3.messagelabs.com id
	1D/DA-22569-AE627035; Fri, 21 Feb 2014 10:14:02 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-16.tower-31.messagelabs.com!1392977641!2027285!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20151 invoked from network); 21 Feb 2014 10:14:02 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-16.tower-31.messagelabs.com with SMTP;
	21 Feb 2014 10:14:02 -0000
Received: (qmail 3951 invoked by uid 634); 21 Feb 2014 10:14:01 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.62]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Fri, 21 Feb 2014 10:14:01 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <5307264E.5060108@xen.org>
Date: Fri, 21 Feb 2014 10:13:58 +0000
Message-Id: 
References: <5305E391.8020406@xen.org>
	
	<5307264E.5060108@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Russell Pavlicek ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 21 Feb 2014, at 10:11, Lars Kurth  wrote:

> On 20/02/2014 11:45, Anil Madhavapeddy wrote:
>> On 20 Feb 2014, at 11:14, Lars Kurth  wrote:
>> 
>>> Guys,
>>> when you spin out a new release, can you please coordinate with Russell and me
>>> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
>>> Regards
>>> Lars
>> Good point -- will do for future releases!
>> 
>> -anil
>> 
> Or we can re-label the 1.0 release 1.x ... As far as I understand OPAM picks up the latest versions anyway.
> Lar

That's right -- although older versions can still be installed by manually picking the right version number.  We're likely to release a point release 1.1.1 shortly as well, so it could just be 1.1.x to signify that the user should just get the latest point release via OPAM.

-anil


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 12:54:21 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 12:54: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 1WGpcN-0005BK-Lq; Fri, 21 Feb 2014 12:54:15 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGpcM-0005BF-4K
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 12:54:14 +0000
Received: from [85.158.139.211:61818] by server-13.bemta-5.messagelabs.com id
	8B/88-18801-57C47035; Fri, 21 Feb 2014 12:54:13 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-2.tower-206.messagelabs.com!1392987252!5380588!1
X-Originating-IP: [131.111.8.133]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32520 invoked from network); 21 Feb 2014 12:54:12 -0000
Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk)
	(131.111.8.133)
	by server-2.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 21 Feb 2014 12:54:12 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from host86-166-232-127.range86-166.btcentralplus.com
	([86.166.232.127]:58113 helo=[192.168.1.93])
	by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WGpcJ-0003dR-hD (Exim 4.82_3-c0e5623)
	(return-path ); Fri, 21 Feb 2014 12:54:11 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: 
Date: Fri, 21 Feb 2014 12:54:10 +0000
Message-Id: <85A78109-A12C-4806-BE9D-FB9FA7CE98F4@cam.ac.uk>
References: <5305E391.8020406@xen.org>
	
	<5307264E.5060108@xen.org>
	
To: Russell Pavlicek ,
	Lars Kurth 
X-Mailer: Apple Mail (2.1510)
Cc: mirageos-devel@lists.xenproject.org, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 21 Feb 2014, at 10:13, Anil Madhavapeddy  wrote:

> On 21 Feb 2014, at 10:11, Lars Kurth  wrote:
> 
>> On 20/02/2014 11:45, Anil Madhavapeddy wrote:
>>> On 20 Feb 2014, at 11:14, Lars Kurth  wrote:
>>> 
>>>> Guys,
>>>> when you spin out a new release, can you please coordinate with Russell and me
>>>> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
>>>> Regards
>>>> Lars
>>> Good point -- will do for future releases!
>>> 
>>> -anil
>>> 
>> Or we can re-label the 1.0 release 1.x ... As far as I understand OPAM picks up the latest versions anyway.
>> Lar
> 
> That's right -- although older versions can still be installed by manually picking the right version number.  We're likely to release a point release 1.1.1 shortly as well, so it could just be 1.1.x to signify that the user should just get the latest point release via OPAM.


My inclination is to stick with 1.x.x.  It makes the most sense for now (e.g. the getting started instructions would be different and it's unhelpful to users to maintain both).

Since I don't have edit access [1], Russell, Lars, are you able to make the following changes the text on the following page:
http://xenproject.org/downloads/mirage-os-archives/mirage-os-10.html

Title: Mirage 1.x.x  (URL can stay as it is)

MirageOS v1.0 consists of a set of libraries -> MirageOS v1.x.x consists of a set of libraries

look at the [Mirage Introduction] on -> look at the [Mirage Docs][2] on

and what the libraries enable you to do. -> and what the libraries enable you to do. You should also read the announcement post for the [original 1.0 release][3], which provides useful background.

[1] I asked before but apparently the downloads part of the CMS is awkward so I can't do this myself (c.f email from Lars on 5 Dec @ 2230-ish)

[2] link should be http://openmirage.org/docs/

[3] link should be http://openmirage.org/blog/announcing-mirage10


I hope that all makes sense.

Amir
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 12:54:21 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 12:54: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 1WGpcN-0005BK-Lq; Fri, 21 Feb 2014 12:54:15 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGpcM-0005BF-4K
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 12:54:14 +0000
Received: from [85.158.139.211:61818] by server-13.bemta-5.messagelabs.com id
	8B/88-18801-57C47035; Fri, 21 Feb 2014 12:54:13 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-2.tower-206.messagelabs.com!1392987252!5380588!1
X-Originating-IP: [131.111.8.133]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32520 invoked from network); 21 Feb 2014 12:54:12 -0000
Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk)
	(131.111.8.133)
	by server-2.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 21 Feb 2014 12:54:12 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from host86-166-232-127.range86-166.btcentralplus.com
	([86.166.232.127]:58113 helo=[192.168.1.93])
	by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WGpcJ-0003dR-hD (Exim 4.82_3-c0e5623)
	(return-path ); Fri, 21 Feb 2014 12:54:11 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: 
Date: Fri, 21 Feb 2014 12:54:10 +0000
Message-Id: <85A78109-A12C-4806-BE9D-FB9FA7CE98F4@cam.ac.uk>
References: <5305E391.8020406@xen.org>
	
	<5307264E.5060108@xen.org>
	
To: Russell Pavlicek ,
	Lars Kurth 
X-Mailer: Apple Mail (2.1510)
Cc: mirageos-devel@lists.xenproject.org, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 21 Feb 2014, at 10:13, Anil Madhavapeddy  wrote:

> On 21 Feb 2014, at 10:11, Lars Kurth  wrote:
> 
>> On 20/02/2014 11:45, Anil Madhavapeddy wrote:
>>> On 20 Feb 2014, at 11:14, Lars Kurth  wrote:
>>> 
>>>> Guys,
>>>> when you spin out a new release, can you please coordinate with Russell and me
>>>> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
>>>> Regards
>>>> Lars
>>> Good point -- will do for future releases!
>>> 
>>> -anil
>>> 
>> Or we can re-label the 1.0 release 1.x ... As far as I understand OPAM picks up the latest versions anyway.
>> Lar
> 
> That's right -- although older versions can still be installed by manually picking the right version number.  We're likely to release a point release 1.1.1 shortly as well, so it could just be 1.1.x to signify that the user should just get the latest point release via OPAM.


My inclination is to stick with 1.x.x.  It makes the most sense for now (e.g. the getting started instructions would be different and it's unhelpful to users to maintain both).

Since I don't have edit access [1], Russell, Lars, are you able to make the following changes the text on the following page:
http://xenproject.org/downloads/mirage-os-archives/mirage-os-10.html

Title: Mirage 1.x.x  (URL can stay as it is)

MirageOS v1.0 consists of a set of libraries -> MirageOS v1.x.x consists of a set of libraries

look at the [Mirage Introduction] on -> look at the [Mirage Docs][2] on

and what the libraries enable you to do. -> and what the libraries enable you to do. You should also read the announcement post for the [original 1.0 release][3], which provides useful background.

[1] I asked before but apparently the downloads part of the CMS is awkward so I can't do this myself (c.f email from Lars on 5 Dec @ 2230-ish)

[2] link should be http://openmirage.org/docs/

[3] link should be http://openmirage.org/blog/announcing-mirage10


I hope that all makes sense.

Amir
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 13:06:52 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 13:06: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 1WGpoY-0005uX-EY; Fri, 21 Feb 2014 13:06:50 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGpoW-0005uF-L7
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 13:06:48 +0000
Received: from [85.158.143.35:21328] by server-1.bemta-4.messagelabs.com id
	B6/FC-31661-76F47035; Fri, 21 Feb 2014 13:06:47 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-14.tower-21.messagelabs.com!1392988007!7370491!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8404 invoked from network); 21 Feb 2014 13:06:47 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-14.tower-21.messagelabs.com with SMTP;
	21 Feb 2014 13:06:47 -0000
Received: (qmail 15274 invoked by uid 634); 21 Feb 2014 13:06:46 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.62]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Fri, 21 Feb 2014 13:06:46 +0000
From: Anil Madhavapeddy 
Message-Id: <3383A1B2-F260-499E-B2F2-BF194E250A54@recoil.org>
Date: Fri, 21 Feb 2014 13:06:49 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] headsup: stackv4 change soon
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

When preparing the functorized network stack (the `STACKV4` module type), I missed out on exposing a way to obtain a UDPv4 or TCPv4 handle.  This is necessary to transmit new packets, and was missed because all our existing skeletons only ever respond to server requests!

On the bright side, the fix is really tiny [1], but does require a mirage-types-1.1.1 and tcpip-1.1.1 release [2].  I'll cut those today and upload them to OPAM.  Most of you should just need to `opam update -u`, but if you have stuff pinned it could break until you refresh your local copies.

In return for this upgrade, we will shortly have working DNS resolvers [3], which will in turn let us have a working HTTP client (which needs to resolve names in order to connect).  Yay!  Examples have been updated with a DNS skeleton too [4].  All of this continues to work fine with all the combinations (socket vs direct stacks in particular).

[1] https://github.com/mirage/mirage/pull/227
[2] https://github.com/mirage/mirage-tcpip/pull/47
[3] https://github.com/mirage/ocaml-dns/pull/11
[4] https://github.com/mirage/mirage-skeleton/pull/31

-anil




_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 13:06:52 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 13:06: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 1WGpoY-0005uX-EY; Fri, 21 Feb 2014 13:06:50 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGpoW-0005uF-L7
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 13:06:48 +0000
Received: from [85.158.143.35:21328] by server-1.bemta-4.messagelabs.com id
	B6/FC-31661-76F47035; Fri, 21 Feb 2014 13:06:47 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-14.tower-21.messagelabs.com!1392988007!7370491!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8404 invoked from network); 21 Feb 2014 13:06:47 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-14.tower-21.messagelabs.com with SMTP;
	21 Feb 2014 13:06:47 -0000
Received: (qmail 15274 invoked by uid 634); 21 Feb 2014 13:06:46 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.62]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Fri, 21 Feb 2014 13:06:46 +0000
From: Anil Madhavapeddy 
Message-Id: <3383A1B2-F260-499E-B2F2-BF194E250A54@recoil.org>
Date: Fri, 21 Feb 2014 13:06:49 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] headsup: stackv4 change soon
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

When preparing the functorized network stack (the `STACKV4` module type), I missed out on exposing a way to obtain a UDPv4 or TCPv4 handle.  This is necessary to transmit new packets, and was missed because all our existing skeletons only ever respond to server requests!

On the bright side, the fix is really tiny [1], but does require a mirage-types-1.1.1 and tcpip-1.1.1 release [2].  I'll cut those today and upload them to OPAM.  Most of you should just need to `opam update -u`, but if you have stuff pinned it could break until you refresh your local copies.

In return for this upgrade, we will shortly have working DNS resolvers [3], which will in turn let us have a working HTTP client (which needs to resolve names in order to connect).  Yay!  Examples have been updated with a DNS skeleton too [4].  All of this continues to work fine with all the combinations (socket vs direct stacks in particular).

[1] https://github.com/mirage/mirage/pull/227
[2] https://github.com/mirage/mirage-tcpip/pull/47
[3] https://github.com/mirage/ocaml-dns/pull/11
[4] https://github.com/mirage/mirage-skeleton/pull/31

-anil




_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 15:32:11 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 15:32: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 1WGs58-0004Sb-PH; Fri, 21 Feb 2014 15:32:06 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGs47-0004RZ-Jb
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 15:31:05 +0000
Received: from [85.158.139.211:51976] by server-11.bemta-5.messagelabs.com id
	96/D2-23886-63177035; Fri, 21 Feb 2014 15:31:02 +0000
X-Env-Sender: russell.pavlicek@citrix.com
X-Msg-Ref: server-3.tower-206.messagelabs.com!1392996660!5469357!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3047 invoked from network); 21 Feb 2014 15:31:01 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	21 Feb 2014 15:31:01 -0000
X-IronPort-AV: E=Sophos;i="4.97,519,1389744000"; d="scan'208";a="104699713"
Received: from sjcpex01cl02.citrite.net ([10.216.14.144])
	by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA;
	21 Feb 2014 15:30:59 +0000
Received: from SJCPEX01CL03.citrite.net ([169.254.3.247]) by
	SJCPEX01CL02.citrite.net ([10.216.14.144]) with mapi id 14.02.0342.004;
	Fri, 21 Feb 2014 07:30:58 -0800
From: Russell Pavlicek 
To: Amir Chaudhry , Lars Kurth 
Thread-Topic: [MirageOS-devel] Mirage OS releases and XenProject.org
Thread-Index: AQHPLi0JXYvraR9BZ0y1eXHCN1A685q+jD8AgAF4EgCAAAC1AIAALMIA//+lU/Q=
Date: Fri, 21 Feb 2014 15:30:58 +0000
Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA2185BE2@SJCPEX01CL03.citrite.net>
References: <5305E391.8020406@xen.org>
	
	<5307264E.5060108@xen.org>
	,
	<85A78109-A12C-4806-BE9D-FB9FA7CE98F4@cam.ac.uk>
In-Reply-To: <85A78109-A12C-4806-BE9D-FB9FA7CE98F4@cam.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.13.112.14]
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 21 Feb 2014 15:32:05 +0000
Cc: "mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Amir,

Thanks for the changes.  I will look into it, although it may be Monday before it happens.  At SCALE 12X right now and the Internet is pretty flaky.

Russ Pavlicek
Xen Project Evangelist, Citrix Systems
Home Office: +1-301-829-5327
Mobile: +1-240-397-0199
UK VoIP: +44 1223 852 894
________________________________________
From: Amir Chaudhry [amc79@cam.ac.uk]
Sent: Friday, February 21, 2014 7:54 AM
To: Russell Pavlicek; Lars Kurth
Cc: mirageos-devel@lists.xenproject.org; Anil Madhavapeddy
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org

On 21 Feb 2014, at 10:13, Anil Madhavapeddy  wrote:

> On 21 Feb 2014, at 10:11, Lars Kurth  wrote:
>
>> On 20/02/2014 11:45, Anil Madhavapeddy wrote:
>>> On 20 Feb 2014, at 11:14, Lars Kurth  wrote:
>>>
>>>> Guys,
>>>> when you spin out a new release, can you please coordinate with Russell and me
>>>> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
>>>> Regards
>>>> Lars
>>> Good point -- will do for future releases!
>>>
>>> -anil
>>>
>> Or we can re-label the 1.0 release 1.x ... As far as I understand OPAM picks up the latest versions anyway.
>> Lar
>
> That's right -- although older versions can still be installed by manually picking the right version number.  We're likely to release a point release 1.1.1 shortly as well, so it could just be 1.1.x to signify that the user should just get the latest point release via OPAM.


My inclination is to stick with 1.x.x.  It makes the most sense for now (e.g. the getting started instructions would be different and it's unhelpful to users to maintain both).

Since I don't have edit access [1], Russell, Lars, are you able to make the following changes the text on the following page:
http://xenproject.org/downloads/mirage-os-archives/mirage-os-10.html

Title: Mirage 1.x.x  (URL can stay as it is)

MirageOS v1.0 consists of a set of libraries -> MirageOS v1.x.x consists of a set of libraries

look at the [Mirage Introduction] on -> look at the [Mirage Docs][2] on

and what the libraries enable you to do. -> and what the libraries enable you to do. You should also read the announcement post for the [original 1.0 release][3], which provides useful background.

[1] I asked before but apparently the downloads part of the CMS is awkward so I can't do this myself (c.f email from Lars on 5 Dec @ 2230-ish)

[2] link should be http://openmirage.org/docs/

[3] link should be http://openmirage.org/blog/announcing-mirage10


I hope that all makes sense.

Amir

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 15:32:11 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 15:32: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 1WGs58-0004Sb-PH; Fri, 21 Feb 2014 15:32:06 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGs47-0004RZ-Jb
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 15:31:05 +0000
Received: from [85.158.139.211:51976] by server-11.bemta-5.messagelabs.com id
	96/D2-23886-63177035; Fri, 21 Feb 2014 15:31:02 +0000
X-Env-Sender: russell.pavlicek@citrix.com
X-Msg-Ref: server-3.tower-206.messagelabs.com!1392996660!5469357!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3047 invoked from network); 21 Feb 2014 15:31:01 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	21 Feb 2014 15:31:01 -0000
X-IronPort-AV: E=Sophos;i="4.97,519,1389744000"; d="scan'208";a="104699713"
Received: from sjcpex01cl02.citrite.net ([10.216.14.144])
	by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA;
	21 Feb 2014 15:30:59 +0000
Received: from SJCPEX01CL03.citrite.net ([169.254.3.247]) by
	SJCPEX01CL02.citrite.net ([10.216.14.144]) with mapi id 14.02.0342.004;
	Fri, 21 Feb 2014 07:30:58 -0800
From: Russell Pavlicek 
To: Amir Chaudhry , Lars Kurth 
Thread-Topic: [MirageOS-devel] Mirage OS releases and XenProject.org
Thread-Index: AQHPLi0JXYvraR9BZ0y1eXHCN1A685q+jD8AgAF4EgCAAAC1AIAALMIA//+lU/Q=
Date: Fri, 21 Feb 2014 15:30:58 +0000
Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA2185BE2@SJCPEX01CL03.citrite.net>
References: <5305E391.8020406@xen.org>
	
	<5307264E.5060108@xen.org>
	,
	<85A78109-A12C-4806-BE9D-FB9FA7CE98F4@cam.ac.uk>
In-Reply-To: <85A78109-A12C-4806-BE9D-FB9FA7CE98F4@cam.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.13.112.14]
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 21 Feb 2014 15:32:05 +0000
Cc: "mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Amir,

Thanks for the changes.  I will look into it, although it may be Monday before it happens.  At SCALE 12X right now and the Internet is pretty flaky.

Russ Pavlicek
Xen Project Evangelist, Citrix Systems
Home Office: +1-301-829-5327
Mobile: +1-240-397-0199
UK VoIP: +44 1223 852 894
________________________________________
From: Amir Chaudhry [amc79@cam.ac.uk]
Sent: Friday, February 21, 2014 7:54 AM
To: Russell Pavlicek; Lars Kurth
Cc: mirageos-devel@lists.xenproject.org; Anil Madhavapeddy
Subject: Re: [MirageOS-devel] Mirage OS releases and XenProject.org

On 21 Feb 2014, at 10:13, Anil Madhavapeddy  wrote:

> On 21 Feb 2014, at 10:11, Lars Kurth  wrote:
>
>> On 20/02/2014 11:45, Anil Madhavapeddy wrote:
>>> On 20 Feb 2014, at 11:14, Lars Kurth  wrote:
>>>
>>>> Guys,
>>>> when you spin out a new release, can you please coordinate with Russell and me
>>>> If I look at  http://xenproject.org/developers/teams/mirage-os.html andhttp://xenproject.org/downloads/mirage-os-archives.html these are now out-of-date
>>>> Regards
>>>> Lars
>>> Good point -- will do for future releases!
>>>
>>> -anil
>>>
>> Or we can re-label the 1.0 release 1.x ... As far as I understand OPAM picks up the latest versions anyway.
>> Lar
>
> That's right -- although older versions can still be installed by manually picking the right version number.  We're likely to release a point release 1.1.1 shortly as well, so it could just be 1.1.x to signify that the user should just get the latest point release via OPAM.


My inclination is to stick with 1.x.x.  It makes the most sense for now (e.g. the getting started instructions would be different and it's unhelpful to users to maintain both).

Since I don't have edit access [1], Russell, Lars, are you able to make the following changes the text on the following page:
http://xenproject.org/downloads/mirage-os-archives/mirage-os-10.html

Title: Mirage 1.x.x  (URL can stay as it is)

MirageOS v1.0 consists of a set of libraries -> MirageOS v1.x.x consists of a set of libraries

look at the [Mirage Introduction] on -> look at the [Mirage Docs][2] on

and what the libraries enable you to do. -> and what the libraries enable you to do. You should also read the announcement post for the [original 1.0 release][3], which provides useful background.

[1] I asked before but apparently the downloads part of the CMS is awkward so I can't do this myself (c.f email from Lars on 5 Dec @ 2230-ish)

[2] link should be http://openmirage.org/docs/

[3] link should be http://openmirage.org/blog/announcing-mirage10


I hope that all makes sense.

Amir

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 16:15:51 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 16:15:51 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WGslR-0006iY-Il; Fri, 21 Feb 2014 16:15:49 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGslQ-0006iT-6J
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 16:15:48 +0000
Received: from [85.158.139.211:53420] by server-8.bemta-5.messagelabs.com id
	C6/CB-05298-3BB77035; Fri, 21 Feb 2014 16:15:47 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-11.tower-206.messagelabs.com!1392999346!920720!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2526 invoked from network); 21 Feb 2014 16:15:46 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-11.tower-206.messagelabs.com with SMTP;
	21 Feb 2014 16:15:46 -0000
Received: (qmail 930 invoked by uid 634); 21 Feb 2014 16:15:46 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.62]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Fri, 21 Feb 2014 16:15:45 +0000
From: Anil Madhavapeddy 
Message-Id: <938C35DF-3323-49C6-AAFB-F1F80308D953@recoil.org>
Date: Fri, 21 Feb 2014 16:15:44 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] mirage-1.1.1 released
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

I just merged the 1.1.1 release with the aforementioned incompatibilities fixed, and a few other bug fixes.  I'll do a blog post when I get the mirage-dns library done.

Changelogs:

mirage.1.1.1 (2014-02-21):
* Man page fixes for typos and terminology (#220).
* Activate backtrace recording by default (#225).
* Fixes in the `V1.STACKV4` to expose UDPv4/TCPv4 types properly (#226).

cstruct.1.1.0 (2014-02-19)
* Improve bounds checks on sub, shift, set_len, add_len.
* Add `to_bigarray` to convert back into a Bigarray slice.

dns.0.8.0 (2014-02-21):
* Use `Ipaddr.V6` to restore IPv6/AAAA RR support.
* `process_query` now takes an output buffer so it doesn't have to
  overwrite the input buffer it just parsed.
* Add Travis continuous integration scripts.
* Regenerate with OASIS 0.4.1
* Split the `dns.lwt` into a portable `dns.lwt-core` that doesn't
  require Unix (from which a Mirage version can be built).  The only
  change to existing applications is that Unix-specific functions
  have shifted into `Dns_resolver_unix` or `Dns_server_unix`, with
  the module types for `PROCESSOR` and `CLIENT` unchanged.

tcpip.1.1.1 (21-February-2013):
* Catch and ignore top-level socket exceptions (#219).
* Set `SO_REUSEADDR` on listening sockets for Unix (#218).
* Adapt the Stack interfaces to the v1.1.1 mirage-types interface
  (see mirage/mirage#226 for details).

Mirage-skeleton also has a new dns/ directory with a skeleton
app (that is overly complicated for now until its logic gets pulled
into a library, but it does serve DNS traffic :)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 16:15:51 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 16:15:51 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WGslR-0006iY-Il; Fri, 21 Feb 2014 16:15:49 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGslQ-0006iT-6J
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 16:15:48 +0000
Received: from [85.158.139.211:53420] by server-8.bemta-5.messagelabs.com id
	C6/CB-05298-3BB77035; Fri, 21 Feb 2014 16:15:47 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-11.tower-206.messagelabs.com!1392999346!920720!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2526 invoked from network); 21 Feb 2014 16:15:46 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-11.tower-206.messagelabs.com with SMTP;
	21 Feb 2014 16:15:46 -0000
Received: (qmail 930 invoked by uid 634); 21 Feb 2014 16:15:46 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.62]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Fri, 21 Feb 2014 16:15:45 +0000
From: Anil Madhavapeddy 
Message-Id: <938C35DF-3323-49C6-AAFB-F1F80308D953@recoil.org>
Date: Fri, 21 Feb 2014 16:15:44 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] mirage-1.1.1 released
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

I just merged the 1.1.1 release with the aforementioned incompatibilities fixed, and a few other bug fixes.  I'll do a blog post when I get the mirage-dns library done.

Changelogs:

mirage.1.1.1 (2014-02-21):
* Man page fixes for typos and terminology (#220).
* Activate backtrace recording by default (#225).
* Fixes in the `V1.STACKV4` to expose UDPv4/TCPv4 types properly (#226).

cstruct.1.1.0 (2014-02-19)
* Improve bounds checks on sub, shift, set_len, add_len.
* Add `to_bigarray` to convert back into a Bigarray slice.

dns.0.8.0 (2014-02-21):
* Use `Ipaddr.V6` to restore IPv6/AAAA RR support.
* `process_query` now takes an output buffer so it doesn't have to
  overwrite the input buffer it just parsed.
* Add Travis continuous integration scripts.
* Regenerate with OASIS 0.4.1
* Split the `dns.lwt` into a portable `dns.lwt-core` that doesn't
  require Unix (from which a Mirage version can be built).  The only
  change to existing applications is that Unix-specific functions
  have shifted into `Dns_resolver_unix` or `Dns_server_unix`, with
  the module types for `PROCESSOR` and `CLIENT` unchanged.

tcpip.1.1.1 (21-February-2013):
* Catch and ignore top-level socket exceptions (#219).
* Set `SO_REUSEADDR` on listening sockets for Unix (#218).
* Adapt the Stack interfaces to the v1.1.1 mirage-types interface
  (see mirage/mirage#226 for details).

Mirage-skeleton also has a new dns/ directory with a skeleton
app (that is overly complicated for now until its logic gets pulled
into a library, but it does serve DNS traffic :)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 18:59:04 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 18:59: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 1WGvJL-0004kX-Qp; Fri, 21 Feb 2014 18:58:59 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGvJJ-0004kS-UL
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 18:58:58 +0000
Received: from [85.158.137.68:63855] by server-4.bemta-3.messagelabs.com id
	D5/A2-04858-1F1A7035; Fri, 21 Feb 2014 18:58:57 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-2.tower-31.messagelabs.com!1393009136!64005!1
X-Originating-IP: [209.85.212.181]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29797 invoked from network); 21 Feb 2014 18:58:56 -0000
Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com)
	(209.85.212.181)
	by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	21 Feb 2014 18:58:56 -0000
Received: by mail-wi0-f181.google.com with SMTP id hi5so1163690wib.14
	for ;
	Fri, 21 Feb 2014 10:58:55 -0800 (PST)
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:content-type:content-transfer-encoding;
	bh=N5Xyf6KxWNs5KXIfe+etmHbi4X1nuzT0xHDU/vL7tNs=;
	b=yd/0yVFgw/G1pVfdaykaWAG3+1oFdLd7d1zTpOHHOytpGRENruOVcPijwhmKr8jnQG
	aaSrArlUaqEM0DMdr7HeiHT3Qus6mPaR0Q81Gxg3fBHas0dZS7YYdzmaEGt/nF8bNNpM
	yFuhU9uXVo8mM3vu7W+nk7cXeNgQiluHEIFumadHVzGyqzLN3ryse55mhkHIr1/Hpscm
	ATkHQbtnsyEF7PO8a17wBGNEjDyNdehFAD4KoVdi6GJiKgykFyHQL+mgcqj9+oksVkqg
	3cAPitZANfNefecgA+ZmXRG1npFEuJp0jkrutm8fvd9WczMD02yNVYtM79lfRK240Zo2
	5wtg==
X-Received: by 10.194.175.202 with SMTP id cc10mr8596193wjc.48.1393009135737; 
	Fri, 21 Feb 2014 10:58:55 -0800 (PST)
Received: from [172.16.26.11] ([2.122.219.75])
	by mx.google.com with ESMTPSA id fb8sm10143506wic.3.2014.02.21.10.58.54
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Fri, 21 Feb 2014 10:58:54 -0800 (PST)
Message-ID: <5307A1ED.3020207@xen.org>
Date: Fri, 21 Feb 2014 18:58:53 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "mirageos-devel@lists.xenproject.org" 
Cc: George Dunlap 
Subject: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi,
can you tell us what the memory requirements of a typical Mirage OS VM 
are. If you have visibility of size needs of HalVM, ErlangOnXen, ... 
that would be helpful too
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 21 18:59:04 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 21 Feb 2014 18:59: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 1WGvJL-0004kX-Qp; Fri, 21 Feb 2014 18:58:59 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WGvJJ-0004kS-UL
	for mirageos-devel@lists.xenproject.org; Fri, 21 Feb 2014 18:58:58 +0000
Received: from [85.158.137.68:63855] by server-4.bemta-3.messagelabs.com id
	D5/A2-04858-1F1A7035; Fri, 21 Feb 2014 18:58:57 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-2.tower-31.messagelabs.com!1393009136!64005!1
X-Originating-IP: [209.85.212.181]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29797 invoked from network); 21 Feb 2014 18:58:56 -0000
Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com)
	(209.85.212.181)
	by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	21 Feb 2014 18:58:56 -0000
Received: by mail-wi0-f181.google.com with SMTP id hi5so1163690wib.14
	for ;
	Fri, 21 Feb 2014 10:58:55 -0800 (PST)
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:content-type:content-transfer-encoding;
	bh=N5Xyf6KxWNs5KXIfe+etmHbi4X1nuzT0xHDU/vL7tNs=;
	b=yd/0yVFgw/G1pVfdaykaWAG3+1oFdLd7d1zTpOHHOytpGRENruOVcPijwhmKr8jnQG
	aaSrArlUaqEM0DMdr7HeiHT3Qus6mPaR0Q81Gxg3fBHas0dZS7YYdzmaEGt/nF8bNNpM
	yFuhU9uXVo8mM3vu7W+nk7cXeNgQiluHEIFumadHVzGyqzLN3ryse55mhkHIr1/Hpscm
	ATkHQbtnsyEF7PO8a17wBGNEjDyNdehFAD4KoVdi6GJiKgykFyHQL+mgcqj9+oksVkqg
	3cAPitZANfNefecgA+ZmXRG1npFEuJp0jkrutm8fvd9WczMD02yNVYtM79lfRK240Zo2
	5wtg==
X-Received: by 10.194.175.202 with SMTP id cc10mr8596193wjc.48.1393009135737; 
	Fri, 21 Feb 2014 10:58:55 -0800 (PST)
Received: from [172.16.26.11] ([2.122.219.75])
	by mx.google.com with ESMTPSA id fb8sm10143506wic.3.2014.02.21.10.58.54
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Fri, 21 Feb 2014 10:58:54 -0800 (PST)
Message-ID: <5307A1ED.3020207@xen.org>
Date: Fri, 21 Feb 2014 18:58:53 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "mirageos-devel@lists.xenproject.org" 
Cc: George Dunlap 
Subject: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi,
can you tell us what the memory requirements of a typical Mirage OS VM 
are. If you have visibility of size needs of HalVM, ErlangOnXen, ... 
that would be helpful too
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 22 11:41:53 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 22 Feb 2014 11:41: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 1WHAxo-0001cj-AY; Sat, 22 Feb 2014 11:41:48 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WHAxn-0001ca-75
	for mirageos-devel@lists.xenproject.org; Sat, 22 Feb 2014 11:41:47 +0000
Received: from [85.158.139.211:64442] by server-2.bemta-5.messagelabs.com id
	51/7D-23037-AFC88035; Sat, 22 Feb 2014 11:41:46 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-3.tower-206.messagelabs.com!1393069305!5580155!1
X-Originating-IP: [195.62.217.152]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTIgPT4gMTY3OTY=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16090 invoked from network); 22 Feb 2014 11:41:45 -0000
Received: from engine04-20433-4.icritical.com (HELO
	engine04-20433-4.icritical.com) (195.62.217.152)
	by server-3.tower-206.messagelabs.com with SMTP;
	22 Feb 2014 11:41:45 -0000
Received: (qmail 11338 invoked from network); 22 Feb 2014 11:41:39 -0000
Received: from localhost (127.0.0.1)
	by engine04-20433-4.icritical.com with SMTP; 22 Feb 2014 11:41:39 -0000
Received: from engine04-20433-4.icritical.com ([127.0.0.1])
	by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 09198-06 for ;
	Sat, 22 Feb 2014 11:41:38 +0000 (GMT)
Received: (qmail 11319 invoked by uid 599); 22 Feb 2014 11:41:37 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP;
	Sat, 22 Feb 2014 11:41:37 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WHAxi-0005v6-7v; Sat, 22 Feb 2014 11:41:42 +0000
From: Richard Mortier 
To: "lars.kurth@xen.org" 
Date: Sat, 22 Feb 2014 11:41:41 +0000
Thread-Topic: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
Thread-Index: Ac8vww31eFNiIM7aQfWH4ULXJKdr2Q==
Message-ID: <3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
References: <5307A1ED.3020207@xen.org>
In-Reply-To: <5307A1ED.3020207@xen.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 21 Feb 2014, at 18:58, Lars Kurth  wrote:

> can you tell us what the memory requirements of a typical Mirage OS VM 
> are.

er, define typical... :)

there are some figures on memory footprint (now perhaps a little outdated) in the mirage ASPLOS'13 paper. the latest xen image in the mirage-www-deployment repo looks like ~2.5MB for the entire http://openmirage.org website.

> If you have visibility of size needs of HalVM, ErlangOnXen, ... 
> that would be helpful too

sorry, i don't, don't know if anyone else does.

fwiw i've a 3rd year undergrad project student (sam williams) at the moment who's putting erlang on xen directly (ie., not using ErlangOnXen). i expect it will be open source when released (though that's up to him). the student has already released some of his early prototypes, including moo and lisp -- https://github.com/samcamwilliams/moo-on-xen and https://github.com/samcamwilliams/lisp-on-xen. i expect he'll get some figures on memory footprint when he writes his dissertation.

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 22 11:41:53 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 22 Feb 2014 11:41: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 1WHAxo-0001cj-AY; Sat, 22 Feb 2014 11:41:48 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WHAxn-0001ca-75
	for mirageos-devel@lists.xenproject.org; Sat, 22 Feb 2014 11:41:47 +0000
Received: from [85.158.139.211:64442] by server-2.bemta-5.messagelabs.com id
	51/7D-23037-AFC88035; Sat, 22 Feb 2014 11:41:46 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-3.tower-206.messagelabs.com!1393069305!5580155!1
X-Originating-IP: [195.62.217.152]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTIgPT4gMTY3OTY=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16090 invoked from network); 22 Feb 2014 11:41:45 -0000
Received: from engine04-20433-4.icritical.com (HELO
	engine04-20433-4.icritical.com) (195.62.217.152)
	by server-3.tower-206.messagelabs.com with SMTP;
	22 Feb 2014 11:41:45 -0000
Received: (qmail 11338 invoked from network); 22 Feb 2014 11:41:39 -0000
Received: from localhost (127.0.0.1)
	by engine04-20433-4.icritical.com with SMTP; 22 Feb 2014 11:41:39 -0000
Received: from engine04-20433-4.icritical.com ([127.0.0.1])
	by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 09198-06 for ;
	Sat, 22 Feb 2014 11:41:38 +0000 (GMT)
Received: (qmail 11319 invoked by uid 599); 22 Feb 2014 11:41:37 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP;
	Sat, 22 Feb 2014 11:41:37 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WHAxi-0005v6-7v; Sat, 22 Feb 2014 11:41:42 +0000
From: Richard Mortier 
To: "lars.kurth@xen.org" 
Date: Sat, 22 Feb 2014 11:41:41 +0000
Thread-Topic: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
Thread-Index: Ac8vww31eFNiIM7aQfWH4ULXJKdr2Q==
Message-ID: <3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
References: <5307A1ED.3020207@xen.org>
In-Reply-To: <5307A1ED.3020207@xen.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 21 Feb 2014, at 18:58, Lars Kurth  wrote:

> can you tell us what the memory requirements of a typical Mirage OS VM 
> are.

er, define typical... :)

there are some figures on memory footprint (now perhaps a little outdated) in the mirage ASPLOS'13 paper. the latest xen image in the mirage-www-deployment repo looks like ~2.5MB for the entire http://openmirage.org website.

> If you have visibility of size needs of HalVM, ErlangOnXen, ... 
> that would be helpful too

sorry, i don't, don't know if anyone else does.

fwiw i've a 3rd year undergrad project student (sam williams) at the moment who's putting erlang on xen directly (ie., not using ErlangOnXen). i expect it will be open source when released (though that's up to him). the student has already released some of his early prototypes, including moo and lisp -- https://github.com/samcamwilliams/moo-on-xen and https://github.com/samcamwilliams/lisp-on-xen. i expect he'll get some figures on memory footprint when he writes his dissertation.

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 22 15:56:02 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 22 Feb 2014 15:56: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 1WHEvi-00030U-V2; Sat, 22 Feb 2014 15:55:54 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHEvh-00030P-Dt
	for mirageos-devel@lists.xenproject.org; Sat, 22 Feb 2014 15:55:53 +0000
Received: from [193.109.254.147:3909] by server-5.bemta-14.messagelabs.com id
	0E/EB-16688-888C8035; Sat, 22 Feb 2014 15:55:52 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-15.tower-27.messagelabs.com!1393084550!6082984!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31496 invoked from network); 22 Feb 2014 15:55:50 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-15.tower-27.messagelabs.com with SMTP;
	22 Feb 2014 15:55:50 -0000
Received: (qmail 26781 invoked by uid 634); 22 Feb 2014 15:55:49 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.110]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sat, 22 Feb 2014 15:55:49 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
Date: Sat, 22 Feb 2014 15:55:48 +0000
Message-Id: <5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
References: <5307A1ED.3020207@xen.org>
	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 22 Feb 2014, at 11:41, Richard Mortier  wrote:

> 
> On 21 Feb 2014, at 18:58, Lars Kurth  wrote:
> 
>> can you tell us what the memory requirements of a typical Mirage OS VM 
>> are.
> 
> er, define typical... :)
> 
> there are some figures on memory footprint (now perhaps a little outdated) in the mirage ASPLOS'13 paper. the latest xen image in the mirage-www-deployment repo looks like ~2.5MB for the entire http://openmirage.org website.

The live Mirage website is configured with 64MB of RAM, fwiw.  It could probably be lowered, but we haven't bothered trying recently.  It's on the list of things to do (integrate the GC with the balloon driver, and/or experiment with the page sharing APIs for immutable data).


> 
>> If you have visibility of size needs of HalVM, ErlangOnXen, ... 
>> that would be helpful too
> 
> sorry, i don't, don't know if anyone else does.

I'm not aware of any published numbers for the others either, sorry.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 22 15:56:02 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 22 Feb 2014 15:56: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 1WHEvi-00030U-V2; Sat, 22 Feb 2014 15:55:54 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHEvh-00030P-Dt
	for mirageos-devel@lists.xenproject.org; Sat, 22 Feb 2014 15:55:53 +0000
Received: from [193.109.254.147:3909] by server-5.bemta-14.messagelabs.com id
	0E/EB-16688-888C8035; Sat, 22 Feb 2014 15:55:52 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-15.tower-27.messagelabs.com!1393084550!6082984!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31496 invoked from network); 22 Feb 2014 15:55:50 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-15.tower-27.messagelabs.com with SMTP;
	22 Feb 2014 15:55:50 -0000
Received: (qmail 26781 invoked by uid 634); 22 Feb 2014 15:55:49 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.110]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sat, 22 Feb 2014 15:55:49 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
Date: Sat, 22 Feb 2014 15:55:48 +0000
Message-Id: <5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
References: <5307A1ED.3020207@xen.org>
	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 22 Feb 2014, at 11:41, Richard Mortier  wrote:

> 
> On 21 Feb 2014, at 18:58, Lars Kurth  wrote:
> 
>> can you tell us what the memory requirements of a typical Mirage OS VM 
>> are.
> 
> er, define typical... :)
> 
> there are some figures on memory footprint (now perhaps a little outdated) in the mirage ASPLOS'13 paper. the latest xen image in the mirage-www-deployment repo looks like ~2.5MB for the entire http://openmirage.org website.

The live Mirage website is configured with 64MB of RAM, fwiw.  It could probably be lowered, but we haven't bothered trying recently.  It's on the list of things to do (integrate the GC with the balloon driver, and/or experiment with the page sharing APIs for immutable data).


> 
>> If you have visibility of size needs of HalVM, ErlangOnXen, ... 
>> that would be helpful too
> 
> sorry, i don't, don't know if anyone else does.

I'm not aware of any published numbers for the others either, sorry.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 22 22:15:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 22 Feb 2014 22:15: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 1WHKrI-0004kH-Ei; Sat, 22 Feb 2014 22:15:44 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHKrG-0004kC-Hx
	for mirageos-devel@lists.xenproject.org; Sat, 22 Feb 2014 22:15:42 +0000
Received: from [85.158.139.211:18797] by server-12.bemta-5.messagelabs.com id
	44/80-15415-D8129035; Sat, 22 Feb 2014 22:15:41 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-6.tower-206.messagelabs.com!1393107340!5595084!1
X-Originating-IP: [74.125.82.46]
X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27602 invoked from network); 22 Feb 2014 22:15:40 -0000
Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com)
	(74.125.82.46)
	by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	22 Feb 2014 22:15:40 -0000
Received: by mail-wg0-f46.google.com with SMTP id x13so3495210wgg.1
	for ;
	Sat, 22 Feb 2014 14:15:40 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:references:mime-version:in-reply-to:content-type
	:content-transfer-encoding:message-id:cc:from:subject:date:to;
	bh=vT39ifU45BIotkuFKzNtWgGsy07oIbbBYZm1MjIo2Bo=;
	b=ZaeYt8nhreieLBHsSHKS/leHlUYfzrouHxTUwboYpKJOQzjhb69d86kbMV9F6w+JJp
	qKvu+DfsNDNX3Q9tBucH7VGoEx9PHH5ktxxDh29S7YiDpbXDWK+54zQjQz8pHjZDUx4Q
	D42spp42Fn938T2NYlQeo9JioElxhLmINcRAGLJQ0IEh7q7SwY2QutrelSRjUn97sgjy
	+1LkGOXheB5SSPcElgTMU9ek7rbhAXq5mifQO7zRbyqVXXlRuOeBgArGUs5+eCgsZLoq
	gHQcyQXLi0zBQAgeJP82vI8tFFKrQrNIPmIh70YHCcA+2G97nfp7oPlYtXFq6FM3E/DN
	xgXw==
X-Gm-Message-State: ALoCoQnk5VBvWsSA7Pb6AmvvvQxLQ7m8M7MjBxztDYfBs051iW7u13FxqHZC/wtcxpAior1+VJFt
X-Received: by 10.180.206.172 with SMTP id lp12mr8233832wic.46.1393107340122; 
	Sat, 22 Feb 2014 14:15:40 -0800 (PST)
Received: from [192.168.1.5] (94-30-83-216.xdsl.murphx.net. [94.30.83.216])
	by mx.google.com with ESMTPSA id
	s12sm17535835wju.13.2014.02.22.14.15.37 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sat, 22 Feb 2014 14:15:38 -0800 (PST)
References: <5307A1ED.3020207@xen.org>
	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
Message-Id: 
X-Mailer: iPhone Mail (10B329)
From: Julian Chesterfield 
Date: Sat, 22 Feb 2014 22:13:41 +0000
To: Anil Madhavapeddy 
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Doesn't the website image include the embedded content as well? Is the content stored compressed? So hosting the website image will require more ram than a minimal image.

Sent from my iPhone

On 22 Feb 2014, at 15:55, Anil Madhavapeddy  wrote:

> On 22 Feb 2014, at 11:41, Richard Mortier  wrote:
> 
>> 
>> On 21 Feb 2014, at 18:58, Lars Kurth  wrote:
>> 
>>> can you tell us what the memory requirements of a typical Mirage OS VM 
>>> are.
>> 
>> er, define typical... :)
>> 
>> there are some figures on memory footprint (now perhaps a little outdated) in the mirage ASPLOS'13 paper. the latest xen image in the mirage-www-deployment repo looks like ~2.5MB for the entire http://openmirage.org website.
> 
> The live Mirage website is configured with 64MB of RAM, fwiw.  It could probably be lowered, but we haven't bothered trying recently.  It's on the list of things to do (integrate the GC with the balloon driver, and/or experiment with the page sharing APIs for immutable data).
> 
> 
>> 
>>> If you have visibility of size needs of HalVM, ErlangOnXen, ... 
>>> that would be helpful too
>> 
>> sorry, i don't, don't know if anyone else does.
> 
> I'm not aware of any published numbers for the others either, sorry.
> 
> -anil
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 22 22:15:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 22 Feb 2014 22:15: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 1WHKrI-0004kH-Ei; Sat, 22 Feb 2014 22:15:44 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHKrG-0004kC-Hx
	for mirageos-devel@lists.xenproject.org; Sat, 22 Feb 2014 22:15:42 +0000
Received: from [85.158.139.211:18797] by server-12.bemta-5.messagelabs.com id
	44/80-15415-D8129035; Sat, 22 Feb 2014 22:15:41 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-6.tower-206.messagelabs.com!1393107340!5595084!1
X-Originating-IP: [74.125.82.46]
X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27602 invoked from network); 22 Feb 2014 22:15:40 -0000
Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com)
	(74.125.82.46)
	by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	22 Feb 2014 22:15:40 -0000
Received: by mail-wg0-f46.google.com with SMTP id x13so3495210wgg.1
	for ;
	Sat, 22 Feb 2014 14:15:40 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:references:mime-version:in-reply-to:content-type
	:content-transfer-encoding:message-id:cc:from:subject:date:to;
	bh=vT39ifU45BIotkuFKzNtWgGsy07oIbbBYZm1MjIo2Bo=;
	b=ZaeYt8nhreieLBHsSHKS/leHlUYfzrouHxTUwboYpKJOQzjhb69d86kbMV9F6w+JJp
	qKvu+DfsNDNX3Q9tBucH7VGoEx9PHH5ktxxDh29S7YiDpbXDWK+54zQjQz8pHjZDUx4Q
	D42spp42Fn938T2NYlQeo9JioElxhLmINcRAGLJQ0IEh7q7SwY2QutrelSRjUn97sgjy
	+1LkGOXheB5SSPcElgTMU9ek7rbhAXq5mifQO7zRbyqVXXlRuOeBgArGUs5+eCgsZLoq
	gHQcyQXLi0zBQAgeJP82vI8tFFKrQrNIPmIh70YHCcA+2G97nfp7oPlYtXFq6FM3E/DN
	xgXw==
X-Gm-Message-State: ALoCoQnk5VBvWsSA7Pb6AmvvvQxLQ7m8M7MjBxztDYfBs051iW7u13FxqHZC/wtcxpAior1+VJFt
X-Received: by 10.180.206.172 with SMTP id lp12mr8233832wic.46.1393107340122; 
	Sat, 22 Feb 2014 14:15:40 -0800 (PST)
Received: from [192.168.1.5] (94-30-83-216.xdsl.murphx.net. [94.30.83.216])
	by mx.google.com with ESMTPSA id
	s12sm17535835wju.13.2014.02.22.14.15.37 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sat, 22 Feb 2014 14:15:38 -0800 (PST)
References: <5307A1ED.3020207@xen.org>
	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
Message-Id: 
X-Mailer: iPhone Mail (10B329)
From: Julian Chesterfield 
Date: Sat, 22 Feb 2014 22:13:41 +0000
To: Anil Madhavapeddy 
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Doesn't the website image include the embedded content as well? Is the content stored compressed? So hosting the website image will require more ram than a minimal image.

Sent from my iPhone

On 22 Feb 2014, at 15:55, Anil Madhavapeddy  wrote:

> On 22 Feb 2014, at 11:41, Richard Mortier  wrote:
> 
>> 
>> On 21 Feb 2014, at 18:58, Lars Kurth  wrote:
>> 
>>> can you tell us what the memory requirements of a typical Mirage OS VM 
>>> are.
>> 
>> er, define typical... :)
>> 
>> there are some figures on memory footprint (now perhaps a little outdated) in the mirage ASPLOS'13 paper. the latest xen image in the mirage-www-deployment repo looks like ~2.5MB for the entire http://openmirage.org website.
> 
> The live Mirage website is configured with 64MB of RAM, fwiw.  It could probably be lowered, but we haven't bothered trying recently.  It's on the list of things to do (integrate the GC with the balloon driver, and/or experiment with the page sharing APIs for immutable data).
> 
> 
>> 
>>> If you have visibility of size needs of HalVM, ErlangOnXen, ... 
>>> that would be helpful too
>> 
>> sorry, i don't, don't know if anyone else does.
> 
> I'm not aware of any published numbers for the others either, sorry.
> 
> -anil
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 22 22:32:00 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 22 Feb 2014 22:32: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 1WHL6z-0004n1-N3; Sat, 22 Feb 2014 22:31:57 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WHL6y-0004mw-Q1
	for mirageos-devel@lists.xenproject.org; Sat, 22 Feb 2014 22:31:56 +0000
Received: from [193.109.254.147:43185] by server-5.bemta-14.messagelabs.com id
	CD/53-16688-B5529035; Sat, 22 Feb 2014 22:31:55 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-15.tower-27.messagelabs.com!1393108314!6112879!1
X-Originating-IP: [93.95.15.170]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3784 invoked from network); 22 Feb 2014 22:31:54 -0000
Received: from engine03-20433-3.icritical.com (HELO
	engine03-20433-3.icritical.com) (93.95.15.170)
	by server-15.tower-27.messagelabs.com with SMTP;
	22 Feb 2014 22:31:54 -0000
Received: (qmail 24582 invoked from network); 22 Feb 2014 22:31:55 -0000
Received: from localhost (127.0.0.1)
	by engine03-20433-3.icritical.com with SMTP; 22 Feb 2014 22:31:55 -0000
Received: from engine03-20433-3.icritical.com ([127.0.0.1])
	by localhost (engine03-20433-3.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 24423-02 for ;
	Sat, 22 Feb 2014 22:31:54 +0000 (GMT)
Received: (qmail 24570 invoked by uid 599); 22 Feb 2014 22:31:54 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP;
	Sat, 22 Feb 2014 22:31:54 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WHL6r-0007xR-DL; Sat, 22 Feb 2014 22:31:49 +0000
From: Richard Mortier 
To: Julian Chesterfield 
Date: Sat, 22 Feb 2014 22:29:54 +0000
Thread-Topic: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
Thread-Index: Ac8wHeA5CpACjg4xQuW8wNWGiYSVMA==
Message-ID: 
References: <5307A1ED.3020207@xen.org>
	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
	
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine03-20433-3.icritical.com
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 22 Feb 2014, at 22:13, Julian Chesterfield  wrote:

> Doesn't the website image include the embedded content as well?

yes

> Is the content stored compressed? 

no

> So hosting the website image will require more ram than a minimal image.

yes; hence my question about what "typical" means :)

> 
> Sent from my iPhone
> 
> On 22 Feb 2014, at 15:55, Anil Madhavapeddy  wrote:
> 
>> On 22 Feb 2014, at 11:41, Richard Mortier  wrote:
>> 
>>> 
>>> On 21 Feb 2014, at 18:58, Lars Kurth  wrote:
>>> 
>>>> can you tell us what the memory requirements of a typical Mirage OS VM 
>>>> are.
>>> 
>>> er, define typical... :)
>>> 
>>> there are some figures on memory footprint (now perhaps a little outdated) in the mirage ASPLOS'13 paper. the latest xen image in the mirage-www-deployment repo looks like ~2.5MB for the entire http://openmirage.org website.
>> 
>> The live Mirage website is configured with 64MB of RAM, fwiw.  It could probably be lowered, but we haven't bothered trying recently.  It's on the list of things to do (integrate the GC with the balloon driver, and/or experiment with the page sharing APIs for immutable data).
>> 
>> 
>>> 
>>>> If you have visibility of size needs of HalVM, ErlangOnXen, ... 
>>>> that would be helpful too
>>> 
>>> sorry, i don't, don't know if anyone else does.
>> 
>> I'm not aware of any published numbers for the others either, sorry.
>> 
>> -anil
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sat Feb 22 22:32:00 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sat, 22 Feb 2014 22:32: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 1WHL6z-0004n1-N3; Sat, 22 Feb 2014 22:31:57 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WHL6y-0004mw-Q1
	for mirageos-devel@lists.xenproject.org; Sat, 22 Feb 2014 22:31:56 +0000
Received: from [193.109.254.147:43185] by server-5.bemta-14.messagelabs.com id
	CD/53-16688-B5529035; Sat, 22 Feb 2014 22:31:55 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-15.tower-27.messagelabs.com!1393108314!6112879!1
X-Originating-IP: [93.95.15.170]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3784 invoked from network); 22 Feb 2014 22:31:54 -0000
Received: from engine03-20433-3.icritical.com (HELO
	engine03-20433-3.icritical.com) (93.95.15.170)
	by server-15.tower-27.messagelabs.com with SMTP;
	22 Feb 2014 22:31:54 -0000
Received: (qmail 24582 invoked from network); 22 Feb 2014 22:31:55 -0000
Received: from localhost (127.0.0.1)
	by engine03-20433-3.icritical.com with SMTP; 22 Feb 2014 22:31:55 -0000
Received: from engine03-20433-3.icritical.com ([127.0.0.1])
	by localhost (engine03-20433-3.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 24423-02 for ;
	Sat, 22 Feb 2014 22:31:54 +0000 (GMT)
Received: (qmail 24570 invoked by uid 599); 22 Feb 2014 22:31:54 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP;
	Sat, 22 Feb 2014 22:31:54 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WHL6r-0007xR-DL; Sat, 22 Feb 2014 22:31:49 +0000
From: Richard Mortier 
To: Julian Chesterfield 
Date: Sat, 22 Feb 2014 22:29:54 +0000
Thread-Topic: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
Thread-Index: Ac8wHeA5CpACjg4xQuW8wNWGiYSVMA==
Message-ID: 
References: <5307A1ED.3020207@xen.org>
	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
	
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine03-20433-3.icritical.com
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 22 Feb 2014, at 22:13, Julian Chesterfield  wrote:

> Doesn't the website image include the embedded content as well?

yes

> Is the content stored compressed? 

no

> So hosting the website image will require more ram than a minimal image.

yes; hence my question about what "typical" means :)

> 
> Sent from my iPhone
> 
> On 22 Feb 2014, at 15:55, Anil Madhavapeddy  wrote:
> 
>> On 22 Feb 2014, at 11:41, Richard Mortier  wrote:
>> 
>>> 
>>> On 21 Feb 2014, at 18:58, Lars Kurth  wrote:
>>> 
>>>> can you tell us what the memory requirements of a typical Mirage OS VM 
>>>> are.
>>> 
>>> er, define typical... :)
>>> 
>>> there are some figures on memory footprint (now perhaps a little outdated) in the mirage ASPLOS'13 paper. the latest xen image in the mirage-www-deployment repo looks like ~2.5MB for the entire http://openmirage.org website.
>> 
>> The live Mirage website is configured with 64MB of RAM, fwiw.  It could probably be lowered, but we haven't bothered trying recently.  It's on the list of things to do (integrate the GC with the balloon driver, and/or experiment with the page sharing APIs for immutable data).
>> 
>> 
>>> 
>>>> If you have visibility of size needs of HalVM, ErlangOnXen, ... 
>>>> that would be helpful too
>>> 
>>> sorry, i don't, don't know if anyone else does.
>> 
>> I'm not aware of any published numbers for the others either, sorry.
>> 
>> -anil
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 23 12:57:14 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 23 Feb 2014 12:57:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WHYcI-0004aG-16; Sun, 23 Feb 2014 12:57:10 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHYcG-0004aB-BA
	for mirageos-devel@lists.xenproject.org; Sun, 23 Feb 2014 12:57:08 +0000
Received: from [85.158.137.68:63079] by server-9.bemta-3.messagelabs.com id
	80/FB-10184-320F9035; Sun, 23 Feb 2014 12:57:07 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-6.tower-31.messagelabs.com!1393160225!3609628!1
X-Originating-IP: [74.125.82.44]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16515 invoked from network); 23 Feb 2014 12:57:05 -0000
Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com)
	(74.125.82.44)
	by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	23 Feb 2014 12:57:05 -0000
Received: by mail-wg0-f44.google.com with SMTP id k14so3869806wgh.35
	for ;
	Sun, 23 Feb 2014 04:57:05 -0800 (PST)
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=wmUE/QXqhuxtp3erbJyEBpHuH4VgP7OXK9O2zSzXmfc=;
	b=LGGSfeciAivNNLe6nRkjKZdEbywd0qeZKWkf29ru/CT0/e1PknnBBDomBFmaavdrts
	KsHRwJDa8IkDpuo0XpMQq8iXscVwcZrZGVksMXW7OXo6LnfzNlEUFq3EaC+RWgNaMBSb
	hbAR4xre9CLLywKXR7AP93aw5edrB6GoSE34vgBtx3aZCiBvH1g/ee7r4JEPtHcCKQXl
	J4JTgjziLs8Yyxq+XfO+iF2PXiV8VFGHvRJt0RnSEJSc/yfKJXns00YULnHO5Juhu/Ox
	cpCTs68IL8QKl1rFS9bMuyvYj71pi/BdVYGGOucsZYxFY8D3ZI7bMSVvYtBhHrJkIAli
	5qIw==
X-Received: by 10.194.6.8 with SMTP id w8mr14512877wjw.16.1393160224904;
	Sun, 23 Feb 2014 04:57:04 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id uq2sm33200164wjc.5.2014.02.23.04.57.03
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sun, 23 Feb 2014 04:57:03 -0800 (PST)
Message-ID: <5309F01E.7070703@xen.org>
Date: Sun, 23 Feb 2014 12:57:02 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mirageos-devel@lists.xenproject.org
References: <5307A1ED.3020207@xen.org>	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>	
	
In-Reply-To: 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 22/02/2014 22:29, Richard Mortier wrote:
> On 22 Feb 2014, at 22:13, Julian Chesterfield  wrote:
>
>> So hosting the website image will require more ram than a minimal image.
> yes; hence my question about what "typical" means :)
The background for the question was whether the event channel 
improvements in Xen 4.4 (and thus the capability to run a lot of smaller 
VMs on one host) will benefit Mirage OS and others. That argement hinges 
on Mirage OS (and similar) having significantly smaller memory 
footprints that your traditional VM.

I guess "typical" means "memory requirements for the type of workloads 
Mirage OS is aiming to target

Regards
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 23 12:57:14 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 23 Feb 2014 12:57:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WHYcI-0004aG-16; Sun, 23 Feb 2014 12:57:10 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHYcG-0004aB-BA
	for mirageos-devel@lists.xenproject.org; Sun, 23 Feb 2014 12:57:08 +0000
Received: from [85.158.137.68:63079] by server-9.bemta-3.messagelabs.com id
	80/FB-10184-320F9035; Sun, 23 Feb 2014 12:57:07 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-6.tower-31.messagelabs.com!1393160225!3609628!1
X-Originating-IP: [74.125.82.44]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16515 invoked from network); 23 Feb 2014 12:57:05 -0000
Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com)
	(74.125.82.44)
	by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	23 Feb 2014 12:57:05 -0000
Received: by mail-wg0-f44.google.com with SMTP id k14so3869806wgh.35
	for ;
	Sun, 23 Feb 2014 04:57:05 -0800 (PST)
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=wmUE/QXqhuxtp3erbJyEBpHuH4VgP7OXK9O2zSzXmfc=;
	b=LGGSfeciAivNNLe6nRkjKZdEbywd0qeZKWkf29ru/CT0/e1PknnBBDomBFmaavdrts
	KsHRwJDa8IkDpuo0XpMQq8iXscVwcZrZGVksMXW7OXo6LnfzNlEUFq3EaC+RWgNaMBSb
	hbAR4xre9CLLywKXR7AP93aw5edrB6GoSE34vgBtx3aZCiBvH1g/ee7r4JEPtHcCKQXl
	J4JTgjziLs8Yyxq+XfO+iF2PXiV8VFGHvRJt0RnSEJSc/yfKJXns00YULnHO5Juhu/Ox
	cpCTs68IL8QKl1rFS9bMuyvYj71pi/BdVYGGOucsZYxFY8D3ZI7bMSVvYtBhHrJkIAli
	5qIw==
X-Received: by 10.194.6.8 with SMTP id w8mr14512877wjw.16.1393160224904;
	Sun, 23 Feb 2014 04:57:04 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id uq2sm33200164wjc.5.2014.02.23.04.57.03
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sun, 23 Feb 2014 04:57:03 -0800 (PST)
Message-ID: <5309F01E.7070703@xen.org>
Date: Sun, 23 Feb 2014 12:57:02 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mirageos-devel@lists.xenproject.org
References: <5307A1ED.3020207@xen.org>	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>	
	
In-Reply-To: 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 22/02/2014 22:29, Richard Mortier wrote:
> On 22 Feb 2014, at 22:13, Julian Chesterfield  wrote:
>
>> So hosting the website image will require more ram than a minimal image.
> yes; hence my question about what "typical" means :)
The background for the question was whether the event channel 
improvements in Xen 4.4 (and thus the capability to run a lot of smaller 
VMs on one host) will benefit Mirage OS and others. That argement hinges 
on Mirage OS (and similar) having significantly smaller memory 
footprints that your traditional VM.

I guess "typical" means "memory requirements for the type of workloads 
Mirage OS is aiming to target

Regards
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 23 15:51:07 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 23 Feb 2014 15:51: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 1WHbKZ-000541-7G; Sun, 23 Feb 2014 15:51:03 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHbKW-00053w-UN
	for mirageos-devel@lists.xenproject.org; Sun, 23 Feb 2014 15:51:01 +0000
Received: from [85.158.137.68:57506] by server-10.bemta-3.messagelabs.com id
	E7/54-07302-4E81A035; Sun, 23 Feb 2014 15:51:00 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-9.tower-31.messagelabs.com!1393170659!3615304!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10841 invoked from network); 23 Feb 2014 15:50:59 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-9.tower-31.messagelabs.com with SMTP;
	23 Feb 2014 15:50:59 -0000
Received: (qmail 485 invoked by uid 634); 23 Feb 2014 15:50:58 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sun, 23 Feb 2014 15:50:57 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <5309F01E.7070703@xen.org>
Date: Sun, 23 Feb 2014 15:50:54 +0000
Message-Id: <18219775-7A11-4AC6-8C07-D02D777EB74E@recoil.org>
References: <5307A1ED.3020207@xen.org>	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>	
	
	<5309F01E.7070703@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: George Dunlap ,
	mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 23 Feb 2014, at 12:57, Lars Kurth  wrote:

> On 22/02/2014 22:29, Richard Mortier wrote:
>> On 22 Feb 2014, at 22:13, Julian Chesterfield  wrote:
>> 
>>> So hosting the website image will require more ram than a minimal image.
>> yes; hence my question about what "typical" means :)
> The background for the question was whether the event channel improvements in Xen 4.4 (and thus the capability to run a lot of smaller VMs on one host) will benefit Mirage OS and others. That argement hinges on Mirage OS (and similar) having significantly smaller memory footprints that your traditional VM.
> 
> I guess "typical" means "memory requirements for the type of workloads Mirage OS is aiming to target

They definitely will have a big positive impact.  Our overall goal is to get an equivalent number of MirageOS VMs running as you can get distinct processes running on a single Unix host.  If most are idle (e.g. just brief amount of traffic) and we are using modern 64-core machines, then we've estimated that we able to get to 10000 VMs without too many problems, with these problems rearing their head:

- RAM utilization (given 24MB is right on the edge, so page sharing is needed)
- page sharing between similar VMs will help reduce load
- that many VMs would require driver domains, since a dom0 is very unlikely to be able to handle all the load.
- the VM scheduler may come under some pressure

The "10000 VM" goal is a stake in the ground to see how well the Xen architecture holds up to very dense clouds of tiny VMs, and it was really blocked on the low event channel number that existed in Xen 4.4+.

cheers,
Anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Sun Feb 23 15:51:07 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Sun, 23 Feb 2014 15:51: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 1WHbKZ-000541-7G; Sun, 23 Feb 2014 15:51:03 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHbKW-00053w-UN
	for mirageos-devel@lists.xenproject.org; Sun, 23 Feb 2014 15:51:01 +0000
Received: from [85.158.137.68:57506] by server-10.bemta-3.messagelabs.com id
	E7/54-07302-4E81A035; Sun, 23 Feb 2014 15:51:00 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-9.tower-31.messagelabs.com!1393170659!3615304!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10841 invoked from network); 23 Feb 2014 15:50:59 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-9.tower-31.messagelabs.com with SMTP;
	23 Feb 2014 15:50:59 -0000
Received: (qmail 485 invoked by uid 634); 23 Feb 2014 15:50:58 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Sun, 23 Feb 2014 15:50:57 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <5309F01E.7070703@xen.org>
Date: Sun, 23 Feb 2014 15:50:54 +0000
Message-Id: <18219775-7A11-4AC6-8C07-D02D777EB74E@recoil.org>
References: <5307A1ED.3020207@xen.org>	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>	
	
	<5309F01E.7070703@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: George Dunlap ,
	mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 23 Feb 2014, at 12:57, Lars Kurth  wrote:

> On 22/02/2014 22:29, Richard Mortier wrote:
>> On 22 Feb 2014, at 22:13, Julian Chesterfield  wrote:
>> 
>>> So hosting the website image will require more ram than a minimal image.
>> yes; hence my question about what "typical" means :)
> The background for the question was whether the event channel improvements in Xen 4.4 (and thus the capability to run a lot of smaller VMs on one host) will benefit Mirage OS and others. That argement hinges on Mirage OS (and similar) having significantly smaller memory footprints that your traditional VM.
> 
> I guess "typical" means "memory requirements for the type of workloads Mirage OS is aiming to target

They definitely will have a big positive impact.  Our overall goal is to get an equivalent number of MirageOS VMs running as you can get distinct processes running on a single Unix host.  If most are idle (e.g. just brief amount of traffic) and we are using modern 64-core machines, then we've estimated that we able to get to 10000 VMs without too many problems, with these problems rearing their head:

- RAM utilization (given 24MB is right on the edge, so page sharing is needed)
- page sharing between similar VMs will help reduce load
- that many VMs would require driver domains, since a dom0 is very unlikely to be able to handle all the load.
- the VM scheduler may come under some pressure

The "10000 VM" goal is a stake in the ground to see how well the Xen architecture holds up to very dense clouds of tiny VMs, and it was really blocked on the low event channel number that existed in Xen 4.4+.

cheers,
Anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 13:19:31 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 13:19: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 1WHvRN-0001Ad-R1; Mon, 24 Feb 2014 13:19:25 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHvRM-0001AQ-EG
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 13:19:24 +0000
Received: from [85.158.143.35:23806] by server-2.bemta-4.messagelabs.com id
	50/2A-10891-BD64B035; Mon, 24 Feb 2014 13:19:23 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-3.tower-21.messagelabs.com!1393247963!7881721!1
X-Originating-IP: [74.125.82.46]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19861 invoked from network); 24 Feb 2014 13:19:23 -0000
Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com)
	(74.125.82.46)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	24 Feb 2014 13:19:23 -0000
Received: by mail-wg0-f46.google.com with SMTP id x13so4562220wgg.1
	for ;
	Mon, 24 Feb 2014 05:19:22 -0800 (PST)
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=FztG5DNbEvWoN1uAYvSYVXnfHQJzOWy+OMaxepTXRW0=;
	b=gRjvaM8HP0+UZJcwPhgtz5CeB0EK5TXM9P/lwcYTgaEJDtc+rM3puxbvYyfhMhraVQ
	125FYVr9MfdR2a/SDGgBVW9FHzfT7YV/39IJmCTG64qgttFX8udeV7ep9RLBGk4mFJg1
	TmrwHTxQoMqXB5Fz8iYVoOgS6U87l2my8FuevSOOQiZ+brexxOEfYNvES1EtQhnybg8y
	7qrTlihgH5r4C+xv+HuZtTs1QOAjGu1netP7Tj38xzTVhfnNimHapJLq8wPGWl84KgIg
	8QTgRyl2FCrDM4mcIa98+kfmJ/D09MHfbG80b4Teaq3SguEGZCvjWm+XN6xaTuQ5pkQf
	B70g==
X-Received: by 10.180.11.233 with SMTP id t9mr14790111wib.1.1393247962706;
	Mon, 24 Feb 2014 05:19:22 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id fb8sm24267819wic.3.2014.02.24.05.19.21
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 24 Feb 2014 05:19:21 -0800 (PST)
Message-ID: <530B46D8.5020501@xen.org>
Date: Mon, 24 Feb 2014 13:19:20 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: George Dunlap , 
	Anil Madhavapeddy 
References: <5307A1ED.3020207@xen.org>	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>	
	
	<5309F01E.7070703@xen.org>
	<18219775-7A11-4AC6-8C07-D02D777EB74E@recoil.org>
	<530B2370.7090603@eu.citrix.com>
In-Reply-To: <530B2370.7090603@eu.citrix.com>
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 24/02/2014 10:48, George Dunlap wrote:
> On 02/23/2014 03:50 PM, Anil Madhavapeddy wrote:
>> On 23 Feb 2014, at 12:57, Lars Kurth  wrote:
>>
>>> On 22/02/2014 22:29, Richard Mortier wrote:
>>>> On 22 Feb 2014, at 22:13, Julian Chesterfield 
>>>>  wrote:
>>>>
>>>>> So hosting the website image will require more ram than a minimal 
>>>>> image.
>>>> yes; hence my question about what "typical" means :)
>>> The background for the question was whether the event channel 
>>> improvements in Xen 4.4 (and thus the capability to run a lot of 
>>> smaller VMs on one host) will benefit Mirage OS and others. That 
>>> argement hinges on Mirage OS (and similar) having significantly 
>>> smaller memory footprints that your traditional VM.
>>>
>>> I guess "typical" means "memory requirements for the type of 
>>> workloads Mirage OS is aiming to target
>> They definitely will have a big positive impact.  Our overall goal is 
>> to get an equivalent number of MirageOS VMs running as you can get 
>> distinct processes running on a single Unix host. If most are idle 
>> (e.g. just brief amount of traffic) and we are using modern 64-core 
>> machines, then we've estimated that we able to get to 10000 VMs 
>> without too many problems, with these problems rearing their head:
>
> Lars, I think you're missing part of the question: Matt Wilson's 
> question (re our press release) was whether event channel scalability 
> will have a benefit to MirageOS, OSV, and others *in public clouds*.  
> At least a few years ago, the assumption was that most public clouds 
> would be using massive amounts of rather inexpensive machines; maybe 8 
> cores at the most.
>
> So yes, for 64+core machines, event channels will obviously be a 
> scalability limit.  But is it really even useful to try to run >1000 
> actual servers on an 8-core box?  Even if you have enough memory for 
> them all, do yo have enough CPU?
I suppose I did miss this. Too much mult-tasking )-: And 
https://www.linux.com/news/enterprise/cloud-computing/751156-are-cloud-operating-systems-the-next-big-thing- 
under "Remaining challenges" actually look at issues.

>
> Of course the default size of physical servers in the cloud may have 
> changed; maybe public clouds now have 64-core boxes.  But given the 
> person who asked the question, I'm inclined to think it hasn't changed 
> much.
>
Maybe a the more correct thing would be to say that we are building the 
foundations that will enable Cloud OS use-cases in future incarnations 
of public clouds

Lars


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 13:19:31 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 13:19: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 1WHvRN-0001Ad-R1; Mon, 24 Feb 2014 13:19:25 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHvRM-0001AQ-EG
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 13:19:24 +0000
Received: from [85.158.143.35:23806] by server-2.bemta-4.messagelabs.com id
	50/2A-10891-BD64B035; Mon, 24 Feb 2014 13:19:23 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-3.tower-21.messagelabs.com!1393247963!7881721!1
X-Originating-IP: [74.125.82.46]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19861 invoked from network); 24 Feb 2014 13:19:23 -0000
Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com)
	(74.125.82.46)
	by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	24 Feb 2014 13:19:23 -0000
Received: by mail-wg0-f46.google.com with SMTP id x13so4562220wgg.1
	for ;
	Mon, 24 Feb 2014 05:19:22 -0800 (PST)
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=FztG5DNbEvWoN1uAYvSYVXnfHQJzOWy+OMaxepTXRW0=;
	b=gRjvaM8HP0+UZJcwPhgtz5CeB0EK5TXM9P/lwcYTgaEJDtc+rM3puxbvYyfhMhraVQ
	125FYVr9MfdR2a/SDGgBVW9FHzfT7YV/39IJmCTG64qgttFX8udeV7ep9RLBGk4mFJg1
	TmrwHTxQoMqXB5Fz8iYVoOgS6U87l2my8FuevSOOQiZ+brexxOEfYNvES1EtQhnybg8y
	7qrTlihgH5r4C+xv+HuZtTs1QOAjGu1netP7Tj38xzTVhfnNimHapJLq8wPGWl84KgIg
	8QTgRyl2FCrDM4mcIa98+kfmJ/D09MHfbG80b4Teaq3SguEGZCvjWm+XN6xaTuQ5pkQf
	B70g==
X-Received: by 10.180.11.233 with SMTP id t9mr14790111wib.1.1393247962706;
	Mon, 24 Feb 2014 05:19:22 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id fb8sm24267819wic.3.2014.02.24.05.19.21
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 24 Feb 2014 05:19:21 -0800 (PST)
Message-ID: <530B46D8.5020501@xen.org>
Date: Mon, 24 Feb 2014 13:19:20 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: George Dunlap , 
	Anil Madhavapeddy 
References: <5307A1ED.3020207@xen.org>	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>	
	
	<5309F01E.7070703@xen.org>
	<18219775-7A11-4AC6-8C07-D02D777EB74E@recoil.org>
	<530B2370.7090603@eu.citrix.com>
In-Reply-To: <530B2370.7090603@eu.citrix.com>
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 24/02/2014 10:48, George Dunlap wrote:
> On 02/23/2014 03:50 PM, Anil Madhavapeddy wrote:
>> On 23 Feb 2014, at 12:57, Lars Kurth  wrote:
>>
>>> On 22/02/2014 22:29, Richard Mortier wrote:
>>>> On 22 Feb 2014, at 22:13, Julian Chesterfield 
>>>>  wrote:
>>>>
>>>>> So hosting the website image will require more ram than a minimal 
>>>>> image.
>>>> yes; hence my question about what "typical" means :)
>>> The background for the question was whether the event channel 
>>> improvements in Xen 4.4 (and thus the capability to run a lot of 
>>> smaller VMs on one host) will benefit Mirage OS and others. That 
>>> argement hinges on Mirage OS (and similar) having significantly 
>>> smaller memory footprints that your traditional VM.
>>>
>>> I guess "typical" means "memory requirements for the type of 
>>> workloads Mirage OS is aiming to target
>> They definitely will have a big positive impact.  Our overall goal is 
>> to get an equivalent number of MirageOS VMs running as you can get 
>> distinct processes running on a single Unix host. If most are idle 
>> (e.g. just brief amount of traffic) and we are using modern 64-core 
>> machines, then we've estimated that we able to get to 10000 VMs 
>> without too many problems, with these problems rearing their head:
>
> Lars, I think you're missing part of the question: Matt Wilson's 
> question (re our press release) was whether event channel scalability 
> will have a benefit to MirageOS, OSV, and others *in public clouds*.  
> At least a few years ago, the assumption was that most public clouds 
> would be using massive amounts of rather inexpensive machines; maybe 8 
> cores at the most.
>
> So yes, for 64+core machines, event channels will obviously be a 
> scalability limit.  But is it really even useful to try to run >1000 
> actual servers on an 8-core box?  Even if you have enough memory for 
> them all, do yo have enough CPU?
I suppose I did miss this. Too much mult-tasking )-: And 
https://www.linux.com/news/enterprise/cloud-computing/751156-are-cloud-operating-systems-the-next-big-thing- 
under "Remaining challenges" actually look at issues.

>
> Of course the default size of physical servers in the cloud may have 
> changed; maybe public clouds now have 64-core boxes.  But given the 
> person who asked the question, I'm inclined to think it hasn't changed 
> much.
>
Maybe a the more correct thing would be to say that we are building the 
foundations that will enable Cloud OS use-cases in future incarnations 
of public clouds

Lars


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 13:27:36 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 13:27: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 1WHvZH-0001GY-LD; Mon, 24 Feb 2014 13:27:35 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHvZG-0001GT-BE
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 13:27:34 +0000
Received: from [85.158.137.68:59245] by server-3.bemta-3.messagelabs.com id
	7E/8A-14520-5C84B035; Mon, 24 Feb 2014 13:27:33 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-15.tower-31.messagelabs.com!1393248452!3839778!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16777 invoked from network); 24 Feb 2014 13:27:32 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-15.tower-31.messagelabs.com with SMTP;
	24 Feb 2014 13:27:32 -0000
Received: (qmail 2994 invoked by uid 634); 24 Feb 2014 13:27:32 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Mon, 24 Feb 2014 13:27:30 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <530B2370.7090603@eu.citrix.com>
Date: Mon, 24 Feb 2014 13:27:27 +0000
Message-Id: 
References: <5307A1ED.3020207@xen.org>	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>	
	
	<5309F01E.7070703@xen.org>
	<18219775-7A11-4AC6-8C07-D02D777EB74E@recoil.org>
	<530B2370.7090603@eu.citrix.com>
To: George Dunlap 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 24 Feb 2014, at 10:48, George Dunlap  wrote:

> On 02/23/2014 03:50 PM, Anil Madhavapeddy wrote:
>> On 23 Feb 2014, at 12:57, Lars Kurth  wrote:
>> 
>>> On 22/02/2014 22:29, Richard Mortier wrote:
>>>> On 22 Feb 2014, at 22:13, Julian Chesterfield  wrote:
>>>> 
>>>>> So hosting the website image will require more ram than a minimal image.
>>>> yes; hence my question about what "typical" means :)
>>> The background for the question was whether the event channel improvements in Xen 4.4 (and thus the capability to run a lot of smaller VMs on one host) will benefit Mirage OS and others. That argement hinges on Mirage OS (and similar) having significantly smaller memory footprints that your traditional VM.
>>> 
>>> I guess "typical" means "memory requirements for the type of workloads Mirage OS is aiming to target
>> They definitely will have a big positive impact.  Our overall goal is to get an equivalent number of MirageOS VMs running as you can get distinct processes running on a single Unix host.  If most are idle (e.g. just brief amount of traffic) and we are using modern 64-core machines, then we've estimated that we able to get to 10000 VMs without too many problems, with these problems rearing their head:
> 
> Lars, I think you're missing part of the question: Matt Wilson's question (re our press release) was whether event channel scalability will have a benefit to MirageOS, OSV, and others *in public clouds*.  At least a few years ago, the assumption was that most public clouds would be using massive amounts of rather inexpensive machines; maybe 8 cores at the most.
> 
> So yes, for 64+core machines, event channels will obviously be a scalability limit.  But is it really even useful to try to run >1000 actual servers on an 8-core box?  Even if you have enough memory for them all, do yo have enough CPU?
> 
> Of course the default size of physical servers in the cloud may have changed; maybe public clouds now have 64-core boxes.  But given the person who asked the question, I'm inclined to think it hasn't changed much.

I don't think it's helpful to speculate on whether public clouds have 8- or 64-core machines without further data.  Instead, it's worth considering all the steps required to support unikernels on the public cloud *with the same levels of isolation that Xen provides* (i.e. not containers).

When you consider it like this, Xen has been getting progressively better with every release since 1.0.  Off the top of my head:

- device model stub domains (spread cpu load)
- numa affinity (reduce memory pressure of many domain communication)
- cpupool (to gang schedule same-customer unikernels?)
- memory page sharing + swap (still HVM only as I understand it, but still usable by a unikernel guest)

...and event channel scalability gets added into this to ease pressure off the scheduler.  Scaling is about finding the right resource balances after all, and not a single big-bang feature.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 13:27:36 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 13:27: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 1WHvZH-0001GY-LD; Mon, 24 Feb 2014 13:27:35 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WHvZG-0001GT-BE
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 13:27:34 +0000
Received: from [85.158.137.68:59245] by server-3.bemta-3.messagelabs.com id
	7E/8A-14520-5C84B035; Mon, 24 Feb 2014 13:27:33 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-15.tower-31.messagelabs.com!1393248452!3839778!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16777 invoked from network); 24 Feb 2014 13:27:32 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-15.tower-31.messagelabs.com with SMTP;
	24 Feb 2014 13:27:32 -0000
Received: (qmail 2994 invoked by uid 634); 24 Feb 2014 13:27:32 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Mon, 24 Feb 2014 13:27:30 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <530B2370.7090603@eu.citrix.com>
Date: Mon, 24 Feb 2014 13:27:27 +0000
Message-Id: 
References: <5307A1ED.3020207@xen.org>	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>	
	
	<5309F01E.7070703@xen.org>
	<18219775-7A11-4AC6-8C07-D02D777EB74E@recoil.org>
	<530B2370.7090603@eu.citrix.com>
To: George Dunlap 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 24 Feb 2014, at 10:48, George Dunlap  wrote:

> On 02/23/2014 03:50 PM, Anil Madhavapeddy wrote:
>> On 23 Feb 2014, at 12:57, Lars Kurth  wrote:
>> 
>>> On 22/02/2014 22:29, Richard Mortier wrote:
>>>> On 22 Feb 2014, at 22:13, Julian Chesterfield  wrote:
>>>> 
>>>>> So hosting the website image will require more ram than a minimal image.
>>>> yes; hence my question about what "typical" means :)
>>> The background for the question was whether the event channel improvements in Xen 4.4 (and thus the capability to run a lot of smaller VMs on one host) will benefit Mirage OS and others. That argement hinges on Mirage OS (and similar) having significantly smaller memory footprints that your traditional VM.
>>> 
>>> I guess "typical" means "memory requirements for the type of workloads Mirage OS is aiming to target
>> They definitely will have a big positive impact.  Our overall goal is to get an equivalent number of MirageOS VMs running as you can get distinct processes running on a single Unix host.  If most are idle (e.g. just brief amount of traffic) and we are using modern 64-core machines, then we've estimated that we able to get to 10000 VMs without too many problems, with these problems rearing their head:
> 
> Lars, I think you're missing part of the question: Matt Wilson's question (re our press release) was whether event channel scalability will have a benefit to MirageOS, OSV, and others *in public clouds*.  At least a few years ago, the assumption was that most public clouds would be using massive amounts of rather inexpensive machines; maybe 8 cores at the most.
> 
> So yes, for 64+core machines, event channels will obviously be a scalability limit.  But is it really even useful to try to run >1000 actual servers on an 8-core box?  Even if you have enough memory for them all, do yo have enough CPU?
> 
> Of course the default size of physical servers in the cloud may have changed; maybe public clouds now have 64-core boxes.  But given the person who asked the question, I'm inclined to think it hasn't changed much.

I don't think it's helpful to speculate on whether public clouds have 8- or 64-core machines without further data.  Instead, it's worth considering all the steps required to support unikernels on the public cloud *with the same levels of isolation that Xen provides* (i.e. not containers).

When you consider it like this, Xen has been getting progressively better with every release since 1.0.  Off the top of my head:

- device model stub domains (spread cpu load)
- numa affinity (reduce memory pressure of many domain communication)
- cpupool (to gang schedule same-customer unikernels?)
- memory page sharing + swap (still HVM only as I understand it, but still usable by a unikernel guest)

...and event channel scalability gets added into this to ease pressure off the scheduler.  Scaling is about finding the right resource balances after all, and not a single big-bang feature.

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 15:48:42 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 15:48: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 1WHxlm-0001wL-7j; Mon, 24 Feb 2014 15:48:38 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WHxlk-0001vh-4F
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 15:48:36 +0000
Received: from [85.158.137.68:9387] by server-8.bemta-3.messagelabs.com id
	55/CB-16039-3D96B035; Mon, 24 Feb 2014 15:48:35 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-9.tower-31.messagelabs.com!1393256914!3830887!1
X-Originating-IP: [195.62.217.150]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27401 invoked from network); 24 Feb 2014 15:48:34 -0000
Received: from engine06-20433-6.icritical.com (HELO
	engine06-20433-6.icritical.com) (195.62.217.150)
	by server-9.tower-31.messagelabs.com with SMTP;
	24 Feb 2014 15:48:34 -0000
Received: (qmail 23517 invoked from network); 24 Feb 2014 15:48:26 -0000
Received: from localhost (127.0.0.1)
	by engine06-20433-6.icritical.com with SMTP; 24 Feb 2014 15:48:26 -0000
Received: from engine06-20433-6.icritical.com ([127.0.0.1])
	by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 23373-06 for ;
	Mon, 24 Feb 2014 15:48:26 +0000 (GMT)
Received: (qmail 21995 invoked by uid 599); 24 Feb 2014 15:44:27 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP;
	Mon, 24 Feb 2014 15:44:26 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WHvxN-0001OW-Ky; Mon, 24 Feb 2014 13:52:29 +0000
From: Richard Mortier 
To: Anil Madhavapeddy 
Date: Mon, 24 Feb 2014 13:48:48 +0000
Thread-Topic: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
Thread-Index: Ac8xZySyXYmIXCT+Q0yNGAXbxjw+Ug==
Message-ID: 
References: <5307A1ED.3020207@xen.org>
	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
	
	
	<5309F01E.7070703@xen.org>	<18219775-7A11-4AC6-8C07-D02D777EB74E@recoil.org>
	<530B2370.7090603@eu.citrix.com>
	
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 24 Feb 2014, at 13:27, Anil Madhavapeddy  wrote:

> ...and event channel scalability gets added into this to ease pressure off the scheduler. Scaling is about finding the right resource balances after all, and not a single big-bang feature.

i'd probably even say it's about dynamically finding and continually readjusting resource balances as the workload and system evolves. not a single big bang feature, and not something that you ever really get "right". (imo.)

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 15:48:42 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 15:48: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 1WHxlm-0001wL-7j; Mon, 24 Feb 2014 15:48:38 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WHxlk-0001vh-4F
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 15:48:36 +0000
Received: from [85.158.137.68:9387] by server-8.bemta-3.messagelabs.com id
	55/CB-16039-3D96B035; Mon, 24 Feb 2014 15:48:35 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-9.tower-31.messagelabs.com!1393256914!3830887!1
X-Originating-IP: [195.62.217.150]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27401 invoked from network); 24 Feb 2014 15:48:34 -0000
Received: from engine06-20433-6.icritical.com (HELO
	engine06-20433-6.icritical.com) (195.62.217.150)
	by server-9.tower-31.messagelabs.com with SMTP;
	24 Feb 2014 15:48:34 -0000
Received: (qmail 23517 invoked from network); 24 Feb 2014 15:48:26 -0000
Received: from localhost (127.0.0.1)
	by engine06-20433-6.icritical.com with SMTP; 24 Feb 2014 15:48:26 -0000
Received: from engine06-20433-6.icritical.com ([127.0.0.1])
	by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 23373-06 for ;
	Mon, 24 Feb 2014 15:48:26 +0000 (GMT)
Received: (qmail 21995 invoked by uid 599); 24 Feb 2014 15:44:27 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP;
	Mon, 24 Feb 2014 15:44:26 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WHvxN-0001OW-Ky; Mon, 24 Feb 2014 13:52:29 +0000
From: Richard Mortier 
To: Anil Madhavapeddy 
Date: Mon, 24 Feb 2014 13:48:48 +0000
Thread-Topic: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
Thread-Index: Ac8xZySyXYmIXCT+Q0yNGAXbxjw+Ug==
Message-ID: 
References: <5307A1ED.3020207@xen.org>
	<3D78420F-B42C-45B8-9D42-E7FC127C4D33@nottingham.ac.uk>
	<5CC1DBA9-3CDA-41BA-94D7-8B0CD8A53A79@recoil.org>
	
	
	<5309F01E.7070703@xen.org>	<18219775-7A11-4AC6-8C07-D02D777EB74E@recoil.org>
	<530B2370.7090603@eu.citrix.com>
	
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com
Cc: George Dunlap ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Memory requirements for a typical Mirage OS VM
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 24 Feb 2014, at 13:27, Anil Madhavapeddy  wrote:

> ...and event channel scalability gets added into this to ease pressure off the scheduler. Scaling is about finding the right resource balances after all, and not a single big-bang feature.

i'd probably even say it's about dynamically finding and continually readjusting resource balances as the workload and system evolves. not a single big bang feature, and not something that you ever really get "right". (imo.)

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 18:57:49 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 18:57: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 1WI0io-0001HI-87; Mon, 24 Feb 2014 18:57:46 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WI0il-0001Gu-Vx
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 18:57:44 +0000
Received: from [85.158.137.68:38594] by server-14.bemta-3.messagelabs.com id
	A0/0F-08196-6269B035; Mon, 24 Feb 2014 18:57:42 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-9.tower-31.messagelabs.com!1393268259!3866849!1
X-Originating-IP: [209.85.216.175]
X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32149 invoked from network); 24 Feb 2014 18:57:40 -0000
Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com)
	(209.85.216.175)
	by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	24 Feb 2014 18:57:40 -0000
Received: by mail-qc0-f175.google.com with SMTP id e16so2547667qcx.34
	for ;
	Mon, 24 Feb 2014 10:57:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:cc:content-type;
	bh=C5Q/sQM3qD0x0LCzXl30UOOzqvFkZFQR0xrj/4mDE8M=;
	b=qIGFohBEkl5XrLhGBQX6t5hyuS0HQ66b97JlycdPTo6P2GPwZptr9ym29gWDjcU/3V
	Q3om4BoQEF5QaVKEHXdR9bBJgZ4fUBANjauhk94/r0JlxTQdxwM4JesERgvfk5M7MdJU
	E8T/kH4OJBnBff9C/Zfiw6aVY83b+L53QSh/xJXGtn2oSNGuFlZd2SpvXXu8blJCxw9v
	MurmMpiStJ/tQtctjbsB/uWE6oBiel7+YWB4kKsNE9QELigFvpGgtp4JmRDk67khe0NV
	d7OyBsaH+soHr47zp7P2NLhgPY4Pi295aZk0J/F5xhFS2clL96rx8yezd54QpMcOfX2X
	6wiw==
MIME-Version: 1.0
X-Received: by 10.140.95.179 with SMTP id i48mr30973503qge.1.1393268259343;
	Mon, 24 Feb 2014 10:57:39 -0800 (PST)
Received: by 10.140.89.47 with HTTP; Mon, 24 Feb 2014 10:57:39 -0800 (PST)
Date: Mon, 24 Feb 2014 18:57:39 +0000
Message-ID: 
From: Lars Kurth 
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" , 
	"mirageos-devel@lists.xenproject.org" 
Cc: Russell Pavlicek 
Subject: [MirageOS-devel] Fwd: [Xen Project] Your organization application
	has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2711770353574574554=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============2711770353574574554==
Content-Type: multipart/alternative; boundary=001a11c16dfcacd2c504f32b8ba7

--001a11c16dfcacd2c504f32b8ba7
Content-Type: text/plain; charset=ISO-8859-1

Good news everyone : now the real work awaits.

Cleaning up the project list, etc. and making sure that mentors are signed
up via https://www.google-melange.com/gsoc/homepage/google/gsoc2014, etc. -
Ian Jackson will receive mails from GSoC while I am away and may have to
forward key bits of information to you all.

I would suggest a conference call that includes mentors to tidy the project
list pretty soon. Maybe Russell can act as GSoC master, arrange the call
and chase mentors while I am away. We need to make sure that the project
list is in good shape before the 10th. Ideally by next week.

Also our home page in Melange may needs fixing. @Russell, please read the
mail below and lets discuss tomorrow before I leave.

24 February:19:00 UTCList of accepted mentoring organizations published on
the *Google Summer of Code* 2014 site.Interim Period:Would-be students
discuss project ideas with potential mentoring organizations.28 February
16:00 UTC:IRC meeting with rejected meThe ntoring organizations.10 March:19:00
UTCStudent application period opens.

IMPORTANT: in the application I stated that we encourage students to work
on bite size projects before the application (in the same way as it works
for OPW). Maybe OPW mentors want to share their experiences!

This will come your way in the next few weeks and you really should use
those 2-3 weeks to find out which students can work with you.

Best Regards
Lars

---------- Forwarded message ----------
From: 
Date: 24 Feb 2014 18:41
Subject: [Xen Project] Your organization application has been accepted.
To: 
Cc:

Congratulations!

Your Organization Application for Xen Project to Google Summer of Code 2014
has been accepted. Your organization's information will be auto-populated
from your Organization profile onto our Participating Organizations
page. Please
click
http://www.google-melange.com/gsoc/org/profile/edit/google/gsoc2014/xen_project
if you want to modify your Organization profile. We recommend you take
time to review your profile carefully and add relevant information and
links for the students where applicable.

If you have questions about items on this profile we would recommend you
read over the Melange User's Guide's section titled "Our organization was
accepted! How do I create my organization
homepage?
"

Please be aware the your organization's information is now available to
students, so you should expect to get contact from potential applicants
very soon. If you have any questions, please email Carol Smith directly at
carols@google.com, but generally, you are off to the races. Student
applications formally open on 10 March at 19:00 UTC.

Best regards,

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


Good news everyone : now the re=
al work awaits.

Cleaning up the project list, etc. and making sure that mentors a=
re signed up via=A0https://www.google-melange.com/gsoc/homepage/google/gsoc20=
14, etc. - Ian Jackson will receive mails from GSoC while I am away and=
 may have to forward key bits of information to you all.



I would sug=
gest a conference call that includes mentors to tidy the project list prett=
y soon. Maybe Russell can act as GSoC master, arrange the call and chase me=
ntors while I am away. We need to make sure that the project list is in goo=
d shape before the 10th. Ideally by next week.



Also our ho=
me page in Melange may needs fixing. @Russell, please read the mail below a=
nd lets discuss tomorrow before I leave.







24 February:

19:00 UTC


List of accepted mento=
ring organizations published on the G=
oogle Summer of Code 2014 site.




Interim Period:=




Would-be students discuss project ideas with potential m=
entoring organizations.




28 February 16:00 UTC:=




IRC meeting with rejected meThe ntoring organizations.




10 March:


19:00 UTC



Student application period opens.



IMPORTANT: in the application I stated that we encourage student=
s to work on bite size projects before the application (in the same way as =
it works for OPW). Maybe OPW mentors want to share their experiences!



This will c=
ome your way in the next few weeks and you really should use those 2-3 week=
s to find out which students can work with you.=A0


Best Regards
Lars

---------- Forwarded message ----------
From:  <no-reply@goog=
le-melange.appspotmail.com>

Date: 24 Feb 2014 18:41
Subject: [Xen Project] Your organization applica=
tion has been accepted.

To:  <lar=
s.kurth@xenproject.org>
Cc: 

Congratulations!


Your Organization Application for Xen Pr=
oject to Google Summer of Code 2014 has been accepted.=A0Your organization's information will be auto-popul=
ated from your Organization profile onto our Participating Organizations pa=
ge.=A0Please click http://www.google-melange.com/gsoc/org/profile/edit/googl=
e/gsoc2014/xen_project =A0if you want to modify your Organization profi=
le. We recommend you take time to review your profile carefully and add rel=
evant information and links for the students where applicable.=A0



If you have questions about items on thi=
s profile we would recommend you read over the Melange User's Guide'=
;s section titled "Our organization was accepted! How do=
 I create my organization homepage?"




Please be aware the your organization=
9;s information is now available to students, so you should expect to get c=
ontact from potential applicants very soon. If you have any questions, plea=
se email Carol Smith directly at carols@google.com, but generally, you are off to the races=
. Student applications formally open on 10 March at 19:00 UTC.




Best regards,






--001a11c16dfcacd2c504f32b8ba7--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============2711770353574574554==--


From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 18:57:49 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 18:57: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 1WI0io-0001HI-87; Mon, 24 Feb 2014 18:57:46 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WI0il-0001Gu-Vx
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 18:57:44 +0000
Received: from [85.158.137.68:38594] by server-14.bemta-3.messagelabs.com id
	A0/0F-08196-6269B035; Mon, 24 Feb 2014 18:57:42 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-9.tower-31.messagelabs.com!1393268259!3866849!1
X-Originating-IP: [209.85.216.175]
X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_MESSAGE,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32149 invoked from network); 24 Feb 2014 18:57:40 -0000
Received: from mail-qc0-f175.google.com (HELO mail-qc0-f175.google.com)
	(209.85.216.175)
	by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	24 Feb 2014 18:57:40 -0000
Received: by mail-qc0-f175.google.com with SMTP id e16so2547667qcx.34
	for ;
	Mon, 24 Feb 2014 10:57:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:cc:content-type;
	bh=C5Q/sQM3qD0x0LCzXl30UOOzqvFkZFQR0xrj/4mDE8M=;
	b=qIGFohBEkl5XrLhGBQX6t5hyuS0HQ66b97JlycdPTo6P2GPwZptr9ym29gWDjcU/3V
	Q3om4BoQEF5QaVKEHXdR9bBJgZ4fUBANjauhk94/r0JlxTQdxwM4JesERgvfk5M7MdJU
	E8T/kH4OJBnBff9C/Zfiw6aVY83b+L53QSh/xJXGtn2oSNGuFlZd2SpvXXu8blJCxw9v
	MurmMpiStJ/tQtctjbsB/uWE6oBiel7+YWB4kKsNE9QELigFvpGgtp4JmRDk67khe0NV
	d7OyBsaH+soHr47zp7P2NLhgPY4Pi295aZk0J/F5xhFS2clL96rx8yezd54QpMcOfX2X
	6wiw==
MIME-Version: 1.0
X-Received: by 10.140.95.179 with SMTP id i48mr30973503qge.1.1393268259343;
	Mon, 24 Feb 2014 10:57:39 -0800 (PST)
Received: by 10.140.89.47 with HTTP; Mon, 24 Feb 2014 10:57:39 -0800 (PST)
Date: Mon, 24 Feb 2014 18:57:39 +0000
Message-ID: 
From: Lars Kurth 
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" , 
	"mirageos-devel@lists.xenproject.org" 
Cc: Russell Pavlicek 
Subject: [MirageOS-devel] Fwd: [Xen Project] Your organization application
	has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2711770353574574554=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============2711770353574574554==
Content-Type: multipart/alternative; boundary=001a11c16dfcacd2c504f32b8ba7

--001a11c16dfcacd2c504f32b8ba7
Content-Type: text/plain; charset=ISO-8859-1

Good news everyone : now the real work awaits.

Cleaning up the project list, etc. and making sure that mentors are signed
up via https://www.google-melange.com/gsoc/homepage/google/gsoc2014, etc. -
Ian Jackson will receive mails from GSoC while I am away and may have to
forward key bits of information to you all.

I would suggest a conference call that includes mentors to tidy the project
list pretty soon. Maybe Russell can act as GSoC master, arrange the call
and chase mentors while I am away. We need to make sure that the project
list is in good shape before the 10th. Ideally by next week.

Also our home page in Melange may needs fixing. @Russell, please read the
mail below and lets discuss tomorrow before I leave.

24 February:19:00 UTCList of accepted mentoring organizations published on
the *Google Summer of Code* 2014 site.Interim Period:Would-be students
discuss project ideas with potential mentoring organizations.28 February
16:00 UTC:IRC meeting with rejected meThe ntoring organizations.10 March:19:00
UTCStudent application period opens.

IMPORTANT: in the application I stated that we encourage students to work
on bite size projects before the application (in the same way as it works
for OPW). Maybe OPW mentors want to share their experiences!

This will come your way in the next few weeks and you really should use
those 2-3 weeks to find out which students can work with you.

Best Regards
Lars

---------- Forwarded message ----------
From: 
Date: 24 Feb 2014 18:41
Subject: [Xen Project] Your organization application has been accepted.
To: 
Cc:

Congratulations!

Your Organization Application for Xen Project to Google Summer of Code 2014
has been accepted. Your organization's information will be auto-populated
from your Organization profile onto our Participating Organizations
page. Please
click
http://www.google-melange.com/gsoc/org/profile/edit/google/gsoc2014/xen_project
if you want to modify your Organization profile. We recommend you take
time to review your profile carefully and add relevant information and
links for the students where applicable.

If you have questions about items on this profile we would recommend you
read over the Melange User's Guide's section titled "Our organization was
accepted! How do I create my organization
homepage?
"

Please be aware the your organization's information is now available to
students, so you should expect to get contact from potential applicants
very soon. If you have any questions, please email Carol Smith directly at
carols@google.com, but generally, you are off to the races. Student
applications formally open on 10 March at 19:00 UTC.

Best regards,

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


Good news everyone : now the re=
al work awaits.

Cleaning up the project list, etc. and making sure that mentors a=
re signed up via=A0https://www.google-melange.com/gsoc/homepage/google/gsoc20=
14, etc. - Ian Jackson will receive mails from GSoC while I am away and=
 may have to forward key bits of information to you all.



I would sug=
gest a conference call that includes mentors to tidy the project list prett=
y soon. Maybe Russell can act as GSoC master, arrange the call and chase me=
ntors while I am away. We need to make sure that the project list is in goo=
d shape before the 10th. Ideally by next week.



Also our ho=
me page in Melange may needs fixing. @Russell, please read the mail below a=
nd lets discuss tomorrow before I leave.







24 February:

19:00 UTC


List of accepted mento=
ring organizations published on the G=
oogle Summer of Code 2014 site.




Interim Period:=




Would-be students discuss project ideas with potential m=
entoring organizations.




28 February 16:00 UTC:=




IRC meeting with rejected meThe ntoring organizations.




10 March:


19:00 UTC



Student application period opens.



IMPORTANT: in the application I stated that we encourage student=
s to work on bite size projects before the application (in the same way as =
it works for OPW). Maybe OPW mentors want to share their experiences!



This will c=
ome your way in the next few weeks and you really should use those 2-3 week=
s to find out which students can work with you.=A0


Best Regards
Lars

---------- Forwarded message ----------
From:  <no-reply@goog=
le-melange.appspotmail.com>

Date: 24 Feb 2014 18:41
Subject: [Xen Project] Your organization applica=
tion has been accepted.

To:  <lar=
s.kurth@xenproject.org>
Cc: 

Congratulations!


Your Organization Application for Xen Pr=
oject to Google Summer of Code 2014 has been accepted.=A0Your organization's information will be auto-popul=
ated from your Organization profile onto our Participating Organizations pa=
ge.=A0Please click http://www.google-melange.com/gsoc/org/profile/edit/googl=
e/gsoc2014/xen_project =A0if you want to modify your Organization profi=
le. We recommend you take time to review your profile carefully and add rel=
evant information and links for the students where applicable.=A0



If you have questions about items on thi=
s profile we would recommend you read over the Melange User's Guide'=
;s section titled "Our organization was accepted! How do=
 I create my organization homepage?"




Please be aware the your organization=
9;s information is now available to students, so you should expect to get c=
ontact from potential applicants very soon. If you have any questions, plea=
se email Carol Smith directly at carols@google.com, but generally, you are off to the races=
. Student applications formally open on 10 March at 19:00 UTC.




Best regards,






--001a11c16dfcacd2c504f32b8ba7--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============2711770353574574554==--


From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 23:23:11 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 23:23: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 1WI4rY-0004pX-Sc; Mon, 24 Feb 2014 23:23:04 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WI4rX-0004pS-T5
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 23:23:04 +0000
Received: from [85.158.137.68:49326] by server-1.bemta-3.messagelabs.com id
	41/57-17293-754DB035; Mon, 24 Feb 2014 23:23:03 +0000
X-Env-Sender: avsm@dark.recoil.org
X-Msg-Ref: server-14.tower-31.messagelabs.com!1393284181!3953356!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1429 invoked from network); 24 Feb 2014 23:23:02 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-14.tower-31.messagelabs.com with SMTP;
	24 Feb 2014 23:23:02 -0000
Received: (qmail 8362 invoked by uid 10000); 24 Feb 2014 23:23:01 -0000
Date: Mon, 24 Feb 2014 23:23:01 +0000
From: Anil Madhavapeddy 
To: Lars Kurth 
Message-ID: <20140224232301.GD12291@dark.recoil.org>
References: 
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: 
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Fwd: [Xen Project] Your organization
 application has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

[ dropping CC to just mirageos-devel ]

This is excellent news for us! I have a slight fear that some of the
projects we suggested on the Xen wiki require a good working knowledge of
both Xen and OCaml.  In practise, it's likely that we'll get one or the
other, and so we should take the chance to focus the projects a little
more to ensure that interns can succeed at them (as opposed to the
projects that *we* would like to work on :-)

I particularly like the idea of assigning particular protocol
implementations, or working on a testing framework for (e.g.) cohttp or
the TCP stack.  Something around the cloud deployment scripts or Docker
might also be quite a good place for a budding intern to start with.

Happy to take suggestions: see the existing list here:
http://wiki.xen.org/wiki/GSoc_2014#Mirage_OS

-anil

On Mon, Feb 24, 2014 at 06:57:39PM +0000, Lars Kurth wrote:
> Good news everyone : now the real work awaits.
> 
> Cleaning up the project list, etc. and making sure that mentors are signed
> up via https://www.google-melange.com/gsoc/homepage/google/gsoc2014, etc. -
> Ian Jackson will receive mails from GSoC while I am away and may have to
> forward key bits of information to you all.
> 
> I would suggest a conference call that includes mentors to tidy the project
> list pretty soon. Maybe Russell can act as GSoC master, arrange the call
> and chase mentors while I am away. We need to make sure that the project
> list is in good shape before the 10th. Ideally by next week.
> 
> Also our home page in Melange may needs fixing. @Russell, please read the
> mail below and lets discuss tomorrow before I leave.
> 
> 24 February:19:00 UTCList of accepted mentoring organizations published on
> the *Google Summer of Code* 2014 site.Interim Period:Would-be students
> discuss project ideas with potential mentoring organizations.28 February
> 16:00 UTC:IRC meeting with rejected meThe ntoring organizations.10 March:19:00
> UTCStudent application period opens.
> 
> IMPORTANT: in the application I stated that we encourage students to work
> on bite size projects before the application (in the same way as it works
> for OPW). Maybe OPW mentors want to share their experiences!
> 
> This will come your way in the next few weeks and you really should use
> those 2-3 weeks to find out which students can work with you.
> 
> Best Regards
> Lars
> 
> ---------- Forwarded message ----------
> From: 
> Date: 24 Feb 2014 18:41
> Subject: [Xen Project] Your organization application has been accepted.
> To: 
> Cc:
> 
> Congratulations!
> 
> Your Organization Application for Xen Project to Google Summer of Code 2014
> has been accepted. Your organization's information will be auto-populated
> from your Organization profile onto our Participating Organizations
> page. Please
> click
> http://www.google-melange.com/gsoc/org/profile/edit/google/gsoc2014/xen_project
> if you want to modify your Organization profile. We recommend you take
> time to review your profile carefully and add relevant information and
> links for the students where applicable.
> 
> If you have questions about items on this profile we would recommend you
> read over the Melange User's Guide's section titled "Our organization was
> accepted! How do I create my organization
> homepage?
> "
> 
> Please be aware the your organization's information is now available to
> students, so you should expect to get contact from potential applicants
> very soon. If you have any questions, please email Carol Smith directly at
> carols@google.com, but generally, you are off to the races. Student
> applications formally open on 10 March at 19:00 UTC.
> 
> Best regards,

> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Mon Feb 24 23:23:11 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Mon, 24 Feb 2014 23:23: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 1WI4rY-0004pX-Sc; Mon, 24 Feb 2014 23:23:04 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WI4rX-0004pS-T5
	for mirageos-devel@lists.xenproject.org; Mon, 24 Feb 2014 23:23:04 +0000
Received: from [85.158.137.68:49326] by server-1.bemta-3.messagelabs.com id
	41/57-17293-754DB035; Mon, 24 Feb 2014 23:23:03 +0000
X-Env-Sender: avsm@dark.recoil.org
X-Msg-Ref: server-14.tower-31.messagelabs.com!1393284181!3953356!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1429 invoked from network); 24 Feb 2014 23:23:02 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-14.tower-31.messagelabs.com with SMTP;
	24 Feb 2014 23:23:02 -0000
Received: (qmail 8362 invoked by uid 10000); 24 Feb 2014 23:23:01 -0000
Date: Mon, 24 Feb 2014 23:23:01 +0000
From: Anil Madhavapeddy 
To: Lars Kurth 
Message-ID: <20140224232301.GD12291@dark.recoil.org>
References: 
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: 
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Fwd: [Xen Project] Your organization
 application has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

[ dropping CC to just mirageos-devel ]

This is excellent news for us! I have a slight fear that some of the
projects we suggested on the Xen wiki require a good working knowledge of
both Xen and OCaml.  In practise, it's likely that we'll get one or the
other, and so we should take the chance to focus the projects a little
more to ensure that interns can succeed at them (as opposed to the
projects that *we* would like to work on :-)

I particularly like the idea of assigning particular protocol
implementations, or working on a testing framework for (e.g.) cohttp or
the TCP stack.  Something around the cloud deployment scripts or Docker
might also be quite a good place for a budding intern to start with.

Happy to take suggestions: see the existing list here:
http://wiki.xen.org/wiki/GSoc_2014#Mirage_OS

-anil

On Mon, Feb 24, 2014 at 06:57:39PM +0000, Lars Kurth wrote:
> Good news everyone : now the real work awaits.
> 
> Cleaning up the project list, etc. and making sure that mentors are signed
> up via https://www.google-melange.com/gsoc/homepage/google/gsoc2014, etc. -
> Ian Jackson will receive mails from GSoC while I am away and may have to
> forward key bits of information to you all.
> 
> I would suggest a conference call that includes mentors to tidy the project
> list pretty soon. Maybe Russell can act as GSoC master, arrange the call
> and chase mentors while I am away. We need to make sure that the project
> list is in good shape before the 10th. Ideally by next week.
> 
> Also our home page in Melange may needs fixing. @Russell, please read the
> mail below and lets discuss tomorrow before I leave.
> 
> 24 February:19:00 UTCList of accepted mentoring organizations published on
> the *Google Summer of Code* 2014 site.Interim Period:Would-be students
> discuss project ideas with potential mentoring organizations.28 February
> 16:00 UTC:IRC meeting with rejected meThe ntoring organizations.10 March:19:00
> UTCStudent application period opens.
> 
> IMPORTANT: in the application I stated that we encourage students to work
> on bite size projects before the application (in the same way as it works
> for OPW). Maybe OPW mentors want to share their experiences!
> 
> This will come your way in the next few weeks and you really should use
> those 2-3 weeks to find out which students can work with you.
> 
> Best Regards
> Lars
> 
> ---------- Forwarded message ----------
> From: 
> Date: 24 Feb 2014 18:41
> Subject: [Xen Project] Your organization application has been accepted.
> To: 
> Cc:
> 
> Congratulations!
> 
> Your Organization Application for Xen Project to Google Summer of Code 2014
> has been accepted. Your organization's information will be auto-populated
> from your Organization profile onto our Participating Organizations
> page. Please
> click
> http://www.google-melange.com/gsoc/org/profile/edit/google/gsoc2014/xen_project
> if you want to modify your Organization profile. We recommend you take
> time to review your profile carefully and add relevant information and
> links for the students where applicable.
> 
> If you have questions about items on this profile we would recommend you
> read over the Melange User's Guide's section titled "Our organization was
> accepted! How do I create my organization
> homepage?
> "
> 
> Please be aware the your organization's information is now available to
> students, so you should expect to get contact from potential applicants
> very soon. If you have any questions, please email Carol Smith directly at
> carols@google.com, but generally, you are off to the races. Student
> applications formally open on 10 March at 19:00 UTC.
> 
> Best regards,

> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 10:34:47 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 10:34: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 1WIFLV-00083q-20; Tue, 25 Feb 2014 10:34:41 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIFLT-00083c-TO
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 10:34:40 +0000
Received: from [85.158.137.68:58073] by server-9.bemta-3.messagelabs.com id
	79/B5-10184-FB17C035; Tue, 25 Feb 2014 10:34:39 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-15.tower-31.messagelabs.com!1393324478!4049030!1
X-Originating-IP: [74.125.82.52]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5305 invoked from network); 25 Feb 2014 10:34:38 -0000
Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com)
	(74.125.82.52)
	by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	25 Feb 2014 10:34:38 -0000
Received: by mail-wg0-f52.google.com with SMTP id k14so180317wgh.35
	for ;
	Tue, 25 Feb 2014 02:34:38 -0800 (PST)
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=MZ6jHj+8p7E6bCgmrdZ3WoVmEtkaVvGqm7F+ifBLFuc=;
	b=YNpG9laiIJbvh3w/xXNtUY6Q102azff20iO+KnLTG8J9SeDQ+9Wm5Og4Zymv2kSsEP
	XVqbNsSKZSK1vCBKZlQPqzlQKvYjJXhqJ2k8WZxgdUJ1IzYFUP76nOAqevBjlLsL8suO
	p0DF2FWSMbbqmeQ9sQuKcWZQoqjne456mTn56pg+EqTTUX5nbqesiNcAxg1m21uSw9wC
	gtMUX17qSwtxgLP7Ncce0tHqVkxkzigpudWw41etVSnuIceNIEtN0MEWXWPmjbfLcY2l
	73B/H6x4cZZtDGxOqRSQ7g50TZ6xBYRxDcUc5M1KtGqetS6aE2g/+06JjzwNTORFAO60
	3Xkw==
X-Received: by 10.180.102.97 with SMTP id fn1mr2005013wib.15.1393324478058;
	Tue, 25 Feb 2014 02:34:38 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id fo6sm32765953wib.7.2014.02.25.02.34.33
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 25 Feb 2014 02:34:35 -0800 (PST)
Message-ID: <530C71B7.1030407@xen.org>
Date: Tue, 25 Feb 2014 10:34:31 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Anil Madhavapeddy , Lars Kurth 
References: 
	<20140224232301.GD12291@dark.recoil.org>
In-Reply-To: <20140224232301.GD12291@dark.recoil.org>
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Fwd: [Xen Project] Your organization
 application has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 24/02/2014 23:23, Anil Madhavapeddy wrote:
> [ dropping CC to just mirageos-devel ]
>
> This is excellent news for us! I have a slight fear that some of the
> projects we suggested on the Xen wiki require a good working knowledge of
> both Xen and OCaml.  In practise, it's likely that we'll get one or the
> other, and so we should take the chance to focus the projects a little
> more to ensure that interns can succeed at them (as opposed to the
> projects that *we* would like to work on :-)
Maybe you can add easier projects to the list, or break existing 
projects into pieces?
Any mentors, please create accounts on melange
* aka https://www.google-melange.com/gsoc/homepage/google/gsoc2014
* sign in
* and fill out 
https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 - 
"chose Xen Project"

Regards
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 10:34:47 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 10:34: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 1WIFLV-00083q-20; Tue, 25 Feb 2014 10:34:41 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIFLT-00083c-TO
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 10:34:40 +0000
Received: from [85.158.137.68:58073] by server-9.bemta-3.messagelabs.com id
	79/B5-10184-FB17C035; Tue, 25 Feb 2014 10:34:39 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-15.tower-31.messagelabs.com!1393324478!4049030!1
X-Originating-IP: [74.125.82.52]
X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5305 invoked from network); 25 Feb 2014 10:34:38 -0000
Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com)
	(74.125.82.52)
	by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	25 Feb 2014 10:34:38 -0000
Received: by mail-wg0-f52.google.com with SMTP id k14so180317wgh.35
	for ;
	Tue, 25 Feb 2014 02:34:38 -0800 (PST)
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=MZ6jHj+8p7E6bCgmrdZ3WoVmEtkaVvGqm7F+ifBLFuc=;
	b=YNpG9laiIJbvh3w/xXNtUY6Q102azff20iO+KnLTG8J9SeDQ+9Wm5Og4Zymv2kSsEP
	XVqbNsSKZSK1vCBKZlQPqzlQKvYjJXhqJ2k8WZxgdUJ1IzYFUP76nOAqevBjlLsL8suO
	p0DF2FWSMbbqmeQ9sQuKcWZQoqjne456mTn56pg+EqTTUX5nbqesiNcAxg1m21uSw9wC
	gtMUX17qSwtxgLP7Ncce0tHqVkxkzigpudWw41etVSnuIceNIEtN0MEWXWPmjbfLcY2l
	73B/H6x4cZZtDGxOqRSQ7g50TZ6xBYRxDcUc5M1KtGqetS6aE2g/+06JjzwNTORFAO60
	3Xkw==
X-Received: by 10.180.102.97 with SMTP id fn1mr2005013wib.15.1393324478058;
	Tue, 25 Feb 2014 02:34:38 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id fo6sm32765953wib.7.2014.02.25.02.34.33
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 25 Feb 2014 02:34:35 -0800 (PST)
Message-ID: <530C71B7.1030407@xen.org>
Date: Tue, 25 Feb 2014 10:34:31 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Anil Madhavapeddy , Lars Kurth 
References: 
	<20140224232301.GD12291@dark.recoil.org>
In-Reply-To: <20140224232301.GD12291@dark.recoil.org>
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Fwd: [Xen Project] Your organization
 application has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 24/02/2014 23:23, Anil Madhavapeddy wrote:
> [ dropping CC to just mirageos-devel ]
>
> This is excellent news for us! I have a slight fear that some of the
> projects we suggested on the Xen wiki require a good working knowledge of
> both Xen and OCaml.  In practise, it's likely that we'll get one or the
> other, and so we should take the chance to focus the projects a little
> more to ensure that interns can succeed at them (as opposed to the
> projects that *we* would like to work on :-)
Maybe you can add easier projects to the list, or break existing 
projects into pieces?
Any mentors, please create accounts on melange
* aka https://www.google-melange.com/gsoc/homepage/google/gsoc2014
* sign in
* and fill out 
https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 - 
"chose Xen Project"

Regards
Lars

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 13:39:02 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 13:39: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 1WIIDo-0004L6-GP; Tue, 25 Feb 2014 13:38:56 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIIDn-0004Kh-NX
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 13:38:55 +0000
Received: from [85.158.137.68:55286] by server-1.bemta-3.messagelabs.com id
	3B/ED-17293-EEC9C035; Tue, 25 Feb 2014 13:38:54 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-3.tower-31.messagelabs.com!1393335533!4096304!1
X-Originating-IP: [74.125.82.50]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3668 invoked from network); 25 Feb 2014 13:38:53 -0000
Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com)
	(74.125.82.50)
	by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	25 Feb 2014 13:38:53 -0000
Received: by mail-wg0-f50.google.com with SMTP id l18so399321wgh.21
	for ;
	Tue, 25 Feb 2014 05:38:53 -0800 (PST)
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:content-type;
	bh=fVGCtSX+ZqWy2KgGF82KYXLUK8P0LSuk7J92T5HqbB8=;
	b=luZYsb1F+Nu6Wkc5PlD0+SajGzYe7Inx+sAGgS1bhnVNtd/9TXiAHoyH/rK6/Gb8XW
	dSjTJF0czpqZtdZDZ1BAE7d5+pQLtOBFyC+Sljc50uqGnsAeCv0EDJyCFY7mvJvZB1Pr
	drFBslxc0C0ODWccJR2JagAq1lYuTHdQ2Ad/k1pnqzeGrYrdbq5FMPyNgTmFOurY4D8R
	DSnKRI0fCaBgMhwEFGTdr+vMALzLCk2/ZWB0lG281mYP/mNc9S/EqqreajGC1gHOXfz5
	LTZkaRnLQsb+8EcnvPdC57Z+t/h3v9q4XM7+RpnqL8d3eJWYVIuaEhUur8LddvLBn8YC
	yv3g==
X-Received: by 10.194.71.116 with SMTP id t20mr2699924wju.51.1393335506220;
	Tue, 25 Feb 2014 05:38:26 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id fo6sm293464wib.7.2014.02.25.05.38.24
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 25 Feb 2014 05:38:25 -0800 (PST)
Message-ID: <530C9CD0.9070508@xen.org>
Date: Tue, 25 Feb 2014 13:38:24 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org" 
Cc: Russell Pavlicek 
Subject: [MirageOS-devel] Dates and Location Xen Project Hackathon,
 Xen Project Developer Summit & Meeting
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0625079911121714150=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============0625079911121714150==
Content-Type: multipart/alternative;
 boundary="------------040001070605010308090103"

This is a multi-part message in MIME format.
--------------040001070605010308090103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

before I go on holidays just a quick note in the 2014 event schedule. 
This only just came together, but you may want to look into getting 
travel approvals.

== Xen Project Hackatho, London, late May (exact dates TBD) ==
Location: London at Rackspaces offices
Dates: exact dates TBD, but a we are targetting a Thu/Fri at the end of May
URL: http://wiki.xenproject.org/wiki/Hackathon/May2014

== Xen Project Developer Summit ==
Location: Chicago, IL, USA
Dates: August 18-19
CFP: open now, closes */May 2, 2014 /*- see 
http://events.linuxfoundation.org/events/xen-project-developer-summit/program/cfp
URL: http://events.linuxfoundation.org/events/xen-project-developer-summit

I am looking for Program Management Committee members.

== Xen Project Developer Meeting ==
Location: Chicago, IL, USA
Dates: August 20
More details to follow. We have the option to do a 1/2 day, a full day 
or 1/2 day with a Hacker space

Best Regards
Lars
P.S.: Apologies to those who were looking for a Hackathon in Amsterdam (-:

--------------040001070605010308090103
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    Hi all,

    

    before I go on holidays just a quick note in the 2014 event
    schedule. This only just came together, but you may want to look
    into getting travel approvals.

    

    == Xen Project Hackatho, London, late May (exact dates TBD) ==

    Location: London at Rackspaces offices  

    Dates: exact dates TBD, but a we are targetting a Thu/Fri at the end
    of May

    URL: http://wiki.xenproject.org/wiki/Hackathon/May2014

    

    == Xen Project Developer Summit == 

    Location: Chicago, IL, USA

    Dates: August 18-19

    CFP: open now, closes May 2, 2014 - see
http://events.linuxfoundation.org/events/xen-project-developer-summit/program/cfp

    URL:
    http://events.linuxfoundation.org/events/xen-project-developer-summit

    

    I am looking for Program Management Committee members.

    

    == Xen Project Developer Meeting == 

    Location: Chicago, IL, USA

    Dates: August 20

    More details to follow. We have the option to do a 1/2 day, a full
    day or 1/2 day with a Hacker space

    

    Best Regards

    Lars

    P.S.: Apologies to those who were looking for a Hackathon in
    Amsterdam (-:

  


--------------040001070605010308090103--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============0625079911121714150==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 13:39:02 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 13:39: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 1WIIDo-0004L6-GP; Tue, 25 Feb 2014 13:38:56 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIIDn-0004Kh-NX
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 13:38:55 +0000
Received: from [85.158.137.68:55286] by server-1.bemta-3.messagelabs.com id
	3B/ED-17293-EEC9C035; Tue, 25 Feb 2014 13:38:54 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-3.tower-31.messagelabs.com!1393335533!4096304!1
X-Originating-IP: [74.125.82.50]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3668 invoked from network); 25 Feb 2014 13:38:53 -0000
Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com)
	(74.125.82.50)
	by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	25 Feb 2014 13:38:53 -0000
Received: by mail-wg0-f50.google.com with SMTP id l18so399321wgh.21
	for ;
	Tue, 25 Feb 2014 05:38:53 -0800 (PST)
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:content-type;
	bh=fVGCtSX+ZqWy2KgGF82KYXLUK8P0LSuk7J92T5HqbB8=;
	b=luZYsb1F+Nu6Wkc5PlD0+SajGzYe7Inx+sAGgS1bhnVNtd/9TXiAHoyH/rK6/Gb8XW
	dSjTJF0czpqZtdZDZ1BAE7d5+pQLtOBFyC+Sljc50uqGnsAeCv0EDJyCFY7mvJvZB1Pr
	drFBslxc0C0ODWccJR2JagAq1lYuTHdQ2Ad/k1pnqzeGrYrdbq5FMPyNgTmFOurY4D8R
	DSnKRI0fCaBgMhwEFGTdr+vMALzLCk2/ZWB0lG281mYP/mNc9S/EqqreajGC1gHOXfz5
	LTZkaRnLQsb+8EcnvPdC57Z+t/h3v9q4XM7+RpnqL8d3eJWYVIuaEhUur8LddvLBn8YC
	yv3g==
X-Received: by 10.194.71.116 with SMTP id t20mr2699924wju.51.1393335506220;
	Tue, 25 Feb 2014 05:38:26 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id fo6sm293464wib.7.2014.02.25.05.38.24
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 25 Feb 2014 05:38:25 -0800 (PST)
Message-ID: <530C9CD0.9070508@xen.org>
Date: Tue, 25 Feb 2014 13:38:24 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org" 
Cc: Russell Pavlicek 
Subject: [MirageOS-devel] Dates and Location Xen Project Hackathon,
 Xen Project Developer Summit & Meeting
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============0625079911121714150=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============0625079911121714150==
Content-Type: multipart/alternative;
 boundary="------------040001070605010308090103"

This is a multi-part message in MIME format.
--------------040001070605010308090103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

before I go on holidays just a quick note in the 2014 event schedule. 
This only just came together, but you may want to look into getting 
travel approvals.

== Xen Project Hackatho, London, late May (exact dates TBD) ==
Location: London at Rackspaces offices
Dates: exact dates TBD, but a we are targetting a Thu/Fri at the end of May
URL: http://wiki.xenproject.org/wiki/Hackathon/May2014

== Xen Project Developer Summit ==
Location: Chicago, IL, USA
Dates: August 18-19
CFP: open now, closes */May 2, 2014 /*- see 
http://events.linuxfoundation.org/events/xen-project-developer-summit/program/cfp
URL: http://events.linuxfoundation.org/events/xen-project-developer-summit

I am looking for Program Management Committee members.

== Xen Project Developer Meeting ==
Location: Chicago, IL, USA
Dates: August 20
More details to follow. We have the option to do a 1/2 day, a full day 
or 1/2 day with a Hacker space

Best Regards
Lars
P.S.: Apologies to those who were looking for a Hackathon in Amsterdam (-:

--------------040001070605010308090103
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    Hi all,

    

    before I go on holidays just a quick note in the 2014 event
    schedule. This only just came together, but you may want to look
    into getting travel approvals.

    

    == Xen Project Hackatho, London, late May (exact dates TBD) ==

    Location: London at Rackspaces offices  

    Dates: exact dates TBD, but a we are targetting a Thu/Fri at the end
    of May

    URL: http://wiki.xenproject.org/wiki/Hackathon/May2014

    

    == Xen Project Developer Summit == 

    Location: Chicago, IL, USA

    Dates: August 18-19

    CFP: open now, closes May 2, 2014 - see
http://events.linuxfoundation.org/events/xen-project-developer-summit/program/cfp

    URL:
    http://events.linuxfoundation.org/events/xen-project-developer-summit

    

    I am looking for Program Management Committee members.

    

    == Xen Project Developer Meeting == 

    Location: Chicago, IL, USA

    Dates: August 20

    More details to follow. We have the option to do a 1/2 day, a full
    day or 1/2 day with a Hacker space

    

    Best Regards

    Lars

    P.S.: Apologies to those who were looking for a Hackathon in
    Amsterdam (-:

  


--------------040001070605010308090103--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============0625079911121714150==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 16:07:23 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 16:07: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 1WIKXP-0006CV-Jy; Tue, 25 Feb 2014 16:07:19 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIKXO-0006CL-Ei
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 16:07:18 +0000
Received: from [193.109.254.147:14847] by server-13.bemta-14.messagelabs.com
	id 67/BE-01226-5BFBC035; Tue, 25 Feb 2014 16:07:17 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-6.tower-27.messagelabs.com!1393344435!6739315!1
X-Originating-IP: [74.125.82.44]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29521 invoked from network); 25 Feb 2014 16:07:16 -0000
Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com)
	(74.125.82.44)
	by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	25 Feb 2014 16:07:16 -0000
Received: by mail-wg0-f44.google.com with SMTP id a1so577525wgh.15
	for ;
	Tue, 25 Feb 2014 08:07:15 -0800 (PST)
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:content-type;
	bh=T77tpPpQD/gB2hLfPb1wFw3Ytmfqk8qRwBttDBh3y10=;
	b=RbN8uUEqE45VUWhWKm7ibuywzOE/+sWGJNSdv8SWhRtKFvkYjO6+Nqv3D5KPvm6pgh
	vEi9RNBo7SCkp2XiuZag6gu3MCS9PoO66VWzKT7GEM5Z4OSZH7DchRmiXmXa3QlpIWX4
	ZvYKthCk+XhW9izJgHvdDkGgSazdHXsLtvtB7jpYuAAsdKLd9+SJx3MeuB5vPkXqZVRM
	Pqh0mLmqFNgz87rpShd1B0cFrPpxgPO0NrKSp4w+1qB3bBw7zeBdkuqiiLY7h+wdOrAQ
	epgTo0spI/cFLk2nxICAADsE1TKAd26jQokzKUVinb/MQ3QE9jsSw7Kfx0GRyD6rs8iE
	/eVg==
X-Received: by 10.194.90.177 with SMTP id bx17mr764921wjb.91.1393344435616;
	Tue, 25 Feb 2014 08:07:15 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id r1sm1410116wia.5.2014.02.25.08.07.14
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 25 Feb 2014 08:07:14 -0800 (PST)
Message-ID: <530CBFB1.5040907@xen.org>
Date: Tue, 25 Feb 2014 16:07:13 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org" 
Cc: Russell Pavlicek 
Subject: [MirageOS-devel] Next steps for GSoC and OPW mentors
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2622497764315505697=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============2622497764315505697==
Content-Type: multipart/alternative;
 boundary="------------040201090704040905090500"

This is a multi-part message in MIME format.
--------------040201090704040905090500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

you may have seen the announcement that the Xen Project and that we are 
also participating in round 8 of the Outreach Program for Women. The 
portals for both programs are here:
* http://wiki.xenproject.org/wiki/GSoc_2014
* http://wiki.xenproject.org/wiki/OutreachProgramForWomen/Round8

Both programs have a very similar structure: the main difference are 
differences in application deadlines and forms. As I will be on holidays 
in the coming weeks, Russell volunteered to help coordinate activities 
related to both programs. He also has administrator rights for the 
Google GSoC system

The other main difference is that OPW requires applicants to make a code 
contribution *before* the application. This requires working with the 
mentor and a reference to the contribution in the application. This can 
be a bug fix, code refactoring, writing a test case, etc. and is 
designed to get interns familiar with the tooling and culture in the 
project.

Although we do not require GSoC students to submit code before they 
apply, we *strongly encourage* them to do so and the application form is 
designed to encourage references to a students first contributions 
(bugs, wiki, etc.) and public communications on mailing lists. See 
http://wiki.xenproject.org/wiki/GSoc_2014#Finding_a_project_that_fits_you

== Program Mangement Committee for Mentors ==
To manage both programs, I propose that we set up a Commitee made up of 
3-4 experienced GSoc and OPW mentors and former GSoC students to sanity 
check and review project proposals and provide advice to other mentors. 
Better the project proposals = happier mentors = happier 
students/interns = better outcome for the Xen Project and students.

Russell volunteered to reach out to candidates for the committee and to 
organize the first meetings (ideally sometimes next week). Once we have 
all applications in and mentors signed up, the committe would become a 
regular meeting for all mentors across GSoC and OPW who are mentoring 
students. We also need to decide which students to accept for both 
programs by April 18.

For mentors: please make sure that you only take on one intern or 
student. Mentoring more than one student is too hard.

== OPW ==
Intern application deadline: March 18th
Close of Intern Selection: April 18
Accepted participants announced: April 21
Internship Period: May 19 - August 18

Request to mentors:
* please update your projects on 
http://wiki.xenproject.org/wiki/OutreachProgramForWomen/Round8
* please hang out on the #xen-opw channel in the coming weeks, if you 
can and engage with interns
* please give interns small achievable tasks (on a public list) that 
help us identify whether the intern can can complete a project, prior to 
the application. This can be a bug fix, code refactoring, writing a test 
case, etc. and is designed to get interns familiar with the tooling and 
culture in the project.

== Google Summer of Code ==
Student application deadline: March 21th
Close of Student Selection: April 18
Accepted participants announced: April 21
Coding Period: May 19 - August 18

Request to mentors:
* please update your projects on http://wiki.xenproject.org/wiki/GSoc_2014
* please sign up to the GSoC website, aka
** create an account on 
https://www.google-melange.com/gsoc/homepage/google/gsoc2014
** sign in
** fill out 
https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 - 
"chose Xen Project"
* please hang out on the #xen-opw channel in the coming weeks, if you 
can and engage with students
* please give students small achievable tasks (on a public list) that 
help us identify whether the student can complete a project, prior to 
the application. This can be a bug fix, code refactoring, writing a test 
case, etc. and is designed to get students familiar with the tooling and 
culture in the project.

Best Regards
Lars

--------------040201090704040905090500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    Hi all,

    

    you may have seen the announcement that the Xen Project and that we
    are also participating in round 8 of the Outreach Program for Women.
    The portals for both programs are here:

    * http://wiki.xenproject.org/wiki/GSoc_2014

    * http://wiki.xenproject.org/wiki/OutreachProgramForWomen/Round8

    

    Both programs have a very similar structure: the main difference are
    differences in application deadlines and forms. As I will be on
    holidays in the coming weeks, Russell volunteered to help coordinate
    activities related to both programs. He also has administrator
    rights for the Google GSoC system

    

    The other main difference is that OPW requires applicants to make a
    code contribution *before* the application. This requires working
    with the mentor and a reference to the contribution in the
    application. This can be a bug fix, code refactoring, writing a test
    case, etc. and is designed to get interns familiar with the tooling
    and culture in the project.

    

    Although we do not require GSoC students to submit code before they
    apply, we *strongly encourage* them to do so and the application
    form is designed to encourage references to a students first
    contributions (bugs, wiki, etc.) and public communications on
    mailing lists. See
    http://wiki.xenproject.org/wiki/GSoc_2014#Finding_a_project_that_fits_you
    

    

    == Program Mangement Committee for Mentors ==

    To manage both programs, I propose that we set up a Commitee made up
    of 3-4 experienced GSoc and OPW mentors and former GSoC students to
    sanity check and review project proposals and provide advice to
    other mentors. Better the project proposals = happier mentors =
    happier students/interns = better outcome for the Xen Project and
    students. 

    

    Russell volunteered to reach out to candidates for the committee and
    to organize the first meetings (ideally sometimes next week). Once
    we have all applications in and mentors signed up, the committe
    would become a regular meeting for all mentors across GSoC and OPW
    who are mentoring students. We also need to decide which students to
    accept for both programs by April 18.

    

    For mentors: please make sure that you only take on one intern or
    student. Mentoring more than one student is too hard.

    

    == OPW ==

    Intern application deadline: March 18th

    Close of Intern Selection: April 18

    Accepted participants announced : April 21

    Internship Period: May 19 - August 18

      

    Request to mentors: 

    * please update your projects on
    http://wiki.xenproject.org/wiki/OutreachProgramForWomen/Round8

    * please hang out on the #xen-opw channel in the coming weeks, if
    you can and engage with interns

    * please give interns small achievable tasks (on a public list) that
    help us identify whether the intern can can complete a project,
    prior to the application. This can be a bug fix, code refactoring,
    writing a test case, etc. and is designed to get interns familiar
    with the tooling and culture in the project.

    

    == Google Summer of Code ==

    Student application deadline: March 21th

    Close of Student Selection: April 18

    Accepted participants announced : April 21

    Coding Period: May 19 - August 18

        

      Request to mentors: 

    * please update your projects on
    http://wiki.xenproject.org/wiki/GSoc_2014

    * please sign up to the GSoC website, aka

    ** create an account on https://www.google-melange.com/gsoc/homepage/google/gsoc2014
    

    ** sign in

    ** fill out https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014
    - "chose Xen Project"
    

    * please hang out on the #xen-opw channel in the coming weeks, if
    you can and engage with students

    * please give students small achievable tasks (on a public list)
    that help us identify whether the student can complete a project,
    prior to the application. This can be a bug fix, code refactoring,
    writing a test case, etc. and is designed to get students familiar
    with the tooling and culture in the project.

    

    Best Regards
    

    Lars
  


--------------040201090704040905090500--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============2622497764315505697==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 16:07:23 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 16:07: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 1WIKXP-0006CV-Jy; Tue, 25 Feb 2014 16:07:19 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIKXO-0006CL-Ei
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 16:07:18 +0000
Received: from [193.109.254.147:14847] by server-13.bemta-14.messagelabs.com
	id 67/BE-01226-5BFBC035; Tue, 25 Feb 2014 16:07:17 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-6.tower-27.messagelabs.com!1393344435!6739315!1
X-Originating-IP: [74.125.82.44]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	RCVD_ILLEGAL_IP
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29521 invoked from network); 25 Feb 2014 16:07:16 -0000
Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com)
	(74.125.82.44)
	by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	25 Feb 2014 16:07:16 -0000
Received: by mail-wg0-f44.google.com with SMTP id a1so577525wgh.15
	for ;
	Tue, 25 Feb 2014 08:07:15 -0800 (PST)
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:content-type;
	bh=T77tpPpQD/gB2hLfPb1wFw3Ytmfqk8qRwBttDBh3y10=;
	b=RbN8uUEqE45VUWhWKm7ibuywzOE/+sWGJNSdv8SWhRtKFvkYjO6+Nqv3D5KPvm6pgh
	vEi9RNBo7SCkp2XiuZag6gu3MCS9PoO66VWzKT7GEM5Z4OSZH7DchRmiXmXa3QlpIWX4
	ZvYKthCk+XhW9izJgHvdDkGgSazdHXsLtvtB7jpYuAAsdKLd9+SJx3MeuB5vPkXqZVRM
	Pqh0mLmqFNgz87rpShd1B0cFrPpxgPO0NrKSp4w+1qB3bBw7zeBdkuqiiLY7h+wdOrAQ
	epgTo0spI/cFLk2nxICAADsE1TKAd26jQokzKUVinb/MQ3QE9jsSw7Kfx0GRyD6rs8iE
	/eVg==
X-Received: by 10.194.90.177 with SMTP id bx17mr764921wjb.91.1393344435616;
	Tue, 25 Feb 2014 08:07:15 -0800 (PST)
Received: from [172.16.25.10] ([2.122.219.75])
	by mx.google.com with ESMTPSA id r1sm1410116wia.5.2014.02.25.08.07.14
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 25 Feb 2014 08:07:14 -0800 (PST)
Message-ID: <530CBFB1.5040907@xen.org>
Date: Tue, 25 Feb 2014 16:07:13 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org" 
Cc: Russell Pavlicek 
Subject: [MirageOS-devel] Next steps for GSoC and OPW mentors
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============2622497764315505697=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============2622497764315505697==
Content-Type: multipart/alternative;
 boundary="------------040201090704040905090500"

This is a multi-part message in MIME format.
--------------040201090704040905090500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

you may have seen the announcement that the Xen Project and that we are 
also participating in round 8 of the Outreach Program for Women. The 
portals for both programs are here:
* http://wiki.xenproject.org/wiki/GSoc_2014
* http://wiki.xenproject.org/wiki/OutreachProgramForWomen/Round8

Both programs have a very similar structure: the main difference are 
differences in application deadlines and forms. As I will be on holidays 
in the coming weeks, Russell volunteered to help coordinate activities 
related to both programs. He also has administrator rights for the 
Google GSoC system

The other main difference is that OPW requires applicants to make a code 
contribution *before* the application. This requires working with the 
mentor and a reference to the contribution in the application. This can 
be a bug fix, code refactoring, writing a test case, etc. and is 
designed to get interns familiar with the tooling and culture in the 
project.

Although we do not require GSoC students to submit code before they 
apply, we *strongly encourage* them to do so and the application form is 
designed to encourage references to a students first contributions 
(bugs, wiki, etc.) and public communications on mailing lists. See 
http://wiki.xenproject.org/wiki/GSoc_2014#Finding_a_project_that_fits_you

== Program Mangement Committee for Mentors ==
To manage both programs, I propose that we set up a Commitee made up of 
3-4 experienced GSoc and OPW mentors and former GSoC students to sanity 
check and review project proposals and provide advice to other mentors. 
Better the project proposals = happier mentors = happier 
students/interns = better outcome for the Xen Project and students.

Russell volunteered to reach out to candidates for the committee and to 
organize the first meetings (ideally sometimes next week). Once we have 
all applications in and mentors signed up, the committe would become a 
regular meeting for all mentors across GSoC and OPW who are mentoring 
students. We also need to decide which students to accept for both 
programs by April 18.

For mentors: please make sure that you only take on one intern or 
student. Mentoring more than one student is too hard.

== OPW ==
Intern application deadline: March 18th
Close of Intern Selection: April 18
Accepted participants announced: April 21
Internship Period: May 19 - August 18

Request to mentors:
* please update your projects on 
http://wiki.xenproject.org/wiki/OutreachProgramForWomen/Round8
* please hang out on the #xen-opw channel in the coming weeks, if you 
can and engage with interns
* please give interns small achievable tasks (on a public list) that 
help us identify whether the intern can can complete a project, prior to 
the application. This can be a bug fix, code refactoring, writing a test 
case, etc. and is designed to get interns familiar with the tooling and 
culture in the project.

== Google Summer of Code ==
Student application deadline: March 21th
Close of Student Selection: April 18
Accepted participants announced: April 21
Coding Period: May 19 - August 18

Request to mentors:
* please update your projects on http://wiki.xenproject.org/wiki/GSoc_2014
* please sign up to the GSoC website, aka
** create an account on 
https://www.google-melange.com/gsoc/homepage/google/gsoc2014
** sign in
** fill out 
https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 - 
"chose Xen Project"
* please hang out on the #xen-opw channel in the coming weeks, if you 
can and engage with students
* please give students small achievable tasks (on a public list) that 
help us identify whether the student can complete a project, prior to 
the application. This can be a bug fix, code refactoring, writing a test 
case, etc. and is designed to get students familiar with the tooling and 
culture in the project.

Best Regards
Lars

--------------040201090704040905090500
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  

    
  
  
    Hi all,

    

    you may have seen the announcement that the Xen Project and that we
    are also participating in round 8 of the Outreach Program for Women.
    The portals for both programs are here:

    * http://wiki.xenproject.org/wiki/GSoc_2014

    * http://wiki.xenproject.org/wiki/OutreachProgramForWomen/Round8

    

    Both programs have a very similar structure: the main difference are
    differences in application deadlines and forms. As I will be on
    holidays in the coming weeks, Russell volunteered to help coordinate
    activities related to both programs. He also has administrator
    rights for the Google GSoC system

    

    The other main difference is that OPW requires applicants to make a
    code contribution *before* the application. This requires working
    with the mentor and a reference to the contribution in the
    application. This can be a bug fix, code refactoring, writing a test
    case, etc. and is designed to get interns familiar with the tooling
    and culture in the project.

    

    Although we do not require GSoC students to submit code before they
    apply, we *strongly encourage* them to do so and the application
    form is designed to encourage references to a students first
    contributions (bugs, wiki, etc.) and public communications on
    mailing lists. See
    http://wiki.xenproject.org/wiki/GSoc_2014#Finding_a_project_that_fits_you
    

    

    == Program Mangement Committee for Mentors ==

    To manage both programs, I propose that we set up a Commitee made up
    of 3-4 experienced GSoc and OPW mentors and former GSoC students to
    sanity check and review project proposals and provide advice to
    other mentors. Better the project proposals = happier mentors =
    happier students/interns = better outcome for the Xen Project and
    students. 

    

    Russell volunteered to reach out to candidates for the committee and
    to organize the first meetings (ideally sometimes next week). Once
    we have all applications in and mentors signed up, the committe
    would become a regular meeting for all mentors across GSoC and OPW
    who are mentoring students. We also need to decide which students to
    accept for both programs by April 18.

    

    For mentors: please make sure that you only take on one intern or
    student. Mentoring more than one student is too hard.

    

    == OPW ==

    Intern application deadline: March 18th

    Close of Intern Selection: April 18

    Accepted participants announced : April 21

    Internship Period: May 19 - August 18

      

    Request to mentors: 

    * please update your projects on
    http://wiki.xenproject.org/wiki/OutreachProgramForWomen/Round8

    * please hang out on the #xen-opw channel in the coming weeks, if
    you can and engage with interns

    * please give interns small achievable tasks (on a public list) that
    help us identify whether the intern can can complete a project,
    prior to the application. This can be a bug fix, code refactoring,
    writing a test case, etc. and is designed to get interns familiar
    with the tooling and culture in the project.

    

    == Google Summer of Code ==

    Student application deadline: March 21th

    Close of Student Selection: April 18

    Accepted participants announced : April 21

    Coding Period: May 19 - August 18

        

      Request to mentors: 

    * please update your projects on
    http://wiki.xenproject.org/wiki/GSoc_2014

    * please sign up to the GSoC website, aka

    ** create an account on https://www.google-melange.com/gsoc/homepage/google/gsoc2014
    

    ** sign in

    ** fill out https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014
    - "chose Xen Project"
    

    * please hang out on the #xen-opw channel in the coming weeks, if
    you can and engage with students

    * please give students small achievable tasks (on a public list)
    that help us identify whether the student can complete a project,
    prior to the application. This can be a bug fix, code refactoring,
    writing a test case, etc. and is designed to get students familiar
    with the tooling and culture in the project.

    

    Best Regards
    

    Lars
  


--------------040201090704040905090500--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============2622497764315505697==--


From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 17:09:17 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 17: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 1WILVJ-0006n2-Rj; Tue, 25 Feb 2014 17:09:13 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WILVI-0006mx-1Z
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 17:09:12 +0000
Received: from [85.158.137.68:28044] by server-2.bemta-3.messagelabs.com id
	18/31-06531-73ECC035; Tue, 25 Feb 2014 17:09:11 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-14.tower-31.messagelabs.com!1393348150!4162671!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17177 invoked from network); 25 Feb 2014 17:09:10 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-14.tower-31.messagelabs.com with SMTP;
	25 Feb 2014 17:09:10 -0000
Received: (qmail 10934 invoked by uid 634); 25 Feb 2014 17:09:09 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 25 Feb 2014 17:09:09 +0000
From: Anil Madhavapeddy 
Message-Id: <99957A9C-EFCD-42FA-973B-54D61FB955A7@recoil.org>
Date: Tue, 25 Feb 2014 17:09:09 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] auto configuring ip/netmask info
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Julian and I were looking into the various Xen config options for networking this morning, and it turns out that the XL/XM toolstacks can both specify a per-VIF ip/netmask/gateway directly in the VIF configuration. e.g.

```
vif = ['bridge=xenbr0,ip=10.0.0.2,netmask=255.255.255.0,gateway=10.0.0.1']

These are written into the VIF backend tree in xenstore.

I'd like to take advantage of this by having the network stack automatically probe for it and use it if available (i.e. a 'default' mode in the stack configuration, which can be overridden by the manual IP or DHCP options).

Any thoughts on the best place to put it, though?  The obvious place is in mirage-net-{unix/xen}, but we would need a Xenstore-equivalent for Unix (which has come up several times. Dave, how viable is it to have a simple Unix Xenstore that maps to a filesystem tree?  We can project configuration variables into there for tuntap, and perhaps take care of bridge configuration at the same time as well.

Another backend that will need an equivalent registry-style interface are the kFreeBSD backend (which could call back into userspace via an ioctl interface).

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 17:09:17 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 17: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 1WILVJ-0006n2-Rj; Tue, 25 Feb 2014 17:09:13 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WILVI-0006mx-1Z
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 17:09:12 +0000
Received: from [85.158.137.68:28044] by server-2.bemta-3.messagelabs.com id
	18/31-06531-73ECC035; Tue, 25 Feb 2014 17:09:11 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-14.tower-31.messagelabs.com!1393348150!4162671!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17177 invoked from network); 25 Feb 2014 17:09:10 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-14.tower-31.messagelabs.com with SMTP;
	25 Feb 2014 17:09:10 -0000
Received: (qmail 10934 invoked by uid 634); 25 Feb 2014 17:09:09 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 25 Feb 2014 17:09:09 +0000
From: Anil Madhavapeddy 
Message-Id: <99957A9C-EFCD-42FA-973B-54D61FB955A7@recoil.org>
Date: Tue, 25 Feb 2014 17:09:09 +0000
To: mirageos-devel@lists.xenproject.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Subject: [MirageOS-devel] auto configuring ip/netmask info
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Julian and I were looking into the various Xen config options for networking this morning, and it turns out that the XL/XM toolstacks can both specify a per-VIF ip/netmask/gateway directly in the VIF configuration. e.g.

```
vif = ['bridge=xenbr0,ip=10.0.0.2,netmask=255.255.255.0,gateway=10.0.0.1']

These are written into the VIF backend tree in xenstore.

I'd like to take advantage of this by having the network stack automatically probe for it and use it if available (i.e. a 'default' mode in the stack configuration, which can be overridden by the manual IP or DHCP options).

Any thoughts on the best place to put it, though?  The obvious place is in mirage-net-{unix/xen}, but we would need a Xenstore-equivalent for Unix (which has come up several times. Dave, how viable is it to have a simple Unix Xenstore that maps to a filesystem tree?  We can project configuration variables into there for tuntap, and perhaps take care of bridge configuration at the same time as well.

Another backend that will need an equivalent registry-style interface are the kFreeBSD backend (which could call back into userspace via an ioctl interface).

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 20:44:25 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 20:44: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 1WIOrS-00081s-Ap; Tue, 25 Feb 2014 20:44:18 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIOrR-00081n-CX
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 20:44:17 +0000
Received: from [85.158.143.35:33790] by server-2.bemta-4.messagelabs.com id
	A8/1E-04779-0A00D035; Tue, 25 Feb 2014 20:44:16 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-9.tower-21.messagelabs.com!1393361055!8272984!1
X-Originating-IP: [151.236.209.33]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10987 invoked from network); 25 Feb 2014 20:44:15 -0000
Received: from engine01-20433-7.icritical.com (HELO
	engine01-20433-7.icritical.com) (151.236.209.33)
	by server-9.tower-21.messagelabs.com with SMTP;
	25 Feb 2014 20:44:15 -0000
Received: (qmail 18005 invoked from network); 25 Feb 2014 20:40:28 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-7.icritical.com with SMTP; 25 Feb 2014 20:40:28 -0000
Received: from engine01-20433-7.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 17221-02 for ;
	Tue, 25 Feb 2014 20:40:27 +0000 (GMT)
Received: (qmail 17959 invoked by uid 599); 25 Feb 2014 20:40:27 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP;
	Tue, 25 Feb 2014 20:40:27 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WIOnm-0006jK-Jv; Tue, 25 Feb 2014 20:40:30 +0000
From: Richard Mortier 
To: Anil Madhavapeddy 
Date: Tue, 25 Feb 2014 20:40:29 +0000
Thread-Topic: [MirageOS-devel] auto configuring ip/netmask info
Thread-Index: Ac8yadJaDv2mhtlNSQeHxk3UphkWjg==
Message-ID: <1FA460E9-D42B-4B1A-BE7E-47233B3FCBA1@nottingham.ac.uk>
References: <99957A9C-EFCD-42FA-973B-54D61FB955A7@recoil.org>
In-Reply-To: <99957A9C-EFCD-42FA-973B-54D61FB955A7@recoil.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] auto configuring ip/netmask info
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 25 Feb 2014, at 17:09, Anil Madhavapeddy  wrote:

> Julian and I were looking into the various Xen config options for networking this morning, and it turns out that the XL/XM toolstacks can both specify a per-VIF ip/netmask/gateway directly in the VIF configuration. e.g.
> 
> ```
> vif = ['bridge=xenbr0,ip=10.0.0.2,netmask=255.255.255.0,gateway=10.0.0.1']
> 
> These are written into the VIF backend tree in xenstore.

aha. i wondered about that. where's the best docs on xenstore -- it's probably something i should know a bit more about.

> I'd like to take advantage of this by having the network stack automatically probe for it and use it if available (i.e. a 'default' mode in the stack configuration, which can be overridden by the manual IP or DHCP options).
> 
> Any thoughts on the best place to put it, though?  The obvious place is in mirage-net-{unix/xen}, but we would need a Xenstore-equivalent for Unix (which has come up several times. Dave, how viable is it to have a simple Unix Xenstore that maps to a filesystem tree?  We can project configuration variables into there for tuntap, and perhaps take care of bridge configuration at the same time as well.

i can't comment on the viability of a unix equivalent, but that seems to make a lot of sense to me.

> Another backend that will need an equivalent registry-style interface are the kFreeBSD backend (which could call back into userspace via an ioctl interface).

what would the js backend do?  (or would the issue simply never arise?)

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 20:44:25 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 20:44: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 1WIOrS-00081s-Ap; Tue, 25 Feb 2014 20:44:18 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIOrR-00081n-CX
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 20:44:17 +0000
Received: from [85.158.143.35:33790] by server-2.bemta-4.messagelabs.com id
	A8/1E-04779-0A00D035; Tue, 25 Feb 2014 20:44:16 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-9.tower-21.messagelabs.com!1393361055!8272984!1
X-Originating-IP: [151.236.209.33]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10987 invoked from network); 25 Feb 2014 20:44:15 -0000
Received: from engine01-20433-7.icritical.com (HELO
	engine01-20433-7.icritical.com) (151.236.209.33)
	by server-9.tower-21.messagelabs.com with SMTP;
	25 Feb 2014 20:44:15 -0000
Received: (qmail 18005 invoked from network); 25 Feb 2014 20:40:28 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-7.icritical.com with SMTP; 25 Feb 2014 20:40:28 -0000
Received: from engine01-20433-7.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 17221-02 for ;
	Tue, 25 Feb 2014 20:40:27 +0000 (GMT)
Received: (qmail 17959 invoked by uid 599); 25 Feb 2014 20:40:27 -0000
Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55)
	by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP;
	Tue, 25 Feb 2014 20:40:27 +0000
Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133])
	by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WIOnm-0006jK-Jv; Tue, 25 Feb 2014 20:40:30 +0000
From: Richard Mortier 
To: Anil Madhavapeddy 
Date: Tue, 25 Feb 2014 20:40:29 +0000
Thread-Topic: [MirageOS-devel] auto configuring ip/netmask info
Thread-Index: Ac8yadJaDv2mhtlNSQeHxk3UphkWjg==
Message-ID: <1FA460E9-D42B-4B1A-BE7E-47233B3FCBA1@nottingham.ac.uk>
References: <99957A9C-EFCD-42FA-973B-54D61FB955A7@recoil.org>
In-Reply-To: <99957A9C-EFCD-42FA-973B-54D61FB955A7@recoil.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] auto configuring ip/netmask info
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 25 Feb 2014, at 17:09, Anil Madhavapeddy  wrote:

> Julian and I were looking into the various Xen config options for networking this morning, and it turns out that the XL/XM toolstacks can both specify a per-VIF ip/netmask/gateway directly in the VIF configuration. e.g.
> 
> ```
> vif = ['bridge=xenbr0,ip=10.0.0.2,netmask=255.255.255.0,gateway=10.0.0.1']
> 
> These are written into the VIF backend tree in xenstore.

aha. i wondered about that. where's the best docs on xenstore -- it's probably something i should know a bit more about.

> I'd like to take advantage of this by having the network stack automatically probe for it and use it if available (i.e. a 'default' mode in the stack configuration, which can be overridden by the manual IP or DHCP options).
> 
> Any thoughts on the best place to put it, though?  The obvious place is in mirage-net-{unix/xen}, but we would need a Xenstore-equivalent for Unix (which has come up several times. Dave, how viable is it to have a simple Unix Xenstore that maps to a filesystem tree?  We can project configuration variables into there for tuntap, and perhaps take care of bridge configuration at the same time as well.

i can't comment on the viability of a unix equivalent, but that seems to make a lot of sense to me.

> Another backend that will need an equivalent registry-style interface are the kFreeBSD backend (which could call back into userspace via an ioctl interface).

what would the js backend do?  (or would the issue simply never arise?)

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 22:31:46 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 22:31: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 1WIQXI-0001Do-MK; Tue, 25 Feb 2014 22:31:36 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIQXH-0001Dj-I5
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 22:31:35 +0000
Received: from [193.109.254.147:65278] by server-9.bemta-14.messagelabs.com id
	A1/DB-24895-6C91D035; Tue, 25 Feb 2014 22:31:34 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-10.tower-27.messagelabs.com!1393367494!6829425!1
X-Originating-IP: [131.111.8.142]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25854 invoked from network); 25 Feb 2014 22:31:34 -0000
Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk)
	(131.111.8.142)
	by server-10.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 25 Feb 2014 22:31:34 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net
	([86.6.155.105]:49768 helo=[192.168.0.3])
	by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WIQXF-0002Ur-9E (Exim 4.82_3-c0e5623) for
	mirageos-devel@lists.xenproject.org
	(return-path ); Tue, 25 Feb 2014 22:31:33 +0000
From: Amir Chaudhry 
Message-Id: <778B9B71-578F-49D7-AF20-FE7A2BB4667F@cam.ac.uk>
Date: Tue, 25 Feb 2014 22:31:33 +0000
To: "mirageos-devel@lists.xenproject.org" 
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi folks,

I'm having a problem getting a ` --unix` build of a static website to run and I'm not sure how to proceed (I'm on OSX 10.8.5).

I'm using mirage-skeleton/static_website and the `configure` and `build` steps seem to work fine  but `mirage run` gives me the following:

===========================

www         + Executing: make run
www          /dev/tap0
www          Fatal error: exception Failure("net_tap0")
www          Raised at file "src/core/lwt.ml", line 782, characters 22-23
www          Called from file "src/unix/lwt_main.ml", line 34, characters 8-18
www          Called from file "main.ml", line 84, characters 2-28
www          make: *** [run] Error 2
www          uence,principal" -cflag -g -lflags -g,-linkpkg main.native
www          ln -nfs _build/main.native mir-www
www          ./mir-www
[ERROR]      The command "make run" exited with code 2.

===========================

I'm guessing this is something to do with tuntap but I'm not sure how to get more info.  Just in case I had stale copies, I reinstalled tuntap via homebrew and moved items to the appropriate places (i.e I followed the info you can see in `brew info tuntap`).  That didn't help and after digging in the main.ml file, I can see that the exception is raised on line 45.

let stackv41 () =
  console1 () >>= function
  | `Error _    -> fail (Failure "console1")
  | `Ok console ->
  net_tap0 () >>= function
  | `Error _      -> fail (Failure "net_tap0")  (*<------------- this is line 45*)
  | `Ok interface ->
  let config = {
    V1_LWT.name = "stackv41";
    console; interface;
    mode = `IPv4 (Ipaddr.V4.of_string_exn "10.0.0.2", Ipaddr.V4.of_string_exn "255.255.255.0", [Ipaddr.V4.of_string_exn "10.0.0.1"]);
  } in
  Stackv41.connect config

At this point, I don't know what else to do.  Any advice? I kind of wonder that I've missed something obvious.

Amir
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 22:31:46 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 22:31: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 1WIQXI-0001Do-MK; Tue, 25 Feb 2014 22:31:36 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIQXH-0001Dj-I5
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 22:31:35 +0000
Received: from [193.109.254.147:65278] by server-9.bemta-14.messagelabs.com id
	A1/DB-24895-6C91D035; Tue, 25 Feb 2014 22:31:34 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-10.tower-27.messagelabs.com!1393367494!6829425!1
X-Originating-IP: [131.111.8.142]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25854 invoked from network); 25 Feb 2014 22:31:34 -0000
Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk)
	(131.111.8.142)
	by server-10.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 25 Feb 2014 22:31:34 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net
	([86.6.155.105]:49768 helo=[192.168.0.3])
	by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WIQXF-0002Ur-9E (Exim 4.82_3-c0e5623) for
	mirageos-devel@lists.xenproject.org
	(return-path ); Tue, 25 Feb 2014 22:31:33 +0000
From: Amir Chaudhry 
Message-Id: <778B9B71-578F-49D7-AF20-FE7A2BB4667F@cam.ac.uk>
Date: Tue, 25 Feb 2014 22:31:33 +0000
To: "mirageos-devel@lists.xenproject.org" 
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

Hi folks,

I'm having a problem getting a ` --unix` build of a static website to run and I'm not sure how to proceed (I'm on OSX 10.8.5).

I'm using mirage-skeleton/static_website and the `configure` and `build` steps seem to work fine  but `mirage run` gives me the following:

===========================

www         + Executing: make run
www          /dev/tap0
www          Fatal error: exception Failure("net_tap0")
www          Raised at file "src/core/lwt.ml", line 782, characters 22-23
www          Called from file "src/unix/lwt_main.ml", line 34, characters 8-18
www          Called from file "main.ml", line 84, characters 2-28
www          make: *** [run] Error 2
www          uence,principal" -cflag -g -lflags -g,-linkpkg main.native
www          ln -nfs _build/main.native mir-www
www          ./mir-www
[ERROR]      The command "make run" exited with code 2.

===========================

I'm guessing this is something to do with tuntap but I'm not sure how to get more info.  Just in case I had stale copies, I reinstalled tuntap via homebrew and moved items to the appropriate places (i.e I followed the info you can see in `brew info tuntap`).  That didn't help and after digging in the main.ml file, I can see that the exception is raised on line 45.

let stackv41 () =
  console1 () >>= function
  | `Error _    -> fail (Failure "console1")
  | `Ok console ->
  net_tap0 () >>= function
  | `Error _      -> fail (Failure "net_tap0")  (*<------------- this is line 45*)
  | `Ok interface ->
  let config = {
    V1_LWT.name = "stackv41";
    console; interface;
    mode = `IPv4 (Ipaddr.V4.of_string_exn "10.0.0.2", Ipaddr.V4.of_string_exn "255.255.255.0", [Ipaddr.V4.of_string_exn "10.0.0.1"]);
  } in
  Stackv41.connect config

At this point, I don't know what else to do.  Any advice? I kind of wonder that I've missed something obvious.

Amir
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 23:50:26 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 23:50: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 1WIRlW-0001U3-TV; Tue, 25 Feb 2014 23:50:22 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIRlV-0001Ty-Al
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 23:50:21 +0000
Received: from [193.109.254.147:54970] by server-12.bemta-14.messagelabs.com
	id 36/A2-17220-C3C2D035; Tue, 25 Feb 2014 23:50:20 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-3.tower-27.messagelabs.com!1393372219!6838224!1
X-Originating-IP: [151.236.209.33]
X-SpamReason: No, hits=1.0 required=7.0 tests=BODY_RANDOM_LONG,
	MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20291 invoked from network); 25 Feb 2014 23:50:19 -0000
Received: from engine01-20433-7.icritical.com (HELO
	engine01-20433-7.icritical.com) (151.236.209.33)
	by server-3.tower-27.messagelabs.com with SMTP;
	25 Feb 2014 23:50:19 -0000
Received: (qmail 17184 invoked from network); 25 Feb 2014 23:50:12 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-7.icritical.com with SMTP; 25 Feb 2014 23:50:12 -0000
Received: from engine01-20433-7.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 17170-01 for ;
	Tue, 25 Feb 2014 23:50:11 +0000 (GMT)
Received: (qmail 17167 invoked by uid 599); 25 Feb 2014 23:50:09 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP;
	Tue, 25 Feb 2014 23:50:09 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WIRlP-0003b2-1t
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 23:50:15 +0000
From: Richard Mortier 
To: Amir Chaudhry 
Date: Tue, 25 Feb 2014 23:50:13 +0000
Thread-Topic: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
Thread-Index: Ac8yhFN+A3373/2zTC6ZqvQjCcmSuw==
Message-ID: 
References: <778B9B71-578F-49D7-AF20-FE7A2BB4667F@cam.ac.uk>
In-Reply-To: <778B9B71-578F-49D7-AF20-FE7A2BB4667F@cam.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build
	of	static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 25 Feb 2014, at 22:31, Amir Chaudhry  wrote:

> Hi folks,
> 
> I'm having a problem getting a ` --unix` build of a static website to run and I'm not sure how to proceed (I'm on OSX 10.8.5).
> 
> I'm using mirage-skeleton/static_website and the `configure` and `build` steps seem to work fine  but `mirage run` gives me the following:

"mirage run" or "make run"? :)

probably a sudo issue -- opening tap0 requires sudo privs. 

in any case, i've not been finding either "make run" or "mirage run" particularly reliable recently so have been avoiding it on unix. just run the binary directly -- "sudo ./src/mir-www" or some such.

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Tue Feb 25 23:50:26 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Tue, 25 Feb 2014 23:50: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 1WIRlW-0001U3-TV; Tue, 25 Feb 2014 23:50:22 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIRlV-0001Ty-Al
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 23:50:21 +0000
Received: from [193.109.254.147:54970] by server-12.bemta-14.messagelabs.com
	id 36/A2-17220-C3C2D035; Tue, 25 Feb 2014 23:50:20 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-3.tower-27.messagelabs.com!1393372219!6838224!1
X-Originating-IP: [151.236.209.33]
X-SpamReason: No, hits=1.0 required=7.0 tests=BODY_RANDOM_LONG,
	MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20291 invoked from network); 25 Feb 2014 23:50:19 -0000
Received: from engine01-20433-7.icritical.com (HELO
	engine01-20433-7.icritical.com) (151.236.209.33)
	by server-3.tower-27.messagelabs.com with SMTP;
	25 Feb 2014 23:50:19 -0000
Received: (qmail 17184 invoked from network); 25 Feb 2014 23:50:12 -0000
Received: from localhost (127.0.0.1)
	by engine01-20433-7.icritical.com with SMTP; 25 Feb 2014 23:50:12 -0000
Received: from engine01-20433-7.icritical.com ([127.0.0.1])
	by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 17170-01 for ;
	Tue, 25 Feb 2014 23:50:11 +0000 (GMT)
Received: (qmail 17167 invoked by uid 599); 25 Feb 2014 23:50:09 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP;
	Tue, 25 Feb 2014 23:50:09 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WIRlP-0003b2-1t
	for mirageos-devel@lists.xenproject.org; Tue, 25 Feb 2014 23:50:15 +0000
From: Richard Mortier 
To: Amir Chaudhry 
Date: Tue, 25 Feb 2014 23:50:13 +0000
Thread-Topic: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
Thread-Index: Ac8yhFN+A3373/2zTC6ZqvQjCcmSuw==
Message-ID: 
References: <778B9B71-578F-49D7-AF20-FE7A2BB4667F@cam.ac.uk>
In-Reply-To: <778B9B71-578F-49D7-AF20-FE7A2BB4667F@cam.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build
	of	static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 25 Feb 2014, at 22:31, Amir Chaudhry  wrote:

> Hi folks,
> 
> I'm having a problem getting a ` --unix` build of a static website to run and I'm not sure how to proceed (I'm on OSX 10.8.5).
> 
> I'm using mirage-skeleton/static_website and the `configure` and `build` steps seem to work fine  but `mirage run` gives me the following:

"mirage run" or "make run"? :)

probably a sudo issue -- opening tap0 requires sudo privs. 

in any case, i've not been finding either "make run" or "mirage run" particularly reliable recently so have been avoiding it on unix. just run the binary directly -- "sudo ./src/mir-www" or some such.

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 00:34:41 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 00:34: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 1WISSM-0002Qi-3k; Wed, 26 Feb 2014 00:34:38 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WISSK-0002Qd-Td
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 00:34:37 +0000
Received: from [85.158.139.211:64163] by server-4.bemta-5.messagelabs.com id
	8B/BD-08092-C963D035; Wed, 26 Feb 2014 00:34:36 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-8.tower-206.messagelabs.com!1393374875!6247305!1
X-Originating-IP: [131.111.8.133]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR,
	ML_RADAR_SPEW_LINKS_32,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25069 invoked from network); 26 Feb 2014 00:34:35 -0000
Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk)
	(131.111.8.133)
	by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 26 Feb 2014 00:34:35 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net
	([86.6.155.105]:50891 helo=[192.168.0.3])
	by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WISSI-00062V-iD (Exim 4.82_3-c0e5623)
	(return-path ); Wed, 26 Feb 2014 00:34:34 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: 
Date: Wed, 26 Feb 2014 00:34:33 +0000
Message-Id: 
References: <778B9B71-578F-49D7-AF20-FE7A2BB4667F@cam.ac.uk>
	
To: Richard Mortier 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 25 Feb 2014, at 23:50, Richard Mortier  wrote:

> 
> On 25 Feb 2014, at 22:31, Amir Chaudhry  wrote:
> 
>> Hi folks,
>> 
>> I'm having a problem getting a ` --unix` build of a static website to run and I'm not sure how to proceed (I'm on OSX 10.8.5).
>> 
>> I'm using mirage-skeleton/static_website and the `configure` and `build` steps seem to work fine  but `mirage run` gives me the following:
> 
> "mirage run" or "make run"? :)

"Mirage run" as that's what's in the main readme. :)  "make run" does the same stuff without the pretty colours.

> probably a sudo issue -- opening tap0 requires sudo privs. 
> 
> in any case, i've not been finding either "make run" or "mirage run" particularly reliable recently so have been avoiding it on unix. just run the binary directly -- "sudo ./src/mir-www" or some such.

Hooray!  I'd forgotten about the sudo privilege. "sudo ./mir-www" got me a bit further and then I realised I should have read the instructions for mirage-www [1].  That mentions the need to set up the routing (which would have been my next hurdle).  I'll think of a way to update the static_website readme and submit a PR tomorrow (prob a brief summary and link to the wiki).

One thing I've noticed is that all my internal links are broken.  I have URLs of the form "domain.com/title-of-post", where the content is actually at "domain.com/title-of-post/index.html".  How do I go about fixing this, assuming I can?  Or does it require new code somewhere to support URLs like this (e.g. cohttp)?

[1] http://openmirage.org/wiki/mirage-www

Aside from the above, I'm really happy that I can get my site building and running as a unikernel!  mirage skeleton was a great way to get there quickly so thanks for the effort that went into it.  Once I've figured out enough of the pieces, I should be able to set up a github repo that travis can build and deploy on each push.  I think enough of you (mort, anil) have scripts I can crib from.

Amir :)
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 00:34:41 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 00:34: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 1WISSM-0002Qi-3k; Wed, 26 Feb 2014 00:34:38 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WISSK-0002Qd-Td
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 00:34:37 +0000
Received: from [85.158.139.211:64163] by server-4.bemta-5.messagelabs.com id
	8B/BD-08092-C963D035; Wed, 26 Feb 2014 00:34:36 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-8.tower-206.messagelabs.com!1393374875!6247305!1
X-Originating-IP: [131.111.8.133]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR,
	ML_RADAR_SPEW_LINKS_32,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25069 invoked from network); 26 Feb 2014 00:34:35 -0000
Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk)
	(131.111.8.133)
	by server-8.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 26 Feb 2014 00:34:35 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net
	([86.6.155.105]:50891 helo=[192.168.0.3])
	by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WISSI-00062V-iD (Exim 4.82_3-c0e5623)
	(return-path ); Wed, 26 Feb 2014 00:34:34 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: 
Date: Wed, 26 Feb 2014 00:34:33 +0000
Message-Id: 
References: <778B9B71-578F-49D7-AF20-FE7A2BB4667F@cam.ac.uk>
	
To: Richard Mortier 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 25 Feb 2014, at 23:50, Richard Mortier  wrote:

> 
> On 25 Feb 2014, at 22:31, Amir Chaudhry  wrote:
> 
>> Hi folks,
>> 
>> I'm having a problem getting a ` --unix` build of a static website to run and I'm not sure how to proceed (I'm on OSX 10.8.5).
>> 
>> I'm using mirage-skeleton/static_website and the `configure` and `build` steps seem to work fine  but `mirage run` gives me the following:
> 
> "mirage run" or "make run"? :)

"Mirage run" as that's what's in the main readme. :)  "make run" does the same stuff without the pretty colours.

> probably a sudo issue -- opening tap0 requires sudo privs. 
> 
> in any case, i've not been finding either "make run" or "mirage run" particularly reliable recently so have been avoiding it on unix. just run the binary directly -- "sudo ./src/mir-www" or some such.

Hooray!  I'd forgotten about the sudo privilege. "sudo ./mir-www" got me a bit further and then I realised I should have read the instructions for mirage-www [1].  That mentions the need to set up the routing (which would have been my next hurdle).  I'll think of a way to update the static_website readme and submit a PR tomorrow (prob a brief summary and link to the wiki).

One thing I've noticed is that all my internal links are broken.  I have URLs of the form "domain.com/title-of-post", where the content is actually at "domain.com/title-of-post/index.html".  How do I go about fixing this, assuming I can?  Or does it require new code somewhere to support URLs like this (e.g. cohttp)?

[1] http://openmirage.org/wiki/mirage-www

Aside from the above, I'm really happy that I can get my site building and running as a unikernel!  mirage skeleton was a great way to get there quickly so thanks for the effort that went into it.  Once I've figured out enough of the pieces, I should be able to set up a github repo that travis can build and deploy on each push.  I think enough of you (mort, anil) have scripts I can crib from.

Amir :)
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 06:43:19 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 06:43:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIYD4-0000TA-KJ; Wed, 26 Feb 2014 06:43:14 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIYD3-0000T5-5U
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 06:43:13 +0000
Received: from [85.158.139.211:50061] by server-3.bemta-5.messagelabs.com id
	39/23-13671-00D8D035; Wed, 26 Feb 2014 06:43:12 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-13.tower-206.messagelabs.com!1393396991!6273762!1
X-Originating-IP: [195.62.217.151]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12041 invoked from network); 26 Feb 2014 06:43:11 -0000
Received: from engine02-20433-2.icritical.com (HELO
	engine02-20433-2.icritical.com) (195.62.217.151)
	by server-13.tower-206.messagelabs.com with SMTP;
	26 Feb 2014 06:43:11 -0000
Received: (qmail 11179 invoked from network); 26 Feb 2014 06:43:05 -0000
Received: from localhost (127.0.0.1)
	by engine02-20433-2.icritical.com with SMTP; 26 Feb 2014 06:43:05 -0000
Received: from engine02-20433-2.icritical.com ([127.0.0.1])
	by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 11144-01 for ;
	Wed, 26 Feb 2014 06:43:03 +0000 (GMT)
Received: (qmail 11154 invoked by uid 599); 26 Feb 2014 06:43:03 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP;
	Wed, 26 Feb 2014 06:43:03 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WIYCx-0001AO-Ca
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 06:43:07 +0000
From: Richard Mortier 
To: Amir M M Chaudhry 
Date: Wed, 26 Feb 2014 06:43:04 +0000
Thread-Topic: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
Thread-Index: Ac8yvgFpOR5sOxRXQ4adJRPyHF+wkQ==
Message-ID: <428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1D@EXCHANGE1.ad.nottingham.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build of
 static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4099762852554477753=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============4099762852554477753==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1DEXCHANGE1adno_"

--_000_428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1DEXCHANGE1adno_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpPbiAyNiBGZWIgMjAxNCAwMDozNCwgQW1pciBDaGF1ZGhyeSA8YW1jNzlAY2FtLmFjLnVrPiB3
cm90ZToNCj4NCj4gT25lIHRoaW5nIEkndmUgbm90aWNlZCBpcyB0aGF0IGFsbCBteSBpbnRlcm5h
bCBsaW5rcyBhcmUgYnJva2VuLiAgSSBoYXZlIFVSTHMgb2YgdGhlIGZvcm0gImRvbWFpbi5jb20v
dGl0bGUtb2YtcG9zdCIsIHdoZXJlIHRoZSBjb250ZW50IGlzIGFjdHVhbGx5IGF0ICJkb21haW4u
Y29tL3RpdGxlLW9mLXBvc3QvaW5kZXguaHRtbCIuICBIb3cgZG8gSSBnbyBhYm91dCBmaXhpbmcg
dGhpcywgYXNzdW1pbmcgSSBjYW4/ICBPciBkb2VzIGl0IHJlcXVpcmUgbmV3IGNvZGUgc29tZXdo
ZXJlIHRvIHN1cHBvcnQgVVJMcyBsaWtlIHRoaXMgKGUuZy4gY29odHRwKT8NCj4NCg0KVGhpcyBp
cyBoYW5kbGVkIGJ5IHRoZSBVUkwgZGlzcGF0Y2hlci4gQ2FuJ3QgcmVtZW1iZXIgZmlsZW5hbWUs
IGJ1dCB1bmlrZXJuZWwubWwgb3Igc2l0ZS5tbCBvciBzb21ldGhpbmcuIFRoZXJlIHdpbGwgYmUg
YSBtYXRjaCBzdGF0ZW1lbnQgdGhhdCBtYXBzIHRoZSByZXF1ZXN0ZWQgVVJMIHRvIGFuIGFjdHVh
bCBmaWxlLCBpbiBhIHRyeSBjbGF1c2UgdGhhdCBoYW5kbGVzIHRoZSBjYXNlIHdoZXJlIHRoZSBm
aWxlIGRvZXNuJ3QgZXhpc3QgaWlyYy4gWW91J2xsIHByb2JhYmx5IHdhbnQgdG8gdHdlYWsgdGhh
dCBzbyB0aGF0IGl0IGFsc28gbWFwcyB1cmxzIGVuZGluZyB0b28vaW5kZXguaHRtbCB0byB0aGUg
ZmlsZSBmb28gIGFzIHdlbGwuDQoNCklmIHVzaW5nIGNvd2FibG9nYSwgdGhpcyBjaHVuayBvZiBj
b2RlIGNvdWxkIGJlIGluIHRoZXJlIGluc3RlYWQsIGNhbid0IHJlbWVtYmVyIG9mZiB0b3Agb2Yg
bXkgaGVhZC4gQnV0IGxvb2sgaW4gdGhlIHNpdGUgY29kZSBmaXJzdC4uLg0K

--_000_428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1DEXCHANGE1adno_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PHAgZGlyPSJsdHIiPjxicj4KT24gMjYgRmViIDIwMTQgMDA6MzQsIEFtaXIgQ2hhdWRocnkgJmx0
O2FtYzc5QGNhbS5hYy51ayZndDsgd3JvdGU6PGJyPgomZ3Q7PGJyPgomZ3Q7IE9uZSB0aGluZyBJ
J3ZlIG5vdGljZWQgaXMgdGhhdCBhbGwgbXkgaW50ZXJuYWwgbGlua3MgYXJlIGJyb2tlbi4mIzE2
MDsgSSBoYXZlIFVSTHMgb2YgdGhlIGZvcm0gImRvbWFpbi5jb20vdGl0bGUtb2YtcG9zdCIsIHdo
ZXJlIHRoZSBjb250ZW50IGlzIGFjdHVhbGx5IGF0ICJkb21haW4uY29tL3RpdGxlLW9mLXBvc3Qv
aW5kZXguaHRtbCIuJiMxNjA7IEhvdyBkbyBJIGdvIGFib3V0IGZpeGluZyB0aGlzLCBhc3N1bWlu
ZyBJIGNhbj8mIzE2MDsgT3IgZG9lcyBpdCByZXF1aXJlIG5ldyBjb2RlIHNvbWV3aGVyZSB0byBz
dXBwb3J0IFVSTHMgbGlrZSB0aGlzIChlLmcuIGNvaHR0cCk/PGJyPgomZ3Q7PC9wPgo8cCBkaXI9
Imx0ciI+VGhpcyBpcyBoYW5kbGVkIGJ5IHRoZSBVUkwgZGlzcGF0Y2hlci4gQ2FuJ3QgcmVtZW1i
ZXIgZmlsZW5hbWUsIGJ1dCB1bmlrZXJuZWwubWwgb3Igc2l0ZS5tbCBvciBzb21ldGhpbmcuIFRo
ZXJlIHdpbGwgYmUgYSBtYXRjaCBzdGF0ZW1lbnQgdGhhdCBtYXBzIHRoZSByZXF1ZXN0ZWQgVVJM
IHRvIGFuIGFjdHVhbCBmaWxlLCBpbiBhIHRyeSBjbGF1c2UgdGhhdCBoYW5kbGVzIHRoZSBjYXNl
IHdoZXJlIHRoZSBmaWxlIGRvZXNuJ3QgZXhpc3QgaWlyYy4gWW91J2xsIHByb2JhYmx5IHdhbnQg
dG8gdHdlYWsgdGhhdCBzbyB0aGF0IGl0IGFsc28gbWFwcyB1cmxzIGVuZGluZyB0b28vaW5kZXgu
aHRtbCB0byB0aGUgZmlsZSBmb28mbmJzcDsgYXMgd2VsbC48L3A+CjxwIGRpcj0ibHRyIj5JZiB1
c2luZyBjb3dhYmxvZ2EsIHRoaXMgY2h1bmsgb2YgY29kZSBjb3VsZCBiZSBpbiB0aGVyZSBpbnN0
ZWFkLCBjYW4ndCByZW1lbWJlciBvZmYgdG9wIG9mIG15IGhlYWQuIEJ1dCBsb29rIGluIHRoZSBz
aXRlIGNvZGUgZmlyc3QuLi48L3A+Cg==

--_000_428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1DEXCHANGE1adno_--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============4099762852554477753==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 06:43:19 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 06:43:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIYD4-0000TA-KJ; Wed, 26 Feb 2014 06:43:14 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIYD3-0000T5-5U
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 06:43:13 +0000
Received: from [85.158.139.211:50061] by server-3.bemta-5.messagelabs.com id
	39/23-13671-00D8D035; Wed, 26 Feb 2014 06:43:12 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-13.tower-206.messagelabs.com!1393396991!6273762!1
X-Originating-IP: [195.62.217.151]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12041 invoked from network); 26 Feb 2014 06:43:11 -0000
Received: from engine02-20433-2.icritical.com (HELO
	engine02-20433-2.icritical.com) (195.62.217.151)
	by server-13.tower-206.messagelabs.com with SMTP;
	26 Feb 2014 06:43:11 -0000
Received: (qmail 11179 invoked from network); 26 Feb 2014 06:43:05 -0000
Received: from localhost (127.0.0.1)
	by engine02-20433-2.icritical.com with SMTP; 26 Feb 2014 06:43:05 -0000
Received: from engine02-20433-2.icritical.com ([127.0.0.1])
	by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 11144-01 for ;
	Wed, 26 Feb 2014 06:43:03 +0000 (GMT)
Received: (qmail 11154 invoked by uid 599); 26 Feb 2014 06:43:03 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP;
	Wed, 26 Feb 2014 06:43:03 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WIYCx-0001AO-Ca
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 06:43:07 +0000
From: Richard Mortier 
To: Amir M M Chaudhry 
Date: Wed, 26 Feb 2014 06:43:04 +0000
Thread-Topic: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
Thread-Index: Ac8yvgFpOR5sOxRXQ4adJRPyHF+wkQ==
Message-ID: <428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1D@EXCHANGE1.ad.nottingham.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build of
 static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============4099762852554477753=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============4099762852554477753==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1DEXCHANGE1adno_"

--_000_428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1DEXCHANGE1adno_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpPbiAyNiBGZWIgMjAxNCAwMDozNCwgQW1pciBDaGF1ZGhyeSA8YW1jNzlAY2FtLmFjLnVrPiB3
cm90ZToNCj4NCj4gT25lIHRoaW5nIEkndmUgbm90aWNlZCBpcyB0aGF0IGFsbCBteSBpbnRlcm5h
bCBsaW5rcyBhcmUgYnJva2VuLiAgSSBoYXZlIFVSTHMgb2YgdGhlIGZvcm0gImRvbWFpbi5jb20v
dGl0bGUtb2YtcG9zdCIsIHdoZXJlIHRoZSBjb250ZW50IGlzIGFjdHVhbGx5IGF0ICJkb21haW4u
Y29tL3RpdGxlLW9mLXBvc3QvaW5kZXguaHRtbCIuICBIb3cgZG8gSSBnbyBhYm91dCBmaXhpbmcg
dGhpcywgYXNzdW1pbmcgSSBjYW4/ICBPciBkb2VzIGl0IHJlcXVpcmUgbmV3IGNvZGUgc29tZXdo
ZXJlIHRvIHN1cHBvcnQgVVJMcyBsaWtlIHRoaXMgKGUuZy4gY29odHRwKT8NCj4NCg0KVGhpcyBp
cyBoYW5kbGVkIGJ5IHRoZSBVUkwgZGlzcGF0Y2hlci4gQ2FuJ3QgcmVtZW1iZXIgZmlsZW5hbWUs
IGJ1dCB1bmlrZXJuZWwubWwgb3Igc2l0ZS5tbCBvciBzb21ldGhpbmcuIFRoZXJlIHdpbGwgYmUg
YSBtYXRjaCBzdGF0ZW1lbnQgdGhhdCBtYXBzIHRoZSByZXF1ZXN0ZWQgVVJMIHRvIGFuIGFjdHVh
bCBmaWxlLCBpbiBhIHRyeSBjbGF1c2UgdGhhdCBoYW5kbGVzIHRoZSBjYXNlIHdoZXJlIHRoZSBm
aWxlIGRvZXNuJ3QgZXhpc3QgaWlyYy4gWW91J2xsIHByb2JhYmx5IHdhbnQgdG8gdHdlYWsgdGhh
dCBzbyB0aGF0IGl0IGFsc28gbWFwcyB1cmxzIGVuZGluZyB0b28vaW5kZXguaHRtbCB0byB0aGUg
ZmlsZSBmb28gIGFzIHdlbGwuDQoNCklmIHVzaW5nIGNvd2FibG9nYSwgdGhpcyBjaHVuayBvZiBj
b2RlIGNvdWxkIGJlIGluIHRoZXJlIGluc3RlYWQsIGNhbid0IHJlbWVtYmVyIG9mZiB0b3Agb2Yg
bXkgaGVhZC4gQnV0IGxvb2sgaW4gdGhlIHNpdGUgY29kZSBmaXJzdC4uLg0K

--_000_428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1DEXCHANGE1adno_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PHAgZGlyPSJsdHIiPjxicj4KT24gMjYgRmViIDIwMTQgMDA6MzQsIEFtaXIgQ2hhdWRocnkgJmx0
O2FtYzc5QGNhbS5hYy51ayZndDsgd3JvdGU6PGJyPgomZ3Q7PGJyPgomZ3Q7IE9uZSB0aGluZyBJ
J3ZlIG5vdGljZWQgaXMgdGhhdCBhbGwgbXkgaW50ZXJuYWwgbGlua3MgYXJlIGJyb2tlbi4mIzE2
MDsgSSBoYXZlIFVSTHMgb2YgdGhlIGZvcm0gImRvbWFpbi5jb20vdGl0bGUtb2YtcG9zdCIsIHdo
ZXJlIHRoZSBjb250ZW50IGlzIGFjdHVhbGx5IGF0ICJkb21haW4uY29tL3RpdGxlLW9mLXBvc3Qv
aW5kZXguaHRtbCIuJiMxNjA7IEhvdyBkbyBJIGdvIGFib3V0IGZpeGluZyB0aGlzLCBhc3N1bWlu
ZyBJIGNhbj8mIzE2MDsgT3IgZG9lcyBpdCByZXF1aXJlIG5ldyBjb2RlIHNvbWV3aGVyZSB0byBz
dXBwb3J0IFVSTHMgbGlrZSB0aGlzIChlLmcuIGNvaHR0cCk/PGJyPgomZ3Q7PC9wPgo8cCBkaXI9
Imx0ciI+VGhpcyBpcyBoYW5kbGVkIGJ5IHRoZSBVUkwgZGlzcGF0Y2hlci4gQ2FuJ3QgcmVtZW1i
ZXIgZmlsZW5hbWUsIGJ1dCB1bmlrZXJuZWwubWwgb3Igc2l0ZS5tbCBvciBzb21ldGhpbmcuIFRo
ZXJlIHdpbGwgYmUgYSBtYXRjaCBzdGF0ZW1lbnQgdGhhdCBtYXBzIHRoZSByZXF1ZXN0ZWQgVVJM
IHRvIGFuIGFjdHVhbCBmaWxlLCBpbiBhIHRyeSBjbGF1c2UgdGhhdCBoYW5kbGVzIHRoZSBjYXNl
IHdoZXJlIHRoZSBmaWxlIGRvZXNuJ3QgZXhpc3QgaWlyYy4gWW91J2xsIHByb2JhYmx5IHdhbnQg
dG8gdHdlYWsgdGhhdCBzbyB0aGF0IGl0IGFsc28gbWFwcyB1cmxzIGVuZGluZyB0b28vaW5kZXgu
aHRtbCB0byB0aGUgZmlsZSBmb28mbmJzcDsgYXMgd2VsbC48L3A+CjxwIGRpcj0ibHRyIj5JZiB1
c2luZyBjb3dhYmxvZ2EsIHRoaXMgY2h1bmsgb2YgY29kZSBjb3VsZCBiZSBpbiB0aGVyZSBpbnN0
ZWFkLCBjYW4ndCByZW1lbWJlciBvZmYgdG9wIG9mIG15IGhlYWQuIEJ1dCBsb29rIGluIHRoZSBz
aXRlIGNvZGUgZmlyc3QuLi48L3A+Cg==

--_000_428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1DEXCHANGE1adno_--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============4099762852554477753==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 10:12:26 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 10:12: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 1WIbTP-0003ya-NF; Wed, 26 Feb 2014 10:12:19 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIbTO-0003yV-C8
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 10:12:18 +0000
Received: from [85.158.139.211:30432] by server-3.bemta-5.messagelabs.com id
	E3/95-13671-10EBD035; Wed, 26 Feb 2014 10:12:17 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-11.tower-206.messagelabs.com!1393409536!1800312!1
X-Originating-IP: [131.111.8.142]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14553 invoked from network); 26 Feb 2014 10:12:17 -0000
Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk)
	(131.111.8.142)
	by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA
	encrypted SMTP; 26 Feb 2014 10:12:17 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from host81-149-102-120.in-addr.btopenworld.com
	([81.149.102.120]:52900 helo=[10.0.0.151])
	by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WIbTM-0006Hu-7Q (Exim 4.82_3-c0e5623)
	(return-path ); Wed, 26 Feb 2014 10:12:16 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: <428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1D@EXCHANGE1.ad.nottingham.ac.uk>
Date: Wed, 26 Feb 2014 10:12:14 +0000
Message-Id: 
References: <428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1D@EXCHANGE1.ad.nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 26 Feb 2014, at 06:43, Richard Mortier  wrote:

> =

> On 26 Feb 2014 00:34, Amir Chaudhry  wrote:
> >
> > One thing I've noticed is that all my internal links are broken.  I hav=
e URLs of the form "domain.com/title-of-post", where the content is actuall=
y at "domain.com/title-of-post/index.html".  How do I go about fixing this,=
 assuming I can?  Or does it require new code somewhere to support URLs lik=
e this (e.g. cohttp)?
> >
> =

> This is handled by the URL dispatcher. Can't remember filename, but unike=
rnel.ml or site.ml or something. There will be a match statement that maps =
the requested URL to an actual file, in a try clause that handles the case =
where the file doesn't exist iirc. You'll probably want to tweak that so th=
at it also maps urls ending too/index.html to the file foo  as well.
> =

> If using cowabloga, this chunk of code could be in there instead, can't r=
emember off top of my head. But look in the site code first=85

Helpful info, thanks!

There's a file called dispatch.ml and it looks like the piece I need is in =
there [1].  However, I'm not sure how to edit it to get what I want.  I'm g=
uessing it involves adding some more code to try different locations for th=
e content before raising the exception (see lines 39 40 at link below).

[1] https://github.com/mirage/mirage-skeleton/blob/master/static_website/di=
spatch.ml#L32

ac
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 10:12:26 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 10:12: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 1WIbTP-0003ya-NF; Wed, 26 Feb 2014 10:12:19 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIbTO-0003yV-C8
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 10:12:18 +0000
Received: from [85.158.139.211:30432] by server-3.bemta-5.messagelabs.com id
	E3/95-13671-10EBD035; Wed, 26 Feb 2014 10:12:17 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-11.tower-206.messagelabs.com!1393409536!1800312!1
X-Originating-IP: [131.111.8.142]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14553 invoked from network); 26 Feb 2014 10:12:17 -0000
Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk)
	(131.111.8.142)
	by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA
	encrypted SMTP; 26 Feb 2014 10:12:17 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from host81-149-102-120.in-addr.btopenworld.com
	([81.149.102.120]:52900 helo=[10.0.0.151])
	by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WIbTM-0006Hu-7Q (Exim 4.82_3-c0e5623)
	(return-path ); Wed, 26 Feb 2014 10:12:16 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: <428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1D@EXCHANGE1.ad.nottingham.ac.uk>
Date: Wed, 26 Feb 2014 10:12:14 +0000
Message-Id: 
References: <428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1D@EXCHANGE1.ad.nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 26 Feb 2014, at 06:43, Richard Mortier  wrote:

> =

> On 26 Feb 2014 00:34, Amir Chaudhry  wrote:
> >
> > One thing I've noticed is that all my internal links are broken.  I hav=
e URLs of the form "domain.com/title-of-post", where the content is actuall=
y at "domain.com/title-of-post/index.html".  How do I go about fixing this,=
 assuming I can?  Or does it require new code somewhere to support URLs lik=
e this (e.g. cohttp)?
> >
> =

> This is handled by the URL dispatcher. Can't remember filename, but unike=
rnel.ml or site.ml or something. There will be a match statement that maps =
the requested URL to an actual file, in a try clause that handles the case =
where the file doesn't exist iirc. You'll probably want to tweak that so th=
at it also maps urls ending too/index.html to the file foo  as well.
> =

> If using cowabloga, this chunk of code could be in there instead, can't r=
emember off top of my head. But look in the site code first=85

Helpful info, thanks!

There's a file called dispatch.ml and it looks like the piece I need is in =
there [1].  However, I'm not sure how to edit it to get what I want.  I'm g=
uessing it involves adding some more code to try different locations for th=
e content before raising the exception (see lines 39 40 at link below).

[1] https://github.com/mirage/mirage-skeleton/blob/master/static_website/di=
spatch.ml#L32

ac
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 10:24:37 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 10:24: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 1WIbfH-00042f-E7; Wed, 26 Feb 2014 10:24:35 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIbfF-00042X-KA
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 10:24:33 +0000
Received: from [193.109.254.147:26413] by server-16.bemta-14.messagelabs.com
	id 89/CA-21945-1E0CD035; Wed, 26 Feb 2014 10:24:33 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-14.tower-27.messagelabs.com!1393410272!6905266!1
X-Originating-IP: [195.62.217.151]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31159 invoked from network); 26 Feb 2014 10:24:32 -0000
Received: from engine02-20433-2.icritical.com (HELO
	engine02-20433-2.icritical.com) (195.62.217.151)
	by server-14.tower-27.messagelabs.com with SMTP;
	26 Feb 2014 10:24:32 -0000
Received: (qmail 14243 invoked from network); 26 Feb 2014 10:24:23 -0000
Received: from localhost (127.0.0.1)
	by engine02-20433-2.icritical.com with SMTP; 26 Feb 2014 10:24:23 -0000
Received: from engine02-20433-2.icritical.com ([127.0.0.1])
	by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 13553-09 for ;
	Wed, 26 Feb 2014 10:24:23 +0000 (GMT)
Received: (qmail 11572 invoked by uid 599); 26 Feb 2014 10:20:15 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP;
	Wed, 26 Feb 2014 10:20:15 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WIbaU-000280-U0
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 10:19:39 +0000
From: Richard Mortier 
To: Amir Chaudhry 
Date: Wed, 26 Feb 2014 10:19:37 +0000
Thread-Topic: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
Thread-Index: Ac8y3ED66oVM2jceQiW2+Qw3aE5O3Q==
Message-ID: 
References: <428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1D@EXCHANGE1.ad.nottingham.ac.uk>
	
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build of
 static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 26 Feb 2014, at 10:12, Amir Chaudhry  wrote:

> Helpful info, thanks!
> 
> There's a file called dispatch.ml and it looks like the piece I need is in there [1].  However, I'm not sure how to edit it to get what I want.  I'm guessing it involves adding some more code to try different locations for the content before raising the exception (see lines 39 40 at link below).
> 
> [1] https://github.com/mirage/mirage-skeleton/blob/master/static_website/dispatch.ml#L32

yup, that's it. (i should really pull this kind of thing into cowabloga as it's fairly standard behaviour if it's not already there. proposal rebuttals and other documents to write in the next day or two, but i'll try and do that later this week.)

look at line 34 -- what i'd do is check the list "segments" and if the last element is "index.html", drop it before doing the String.concat to create the path that's tried...

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 10:24:37 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 10:24: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 1WIbfH-00042f-E7; Wed, 26 Feb 2014 10:24:35 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIbfF-00042X-KA
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 10:24:33 +0000
Received: from [193.109.254.147:26413] by server-16.bemta-14.messagelabs.com
	id 89/CA-21945-1E0CD035; Wed, 26 Feb 2014 10:24:33 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-14.tower-27.messagelabs.com!1393410272!6905266!1
X-Originating-IP: [195.62.217.151]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31159 invoked from network); 26 Feb 2014 10:24:32 -0000
Received: from engine02-20433-2.icritical.com (HELO
	engine02-20433-2.icritical.com) (195.62.217.151)
	by server-14.tower-27.messagelabs.com with SMTP;
	26 Feb 2014 10:24:32 -0000
Received: (qmail 14243 invoked from network); 26 Feb 2014 10:24:23 -0000
Received: from localhost (127.0.0.1)
	by engine02-20433-2.icritical.com with SMTP; 26 Feb 2014 10:24:23 -0000
Received: from engine02-20433-2.icritical.com ([127.0.0.1])
	by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 13553-09 for ;
	Wed, 26 Feb 2014 10:24:23 +0000 (GMT)
Received: (qmail 11572 invoked by uid 599); 26 Feb 2014 10:20:15 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP;
	Wed, 26 Feb 2014 10:20:15 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WIbaU-000280-U0
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 10:19:39 +0000
From: Richard Mortier 
To: Amir Chaudhry 
Date: Wed, 26 Feb 2014 10:19:37 +0000
Thread-Topic: [MirageOS-devel] Problem with `mirage run`on unix build of
	static_website
Thread-Index: Ac8y3ED66oVM2jceQiW2+Qw3aE5O3Q==
Message-ID: 
References: <428C7B00B03E6C45AA850C87DC9DF3C65FACB1EE1D@EXCHANGE1.ad.nottingham.ac.uk>
	
In-Reply-To: 
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Problem with `mirage run`on unix build of
 static_website
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 26 Feb 2014, at 10:12, Amir Chaudhry  wrote:

> Helpful info, thanks!
> 
> There's a file called dispatch.ml and it looks like the piece I need is in there [1].  However, I'm not sure how to edit it to get what I want.  I'm guessing it involves adding some more code to try different locations for the content before raising the exception (see lines 39 40 at link below).
> 
> [1] https://github.com/mirage/mirage-skeleton/blob/master/static_website/dispatch.ml#L32

yup, that's it. (i should really pull this kind of thing into cowabloga as it's fairly standard behaviour if it's not already there. proposal rebuttals and other documents to write in the next day or two, but i'll try and do that later this week.)

look at line 34 -- what i'd do is check the list "segments" and if the last element is "index.html", drop it before doing the String.concat to create the path that's tried...

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 11:06:22 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 11:06: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 1WIcJg-0005GC-6m; Wed, 26 Feb 2014 11:06:20 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIcJe-0005G7-GS
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 11:06:18 +0000
Received: from [85.158.139.211:43852] by server-7.bemta-5.messagelabs.com id
	95/24-14867-9AACD035; Wed, 26 Feb 2014 11:06:17 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-9.tower-206.messagelabs.com!1393412776!6327013!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8563 invoked from network); 26 Feb 2014 11:06:16 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-9.tower-206.messagelabs.com with SMTP;
	26 Feb 2014 11:06:16 -0000
Received: (qmail 25137 invoked by uid 634); 26 Feb 2014 11:06:15 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Wed, 26 Feb 2014 11:06:13 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <530C71B7.1030407@xen.org>
Date: Wed, 26 Feb 2014 11:06:12 +0000
Message-Id: <0E829CDF-9507-424F-A34D-9746A831BFD7@recoil.org>
References: 
	<20140224232301.GD12291@dark.recoil.org> <530C71B7.1030407@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Lars Kurth ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] [Xen Project] Your organization application
	has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 25 Feb 2014, at 10:34, Lars Kurth  wrote:

> On 24/02/2014 23:23, Anil Madhavapeddy wrote:
>> [ dropping CC to just mirageos-devel ]
>> 
>> This is excellent news for us! I have a slight fear that some of the
>> projects we suggested on the Xen wiki require a good working knowledge of
>> both Xen and OCaml.  In practise, it's likely that we'll get one or the
>> other, and so we should take the chance to focus the projects a little
>> more to ensure that interns can succeed at them (as opposed to the
>> projects that *we* would like to work on :-)
> Maybe you can add easier projects to the list, or break existing projects into pieces?
> Any mentors, please create accounts on melange
> * aka https://www.google-melange.com/gsoc/homepage/google/gsoc2014
> * sign in
> * and fill out https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 - "chose Xen Project"

I've signed up as a mentor -- Dave/Mort, are you in for this?

Also put up a blog post with some tips to prospective students: 
http://openmirage.org/blog/applying-for-gsoc2014

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 11:06:22 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 11:06: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 1WIcJg-0005GC-6m; Wed, 26 Feb 2014 11:06:20 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIcJe-0005G7-GS
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 11:06:18 +0000
Received: from [85.158.139.211:43852] by server-7.bemta-5.messagelabs.com id
	95/24-14867-9AACD035; Wed, 26 Feb 2014 11:06:17 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-9.tower-206.messagelabs.com!1393412776!6327013!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8563 invoked from network); 26 Feb 2014 11:06:16 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-9.tower-206.messagelabs.com with SMTP;
	26 Feb 2014 11:06:16 -0000
Received: (qmail 25137 invoked by uid 634); 26 Feb 2014 11:06:15 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.94]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Wed, 26 Feb 2014 11:06:13 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: <530C71B7.1030407@xen.org>
Date: Wed, 26 Feb 2014 11:06:12 +0000
Message-Id: <0E829CDF-9507-424F-A34D-9746A831BFD7@recoil.org>
References: 
	<20140224232301.GD12291@dark.recoil.org> <530C71B7.1030407@xen.org>
To: Lars Kurth 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Lars Kurth ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] [Xen Project] Your organization application
	has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 25 Feb 2014, at 10:34, Lars Kurth  wrote:

> On 24/02/2014 23:23, Anil Madhavapeddy wrote:
>> [ dropping CC to just mirageos-devel ]
>> 
>> This is excellent news for us! I have a slight fear that some of the
>> projects we suggested on the Xen wiki require a good working knowledge of
>> both Xen and OCaml.  In practise, it's likely that we'll get one or the
>> other, and so we should take the chance to focus the projects a little
>> more to ensure that interns can succeed at them (as opposed to the
>> projects that *we* would like to work on :-)
> Maybe you can add easier projects to the list, or break existing projects into pieces?
> Any mentors, please create accounts on melange
> * aka https://www.google-melange.com/gsoc/homepage/google/gsoc2014
> * sign in
> * and fill out https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 - "chose Xen Project"

I've signed up as a mentor -- Dave/Mort, are you in for this?

Also put up a blog post with some tips to prospective students: 
http://openmirage.org/blog/applying-for-gsoc2014

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 11:35:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 11:35: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 1WIcmC-0005XK-B1; Wed, 26 Feb 2014 11:35:48 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIcmA-0005X8-Uf
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 11:35:47 +0000
Received: from [85.158.139.211:53232] by server-15.bemta-5.messagelabs.com id
	B4/F5-24395-291DD035; Wed, 26 Feb 2014 11:35:46 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-8.tower-206.messagelabs.com!1393414543!6367512!1
X-Originating-IP: [209.85.220.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19965 invoked from network); 26 Feb 2014 11:35:45 -0000
Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com)
	(209.85.220.45)
	by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	26 Feb 2014 11:35:45 -0000
Received: by mail-pa0-f45.google.com with SMTP id lf10so859890pab.32
	for ;
	Wed, 26 Feb 2014 03:35:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=AA/j8pYOdRU79TqV89X7CoLWICU2fkNfJYhKoJxKuOY=;
	b=psQWg3U7fERe+5W3EOnXPM4BE11tW0BduSCE46b5NHXJqr4r5wNuQOSl9B+fRUve6R
	wN/ey1q+gFieVktIJkL0pwsdiiJVIyc5ymolz1tG1PbLM66bGc90ip4/j2SZG/Y1pcB5
	u8/z185dsATIRXDQsSERIQnf78x92Uec739jQxIe9jBtVQwqzxvFr7ezukZY6qGgEFFR
	n5/eG/K6d2seD1QVmI+quj77pXbnH1lp8CMv6pTBJIHcBIOCigGa4lO4MUPQTWdD5J0J
	DHqkGqSnIyJ6IFtJYEVwKy2izchXHqVRA5s8S4ZymrfZ6any4FyChafkBrCfqv5lJUdG
	RfQQ==
MIME-Version: 1.0
X-Received: by 10.68.245.162 with SMTP id xp2mr6125072pbc.69.1393414542848;
	Wed, 26 Feb 2014 03:35:42 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Wed, 26 Feb 2014 03:35:42 -0800 (PST)
Date: Wed, 26 Feb 2014 11:35:42 +0000
Message-ID: 
From: David Scott 
To: "mirageos-devel@lists.xenproject.org" 
Subject: [MirageOS-devel] Mirage weekly call, today (wed) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5466367514946954897=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============5466367514946954897==
Content-Type: multipart/alternative; boundary=047d7b1637edd9f65304f34d9aa5

--047d7b1637edd9f65304f34d9aa5
Content-Type: text/plain; charset=ISO-8859-1

Agenda:
* GSoC, yay
* homepage progress

Please send other agenda items to be before the meeting and I'll collate.
Amir has kindly offered to take minutes, provided the agenda is clearly
stated before the meeting...

1.  Please join my meeting.
https://www1.gotomeeting.com/join/591890401

2.  Use your microphone and speakers (VoIP) - a headset is recommended.
 Or, call in using your telephone.

United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151
1817

United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017

Access Code: 591-890-401
Audio PIN: Shown after joining the meeting

Meeting ID: 591-890-401

-- 
Dave Scott

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


Agenda:
* =
GSoC, yay
*=
 homepage progress



Please send other agen=
da items to be before the meeting and I'll collate. Amir has kindly off=
ered to take minutes, provided the agenda is clearly stated before the meet=
ing...



1. =A0Please join my m=
eeting.



2. =A0Use your microph=
one and speakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0i=
n using your telephone.



United Kingdom (toll-f=
ree): 0 808 168 0209 United Kingdom:=A0+44 (0) 207 151 18=
17



United States (toll-fr=
ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00=
17



Access Code: 591-890-4=
01
Audio PI=
N: Shown after joining the meeting



Meeting ID: 591-890-40=
1

-- 
Dave Scott



--047d7b1637edd9f65304f34d9aa5--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============5466367514946954897==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 11:35:50 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 11:35: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 1WIcmC-0005XK-B1; Wed, 26 Feb 2014 11:35:48 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIcmA-0005X8-Uf
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 11:35:47 +0000
Received: from [85.158.139.211:53232] by server-15.bemta-5.messagelabs.com id
	B4/F5-24395-291DD035; Wed, 26 Feb 2014 11:35:46 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-8.tower-206.messagelabs.com!1393414543!6367512!1
X-Originating-IP: [209.85.220.45]
X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19965 invoked from network); 26 Feb 2014 11:35:45 -0000
Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com)
	(209.85.220.45)
	by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	26 Feb 2014 11:35:45 -0000
Received: by mail-pa0-f45.google.com with SMTP id lf10so859890pab.32
	for ;
	Wed, 26 Feb 2014 03:35:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=AA/j8pYOdRU79TqV89X7CoLWICU2fkNfJYhKoJxKuOY=;
	b=psQWg3U7fERe+5W3EOnXPM4BE11tW0BduSCE46b5NHXJqr4r5wNuQOSl9B+fRUve6R
	wN/ey1q+gFieVktIJkL0pwsdiiJVIyc5ymolz1tG1PbLM66bGc90ip4/j2SZG/Y1pcB5
	u8/z185dsATIRXDQsSERIQnf78x92Uec739jQxIe9jBtVQwqzxvFr7ezukZY6qGgEFFR
	n5/eG/K6d2seD1QVmI+quj77pXbnH1lp8CMv6pTBJIHcBIOCigGa4lO4MUPQTWdD5J0J
	DHqkGqSnIyJ6IFtJYEVwKy2izchXHqVRA5s8S4ZymrfZ6any4FyChafkBrCfqv5lJUdG
	RfQQ==
MIME-Version: 1.0
X-Received: by 10.68.245.162 with SMTP id xp2mr6125072pbc.69.1393414542848;
	Wed, 26 Feb 2014 03:35:42 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Wed, 26 Feb 2014 03:35:42 -0800 (PST)
Date: Wed, 26 Feb 2014 11:35:42 +0000
Message-ID: 
From: David Scott 
To: "mirageos-devel@lists.xenproject.org" 
Subject: [MirageOS-devel] Mirage weekly call, today (wed) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5466367514946954897=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============5466367514946954897==
Content-Type: multipart/alternative; boundary=047d7b1637edd9f65304f34d9aa5

--047d7b1637edd9f65304f34d9aa5
Content-Type: text/plain; charset=ISO-8859-1

Agenda:
* GSoC, yay
* homepage progress

Please send other agenda items to be before the meeting and I'll collate.
Amir has kindly offered to take minutes, provided the agenda is clearly
stated before the meeting...

1.  Please join my meeting.
https://www1.gotomeeting.com/join/591890401

2.  Use your microphone and speakers (VoIP) - a headset is recommended.
 Or, call in using your telephone.

United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151
1817

United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017

Access Code: 591-890-401
Audio PIN: Shown after joining the meeting

Meeting ID: 591-890-401

-- 
Dave Scott

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


Agenda:
* =
GSoC, yay
*=
 homepage progress



Please send other agen=
da items to be before the meeting and I'll collate. Amir has kindly off=
ered to take minutes, provided the agenda is clearly stated before the meet=
ing...



1. =A0Please join my m=
eeting.



2. =A0Use your microph=
one and speakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0i=
n using your telephone.



United Kingdom (toll-f=
ree): 0 808 168 0209 United Kingdom:=A0+44 (0) 207 151 18=
17



United States (toll-fr=
ee):=A01 877 309 2070=A0United States:=A0+1 (626) 521-00=
17



Access Code: 591-890-4=
01
Audio PI=
N: Shown after joining the meeting



Meeting ID: 591-890-40=
1

-- 
Dave Scott



--047d7b1637edd9f65304f34d9aa5--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============5466367514946954897==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 11:40:34 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 11:40: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 1WIcqn-0005eJ-OO; Wed, 26 Feb 2014 11:40:33 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIcqm-0005eE-Hl
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 11:40:32 +0000
Received: from [85.158.137.68:23155] by server-9.bemta-3.messagelabs.com id
	65/37-10184-FA2DD035; Wed, 26 Feb 2014 11:40:31 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-7.tower-31.messagelabs.com!1393414831!4333603!1
X-Originating-IP: [131.111.8.142]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8282 invoked from network); 26 Feb 2014 11:40:31 -0000
Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk)
	(131.111.8.142)
	by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 26 Feb 2014 11:40:31 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from dhcp-172-17-153-57.eduroam.lapwing.private.cam.ac.uk
	([172.17.153.57]:53903)
	by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WIcqk-00038I-9e (Exim 4.82_3-c0e5623)
	(return-path ); Wed, 26 Feb 2014 11:40:31 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: 
Date: Wed, 26 Feb 2014 11:40:30 +0000
Message-Id: <5CC03483-8A4A-4F5C-B7FB-DAE839A04BC1@cam.ac.uk>
References: 
To: David Scott 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage weekly call, today (wed) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

I should have sent these to you in advance (sorry).
Some sub-items under homepages I'd like to bring up are:

- tweaks and configs to static sites (best way forward)
- status of punk (set up for kernels etc)
- deployment of static sites to punk
- tutorials/wiki pages

Looking forward to it!

Amir


On 26 Feb 2014, at 11:35, David Scott  wrote:

> Agenda:
> * GSoC, yay
> * homepage progress
> 
> Please send other agenda items to be before the meeting and I'll collate. Amir has kindly offered to take minutes, provided the agenda is clearly stated before the meeting...
> 
> 1.  Please join my meeting.
> https://www1.gotomeeting.com/join/591890401
> 
> 2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, call in using your telephone.
> 
> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817
> 
> United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017
> 
> Access Code: 591-890-401
> Audio PIN: Shown after joining the meeting
> 
> Meeting ID: 591-890-401
> 
> -- 
> Dave Scott
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 11:40:34 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 11:40: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 1WIcqn-0005eJ-OO; Wed, 26 Feb 2014 11:40:33 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIcqm-0005eE-Hl
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 11:40:32 +0000
Received: from [85.158.137.68:23155] by server-9.bemta-3.messagelabs.com id
	65/37-10184-FA2DD035; Wed, 26 Feb 2014 11:40:31 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-7.tower-31.messagelabs.com!1393414831!4333603!1
X-Originating-IP: [131.111.8.142]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8282 invoked from network); 26 Feb 2014 11:40:31 -0000
Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk)
	(131.111.8.142)
	by server-7.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 26 Feb 2014 11:40:31 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from dhcp-172-17-153-57.eduroam.lapwing.private.cam.ac.uk
	([172.17.153.57]:53903)
	by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1WIcqk-00038I-9e (Exim 4.82_3-c0e5623)
	(return-path ); Wed, 26 Feb 2014 11:40:31 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry 
In-Reply-To: 
Date: Wed, 26 Feb 2014 11:40:30 +0000
Message-Id: <5CC03483-8A4A-4F5C-B7FB-DAE839A04BC1@cam.ac.uk>
References: 
To: David Scott 
X-Mailer: Apple Mail (2.1510)
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage weekly call, today (wed) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

I should have sent these to you in advance (sorry).
Some sub-items under homepages I'd like to bring up are:

- tweaks and configs to static sites (best way forward)
- status of punk (set up for kernels etc)
- deployment of static sites to punk
- tutorials/wiki pages

Looking forward to it!

Amir


On 26 Feb 2014, at 11:35, David Scott  wrote:

> Agenda:
> * GSoC, yay
> * homepage progress
> 
> Please send other agenda items to be before the meeting and I'll collate. Amir has kindly offered to take minutes, provided the agenda is clearly stated before the meeting...
> 
> 1.  Please join my meeting.
> https://www1.gotomeeting.com/join/591890401
> 
> 2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, call in using your telephone.
> 
> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817
> 
> United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017
> 
> Access Code: 591-890-401
> Audio PIN: Shown after joining the meeting
> 
> Meeting ID: 591-890-401
> 
> -- 
> Dave Scott
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 15:41:19 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 15:41:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIgbg-000367-FX; Wed, 26 Feb 2014 15:41:12 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIgbe-000361-P2
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 15:41:11 +0000
Received: from [85.158.137.68:32975] by server-2.bemta-3.messagelabs.com id
	0D/62-06531-51B0E035; Wed, 26 Feb 2014 15:41:09 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-11.tower-31.messagelabs.com!1393429266!4402813!1
X-Originating-IP: [209.85.128.182]
X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26274 invoked from network); 26 Feb 2014 15:41:07 -0000
Received: from mail-ve0-f182.google.com (HELO mail-ve0-f182.google.com)
	(209.85.128.182)
	by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	26 Feb 2014 15:41:07 -0000
Received: by mail-ve0-f182.google.com with SMTP id jy13so2331012veb.41
	for ;
	Wed, 26 Feb 2014 07:41:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=XeEl2WP2yNsqELPCTXG1Kaoa3QCc6tgljCaRVC3Rq1U=;
	b=XnULdTNut85LWSuU53fvrAkkjREkkwQNnN2uVFhrsfuyOxHwcmBdZ/iwCuxfbgyoEv
	IzSsXskYfOCaEFnvSn+9/XgOyWeUN2FwVcmccHQPIzyAy6r/UrEWLVfI5C4qN5JLssav
	ofpWyYpl0mRmdTKArcGRBUt0p4kT7dM9oHFEy53qBRZAO2jGuAgaGcL9SD9ibocM91zv
	OlD6QkR0DKA65QmWDAuN/1KDJSDWO2xdIAtVUrZampGQ0fLNb9BEEqG66bOJbvy0ock5
	yJ2BkEZGOwwI++tCfQDUJSva7n1j2rDuOdnV3IZs6s++VTW3Y7AW8tcFvFGRv+a8TCS7
	lt7A==
MIME-Version: 1.0
X-Received: by 10.58.188.78 with SMTP id fy14mr6512336vec.23.1393429265637;
	Wed, 26 Feb 2014 07:41:05 -0800 (PST)
Received: by 10.52.109.2 with HTTP; Wed, 26 Feb 2014 07:41:05 -0800 (PST)
In-Reply-To: <5CC03483-8A4A-4F5C-B7FB-DAE839A04BC1@cam.ac.uk>
References: 
	<5CC03483-8A4A-4F5C-B7FB-DAE839A04BC1@cam.ac.uk>
Date: Wed, 26 Feb 2014 15:41:05 +0000
Message-ID: 
From: David Scott 
To: Amir Chaudhry 
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage weekly call, today (wed) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3299744159271084917=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============3299744159271084917==
Content-Type: multipart/alternative; boundary=089e013a12f065f00a04f3510830

--089e013a12f065f00a04f3510830
Content-Type: text/plain; charset=ISO-8859-1

OK, with less than 30 minutes to go I declare the agenda has become stable
with:

* GSoC
* homepages
- tweaks and configs to static sites (best way forward)
- status of punk (set up for kernels etc)
- deployment of static sites to punk
- tutorials/wiki pages

Cheers,
Dave

On Wed, Feb 26, 2014 at 11:40 AM, Amir Chaudhry  wrote:

> I should have sent these to you in advance (sorry).
> Some sub-items under homepages I'd like to bring up are:
>
> - tweaks and configs to static sites (best way forward)
> - status of punk (set up for kernels etc)
> - deployment of static sites to punk
> - tutorials/wiki pages
>
> Looking forward to it!
>
> Amir
>
>
> On 26 Feb 2014, at 11:35, David Scott  wrote:
>
> > Agenda:
> > * GSoC, yay
> > * homepage progress
> >
> > Please send other agenda items to be before the meeting and I'll
> collate. Amir has kindly offered to take minutes, provided the agenda is
> clearly stated before the meeting...
> >
> > 1.  Please join my meeting.
> > https://www1.gotomeeting.com/join/591890401
> >
> > 2.  Use your microphone and speakers (VoIP) - a headset is recommended.
>  Or, call in using your telephone.
> >
> > United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207
> 151 1817
> >
> > United States (toll-free): 1 877 309 2070 United States: +1 (626)
> 521-0017
> >
> > Access Code: 591-890-401
> > Audio PIN: Shown after joining the meeting
> >
> > Meeting ID: 591-890-401
> >
> > --
> > Dave Scott
> > _______________________________________________
> > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenproject.org
> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>
>


-- 
Dave Scott

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


OK, with less than 30 minutes to go I declare the agenda h=
as become stable with:

* GSoC
* homepages=

- tw=
eaks and configs to static sites (best way forward)

- status of pun=
k (set up for kernels etc)
- deployment of static sites to punk

- tutorials/wik=
i pages

Cheers,
Dave


On Wed, Feb 26, 2014 at 11:40 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:

I should have sent these to you in advance (sorry).

Some sub-items under homepages I'd like to bring up are:



- tweaks and configs to static sites (best way forward)

- status of punk (set up for kernels etc)

- deployment of static sites to punk

- tutorials/wiki pages



Looking forward to it!



Amir






On 26 Feb 2014, at 11:35, David Scott <scott.dj@gmail.com> wrote:



> Agenda:

> * GSoC, yay

> * homepage progress

>

> Please send other agenda items to be before the meeting and I'll c=
ollate. Amir has kindly offered to take minutes, provided the agenda is cle=
arly stated before the meeting...

>

> 1. =A0Please join my meeting.

> https://www1.gotomeeting.com/join/591890401

>

> 2. =A0Use your microphone and speakers (VoIP) - a headset is recommend=
ed. =A0Or, call in using your telephone.

>

> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207=
 151 1817

>

> United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017

>

> Access Code: 591-890-401

> Audio PIN: Shown after joining the meeting

>

> Meeting ID: 591-890-401

>

> --

> Dave Scott


> _______________________________________________

> MirageOS-devel mailing list

> MirageOS-devel@=
lists.xenproject.org

> http://lists.xenproject.org/cgi-bin/mailman/lis=
tinfo/mirageos-devel







-- 
Dave Scott



--089e013a12f065f00a04f3510830--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============3299744159271084917==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 15:41:19 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 15:41:19 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIgbg-000367-FX; Wed, 26 Feb 2014 15:41:12 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIgbe-000361-P2
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 15:41:11 +0000
Received: from [85.158.137.68:32975] by server-2.bemta-3.messagelabs.com id
	0D/62-06531-51B0E035; Wed, 26 Feb 2014 15:41:09 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-11.tower-31.messagelabs.com!1393429266!4402813!1
X-Originating-IP: [209.85.128.182]
X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26274 invoked from network); 26 Feb 2014 15:41:07 -0000
Received: from mail-ve0-f182.google.com (HELO mail-ve0-f182.google.com)
	(209.85.128.182)
	by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	26 Feb 2014 15:41:07 -0000
Received: by mail-ve0-f182.google.com with SMTP id jy13so2331012veb.41
	for ;
	Wed, 26 Feb 2014 07:41:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=XeEl2WP2yNsqELPCTXG1Kaoa3QCc6tgljCaRVC3Rq1U=;
	b=XnULdTNut85LWSuU53fvrAkkjREkkwQNnN2uVFhrsfuyOxHwcmBdZ/iwCuxfbgyoEv
	IzSsXskYfOCaEFnvSn+9/XgOyWeUN2FwVcmccHQPIzyAy6r/UrEWLVfI5C4qN5JLssav
	ofpWyYpl0mRmdTKArcGRBUt0p4kT7dM9oHFEy53qBRZAO2jGuAgaGcL9SD9ibocM91zv
	OlD6QkR0DKA65QmWDAuN/1KDJSDWO2xdIAtVUrZampGQ0fLNb9BEEqG66bOJbvy0ock5
	yJ2BkEZGOwwI++tCfQDUJSva7n1j2rDuOdnV3IZs6s++VTW3Y7AW8tcFvFGRv+a8TCS7
	lt7A==
MIME-Version: 1.0
X-Received: by 10.58.188.78 with SMTP id fy14mr6512336vec.23.1393429265637;
	Wed, 26 Feb 2014 07:41:05 -0800 (PST)
Received: by 10.52.109.2 with HTTP; Wed, 26 Feb 2014 07:41:05 -0800 (PST)
In-Reply-To: <5CC03483-8A4A-4F5C-B7FB-DAE839A04BC1@cam.ac.uk>
References: 
	<5CC03483-8A4A-4F5C-B7FB-DAE839A04BC1@cam.ac.uk>
Date: Wed, 26 Feb 2014 15:41:05 +0000
Message-ID: 
From: David Scott 
To: Amir Chaudhry 
Cc: "mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] Mirage weekly call, today (wed) 4pm
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============3299744159271084917=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============3299744159271084917==
Content-Type: multipart/alternative; boundary=089e013a12f065f00a04f3510830

--089e013a12f065f00a04f3510830
Content-Type: text/plain; charset=ISO-8859-1

OK, with less than 30 minutes to go I declare the agenda has become stable
with:

* GSoC
* homepages
- tweaks and configs to static sites (best way forward)
- status of punk (set up for kernels etc)
- deployment of static sites to punk
- tutorials/wiki pages

Cheers,
Dave

On Wed, Feb 26, 2014 at 11:40 AM, Amir Chaudhry  wrote:

> I should have sent these to you in advance (sorry).
> Some sub-items under homepages I'd like to bring up are:
>
> - tweaks and configs to static sites (best way forward)
> - status of punk (set up for kernels etc)
> - deployment of static sites to punk
> - tutorials/wiki pages
>
> Looking forward to it!
>
> Amir
>
>
> On 26 Feb 2014, at 11:35, David Scott  wrote:
>
> > Agenda:
> > * GSoC, yay
> > * homepage progress
> >
> > Please send other agenda items to be before the meeting and I'll
> collate. Amir has kindly offered to take minutes, provided the agenda is
> clearly stated before the meeting...
> >
> > 1.  Please join my meeting.
> > https://www1.gotomeeting.com/join/591890401
> >
> > 2.  Use your microphone and speakers (VoIP) - a headset is recommended.
>  Or, call in using your telephone.
> >
> > United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207
> 151 1817
> >
> > United States (toll-free): 1 877 309 2070 United States: +1 (626)
> 521-0017
> >
> > Access Code: 591-890-401
> > Audio PIN: Shown after joining the meeting
> >
> > Meeting ID: 591-890-401
> >
> > --
> > Dave Scott
> > _______________________________________________
> > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenproject.org
> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>
>


-- 
Dave Scott

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


OK, with less than 30 minutes to go I declare the agenda h=
as become stable with:

* GSoC
* homepages=

- tw=
eaks and configs to static sites (best way forward)

- status of pun=
k (set up for kernels etc)
- deployment of static sites to punk

- tutorials/wik=
i pages

Cheers,
Dave


On Wed, Feb 26, 2014 at 11:40 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:

I should have sent these to you in advance (sorry).

Some sub-items under homepages I'd like to bring up are:



- tweaks and configs to static sites (best way forward)

- status of punk (set up for kernels etc)

- deployment of static sites to punk

- tutorials/wiki pages



Looking forward to it!



Amir






On 26 Feb 2014, at 11:35, David Scott <scott.dj@gmail.com> wrote:



> Agenda:

> * GSoC, yay

> * homepage progress

>

> Please send other agenda items to be before the meeting and I'll c=
ollate. Amir has kindly offered to take minutes, provided the agenda is cle=
arly stated before the meeting...

>

> 1. =A0Please join my meeting.

> https://www1.gotomeeting.com/join/591890401

>

> 2. =A0Use your microphone and speakers (VoIP) - a headset is recommend=
ed. =A0Or, call in using your telephone.

>

> United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207=
 151 1817

>

> United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017

>

> Access Code: 591-890-401

> Audio PIN: Shown after joining the meeting

>

> Meeting ID: 591-890-401

>

> --

> Dave Scott


> _______________________________________________

> MirageOS-devel mailing list

> MirageOS-devel@=
lists.xenproject.org

> http://lists.xenproject.org/cgi-bin/mailman/lis=
tinfo/mirageos-devel







-- 
Dave Scott



--089e013a12f065f00a04f3510830--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============3299744159271084917==--


From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 17:10:42 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 17:10: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 1WIi0C-00061Y-Ob; Wed, 26 Feb 2014 17:10:36 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIi0B-00061P-AA
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 17:10:35 +0000
Received: from [193.109.254.147:17909] by server-3.bemta-14.messagelabs.com id
	E5/CB-00432-A002E035; Wed, 26 Feb 2014 17:10:34 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1393434633!7054358!1
X-Originating-IP: [209.85.212.171]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29542 invoked from network); 26 Feb 2014 17:10:33 -0000
Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com)
	(209.85.212.171)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	26 Feb 2014 17:10:33 -0000
Received: by mail-wi0-f171.google.com with SMTP id cc10so6170933wib.10
	for ;
	Wed, 26 Feb 2014 09:10:33 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:mime-version:content-type:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id:references
	:to; bh=DfIqad/I+wgf6lG3jLoq+FiptqR2ku4mrPQ6RyV3Yj8=;
	b=GxM3qY9Hk0z9zky11JY4Ky6tLDR3h8WovtCQu6X1RZAemjNUJVSFDlf6WyoJM1iy8i
	D712DuAkBBMpdt6If5DQYUlt/6g1fr9nDgF9FWuslrv9ctbr0IJ8qlcnmjtuPM38+igs
	zwAamknj/A/dDrB0I+1iwhoba2pnOJKqAsIknHVSmPJieNFXiVAj4ENWkRWw2gu6+qZV
	ZlG8q9ehKBOOL3/bBNKDlxn9nBLncWaD3oBzeMSg+phEWfNmxrJmUMgUQfkbBe5AunpM
	O8PuxBONzX1utzApQikBuwnrLLBdg5vFkSzPAT1Bef1o9Bdr2SLX3Xi53aYWqm2i9sJr
	Yg5Q==
X-Gm-Message-State: ALoCoQmUjraTSHwz7c65nkwoX3RYsxzaVyMIlbUzN2cgkN8Tjk8xaEb+DLZDOpVcHreeNMlT92dd
X-Received: by 10.180.219.66 with SMTP id pm2mr5646980wic.60.1393434633027;
	Wed, 26 Feb 2014 09:10:33 -0800 (PST)
Received: from [192.168.1.15] (212.44.45.208.ip.redstone-isp.net.
	[212.44.45.208])
	by mx.google.com with ESMTPSA id br10sm4068170wjb.3.2014.02.26.09.10.29
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 26 Feb 2014 09:10:30 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
From: Julian Chesterfield 
In-Reply-To: <1FA460E9-D42B-4B1A-BE7E-47233B3FCBA1@nottingham.ac.uk>
Date: Wed, 26 Feb 2014 17:10:29 +0000
Message-Id: <26631AF0-4A65-4C08-A1CA-BCBCF2FB83CF@onapp.com>
References: <99957A9C-EFCD-42FA-973B-54D61FB955A7@recoil.org>
	<1FA460E9-D42B-4B1A-BE7E-47233B3FCBA1@nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1283)
Cc: "mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] auto configuring ip/netmask info
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

I've opened a ticket for this discussion:

https://github.com/mirage/mirage/issues/228

- J

On 25 Feb 2014, at 20:40, Richard Mortier wrote:

> 
> On 25 Feb 2014, at 17:09, Anil Madhavapeddy  wrote:
> 
>> Julian and I were looking into the various Xen config options for networking this morning, and it turns out that the XL/XM toolstacks can both specify a per-VIF ip/netmask/gateway directly in the VIF configuration. e.g.
>> 
>> ```
>> vif = ['bridge=xenbr0,ip=10.0.0.2,netmask=255.255.255.0,gateway=10.0.0.1']
>> 
>> These are written into the VIF backend tree in xenstore.
> 
> aha. i wondered about that. where's the best docs on xenstore -- it's probably something i should know a bit more about.
> 
>> I'd like to take advantage of this by having the network stack automatically probe for it and use it if available (i.e. a 'default' mode in the stack configuration, which can be overridden by the manual IP or DHCP options).
>> 
>> Any thoughts on the best place to put it, though?  The obvious place is in mirage-net-{unix/xen}, but we would need a Xenstore-equivalent for Unix (which has come up several times. Dave, how viable is it to have a simple Unix Xenstore that maps to a filesystem tree?  We can project configuration variables into there for tuntap, and perhaps take care of bridge configuration at the same time as well.
> 
> i can't comment on the viability of a unix equivalent, but that seems to make a lot of sense to me.
> 
>> Another backend that will need an equivalent registry-style interface are the kFreeBSD backend (which could call back into userspace via an ioctl interface).
> 
> what would the js backend do?  (or would the issue simply never arise?)
> 
> -- 
> Cheers,
> 
> R.
> 
> 
> 
> 
> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.
> 
> 
> 
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Wed Feb 26 17:10:42 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Wed, 26 Feb 2014 17:10: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 1WIi0C-00061Y-Ob; Wed, 26 Feb 2014 17:10:36 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIi0B-00061P-AA
	for mirageos-devel@lists.xenproject.org; Wed, 26 Feb 2014 17:10:35 +0000
Received: from [193.109.254.147:17909] by server-3.bemta-14.messagelabs.com id
	E5/CB-00432-A002E035; Wed, 26 Feb 2014 17:10:34 +0000
X-Env-Sender: julian.chesterfield@onapp.com
X-Msg-Ref: server-13.tower-27.messagelabs.com!1393434633!7054358!1
X-Originating-IP: [209.85.212.171]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29542 invoked from network); 26 Feb 2014 17:10:33 -0000
Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com)
	(209.85.212.171)
	by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	26 Feb 2014 17:10:33 -0000
Received: by mail-wi0-f171.google.com with SMTP id cc10so6170933wib.10
	for ;
	Wed, 26 Feb 2014 09:10:33 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:mime-version:content-type:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id:references
	:to; bh=DfIqad/I+wgf6lG3jLoq+FiptqR2ku4mrPQ6RyV3Yj8=;
	b=GxM3qY9Hk0z9zky11JY4Ky6tLDR3h8WovtCQu6X1RZAemjNUJVSFDlf6WyoJM1iy8i
	D712DuAkBBMpdt6If5DQYUlt/6g1fr9nDgF9FWuslrv9ctbr0IJ8qlcnmjtuPM38+igs
	zwAamknj/A/dDrB0I+1iwhoba2pnOJKqAsIknHVSmPJieNFXiVAj4ENWkRWw2gu6+qZV
	ZlG8q9ehKBOOL3/bBNKDlxn9nBLncWaD3oBzeMSg+phEWfNmxrJmUMgUQfkbBe5AunpM
	O8PuxBONzX1utzApQikBuwnrLLBdg5vFkSzPAT1Bef1o9Bdr2SLX3Xi53aYWqm2i9sJr
	Yg5Q==
X-Gm-Message-State: ALoCoQmUjraTSHwz7c65nkwoX3RYsxzaVyMIlbUzN2cgkN8Tjk8xaEb+DLZDOpVcHreeNMlT92dd
X-Received: by 10.180.219.66 with SMTP id pm2mr5646980wic.60.1393434633027;
	Wed, 26 Feb 2014 09:10:33 -0800 (PST)
Received: from [192.168.1.15] (212.44.45.208.ip.redstone-isp.net.
	[212.44.45.208])
	by mx.google.com with ESMTPSA id br10sm4068170wjb.3.2014.02.26.09.10.29
	for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 26 Feb 2014 09:10:30 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
From: Julian Chesterfield 
In-Reply-To: <1FA460E9-D42B-4B1A-BE7E-47233B3FCBA1@nottingham.ac.uk>
Date: Wed, 26 Feb 2014 17:10:29 +0000
Message-Id: <26631AF0-4A65-4C08-A1CA-BCBCF2FB83CF@onapp.com>
References: <99957A9C-EFCD-42FA-973B-54D61FB955A7@recoil.org>
	<1FA460E9-D42B-4B1A-BE7E-47233B3FCBA1@nottingham.ac.uk>
To: Richard Mortier 
X-Mailer: Apple Mail (2.1283)
Cc: "mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] auto configuring ip/netmask info
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

I've opened a ticket for this discussion:

https://github.com/mirage/mirage/issues/228

- J

On 25 Feb 2014, at 20:40, Richard Mortier wrote:

> 
> On 25 Feb 2014, at 17:09, Anil Madhavapeddy  wrote:
> 
>> Julian and I were looking into the various Xen config options for networking this morning, and it turns out that the XL/XM toolstacks can both specify a per-VIF ip/netmask/gateway directly in the VIF configuration. e.g.
>> 
>> ```
>> vif = ['bridge=xenbr0,ip=10.0.0.2,netmask=255.255.255.0,gateway=10.0.0.1']
>> 
>> These are written into the VIF backend tree in xenstore.
> 
> aha. i wondered about that. where's the best docs on xenstore -- it's probably something i should know a bit more about.
> 
>> I'd like to take advantage of this by having the network stack automatically probe for it and use it if available (i.e. a 'default' mode in the stack configuration, which can be overridden by the manual IP or DHCP options).
>> 
>> Any thoughts on the best place to put it, though?  The obvious place is in mirage-net-{unix/xen}, but we would need a Xenstore-equivalent for Unix (which has come up several times. Dave, how viable is it to have a simple Unix Xenstore that maps to a filesystem tree?  We can project configuration variables into there for tuntap, and perhaps take care of bridge configuration at the same time as well.
> 
> i can't comment on the viability of a unix equivalent, but that seems to make a lot of sense to me.
> 
>> Another backend that will need an equivalent registry-style interface are the kFreeBSD backend (which could call back into userspace via an ioctl interface).
> 
> what would the js backend do?  (or would the issue simply never arise?)
> 
> -- 
> Cheers,
> 
> R.
> 
> 
> 
> 
> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.
> 
> 
> 
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 12:05:20 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 12:05:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIziE-00047Z-5z; Thu, 27 Feb 2014 12:05:14 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIziC-00047U-Sq
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 12:05:13 +0000
Received: from [193.109.254.147:27269] by server-5.bemta-14.messagelabs.com id
	F2/49-16688-8F92F035; Thu, 27 Feb 2014 12:05:12 +0000
X-Env-Sender: sa.abramyan@gmail.com
X-Msg-Ref: server-12.tower-27.messagelabs.com!1393502709!3533589!1
X-Originating-IP: [209.85.216.169]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16301 invoked from network); 27 Feb 2014 12:05:10 -0000
Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com)
	(209.85.216.169)
	by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	27 Feb 2014 12:05:10 -0000
Received: by mail-qc0-f169.google.com with SMTP id e9so3104420qcy.0
	for ;
	Thu, 27 Feb 2014 04:05:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=dgAQUTw/WNfjyk8PCF+MAdq8Se23kdL5q0tUAPZAR4M=;
	b=BKeVx7FZwwqaMQ8w77xA7D+1uXYwDa9DMp5NwtwPkCnCvCm9owbIA9AVYtpHnBEgy3
	iRP29mahp3MLiaM99kwKFZladUWoNnFlSv9dT/NAn+dIGkUJOSPWkpRIHiy2eyBc45qE
	URBMD3ldqg/rlf03+HmJF7eVVHXtyEcpv/+M4bDrQgXLS737kYOFwcjoU3qRGZHHL0go
	ApYOvxhcnBGFFoVfLmO9Ayyixe6vSBjYZRo7E/BJoY7Eh5Mu/BuabqJPQ4nfpj8zmPt+
	Am5IDTUw7ECdQBONaCCnjULV6A3ETRKwXy6XKlvxkFg3BidCbbKWN/bgXL1l9t/ltGyL
	jlGw==
MIME-Version: 1.0
X-Received: by 10.224.5.136 with SMTP id 8mr16125162qav.42.1393502709416; Thu,
	27 Feb 2014 04:05:09 -0800 (PST)
Received: by 10.224.102.9 with HTTP; Thu, 27 Feb 2014 04:05:09 -0800 (PST)
Date: Thu, 27 Feb 2014 16:05:09 +0400
Message-ID: 
From: Sergey Abramyan 
To: mirageos-devel@lists.xenproject.org
Subject: [MirageOS-devel] GSoC 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6085975729691653169=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============6085975729691653169==
Content-Type: multipart/alternative; boundary=001a11c2c59afd0bcd04f362215c

--001a11c2c59afd0bcd04f362215c
Content-Type: text/plain; charset=UTF-8

Hello.

My name is Sergey.  I'm from Saint-Petersburg, Russia.

I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost :),
for real projects) and wath this project.
I know very little and use ocaml, but developing a 3 years (2 years -
python and 1 year - erlang). Rules quite small typo in xapi (
https://github.com/xapi-project/xen-api/commit/fe664e7f02c28dd1579d9b18ecc685f70f9166d9)
commit accepted.
I want to do something useful for the project and to support it in the
future.
After reviewing a list of ideas, it is not clear what will take precedence.
What kind of tasks to better navigate?

Thanks.

-- 
Best regards,
Sergey Abramyan

--001a11c2c59afd0bcd04f362215c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


Hel=
lo.

<=
div class=3D"gmail_default" style=3D"font-size:small">My name is Sergey.=C2=
=A0=C2=A0I'm from Saint-Petersburg, Russia=
.



=
I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost :), =
for real projects) and wath this project.


I =
know very little and use ocaml,=C2=A0but developing a 3 years (2 years - py=
thon and 1 year - erlang).=C2=A0Rules quite small typo in xapi (https://github.com/xapi-project/xen-api/commit/fe664e7f02c28d=
d1579d9b18ecc685f70f9166d9) commit accepted.


I =
want to do something useful for the project and to support it in the future=
.
After reviewing a list of ideas, it is not clear what will =
take precedence.=C2=A0


What kind of tasks to better navigate?

=



Th=
anks.

-- 
Best regards,=

Sergey Abramyan



--001a11c2c59afd0bcd04f362215c--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============6085975729691653169==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 12:05:20 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 12:05:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WIziE-00047Z-5z; Thu, 27 Feb 2014 12:05:14 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WIziC-00047U-Sq
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 12:05:13 +0000
Received: from [193.109.254.147:27269] by server-5.bemta-14.messagelabs.com id
	F2/49-16688-8F92F035; Thu, 27 Feb 2014 12:05:12 +0000
X-Env-Sender: sa.abramyan@gmail.com
X-Msg-Ref: server-12.tower-27.messagelabs.com!1393502709!3533589!1
X-Originating-IP: [209.85.216.169]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16301 invoked from network); 27 Feb 2014 12:05:10 -0000
Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com)
	(209.85.216.169)
	by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	27 Feb 2014 12:05:10 -0000
Received: by mail-qc0-f169.google.com with SMTP id e9so3104420qcy.0
	for ;
	Thu, 27 Feb 2014 04:05:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=dgAQUTw/WNfjyk8PCF+MAdq8Se23kdL5q0tUAPZAR4M=;
	b=BKeVx7FZwwqaMQ8w77xA7D+1uXYwDa9DMp5NwtwPkCnCvCm9owbIA9AVYtpHnBEgy3
	iRP29mahp3MLiaM99kwKFZladUWoNnFlSv9dT/NAn+dIGkUJOSPWkpRIHiy2eyBc45qE
	URBMD3ldqg/rlf03+HmJF7eVVHXtyEcpv/+M4bDrQgXLS737kYOFwcjoU3qRGZHHL0go
	ApYOvxhcnBGFFoVfLmO9Ayyixe6vSBjYZRo7E/BJoY7Eh5Mu/BuabqJPQ4nfpj8zmPt+
	Am5IDTUw7ECdQBONaCCnjULV6A3ETRKwXy6XKlvxkFg3BidCbbKWN/bgXL1l9t/ltGyL
	jlGw==
MIME-Version: 1.0
X-Received: by 10.224.5.136 with SMTP id 8mr16125162qav.42.1393502709416; Thu,
	27 Feb 2014 04:05:09 -0800 (PST)
Received: by 10.224.102.9 with HTTP; Thu, 27 Feb 2014 04:05:09 -0800 (PST)
Date: Thu, 27 Feb 2014 16:05:09 +0400
Message-ID: 
From: Sergey Abramyan 
To: mirageos-devel@lists.xenproject.org
Subject: [MirageOS-devel] GSoC 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============6085975729691653169=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============6085975729691653169==
Content-Type: multipart/alternative; boundary=001a11c2c59afd0bcd04f362215c

--001a11c2c59afd0bcd04f362215c
Content-Type: text/plain; charset=UTF-8

Hello.

My name is Sergey.  I'm from Saint-Petersburg, Russia.

I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost :),
for real projects) and wath this project.
I know very little and use ocaml, but developing a 3 years (2 years -
python and 1 year - erlang). Rules quite small typo in xapi (
https://github.com/xapi-project/xen-api/commit/fe664e7f02c28dd1579d9b18ecc685f70f9166d9)
commit accepted.
I want to do something useful for the project and to support it in the
future.
After reviewing a list of ideas, it is not clear what will take precedence.
What kind of tasks to better navigate?

Thanks.

-- 
Best regards,
Sergey Abramyan

--001a11c2c59afd0bcd04f362215c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


Hel=
lo.

<=
div class=3D"gmail_default" style=3D"font-size:small">My name is Sergey.=C2=
=A0=C2=A0I'm from Saint-Petersburg, Russia=
.



=
I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost :), =
for real projects) and wath this project.


I =
know very little and use ocaml,=C2=A0but developing a 3 years (2 years - py=
thon and 1 year - erlang).=C2=A0Rules quite small typo in xapi (https://github.com/xapi-project/xen-api/commit/fe664e7f02c28d=
d1579d9b18ecc685f70f9166d9) commit accepted.


I =
want to do something useful for the project and to support it in the future=
.
After reviewing a list of ideas, it is not clear what will =
take precedence.=C2=A0


What kind of tasks to better navigate?

=



Th=
anks.

-- 
Best regards,=

Sergey Abramyan



--001a11c2c59afd0bcd04f362215c--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============6085975729691653169==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 14:30:45 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 14:30: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 1WJ1yy-0001sw-JA; Thu, 27 Feb 2014 14:30:40 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WJ1yw-0001sh-W3
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 14:30:39 +0000
Received: from [85.158.137.68:6515] by server-5.bemta-3.messagelabs.com id
	C5/F3-04712-E0C4F035; Thu, 27 Feb 2014 14:30:38 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-4.tower-31.messagelabs.com!1393511437!3366732!1
X-Originating-IP: [93.95.15.170]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32492 invoked from network); 27 Feb 2014 14:30:37 -0000
Received: from engine03-20433-3.icritical.com (HELO
	engine03-20433-3.icritical.com) (93.95.15.170)
	by server-4.tower-31.messagelabs.com with SMTP;
	27 Feb 2014 14:30:37 -0000
Received: (qmail 17311 invoked from network); 27 Feb 2014 14:30:58 -0000
Received: from localhost (127.0.0.1)
	by engine03-20433-3.icritical.com with SMTP; 27 Feb 2014 14:30:58 -0000
Received: from engine03-20433-3.icritical.com ([127.0.0.1])
	by localhost (engine03-20433-3.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 17142-03 for ;
	Thu, 27 Feb 2014 14:30:58 +0000 (GMT)
Received: (qmail 16481 invoked by uid 599); 27 Feb 2014 14:30:09 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP;
	Thu, 27 Feb 2014 14:30:09 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WJ1y3-0003lN-HK; Thu, 27 Feb 2014 14:29:43 +0000
From: Richard Mortier 
To: Anil Madhavapeddy , Lars Kurth 
Date: Thu, 27 Feb 2014 14:29:42 +0000
Thread-Topic: [MirageOS-devel] [Xen Project] Your organization application
	has been accepted.
Thread-Index: Ac8zyFrHWHMn/mMBTguKmKPEXVGPQw==
Message-ID: <59CB0C32-A571-4330-A6A0-AE779473E566@nottingham.ac.uk>
References: 
	<20140224232301.GD12291@dark.recoil.org> <530C71B7.1030407@xen.org>
	<0E829CDF-9507-424F-A34D-9746A831BFD7@recoil.org>
In-Reply-To: <0E829CDF-9507-424F-A34D-9746A831BFD7@recoil.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine03-20433-3.icritical.com
Cc: Lars Kurth ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] [Xen Project] Your organization
	application	has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 26 Feb 2014, at 11:06, Anil Madhavapeddy  wrote:

> On 25 Feb 2014, at 10:34, Lars Kurth  wrote:
> 
>> Maybe you can add easier projects to the list, or break existing projects into pieces?
>> Any mentors, please create accounts on melange
>> * aka https://www.google-melange.com/gsoc/homepage/google/gsoc2014
>> * sign in
>> * and fill out https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 - "chose Xen Project"
> 
> I've signed up as a mentor -- Dave/Mort, are you in for this?

done. signed up.

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 14:30:45 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 14:30: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 1WJ1yy-0001sw-JA; Thu, 27 Feb 2014 14:30:40 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WJ1yw-0001sh-W3
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 14:30:39 +0000
Received: from [85.158.137.68:6515] by server-5.bemta-3.messagelabs.com id
	C5/F3-04712-E0C4F035; Thu, 27 Feb 2014 14:30:38 +0000
X-Env-Sender: Richard.Mortier@nottingham.ac.uk
X-Msg-Ref: server-4.tower-31.messagelabs.com!1393511437!3366732!1
X-Originating-IP: [93.95.15.170]
X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG,
	MIME_QP_LONG_LINE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32492 invoked from network); 27 Feb 2014 14:30:37 -0000
Received: from engine03-20433-3.icritical.com (HELO
	engine03-20433-3.icritical.com) (93.95.15.170)
	by server-4.tower-31.messagelabs.com with SMTP;
	27 Feb 2014 14:30:37 -0000
Received: (qmail 17311 invoked from network); 27 Feb 2014 14:30:58 -0000
Received: from localhost (127.0.0.1)
	by engine03-20433-3.icritical.com with SMTP; 27 Feb 2014 14:30:58 -0000
Received: from engine03-20433-3.icritical.com ([127.0.0.1])
	by localhost (engine03-20433-3.icritical.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with SMTP id 17142-03 for ;
	Thu, 27 Feb 2014 14:30:58 +0000 (GMT)
Received: (qmail 16481 invoked by uid 599); 27 Feb 2014 14:30:09 -0000
Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65)
	by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP;
	Thu, 27 Feb 2014 14:30:09 +0000
Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132])
	by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128)
	(Exim 4.77) (envelope-from )
	id 1WJ1y3-0003lN-HK; Thu, 27 Feb 2014 14:29:43 +0000
From: Richard Mortier 
To: Anil Madhavapeddy , Lars Kurth 
Date: Thu, 27 Feb 2014 14:29:42 +0000
Thread-Topic: [MirageOS-devel] [Xen Project] Your organization application
	has been accepted.
Thread-Index: Ac8zyFrHWHMn/mMBTguKmKPEXVGPQw==
Message-ID: <59CB0C32-A571-4330-A6A0-AE779473E566@nottingham.ac.uk>
References: 
	<20140224232301.GD12291@dark.recoil.org> <530C71B7.1030407@xen.org>
	<0E829CDF-9507-424F-A34D-9746A831BFD7@recoil.org>
In-Reply-To: <0E829CDF-9507-424F-A34D-9746A831BFD7@recoil.org>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
MIME-Version: 1.0
X-Virus-Scanned: by iCritical at engine03-20433-3.icritical.com
Cc: Lars Kurth ,
	"mirageos-devel@lists.xenproject.org" 
Subject: Re: [MirageOS-devel] [Xen Project] Your organization
	application	has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org


On 26 Feb 2014, at 11:06, Anil Madhavapeddy  wrote:

> On 25 Feb 2014, at 10:34, Lars Kurth  wrote:
> 
>> Maybe you can add easier projects to the list, or break existing projects into pieces?
>> Any mentors, please create accounts on melange
>> * aka https://www.google-melange.com/gsoc/homepage/google/gsoc2014
>> * sign in
>> * and fill out https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 - "chose Xen Project"
> 
> I've signed up as a mentor -- Dave/Mort, are you in for this?

done. signed up.

-- 
Cheers,

R.




This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.





_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 15:52:35 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 15:52: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 1WJ3GA-0007mx-6l; Thu, 27 Feb 2014 15:52:30 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJ3G8-0007mb-C8
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 15:52:28 +0000
Received: from [85.158.137.68:46127] by server-8.bemta-3.messagelabs.com id
	A6/32-16039-B3F5F035; Thu, 27 Feb 2014 15:52:27 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-9.tower-31.messagelabs.com!1393516219!4603507!1
X-Originating-IP: [209.85.192.180]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 532 invoked from network); 27 Feb 2014 15:50:25 -0000
Received: from mail-pd0-f180.google.com (HELO mail-pd0-f180.google.com)
	(209.85.192.180)
	by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	27 Feb 2014 15:50:25 -0000
Received: by mail-pd0-f180.google.com with SMTP id y10so2582024pdj.25
	for ;
	Thu, 27 Feb 2014 07:50:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=HEfuCVziEBcQwNaoTUjM5hXWjtVbSANfC0yASpgLOlM=;
	b=u6JDam49OTdLNA+0g25nVVvHH76zZSnEDt9SInvxZxyMxdqvgGxfTvagb8NM2w6O4N
	wgq/nYXxLcwBPRqRJR501iGNJRVyO0ZkFZ6c+GziNszyUW4tfAf41tBKQg7PNtpJVnXl
	22G97STq7kd8dXYIPqK5ODy5airV3TlLjHt9ljfjvy8DWukQiHiaA4gZ8xLzjX+dqvZU
	A5+u5+Ng8ElyF1iZ254vmMURfMfiBjvVUdwkiQaTA9MDUJfUVEgtDJoZ9QMdox8utF/s
	bObkssvj7gba3y8VrZQaXkKGQcQhr07+yeR/xoRgZ76yDpSzNu7m3EZ9NL2RP6K5BnIX
	01qA==
MIME-Version: 1.0
X-Received: by 10.68.245.162 with SMTP id xp2mr13987218pbc.69.1393516215269;
	Thu, 27 Feb 2014 07:50:15 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Thu, 27 Feb 2014 07:50:15 -0800 (PST)
In-Reply-To: <59CB0C32-A571-4330-A6A0-AE779473E566@nottingham.ac.uk>
References: 
	<20140224232301.GD12291@dark.recoil.org> <530C71B7.1030407@xen.org>
	<0E829CDF-9507-424F-A34D-9746A831BFD7@recoil.org>
	<59CB0C32-A571-4330-A6A0-AE779473E566@nottingham.ac.uk>
Date: Thu, 27 Feb 2014 15:50:15 +0000
Message-ID: 
From: David Scott 
To: Richard Mortier 
Cc: Lars Kurth ,
	"mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] [Xen Project] Your organization application
 has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8170978645238845038=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============8170978645238845038==
Content-Type: multipart/alternative; boundary=047d7b1637ed00010504f3654723

--047d7b1637ed00010504f3654723
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Feb 27, 2014 at 2:29 PM, Richard Mortier <
Richard.Mortier@nottingham.ac.uk> wrote:

>
> On 26 Feb 2014, at 11:06, Anil Madhavapeddy  wrote:
>
> > On 25 Feb 2014, at 10:34, Lars Kurth  wrote:
> >
> >> Maybe you can add easier projects to the list, or break existing
> projects into pieces?
> >> Any mentors, please create accounts on melange
> >> * aka https://www.google-melange.com/gsoc/homepage/google/gsoc2014
> >> * sign in
> >> * and fill out
> https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 -
> "chose Xen Project"
> >
> > I've signed up as a mentor -- Dave/Mort, are you in for this?
>
> done. signed up.
>

I've also signed up.

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





On Thu, Feb 27, 2014 at 2:29 PM, Richard Mortier =
<R=
ichard.Mortier@nottingham.ac.uk> wrote:




On 26 Feb 2014, at 11:06, Anil Madhavapeddy <anil@recoil.org> wrote:



> On 25 Feb 2014, at 10:34, Lars Kurth <lars.kurth@xen.org> wrote:

>


>> Maybe you can add easier projects to the lis=
t, or break existing projects into pieces?

>> Any mentors, please create accounts on melange

>> * aka https://www.google-melange.com/gsoc/homepage=
/google/gsoc2014

>> * sign in

>> * and fill out https://www.google-melange.c=
om/gsoc/connection/pick/google/gsoc2014 - "chose Xen Project"=



>

> I've signed up as a mentor -- Dave/Mort, are you in for this?




done. signed up.

I've also si=
gned up.




--047d7b1637ed00010504f3654723--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============8170978645238845038==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 15:52:35 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 15:52: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 1WJ3GA-0007mx-6l; Thu, 27 Feb 2014 15:52:30 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJ3G8-0007mb-C8
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 15:52:28 +0000
Received: from [85.158.137.68:46127] by server-8.bemta-3.messagelabs.com id
	A6/32-16039-B3F5F035; Thu, 27 Feb 2014 15:52:27 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-9.tower-31.messagelabs.com!1393516219!4603507!1
X-Originating-IP: [209.85.192.180]
X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 532 invoked from network); 27 Feb 2014 15:50:25 -0000
Received: from mail-pd0-f180.google.com (HELO mail-pd0-f180.google.com)
	(209.85.192.180)
	by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	27 Feb 2014 15:50:25 -0000
Received: by mail-pd0-f180.google.com with SMTP id y10so2582024pdj.25
	for ;
	Thu, 27 Feb 2014 07:50:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=HEfuCVziEBcQwNaoTUjM5hXWjtVbSANfC0yASpgLOlM=;
	b=u6JDam49OTdLNA+0g25nVVvHH76zZSnEDt9SInvxZxyMxdqvgGxfTvagb8NM2w6O4N
	wgq/nYXxLcwBPRqRJR501iGNJRVyO0ZkFZ6c+GziNszyUW4tfAf41tBKQg7PNtpJVnXl
	22G97STq7kd8dXYIPqK5ODy5airV3TlLjHt9ljfjvy8DWukQiHiaA4gZ8xLzjX+dqvZU
	A5+u5+Ng8ElyF1iZ254vmMURfMfiBjvVUdwkiQaTA9MDUJfUVEgtDJoZ9QMdox8utF/s
	bObkssvj7gba3y8VrZQaXkKGQcQhr07+yeR/xoRgZ76yDpSzNu7m3EZ9NL2RP6K5BnIX
	01qA==
MIME-Version: 1.0
X-Received: by 10.68.245.162 with SMTP id xp2mr13987218pbc.69.1393516215269;
	Thu, 27 Feb 2014 07:50:15 -0800 (PST)
Received: by 10.70.55.132 with HTTP; Thu, 27 Feb 2014 07:50:15 -0800 (PST)
In-Reply-To: <59CB0C32-A571-4330-A6A0-AE779473E566@nottingham.ac.uk>
References: 
	<20140224232301.GD12291@dark.recoil.org> <530C71B7.1030407@xen.org>
	<0E829CDF-9507-424F-A34D-9746A831BFD7@recoil.org>
	<59CB0C32-A571-4330-A6A0-AE779473E566@nottingham.ac.uk>
Date: Thu, 27 Feb 2014 15:50:15 +0000
Message-ID: 
From: David Scott 
To: Richard Mortier 
Cc: Lars Kurth ,
	"mirageos-devel@lists.xenproject.org"
	, Anil Madhavapeddy 
Subject: Re: [MirageOS-devel] [Xen Project] Your organization application
 has been accepted.
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8170978645238845038=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============8170978645238845038==
Content-Type: multipart/alternative; boundary=047d7b1637ed00010504f3654723

--047d7b1637ed00010504f3654723
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Feb 27, 2014 at 2:29 PM, Richard Mortier <
Richard.Mortier@nottingham.ac.uk> wrote:

>
> On 26 Feb 2014, at 11:06, Anil Madhavapeddy  wrote:
>
> > On 25 Feb 2014, at 10:34, Lars Kurth  wrote:
> >
> >> Maybe you can add easier projects to the list, or break existing
> projects into pieces?
> >> Any mentors, please create accounts on melange
> >> * aka https://www.google-melange.com/gsoc/homepage/google/gsoc2014
> >> * sign in
> >> * and fill out
> https://www.google-melange.com/gsoc/connection/pick/google/gsoc2014 -
> "chose Xen Project"
> >
> > I've signed up as a mentor -- Dave/Mort, are you in for this?
>
> done. signed up.
>

I've also signed up.

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





On Thu, Feb 27, 2014 at 2:29 PM, Richard Mortier =
<R=
ichard.Mortier@nottingham.ac.uk> wrote:




On 26 Feb 2014, at 11:06, Anil Madhavapeddy <anil@recoil.org> wrote:



> On 25 Feb 2014, at 10:34, Lars Kurth <lars.kurth@xen.org> wrote:

>


>> Maybe you can add easier projects to the lis=
t, or break existing projects into pieces?

>> Any mentors, please create accounts on melange

>> * aka https://www.google-melange.com/gsoc/homepage=
/google/gsoc2014

>> * sign in

>> * and fill out https://www.google-melange.c=
om/gsoc/connection/pick/google/gsoc2014 - "chose Xen Project"=



>

> I've signed up as a mentor -- Dave/Mort, are you in for this?




done. signed up.

I've also si=
gned up.




--047d7b1637ed00010504f3654723--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============8170978645238845038==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 22:44:53 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 22:44: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 1WJ9hA-0006S7-0T; Thu, 27 Feb 2014 22:44:48 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJ9h8-0006Ru-TR
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 22:44:47 +0000
Received: from [193.109.254.147:64442] by server-11.bemta-14.messagelabs.com
	id 2E/A7-24604-EDFBF035; Thu, 27 Feb 2014 22:44:46 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-15.tower-27.messagelabs.com!1393541083!7324916!1
X-Originating-IP: [209.85.192.180]
X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26141 invoked from network); 27 Feb 2014 22:44:45 -0000
Received: from mail-pd0-f180.google.com (HELO mail-pd0-f180.google.com)
	(209.85.192.180)
	by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	27 Feb 2014 22:44:45 -0000
Received: by mail-pd0-f180.google.com with SMTP id y10so3029424pdj.25
	for ;
	Thu, 27 Feb 2014 14:44:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type;
	bh=rjxJndkq86V5fwWAwnuwpj49Bmb9bF4tuGXc4aCbeKk=;
	b=Wq+Jnl5sioX00sGnMYCICg7YlkTBMoQ9B2wD6M8UoIdi9wF15kcwo7wbl2wHn00uJL
	BthpmZwxGau80ylUsgk0ca6v0PZ74bp9FydcNwxv9FrNq6l7ceNdyMF18z6YbO6YCGrM
	sK4eIxacgJsLOV7zbvvnyK61sIEkQhjCYGYNTPrGYtRbA3g3Qipp/ePJSFnTS2ZNK3AZ
	nnITfA8tCpOCOn1NZm9qgzX+DKKgWNXYzmpQ1o9bf0HVOJ2TqKNDbmqCcJb91PPUUzni
	RVVJ1pIX3vLF+NMCy5bmvEkQAHPV5V1di0sxuuZoUDOr2zc0nWVlphjOTFVuhQWBlpxW
	ufrg==
X-Received: by 10.68.4.232 with SMTP id n8mr16015160pbn.114.1393541082849;
	Thu, 27 Feb 2014 14:44:42 -0800 (PST)
Received: from [172.16.26.11] ([121.211.204.213])
	by mx.google.com with ESMTPSA id
	ou9sm17117908pbc.30.2014.02.27.14.44.40 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 27 Feb 2014 14:44:42 -0800 (PST)
Message-ID: <530FBFD6.8040905@xen.org>
Date: Thu, 27 Feb 2014 22:44:38 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org" 
References: <530C9CD0.9070508@xen.org>
In-Reply-To: <530C9CD0.9070508@xen.org>
Cc: Russell Pavlicek 
Subject: Re: [MirageOS-devel] Dates and Location Xen Project Hackathon,
 Xen Project Developer Summit & Meeting
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8702070146054572953=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============8702070146054572953==
Content-Type: multipart/alternative;
 boundary="------------020008090104000901060101"

This is a multi-part message in MIME format.
--------------020008090104000901060101
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 25/02/2014 13:38, Lars Kurth wrote:
> Hi all,
>
> before I go on holidays just a quick note in the 2014 event schedule. 
> This only just came together, but you may want to look into getting 
> travel approvals.
>
> == Xen Project Hackatho, London, late May (exact dates TBD) ==
> Location: London at Rackspaces offices
> Dates: exact dates TBD, but a we are targetting a Thu/Fri at the end 
> of May
> URL: http://wiki.xenproject.org/wiki/Hackathon/May2014
Hi all, the date has been confirmed for May 29-30
Regards
Lars

--------------020008090104000901060101
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    
On 25/02/2014 13:38, Lars Kurth wrote:

    

    

      
      Hi all,

      

      before I go on holidays just a quick note in the 2014 event
      schedule. This only just came together, but you may want to look
      into getting travel approvals.

      

      == Xen Project Hackatho, London, late May (exact dates TBD) ==

      Location: London at Rackspaces offices  

      Dates: exact dates TBD, but a we are targetting a Thu/Fri at the
      end of May

      URL: http://wiki.xenproject.org/wiki/Hackathon/May2014

    

    Hi all, the date has been confirmed for May 29-30

    Regards

    Lars

  


--------------020008090104000901060101--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============8702070146054572953==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 22:44:53 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 22:44: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 1WJ9hA-0006S7-0T; Thu, 27 Feb 2014 22:44:48 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJ9h8-0006Ru-TR
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 22:44:47 +0000
Received: from [193.109.254.147:64442] by server-11.bemta-14.messagelabs.com
	id 2E/A7-24604-EDFBF035; Thu, 27 Feb 2014 22:44:46 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-15.tower-27.messagelabs.com!1393541083!7324916!1
X-Originating-IP: [209.85.192.180]
X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26141 invoked from network); 27 Feb 2014 22:44:45 -0000
Received: from mail-pd0-f180.google.com (HELO mail-pd0-f180.google.com)
	(209.85.192.180)
	by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	27 Feb 2014 22:44:45 -0000
Received: by mail-pd0-f180.google.com with SMTP id y10so3029424pdj.25
	for ;
	Thu, 27 Feb 2014 14:44:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type;
	bh=rjxJndkq86V5fwWAwnuwpj49Bmb9bF4tuGXc4aCbeKk=;
	b=Wq+Jnl5sioX00sGnMYCICg7YlkTBMoQ9B2wD6M8UoIdi9wF15kcwo7wbl2wHn00uJL
	BthpmZwxGau80ylUsgk0ca6v0PZ74bp9FydcNwxv9FrNq6l7ceNdyMF18z6YbO6YCGrM
	sK4eIxacgJsLOV7zbvvnyK61sIEkQhjCYGYNTPrGYtRbA3g3Qipp/ePJSFnTS2ZNK3AZ
	nnITfA8tCpOCOn1NZm9qgzX+DKKgWNXYzmpQ1o9bf0HVOJ2TqKNDbmqCcJb91PPUUzni
	RVVJ1pIX3vLF+NMCy5bmvEkQAHPV5V1di0sxuuZoUDOr2zc0nWVlphjOTFVuhQWBlpxW
	ufrg==
X-Received: by 10.68.4.232 with SMTP id n8mr16015160pbn.114.1393541082849;
	Thu, 27 Feb 2014 14:44:42 -0800 (PST)
Received: from [172.16.26.11] ([121.211.204.213])
	by mx.google.com with ESMTPSA id
	ou9sm17117908pbc.30.2014.02.27.14.44.40 for 
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 27 Feb 2014 14:44:42 -0800 (PST)
Message-ID: <530FBFD6.8040905@xen.org>
Date: Thu, 27 Feb 2014 22:44:38 +0000
From: Lars Kurth 
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" , 
	"xen-api@lists.xen.org" ,
	"mirageos-devel@lists.xenproject.org" 
References: <530C9CD0.9070508@xen.org>
In-Reply-To: <530C9CD0.9070508@xen.org>
Cc: Russell Pavlicek 
Subject: Re: [MirageOS-devel] Dates and Location Xen Project Hackathon,
 Xen Project Developer Summit & Meeting
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============8702070146054572953=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

This is a multi-part message in MIME format.
--===============8702070146054572953==
Content-Type: multipart/alternative;
 boundary="------------020008090104000901060101"

This is a multi-part message in MIME format.
--------------020008090104000901060101
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 25/02/2014 13:38, Lars Kurth wrote:
> Hi all,
>
> before I go on holidays just a quick note in the 2014 event schedule. 
> This only just came together, but you may want to look into getting 
> travel approvals.
>
> == Xen Project Hackatho, London, late May (exact dates TBD) ==
> Location: London at Rackspaces offices
> Dates: exact dates TBD, but a we are targetting a Thu/Fri at the end 
> of May
> URL: http://wiki.xenproject.org/wiki/Hackathon/May2014
Hi all, the date has been confirmed for May 29-30
Regards
Lars

--------------020008090104000901060101
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


  
    
  
  
    
On 25/02/2014 13:38, Lars Kurth wrote:

    

    

      
      Hi all,

      

      before I go on holidays just a quick note in the 2014 event
      schedule. This only just came together, but you may want to look
      into getting travel approvals.

      

      == Xen Project Hackatho, London, late May (exact dates TBD) ==

      Location: London at Rackspaces offices  

      Dates: exact dates TBD, but a we are targetting a Thu/Fri at the
      end of May

      URL: http://wiki.xenproject.org/wiki/Hackathon/May2014

    

    Hi all, the date has been confirmed for May 29-30

    Regards

    Lars

  


--------------020008090104000901060101--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============8702070146054572953==--


From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 23:46:44 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 23:46: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 1WJAf3-0008TS-M4; Thu, 27 Feb 2014 23:46:41 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJAf2-0008TN-V7
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 23:46:41 +0000
Received: from [193.109.254.147:57095] by server-12.bemta-14.messagelabs.com
	id AA/11-17220-06ECF035; Thu, 27 Feb 2014 23:46:40 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-6.tower-27.messagelabs.com!1393544799!7335891!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12491 invoked from network); 27 Feb 2014 23:46:39 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-6.tower-27.messagelabs.com with SMTP;
	27 Feb 2014 23:46:39 -0000
Received: (qmail 28216 invoked by uid 634); 27 Feb 2014 23:46:39 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.62]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 27 Feb 2014 23:46:38 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: 
Date: Thu, 27 Feb 2014 23:46:37 +0000
Message-Id: <14C76B07-6BA2-4FD0-98BE-6F95E6E88A70@recoil.org>
References: 
To: Sergey Abramyan 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] GSoC 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 27 Feb 2014, at 12:05, Sergey Abramyan  wrote:

> Hello.
> 
> My name is Sergey.  I'm from Saint-Petersburg, Russia.
> 
> I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost :), for real projects) and wath this project.
> I know very little and use ocaml, but developing a 3 years (2 years - python and 1 year - erlang). Rules quite small typo in xapi (https://github.com/xapi-project/xen-api/commit/fe664e7f02c28dd1579d9b18ecc685f70f9166d9) commit accepted.
> I want to do something useful for the project and to support it in the future.
> After reviewing a list of ideas, it is not clear what will take precedence. 
> What kind of tasks to better navigate?

Hi Sergey!  If you've used Xapi before, then a good place to start would be the fuzz testing project for Xen.  It would involve building kernels that attempt to stress various components of xcp (e.g. xenstore) and spotting problems and testing expected behaviour (e.g. with different SR backends).

best,
Anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Thu Feb 27 23:46:44 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Thu, 27 Feb 2014 23:46: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 1WJAf3-0008TS-M4; Thu, 27 Feb 2014 23:46:41 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJAf2-0008TN-V7
	for mirageos-devel@lists.xenproject.org; Thu, 27 Feb 2014 23:46:41 +0000
Received: from [193.109.254.147:57095] by server-12.bemta-14.messagelabs.com
	id AA/11-17220-06ECF035; Thu, 27 Feb 2014 23:46:40 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-6.tower-27.messagelabs.com!1393544799!7335891!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12491 invoked from network); 27 Feb 2014 23:46:39 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-6.tower-27.messagelabs.com with SMTP;
	27 Feb 2014 23:46:39 -0000
Received: (qmail 28216 invoked by uid 634); 27 Feb 2014 23:46:39 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO
	[192.168.1.62]) (86.30.244.239)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 27 Feb 2014 23:46:38 +0000
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\))
From: Anil Madhavapeddy 
In-Reply-To: 
Date: Thu, 27 Feb 2014 23:46:37 +0000
Message-Id: <14C76B07-6BA2-4FD0-98BE-6F95E6E88A70@recoil.org>
References: 
To: Sergey Abramyan 
X-Mailer: Apple Mail (2.1812)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] GSoC 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

On 27 Feb 2014, at 12:05, Sergey Abramyan  wrote:

> Hello.
> 
> My name is Sergey.  I'm from Saint-Petersburg, Russia.
> 
> I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost :), for real projects) and wath this project.
> I know very little and use ocaml, but developing a 3 years (2 years - python and 1 year - erlang). Rules quite small typo in xapi (https://github.com/xapi-project/xen-api/commit/fe664e7f02c28dd1579d9b18ecc685f70f9166d9) commit accepted.
> I want to do something useful for the project and to support it in the future.
> After reviewing a list of ideas, it is not clear what will take precedence. 
> What kind of tasks to better navigate?

Hi Sergey!  If you've used Xapi before, then a good place to start would be the fuzz testing project for Xen.  It would involve building kernels that attempt to stress various components of xcp (e.g. xenstore) and spotting problems and testing expected behaviour (e.g. with different SR backends).

best,
Anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 28 07:30:14 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 28 Feb 2014 07:30:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WJHtX-0003MA-Cv; Fri, 28 Feb 2014 07:30:07 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJHtV-0003Ly-9C
	for mirageos-devel@lists.xenproject.org; Fri, 28 Feb 2014 07:30:05 +0000
Received: from [193.109.254.147:40323] by server-13.bemta-14.messagelabs.com
	id 67/42-01226-CFA30135; Fri, 28 Feb 2014 07:30:04 +0000
X-Env-Sender: sa.abramyan@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1393572602!3618995!1
X-Originating-IP: [209.85.216.51]
X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10476 invoked from network); 28 Feb 2014 07:30:03 -0000
Received: from mail-qa0-f51.google.com (HELO mail-qa0-f51.google.com)
	(209.85.216.51)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	28 Feb 2014 07:30:03 -0000
Received: by mail-qa0-f51.google.com with SMTP id j7so307063qaq.24
	for ;
	Thu, 27 Feb 2014 23:30:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=b2yP1yUg11spHnwwOQWJtvNzmhocAB2Ofj3oD+SoTow=;
	b=ma/5x9MnHEbzl4L93BS6TyiAWZxxLge3hOQC1/SK0TbHPkqpM5FpcB6noi/masWeEi
	QrTzUmTzLCYVN4HZc5PKdZJFzfdwykDM6RvglZk15jRsdeFAAh1xj+PAKXbzdWUmqMF2
	qis4uMl+fTsNd+8o3smnROXESvu8huz376M9iXOV5RZtEBnj2T5ryTewG1XiBRA9MnUD
	C7E7S3OThma9L0d5vWzCnjur0dxcdvIVjDdGYyuVcm/EfOEItYxKgtoKsVqHcyak9Scf
	WM/YJTg2iBaarqsv65Jh5JN2TRsUw7grv4xWbrm5jYUN+7VK5rTtho0I6pxB2RyKn0ZK
	69tg==
MIME-Version: 1.0
X-Received: by 10.224.80.134 with SMTP id t6mr1644625qak.34.1393572602472;
	Thu, 27 Feb 2014 23:30:02 -0800 (PST)
Received: by 10.224.102.9 with HTTP; Thu, 27 Feb 2014 23:30:02 -0800 (PST)
In-Reply-To: <14C76B07-6BA2-4FD0-98BE-6F95E6E88A70@recoil.org>
References: 
	<14C76B07-6BA2-4FD0-98BE-6F95E6E88A70@recoil.org>
Date: Fri, 28 Feb 2014 11:30:02 +0400
Message-ID: 
From: Sergey Abramyan 
To: Anil Madhavapeddy 
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] GSoC 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5218535511469939255=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============5218535511469939255==
Content-Type: multipart/alternative; boundary=001a1132e232f06f0f04f372678b

--001a1132e232f06f0f04f372678b
Content-Type: text/plain; charset=UTF-8

Great! There is a test task for this project? After that I could start
working on application.

Thanks.


On Fri, Feb 28, 2014 at 3:46 AM, Anil Madhavapeddy  wrote:

> On 27 Feb 2014, at 12:05, Sergey Abramyan  wrote:
>
> > Hello.
> >
> > My name is Sergey.  I'm from Saint-Petersburg, Russia.
> >
> > I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost
> :), for real projects) and wath this project.
> > I know very little and use ocaml, but developing a 3 years (2 years -
> python and 1 year - erlang). Rules quite small typo in xapi (
> https://github.com/xapi-project/xen-api/commit/fe664e7f02c28dd1579d9b18ecc685f70f9166d9)
> commit accepted.
> > I want to do something useful for the project and to support it in the
> future.
> > After reviewing a list of ideas, it is not clear what will take
> precedence.
> > What kind of tasks to better navigate?
>
> Hi Sergey!  If you've used Xapi before, then a good place to start would
> be the fuzz testing project for Xen.  It would involve building kernels
> that attempt to stress various components of xcp (e.g. xenstore) and
> spotting problems and testing expected behaviour (e.g. with different SR
> backends).
>
> best,
> Anil




-- 
Best regards,
Sergey Abramyan

--001a1132e232f06f0f04f372678b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


Great!=C2=A0There is a test task for this project?=C2=A0After that I=
 could start working on application.



Thanks.



On Fri, Feb 28, 2014 at 3:46 AM, Anil Ma=
dhavapeddy <anil@recoil.org> wrote:


On 27 Feb 2014, at 12:05, Sergey Ab=
ramyan <sa.abramyan@gmail.com> wrote:



> Hello.

>

> My name is Sergey. =C2=A0I'm from Saint-Petersburg, Russia.

>

> I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost=
 :), for real projects) and wath this project.

> I know very little and use ocaml, but developing a 3 years (2 years - =
python and 1 year - erlang). Rules quite small typo in xapi (https://github.com/xapi-project/xen-api/commit=
/fe664e7f02c28dd1579d9b18ecc685f70f9166d9) commit accepted.


> I want to do something useful for the project and to support it in the=
 future.

> After reviewing a list of ideas, it is not clear what will take preced=
ence.

> What kind of tasks to better navigate?




Hi Sergey! =C2=A0If you've used Xapi before, then a good pl=
ace to start would be the fuzz testing project for Xen. =C2=A0It would invo=
lve building kernels that attempt to stress various components of xcp (e.g.=
 xenstore) and spotting problems and testing expected behaviour (e.g. with =
different SR backends).




best,

Anil



-- 
Best regards,
Sergey Abramyan




--001a1132e232f06f0f04f372678b--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============5218535511469939255==--


From mirageos-devel-bounces@lists.xenproject.org Fri Feb 28 07:30:14 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 28 Feb 2014 07:30:14 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WJHtX-0003MA-Cv; Fri, 28 Feb 2014 07:30:07 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJHtV-0003Ly-9C
	for mirageos-devel@lists.xenproject.org; Fri, 28 Feb 2014 07:30:05 +0000
Received: from [193.109.254.147:40323] by server-13.bemta-14.messagelabs.com
	id 67/42-01226-CFA30135; Fri, 28 Feb 2014 07:30:04 +0000
X-Env-Sender: sa.abramyan@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1393572602!3618995!1
X-Originating-IP: [209.85.216.51]
X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10476 invoked from network); 28 Feb 2014 07:30:03 -0000
Received: from mail-qa0-f51.google.com (HELO mail-qa0-f51.google.com)
	(209.85.216.51)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	28 Feb 2014 07:30:03 -0000
Received: by mail-qa0-f51.google.com with SMTP id j7so307063qaq.24
	for ;
	Thu, 27 Feb 2014 23:30:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=b2yP1yUg11spHnwwOQWJtvNzmhocAB2Ofj3oD+SoTow=;
	b=ma/5x9MnHEbzl4L93BS6TyiAWZxxLge3hOQC1/SK0TbHPkqpM5FpcB6noi/masWeEi
	QrTzUmTzLCYVN4HZc5PKdZJFzfdwykDM6RvglZk15jRsdeFAAh1xj+PAKXbzdWUmqMF2
	qis4uMl+fTsNd+8o3smnROXESvu8huz376M9iXOV5RZtEBnj2T5ryTewG1XiBRA9MnUD
	C7E7S3OThma9L0d5vWzCnjur0dxcdvIVjDdGYyuVcm/EfOEItYxKgtoKsVqHcyak9Scf
	WM/YJTg2iBaarqsv65Jh5JN2TRsUw7grv4xWbrm5jYUN+7VK5rTtho0I6pxB2RyKn0ZK
	69tg==
MIME-Version: 1.0
X-Received: by 10.224.80.134 with SMTP id t6mr1644625qak.34.1393572602472;
	Thu, 27 Feb 2014 23:30:02 -0800 (PST)
Received: by 10.224.102.9 with HTTP; Thu, 27 Feb 2014 23:30:02 -0800 (PST)
In-Reply-To: <14C76B07-6BA2-4FD0-98BE-6F95E6E88A70@recoil.org>
References: 
	<14C76B07-6BA2-4FD0-98BE-6F95E6E88A70@recoil.org>
Date: Fri, 28 Feb 2014 11:30:02 +0400
Message-ID: 
From: Sergey Abramyan 
To: Anil Madhavapeddy 
Cc: mirageos-devel@lists.xenproject.org
Subject: Re: [MirageOS-devel] GSoC 2014
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: multipart/mixed; boundary="===============5218535511469939255=="
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

--===============5218535511469939255==
Content-Type: multipart/alternative; boundary=001a1132e232f06f0f04f372678b

--001a1132e232f06f0f04f372678b
Content-Type: text/plain; charset=UTF-8

Great! There is a test task for this project? After that I could start
working on application.

Thanks.


On Fri, Feb 28, 2014 at 3:46 AM, Anil Madhavapeddy  wrote:

> On 27 Feb 2014, at 12:05, Sergey Abramyan  wrote:
>
> > Hello.
> >
> > My name is Sergey.  I'm from Saint-Petersburg, Russia.
> >
> > I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost
> :), for real projects) and wath this project.
> > I know very little and use ocaml, but developing a 3 years (2 years -
> python and 1 year - erlang). Rules quite small typo in xapi (
> https://github.com/xapi-project/xen-api/commit/fe664e7f02c28dd1579d9b18ecc685f70f9166d9)
> commit accepted.
> > I want to do something useful for the project and to support it in the
> future.
> > After reviewing a list of ideas, it is not clear what will take
> precedence.
> > What kind of tasks to better navigate?
>
> Hi Sergey!  If you've used Xapi before, then a good place to start would
> be the fuzz testing project for Xen.  It would involve building kernels
> that attempt to stress various components of xcp (e.g. xenstore) and
> spotting problems and testing expected behaviour (e.g. with different SR
> backends).
>
> best,
> Anil




-- 
Best regards,
Sergey Abramyan

--001a1132e232f06f0f04f372678b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


Great!=C2=A0There is a test task for this project?=C2=A0After that I=
 could start working on application.



Thanks.



On Fri, Feb 28, 2014 at 3:46 AM, Anil Ma=
dhavapeddy <anil@recoil.org> wrote:


On 27 Feb 2014, at 12:05, Sergey Ab=
ramyan <sa.abramyan@gmail.com> wrote:



> Hello.

>

> My name is Sergey. =C2=A0I'm from Saint-Petersburg, Russia.

>

> I am interested in Xen and MirageOS. I use xcp/xenserver (no localhost=
 :), for real projects) and wath this project.

> I know very little and use ocaml, but developing a 3 years (2 years - =
python and 1 year - erlang). Rules quite small typo in xapi (https://github.com/xapi-project/xen-api/commit=
/fe664e7f02c28dd1579d9b18ecc685f70f9166d9) commit accepted.


> I want to do something useful for the project and to support it in the=
 future.

> After reviewing a list of ideas, it is not clear what will take preced=
ence.

> What kind of tasks to better navigate?




Hi Sergey! =C2=A0If you've used Xapi before, then a good pl=
ace to start would be the fuzz testing project for Xen. =C2=A0It would invo=
lve building kernels that attempt to stress various components of xcp (e.g.=
 xenstore) and spotting problems and testing expected behaviour (e.g. with =
different SR backends).




best,

Anil



-- 
Best regards,
Sergey Abramyan




--001a1132e232f06f0f04f372678b--


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

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

--===============5218535511469939255==--


From mirageos-devel-bounces@lists.xenproject.org Fri Feb 28 17:30:57 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 28 Feb 2014 17:30:57 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WJRGr-0007QY-TB; Fri, 28 Feb 2014 17:30:49 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJRGq-0007QF-7H
	for mirageos-devel@lists.xenproject.org; Fri, 28 Feb 2014 17:30:48 +0000
Received: from [193.109.254.147:32614] by server-15.bemta-14.messagelabs.com
	id 0A/31-10839-7C7C0135; Fri, 28 Feb 2014 17:30:47 +0000
X-Env-Sender: hannes@mehnert.org
X-Msg-Ref: server-7.tower-27.messagelabs.com!1393608646!2273424!1
X-Originating-IP: [213.73.89.199]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23201 invoked from network); 28 Feb 2014 17:30:46 -0000
Received: from mail.h3q.com (HELO mail.h3q.com) (213.73.89.199)
	by server-7.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 28 Feb 2014 17:30:46 -0000
Received: (qmail 96035 invoked from network); 28 Feb 2014 17:30:44 -0000
Received: from mail.h3q.com (HELO mail.h3q.com) (hannes)
	by mail.h3q.com with CAMELLIA256-SHA encrypted SMTP;
	28 Feb 2014 17:30:44 -0000
Message-ID: <5310C7C0.1010105@mehnert.org>
Date: Fri, 28 Feb 2014 17:30:40 +0000
From: Hannes Mehnert 
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: mirageos-devel@lists.xenproject.org
Subject: [MirageOS-devel] TCP client problems
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Dear hackers,

I have a slight problem when trying to open a tcp connection as client
- - the mirage application is at
https://github.com/mirleft/ocaml-tls/tree/master/mirage-client (using
a tap interface on my FreeBSD laptop). The only packet I can see on
tap0 is
17:22:49.859718 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
10.0.0.1 (ff:ff:ff:ff:ff:ff) tell 0.0.0.0, length 28
        0x0000:  0001 0800 0604 0001 c29d 5619 d72c 0000
        0x0010:  0000 ffff ffff ffff 0a00 0001

console output being:
[17:22 hannes@aterscientia:mirage-client] sudo ./mir-mirage-tls-client
assembled CLIENT_HELLO into a buf of size 41

01 00 00 29 03 01 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 02 00 0a 01 00
plugging into tap0 with mac c2:9d:56:19:d7:2c..
Netif: connect tap0
Manager: connect
connecting to host
ARP: transmitting probe -> 10.0.0.1


In contrast, when running a combined client and server (which
initiates a tcp client connection to 10.0.0.1:4433 when a connection
to itself (10.0.0.2:80) was opened) it works fine
[https://github.com/mirleft/ocaml-tls/tree/master/mirage-server-client]:
17:24:54.850357 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.0.0.2
is-at c2:9d:56:19:d7:2c, length 28
        0x0000:  0001 0800 0604 0002 c29d 5619 d72c 0a00
        0x0010:  0002 ffff ffff ffff 0000 0000
17:25:03.772870 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
10.0.0.2 tell 10.0.0.1, length 28
        0x0000:  0001 0800 0604 0001 00bd 4de2 ab00 0a00
        0x0010:  0001 0000 0000 0000 0a00 0002
17:25:03.772995 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.0.0.2
is-at c2:9d:56:19:d7:2c, length 28
        0x0000:  0001 0800 0604 0002 c29d 5619 d72c 0a00
        0x0010:  0002 00bd 4de2 ab00 0a00 0001

(* this is the telnet client to 10.0.0.2 port 80 *)
17:25:03.773014 IP (tos 0x10, ttl 64, id 33970, offset 0, flags [DF],
proto TCP (6), length 60)
    10.0.0.1.54093 > 10.0.0.2.80: Flags [S], cksum 0x9fd0 (correct),
seq 3163617414, win 65535, options [mss 1460,nop,wscale 6,sackOK,TS
val 82118292 ecr 0], length 0
        0x0000:  4510 003c 84b2 4000 4006 a1f7 0a00 0001
        0x0010:  0a00 0002 d34d 0050 bc90 f886 0000 0000
        0x0020:  a002 ffff 9fd0 0000 0204 05b4 0103 0306
        0x0030:  0402 080a 04e5 0694 0000 0000

(* ARP request from mirage *)
17:25:03.773126 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
10.0.0.1 (ff:ff:ff:ff:ff:ff) tell 10.0.0.2, length 28
        0x0000:  0001 0800 0604 0001 c29d 5619 d72c 0a00
        0x0010:  0002 ffff ffff ffff 0a00 0001
17:25:03.773140 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.0.0.1
is-at 00:bd:4d:e2:ab:00, length 28
        0x0000:  0001 0800 0604 0002 00bd 4de2 ab00 0a00
        0x0010:  0001 c29d 5619 d72c 0a00 0002
17:25:03.773254 IP (tos 0x0, ttl 38, id 58875, offset 0, flags [none],
proto TCP (6), length 48)
    10.0.0.2.80 > 10.0.0.1.54093: Flags [S.], cksum 0xb281 (correct),
seq 452860119, ack 3163617415, win 65535, options [mss 1460,wscale
2,eol], length 0
        0x0000:  4500 0030 e5fb 0000 2606 9aca 0a00 0002
        0x0010:  0a00 0001 0050 d34d 1afe 18d7 bc90 f887
        0x0020:  7012 ffff b281 0000 0204 05b4 0303 0200
17:25:03.773308 IP (tos 0x10, ttl 64, id 33971, offset 0, flags [DF],
proto TCP (6), length 40)
    10.0.0.1.54093 > 10.0.0.2.80: Flags [.], cksum 0xdb43 (correct),
seq 1, ack 1, win 1026, length 0
        0x0000:  4510 0028 84b3 4000 4006 a20a 0a00 0001
        0x0010:  0a00 0002 d34d 0050 bc90 f887 1afe 18d8
        0x0020:  5010 0402 db43 0000

(* this is the client connection by mirage to 10.0.0.1:4433 *)
17:25:03.773385 IP (tos 0x0, ttl 38, id 46421, offset 0, flags [none],
proto TCP (6), length 48)
    10.0.0.2.11201 > 10.0.0.1.4433: Flags [S], cksum 0x3f53 (correct),
seq 466468890, win 5840, options [mss 1460,wscale 2,eol], length 0
        0x0000:  4500 0030 b555 0000 2606 cb70 0a00 0002
        0x0010:  0a00 0001 2bc1 1151 1bcd c01a 0000 0000
        0x0020:  7002 16d0 3f53 0000 0204 05b4 0303 0200

console output:
[17:24 hannes@aterscientia:mirage-server-client] sudo
./mir-mirage-tls-server-and-client
assembled CLIENT_HELLO into a buf of size 41

01 00 00 29 03 01 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 02 00 0a 01 00
plugging into tap0 with mac c2:9d:56:19:d7:2c..
Netif: connect tap0
Manager: connect
Manager: configuring
Manager: Interface to 10.0.0.2 nm 255.255.255.0 gw [10.0.0.1]

ARP: sending gratuitous from 10.0.0.2
ARP responding to: who-has 10.0.0.2?
ARP: transmitting probe -> 10.0.0.1
ARP: updating 10.0.0.1 -> 00:bd:4d:e2:ab:00
new tcp connection from 10.0.0.1 54093
HANDLE_RECORD (in state Initial) HANDSHAKE
...

Anything obvious that I'm missing? It seems mirage does not have an
IPv4 address allocated (it's mac address shows up nicely in the first
ARP request, but it's ip is 0?!?).

Any pointers are highly appreciated (fortunately I can for now use the
combined server and client for testing purposes),

Hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBCQAGBQJTEMfAAAoJELyJZYjffCjuPxcP/07LaW3YHHBILzg2LqY5KmNp
rZSHHkQMJ3vrU7b25mXTSyR8zdQmDCJSZ6NgkGJbVBl9ocWx+ht1TDtvUL75yVSk
Sc5r7iRK+K5FMEeMm5Z1ZB1apxGRBZMgefxvK4IPdg08bO7r39DUuFcJaQW8YBhV
K32FAxhOMKe2lwFWXhxKsuRD2j8lnSN1Fd3cFJ4W/mg7dyFW578uGTa9TWm3t6jt
TKHYJujDZxmgXX1UEYZHJXZchm8bvh4m01UVrcrjfz3OPysAnkcEoTnOWph227ii
tnEOicBtza05B4Ao3OUxqlj52O+dYgJ1rA1PwhdwcWw7ZrK311xflNlRmtOdIbc3
AoomkLcy2syiAtNJORpgnEyQoT2EvmDsJ7EY3PP+CxxwTSGLgo4vAA9Ww/SqWgoa
NdUSvBXNVa6kbvl1XrscaeIGP4qRfn8kcIye1E4YYIpsCbFnZJGWMIgcNM7jIvF1
sqDH+jYgGsygqCejWEnJPy/7MA8dYs4Sj2nPHuERvwyYFGH2JjV1UJTeH2t78Eq3
xwFuK89Prtz08KHV2YCELfFrKX9imsamnjHasLtVA+L/XJ3WOv6rDHEKgzaXfJYk
cK5QztZM2OChisiF7XmR633afbfLUy8zjosrXyYg33GR3x/hpIJzLB31396FlNyC
PkLkfuz8eA/eZHtGlmnX
=bn23
-----END PGP SIGNATURE-----

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel

From mirageos-devel-bounces@lists.xenproject.org Fri Feb 28 17:30:57 2014
Return-path: 
Envelope-to: archives@lists.xenproject.org
Delivery-date: Fri, 28 Feb 2014 17:30:57 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from )
	id 1WJRGr-0007QY-TB; Fri, 28 Feb 2014 17:30:49 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from ) id 1WJRGq-0007QF-7H
	for mirageos-devel@lists.xenproject.org; Fri, 28 Feb 2014 17:30:48 +0000
Received: from [193.109.254.147:32614] by server-15.bemta-14.messagelabs.com
	id 0A/31-10839-7C7C0135; Fri, 28 Feb 2014 17:30:47 +0000
X-Env-Sender: hannes@mehnert.org
X-Msg-Ref: server-7.tower-27.messagelabs.com!1393608646!2273424!1
X-Originating-IP: [213.73.89.199]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23201 invoked from network); 28 Feb 2014 17:30:46 -0000
Received: from mail.h3q.com (HELO mail.h3q.com) (213.73.89.199)
	by server-7.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 28 Feb 2014 17:30:46 -0000
Received: (qmail 96035 invoked from network); 28 Feb 2014 17:30:44 -0000
Received: from mail.h3q.com (HELO mail.h3q.com) (hannes)
	by mail.h3q.com with CAMELLIA256-SHA encrypted SMTP;
	28 Feb 2014 17:30:44 -0000
Message-ID: <5310C7C0.1010105@mehnert.org>
Date: Fri, 28 Feb 2014 17:30:40 +0000
From: Hannes Mehnert 
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: mirageos-devel@lists.xenproject.org
Subject: [MirageOS-devel] TCP client problems
X-BeenThere: mirageos-devel@lists.xenproject.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Developer list for MirageOS 
List-Unsubscribe: ,
	
List-Post: 
List-Help: 
List-Subscribe: ,
	
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mirageos-devel-bounces@lists.xenproject.org
Errors-To: mirageos-devel-bounces@lists.xenproject.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Dear hackers,

I have a slight problem when trying to open a tcp connection as client
- - the mirage application is at
https://github.com/mirleft/ocaml-tls/tree/master/mirage-client (using
a tap interface on my FreeBSD laptop). The only packet I can see on
tap0 is
17:22:49.859718 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
10.0.0.1 (ff:ff:ff:ff:ff:ff) tell 0.0.0.0, length 28
        0x0000:  0001 0800 0604 0001 c29d 5619 d72c 0000
        0x0010:  0000 ffff ffff ffff 0a00 0001

console output being:
[17:22 hannes@aterscientia:mirage-client] sudo ./mir-mirage-tls-client
assembled CLIENT_HELLO into a buf of size 41

01 00 00 29 03 01 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 02 00 0a 01 00
plugging into tap0 with mac c2:9d:56:19:d7:2c..
Netif: connect tap0
Manager: connect
connecting to host
ARP: transmitting probe -> 10.0.0.1


In contrast, when running a combined client and server (which
initiates a tcp client connection to 10.0.0.1:4433 when a connection
to itself (10.0.0.2:80) was opened) it works fine
[https://github.com/mirleft/ocaml-tls/tree/master/mirage-server-client]:
17:24:54.850357 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.0.0.2
is-at c2:9d:56:19:d7:2c, length 28
        0x0000:  0001 0800 0604 0002 c29d 5619 d72c 0a00
        0x0010:  0002 ffff ffff ffff 0000 0000
17:25:03.772870 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
10.0.0.2 tell 10.0.0.1, length 28
        0x0000:  0001 0800 0604 0001 00bd 4de2 ab00 0a00
        0x0010:  0001 0000 0000 0000 0a00 0002
17:25:03.772995 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.0.0.2
is-at c2:9d:56:19:d7:2c, length 28
        0x0000:  0001 0800 0604 0002 c29d 5619 d72c 0a00
        0x0010:  0002 00bd 4de2 ab00 0a00 0001

(* this is the telnet client to 10.0.0.2 port 80 *)
17:25:03.773014 IP (tos 0x10, ttl 64, id 33970, offset 0, flags [DF],
proto TCP (6), length 60)
    10.0.0.1.54093 > 10.0.0.2.80: Flags [S], cksum 0x9fd0 (correct),
seq 3163617414, win 65535, options [mss 1460,nop,wscale 6,sackOK,TS
val 82118292 ecr 0], length 0
        0x0000:  4510 003c 84b2 4000 4006 a1f7 0a00 0001
        0x0010:  0a00 0002 d34d 0050 bc90 f886 0000 0000
        0x0020:  a002 ffff 9fd0 0000 0204 05b4 0103 0306
        0x0030:  0402 080a 04e5 0694 0000 0000

(* ARP request from mirage *)
17:25:03.773126 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
10.0.0.1 (ff:ff:ff:ff:ff:ff) tell 10.0.0.2, length 28
        0x0000:  0001 0800 0604 0001 c29d 5619 d72c 0a00
        0x0010:  0002 ffff ffff ffff 0a00 0001
17:25:03.773140 ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.0.0.1
is-at 00:bd:4d:e2:ab:00, length 28
        0x0000:  0001 0800 0604 0002 00bd 4de2 ab00 0a00
        0x0010:  0001 c29d 5619 d72c 0a00 0002
17:25:03.773254 IP (tos 0x0, ttl 38, id 58875, offset 0, flags [none],
proto TCP (6), length 48)
    10.0.0.2.80 > 10.0.0.1.54093: Flags [S.], cksum 0xb281 (correct),
seq 452860119, ack 3163617415, win 65535, options [mss 1460,wscale
2,eol], length 0
        0x0000:  4500 0030 e5fb 0000 2606 9aca 0a00 0002
        0x0010:  0a00 0001 0050 d34d 1afe 18d7 bc90 f887
        0x0020:  7012 ffff b281 0000 0204 05b4 0303 0200
17:25:03.773308 IP (tos 0x10, ttl 64, id 33971, offset 0, flags [DF],
proto TCP (6), length 40)
    10.0.0.1.54093 > 10.0.0.2.80: Flags [.], cksum 0xdb43 (correct),
seq 1, ack 1, win 1026, length 0
        0x0000:  4510 0028 84b3 4000 4006 a20a 0a00 0001
        0x0010:  0a00 0002 d34d 0050 bc90 f887 1afe 18d8
        0x0020:  5010 0402 db43 0000

(* this is the client connection by mirage to 10.0.0.1:4433 *)
17:25:03.773385 IP (tos 0x0, ttl 38, id 46421, offset 0, flags [none],
proto TCP (6), length 48)
    10.0.0.2.11201 > 10.0.0.1.4433: Flags [S], cksum 0x3f53 (correct),
seq 466468890, win 5840, options [mss 1460,wscale 2,eol], length 0
        0x0000:  4500 0030 b555 0000 2606 cb70 0a00 0002
        0x0010:  0a00 0001 2bc1 1151 1bcd c01a 0000 0000
        0x0020:  7002 16d0 3f53 0000 0204 05b4 0303 0200

console output:
[17:24 hannes@aterscientia:mirage-server-client] sudo
./mir-mirage-tls-server-and-client
assembled CLIENT_HELLO into a buf of size 41

01 00 00 29 03 01 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 02 00 0a 01 00
plugging into tap0 with mac c2:9d:56:19:d7:2c..
Netif: connect tap0
Manager: connect
Manager: configuring
Manager: Interface to 10.0.0.2 nm 255.255.255.0 gw [10.0.0.1]

ARP: sending gratuitous from 10.0.0.2
ARP responding to: who-has 10.0.0.2?
ARP: transmitting probe -> 10.0.0.1
ARP: updating 10.0.0.1 -> 00:bd:4d:e2:ab:00
new tcp connection from 10.0.0.1 54093
HANDLE_RECORD (in state Initial) HANDSHAKE
...

Anything obvious that I'm missing? It seems mirage does not have an
IPv4 address allocated (it's mac address shows up nicely in the first
ARP request, but it's ip is 0?!?).

Any pointers are highly appreciated (fortunately I can for now use the
combined server and client for testing purposes),

Hannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQIcBAEBCQAGBQJTEMfAAAoJELyJZYjffCjuPxcP/07LaW3YHHBILzg2LqY5KmNp
rZSHHkQMJ3vrU7b25mXTSyR8zdQmDCJSZ6NgkGJbVBl9ocWx+ht1TDtvUL75yVSk
Sc5r7iRK+K5FMEeMm5Z1ZB1apxGRBZMgefxvK4IPdg08bO7r39DUuFcJaQW8YBhV
K32FAxhOMKe2lwFWXhxKsuRD2j8lnSN1Fd3cFJ4W/mg7dyFW578uGTa9TWm3t6jt
TKHYJujDZxmgXX1UEYZHJXZchm8bvh4m01UVrcrjfz3OPysAnkcEoTnOWph227ii
tnEOicBtza05B4Ao3OUxqlj52O+dYgJ1rA1PwhdwcWw7ZrK311xflNlRmtOdIbc3
AoomkLcy2syiAtNJORpgnEyQoT2EvmDsJ7EY3PP+CxxwTSGLgo4vAA9Ww/SqWgoa
NdUSvBXNVa6kbvl1XrscaeIGP4qRfn8kcIye1E4YYIpsCbFnZJGWMIgcNM7jIvF1
sqDH+jYgGsygqCejWEnJPy/7MA8dYs4Sj2nPHuERvwyYFGH2JjV1UJTeH2t78Eq3
xwFuK89Prtz08KHV2YCELfFrKX9imsamnjHasLtVA+L/XJ3WOv6rDHEKgzaXfJYk
cK5QztZM2OChisiF7XmR633afbfLUy8zjosrXyYg33GR3x/hpIJzLB31396FlNyC
PkLkfuz8eA/eZHtGlmnX
=bn23
-----END PGP SIGNATURE-----

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel