From mirageos-devel-bounces@lists.xenproject.org Wed Jan 01 11:48:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Jan 2014 11:48: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 1VyKHv-00073I-CJ; Wed, 01 Jan 2014 11:48:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyKHu-00073D-HQ for mirageos-devel@lists.xenproject.org; Wed, 01 Jan 2014 11:48:38 +0000 Received: from [85.158.143.35:15414] by server-1.bemta-4.messagelabs.com id D2/60-02132-59004C25; Wed, 01 Jan 2014 11:48:37 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-21.messagelabs.com!1388576916!9040647!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 21568 invoked from network); 1 Jan 2014 11:48:36 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-21.messagelabs.com with SMTP; 1 Jan 2014 11:48:36 -0000 Received: (qmail 5241 invoked by uid 634); 1 Jan 2014 11:48:36 -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; Wed, 01 Jan 2014 11:48:36 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 1 Jan 2014 11:48:34 +0000 Message-Id: References: To: hugo 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] porting ocsigenserver 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 30 Dec 2013, at 19:28, hugo wrote: > I would like to experiment with mirage and try to port ocsigen/eliom project. > Are there any ongoing work in that direction ? > Any advice ? > What's the status of (native) dynlink ? Hi Hugo, Porting Ocsigen and Eliom would be great, but it does require rethinking how you handle configuration. In Mirage, all the major dependencies are functorized across the module signatures in: https://github.com/mirage/mirage-types The V1 module contains the 1.0 versions, and Thomas' pull request shows the improved ones in V2. At build time, the `mirage` command line tool parses a configuration file to determine the concrete module implementations to satisfy a job. So to start porting Ocsigen and Eliom, it would be best to understand how to break it up and interface with these libraries. Would it be difficult to swap out the HTTP handler in Ocsigen with Cohttp and run that under Unix? Eliom might be slightly problematic due to a clash between type_conv and deriving-ocsigen. -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 Jan 01 11:48:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Jan 2014 11:48: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 1VyKHv-00073I-CJ; Wed, 01 Jan 2014 11:48:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VyKHu-00073D-HQ for mirageos-devel@lists.xenproject.org; Wed, 01 Jan 2014 11:48:38 +0000 Received: from [85.158.143.35:15414] by server-1.bemta-4.messagelabs.com id D2/60-02132-59004C25; Wed, 01 Jan 2014 11:48:37 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-21.messagelabs.com!1388576916!9040647!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 21568 invoked from network); 1 Jan 2014 11:48:36 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-21.messagelabs.com with SMTP; 1 Jan 2014 11:48:36 -0000 Received: (qmail 5241 invoked by uid 634); 1 Jan 2014 11:48:36 -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; Wed, 01 Jan 2014 11:48:36 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 1 Jan 2014 11:48:34 +0000 Message-Id: References: To: hugo 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] porting ocsigenserver 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 30 Dec 2013, at 19:28, hugo wrote: > I would like to experiment with mirage and try to port ocsigen/eliom project. > Are there any ongoing work in that direction ? > Any advice ? > What's the status of (native) dynlink ? Hi Hugo, Porting Ocsigen and Eliom would be great, but it does require rethinking how you handle configuration. In Mirage, all the major dependencies are functorized across the module signatures in: https://github.com/mirage/mirage-types The V1 module contains the 1.0 versions, and Thomas' pull request shows the improved ones in V2. At build time, the `mirage` command line tool parses a configuration file to determine the concrete module implementations to satisfy a job. So to start porting Ocsigen and Eliom, it would be best to understand how to break it up and interface with these libraries. Would it be difficult to swap out the HTTP handler in Ocsigen with Cohttp and run that under Unix? Eliom might be slightly problematic due to a clash between type_conv and deriving-ocsigen. -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 Jan 03 16:50:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Jan 2014 16:50: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 1Vz7xT-000097-BF; Fri, 03 Jan 2014 16:50:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vz7xS-000090-A9 for mirageos-devel@lists.xenproject.org; Fri, 03 Jan 2014 16:50:50 +0000 Received: from [193.109.254.147:17358] by server-4.bemta-14.messagelabs.com id 9C/05-03916-96AE6C25; Fri, 03 Jan 2014 16:50:49 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-27.messagelabs.com!1388767848!8702478!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 19005 invoked from network); 3 Jan 2014 16:50:48 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-27.messagelabs.com with SMTP; 3 Jan 2014 16:50:48 -0000 Received: (qmail 32548 invoked by uid 634); 3 Jan 2014 16:50:47 -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; Fri, 03 Jan 2014 16:50:47 +0000 From: Anil Madhavapeddy Message-Id: Date: Fri, 3 Jan 2014 16:50:46 +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] decks.openmirage.org ported 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 http://decks.openmirage.org is now running on Mirage 1.0 too, and the Zurb libraries are slowly coming together (Cowabloga is still very rough and ready, but at least we have >1 site using it now). Thanks Mort for the blog post: http://openmirage.org/blog/decks-n-drums Word of warning: the decks website comes out to about 50MB for each build (due to the crunched filesystem), so it'll likely be the first one to use the block device + buffer cache from Thomas' combinator branch. I'll do a roundup blog post of the latest wiki updates that everyone has submitted recently. -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 Jan 03 16:50:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Jan 2014 16:50: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 1Vz7xT-000097-BF; Fri, 03 Jan 2014 16:50:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vz7xS-000090-A9 for mirageos-devel@lists.xenproject.org; Fri, 03 Jan 2014 16:50:50 +0000 Received: from [193.109.254.147:17358] by server-4.bemta-14.messagelabs.com id 9C/05-03916-96AE6C25; Fri, 03 Jan 2014 16:50:49 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-27.messagelabs.com!1388767848!8702478!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 19005 invoked from network); 3 Jan 2014 16:50:48 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-27.messagelabs.com with SMTP; 3 Jan 2014 16:50:48 -0000 Received: (qmail 32548 invoked by uid 634); 3 Jan 2014 16:50:47 -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; Fri, 03 Jan 2014 16:50:47 +0000 From: Anil Madhavapeddy Message-Id: Date: Fri, 3 Jan 2014 16:50:46 +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] decks.openmirage.org ported 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 http://decks.openmirage.org is now running on Mirage 1.0 too, and the Zurb libraries are slowly coming together (Cowabloga is still very rough and ready, but at least we have >1 site using it now). Thanks Mort for the blog post: http://openmirage.org/blog/decks-n-drums Word of warning: the decks website comes out to about 50MB for each build (due to the crunched filesystem), so it'll likely be the first one to use the block device + buffer cache from Thomas' combinator branch. I'll do a roundup blog post of the latest wiki updates that everyone has submitted recently. -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 Jan 05 13:43:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 05 Jan 2014 13:43:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VznzL-0006Gv-NJ; Sun, 05 Jan 2014 13:43:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VznzK-0006Gq-02 for mirageos-devel@lists.xenproject.org; Sun, 05 Jan 2014 13:43:34 +0000 Received: from [85.158.139.211:32834] by server-6.bemta-5.messagelabs.com id 9F/46-16310-58169C25; Sun, 05 Jan 2014 13:43:33 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1388929412!7716495!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 22974 invoked from network); 5 Jan 2014 13:43:32 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 5 Jan 2014 13:43:32 -0000 Received: (qmail 15672 invoked by uid 10000); 5 Jan 2014 13:43:31 -0000 Date: Sun, 5 Jan 2014 13:43:31 +0000 From: Anil Madhavapeddy To: Christopher Greenhalgh Message-ID: <20140105134331.GF12036@dark.recoil.org> References: <87A0C928-9B3F-46DB-A2EF-188FFEBB424F@eu.citrix.com> <1057E5A7-1A94-4541-979A-1821CFF65AD1@recoil.org> <4C20415C7327A849961F3B8421413725010CD5506A81@EXCHANGE1.ad.nottingham.ac.uk> <8972A91E-F38D-4D98-B100-BAE25D17F987@recoil.org> <4C20415C7327A849961F3B8421413725010CD5506A95@EXCHANGE1.ad.nottingham.ac.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4C20415C7327A849961F3B8421413725010CD5506A95@EXCHANGE1.ad.nottingham.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] mirage, opam and cross-compiling... ? 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 Chris, Now that the release is out, I've created a tracker issue for the cross compilation question, as our next major backend target is Xen/ARM: https://github.com/mirage/mirage/issues/182 -anil On Thu, Sep 19, 2013 at 09:55:55AM +0100, Christopher Greenhalgh wrote: > On 18 September 2013 16:58 Anil Madhavapeddy wrote: > > >- there's no standard for specifying an equivalent to CFLAGS/CC in > >OCaml build systems -- everyone defines their own. > > I did some thinking about (something that turned out to be equivalent > to) this and I came up with what - to me - seems like a sensible scheme; > for posterity I've noted it here: > https://github.com/cgreenhalgh/ocaml-crosscompiling/blob/master/docs/toolchainproposal.md > but probably it should be fed somewhere else as it would involve a new > flag in all the ocaml commands... > > >- the annoying ones are usually syntax extensions, which need to be > >built as host libraries and not target libraries. We have a way to > >sidestep this as of a few weeks ago. Leo White has built a specialized > >compiler driver that bypasses the usual compiler parse tree, and > >instead statically links in some camlp4 extensions. This is not only > >faster, but it avoids dynamic linking in the compiler completely! Most > >of our syntax extension requirements are actually pretty minimal (the > >Lwt one, and perhaps Sexplib and Cow), so we could just link those into > >one mega-compiler-driver that works on all the source code that we care > >about. > > With and ocaml-android cross-compiler this seems to have 'just worked' > so far, presumably because it is using the syntax extensions as bytecode > only and they have no dependencies on native libraries. (I haven't dug > enough to see exactly what is going on yet). Potentially fragile, > though... > > p.s. I've left a link but moved my notes to a new git repo, > https://github.com/cgreenhalgh/ocaml-crosscompiling ) > > Cheers Chris _______________________________________________ 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 Jan 05 13:43:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 05 Jan 2014 13:43:40 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VznzL-0006Gv-NJ; Sun, 05 Jan 2014 13:43:35 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VznzK-0006Gq-02 for mirageos-devel@lists.xenproject.org; Sun, 05 Jan 2014 13:43:34 +0000 Received: from [85.158.139.211:32834] by server-6.bemta-5.messagelabs.com id 9F/46-16310-58169C25; Sun, 05 Jan 2014 13:43:33 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1388929412!7716495!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 22974 invoked from network); 5 Jan 2014 13:43:32 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 5 Jan 2014 13:43:32 -0000 Received: (qmail 15672 invoked by uid 10000); 5 Jan 2014 13:43:31 -0000 Date: Sun, 5 Jan 2014 13:43:31 +0000 From: Anil Madhavapeddy To: Christopher Greenhalgh Message-ID: <20140105134331.GF12036@dark.recoil.org> References: <87A0C928-9B3F-46DB-A2EF-188FFEBB424F@eu.citrix.com> <1057E5A7-1A94-4541-979A-1821CFF65AD1@recoil.org> <4C20415C7327A849961F3B8421413725010CD5506A81@EXCHANGE1.ad.nottingham.ac.uk> <8972A91E-F38D-4D98-B100-BAE25D17F987@recoil.org> <4C20415C7327A849961F3B8421413725010CD5506A95@EXCHANGE1.ad.nottingham.ac.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4C20415C7327A849961F3B8421413725010CD5506A95@EXCHANGE1.ad.nottingham.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] mirage, opam and cross-compiling... ? 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 Chris, Now that the release is out, I've created a tracker issue for the cross compilation question, as our next major backend target is Xen/ARM: https://github.com/mirage/mirage/issues/182 -anil On Thu, Sep 19, 2013 at 09:55:55AM +0100, Christopher Greenhalgh wrote: > On 18 September 2013 16:58 Anil Madhavapeddy wrote: > > >- there's no standard for specifying an equivalent to CFLAGS/CC in > >OCaml build systems -- everyone defines their own. > > I did some thinking about (something that turned out to be equivalent > to) this and I came up with what - to me - seems like a sensible scheme; > for posterity I've noted it here: > https://github.com/cgreenhalgh/ocaml-crosscompiling/blob/master/docs/toolchainproposal.md > but probably it should be fed somewhere else as it would involve a new > flag in all the ocaml commands... > > >- the annoying ones are usually syntax extensions, which need to be > >built as host libraries and not target libraries. We have a way to > >sidestep this as of a few weeks ago. Leo White has built a specialized > >compiler driver that bypasses the usual compiler parse tree, and > >instead statically links in some camlp4 extensions. This is not only > >faster, but it avoids dynamic linking in the compiler completely! Most > >of our syntax extension requirements are actually pretty minimal (the > >Lwt one, and perhaps Sexplib and Cow), so we could just link those into > >one mega-compiler-driver that works on all the source code that we care > >about. > > With and ocaml-android cross-compiler this seems to have 'just worked' > so far, presumably because it is using the syntax extensions as bytecode > only and they have no dependencies on native libraries. (I haven't dug > enough to see exactly what is going on yet). Potentially fragile, > though... > > p.s. I've left a link but moved my notes to a new git repo, > https://github.com/cgreenhalgh/ocaml-crosscompiling ) > > Cheers Chris _______________________________________________ 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 Jan 05 14:03:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 05 Jan 2014 14:03:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VzoIJ-00071i-IB; Sun, 05 Jan 2014 14:03:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VzoII-00071d-9q for mirageos-devel@lists.xenproject.org; Sun, 05 Jan 2014 14:03:10 +0000 Received: from [85.158.137.68:30463] by server-12.bemta-3.messagelabs.com id 5B/C8-20055-D1669C25; Sun, 05 Jan 2014 14:03:09 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-13.tower-31.messagelabs.com!1388930588!7337705!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23307 invoked from network); 5 Jan 2014 14:03:08 -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; 5 Jan 2014 14:03:08 -0000 Received: (qmail 9015 invoked by uid 10000); 5 Jan 2014 14:03:07 -0000 Date: Sun, 5 Jan 2014 14:03:07 +0000 From: Anil Madhavapeddy To: William Le Ferrand Message-ID: <20140105140307.GK12036@dark.recoil.org> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Balraj Singh , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] cohttp_lwt_mirage.ml / client 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 The HTTP client is still stubbed out (mainly because it wasn't a lot of use to have without SSL support, which is being worked on slowly). We've split out the HTTP library into https://github.com/mirage/mirage-http-xen and I've created https://github.com/mirage/mirage/issues/184 to track the implementation. -anil On Thu, Oct 10, 2013 at 05:34:34PM -0700, William Le Ferrand wrote: > Hi Balraj, hi Anil, what is the status of cohttp/client on mirage? (I'll be > happy to write it if mirage has the required primitives) > > thanks > > william > > On Wed, Sep 18, 2013 at 4:56 PM, Anil Madhavapeddy wrote: > > > I didn't fill it out as I was waiting for Balraj's TCP connect state > > machine to be tested (we were mainly just testing servers before). Balraj: > > is that in trunk in mirage-net now? > > > > -anil > > > > On 19 Sep 2013, at 00:54, William Le Ferrand wrote: > > > > > Hello everyone > > > > > > Is there a version of Cohttp_lwt_mirage.Client that works somewhere? Is > > there any special difficulties with it? The one on github has fail "no > > implemented" here and there. > > > > > > Thanks! > > > > > > William > > > > > > -- > > > William Le Ferrand > > > > > > Mobile : (+1) (415) 683-1484 > > > Web : http://williamleferrand.github.com/ > > > > > > > > > > -- > William Le Ferrand > > Mobile : (+1) (415) 683-1484 > Web : http://williamleferrand.github.com/ > -- Anil Madhavapeddy http://anil.recoil.org _______________________________________________ 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 Jan 05 14:03:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 05 Jan 2014 14:03:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VzoIJ-00071i-IB; Sun, 05 Jan 2014 14:03:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VzoII-00071d-9q for mirageos-devel@lists.xenproject.org; Sun, 05 Jan 2014 14:03:10 +0000 Received: from [85.158.137.68:30463] by server-12.bemta-3.messagelabs.com id 5B/C8-20055-D1669C25; Sun, 05 Jan 2014 14:03:09 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-13.tower-31.messagelabs.com!1388930588!7337705!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23307 invoked from network); 5 Jan 2014 14:03:08 -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; 5 Jan 2014 14:03:08 -0000 Received: (qmail 9015 invoked by uid 10000); 5 Jan 2014 14:03:07 -0000 Date: Sun, 5 Jan 2014 14:03:07 +0000 From: Anil Madhavapeddy To: William Le Ferrand Message-ID: <20140105140307.GK12036@dark.recoil.org> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Balraj Singh , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] cohttp_lwt_mirage.ml / client 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 The HTTP client is still stubbed out (mainly because it wasn't a lot of use to have without SSL support, which is being worked on slowly). We've split out the HTTP library into https://github.com/mirage/mirage-http-xen and I've created https://github.com/mirage/mirage/issues/184 to track the implementation. -anil On Thu, Oct 10, 2013 at 05:34:34PM -0700, William Le Ferrand wrote: > Hi Balraj, hi Anil, what is the status of cohttp/client on mirage? (I'll be > happy to write it if mirage has the required primitives) > > thanks > > william > > On Wed, Sep 18, 2013 at 4:56 PM, Anil Madhavapeddy wrote: > > > I didn't fill it out as I was waiting for Balraj's TCP connect state > > machine to be tested (we were mainly just testing servers before). Balraj: > > is that in trunk in mirage-net now? > > > > -anil > > > > On 19 Sep 2013, at 00:54, William Le Ferrand wrote: > > > > > Hello everyone > > > > > > Is there a version of Cohttp_lwt_mirage.Client that works somewhere? Is > > there any special difficulties with it? The one on github has fail "no > > implemented" here and there. > > > > > > Thanks! > > > > > > William > > > > > > -- > > > William Le Ferrand > > > > > > Mobile : (+1) (415) 683-1484 > > > Web : http://williamleferrand.github.com/ > > > > > > > > > > -- > William Le Ferrand > > Mobile : (+1) (415) 683-1484 > Web : http://williamleferrand.github.com/ > -- Anil Madhavapeddy http://anil.recoil.org _______________________________________________ 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 Jan 05 14:15:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 05 Jan 2014 14:15: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 1VzoUA-0007Oz-VR; Sun, 05 Jan 2014 14:15:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VzoU9-0007Ou-CA for mirageos-devel@lists.xenproject.org; Sun, 05 Jan 2014 14:15:25 +0000 Received: from [85.158.137.68:19952] by server-16.bemta-3.messagelabs.com id 32/24-26128-CF869C25; Sun, 05 Jan 2014 14:15:24 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-10.tower-31.messagelabs.com!1388931322!6149425!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 2535 invoked from network); 5 Jan 2014 14:15:23 -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; 5 Jan 2014 14:15:23 -0000 Received: (qmail 23695 invoked by uid 10000); 5 Jan 2014 14:15:22 -0000 Date: Sun, 5 Jan 2014 14:15:22 +0000 From: Anil Madhavapeddy To: Christopher Greenhalgh Message-ID: <20140105141522.GO12036@dark.recoil.org> References: <4C20415C7327A849961F3B8421413725010CD72B64D9@EXCHANGE1.ad.nottingham.ac.uk> <2A9BC77A-0999-4C6E-AC17-C35983A7A6E3@nottingham.ac.uk> <4C20415C7327A849961F3B8421413725010CD72B64DC@EXCHANGE1.ad.nottingham.ac.uk> <4C20415C7327A849961F3B8421413725010CD7203AAC@EXCHANGE1.ad.nottingham.ac.uk> <4C20415C7327A849961F3B8421413725010CD7203BB2@EXCHANGE1.ad.nottingham.ac.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4C20415C7327A849961F3B8421413725010CD7203BB2@EXCHANGE1.ad.nottingham.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Mirage List Subject: Re: [MirageOS-devel] mutable store on 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 I've taken a look at Baardskeerder, and it looks extremely good for a Xen port indeed (and possibly as an Irminsule backend for the blob store, Thomas). Issue: https://github.com/mirage/mirage/issues/185 I'd suggest using it more for logging and the like, but the only hitch is that it doesn't compile under non-Linux yet due to depending on some non-Posix ioctls, but that should be fairly easy to patch with a portable but less durable equivalent. -anil On Fri, Nov 01, 2013 at 10:50:59AM +0000, Christopher Greenhalgh wrote: > As I said in the call, I've got baardskeerder running in Xen/mirage over blkif. > https://github.com/cgreenhalgh/baardskeerder/ > https://github.com/cgreenhalgh/baardskeerder/blob/master/xen_test/README.md > I've run the bsmgr benchmark(s) to run on it, but my dev set-up is in a virtual box vm and I was using xen blktap for the vdisk > https://github.com/cgreenhalgh/baardskeerder/blob/master/benchmark-out.txt > I added page cacheing to the baardskeerder store over blkif but performance is still ~10 slower then direct lwt on unix, and my xen setup is currently about twice as slow again (hopefully down to the blktap disk - I couldn't get xen-disk to compile and I haven't got lvm set up at the mo). > > Anyway, I'll leave the performance alone for now and try building a web app with it and cohttp/etc > > Cheers > Chris > > > > From: cl-mirage-bounces@lists.cam.ac.uk [mailto:cl-mirage-bounces@lists.cam.ac.uk] On Behalf Of Christopher Greenhalgh > Sent: 23 October 2013 16:42 > To: David Scott > Cc: Mirage List > Subject: RE: mutable store on mirage? > > I don't feel like I know enough about block device internals to suggest an alternative yet. > > I've now made a first-cut port of baardskeerder to mirage (splitting out mirage & unix dependencies into sub-packages): > https://github.com/cgreenhalgh/baardskeerder > This has a store that runs over blkif, but currently only the basic baardskeerder Flog0 log option (which has little resilience and no compaction). The store also does no cacheing at the moment... (needs mirage 0.9.8, i.e. io_page fix) > > I've make a very simple mirage btree fa?ade over this: > https://github.com/cgreenhalgh/ocaml-btree > This is passing basic tests on unix, but I haven't got a test harness together yet to try it on Xen. > > The Opam packages are in: > https://github.com/cgreenhalgh/opam-dev-repository > unix-simple-blkdev > mirage-baardskeerder > ocaml-btree > > cheers > Chris > > > From: cl-mirage-bounces@lists.cam.ac.uk [mailto:cl-mirage-bounces@lists.cam.ac.uk] On Behalf Of David Scott > Sent: 21 October 2013 21:16 > To: Christopher Greenhalgh > Cc: Mirage List > Subject: Re: mutable store on mirage? > > Hi Chris, > > Thanks for taking a look at this. When I get a moment I'll check out your code and see if it makes sense to merge in some patches I've got lying around. > > The Blkif API is very quirky. I think we should chuck it away and put something sensible in place. Feel free to propose a new signature! :-) > > Cheers, > Dave > > On Mon, Oct 21, 2013 at 8:57 PM, Christopher Greenhalgh > wrote: > Partly as a learning exercise I have made a blkif implementation over a single file using Lwt_unix - https://github.com/cgreenhalgh/mirage-unix-simple-blkif > It has a couple of basic tests which it passes, but hasn't been exercised beyond that yet; > Neither is it abstracted over threading, but then the Blkif interface isn't yet either... > i intend to try using it as a baardskeerder store next, so we'll see what happens. > > Threw up a few questions... > > As noted in the comment near the top of https://github.com/cgreenhalgh/mirage-unix-simple-blkif/blob/master/lib/blkdev.ml i don't think it will behave precisely the same as ocaml-xen-block-driver for concurrent multi-block reads and writes: currently it will do each in one chunk while the xen driver subdivides and potentially interleaves large reads and... > > Btw there seems to be an ambiguity in the OS.Devices.Blkif interface, specifically what should happen if write_page is called with an Io_page which is actually >1 page long (e.g.from Io_page.get N)? ocaml-xen-block-driver write_page seems to assume that it will be exactly one page (without checking) but is the intended bevaviour (a) split pages and handle each page in turn or (b) explicit error? > > It is also slightly unclear (to me) what the ordering semantics are intended to be for read_512; currently this and the xen-block-driver only actually initiate the read when a thread attempts a (blocking) get on the returned Lwt_sequence. This is the more obvious route as read_512 is non-blocking (i.e. has to immediately return the sequence), but feels slightly odd. > > p.s. as there is no sync operation, is there a particular level of sync to disk/durability defined in the xen block protocol? > > I'm also unsure if it is deliberate that Io_page.page_size isn't visible; i had to use Io_page.round_to_page_size 1 to get page_size out... > > cheers > chris > > > _________________________ > From: Richard Mortier [Richard.Mortier@nottingham.ac.uk] > Sent: 16 October 2013 21:16 > To: David Scott > Cc: Christopher Greenhalgh; Mirage List > Subject: Re: mutable store on mirage? > > On 16 Oct 2013, at 21:08, David Scott wrote: > > > I'd like to see unix blkif implemented (without using the xen implementation). I've got some patches lying around which open files with O_DIRECT and perform unbuffered sector-aligned I/O. I was thinking of making a 'unix-block-driver' with this code in it, mirroring the xen implementation. It's mostly a thin veneer over Lwt_bytes, replacing Bigarray.t with Cstruct.t. In future I was thinking the mirage-platform repo could become the minimal 'boot' code plus module types for Blkif, Netif etc; and all the concrete implementations could be spun out into other repos. > > > > What do people think? > > absolutely agree. thought perhaps we would want to functorise(*) over Lwt, eg packages named > > mirage-blk-xen-lwt > mirage-blk-posix-async > mirage-blk-bsd-blah > > etc...? opam can handle the constraints though (i firmly expect :) > > (*) if i'm making up a verb there and/or using it incorrectly, i apologise... :) > > > -- > 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. > > > > > > > -- > Dave Scott > > > 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. > > > 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. > > > > > > > > > -- Anil Madhavapeddy http://anil.recoil.org _______________________________________________ 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 Jan 05 14:15:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 05 Jan 2014 14:15: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 1VzoUA-0007Oz-VR; Sun, 05 Jan 2014 14:15:26 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VzoU9-0007Ou-CA for mirageos-devel@lists.xenproject.org; Sun, 05 Jan 2014 14:15:25 +0000 Received: from [85.158.137.68:19952] by server-16.bemta-3.messagelabs.com id 32/24-26128-CF869C25; Sun, 05 Jan 2014 14:15:24 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-10.tower-31.messagelabs.com!1388931322!6149425!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 2535 invoked from network); 5 Jan 2014 14:15:23 -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; 5 Jan 2014 14:15:23 -0000 Received: (qmail 23695 invoked by uid 10000); 5 Jan 2014 14:15:22 -0000 Date: Sun, 5 Jan 2014 14:15:22 +0000 From: Anil Madhavapeddy To: Christopher Greenhalgh Message-ID: <20140105141522.GO12036@dark.recoil.org> References: <4C20415C7327A849961F3B8421413725010CD72B64D9@EXCHANGE1.ad.nottingham.ac.uk> <2A9BC77A-0999-4C6E-AC17-C35983A7A6E3@nottingham.ac.uk> <4C20415C7327A849961F3B8421413725010CD72B64DC@EXCHANGE1.ad.nottingham.ac.uk> <4C20415C7327A849961F3B8421413725010CD7203AAC@EXCHANGE1.ad.nottingham.ac.uk> <4C20415C7327A849961F3B8421413725010CD7203BB2@EXCHANGE1.ad.nottingham.ac.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4C20415C7327A849961F3B8421413725010CD7203BB2@EXCHANGE1.ad.nottingham.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Mirage List Subject: Re: [MirageOS-devel] mutable store on 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 I've taken a look at Baardskeerder, and it looks extremely good for a Xen port indeed (and possibly as an Irminsule backend for the blob store, Thomas). Issue: https://github.com/mirage/mirage/issues/185 I'd suggest using it more for logging and the like, but the only hitch is that it doesn't compile under non-Linux yet due to depending on some non-Posix ioctls, but that should be fairly easy to patch with a portable but less durable equivalent. -anil On Fri, Nov 01, 2013 at 10:50:59AM +0000, Christopher Greenhalgh wrote: > As I said in the call, I've got baardskeerder running in Xen/mirage over blkif. > https://github.com/cgreenhalgh/baardskeerder/ > https://github.com/cgreenhalgh/baardskeerder/blob/master/xen_test/README.md > I've run the bsmgr benchmark(s) to run on it, but my dev set-up is in a virtual box vm and I was using xen blktap for the vdisk > https://github.com/cgreenhalgh/baardskeerder/blob/master/benchmark-out.txt > I added page cacheing to the baardskeerder store over blkif but performance is still ~10 slower then direct lwt on unix, and my xen setup is currently about twice as slow again (hopefully down to the blktap disk - I couldn't get xen-disk to compile and I haven't got lvm set up at the mo). > > Anyway, I'll leave the performance alone for now and try building a web app with it and cohttp/etc > > Cheers > Chris > > > > From: cl-mirage-bounces@lists.cam.ac.uk [mailto:cl-mirage-bounces@lists.cam.ac.uk] On Behalf Of Christopher Greenhalgh > Sent: 23 October 2013 16:42 > To: David Scott > Cc: Mirage List > Subject: RE: mutable store on mirage? > > I don't feel like I know enough about block device internals to suggest an alternative yet. > > I've now made a first-cut port of baardskeerder to mirage (splitting out mirage & unix dependencies into sub-packages): > https://github.com/cgreenhalgh/baardskeerder > This has a store that runs over blkif, but currently only the basic baardskeerder Flog0 log option (which has little resilience and no compaction). The store also does no cacheing at the moment... (needs mirage 0.9.8, i.e. io_page fix) > > I've make a very simple mirage btree fa?ade over this: > https://github.com/cgreenhalgh/ocaml-btree > This is passing basic tests on unix, but I haven't got a test harness together yet to try it on Xen. > > The Opam packages are in: > https://github.com/cgreenhalgh/opam-dev-repository > unix-simple-blkdev > mirage-baardskeerder > ocaml-btree > > cheers > Chris > > > From: cl-mirage-bounces@lists.cam.ac.uk [mailto:cl-mirage-bounces@lists.cam.ac.uk] On Behalf Of David Scott > Sent: 21 October 2013 21:16 > To: Christopher Greenhalgh > Cc: Mirage List > Subject: Re: mutable store on mirage? > > Hi Chris, > > Thanks for taking a look at this. When I get a moment I'll check out your code and see if it makes sense to merge in some patches I've got lying around. > > The Blkif API is very quirky. I think we should chuck it away and put something sensible in place. Feel free to propose a new signature! :-) > > Cheers, > Dave > > On Mon, Oct 21, 2013 at 8:57 PM, Christopher Greenhalgh > wrote: > Partly as a learning exercise I have made a blkif implementation over a single file using Lwt_unix - https://github.com/cgreenhalgh/mirage-unix-simple-blkif > It has a couple of basic tests which it passes, but hasn't been exercised beyond that yet; > Neither is it abstracted over threading, but then the Blkif interface isn't yet either... > i intend to try using it as a baardskeerder store next, so we'll see what happens. > > Threw up a few questions... > > As noted in the comment near the top of https://github.com/cgreenhalgh/mirage-unix-simple-blkif/blob/master/lib/blkdev.ml i don't think it will behave precisely the same as ocaml-xen-block-driver for concurrent multi-block reads and writes: currently it will do each in one chunk while the xen driver subdivides and potentially interleaves large reads and... > > Btw there seems to be an ambiguity in the OS.Devices.Blkif interface, specifically what should happen if write_page is called with an Io_page which is actually >1 page long (e.g.from Io_page.get N)? ocaml-xen-block-driver write_page seems to assume that it will be exactly one page (without checking) but is the intended bevaviour (a) split pages and handle each page in turn or (b) explicit error? > > It is also slightly unclear (to me) what the ordering semantics are intended to be for read_512; currently this and the xen-block-driver only actually initiate the read when a thread attempts a (blocking) get on the returned Lwt_sequence. This is the more obvious route as read_512 is non-blocking (i.e. has to immediately return the sequence), but feels slightly odd. > > p.s. as there is no sync operation, is there a particular level of sync to disk/durability defined in the xen block protocol? > > I'm also unsure if it is deliberate that Io_page.page_size isn't visible; i had to use Io_page.round_to_page_size 1 to get page_size out... > > cheers > chris > > > _________________________ > From: Richard Mortier [Richard.Mortier@nottingham.ac.uk] > Sent: 16 October 2013 21:16 > To: David Scott > Cc: Christopher Greenhalgh; Mirage List > Subject: Re: mutable store on mirage? > > On 16 Oct 2013, at 21:08, David Scott wrote: > > > I'd like to see unix blkif implemented (without using the xen implementation). I've got some patches lying around which open files with O_DIRECT and perform unbuffered sector-aligned I/O. I was thinking of making a 'unix-block-driver' with this code in it, mirroring the xen implementation. It's mostly a thin veneer over Lwt_bytes, replacing Bigarray.t with Cstruct.t. In future I was thinking the mirage-platform repo could become the minimal 'boot' code plus module types for Blkif, Netif etc; and all the concrete implementations could be spun out into other repos. > > > > What do people think? > > absolutely agree. thought perhaps we would want to functorise(*) over Lwt, eg packages named > > mirage-blk-xen-lwt > mirage-blk-posix-async > mirage-blk-bsd-blah > > etc...? opam can handle the constraints though (i firmly expect :) > > (*) if i'm making up a verb there and/or using it incorrectly, i apologise... :) > > > -- > 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. > > > > > > > -- > Dave Scott > > > 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. > > > 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. > > > > > > > > > -- Anil Madhavapeddy http://anil.recoil.org _______________________________________________ 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 Jan 05 17:46:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 05 Jan 2014 17:46: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 1VzrmP-0006QO-BO; Sun, 05 Jan 2014 17:46:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VzrmN-0006QJ-9g for mirageos-devel@lists.xenproject.org; Sun, 05 Jan 2014 17:46:27 +0000 Received: from [85.158.139.211:29608] by server-12.bemta-5.messagelabs.com id 8F/0A-30017-27A99C25; Sun, 05 Jan 2014 17:46:26 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1388943985!7948707!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 12929 invoked from network); 5 Jan 2014 17:46:25 -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; 5 Jan 2014 17:46:25 -0000 Received: (qmail 349 invoked by uid 10000); 5 Jan 2014 17:46:24 -0000 Date: Sun, 5 Jan 2014 17:46:24 +0000 From: Anil Madhavapeddy To: Christopher Greenhalgh Message-ID: <20140105174624.GH6636@dark.recoil.org> References: <4C20415C7327A849961F3B8421413725010CD7CBC6AC@EXCHANGE1.ad.nottingham.ac.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4C20415C7327A849961F3B8421413725010CD7CBC6AC@EXCHANGE1.ad.nottingham.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Mirage List Subject: Re: [MirageOS-devel] thoughts about block devices in 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 A 'sync' operation shouldn't be needed with the existing Block API, since it's all guaranteed to be synchronous. Thomas' combinator branch [1] gives us the ability to add transformers to the various interfaces, and I anticipate one of the first ones will be a buffer cache on top of the KV_RO. That cache will need to have the sync operation. Sector size still needs some more thought, though. Dave, what's the state of play with Xen blkfront sector sizes? It seems to creeping up to 4096, which is quite conveniently page-sized... [1] https://github.com/mirage/mirage/pull/178 -anil On Thu, Nov 21, 2013 at 02:38:19PM +0000, Christopher Greenhalgh wrote: > Might be worth adding a 'sync' operation to the abstract signature, even > if it doesn't do anything with initial drivers I would find it useful if > the comments clarified any general constraints/expectations on the > size(s) of buffers for read and write, e.g. arbitrary length in bytes? > Exactly one sector? Any multiple of sector size? A specific multiple of > sector size? Up to any size? > > Cheers > Chris > > > From: cl-mirage-bounces@lists.cam.ac.uk [mailto:cl-mirage-bounces@lists.cam.ac.uk] On Behalf Of Anil Madhavapeddy > Sent: 21 November 2013 11:51 > To: David Scott > Cc: Mirage List > Subject: Re: thoughts about block devices in Mirage > > This all looks right to me. I've merged in most of them (except > xen-block-driver; made a few minor comments on the pull req). > > I'm coming around to the idea that the dynamic device registration is > generally a good idea rather than a pure Mirari-generator, since it > covers hotplug too, and makes development much easier (less boilerplate > code to generate). > > I'm currently porting the Release framework to work as a non-root user, > which will give us an IPC-capable, privdropping Unix backend. I'll hook > in a block device message to dynamically "hotplug" new block devices > into the Unix backend too. This is useful both for testing and for > production use in Unix, since it allows incoming file descriptors to be > sandboxed more easily using frameworks such as Capsicum on FreeBSD. > > -anil > > On 20 Nov 2013, at 15:37, David Scott > wrote: > > > Hi, > > I've been trying to tidy up the mirage block device interface before the big release. I've added a signature BLOCK to mirage-types: > > https://github.com/mirage/mirage-types/blob/master/lib/v1.ml#L124 > > This has notions of > * an active/ open device > * a blocking I/O action > * a page aligned buffer > and allows you to read and write from/to a set of buffers. > > I've proposed a less-abstract version of the signature in mirage-platform/xen (but it should be common to both unix and xen): > > https://github.com/mirage/mirage-platform/pull/73/files > > which looks like this: > > +module type S = V1.BLOCK_DEVICE > + with type page_aligned_buffer := Cstruct.t > + and type 'a io := 'a Lwt.t > > together with a lookup table mapping driver names (strings) to (module S) instances. Does this seem like a reasonable approach? > > In my xen block driver I've added support for this interface and left the old code for backwards compat: > > https://github.com/mirage/ocaml-xen-block-driver/pull/8 > > The idea is the block driver will automatically register itself as a driver called "local". A Unix version could do the same. We could add things like "iscsi" later. > > Finally I've proposed some test cases for mirage-skeleton which check various read/write operations seem to be working (and failing when they should be failing etc): > > https://github.com/mirage/mirage-skeleton/pull/15 > > Let me know what you think. The next step would be to get this new interface working on Unix and then to start working on a filesystem interface (for those who like that sort of thing) > > Cheers, > > -- > Dave Scott > > > 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. > > > > > > > > > -- Anil Madhavapeddy http://anil.recoil.org _______________________________________________ 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 Jan 05 17:46:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 05 Jan 2014 17:46: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 1VzrmP-0006QO-BO; Sun, 05 Jan 2014 17:46:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VzrmN-0006QJ-9g for mirageos-devel@lists.xenproject.org; Sun, 05 Jan 2014 17:46:27 +0000 Received: from [85.158.139.211:29608] by server-12.bemta-5.messagelabs.com id 8F/0A-30017-27A99C25; Sun, 05 Jan 2014 17:46:26 +0000 X-Env-Sender: avsm@dark.recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1388943985!7948707!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 12929 invoked from network); 5 Jan 2014 17:46:25 -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; 5 Jan 2014 17:46:25 -0000 Received: (qmail 349 invoked by uid 10000); 5 Jan 2014 17:46:24 -0000 Date: Sun, 5 Jan 2014 17:46:24 +0000 From: Anil Madhavapeddy To: Christopher Greenhalgh Message-ID: <20140105174624.GH6636@dark.recoil.org> References: <4C20415C7327A849961F3B8421413725010CD7CBC6AC@EXCHANGE1.ad.nottingham.ac.uk> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <4C20415C7327A849961F3B8421413725010CD7CBC6AC@EXCHANGE1.ad.nottingham.ac.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Mirage List Subject: Re: [MirageOS-devel] thoughts about block devices in 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 A 'sync' operation shouldn't be needed with the existing Block API, since it's all guaranteed to be synchronous. Thomas' combinator branch [1] gives us the ability to add transformers to the various interfaces, and I anticipate one of the first ones will be a buffer cache on top of the KV_RO. That cache will need to have the sync operation. Sector size still needs some more thought, though. Dave, what's the state of play with Xen blkfront sector sizes? It seems to creeping up to 4096, which is quite conveniently page-sized... [1] https://github.com/mirage/mirage/pull/178 -anil On Thu, Nov 21, 2013 at 02:38:19PM +0000, Christopher Greenhalgh wrote: > Might be worth adding a 'sync' operation to the abstract signature, even > if it doesn't do anything with initial drivers I would find it useful if > the comments clarified any general constraints/expectations on the > size(s) of buffers for read and write, e.g. arbitrary length in bytes? > Exactly one sector? Any multiple of sector size? A specific multiple of > sector size? Up to any size? > > Cheers > Chris > > > From: cl-mirage-bounces@lists.cam.ac.uk [mailto:cl-mirage-bounces@lists.cam.ac.uk] On Behalf Of Anil Madhavapeddy > Sent: 21 November 2013 11:51 > To: David Scott > Cc: Mirage List > Subject: Re: thoughts about block devices in Mirage > > This all looks right to me. I've merged in most of them (except > xen-block-driver; made a few minor comments on the pull req). > > I'm coming around to the idea that the dynamic device registration is > generally a good idea rather than a pure Mirari-generator, since it > covers hotplug too, and makes development much easier (less boilerplate > code to generate). > > I'm currently porting the Release framework to work as a non-root user, > which will give us an IPC-capable, privdropping Unix backend. I'll hook > in a block device message to dynamically "hotplug" new block devices > into the Unix backend too. This is useful both for testing and for > production use in Unix, since it allows incoming file descriptors to be > sandboxed more easily using frameworks such as Capsicum on FreeBSD. > > -anil > > On 20 Nov 2013, at 15:37, David Scott > wrote: > > > Hi, > > I've been trying to tidy up the mirage block device interface before the big release. I've added a signature BLOCK to mirage-types: > > https://github.com/mirage/mirage-types/blob/master/lib/v1.ml#L124 > > This has notions of > * an active/ open device > * a blocking I/O action > * a page aligned buffer > and allows you to read and write from/to a set of buffers. > > I've proposed a less-abstract version of the signature in mirage-platform/xen (but it should be common to both unix and xen): > > https://github.com/mirage/mirage-platform/pull/73/files > > which looks like this: > > +module type S = V1.BLOCK_DEVICE > + with type page_aligned_buffer := Cstruct.t > + and type 'a io := 'a Lwt.t > > together with a lookup table mapping driver names (strings) to (module S) instances. Does this seem like a reasonable approach? > > In my xen block driver I've added support for this interface and left the old code for backwards compat: > > https://github.com/mirage/ocaml-xen-block-driver/pull/8 > > The idea is the block driver will automatically register itself as a driver called "local". A Unix version could do the same. We could add things like "iscsi" later. > > Finally I've proposed some test cases for mirage-skeleton which check various read/write operations seem to be working (and failing when they should be failing etc): > > https://github.com/mirage/mirage-skeleton/pull/15 > > Let me know what you think. The next step would be to get this new interface working on Unix and then to start working on a filesystem interface (for those who like that sort of thing) > > Cheers, > > -- > Dave Scott > > > 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. > > > > > > > > > -- Anil Madhavapeddy http://anil.recoil.org _______________________________________________ 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 Jan 06 13:09:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 06 Jan 2014 13:09: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 1W09vg-0003aL-TW; Mon, 06 Jan 2014 13:09:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W09vf-0003aG-SH for mirageos-devel@lists.xenproject.org; Mon, 06 Jan 2014 13:09:16 +0000 Received: from [85.158.139.211:22744] by server-10.bemta-5.messagelabs.com id 0E/34-01405-BFAAAC25; Mon, 06 Jan 2014 13:09:15 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-206.messagelabs.com!1389013754!8094377!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 16687 invoked from network); 6 Jan 2014 13:09:14 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-13.tower-206.messagelabs.com with SMTP; 6 Jan 2014 13:09:14 -0000 Received: (qmail 20669 invoked from network); 6 Jan 2014 13:09:10 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 6 Jan 2014 13:09:10 -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 20632-02 for ; Mon, 6 Jan 2014 13:09:08 +0000 (GMT) Received: (qmail 20646 invoked by uid 599); 6 Jan 2014 13:09:06 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 06 Jan 2014 13:09:06 +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 1W09vZ-0007gf-0g for mirageos-devel@lists.xenproject.org; Mon, 06 Jan 2014 13:09:09 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Importance: low X-Priority: 5 Date: Mon, 6 Jan 2014 13:09:07 +0000 Thread-Topic: tangential-- rmox Thread-Index: Ac8K4HuUx926FMxYTa2QgoeIfmeJEQ== Message-ID: <7EF42353-506C-4C90-8E18-D4BAE4B0EDC0@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 engine06-20433-6.icritical.com Subject: [MirageOS-devel] tangential-- rmox 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 just came across this -- vaguely mirage-related i guess -- bare-metal occam-pi http://rmox.net/ -- 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 Jan 06 13:09:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 06 Jan 2014 13:09: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 1W09vg-0003aL-TW; Mon, 06 Jan 2014 13:09:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W09vf-0003aG-SH for mirageos-devel@lists.xenproject.org; Mon, 06 Jan 2014 13:09:16 +0000 Received: from [85.158.139.211:22744] by server-10.bemta-5.messagelabs.com id 0E/34-01405-BFAAAC25; Mon, 06 Jan 2014 13:09:15 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-206.messagelabs.com!1389013754!8094377!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 16687 invoked from network); 6 Jan 2014 13:09:14 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-13.tower-206.messagelabs.com with SMTP; 6 Jan 2014 13:09:14 -0000 Received: (qmail 20669 invoked from network); 6 Jan 2014 13:09:10 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 6 Jan 2014 13:09:10 -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 20632-02 for ; Mon, 6 Jan 2014 13:09:08 +0000 (GMT) Received: (qmail 20646 invoked by uid 599); 6 Jan 2014 13:09:06 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 06 Jan 2014 13:09:06 +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 1W09vZ-0007gf-0g for mirageos-devel@lists.xenproject.org; Mon, 06 Jan 2014 13:09:09 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Importance: low X-Priority: 5 Date: Mon, 6 Jan 2014 13:09:07 +0000 Thread-Topic: tangential-- rmox Thread-Index: Ac8K4HuUx926FMxYTa2QgoeIfmeJEQ== Message-ID: <7EF42353-506C-4C90-8E18-D4BAE4B0EDC0@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 engine06-20433-6.icritical.com Subject: [MirageOS-devel] tangential-- rmox 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 just came across this -- vaguely mirage-related i guess -- bare-metal occam-pi http://rmox.net/ -- 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 Jan 06 13:33:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 06 Jan 2014 13:33:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0AJE-0005DE-Nd; Mon, 06 Jan 2014 13:33:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0AJD-0005D1-2l for mirageos-devel@lists.xenproject.org; Mon, 06 Jan 2014 13:33:35 +0000 Received: from [193.109.254.147:4379] by server-12.bemta-14.messagelabs.com id 17/A6-13681-EA0BAC25; Mon, 06 Jan 2014 13:33:34 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1389015211!9100918!1 X-Originating-IP: [209.85.220.53] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9712 invoked from network); 6 Jan 2014 13:33:33 -0000 Received: from mail-pa0-f53.google.com (HELO mail-pa0-f53.google.com) (209.85.220.53) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Jan 2014 13:33:33 -0000 Received: by mail-pa0-f53.google.com with SMTP id hz1so18525121pad.40 for ; Mon, 06 Jan 2014 05:33:31 -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=yjMOx9D/kJ/sjQnKuTcPJz0yDLugvQgNl9M1W3dkMDE=; b=OgJRSIwIJl5soUcbFWikZ7BBu5lADp7Pcg11lQTR3GD1bq/n9SoKucIdDJErMc55EI c/g7ZK0N8wPrSyXeUAsRs3IohfZBbloqZ1k7jsMEAx/9GvBxXE0WH3ThJ8tQYB2YKd8v hG1H9TO4tZpwmuFLPSfWB6HZZtevmkhddxVGsK9reo8kJOVz67UUvoNNuxSvESKoq6Dn PsPKmHFKyzChVWWOskIPyB4byTzUF4kMO26T/ZUIZclZRgtEgR8K3507FDEl2fX1RkKD ME5kGIr+2RtCPVFyQ2HFQTgfthbealUqvSJEvMaj7Wvh8hul1jXAl0CbP9yAdcOkWKpz 6W0g== MIME-Version: 1.0 X-Received: by 10.68.57.98 with SMTP id h2mr127976262pbq.17.1389015211304; Mon, 06 Jan 2014 05:33:31 -0800 (PST) Received: by 10.70.61.136 with HTTP; Mon, 6 Jan 2014 05:33:31 -0800 (PST) In-Reply-To: <7EF42353-506C-4C90-8E18-D4BAE4B0EDC0@nottingham.ac.uk> References: <7EF42353-506C-4C90-8E18-D4BAE4B0EDC0@nottingham.ac.uk> Date: Mon, 6 Jan 2014 13:33:31 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] tangential-- rmox 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="===============8170095429948619006==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8170095429948619006== Content-Type: multipart/alternative; boundary=bcaec544efe041ef4204ef4d4eec --bcaec544efe041ef4204ef4d4eec Content-Type: text/plain; charset=ISO-8859-1 I particularly like their windowing system. I think Mirage also needs an LCARS-inspired widget toolkit... On Mon, Jan 6, 2014 at 1:09 PM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > just came across this -- vaguely mirage-related i guess -- bare-metal > occam-pi > > http://rmox.net/ > > -- > 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 > -- Dave Scott --bcaec544efe041ef4204ef4d4eec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I particularly like their windowing system. I think Mirage= also needs an LCARS-inspired widget toolkit...


On Mon, Jan 6, 2014 at 1:09 PM, Ric= hard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:
just came across this -- vaguely mirage-rela= ted i guess -- bare-metal occam-pi

http://rmox.net/

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l 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



--
Dave Scott
--bcaec544efe041ef4204ef4d4eec-- --===============8170095429948619006== 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 --===============8170095429948619006==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jan 06 13:33:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 06 Jan 2014 13:33:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0AJE-0005DE-Nd; Mon, 06 Jan 2014 13:33:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0AJD-0005D1-2l for mirageos-devel@lists.xenproject.org; Mon, 06 Jan 2014 13:33:35 +0000 Received: from [193.109.254.147:4379] by server-12.bemta-14.messagelabs.com id 17/A6-13681-EA0BAC25; Mon, 06 Jan 2014 13:33:34 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1389015211!9100918!1 X-Originating-IP: [209.85.220.53] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9712 invoked from network); 6 Jan 2014 13:33:33 -0000 Received: from mail-pa0-f53.google.com (HELO mail-pa0-f53.google.com) (209.85.220.53) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Jan 2014 13:33:33 -0000 Received: by mail-pa0-f53.google.com with SMTP id hz1so18525121pad.40 for ; Mon, 06 Jan 2014 05:33:31 -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=yjMOx9D/kJ/sjQnKuTcPJz0yDLugvQgNl9M1W3dkMDE=; b=OgJRSIwIJl5soUcbFWikZ7BBu5lADp7Pcg11lQTR3GD1bq/n9SoKucIdDJErMc55EI c/g7ZK0N8wPrSyXeUAsRs3IohfZBbloqZ1k7jsMEAx/9GvBxXE0WH3ThJ8tQYB2YKd8v hG1H9TO4tZpwmuFLPSfWB6HZZtevmkhddxVGsK9reo8kJOVz67UUvoNNuxSvESKoq6Dn PsPKmHFKyzChVWWOskIPyB4byTzUF4kMO26T/ZUIZclZRgtEgR8K3507FDEl2fX1RkKD ME5kGIr+2RtCPVFyQ2HFQTgfthbealUqvSJEvMaj7Wvh8hul1jXAl0CbP9yAdcOkWKpz 6W0g== MIME-Version: 1.0 X-Received: by 10.68.57.98 with SMTP id h2mr127976262pbq.17.1389015211304; Mon, 06 Jan 2014 05:33:31 -0800 (PST) Received: by 10.70.61.136 with HTTP; Mon, 6 Jan 2014 05:33:31 -0800 (PST) In-Reply-To: <7EF42353-506C-4C90-8E18-D4BAE4B0EDC0@nottingham.ac.uk> References: <7EF42353-506C-4C90-8E18-D4BAE4B0EDC0@nottingham.ac.uk> Date: Mon, 6 Jan 2014 13:33:31 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] tangential-- rmox 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="===============8170095429948619006==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8170095429948619006== Content-Type: multipart/alternative; boundary=bcaec544efe041ef4204ef4d4eec --bcaec544efe041ef4204ef4d4eec Content-Type: text/plain; charset=ISO-8859-1 I particularly like their windowing system. I think Mirage also needs an LCARS-inspired widget toolkit... On Mon, Jan 6, 2014 at 1:09 PM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > just came across this -- vaguely mirage-related i guess -- bare-metal > occam-pi > > http://rmox.net/ > > -- > 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 > -- Dave Scott --bcaec544efe041ef4204ef4d4eec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I particularly like their windowing system. I think Mirage= also needs an LCARS-inspired widget toolkit...


On Mon, Jan 6, 2014 at 1:09 PM, Ric= hard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:
just came across this -- vaguely mirage-rela= ted i guess -- bare-metal occam-pi

http://rmox.net/

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l 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



--
Dave Scott
--bcaec544efe041ef4204ef4d4eec-- --===============8170095429948619006== 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 --===============8170095429948619006==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 07 09:48:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Jan 2014 09:48:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0TGX-0001NR-74; Tue, 07 Jan 2014 09:48:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0TGU-0001NG-4l for mirageos-devel@lists.xenproject.org; Tue, 07 Jan 2014 09:48:03 +0000 Received: from [85.158.143.35:11186] by server-1.bemta-4.messagelabs.com id 33/98-02132-15DCBC25; Tue, 07 Jan 2014 09:48:01 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1389088079!10010184!1 X-Originating-IP: [209.85.160.44] 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 10036 invoked from network); 7 Jan 2014 09:48:00 -0000 Received: from mail-pb0-f44.google.com (HELO mail-pb0-f44.google.com) (209.85.160.44) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2014 09:48:00 -0000 Received: by mail-pb0-f44.google.com with SMTP id rq2so19716152pbb.17 for ; Tue, 07 Jan 2014 01:47:58 -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=yhpU/ObGju0N6y0I/W06eSEyzEt9b73Jr8CY2vIC/yE=; b=ht55WzQfKaWdy4li5SpucCiHhmD9Okf3Q1X76L9gIlWqmM3voTMhG1zDTVL7DZMzuz OHbwSd3wGCSUd0WH9dhcjE++U9/M7npTjSZAWnZppDRQ4V6/KukeApNiKFr6crw2v4gG KmxQpo6oKTV85wenIUyI3Dy7GhQc4FpQrIrTVtGAzGe53zZRMhIFCG1yGRxyHUuCuYdq jtAo/sJH07IIbMURupDGa+chCMmo7QF7BQaDjUP485jNPQLtkKABjWllew4vkxOiqBwB dd5V2euKATVfM7Yjyxm9eBAJsQuEqIbvVZoy34avNQmPbU8lftnPtYbBiSJYyCxb7Lfp W7Fw== MIME-Version: 1.0 X-Received: by 10.68.248.100 with SMTP id yl4mr133372282pbc.41.1389088078539; Tue, 07 Jan 2014 01:47:58 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 7 Jan 2014 01:47:58 -0800 (PST) Date: Tue, 7 Jan 2014 09:47:58 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today, 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="===============0558806424187571377==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0558806424187571377== Content-Type: multipart/alternative; boundary=047d7b2e14f57bb32a04ef5e45ee --047d7b2e14f57bb32a04ef5e45ee Content-Type: text/plain; charset=ISO-8859-1 Main topic: progress with our blog posts and moving our homepages to the brave new world. Feel free to bring up any other burning issues / blocking bug reports. 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 --047d7b2e14f57bb32a04ef5e45ee Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Main topic: progress with our blog posts and moving our homep= ages to the brave new world. Feel free to bring up any other burning issues= / blocking bug reports.

1. =A0Please join my meeting.
https://www1.gotomeeting.com/join/591890401

2. =A0Use your microphone and sp= eakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0in using your telephone.

United Kingdom (toll-free): 0 80= 8 168 0209 United Kingdom:=A0+44 (0) 207 151 1817

United States (toll-free):=A01 877 309 2070=A0United States:=A0+1 (626) 521-0017

Access Code: 591-890-401<= br style=3D"font-family:arial,sans-serif;font-size:13px">Audio PIN: Shown after joining th= e meeting

Meeting ID: 591-890-401

--
Dave Scott
--047d7b2e14f57bb32a04ef5e45ee-- --===============0558806424187571377== 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 --===============0558806424187571377==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 07 09:48:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Jan 2014 09:48:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0TGX-0001NR-74; Tue, 07 Jan 2014 09:48:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0TGU-0001NG-4l for mirageos-devel@lists.xenproject.org; Tue, 07 Jan 2014 09:48:03 +0000 Received: from [85.158.143.35:11186] by server-1.bemta-4.messagelabs.com id 33/98-02132-15DCBC25; Tue, 07 Jan 2014 09:48:01 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1389088079!10010184!1 X-Originating-IP: [209.85.160.44] 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 10036 invoked from network); 7 Jan 2014 09:48:00 -0000 Received: from mail-pb0-f44.google.com (HELO mail-pb0-f44.google.com) (209.85.160.44) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2014 09:48:00 -0000 Received: by mail-pb0-f44.google.com with SMTP id rq2so19716152pbb.17 for ; Tue, 07 Jan 2014 01:47:58 -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=yhpU/ObGju0N6y0I/W06eSEyzEt9b73Jr8CY2vIC/yE=; b=ht55WzQfKaWdy4li5SpucCiHhmD9Okf3Q1X76L9gIlWqmM3voTMhG1zDTVL7DZMzuz OHbwSd3wGCSUd0WH9dhcjE++U9/M7npTjSZAWnZppDRQ4V6/KukeApNiKFr6crw2v4gG KmxQpo6oKTV85wenIUyI3Dy7GhQc4FpQrIrTVtGAzGe53zZRMhIFCG1yGRxyHUuCuYdq jtAo/sJH07IIbMURupDGa+chCMmo7QF7BQaDjUP485jNPQLtkKABjWllew4vkxOiqBwB dd5V2euKATVfM7Yjyxm9eBAJsQuEqIbvVZoy34avNQmPbU8lftnPtYbBiSJYyCxb7Lfp W7Fw== MIME-Version: 1.0 X-Received: by 10.68.248.100 with SMTP id yl4mr133372282pbc.41.1389088078539; Tue, 07 Jan 2014 01:47:58 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 7 Jan 2014 01:47:58 -0800 (PST) Date: Tue, 7 Jan 2014 09:47:58 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today, 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="===============0558806424187571377==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0558806424187571377== Content-Type: multipart/alternative; boundary=047d7b2e14f57bb32a04ef5e45ee --047d7b2e14f57bb32a04ef5e45ee Content-Type: text/plain; charset=ISO-8859-1 Main topic: progress with our blog posts and moving our homepages to the brave new world. Feel free to bring up any other burning issues / blocking bug reports. 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 --047d7b2e14f57bb32a04ef5e45ee Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Main topic: progress with our blog posts and moving our homep= ages to the brave new world. Feel free to bring up any other burning issues= / blocking bug reports.

1. =A0Please join my meeting.
https://www1.gotomeeting.com/join/591890401

2. =A0Use your microphone and sp= eakers (VoIP) - a headset is recommended. =A0Or,=A0call=A0in using your telephone.

United Kingdom (toll-free): 0 80= 8 168 0209 United Kingdom:=A0+44 (0) 207 151 1817

United States (toll-free):=A01 877 309 2070=A0United States:=A0+1 (626) 521-0017

Access Code: 591-890-401<= br style=3D"font-family:arial,sans-serif;font-size:13px">Audio PIN: Shown after joining th= e meeting

Meeting ID: 591-890-401

--
Dave Scott
--047d7b2e14f57bb32a04ef5e45ee-- --===============0558806424187571377== 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 --===============0558806424187571377==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 07 23:34:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Jan 2014 23:34: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 1W0gAT-0007SX-D3; Tue, 07 Jan 2014 23: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 1W0gAR-0007SS-Ji for mirageos-devel@lists.xenproject.org; Tue, 07 Jan 2014 23:34:39 +0000 Received: from [85.158.137.68:63594] by server-1.bemta-3.messagelabs.com id E9/1A-29598-E0F8CC25; Tue, 07 Jan 2014 23:34:38 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1389137677!4132050!1 X-Originating-IP: [74.125.82.170] 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 29233 invoked from network); 7 Jan 2014 23:34:37 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2014 23:34:37 -0000 Received: by mail-we0-f170.google.com with SMTP id u57so588684wes.15 for ; Tue, 07 Jan 2014 15:34:37 -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 :content-transfer-encoding:message-id:references:to; bh=udWT0VzTsMLQx/u0bAmBirXuWfivzdXaKRQXnjwBXt8=; b=DA39QGrFPQnncgQzzhbgUK9OJThAce1CcDpH1UkPC94knqokZk4eLEZcixTRJSs610 P5q+hgB3FLgd4VBUwb6fXb7hGthB4BGWGXpe46MeL3gEHKzH2zihhjcBLuZ+OQf17oBA RDcB08VEN7qvol88vVe5MuLIr8IrA93KirUom3Uk/FV6igSdbLc8mzngF0Gfgsgiu+iC 0Atxoqnt7zrJW9Or69fOtE/xVdYI5kHeEBbhgnHtRLw9fqGD1Z1WS+dOzA2rs+deAZIl eGJ8mw+Mq+CRQw2mNXIgGp1ejoP98Jf6ORz6jCe0DVTdkJyh7zL6meZ7Ze4etXb79fXT Asqw== X-Received: by 10.180.81.38 with SMTP id w6mr13996153wix.27.1389137676982; Tue, 07 Jan 2014 15:34:36 -0800 (PST) Received: from [192.168.0.1] (bar06-2-82-224-156-126.fbx.proxad.net. [82.224.156.126]) by mx.google.com with ESMTPSA id hv3sm5933063wib.5.2014.01.07.15.34.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Jan 2014 15:34:36 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 8 Jan 2014 00:34:34 +0100 Message-Id: <6A732050-907A-41D0-A640-720BC7D87218@gazagnaire.org> References: To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1827) Subject: Re: [MirageOS-devel] thought on a new API for 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 A quick follow-up in this. I've rebased my 'combinators' branch, and I've fixed some bugs in the code generator and the generated code. See the same PR (#178) for the new patches. Also, I've quickly ported mirage-www to this new API. The result config.ml is pretty straightforward (I think): - https://github.com/samoht/mirage-www/blob/combinators/src/config.ml - https://github.com/mirage/mirage-www/pull/83 Feedback is welcome (I'm keen to help to write/adapt a FS dispatcher or something else if needed). Thomas PS: I think I'll stash the branch before integrating #178 because the history is quite messy and not very useful On 27 Dec 2013, at 13:14, Thomas Gazagnaire wrote: > Hi, > > During the last days, I've been working on a new version of the mirage API which should be easier to extend and where defining new operators would be easier. I'm starting to be happy with the result, which is available here: > > https://github.com/mirage/mirage/pull/178 > > The branch is not ready to merge yet, but I've published it anyway to get early feedback, so feel free to shout if you dislike it or have better ideas. > > The new API: https://github.com/samoht/mirage/blob/combinators/lib/mirage.mli > > Some examples: > * https://github.com/samoht/mirage/blob/combinators/lib_test/fat/config.ml > * https://github.com/samoht/mirage/blob/combinators/lib_test/http/config.ml > * some combinator examples: https://github.com/samoht/mirage/blob/combinators/lib_test/combinator/config.ml > > Some of you might have noticed some similarity with the great ctype library -- it's not a coincidence at all: the goal here is to meta-program at the modules/functors level, which is not very far from trying to interface with a foreign language ... > > -- > 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 Tue Jan 07 23:34:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Jan 2014 23:34: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 1W0gAT-0007SX-D3; Tue, 07 Jan 2014 23: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 1W0gAR-0007SS-Ji for mirageos-devel@lists.xenproject.org; Tue, 07 Jan 2014 23:34:39 +0000 Received: from [85.158.137.68:63594] by server-1.bemta-3.messagelabs.com id E9/1A-29598-E0F8CC25; Tue, 07 Jan 2014 23:34:38 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1389137677!4132050!1 X-Originating-IP: [74.125.82.170] 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 29233 invoked from network); 7 Jan 2014 23:34:37 -0000 Received: from mail-we0-f170.google.com (HELO mail-we0-f170.google.com) (74.125.82.170) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Jan 2014 23:34:37 -0000 Received: by mail-we0-f170.google.com with SMTP id u57so588684wes.15 for ; Tue, 07 Jan 2014 15:34:37 -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 :content-transfer-encoding:message-id:references:to; bh=udWT0VzTsMLQx/u0bAmBirXuWfivzdXaKRQXnjwBXt8=; b=DA39QGrFPQnncgQzzhbgUK9OJThAce1CcDpH1UkPC94knqokZk4eLEZcixTRJSs610 P5q+hgB3FLgd4VBUwb6fXb7hGthB4BGWGXpe46MeL3gEHKzH2zihhjcBLuZ+OQf17oBA RDcB08VEN7qvol88vVe5MuLIr8IrA93KirUom3Uk/FV6igSdbLc8mzngF0Gfgsgiu+iC 0Atxoqnt7zrJW9Or69fOtE/xVdYI5kHeEBbhgnHtRLw9fqGD1Z1WS+dOzA2rs+deAZIl eGJ8mw+Mq+CRQw2mNXIgGp1ejoP98Jf6ORz6jCe0DVTdkJyh7zL6meZ7Ze4etXb79fXT Asqw== X-Received: by 10.180.81.38 with SMTP id w6mr13996153wix.27.1389137676982; Tue, 07 Jan 2014 15:34:36 -0800 (PST) Received: from [192.168.0.1] (bar06-2-82-224-156-126.fbx.proxad.net. [82.224.156.126]) by mx.google.com with ESMTPSA id hv3sm5933063wib.5.2014.01.07.15.34.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Jan 2014 15:34:36 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 8 Jan 2014 00:34:34 +0100 Message-Id: <6A732050-907A-41D0-A640-720BC7D87218@gazagnaire.org> References: To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1827) Subject: Re: [MirageOS-devel] thought on a new API for 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 A quick follow-up in this. I've rebased my 'combinators' branch, and I've fixed some bugs in the code generator and the generated code. See the same PR (#178) for the new patches. Also, I've quickly ported mirage-www to this new API. The result config.ml is pretty straightforward (I think): - https://github.com/samoht/mirage-www/blob/combinators/src/config.ml - https://github.com/mirage/mirage-www/pull/83 Feedback is welcome (I'm keen to help to write/adapt a FS dispatcher or something else if needed). Thomas PS: I think I'll stash the branch before integrating #178 because the history is quite messy and not very useful On 27 Dec 2013, at 13:14, Thomas Gazagnaire wrote: > Hi, > > During the last days, I've been working on a new version of the mirage API which should be easier to extend and where defining new operators would be easier. I'm starting to be happy with the result, which is available here: > > https://github.com/mirage/mirage/pull/178 > > The branch is not ready to merge yet, but I've published it anyway to get early feedback, so feel free to shout if you dislike it or have better ideas. > > The new API: https://github.com/samoht/mirage/blob/combinators/lib/mirage.mli > > Some examples: > * https://github.com/samoht/mirage/blob/combinators/lib_test/fat/config.ml > * https://github.com/samoht/mirage/blob/combinators/lib_test/http/config.ml > * some combinator examples: https://github.com/samoht/mirage/blob/combinators/lib_test/combinator/config.ml > > Some of you might have noticed some similarity with the great ctype library -- it's not a coincidence at all: the goal here is to meta-program at the modules/functors level, which is not very far from trying to interface with a foreign language ... > > -- > 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 Wed Jan 08 09:32:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Jan 2014 09:32: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 1W0pUV-0003xo-L1; Wed, 08 Jan 2014 09:31:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0pUT-0003xf-P8 for mirageos-devel@lists.xenproject.org; Wed, 08 Jan 2014 09:31:58 +0000 Received: from [85.158.137.68:34769] by server-12.bemta-3.messagelabs.com id 58/AD-20055-D0B1DC25; Wed, 08 Jan 2014 09:31:57 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1389173515!7830638!1 X-Originating-IP: [74.125.82.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 32242 invoked from network); 8 Jan 2014 09:31:56 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 09:31:56 -0000 Received: by mail-we0-f179.google.com with SMTP id q59so1211147wes.10 for ; Wed, 08 Jan 2014 01:31:55 -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 :content-transfer-encoding:message-id:references:to; bh=cxtCPMcKfotk11eV9g2GSzH7hiBGajEM8fLYAN5Fb70=; b=n1HuaqgKb6MG7TaG38kgo7azU61nzpq6CUJ2p6xeQIv8ihSR7/SF7BDAfVYAUDbfgx 7MJxEe0s57hTSLcfxAeYmfLS8uhKRbqELu9MK4RMbsK2Fu4JKAlqLcMKqAs9m8pzK7m+ SxeY/G/YLTwHQ0mJIo0DsWx19gBUOhP1X9m50MwwY9YBCd+R2TfdpETXgzwK59Ktl8Pq SqTirrmBOg01CuAzUBM4L64hokDQ25p3xcw06XI/VBgctefHryAHbRf7NFnmUULHSdpq At9FMbEuZZd1xzXdy8jjR/kKnNTatEJ5CLxJkIBZGotKUkrf1zjEj/spYomJSgYW2MNH 3QAw== X-Received: by 10.194.78.210 with SMTP id d18mr81597593wjx.27.1389173515538; Wed, 08 Jan 2014 01:31:55 -0800 (PST) Received: from [192.168.0.1] (bar06-2-82-224-156-126.fbx.proxad.net. [82.224.156.126]) by mx.google.com with ESMTPSA id ks3sm27460908wjc.10.2014.01.08.01.31.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 01:31:54 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: <6A732050-907A-41D0-A640-720BC7D87218@gazagnaire.org> Date: Wed, 8 Jan 2014 10:31:54 +0100 Message-Id: References: <6A732050-907A-41D0-A640-720BC7D87218@gazagnaire.org> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1827) Subject: Re: [MirageOS-devel] thought on a new API for 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 > Also, I've quickly ported mirage-www to this new API. The result config.ml is pretty straightforward (I think): > - https://github.com/samoht/mirage-www/blob/combinators/src/config.ml > - https://github.com/mirage/mirage-www/pull/83 I've just added https://github.com/samoht/mirage/commit/53baf3e3204f7380f5e90aeae278dc4a95e03766 to remove the need of the thin shell wrapper that we currently use to pack a directory into a FAT-formated block device. As a result, the tests are now simpler to write: https://github.com/samoht/mirage/commit/822b5cb75aaa9756897c31dd12d793cb8d0eda19 (I've also updated my PR to mirage-www to remove the same shell script and use the new 'fat_of_files' function instead in config.ml) -- 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 Wed Jan 08 09:32:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Jan 2014 09:32: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 1W0pUV-0003xo-L1; Wed, 08 Jan 2014 09:31:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W0pUT-0003xf-P8 for mirageos-devel@lists.xenproject.org; Wed, 08 Jan 2014 09:31:58 +0000 Received: from [85.158.137.68:34769] by server-12.bemta-3.messagelabs.com id 58/AD-20055-D0B1DC25; Wed, 08 Jan 2014 09:31:57 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1389173515!7830638!1 X-Originating-IP: [74.125.82.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 32242 invoked from network); 8 Jan 2014 09:31:56 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 09:31:56 -0000 Received: by mail-we0-f179.google.com with SMTP id q59so1211147wes.10 for ; Wed, 08 Jan 2014 01:31:55 -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 :content-transfer-encoding:message-id:references:to; bh=cxtCPMcKfotk11eV9g2GSzH7hiBGajEM8fLYAN5Fb70=; b=n1HuaqgKb6MG7TaG38kgo7azU61nzpq6CUJ2p6xeQIv8ihSR7/SF7BDAfVYAUDbfgx 7MJxEe0s57hTSLcfxAeYmfLS8uhKRbqELu9MK4RMbsK2Fu4JKAlqLcMKqAs9m8pzK7m+ SxeY/G/YLTwHQ0mJIo0DsWx19gBUOhP1X9m50MwwY9YBCd+R2TfdpETXgzwK59Ktl8Pq SqTirrmBOg01CuAzUBM4L64hokDQ25p3xcw06XI/VBgctefHryAHbRf7NFnmUULHSdpq At9FMbEuZZd1xzXdy8jjR/kKnNTatEJ5CLxJkIBZGotKUkrf1zjEj/spYomJSgYW2MNH 3QAw== X-Received: by 10.194.78.210 with SMTP id d18mr81597593wjx.27.1389173515538; Wed, 08 Jan 2014 01:31:55 -0800 (PST) Received: from [192.168.0.1] (bar06-2-82-224-156-126.fbx.proxad.net. [82.224.156.126]) by mx.google.com with ESMTPSA id ks3sm27460908wjc.10.2014.01.08.01.31.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 01:31:54 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: <6A732050-907A-41D0-A640-720BC7D87218@gazagnaire.org> Date: Wed, 8 Jan 2014 10:31:54 +0100 Message-Id: References: <6A732050-907A-41D0-A640-720BC7D87218@gazagnaire.org> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1827) Subject: Re: [MirageOS-devel] thought on a new API for 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 > Also, I've quickly ported mirage-www to this new API. The result config.ml is pretty straightforward (I think): > - https://github.com/samoht/mirage-www/blob/combinators/src/config.ml > - https://github.com/mirage/mirage-www/pull/83 I've just added https://github.com/samoht/mirage/commit/53baf3e3204f7380f5e90aeae278dc4a95e03766 to remove the need of the thin shell wrapper that we currently use to pack a directory into a FAT-formated block device. As a result, the tests are now simpler to write: https://github.com/samoht/mirage/commit/822b5cb75aaa9756897c31dd12d793cb8d0eda19 (I've also updated my PR to mirage-www to remove the same shell script and use the new 'fat_of_files' function instead in config.ml) -- 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 Wed Jan 08 22:51:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Jan 2014 22:51: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 1W11y5-0001vd-1X; Wed, 08 Jan 2014 22:51:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W11y3-0001vK-2y; Wed, 08 Jan 2014 22:51:19 +0000 Received: from [85.158.143.35:42816] by server-1.bemta-4.messagelabs.com id B2/21-02132-666DDC25; Wed, 08 Jan 2014 22:51:18 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1389221466!10380092!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: YXN5bmNfZGVsYXk6IDcwNjg4ODEgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26199 invoked from network); 8 Jan 2014 22:51:08 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 22:51:08 -0000 X-IronPort-AV: E=Sophos;i="4.95,626,1384300800"; d="asc'?scan'208";a="88938087" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 08 Jan 2014 22:50:49 +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; Wed, 8 Jan 2014 17:50:48 -0500 Message-ID: <1389221447.16457.24.camel@Solace> From: Dario Faggioli To: Date: Wed, 8 Jan 2014 23:50:47 +0100 In-Reply-To: <52C2CD67.6050603@xen.org> References: <52B03A2A.807@xen.org> <1388246226.15148.4.camel@Solace> <52C2CD67.6050603@xen.org> X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , mirageos-devel@lists.xenproject.org, "publicity@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Publicity] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. 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="===============3833443975319149711==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3833443975319149711== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-W8K1qlr634eyxl2U9E1o" --=-W8K1qlr634eyxl2U9E1o Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-12-31 at 13:57 +0000, Lars Kurth wrote: > On 28/12/2013 15:57, Dario Faggioli wrote: > > So I was wondering, we did not get that much of a response about this > > (or perhaps we did, but not in public, in which case, ignore me). > > > > I know, holidays are not helping, etc. but, anyway, should we turn this > > e-mail into a blog post to send out in early January? I'm up for it if > > we think it's a good thing to do. > It is probably the holidays: I know that Cloudious Systems (the makers= =20 > of OSv) are interested showing OSv running on top of Xen and so do the= =20 > XO guys. >=20 > A blog post could be a good idea (tying it up with the DevRoom program,= =20 > which has not yet been published). > Ok. I checked this out earlier today, and the program for Saturday is out... Still waiting for Sunday. As soon as that will be available, I think, as you suggest, we should blog about these two things, i.e.: - the devroom program - the chance of showing demos at the booth (mentioning which ones we=20 already know will be performed) > Another approach would be to reach out pro-actively to people we want to= =20 > do demos (e.g. Samsung, people/projects with RT schedulers, ...).=20 > Unfortunuately I will struggle to do this given that I am in China. >=20 Right. I did that for Qubes, and it worked, as it did for OSv. I'll try to ping some more people directly, let's see how that goes. 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) --=-W8K1qlr634eyxl2U9E1o 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 iEYEABECAAYFAlLN1kcACgkQk4XaBE3IOsS/BQCeKkExjbBjYrffaDvQ8Y1Uljtg 7hsAnifpbMIrvyYu/l69uVvPIszvAalN =WHwC -----END PGP SIGNATURE----- --=-W8K1qlr634eyxl2U9E1o-- --===============3833443975319149711== 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 --===============3833443975319149711==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jan 08 22:51:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 08 Jan 2014 22:51: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 1W11y5-0001vd-1X; Wed, 08 Jan 2014 22:51:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W11y3-0001vK-2y; Wed, 08 Jan 2014 22:51:19 +0000 Received: from [85.158.143.35:42816] by server-1.bemta-4.messagelabs.com id B2/21-02132-666DDC25; Wed, 08 Jan 2014 22:51:18 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1389221466!10380092!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: YXN5bmNfZGVsYXk6IDcwNjg4ODEgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26199 invoked from network); 8 Jan 2014 22:51:08 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 8 Jan 2014 22:51:08 -0000 X-IronPort-AV: E=Sophos;i="4.95,626,1384300800"; d="asc'?scan'208";a="88938087" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 08 Jan 2014 22:50:49 +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; Wed, 8 Jan 2014 17:50:48 -0500 Message-ID: <1389221447.16457.24.camel@Solace> From: Dario Faggioli To: Date: Wed, 8 Jan 2014 23:50:47 +0100 In-Reply-To: <52C2CD67.6050603@xen.org> References: <52B03A2A.807@xen.org> <1388246226.15148.4.camel@Solace> <52C2CD67.6050603@xen.org> X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , mirageos-devel@lists.xenproject.org, "publicity@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Publicity] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. 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="===============3833443975319149711==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3833443975319149711== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-W8K1qlr634eyxl2U9E1o" --=-W8K1qlr634eyxl2U9E1o Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-12-31 at 13:57 +0000, Lars Kurth wrote: > On 28/12/2013 15:57, Dario Faggioli wrote: > > So I was wondering, we did not get that much of a response about this > > (or perhaps we did, but not in public, in which case, ignore me). > > > > I know, holidays are not helping, etc. but, anyway, should we turn this > > e-mail into a blog post to send out in early January? I'm up for it if > > we think it's a good thing to do. > It is probably the holidays: I know that Cloudious Systems (the makers= =20 > of OSv) are interested showing OSv running on top of Xen and so do the= =20 > XO guys. >=20 > A blog post could be a good idea (tying it up with the DevRoom program,= =20 > which has not yet been published). > Ok. I checked this out earlier today, and the program for Saturday is out... Still waiting for Sunday. As soon as that will be available, I think, as you suggest, we should blog about these two things, i.e.: - the devroom program - the chance of showing demos at the booth (mentioning which ones we=20 already know will be performed) > Another approach would be to reach out pro-actively to people we want to= =20 > do demos (e.g. Samsung, people/projects with RT schedulers, ...).=20 > Unfortunuately I will struggle to do this given that I am in China. >=20 Right. I did that for Qubes, and it worked, as it did for OSv. I'll try to ping some more people directly, let's see how that goes. 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) --=-W8K1qlr634eyxl2U9E1o 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 iEYEABECAAYFAlLN1kcACgkQk4XaBE3IOsS/BQCeKkExjbBjYrffaDvQ8Y1Uljtg 7hsAnifpbMIrvyYu/l69uVvPIszvAalN =WHwC -----END PGP SIGNATURE----- --=-W8K1qlr634eyxl2U9E1o-- --===============3833443975319149711== 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 --===============3833443975319149711==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 14 12:16:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jan 2014 12:16: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 1W32ur-0002lD-Tj; Tue, 14 Jan 2014 12:16:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W32uq-0002l8-MU for mirageos-devel@lists.xenproject.org; Tue, 14 Jan 2014 12:16:21 +0000 Received: from [193.109.254.147:57965] by server-1.bemta-14.messagelabs.com id 0F/34-15600-39A25D25; Tue, 14 Jan 2014 12:16:19 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1389701297!10678254!1 X-Originating-IP: [209.85.160.47] 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 31284 invoked from network); 14 Jan 2014 12:08:19 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2014 12:08:19 -0000 Received: by mail-pb0-f47.google.com with SMTP id um1so8582828pbc.34 for ; Tue, 14 Jan 2014 04:07:18 -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=Kd73ahHCxdHEVkY4VCj59boSmrEkOJrqtdVcAc7vj2A=; b=BbJjH4sbSk8AbeT/2ETGvWDqEGZ77HqoOPMArs7duI00kcSfe4tW9AmKqFud3hOzCn ACEcfyBGIeMVYPoscgfvPygvuBoYFfoYdEUhetZk7Tv1MZWw7Ms1jBFBHqbPiYGOs+kG 91Re0AnGUqtLlbMI7G6CvAmZ6sokXSPP2csek5UqhSh31z62scnbIsisIfLshjGiflGN GvGmsa7xRlBnuDSPCRNizYaoNAmUWONUcTtC2Rp68Cju6r9JXC5oL8RrmD4paXvYQIwk SyM8CeYNcOnvNrs8MGo2F9e/1RRlvms3vsoWf55FOaFHx2KA75WhlNViI+3/E0wKL14F qxiQ== MIME-Version: 1.0 X-Received: by 10.68.234.67 with SMTP id uc3mr1255217pbc.27.1389701238420; Tue, 14 Jan 2014 04:07:18 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 14 Jan 2014 04:07:18 -0800 (PST) Date: Tue, 14 Jan 2014 12:07:18 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today, 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="===============8049639294704994669==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8049639294704994669== Content-Type: multipart/alternative; boundary=047d7b33d7a8a8fc0f04efed0850 --047d7b33d7a8a8fc0f04efed0850 Content-Type: text/plain; charset=ISO-8859-1 Main topic: progress with our blog posts and moving our homepages to the brave new world. Feel free to bring up any other burning issues / blocking bug reports. 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 --047d7b33d7a8a8fc0f04efed0850 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Main topic: progress with our blog posts and moving o= ur homepages to the brave new world. Feel free to bring up any other burnin= g issues / blocking bug reports.


1.= =A0Please join my meeting.

2. =A0Use your m= icrophone and speakers (VoIP) - a headset is recommended. =A0Or, call in us= ing your telephone.

United Kingdom (toll-free): 0 808 168 0209 United Kingd= om: +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 meeti= ng

Meeting ID: 591-890-401

-- =
Dave Scott
--047d7b33d7a8a8fc0f04efed0850-- --===============8049639294704994669== 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 --===============8049639294704994669==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 14 12:16:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jan 2014 12:16: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 1W32ur-0002lD-Tj; Tue, 14 Jan 2014 12:16:21 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W32uq-0002l8-MU for mirageos-devel@lists.xenproject.org; Tue, 14 Jan 2014 12:16:21 +0000 Received: from [193.109.254.147:57965] by server-1.bemta-14.messagelabs.com id 0F/34-15600-39A25D25; Tue, 14 Jan 2014 12:16:19 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1389701297!10678254!1 X-Originating-IP: [209.85.160.47] 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 31284 invoked from network); 14 Jan 2014 12:08:19 -0000 Received: from mail-pb0-f47.google.com (HELO mail-pb0-f47.google.com) (209.85.160.47) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 14 Jan 2014 12:08:19 -0000 Received: by mail-pb0-f47.google.com with SMTP id um1so8582828pbc.34 for ; Tue, 14 Jan 2014 04:07:18 -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=Kd73ahHCxdHEVkY4VCj59boSmrEkOJrqtdVcAc7vj2A=; b=BbJjH4sbSk8AbeT/2ETGvWDqEGZ77HqoOPMArs7duI00kcSfe4tW9AmKqFud3hOzCn ACEcfyBGIeMVYPoscgfvPygvuBoYFfoYdEUhetZk7Tv1MZWw7Ms1jBFBHqbPiYGOs+kG 91Re0AnGUqtLlbMI7G6CvAmZ6sokXSPP2csek5UqhSh31z62scnbIsisIfLshjGiflGN GvGmsa7xRlBnuDSPCRNizYaoNAmUWONUcTtC2Rp68Cju6r9JXC5oL8RrmD4paXvYQIwk SyM8CeYNcOnvNrs8MGo2F9e/1RRlvms3vsoWf55FOaFHx2KA75WhlNViI+3/E0wKL14F qxiQ== MIME-Version: 1.0 X-Received: by 10.68.234.67 with SMTP id uc3mr1255217pbc.27.1389701238420; Tue, 14 Jan 2014 04:07:18 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 14 Jan 2014 04:07:18 -0800 (PST) Date: Tue, 14 Jan 2014 12:07:18 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today, 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="===============8049639294704994669==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8049639294704994669== Content-Type: multipart/alternative; boundary=047d7b33d7a8a8fc0f04efed0850 --047d7b33d7a8a8fc0f04efed0850 Content-Type: text/plain; charset=ISO-8859-1 Main topic: progress with our blog posts and moving our homepages to the brave new world. Feel free to bring up any other burning issues / blocking bug reports. 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 --047d7b33d7a8a8fc0f04efed0850 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Main topic: progress with our blog posts and moving o= ur homepages to the brave new world. Feel free to bring up any other burnin= g issues / blocking bug reports.


1.= =A0Please join my meeting.

2. =A0Use your m= icrophone and speakers (VoIP) - a headset is recommended. =A0Or, call in us= ing your telephone.

United Kingdom (toll-free): 0 808 168 0209 United Kingd= om: +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 meeti= ng

Meeting ID: 591-890-401

-- =
Dave Scott
--047d7b33d7a8a8fc0f04efed0850-- --===============8049639294704994669== 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 --===============8049639294704994669==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 14 15:57:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jan 2014 15:57:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W36My-000131-NO; Tue, 14 Jan 2014 15:57:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W36Mx-00012u-02 for mirageos-devel@lists.xenproject.org; Tue, 14 Jan 2014 15:57:35 +0000 Received: from [85.158.137.68:58437] by server-12.bemta-3.messagelabs.com id DD/48-20055-E6E55D25; Tue, 14 Jan 2014 15:57:34 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-31.messagelabs.com!1389715053!9051591!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 13502 invoked from network); 14 Jan 2014 15:57:33 -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; 14 Jan 2014 15:57:33 -0000 Received: (qmail 14500 invoked by uid 634); 14 Jan 2014 15:57: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 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, 14 Jan 2014 15:57:18 +0000 From: Anil Madhavapeddy Message-Id: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> Date: Tue, 14 Jan 2014 15:57:17 +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] Drop OCaml 4.00.1 support? 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 We currently support both OCaml 4.00.1 and 4.01.0. I've got two reasons to propose dropping OCaml 4.00.1 support: - Thomas' extremely useful combinator support uses fancy GADTs that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 - I'm refactoring the runtime library to install cross-compilation headers (see James Bielman's request a while back), and it's extra work to port both runtimes. Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to drop 4.00.1 support unless anyone wants to speak up against. 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 Tue Jan 14 15:57:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jan 2014 15:57:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W36My-000131-NO; Tue, 14 Jan 2014 15:57:36 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W36Mx-00012u-02 for mirageos-devel@lists.xenproject.org; Tue, 14 Jan 2014 15:57:35 +0000 Received: from [85.158.137.68:58437] by server-12.bemta-3.messagelabs.com id DD/48-20055-E6E55D25; Tue, 14 Jan 2014 15:57:34 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-31.messagelabs.com!1389715053!9051591!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 13502 invoked from network); 14 Jan 2014 15:57:33 -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; 14 Jan 2014 15:57:33 -0000 Received: (qmail 14500 invoked by uid 634); 14 Jan 2014 15:57: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 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, 14 Jan 2014 15:57:18 +0000 From: Anil Madhavapeddy Message-Id: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> Date: Tue, 14 Jan 2014 15:57:17 +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] Drop OCaml 4.00.1 support? 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 We currently support both OCaml 4.00.1 and 4.01.0. I've got two reasons to propose dropping OCaml 4.00.1 support: - Thomas' extremely useful combinator support uses fancy GADTs that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 - I'm refactoring the runtime library to install cross-compilation headers (see James Bielman's request a while back), and it's extra work to port both runtimes. Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to drop 4.00.1 support unless anyone wants to speak up against. 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 Tue Jan 14 15:59:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jan 2014 15:59: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 1W36P3-0001GQ-Uw; Tue, 14 Jan 2014 15:59:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W36P2-0001GJ-AZ for mirageos-devel@lists.xenproject.org; Tue, 14 Jan 2014 15:59:44 +0000 Received: from [85.158.143.35:64996] by server-2.bemta-4.messagelabs.com id 2D/A0-11386-FEE55D25; Tue, 14 Jan 2014 15:59:43 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-6.tower-21.messagelabs.com!1389715182!4556535!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 25329 invoked from network); 14 Jan 2014 15:59:42 -0000 Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk) (131.111.8.132) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2014 15:59:42 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-212-230.in-addr.btopenworld.com ([81.149.212.230]:18445 helo=[10.0.1.4]) 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 1W36P0-0000DH-1B (Exim 4.82_3-c0e5623) (return-path ); Tue, 14 Jan 2014 15:59:42 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Tue, 14 Jan 2014 15:59:41 +0000 Message-Id: References: To: David Scott , "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage weekly call today, 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org [thought I'd sent this hours ago -- just found it in my drafts folder. -ac] I welcome our new unikernel overlords. = My transition to willing subservience will be more enjoyable if I can make = a unikernel site by pointing at a root of a directory tree that has a bunch= of html/css/etc and then out pops an image I can just deploy somewhere. More concretely, it means I can keep using Jekyll to produce my static site= (dealing with markdown/scripts/etc) and and then use that as input into a= mirage-ify step. Eventually, this can all be strung together in OCaml/Bas= h but it means I can put off dealing with the 'OCaml static site generation= ' piece until later. I've already said all of the above in person to several of you but I'm wri= ting it down so that it's =85 err ... written down. ac On 14 Jan 2014, at 12:07, David Scott wrote: > Main topic: progress with our blog posts and moving our homepages to the = brave new world. Feel free to bring up any other burning issues / blocking = bug reports. > = > = > 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 15= 1 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 Jan 14 15:59:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jan 2014 15:59: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 1W36P3-0001GQ-Uw; Tue, 14 Jan 2014 15:59:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W36P2-0001GJ-AZ for mirageos-devel@lists.xenproject.org; Tue, 14 Jan 2014 15:59:44 +0000 Received: from [85.158.143.35:64996] by server-2.bemta-4.messagelabs.com id 2D/A0-11386-FEE55D25; Tue, 14 Jan 2014 15:59:43 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-6.tower-21.messagelabs.com!1389715182!4556535!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 25329 invoked from network); 14 Jan 2014 15:59:42 -0000 Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk) (131.111.8.132) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2014 15:59:42 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-212-230.in-addr.btopenworld.com ([81.149.212.230]:18445 helo=[10.0.1.4]) 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 1W36P0-0000DH-1B (Exim 4.82_3-c0e5623) (return-path ); Tue, 14 Jan 2014 15:59:42 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Tue, 14 Jan 2014 15:59:41 +0000 Message-Id: References: To: David Scott , "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage weekly call today, 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org [thought I'd sent this hours ago -- just found it in my drafts folder. -ac] I welcome our new unikernel overlords. = My transition to willing subservience will be more enjoyable if I can make = a unikernel site by pointing at a root of a directory tree that has a bunch= of html/css/etc and then out pops an image I can just deploy somewhere. More concretely, it means I can keep using Jekyll to produce my static site= (dealing with markdown/scripts/etc) and and then use that as input into a= mirage-ify step. Eventually, this can all be strung together in OCaml/Bas= h but it means I can put off dealing with the 'OCaml static site generation= ' piece until later. I've already said all of the above in person to several of you but I'm wri= ting it down so that it's =85 err ... written down. ac On 14 Jan 2014, at 12:07, David Scott wrote: > Main topic: progress with our blog posts and moving our homepages to the = brave new world. Feel free to bring up any other burning issues / blocking = bug reports. > = > = > 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 15= 1 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 Jan 14 17:00:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jan 2014 17:00: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 1W37Le-0006CI-35; Tue, 14 Jan 2014 17:00:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W37Ld-0006CB-2O for mirageos-devel@lists.xenproject.org; Tue, 14 Jan 2014 17:00:17 +0000 Received: from [85.158.143.35:25755] by server-2.bemta-4.messagelabs.com id 74/12-11386-02D65D25; Tue, 14 Jan 2014 17:00:16 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1389718815!11706681!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 6192 invoked from network); 14 Jan 2014 17:00:15 -0000 Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk) (131.111.8.142) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2014 17:00:15 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-152-144.eduroam.lapwing.private.cam.ac.uk ([172.17.152.144]:50734) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jjl25) (TLSv1:AES128-SHA:128) id 1W37Lb-0002Gv-7W (Exim 4.82_3-c0e5623) (return-path ); Tue, 14 Jan 2014 17:00:15 +0000 References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> Mime-Version: 1.0 (1.0) In-Reply-To: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> Message-Id: X-Mailer: iPad Mail (11B554a) From: Jon Ludlam Date: Tue, 14 Jan 2014 17:00:15 +0000 To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Drop OCaml 4.00.1 support? 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 Fine by me. Who needs 4.00.1 when you have opam? :-) Jon Sent from my iPad > On 14 Jan 2014, at 15:57, Anil Madhavapeddy wrote: > > We currently support both OCaml 4.00.1 and 4.01.0. I've got two reasons to propose dropping OCaml 4.00.1 support: > > - Thomas' extremely useful combinator support uses fancy GADTs that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 > > - I'm refactoring the runtime library to install cross-compilation headers (see James Bielman's request a while back), and it's extra work to port both runtimes. > > Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to drop 4.00.1 support unless anyone wants to speak up against. > > cheers, > 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 Tue Jan 14 17:00:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 14 Jan 2014 17:00: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 1W37Le-0006CI-35; Tue, 14 Jan 2014 17:00:18 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W37Ld-0006CB-2O for mirageos-devel@lists.xenproject.org; Tue, 14 Jan 2014 17:00:17 +0000 Received: from [85.158.143.35:25755] by server-2.bemta-4.messagelabs.com id 74/12-11386-02D65D25; Tue, 14 Jan 2014 17:00:16 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1389718815!11706681!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 6192 invoked from network); 14 Jan 2014 17:00:15 -0000 Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk) (131.111.8.142) by server-14.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Jan 2014 17:00:15 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-152-144.eduroam.lapwing.private.cam.ac.uk ([172.17.152.144]:50734) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jjl25) (TLSv1:AES128-SHA:128) id 1W37Lb-0002Gv-7W (Exim 4.82_3-c0e5623) (return-path ); Tue, 14 Jan 2014 17:00:15 +0000 References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> Mime-Version: 1.0 (1.0) In-Reply-To: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> Message-Id: X-Mailer: iPad Mail (11B554a) From: Jon Ludlam Date: Tue, 14 Jan 2014 17:00:15 +0000 To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Drop OCaml 4.00.1 support? 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 Fine by me. Who needs 4.00.1 when you have opam? :-) Jon Sent from my iPad > On 14 Jan 2014, at 15:57, Anil Madhavapeddy wrote: > > We currently support both OCaml 4.00.1 and 4.01.0. I've got two reasons to propose dropping OCaml 4.00.1 support: > > - Thomas' extremely useful combinator support uses fancy GADTs that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 > > - I'm refactoring the runtime library to install cross-compilation headers (see James Bielman's request a while back), and it's extra work to port both runtimes. > > Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to drop 4.00.1 support unless anyone wants to speak up against. > > cheers, > 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 Wed Jan 15 01:15:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 01:15: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 1W3F4d-0001W2-4W; Wed, 15 Jan 2014 01:15:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3F4b-0001Vx-He for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 01:15:13 +0000 Received: from [85.158.137.68:46539] by server-15.bemta-3.messagelabs.com id 4D/7C-11556-021E5D25; Wed, 15 Jan 2014 01:15:12 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1389748511!8353297!1 X-Originating-IP: [209.85.212.173] 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 8190 invoked from network); 15 Jan 2014 01:15:11 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 01:15:11 -0000 Received: by mail-wi0-f173.google.com with SMTP id d13so3090964wiw.0 for ; Tue, 14 Jan 2014 17:15:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=ohstevRC+pGq99pt9sm7YWtmklxt3/hk0Y7852FYm80=; b=g2vLGi8Isgi9vquUtgfujZy73hFcnOvADN3Y8DGOXLOBosR3NjF+wxkNYWu2MVk3gz srVf/V7LG7GUXX/JsTLrSq2tMGMyEoy/BoXbxSmCifNUp/7l/7CODv61MdXW3qv7QY0j 0SJEtt1wNZWxuGsxIQErZddUqCaiIXyImVRFnwvTvW8ebGsNZL+PKptcjJJcvUiyeO2v 9YYHucFtINSBrD4gXLa7sDahbiv41xe7Vv82DJl2qUHhi6IaG3meD74oksMvhcqsPtxW Q47i8MhGAkFbHGwEGk23zLzfbP4pVGrAYilgA/luBTjH+iaTTaAZkZdHAhuBGHJ1DD8y uUEA== X-Received: by 10.180.89.193 with SMTP id bq1mr5783139wib.22.1389748511264; Tue, 14 Jan 2014 17:15:11 -0800 (PST) Received: from [192.168.0.11] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ux5sm1968387wjc.6.2014.01.14.17.15.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Jan 2014 17:15:10 -0800 (PST) From: Thomas Gazagnaire Message-Id: <8943193A-2BE3-4C1E-8252-9EC240DFE2BC@gazagnaire.org> Date: Wed, 15 Jan 2014 01:15:09 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [MirageOS-devel] ocaml-git and git2fat 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, I've just released a small proof-of-concept too to create a FAT image from a Git snapshot. The code is available on my Github account (see [1]) and it should land in OPAM quite soon. This tool takes a Git repository as argument (either local on your disk, or remote) and a commit/tag name, and create a FAT image with the filesystem corresponding to that commit. If the repository is remote, it clones the contents in memory using 'ocaml-git' (see [2]), an implementation of the Git protocol in pure OCaml. Dave, the current FAT API is very low-levell, that would be great if we can have an higher level one to avoid duplicating code with fat/impl.ml in git2fat.ml (see [3]). Best, Thomas [1] https://github.com/samoht/git2fat [2] https://github.com/samoht/ocaml-git [3] https://github.com/samoht/git2fat/blob/master/lib/git2fat.ml _______________________________________________ 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 Jan 15 01:15:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 01:15: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 1W3F4d-0001W2-4W; Wed, 15 Jan 2014 01:15:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3F4b-0001Vx-He for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 01:15:13 +0000 Received: from [85.158.137.68:46539] by server-15.bemta-3.messagelabs.com id 4D/7C-11556-021E5D25; Wed, 15 Jan 2014 01:15:12 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1389748511!8353297!1 X-Originating-IP: [209.85.212.173] 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 8190 invoked from network); 15 Jan 2014 01:15:11 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 01:15:11 -0000 Received: by mail-wi0-f173.google.com with SMTP id d13so3090964wiw.0 for ; Tue, 14 Jan 2014 17:15:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=ohstevRC+pGq99pt9sm7YWtmklxt3/hk0Y7852FYm80=; b=g2vLGi8Isgi9vquUtgfujZy73hFcnOvADN3Y8DGOXLOBosR3NjF+wxkNYWu2MVk3gz srVf/V7LG7GUXX/JsTLrSq2tMGMyEoy/BoXbxSmCifNUp/7l/7CODv61MdXW3qv7QY0j 0SJEtt1wNZWxuGsxIQErZddUqCaiIXyImVRFnwvTvW8ebGsNZL+PKptcjJJcvUiyeO2v 9YYHucFtINSBrD4gXLa7sDahbiv41xe7Vv82DJl2qUHhi6IaG3meD74oksMvhcqsPtxW Q47i8MhGAkFbHGwEGk23zLzfbP4pVGrAYilgA/luBTjH+iaTTaAZkZdHAhuBGHJ1DD8y uUEA== X-Received: by 10.180.89.193 with SMTP id bq1mr5783139wib.22.1389748511264; Tue, 14 Jan 2014 17:15:11 -0800 (PST) Received: from [192.168.0.11] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ux5sm1968387wjc.6.2014.01.14.17.15.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Jan 2014 17:15:10 -0800 (PST) From: Thomas Gazagnaire Message-Id: <8943193A-2BE3-4C1E-8252-9EC240DFE2BC@gazagnaire.org> Date: Wed, 15 Jan 2014 01:15:09 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [MirageOS-devel] ocaml-git and git2fat 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, I've just released a small proof-of-concept too to create a FAT image from a Git snapshot. The code is available on my Github account (see [1]) and it should land in OPAM quite soon. This tool takes a Git repository as argument (either local on your disk, or remote) and a commit/tag name, and create a FAT image with the filesystem corresponding to that commit. If the repository is remote, it clones the contents in memory using 'ocaml-git' (see [2]), an implementation of the Git protocol in pure OCaml. Dave, the current FAT API is very low-levell, that would be great if we can have an higher level one to avoid duplicating code with fat/impl.ml in git2fat.ml (see [3]). Best, Thomas [1] https://github.com/samoht/git2fat [2] https://github.com/samoht/ocaml-git [3] https://github.com/samoht/git2fat/blob/master/lib/git2fat.ml _______________________________________________ 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 Jan 15 11:07:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 11:07:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3OJN-0003KN-8K; Wed, 15 Jan 2014 11:07:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3OJH-0003K2-Ui for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 11:07:00 +0000 Received: from [85.158.139.211:58897] by server-13.bemta-5.messagelabs.com id 5B/B4-11357-ECB66D25; Wed, 15 Jan 2014 11:06:54 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-206.messagelabs.com!1389784013!9874433!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 7056 invoked from network); 15 Jan 2014 11:06:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-206.messagelabs.com with SMTP; 15 Jan 2014 11:06:53 -0000 Received: (qmail 9725 invoked by uid 634); 15 Jan 2014 11:06:53 -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, 15 Jan 2014 11:06:52 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <8943193A-2BE3-4C1E-8252-9EC240DFE2BC@gazagnaire.org> Date: Wed, 15 Jan 2014 11:06:50 +0000 Message-Id: <7BB386DC-4E64-4E85-B207-E0F48CB34381@recoil.org> References: <8943193A-2BE3-4C1E-8252-9EC240DFE2BC@gazagnaire.org> To: Thomas Gazagnaire 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] ocaml-git and git2fat 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 Jan 2014, at 01:15, Thomas Gazagnaire wrote: > Hi, > > I've just released a small proof-of-concept too to create a FAT image from a Git snapshot. The code is available on my Github account (see [1]) and it should land in OPAM quite soon. > > This tool takes a Git repository as argument (either local on your disk, or remote) and a commit/tag name, and create a FAT image with the filesystem corresponding to that commit. If the repository is remote, it clones the contents in memory using 'ocaml-git' (see [2]), an implementation of the Git protocol in pure OCaml. Just to follow up with a note from the weekly call: we're going to try and use this as the update layer for the website code. Mort's got the Cowabloga port almost done for this week, and then I'll hook it together for next week. We're on Sunday 2nd Feb at 1300; https://fosdem.org/2014/schedule/track/miscellaneous/ -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 Jan 15 11:07:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 11:07:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3OJN-0003KN-8K; Wed, 15 Jan 2014 11:07:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3OJH-0003K2-Ui for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 11:07:00 +0000 Received: from [85.158.139.211:58897] by server-13.bemta-5.messagelabs.com id 5B/B4-11357-ECB66D25; Wed, 15 Jan 2014 11:06:54 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-206.messagelabs.com!1389784013!9874433!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 7056 invoked from network); 15 Jan 2014 11:06:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-206.messagelabs.com with SMTP; 15 Jan 2014 11:06:53 -0000 Received: (qmail 9725 invoked by uid 634); 15 Jan 2014 11:06:53 -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, 15 Jan 2014 11:06:52 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <8943193A-2BE3-4C1E-8252-9EC240DFE2BC@gazagnaire.org> Date: Wed, 15 Jan 2014 11:06:50 +0000 Message-Id: <7BB386DC-4E64-4E85-B207-E0F48CB34381@recoil.org> References: <8943193A-2BE3-4C1E-8252-9EC240DFE2BC@gazagnaire.org> To: Thomas Gazagnaire 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] ocaml-git and git2fat 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 Jan 2014, at 01:15, Thomas Gazagnaire wrote: > Hi, > > I've just released a small proof-of-concept too to create a FAT image from a Git snapshot. The code is available on my Github account (see [1]) and it should land in OPAM quite soon. > > This tool takes a Git repository as argument (either local on your disk, or remote) and a commit/tag name, and create a FAT image with the filesystem corresponding to that commit. If the repository is remote, it clones the contents in memory using 'ocaml-git' (see [2]), an implementation of the Git protocol in pure OCaml. Just to follow up with a note from the weekly call: we're going to try and use this as the update layer for the website code. Mort's got the Cowabloga port almost done for this week, and then I'll hook it together for next week. We're on Sunday 2nd Feb at 1300; https://fosdem.org/2014/schedule/track/miscellaneous/ -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 Jan 15 11:11:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 11:11:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3ONm-0003qX-N8; Wed, 15 Jan 2014 11:11:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3ONl-0003qS-KR for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 11:11:38 +0000 Received: from [85.158.139.211:39343] by server-11.bemta-5.messagelabs.com id A1/86-23268-8EC66D25; Wed, 15 Jan 2014 11:11:36 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1389784295!9873318!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 1551 invoked from network); 15 Jan 2014 11:11:35 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-206.messagelabs.com with SMTP; 15 Jan 2014 11:11:35 -0000 Received: (qmail 28663 invoked by uid 634); 15 Jan 2014 11:11:35 -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, 15 Jan 2014 11:11:33 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 15 Jan 2014 11:11:32 +0000 Message-Id: <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@recoil.org> References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> To: Jon Ludlam 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] Drop OCaml 4.00.1 support? 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 Great; this is only for the metaprogramming layer (the Mirage command-line tool), so we'll continue to test the libraries themselves for now. The only other point raised by Daniel Buenzli on GitHub was a lurking bug in the 4.01.0 and libffi integration (which is used by Ctypes). This isn't a critical blocker, so I expect we'll either switch to stub generation or figure out the libffi bug when we get to it in the future. So: dropping 4.00.1 compatibility in Mirage 1.1.x it is. -anil On 14 Jan 2014, at 17:00, Jon Ludlam wrote: > Fine by me. Who needs 4.00.1 when you have opam? :-) > > Jon > > Sent from my iPad > >> On 14 Jan 2014, at 15:57, Anil Madhavapeddy wrote: >> >> We currently support both OCaml 4.00.1 and 4.01.0. I've got two reasons to propose dropping OCaml 4.00.1 support: >> >> - Thomas' extremely useful combinator support uses fancy GADTs that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 >> >> - I'm refactoring the runtime library to install cross-compilation headers (see James Bielman's request a while back), and it's extra work to port both runtimes. >> >> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to drop 4.00.1 support unless anyone wants to speak up against. >> >> cheers, >> 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 > _______________________________________________ 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 Jan 15 11:11:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 11:11:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3ONm-0003qX-N8; Wed, 15 Jan 2014 11:11:38 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3ONl-0003qS-KR for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 11:11:38 +0000 Received: from [85.158.139.211:39343] by server-11.bemta-5.messagelabs.com id A1/86-23268-8EC66D25; Wed, 15 Jan 2014 11:11:36 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1389784295!9873318!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 1551 invoked from network); 15 Jan 2014 11:11:35 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-206.messagelabs.com with SMTP; 15 Jan 2014 11:11:35 -0000 Received: (qmail 28663 invoked by uid 634); 15 Jan 2014 11:11:35 -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, 15 Jan 2014 11:11:33 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 15 Jan 2014 11:11:32 +0000 Message-Id: <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@recoil.org> References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> To: Jon Ludlam 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] Drop OCaml 4.00.1 support? 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 Great; this is only for the metaprogramming layer (the Mirage command-line tool), so we'll continue to test the libraries themselves for now. The only other point raised by Daniel Buenzli on GitHub was a lurking bug in the 4.01.0 and libffi integration (which is used by Ctypes). This isn't a critical blocker, so I expect we'll either switch to stub generation or figure out the libffi bug when we get to it in the future. So: dropping 4.00.1 compatibility in Mirage 1.1.x it is. -anil On 14 Jan 2014, at 17:00, Jon Ludlam wrote: > Fine by me. Who needs 4.00.1 when you have opam? :-) > > Jon > > Sent from my iPad > >> On 14 Jan 2014, at 15:57, Anil Madhavapeddy wrote: >> >> We currently support both OCaml 4.00.1 and 4.01.0. I've got two reasons to propose dropping OCaml 4.00.1 support: >> >> - Thomas' extremely useful combinator support uses fancy GADTs that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 >> >> - I'm refactoring the runtime library to install cross-compilation headers (see James Bielman's request a while back), and it's extra work to port both runtimes. >> >> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to drop 4.00.1 support unless anyone wants to speak up against. >> >> cheers, >> 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 > _______________________________________________ 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 Jan 15 11:14:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 11:14: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 1W3OQE-0003rv-VP; Wed, 15 Jan 2014 11:14:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3OQD-0003rn-Hd for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 11:14:10 +0000 Received: from [85.158.137.68:33618] by server-15.bemta-3.messagelabs.com id 0E/82-11556-08D66D25; Wed, 15 Jan 2014 11:14:08 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1389784444!9215749!1 X-Originating-IP: [209.85.220.53] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_40_50,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 20730 invoked from network); 15 Jan 2014 11:14:06 -0000 Received: from mail-pa0-f53.google.com (HELO mail-pa0-f53.google.com) (209.85.220.53) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 11:14:06 -0000 Received: by mail-pa0-f53.google.com with SMTP id lj1so1005024pab.12 for ; Wed, 15 Jan 2014 03:14:04 -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=cR4aQrQ/67Rk2nNu4VZsxwZ298X6iS9YKVbNRLzXAoo=; b=UNNNXht0X9cc0HFs39r5kmX1gSx/IjI9HYThJ4V63iLwb9Ic00WQMl65LHEEpMIRMx LSSGIIWi42lsowyYzHM0/aWt8r71WRaBRloZn9hHV/dM50bHIDivxBFZkbKxqEKAsqVn yNlzig+ToMRVkmk3INN1CEvsZlLdv5/A2cfmYcMsza3n3patn9XCL3ZXFxeCi3Be6Hxb NY0O2VQn7UEr6vgBBOvxDKObItwEZvuhjVFly4uthgW0wI5b4k/CnSVQV1cpp5ZCCwKB o5ndsTc7/sPdYye5bg43FoKvEoQs3G0w75c8A+Tvl7X/NPKbBQ39XiWCEc/XLJffxyCJ 1TJg== MIME-Version: 1.0 X-Received: by 10.66.158.132 with SMTP id wu4mr2051527pab.66.1389784444583; Wed, 15 Jan 2014 03:14:04 -0800 (PST) Received: by 10.70.61.136 with HTTP; Wed, 15 Jan 2014 03:14:04 -0800 (PST) In-Reply-To: <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@recoil.org> References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@recoil.org> Date: Wed, 15 Jan 2014 11:14:04 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Drop OCaml 4.00.1 support? 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="===============3687916047389317070==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3687916047389317070== Content-Type: multipart/alternative; boundary=047d7bacc1a0224a4904f000683b --047d7bacc1a0224a4904f000683b Content-Type: text/plain; charset=ISO-8859-1 Dropping 4.00.1 is also fine by me! On Wednesday, January 15, 2014, Anil Madhavapeddy wrote: > Great; this is only for the metaprogramming layer (the Mirage command-line > tool), so we'll continue to test the libraries themselves for now. > > The only other point raised by Daniel Buenzli on GitHub was a lurking bug > in the 4.01.0 and libffi integration (which is used by Ctypes). This isn't > a critical blocker, so I expect we'll either switch to stub generation or > figure out the libffi bug when we get to it in the future. > > So: dropping 4.00.1 compatibility in Mirage 1.1.x it is. > > -anil > > On 14 Jan 2014, at 17:00, Jon Ludlam > > wrote: > > > Fine by me. Who needs 4.00.1 when you have opam? :-) > > > > Jon > > > > Sent from my iPad > > > >> On 14 Jan 2014, at 15:57, Anil Madhavapeddy > > wrote: > >> > >> We currently support both OCaml 4.00.1 and 4.01.0. I've got two > reasons to propose dropping OCaml 4.00.1 support: > >> > >> - Thomas' extremely useful combinator support uses fancy GADTs that > don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 > >> > >> - I'm refactoring the runtime library to install cross-compilation > headers (see James Bielman's request a while back), and it's extra work to > port both runtimes. > >> > >> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to drop > 4.00.1 support unless anyone wants to speak up against. > >> > >> cheers, > >> 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 > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --047d7bacc1a0224a4904f000683b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dropping 4.00.1 is also fine by me!

On Wednesday, January 15, 2014, = Anil Madhavapeddy wrote:
Great; this is = only for the metaprogramming layer (the Mirage command-line tool), so we= 9;ll continue to test the libraries themselves for now.

The only other point raised by Daniel Buenzli on GitHub was a lurking bug i= n the 4.01.0 and libffi integration (which is used by Ctypes). =A0This isn&= #39;t a critical blocker, so I expect we'll either switch to stub gener= ation or figure out the libffi bug when we get to it in the future.

So: dropping 4.00.1 compatibility in Mirage 1.1.x it is.

-anil

On 14 Jan 2014, at 17:00, Jon Ludlam <jjl25@cam.ac.uk> wrote:

> Fine by me. Who needs 4.00.1 when you have opam? :-)
>
> Jon
>
> Sent from my iPad
>
>> On 14 Jan 2014, at 15:57, Anil Madhavapeddy <ani= l@recoil.org> wrote:
>>
>> We currently support both OCaml 4.00.1 and 4.01.0. =A0I've got= two reasons to propose dropping OCaml 4.00.1 support:
>>
>> - Thomas' extremely useful combinator support uses fancy GADTs= that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190<= br> >>
>> - I'm refactoring the runtime library to install cross-compila= tion headers (see James Bielman's request a while back), and it's e= xtra work to port both runtimes.
>>
>> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happ= y to drop 4.00.1 support unless anyone wants to speak up against.
>>
>> cheers,
>> 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/lis= tinfo/mirageos-devel
>


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


--
Dave Scott
--047d7bacc1a0224a4904f000683b-- --===============3687916047389317070== 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 --===============3687916047389317070==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jan 15 11:14:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 11:14: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 1W3OQE-0003rv-VP; Wed, 15 Jan 2014 11:14:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3OQD-0003rn-Hd for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 11:14:10 +0000 Received: from [85.158.137.68:33618] by server-15.bemta-3.messagelabs.com id 0E/82-11556-08D66D25; Wed, 15 Jan 2014 11:14:08 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1389784444!9215749!1 X-Originating-IP: [209.85.220.53] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_40_50,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 20730 invoked from network); 15 Jan 2014 11:14:06 -0000 Received: from mail-pa0-f53.google.com (HELO mail-pa0-f53.google.com) (209.85.220.53) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 11:14:06 -0000 Received: by mail-pa0-f53.google.com with SMTP id lj1so1005024pab.12 for ; Wed, 15 Jan 2014 03:14:04 -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=cR4aQrQ/67Rk2nNu4VZsxwZ298X6iS9YKVbNRLzXAoo=; b=UNNNXht0X9cc0HFs39r5kmX1gSx/IjI9HYThJ4V63iLwb9Ic00WQMl65LHEEpMIRMx LSSGIIWi42lsowyYzHM0/aWt8r71WRaBRloZn9hHV/dM50bHIDivxBFZkbKxqEKAsqVn yNlzig+ToMRVkmk3INN1CEvsZlLdv5/A2cfmYcMsza3n3patn9XCL3ZXFxeCi3Be6Hxb NY0O2VQn7UEr6vgBBOvxDKObItwEZvuhjVFly4uthgW0wI5b4k/CnSVQV1cpp5ZCCwKB o5ndsTc7/sPdYye5bg43FoKvEoQs3G0w75c8A+Tvl7X/NPKbBQ39XiWCEc/XLJffxyCJ 1TJg== MIME-Version: 1.0 X-Received: by 10.66.158.132 with SMTP id wu4mr2051527pab.66.1389784444583; Wed, 15 Jan 2014 03:14:04 -0800 (PST) Received: by 10.70.61.136 with HTTP; Wed, 15 Jan 2014 03:14:04 -0800 (PST) In-Reply-To: <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@recoil.org> References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@recoil.org> Date: Wed, 15 Jan 2014 11:14:04 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Drop OCaml 4.00.1 support? 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="===============3687916047389317070==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3687916047389317070== Content-Type: multipart/alternative; boundary=047d7bacc1a0224a4904f000683b --047d7bacc1a0224a4904f000683b Content-Type: text/plain; charset=ISO-8859-1 Dropping 4.00.1 is also fine by me! On Wednesday, January 15, 2014, Anil Madhavapeddy wrote: > Great; this is only for the metaprogramming layer (the Mirage command-line > tool), so we'll continue to test the libraries themselves for now. > > The only other point raised by Daniel Buenzli on GitHub was a lurking bug > in the 4.01.0 and libffi integration (which is used by Ctypes). This isn't > a critical blocker, so I expect we'll either switch to stub generation or > figure out the libffi bug when we get to it in the future. > > So: dropping 4.00.1 compatibility in Mirage 1.1.x it is. > > -anil > > On 14 Jan 2014, at 17:00, Jon Ludlam > > wrote: > > > Fine by me. Who needs 4.00.1 when you have opam? :-) > > > > Jon > > > > Sent from my iPad > > > >> On 14 Jan 2014, at 15:57, Anil Madhavapeddy > > wrote: > >> > >> We currently support both OCaml 4.00.1 and 4.01.0. I've got two > reasons to propose dropping OCaml 4.00.1 support: > >> > >> - Thomas' extremely useful combinator support uses fancy GADTs that > don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 > >> > >> - I'm refactoring the runtime library to install cross-compilation > headers (see James Bielman's request a while back), and it's extra work to > port both runtimes. > >> > >> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to drop > 4.00.1 support unless anyone wants to speak up against. > >> > >> cheers, > >> 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 > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --047d7bacc1a0224a4904f000683b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dropping 4.00.1 is also fine by me!

On Wednesday, January 15, 2014, = Anil Madhavapeddy wrote:
Great; this is = only for the metaprogramming layer (the Mirage command-line tool), so we= 9;ll continue to test the libraries themselves for now.

The only other point raised by Daniel Buenzli on GitHub was a lurking bug i= n the 4.01.0 and libffi integration (which is used by Ctypes). =A0This isn&= #39;t a critical blocker, so I expect we'll either switch to stub gener= ation or figure out the libffi bug when we get to it in the future.

So: dropping 4.00.1 compatibility in Mirage 1.1.x it is.

-anil

On 14 Jan 2014, at 17:00, Jon Ludlam <jjl25@cam.ac.uk> wrote:

> Fine by me. Who needs 4.00.1 when you have opam? :-)
>
> Jon
>
> Sent from my iPad
>
>> On 14 Jan 2014, at 15:57, Anil Madhavapeddy <ani= l@recoil.org> wrote:
>>
>> We currently support both OCaml 4.00.1 and 4.01.0. =A0I've got= two reasons to propose dropping OCaml 4.00.1 support:
>>
>> - Thomas' extremely useful combinator support uses fancy GADTs= that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190<= br> >>
>> - I'm refactoring the runtime library to install cross-compila= tion headers (see James Bielman's request a while back), and it's e= xtra work to port both runtimes.
>>
>> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happ= y to drop 4.00.1 support unless anyone wants to speak up against.
>>
>> cheers,
>> 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/lis= tinfo/mirageos-devel
>


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


--
Dave Scott
--047d7bacc1a0224a4904f000683b-- --===============3687916047389317070== 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 --===============3687916047389317070==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jan 15 13:44:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 13:44:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3QlN-00030m-GG; Wed, 15 Jan 2014 13:44:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3QlM-00030a-Ua for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 13:44:09 +0000 Received: from [85.158.143.35:17522] by server-1.bemta-4.messagelabs.com id 50/8E-02132-8A096D25; Wed, 15 Jan 2014 13:44:08 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1389793447!11833740!1 X-Originating-IP: [74.125.82.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 16392 invoked from network); 15 Jan 2014 13:44:07 -0000 Received: from mail-we0-f181.google.com (HELO mail-we0-f181.google.com) (74.125.82.181) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 13:44:07 -0000 Received: by mail-we0-f181.google.com with SMTP id u56so1802886wes.12 for ; Wed, 15 Jan 2014 05:44:04 -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=8whw3+xWZC/Yq08lhyIWI0l8xIKifE2c2xjfyCk2l5c=; b=UhnqoJuCvmaefP9sLNV/bB/702BBcHsuUIalsVO/q4gxEVHNLV7AtV1F95zOIFMVCR 6kOs7WmbR3IShuiTjvNZ7GcjkCyZw+6V2Ptu1a8n5GadNRuRs4wMxGij/Umk9FxTOkXx H4K2elXNK+R7KKwONAub91+kcWgEiDPSl5tBH5NegQRksfZcGplkwkSrslva6wZSHt2O ISj0HTnq/zM2/UcJUBIVJ9Ww61i9fFzLcgq9imVgFDiv9+TjrePVdnqWiElGCVz0TwtC wrB/oYCgouDp5jU0/jUQSn+2YwVn4w4p6URAFj3ozRPs/02EF2etjTlO22piDPNJojWg LIPA== X-Received: by 10.194.185.205 with SMTP id fe13mr2475541wjc.23.1389793443723; Wed, 15 Jan 2014 05:44:03 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id ot9sm3327688wjc.0.2014.01.15.05.44.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 05:44:02 -0800 (PST) Message-ID: <52D690A1.5060204@xen.org> Date: Wed, 15 Jan 2014 13:44:01 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org References: <52B44230.20209@xen.org> In-Reply-To: <52B44230.20209@xen.org> Subject: Re: [MirageOS-devel] Pre FOSDEM Hackathon [Urgent, please vote] 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 just talked to KB from CentOS about this and we agreed that we don't have enough time to pull this off this time. Both KB and I have too much on our plates right now, to make this happen. Sorry for any inconvenience caused. Regards Lars On 20/12/2013 13:12, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and > it is possible that we can have some space (including sponsored food) > on the 31st of Jan in Brussells to collaborate with other projects. > If we get enough people who would be interested to attend, I will help > coorganize it. If you would go, please reply +1. > 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 Wed Jan 15 13:44:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 13:44:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3QlN-00030m-GG; Wed, 15 Jan 2014 13:44:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3QlM-00030a-Ua for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 13:44:09 +0000 Received: from [85.158.143.35:17522] by server-1.bemta-4.messagelabs.com id 50/8E-02132-8A096D25; Wed, 15 Jan 2014 13:44:08 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1389793447!11833740!1 X-Originating-IP: [74.125.82.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 16392 invoked from network); 15 Jan 2014 13:44:07 -0000 Received: from mail-we0-f181.google.com (HELO mail-we0-f181.google.com) (74.125.82.181) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 13:44:07 -0000 Received: by mail-we0-f181.google.com with SMTP id u56so1802886wes.12 for ; Wed, 15 Jan 2014 05:44:04 -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=8whw3+xWZC/Yq08lhyIWI0l8xIKifE2c2xjfyCk2l5c=; b=UhnqoJuCvmaefP9sLNV/bB/702BBcHsuUIalsVO/q4gxEVHNLV7AtV1F95zOIFMVCR 6kOs7WmbR3IShuiTjvNZ7GcjkCyZw+6V2Ptu1a8n5GadNRuRs4wMxGij/Umk9FxTOkXx H4K2elXNK+R7KKwONAub91+kcWgEiDPSl5tBH5NegQRksfZcGplkwkSrslva6wZSHt2O ISj0HTnq/zM2/UcJUBIVJ9Ww61i9fFzLcgq9imVgFDiv9+TjrePVdnqWiElGCVz0TwtC wrB/oYCgouDp5jU0/jUQSn+2YwVn4w4p6URAFj3ozRPs/02EF2etjTlO22piDPNJojWg LIPA== X-Received: by 10.194.185.205 with SMTP id fe13mr2475541wjc.23.1389793443723; Wed, 15 Jan 2014 05:44:03 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id ot9sm3327688wjc.0.2014.01.15.05.44.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 05:44:02 -0800 (PST) Message-ID: <52D690A1.5060204@xen.org> Date: Wed, 15 Jan 2014 13:44:01 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org References: <52B44230.20209@xen.org> In-Reply-To: <52B44230.20209@xen.org> Subject: Re: [MirageOS-devel] Pre FOSDEM Hackathon [Urgent, please vote] 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 just talked to KB from CentOS about this and we agreed that we don't have enough time to pull this off this time. Both KB and I have too much on our plates right now, to make this happen. Sorry for any inconvenience caused. Regards Lars On 20/12/2013 13:12, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and > it is possible that we can have some space (including sponsored food) > on the 31st of Jan in Brussells to collaborate with other projects. > If we get enough people who would be interested to attend, I will help > coorganize it. If you would go, please reply +1. > 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 Wed Jan 15 14:16:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 14:16: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 1W3RGy-00062I-4g; Wed, 15 Jan 2014 14:16:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3RGu-00061W-H4 for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 14:16:46 +0000 Received: from [85.158.143.35:2645] by server-2.bemta-4.messagelabs.com id 3A/7D-11386-B4896D25; Wed, 15 Jan 2014 14:16:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-21.messagelabs.com!1389795402!9234222!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 2442 invoked from network); 15 Jan 2014 14:16:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-21.messagelabs.com with SMTP; 15 Jan 2014 14:16:42 -0000 Received: (qmail 4439 invoked by uid 634); 15 Jan 2014 14:16:41 -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, 15 Jan 2014 14:16:40 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 15 Jan 2014 14:16:37 +0000 Message-Id: <20367F3A-0A1E-45A0-89AA-CED3D8DA3B4B@recoil.org> References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@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] Drop OCaml 4.00.1 support? 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="===============0424080215328615262==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0424080215328615262== Content-Type: multipart/alternative; boundary="Apple-Mail=_ED564D59-4499-4F32-890C-632420BEF96C" --Apple-Mail=_ED564D59-4499-4F32-890C-632420BEF96C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I've merged the combinator branch, but Jeremy Yallop and I also had a = quick look at why it was broken. It turns out to be because of the use of record disambiguation (a new = feature in 4.01.0), and I've sent a pull request that fixes it here: https://github.com/mirage/mirage/pull/194 It does make the code slightly less elegant though. Thomas, do you mind = if we apply this one for now? -anil On 15 Jan 2014, at 11:14, David Scott wrote: > Dropping 4.00.1 is also fine by me! >=20 > On Wednesday, January 15, 2014, Anil Madhavapeddy wrote: > Great; this is only for the metaprogramming layer (the Mirage = command-line tool), so we'll continue to test the libraries themselves = for now. >=20 > The only other point raised by Daniel Buenzli on GitHub was a lurking = bug in the 4.01.0 and libffi integration (which is used by Ctypes). = This isn't a critical blocker, so I expect we'll either switch to stub = generation or figure out the libffi bug when we get to it in the future. >=20 > So: dropping 4.00.1 compatibility in Mirage 1.1.x it is. >=20 > -anil >=20 > On 14 Jan 2014, at 17:00, Jon Ludlam wrote: >=20 > > Fine by me. Who needs 4.00.1 when you have opam? :-) > > > > Jon > > > > Sent from my iPad > > > >> On 14 Jan 2014, at 15:57, Anil Madhavapeddy = wrote: > >> > >> We currently support both OCaml 4.00.1 and 4.01.0. I've got two = reasons to propose dropping OCaml 4.00.1 support: > >> > >> - Thomas' extremely useful combinator support uses fancy GADTs that = don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 > >> > >> - I'm refactoring the runtime library to install cross-compilation = headers (see James Bielman's request a while back), and it's extra work = to port both runtimes. > >> > >> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to = drop 4.00.1 support unless anyone wants to speak up against. > >> > >> cheers, > >> 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 > > >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 >=20 > --=20 > Dave Scott --Apple-Mail=_ED564D59-4499-4F32-890C-632420BEF96C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I've = merged the combinator branch, but Jeremy Yallop and I also had a quick = look at why it was broken.

It turns out to be because = of the use of record disambiguation (a new feature in 4.01.0), and I've = sent a pull request that fixes it here:

It does make the code = slightly less elegant though. Thomas, do you mind if we apply this one = for now?

-anil

On 15 = Jan 2014, at 11:14, David Scott <scott.dj@gmail.com> = wrote:

Dropping 4.00.1 is also fine by me!

On Wednesday, = January 15, 2014, Anil Madhavapeddy wrote:
Great; this is only for the metaprogramming = layer (the Mirage command-line tool), so we'll continue to test the = libraries themselves for now.

The only other point raised by Daniel Buenzli on GitHub was a lurking = bug in the 4.01.0 and libffi integration (which is used by Ctypes). =  This isn't a critical blocker, so I expect we'll either switch to = stub generation or figure out the libffi bug when we get to it in the = future.

So: dropping 4.00.1 compatibility in Mirage 1.1.x it is.

-anil

On 14 Jan 2014, at 17:00, Jon Ludlam <jjl25@cam.ac.uk> = wrote:

> Fine by me. Who needs 4.00.1 when you have opam? :-)
>
> Jon
>
> Sent from my iPad
>
>> On 14 Jan 2014, at 15:57, Anil Madhavapeddy <anil@recoil.org> wrote:
>>
>> We currently support both OCaml 4.00.1 and 4.01.0.  I've = got two reasons to propose dropping OCaml 4.00.1 support:
>>
>> - Thomas' extremely useful combinator support uses fancy GADTs = that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190
>>
>> - I'm refactoring the runtime library to install = cross-compilation headers (see James Bielman's request a while back), = and it's extra work to port both runtimes.
>>
>> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy = to drop 4.00.1 support unless anyone wants to speak up against.
>>
>> cheers,
>> Anil
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.or= g
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.or= g
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.or= g
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel


--
Dave Scott

= --Apple-Mail=_ED564D59-4499-4F32-890C-632420BEF96C-- --===============0424080215328615262== 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 --===============0424080215328615262==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jan 15 14:16:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 14:16: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 1W3RGy-00062I-4g; Wed, 15 Jan 2014 14:16:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3RGu-00061W-H4 for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 14:16:46 +0000 Received: from [85.158.143.35:2645] by server-2.bemta-4.messagelabs.com id 3A/7D-11386-B4896D25; Wed, 15 Jan 2014 14:16:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-21.messagelabs.com!1389795402!9234222!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 2442 invoked from network); 15 Jan 2014 14:16:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-15.tower-21.messagelabs.com with SMTP; 15 Jan 2014 14:16:42 -0000 Received: (qmail 4439 invoked by uid 634); 15 Jan 2014 14:16:41 -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, 15 Jan 2014 14:16:40 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 15 Jan 2014 14:16:37 +0000 Message-Id: <20367F3A-0A1E-45A0-89AA-CED3D8DA3B4B@recoil.org> References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@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] Drop OCaml 4.00.1 support? 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="===============0424080215328615262==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0424080215328615262== Content-Type: multipart/alternative; boundary="Apple-Mail=_ED564D59-4499-4F32-890C-632420BEF96C" --Apple-Mail=_ED564D59-4499-4F32-890C-632420BEF96C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I've merged the combinator branch, but Jeremy Yallop and I also had a = quick look at why it was broken. It turns out to be because of the use of record disambiguation (a new = feature in 4.01.0), and I've sent a pull request that fixes it here: https://github.com/mirage/mirage/pull/194 It does make the code slightly less elegant though. Thomas, do you mind = if we apply this one for now? -anil On 15 Jan 2014, at 11:14, David Scott wrote: > Dropping 4.00.1 is also fine by me! >=20 > On Wednesday, January 15, 2014, Anil Madhavapeddy wrote: > Great; this is only for the metaprogramming layer (the Mirage = command-line tool), so we'll continue to test the libraries themselves = for now. >=20 > The only other point raised by Daniel Buenzli on GitHub was a lurking = bug in the 4.01.0 and libffi integration (which is used by Ctypes). = This isn't a critical blocker, so I expect we'll either switch to stub = generation or figure out the libffi bug when we get to it in the future. >=20 > So: dropping 4.00.1 compatibility in Mirage 1.1.x it is. >=20 > -anil >=20 > On 14 Jan 2014, at 17:00, Jon Ludlam wrote: >=20 > > Fine by me. Who needs 4.00.1 when you have opam? :-) > > > > Jon > > > > Sent from my iPad > > > >> On 14 Jan 2014, at 15:57, Anil Madhavapeddy = wrote: > >> > >> We currently support both OCaml 4.00.1 and 4.01.0. I've got two = reasons to propose dropping OCaml 4.00.1 support: > >> > >> - Thomas' extremely useful combinator support uses fancy GADTs that = don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 > >> > >> - I'm refactoring the runtime library to install cross-compilation = headers (see James Bielman's request a while back), and it's extra work = to port both runtimes. > >> > >> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to = drop 4.00.1 support unless anyone wants to speak up against. > >> > >> cheers, > >> 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 > > >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 >=20 > --=20 > Dave Scott --Apple-Mail=_ED564D59-4499-4F32-890C-632420BEF96C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I've = merged the combinator branch, but Jeremy Yallop and I also had a quick = look at why it was broken.

It turns out to be because = of the use of record disambiguation (a new feature in 4.01.0), and I've = sent a pull request that fixes it here:

It does make the code = slightly less elegant though. Thomas, do you mind if we apply this one = for now?

-anil

On 15 = Jan 2014, at 11:14, David Scott <scott.dj@gmail.com> = wrote:

Dropping 4.00.1 is also fine by me!

On Wednesday, = January 15, 2014, Anil Madhavapeddy wrote:
Great; this is only for the metaprogramming = layer (the Mirage command-line tool), so we'll continue to test the = libraries themselves for now.

The only other point raised by Daniel Buenzli on GitHub was a lurking = bug in the 4.01.0 and libffi integration (which is used by Ctypes). =  This isn't a critical blocker, so I expect we'll either switch to = stub generation or figure out the libffi bug when we get to it in the = future.

So: dropping 4.00.1 compatibility in Mirage 1.1.x it is.

-anil

On 14 Jan 2014, at 17:00, Jon Ludlam <jjl25@cam.ac.uk> = wrote:

> Fine by me. Who needs 4.00.1 when you have opam? :-)
>
> Jon
>
> Sent from my iPad
>
>> On 14 Jan 2014, at 15:57, Anil Madhavapeddy <anil@recoil.org> wrote:
>>
>> We currently support both OCaml 4.00.1 and 4.01.0.  I've = got two reasons to propose dropping OCaml 4.00.1 support:
>>
>> - Thomas' extremely useful combinator support uses fancy GADTs = that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190
>>
>> - I'm refactoring the runtime library to install = cross-compilation headers (see James Bielman's request a while back), = and it's extra work to port both runtimes.
>>
>> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy = to drop 4.00.1 support unless anyone wants to speak up against.
>>
>> cheers,
>> Anil
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.or= g
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.or= g
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.or= g
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel


--
Dave Scott

= --Apple-Mail=_ED564D59-4499-4F32-890C-632420BEF96C-- --===============0424080215328615262== 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 --===============0424080215328615262==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jan 15 14:22:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 14:22: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 1W3RMi-00079M-7i; Wed, 15 Jan 2014 14:22:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3RMf-00079C-SG for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 14:22:42 +0000 Received: from [85.158.139.211:50513] by server-2.bemta-5.messagelabs.com id B8/DA-29392-1B996D25; Wed, 15 Jan 2014 14:22:41 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1389795759!7218583!1 X-Originating-IP: [209.85.212.181] 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 26029 invoked from network); 15 Jan 2014 14:22:39 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 14:22:39 -0000 Received: by mail-wi0-f181.google.com with SMTP id hi8so773758wib.14 for ; Wed, 15 Jan 2014 06:22:39 -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 :message-id:references:to; bh=FGQQHSjaCi6WphGTxcWs64QyHk6mHruUE/2nw/iOAPc=; b=0IH3QSFTkOslUVEpf2Rv39UDU5E5DxzgqTL4ocvCHCPf7vmSTiOkvPtqzNfmzeKEp+ vRrrZ2fn3E+00MkFdcqpVWc7xNKg7tQEhD6CclzPhlBFLADJU9M8pXwFQ9Vw0I4ak2So 4Pwa9PO9JEgkxi/CYxQza81MquQCM1XqRKaXSQoJ0P7V6acdOT5dAnsWAFCNygJvgjjv B7v6sVCNfvj6F768ULujIFyLALA/4exEiSug0JZVyD++j/xketbLTlS4rlV9GR2QQ8mN saMUvBBZpioobDCpaJx6UXo/xVM3nDHBt5U8Osf7zJZA57rsubloxMLiW7EtosWaxgsD 0YqQ== X-Received: by 10.194.171.34 with SMTP id ar2mr2301378wjc.81.1389795757302; Wed, 15 Jan 2014 06:22:37 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id dh8sm6859552wib.4.2014.01.15.06.22.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 06:22:35 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: <20367F3A-0A1E-45A0-89AA-CED3D8DA3B4B@recoil.org> Date: Wed, 15 Jan 2014 14:22:37 +0000 Message-Id: <86B5013C-2AF9-4316-8A7F-E653CDD5ADAC@gazagnaire.org> References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@recoil.org> <20367F3A-0A1E-45A0-89AA-CED3D8DA3B4B@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1827) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Drop OCaml 4.00.1 support? 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="===============7769664678219603264==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7769664678219603264== Content-Type: multipart/alternative; boundary="Apple-Mail=_07995A74-A418-41F3-9DB6-15DC71FE3BCF" --Apple-Mail=_07995A74-A418-41F3-9DB6-15DC71FE3BCF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 > It does make the code slightly less elegant though. Thomas, do you = mind if we apply this one for now? sure! >=20 > -anil >=20 > On 15 Jan 2014, at 11:14, David Scott wrote: >=20 >> Dropping 4.00.1 is also fine by me! >>=20 >> On Wednesday, January 15, 2014, Anil Madhavapeddy wrote: >> Great; this is only for the metaprogramming layer (the Mirage = command-line tool), so we'll continue to test the libraries themselves = for now. >>=20 >> The only other point raised by Daniel Buenzli on GitHub was a lurking = bug in the 4.01.0 and libffi integration (which is used by Ctypes). = This isn't a critical blocker, so I expect we'll either switch to stub = generation or figure out the libffi bug when we get to it in the future. >>=20 >> So: dropping 4.00.1 compatibility in Mirage 1.1.x it is. >>=20 >> -anil >>=20 >> On 14 Jan 2014, at 17:00, Jon Ludlam wrote: >>=20 >> > Fine by me. Who needs 4.00.1 when you have opam? :-) >> > >> > Jon >> > >> > Sent from my iPad >> > >> >> On 14 Jan 2014, at 15:57, Anil Madhavapeddy = wrote: >> >> >> >> We currently support both OCaml 4.00.1 and 4.01.0. I've got two = reasons to propose dropping OCaml 4.00.1 support: >> >> >> >> - Thomas' extremely useful combinator support uses fancy GADTs = that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 >> >> >> >> - I'm refactoring the runtime library to install cross-compilation = headers (see James Bielman's request a while back), and it's extra work = to port both runtimes. >> >> >> >> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to = drop 4.00.1 support unless anyone wants to speak up against. >> >> >> >> cheers, >> >> 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 >> > >>=20 >>=20 >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=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=_07995A74-A418-41F3-9DB6-15DC71FE3BCF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
It does make the code = slightly less elegant though. Thomas, do you mind if we apply this one = for = now?

sure!


-anil

On = 15 Jan 2014, at 11:14, David Scott <scott.dj@gmail.com> = wrote:

Dropping 4.00.1 is also fine by me!

On Wednesday, = January 15, 2014, Anil Madhavapeddy wrote:
Great; this is only for the metaprogramming = layer (the Mirage command-line tool), so we'll continue to test the = libraries themselves for now.

The only other point raised by Daniel Buenzli on GitHub was a lurking = bug in the 4.01.0 and libffi integration (which is used by Ctypes). =  This isn't a critical blocker, so I expect we'll either switch to = stub generation or figure out the libffi bug when we get to it in the = future.

So: dropping 4.00.1 compatibility in Mirage 1.1.x it is.

-anil

On 14 Jan 2014, at 17:00, Jon Ludlam <jjl25@cam.ac.uk> = wrote:

> Fine by me. Who needs 4.00.1 when you have opam? :-)
>
> Jon
>
> Sent from my iPad
>
>> On 14 Jan 2014, at 15:57, Anil Madhavapeddy <anil@recoil.org> wrote:
>>
>> We currently support both OCaml 4.00.1 and 4.01.0.  I've = got two reasons to propose dropping OCaml 4.00.1 support:
>>
>> - Thomas' extremely useful combinator support uses fancy GADTs = that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190
>>
>> - I'm refactoring the runtime library to install = cross-compilation headers (see James Bielman's request a while back), = and it's extra work to port both runtimes.
>>
>> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy = to drop 4.00.1 support unless anyone wants to speak up against.
>>
>> cheers,
>> Anil
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.or= g
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.or= g
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.or= g
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=_07995A74-A418-41F3-9DB6-15DC71FE3BCF-- --===============7769664678219603264== 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 --===============7769664678219603264==-- From mirageos-devel-bounces@lists.xenproject.org Wed Jan 15 14:22:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 15 Jan 2014 14:22: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 1W3RMi-00079M-7i; Wed, 15 Jan 2014 14:22:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3RMf-00079C-SG for mirageos-devel@lists.xenproject.org; Wed, 15 Jan 2014 14:22:42 +0000 Received: from [85.158.139.211:50513] by server-2.bemta-5.messagelabs.com id B8/DA-29392-1B996D25; Wed, 15 Jan 2014 14:22:41 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-206.messagelabs.com!1389795759!7218583!1 X-Originating-IP: [209.85.212.181] 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 26029 invoked from network); 15 Jan 2014 14:22:39 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-7.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Jan 2014 14:22:39 -0000 Received: by mail-wi0-f181.google.com with SMTP id hi8so773758wib.14 for ; Wed, 15 Jan 2014 06:22:39 -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 :message-id:references:to; bh=FGQQHSjaCi6WphGTxcWs64QyHk6mHruUE/2nw/iOAPc=; b=0IH3QSFTkOslUVEpf2Rv39UDU5E5DxzgqTL4ocvCHCPf7vmSTiOkvPtqzNfmzeKEp+ vRrrZ2fn3E+00MkFdcqpVWc7xNKg7tQEhD6CclzPhlBFLADJU9M8pXwFQ9Vw0I4ak2So 4Pwa9PO9JEgkxi/CYxQza81MquQCM1XqRKaXSQoJ0P7V6acdOT5dAnsWAFCNygJvgjjv B7v6sVCNfvj6F768ULujIFyLALA/4exEiSug0JZVyD++j/xketbLTlS4rlV9GR2QQ8mN saMUvBBZpioobDCpaJx6UXo/xVM3nDHBt5U8Osf7zJZA57rsubloxMLiW7EtosWaxgsD 0YqQ== X-Received: by 10.194.171.34 with SMTP id ar2mr2301378wjc.81.1389795757302; Wed, 15 Jan 2014 06:22:37 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id dh8sm6859552wib.4.2014.01.15.06.22.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 Jan 2014 06:22:35 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: <20367F3A-0A1E-45A0-89AA-CED3D8DA3B4B@recoil.org> Date: Wed, 15 Jan 2014 14:22:37 +0000 Message-Id: <86B5013C-2AF9-4316-8A7F-E653CDD5ADAC@gazagnaire.org> References: <198ECBCC-21F4-45F2-A599-C9415A867BBF@recoil.org> <42EB9EBA-284D-45BD-BB32-B6CD079B11CE@recoil.org> <20367F3A-0A1E-45A0-89AA-CED3D8DA3B4B@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1827) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Drop OCaml 4.00.1 support? 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="===============7769664678219603264==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7769664678219603264== Content-Type: multipart/alternative; boundary="Apple-Mail=_07995A74-A418-41F3-9DB6-15DC71FE3BCF" --Apple-Mail=_07995A74-A418-41F3-9DB6-15DC71FE3BCF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 > It does make the code slightly less elegant though. Thomas, do you = mind if we apply this one for now? sure! >=20 > -anil >=20 > On 15 Jan 2014, at 11:14, David Scott wrote: >=20 >> Dropping 4.00.1 is also fine by me! >>=20 >> On Wednesday, January 15, 2014, Anil Madhavapeddy wrote: >> Great; this is only for the metaprogramming layer (the Mirage = command-line tool), so we'll continue to test the libraries themselves = for now. >>=20 >> The only other point raised by Daniel Buenzli on GitHub was a lurking = bug in the 4.01.0 and libffi integration (which is used by Ctypes). = This isn't a critical blocker, so I expect we'll either switch to stub = generation or figure out the libffi bug when we get to it in the future. >>=20 >> So: dropping 4.00.1 compatibility in Mirage 1.1.x it is. >>=20 >> -anil >>=20 >> On 14 Jan 2014, at 17:00, Jon Ludlam wrote: >>=20 >> > Fine by me. Who needs 4.00.1 when you have opam? :-) >> > >> > Jon >> > >> > Sent from my iPad >> > >> >> On 14 Jan 2014, at 15:57, Anil Madhavapeddy = wrote: >> >> >> >> We currently support both OCaml 4.00.1 and 4.01.0. I've got two = reasons to propose dropping OCaml 4.00.1 support: >> >> >> >> - Thomas' extremely useful combinator support uses fancy GADTs = that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190 >> >> >> >> - I'm refactoring the runtime library to install cross-compilation = headers (see James Bielman's request a while back), and it's extra work = to port both runtimes. >> >> >> >> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy to = drop 4.00.1 support unless anyone wants to speak up against. >> >> >> >> cheers, >> >> 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 >> > >>=20 >>=20 >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=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=_07995A74-A418-41F3-9DB6-15DC71FE3BCF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
It does make the code = slightly less elegant though. Thomas, do you mind if we apply this one = for = now?

sure!


-anil

On = 15 Jan 2014, at 11:14, David Scott <scott.dj@gmail.com> = wrote:

Dropping 4.00.1 is also fine by me!

On Wednesday, = January 15, 2014, Anil Madhavapeddy wrote:
Great; this is only for the metaprogramming = layer (the Mirage command-line tool), so we'll continue to test the = libraries themselves for now.

The only other point raised by Daniel Buenzli on GitHub was a lurking = bug in the 4.01.0 and libffi integration (which is used by Ctypes). =  This isn't a critical blocker, so I expect we'll either switch to = stub generation or figure out the libffi bug when we get to it in the = future.

So: dropping 4.00.1 compatibility in Mirage 1.1.x it is.

-anil

On 14 Jan 2014, at 17:00, Jon Ludlam <jjl25@cam.ac.uk> = wrote:

> Fine by me. Who needs 4.00.1 when you have opam? :-)
>
> Jon
>
> Sent from my iPad
>
>> On 14 Jan 2014, at 15:57, Anil Madhavapeddy <anil@recoil.org> wrote:
>>
>> We currently support both OCaml 4.00.1 and 4.01.0.  I've = got two reasons to propose dropping OCaml 4.00.1 support:
>>
>> - Thomas' extremely useful combinator support uses fancy GADTs = that don't work in 4.00.1: https://github.com/mirage/mirage/pull/190
>>
>> - I'm refactoring the runtime library to install = cross-compilation headers (see James Bielman's request a while back), = and it's extra work to port both runtimes.
>>
>> Given the easy availability of OCaml 4.01.0 PPAs now, I'm happy = to drop 4.00.1 support unless anyone wants to speak up against.
>>
>> cheers,
>> Anil
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@lists.xenproject.or= g
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.or= g
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject.or= g
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=_07995A74-A418-41F3-9DB6-15DC71FE3BCF-- --===============7769664678219603264== 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 --===============7769664678219603264==-- From mirageos-devel-bounces@lists.xenproject.org Thu Jan 16 21:24:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 16 Jan 2014 21:24: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 1W3uQL-0004d7-Su; Thu, 16 Jan 2014 21:24:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3uQJ-0004d2-Ra for mirageos-devel@lists.xenproject.org; Thu, 16 Jan 2014 21:24:23 +0000 Received: from [85.158.137.68:16582] by server-11.bemta-3.messagelabs.com id ED/86-19379-60E48D25; Thu, 16 Jan 2014 21:24:22 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1389907462!9591844!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 19649 invoked from network); 16 Jan 2014 21:24:22 -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; 16 Jan 2014 21:24:22 -0000 Received: (qmail 7841 invoked by uid 634); 16 Jan 2014 21:24:21 -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, 16 Jan 2014 21:24:21 +0000 From: Anil Madhavapeddy Message-Id: <3CF3D06F-9120-45A7-B460-E9A00B7AF256@recoil.org> Date: Thu, 16 Jan 2014 21:24:18 +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] heads up: a Unix dependency snuck in on Uri, to be fixed tomorrow 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 sexp'ed up Uri, and there's a tiny Unix dependency in sexplib that's causing anything that uses Uri to fail. I've sent in the patch upstream [1], but I'll put in a workaround tomorrow morning if there's no quick resolution. For now, you can pin back to the Uri 1.3.12 to avoid the problem if you're building a Xen website. [1] https://github.com/janestreet/sexplib/pull/4 -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 Thu Jan 16 21:24:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 16 Jan 2014 21:24: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 1W3uQL-0004d7-Su; Thu, 16 Jan 2014 21:24:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W3uQJ-0004d2-Ra for mirageos-devel@lists.xenproject.org; Thu, 16 Jan 2014 21:24:23 +0000 Received: from [85.158.137.68:16582] by server-11.bemta-3.messagelabs.com id ED/86-19379-60E48D25; Thu, 16 Jan 2014 21:24:22 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1389907462!9591844!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 19649 invoked from network); 16 Jan 2014 21:24:22 -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; 16 Jan 2014 21:24:22 -0000 Received: (qmail 7841 invoked by uid 634); 16 Jan 2014 21:24:21 -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, 16 Jan 2014 21:24:21 +0000 From: Anil Madhavapeddy Message-Id: <3CF3D06F-9120-45A7-B460-E9A00B7AF256@recoil.org> Date: Thu, 16 Jan 2014 21:24:18 +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] heads up: a Unix dependency snuck in on Uri, to be fixed tomorrow 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 sexp'ed up Uri, and there's a tiny Unix dependency in sexplib that's causing anything that uses Uri to fail. I've sent in the patch upstream [1], but I'll put in a workaround tomorrow morning if there's no quick resolution. For now, you can pin back to the Uri 1.3.12 to avoid the problem if you're building a Xen website. [1] https://github.com/janestreet/sexplib/pull/4 -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 Fri Jan 17 17:15:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 17:15: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 1W4D1C-0006X9-CA; Fri, 17 Jan 2014 17:15:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4D1B-0006X3-Ha for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 17:15:41 +0000 Received: from [85.158.137.68:5983] by server-11.bemta-3.messagelabs.com id 1D/32-19379-C3569D25; Fri, 17 Jan 2014 17:15:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1389978939!9819187!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 30704 invoked from network); 17 Jan 2014 17:15:39 -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; 17 Jan 2014 17:15:39 -0000 Received: (qmail 29361 invoked by uid 634); 17 Jan 2014 17:15:38 -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, 17 Jan 2014 17:15:38 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <3CF3D06F-9120-45A7-B460-E9A00B7AF256@recoil.org> Date: Fri, 17 Jan 2014 17:15:35 +0000 Message-Id: <0BC30F95-D058-459B-84B3-EDCF72A36CB5@recoil.org> References: <3CF3D06F-9120-45A7-B460-E9A00B7AF256@recoil.org> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: Re: [MirageOS-devel] heads up: a Unix dependency snuck in on Uri, to be fixed tomorrow 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 And now fixed in OPAM, so go back to sexp'ing as usual! -anil On 16 Jan 2014, at 21:24, Anil Madhavapeddy wrote: > I sexp'ed up Uri, and there's a tiny Unix dependency in sexplib that's causing anything that uses Uri to fail. I've sent in the patch upstream [1], but I'll put in a workaround tomorrow morning if there's no quick resolution. > > For now, you can pin back to the Uri 1.3.12 to avoid the problem if you're building a Xen website. > > [1] https://github.com/janestreet/sexplib/pull/4 > > -a > _______________________________________________ > 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 Fri Jan 17 17:15:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 17:15: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 1W4D1C-0006X9-CA; Fri, 17 Jan 2014 17:15:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4D1B-0006X3-Ha for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 17:15:41 +0000 Received: from [85.158.137.68:5983] by server-11.bemta-3.messagelabs.com id 1D/32-19379-C3569D25; Fri, 17 Jan 2014 17:15:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1389978939!9819187!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 30704 invoked from network); 17 Jan 2014 17:15:39 -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; 17 Jan 2014 17:15:39 -0000 Received: (qmail 29361 invoked by uid 634); 17 Jan 2014 17:15:38 -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, 17 Jan 2014 17:15:38 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <3CF3D06F-9120-45A7-B460-E9A00B7AF256@recoil.org> Date: Fri, 17 Jan 2014 17:15:35 +0000 Message-Id: <0BC30F95-D058-459B-84B3-EDCF72A36CB5@recoil.org> References: <3CF3D06F-9120-45A7-B460-E9A00B7AF256@recoil.org> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: Re: [MirageOS-devel] heads up: a Unix dependency snuck in on Uri, to be fixed tomorrow 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 And now fixed in OPAM, so go back to sexp'ing as usual! -anil On 16 Jan 2014, at 21:24, Anil Madhavapeddy wrote: > I sexp'ed up Uri, and there's a tiny Unix dependency in sexplib that's causing anything that uses Uri to fail. I've sent in the patch upstream [1], but I'll put in a workaround tomorrow morning if there's no quick resolution. > > For now, you can pin back to the Uri 1.3.12 to avoid the problem if you're building a Xen website. > > [1] https://github.com/janestreet/sexplib/pull/4 > > -a > _______________________________________________ > 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 Fri Jan 17 20:37:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 20:37: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 1W4GAX-00036u-Js; Fri, 17 Jan 2014 20:37:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4GAW-00036p-5m for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 20:37:32 +0000 Received: from [193.109.254.147:23515] by server-3.bemta-14.messagelabs.com id 56/2C-11000-B8499D25; Fri, 17 Jan 2014 20:37:31 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-7.tower-27.messagelabs.com!1389991050!11630962!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 11577 invoked from network); 17 Jan 2014 20:37:30 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-7.tower-27.messagelabs.com with SMTP; 17 Jan 2014 20:37:30 -0000 Received: (qmail 2360 invoked from network); 17 Jan 2014 20:32:45 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 17 Jan 2014 20:32:45 -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 00760-09 for ; Fri, 17 Jan 2014 20:32:44 +0000 (GMT) Received: (qmail 2340 invoked by uid 599); 17 Jan 2014 20:32:44 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 17 Jan 2014 20:32:44 +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 1W4G5z-00051q-Gi for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 20:32:51 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Date: Fri, 17 Jan 2014 20:32:50 +0000 Thread-Topic: has anyone successfully used fat and xen together? Thread-Index: Ac8Tw0qFdljm6sekRWiFcCUMfdu6gg== Message-ID: 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 Subject: [MirageOS-devel] has anyone successfully used fat and xen together? 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 if so, how? :) specifically-- configuring with `MODE=xen` and `FS_MODE=fat` causes installation of `fat-filesystem` and thus `mirage-block-unix`. when i then execute a build i end up with: ``` mort-www + ocamlfind ocamlopt -g -linkpkg -dontlink unix -output-obj -package mirage.types-xen -package mirage-http-xen -package mirage-console-xen -package mirage-block-xen.front -package mirage-block-unix -package io-page-xen -package io-page-unix -package fat-filesystem -package cowabloga -package cow.syntax -package lwt.syntax -syntax camlp4o site_config.cmx posts.cmx page.cmx blog.cmx courses.cmx papers.cmx site.cmx server.cmx main.cmx -o main.native.o mort-www findlib: [WARNING] Interface block.cmi occurs in several directories: /home/mort/.opam/mirage-xen/lib/mirage-block-unix, /home/mort/.opam/mirage-xen/lib/mirage-block-xen mort-www findlib: [WARNING] Interface io_page.cmi occurs in several directories: /home/mort/.opam/mirage-xen/lib/io-page-unix, /home/mort/.opam/mirage-xen/lib/io-page-xen mort-www File "_none_", line 1: mort-www Error: No implementations provided for the following modules: mort-www Unix referenced from /home/mort/.opam/mirage-xen/lib/lwt/lwt-unix.cmxa(Lwt_engine), mort-www /home/mort/.opam/mirage-xen/lib/lwt/lwt-unix.cmxa(Lwt_unix), mort-www /home/mort/.opam/mirage-xen/lib/mirage-block-unix/mirage_block_unix.cmxa(Block) mort-www Command exited with code 2. mort-www make[1]: Leaving directory `/home/mort/mirage/mort-www/src' [ERROR] The command "make build" exited with code 2. ``` i'm using thomas' new combinator branch of mirage. this is a bit of a blocker for me -- my website is on the large side to be crunched (150MB .ml file anyone?) so i'd hoped that FAT would save me... i see the same issue with mirage-www too, and the use of crunch for the live site (afaics) suggests to me that fat might not be supported. (and yes, for the time being i will store the relevant bits of content out of the site and href them from the site itself, but that seems like a bit of a cop-out given we're intending to demo this at fosdem in 2 weeks... :) -- 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 Jan 17 20:37:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 20:37: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 1W4GAX-00036u-Js; Fri, 17 Jan 2014 20:37:33 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4GAW-00036p-5m for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 20:37:32 +0000 Received: from [193.109.254.147:23515] by server-3.bemta-14.messagelabs.com id 56/2C-11000-B8499D25; Fri, 17 Jan 2014 20:37:31 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-7.tower-27.messagelabs.com!1389991050!11630962!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 11577 invoked from network); 17 Jan 2014 20:37:30 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-7.tower-27.messagelabs.com with SMTP; 17 Jan 2014 20:37:30 -0000 Received: (qmail 2360 invoked from network); 17 Jan 2014 20:32:45 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 17 Jan 2014 20:32:45 -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 00760-09 for ; Fri, 17 Jan 2014 20:32:44 +0000 (GMT) Received: (qmail 2340 invoked by uid 599); 17 Jan 2014 20:32:44 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 17 Jan 2014 20:32:44 +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 1W4G5z-00051q-Gi for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 20:32:51 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Date: Fri, 17 Jan 2014 20:32:50 +0000 Thread-Topic: has anyone successfully used fat and xen together? Thread-Index: Ac8Tw0qFdljm6sekRWiFcCUMfdu6gg== Message-ID: 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 Subject: [MirageOS-devel] has anyone successfully used fat and xen together? 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 if so, how? :) specifically-- configuring with `MODE=xen` and `FS_MODE=fat` causes installation of `fat-filesystem` and thus `mirage-block-unix`. when i then execute a build i end up with: ``` mort-www + ocamlfind ocamlopt -g -linkpkg -dontlink unix -output-obj -package mirage.types-xen -package mirage-http-xen -package mirage-console-xen -package mirage-block-xen.front -package mirage-block-unix -package io-page-xen -package io-page-unix -package fat-filesystem -package cowabloga -package cow.syntax -package lwt.syntax -syntax camlp4o site_config.cmx posts.cmx page.cmx blog.cmx courses.cmx papers.cmx site.cmx server.cmx main.cmx -o main.native.o mort-www findlib: [WARNING] Interface block.cmi occurs in several directories: /home/mort/.opam/mirage-xen/lib/mirage-block-unix, /home/mort/.opam/mirage-xen/lib/mirage-block-xen mort-www findlib: [WARNING] Interface io_page.cmi occurs in several directories: /home/mort/.opam/mirage-xen/lib/io-page-unix, /home/mort/.opam/mirage-xen/lib/io-page-xen mort-www File "_none_", line 1: mort-www Error: No implementations provided for the following modules: mort-www Unix referenced from /home/mort/.opam/mirage-xen/lib/lwt/lwt-unix.cmxa(Lwt_engine), mort-www /home/mort/.opam/mirage-xen/lib/lwt/lwt-unix.cmxa(Lwt_unix), mort-www /home/mort/.opam/mirage-xen/lib/mirage-block-unix/mirage_block_unix.cmxa(Block) mort-www Command exited with code 2. mort-www make[1]: Leaving directory `/home/mort/mirage/mort-www/src' [ERROR] The command "make build" exited with code 2. ``` i'm using thomas' new combinator branch of mirage. this is a bit of a blocker for me -- my website is on the large side to be crunched (150MB .ml file anyone?) so i'd hoped that FAT would save me... i see the same issue with mirage-www too, and the use of crunch for the live site (afaics) suggests to me that fat might not be supported. (and yes, for the time being i will store the relevant bits of content out of the site and href them from the site itself, but that seems like a bit of a cop-out given we're intending to demo this at fosdem in 2 weeks... :) -- 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 Jan 17 21:01:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 21:01: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 1W4GXJ-0004Ui-GM; Fri, 17 Jan 2014 21:01:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4GXH-0004Ud-Ob for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 21:01:04 +0000 Received: from [85.158.143.35:5186] by server-1.bemta-4.messagelabs.com id 1F/AB-02132-E0A99D25; Fri, 17 Jan 2014 21:01:02 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1389992459!12491585!1 X-Originating-IP: [209.85.192.171] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20514 invoked from network); 17 Jan 2014 21:01:00 -0000 Received: from mail-pd0-f171.google.com (HELO mail-pd0-f171.google.com) (209.85.192.171) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2014 21:01:00 -0000 Received: by mail-pd0-f171.google.com with SMTP id g10so3706928pdj.16 for ; Fri, 17 Jan 2014 13:00:58 -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=WdiRTMSyTLCHCve1tlWiP/3KB8CpsrdG45+S7sZ18bM=; b=OEe56yf3XqktEwMWQjHsoiYqrv64nHbWwtmH0NHdt2e8uEyjfy9W8EA4iL+M36cQet RLU45amWXlL+CW8I9jHc7olNRWKnxnsqVmqtuifwOEkpioIP8JiWpLr2N4tbUvPyv5VV eGKmD0z3XTtDpOKd33jXyfrSCpHjgkjknvNbGxE+DnEPUQPPqS3AF8kIeBof2y+paJi5 24kIr+nJnqNZQPjbDBBGE+zYY3t/FKfkFUX6f6XL3o874f6+9jSQTYd/f/tpgaAj5hOz /AXCv/YJ3VxuLBA2DNeuFpDuq2/m2kdr4TOvHKerobXebZKum+CBnkiDccHoufAbiRcw WJdA== MIME-Version: 1.0 X-Received: by 10.68.202.8 with SMTP id ke8mr4556602pbc.86.1389992458836; Fri, 17 Jan 2014 13:00:58 -0800 (PST) Received: by 10.70.61.136 with HTTP; Fri, 17 Jan 2014 13:00:58 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Jan 2014 21:00:58 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] has anyone successfully used fat and xen together? 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="===============5782543242108387364==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5782543242108387364== Content-Type: multipart/alternative; boundary=047d7b15a693bfe15e04f030d694 --047d7b15a693bfe15e04f030d694 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jan 17, 2014 at 8:32 PM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > if so, how? :) > I have, but before all the recent tooling improvements. > > specifically-- configuring with `MODE=xen` and `FS_MODE=fat` causes > installation of `fat-filesystem` and thus `mirage-block-unix`. when i then > execute a build i end up with: > > ``` > mort-www + ocamlfind ocamlopt -g -linkpkg -dontlink unix -output-obj > -package mirage.types-xen -package mirage-http-xen -package > mirage-console-xen -package mirage-block-xen.front -package > mirage-block-unix -package io-page-xen -package io-page-unix -package > fat-filesystem -package cowabloga -package cow.syntax -package lwt.syntax > -syntax camlp4o site_config.cmx posts.cmx page.cmx blog.cmx courses.cmx > papers.cmx site.cmx server.cmx main.cmx -o main.native.o > mort-www findlib: [WARNING] Interface block.cmi occurs in several > directories: /home/mort/.opam/mirage-xen/lib/mirage-block-unix, > /home/mort/.opam/mirage-xen/lib/mirage-block-xen > mort-www findlib: [WARNING] Interface io_page.cmi occurs in several > directories: /home/mort/.opam/mirage-xen/lib/io-page-unix, > /home/mort/.opam/mirage-xen/lib/io-page-xen > mort-www File "_none_", line 1: > mort-www Error: No implementations provided for the following modules: > mort-www Unix referenced from > /home/mort/.opam/mirage-xen/lib/lwt/lwt-unix.cmxa(Lwt_engine), > mort-www > /home/mort/.opam/mirage-xen/lib/lwt/lwt-unix.cmxa(Lwt_unix), > mort-www > /home/mort/.opam/mirage-xen/lib/mirage-block-unix/mirage_block_unix.cmxa(Block) > Referencing Unix is not going to work :) I checked the META file for fat-filesystem, it depends on: ``` requires = "cstruct re re.str mirage-types lwt" ``` I think we need to track down where mirage-block-unix is coming from. A second observation is that I recently merged Thomas' io-page improvement, so you can now just use "io-page" instead of "io-page-xen". The old package should work though; I don't think this is related to your problem. > mort-www Command exited with code 2. > mort-www make[1]: Leaving directory `/home/mort/mirage/mort-www/src' > [ERROR] The command "make build" exited with code 2. > ``` > > i'm using thomas' new combinator branch of mirage. > > this is a bit of a blocker for me -- my website is on the large side to be > crunched (150MB .ml file anyone?) so i'd hoped that FAT would save me... > > i see the same issue with mirage-www too, and the use of crunch for the > live site (afaics) suggests to me that fat might not be supported. > > (and yes, for the time being i will store the relevant bits of content out > of the site and href them from the site itself, but that seems like a bit > of a cop-out given we're intending to demo this at fosdem in 2 weeks... :) > > -- > 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 > -- Dave Scott --047d7b15a693bfe15e04f030d694 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Fri, Jan 17, 2014 at 8:32 PM, Richard Mortier <Richard.M= ortier@nottingham.ac.uk> wrote:
if so, how? :)

I have,= but before all the recent tooling improvements.
=A0

specifically-- configuring with `MODE=3Dxen` and `FS_MODE=3Dfat` causes ins= tallation of `fat-filesystem` and thus `mirage-block-unix`. when i then exe= cute a build i end up with:

```
mort-www =A0 =A0 + ocamlfind ocamlopt -g -linkpkg -dontlink unix -output-ob= j -package mirage.types-xen -package mirage-http-xen -package mirage-consol= e-xen -package mirage-block-xen.front -package mirage-block-unix -package i= o-page-xen -package io-page-unix -package fat-filesystem -package cowabloga= -package cow.syntax -package lwt.syntax -syntax camlp4o site_config.cmx po= sts.cmx page.cmx blog.cmx courses.cmx papers.cmx site.cmx server.cmx main.c= mx -o main.native.o
mort-www =A0 =A0 findlib: [WARNING] Interface block.cmi occurs in several d= irectories: /home/mort/.opam/mirage-xen/lib/mirage-block-unix, /home/mort/.= opam/mirage-xen/lib/mirage-block-xen
mort-www =A0 =A0 findlib: [WARNING] Interface io_page.cmi occurs in several= directories: /home/mort/.opam/mirage-xen/lib/io-page-unix, /home/mort/.opa= m/mirage-xen/lib/io-page-xen
mort-www =A0 =A0 File "_none_", line 1:
mort-www =A0 =A0 Error: No implementations provided for the following modul= es:
mort-www =A0 =A0 =A0 =A0 =A0 =A0 =A0Unix referenced from /home/mort/.opam/m= irage-xen/lib/lwt/lwt-unix.cmxa(Lwt_engine),
mort-www =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/home/mort/.opam/mirage-xen/lib/lwt= /lwt-unix.cmxa(Lwt_unix),
mort-www =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/home/mort/.opam/mirage-xen/lib/mir= age-block-unix/mirage_block_unix.cmxa(Block)

Referencing Unix is not going to work :)

I c= hecked the META file for fat-filesystem, it depends on:
```
requires =3D "cstruct re re.str mirage-types l= wt"
```
I think we need to track down where = mirage-block-unix is coming from.

A second observa= tion is that I recently merged Thomas' io-page improvement, so you can = now just use "io-page" instead of "io-page-xen". The ol= d package should work though; I don't think this is related to your pro= blem.
=A0
mort-www =A0 =A0 Command exited with code 2.
mort-www =A0 =A0 make[1]: Leaving directory `/home/mort/mirage/mort-www/src= '
[ERROR] =A0 =A0 =A0The command "make build" exited with code 2. ```

i'm using thomas' new combinator branch of mirage.

this is a bit of a blocker for me -- my website is on the large side to be = crunched (150MB .ml file anyone?) so i'd hoped that FAT would save me..= .

i see the same issue with mirage-www too, and the use of crunch for the liv= e site (afaics) suggests to me that fat might not be supported.

(and yes, for the time being i will store the relevant bits of content out = of the site and href them from the site itself, but that seems like a bit o= f a cop-out given we're intending to demo this at fosdem in 2 weeks... = :)

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l 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



--
Dave Scott
--047d7b15a693bfe15e04f030d694-- --===============5782543242108387364== 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 --===============5782543242108387364==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jan 17 21:01:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 21:01: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 1W4GXJ-0004Ui-GM; Fri, 17 Jan 2014 21:01:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4GXH-0004Ud-Ob for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 21:01:04 +0000 Received: from [85.158.143.35:5186] by server-1.bemta-4.messagelabs.com id 1F/AB-02132-E0A99D25; Fri, 17 Jan 2014 21:01:02 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1389992459!12491585!1 X-Originating-IP: [209.85.192.171] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20514 invoked from network); 17 Jan 2014 21:01:00 -0000 Received: from mail-pd0-f171.google.com (HELO mail-pd0-f171.google.com) (209.85.192.171) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2014 21:01:00 -0000 Received: by mail-pd0-f171.google.com with SMTP id g10so3706928pdj.16 for ; Fri, 17 Jan 2014 13:00:58 -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=WdiRTMSyTLCHCve1tlWiP/3KB8CpsrdG45+S7sZ18bM=; b=OEe56yf3XqktEwMWQjHsoiYqrv64nHbWwtmH0NHdt2e8uEyjfy9W8EA4iL+M36cQet RLU45amWXlL+CW8I9jHc7olNRWKnxnsqVmqtuifwOEkpioIP8JiWpLr2N4tbUvPyv5VV eGKmD0z3XTtDpOKd33jXyfrSCpHjgkjknvNbGxE+DnEPUQPPqS3AF8kIeBof2y+paJi5 24kIr+nJnqNZQPjbDBBGE+zYY3t/FKfkFUX6f6XL3o874f6+9jSQTYd/f/tpgaAj5hOz /AXCv/YJ3VxuLBA2DNeuFpDuq2/m2kdr4TOvHKerobXebZKum+CBnkiDccHoufAbiRcw WJdA== MIME-Version: 1.0 X-Received: by 10.68.202.8 with SMTP id ke8mr4556602pbc.86.1389992458836; Fri, 17 Jan 2014 13:00:58 -0800 (PST) Received: by 10.70.61.136 with HTTP; Fri, 17 Jan 2014 13:00:58 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Jan 2014 21:00:58 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] has anyone successfully used fat and xen together? 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="===============5782543242108387364==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5782543242108387364== Content-Type: multipart/alternative; boundary=047d7b15a693bfe15e04f030d694 --047d7b15a693bfe15e04f030d694 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jan 17, 2014 at 8:32 PM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > if so, how? :) > I have, but before all the recent tooling improvements. > > specifically-- configuring with `MODE=xen` and `FS_MODE=fat` causes > installation of `fat-filesystem` and thus `mirage-block-unix`. when i then > execute a build i end up with: > > ``` > mort-www + ocamlfind ocamlopt -g -linkpkg -dontlink unix -output-obj > -package mirage.types-xen -package mirage-http-xen -package > mirage-console-xen -package mirage-block-xen.front -package > mirage-block-unix -package io-page-xen -package io-page-unix -package > fat-filesystem -package cowabloga -package cow.syntax -package lwt.syntax > -syntax camlp4o site_config.cmx posts.cmx page.cmx blog.cmx courses.cmx > papers.cmx site.cmx server.cmx main.cmx -o main.native.o > mort-www findlib: [WARNING] Interface block.cmi occurs in several > directories: /home/mort/.opam/mirage-xen/lib/mirage-block-unix, > /home/mort/.opam/mirage-xen/lib/mirage-block-xen > mort-www findlib: [WARNING] Interface io_page.cmi occurs in several > directories: /home/mort/.opam/mirage-xen/lib/io-page-unix, > /home/mort/.opam/mirage-xen/lib/io-page-xen > mort-www File "_none_", line 1: > mort-www Error: No implementations provided for the following modules: > mort-www Unix referenced from > /home/mort/.opam/mirage-xen/lib/lwt/lwt-unix.cmxa(Lwt_engine), > mort-www > /home/mort/.opam/mirage-xen/lib/lwt/lwt-unix.cmxa(Lwt_unix), > mort-www > /home/mort/.opam/mirage-xen/lib/mirage-block-unix/mirage_block_unix.cmxa(Block) > Referencing Unix is not going to work :) I checked the META file for fat-filesystem, it depends on: ``` requires = "cstruct re re.str mirage-types lwt" ``` I think we need to track down where mirage-block-unix is coming from. A second observation is that I recently merged Thomas' io-page improvement, so you can now just use "io-page" instead of "io-page-xen". The old package should work though; I don't think this is related to your problem. > mort-www Command exited with code 2. > mort-www make[1]: Leaving directory `/home/mort/mirage/mort-www/src' > [ERROR] The command "make build" exited with code 2. > ``` > > i'm using thomas' new combinator branch of mirage. > > this is a bit of a blocker for me -- my website is on the large side to be > crunched (150MB .ml file anyone?) so i'd hoped that FAT would save me... > > i see the same issue with mirage-www too, and the use of crunch for the > live site (afaics) suggests to me that fat might not be supported. > > (and yes, for the time being i will store the relevant bits of content out > of the site and href them from the site itself, but that seems like a bit > of a cop-out given we're intending to demo this at fosdem in 2 weeks... :) > > -- > 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 > -- Dave Scott --047d7b15a693bfe15e04f030d694 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Fri, Jan 17, 2014 at 8:32 PM, Richard Mortier <Richard.M= ortier@nottingham.ac.uk> wrote:
if so, how? :)

I have,= but before all the recent tooling improvements.
=A0

specifically-- configuring with `MODE=3Dxen` and `FS_MODE=3Dfat` causes ins= tallation of `fat-filesystem` and thus `mirage-block-unix`. when i then exe= cute a build i end up with:

```
mort-www =A0 =A0 + ocamlfind ocamlopt -g -linkpkg -dontlink unix -output-ob= j -package mirage.types-xen -package mirage-http-xen -package mirage-consol= e-xen -package mirage-block-xen.front -package mirage-block-unix -package i= o-page-xen -package io-page-unix -package fat-filesystem -package cowabloga= -package cow.syntax -package lwt.syntax -syntax camlp4o site_config.cmx po= sts.cmx page.cmx blog.cmx courses.cmx papers.cmx site.cmx server.cmx main.c= mx -o main.native.o
mort-www =A0 =A0 findlib: [WARNING] Interface block.cmi occurs in several d= irectories: /home/mort/.opam/mirage-xen/lib/mirage-block-unix, /home/mort/.= opam/mirage-xen/lib/mirage-block-xen
mort-www =A0 =A0 findlib: [WARNING] Interface io_page.cmi occurs in several= directories: /home/mort/.opam/mirage-xen/lib/io-page-unix, /home/mort/.opa= m/mirage-xen/lib/io-page-xen
mort-www =A0 =A0 File "_none_", line 1:
mort-www =A0 =A0 Error: No implementations provided for the following modul= es:
mort-www =A0 =A0 =A0 =A0 =A0 =A0 =A0Unix referenced from /home/mort/.opam/m= irage-xen/lib/lwt/lwt-unix.cmxa(Lwt_engine),
mort-www =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/home/mort/.opam/mirage-xen/lib/lwt= /lwt-unix.cmxa(Lwt_unix),
mort-www =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/home/mort/.opam/mirage-xen/lib/mir= age-block-unix/mirage_block_unix.cmxa(Block)

Referencing Unix is not going to work :)

I c= hecked the META file for fat-filesystem, it depends on:
```
requires =3D "cstruct re re.str mirage-types l= wt"
```
I think we need to track down where = mirage-block-unix is coming from.

A second observa= tion is that I recently merged Thomas' io-page improvement, so you can = now just use "io-page" instead of "io-page-xen". The ol= d package should work though; I don't think this is related to your pro= blem.
=A0
mort-www =A0 =A0 Command exited with code 2.
mort-www =A0 =A0 make[1]: Leaving directory `/home/mort/mirage/mort-www/src= '
[ERROR] =A0 =A0 =A0The command "make build" exited with code 2. ```

i'm using thomas' new combinator branch of mirage.

this is a bit of a blocker for me -- my website is on the large side to be = crunched (150MB .ml file anyone?) so i'd hoped that FAT would save me..= .

i see the same issue with mirage-www too, and the use of crunch for the liv= e site (afaics) suggests to me that fat might not be supported.

(and yes, for the time being i will store the relevant bits of content out = of the site and href them from the site itself, but that seems like a bit o= f a cop-out given we're intending to demo this at fosdem in 2 weeks... = :)

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l 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



--
Dave Scott
--047d7b15a693bfe15e04f030d694-- --===============5782543242108387364== 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 --===============5782543242108387364==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jan 17 21:04:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 21:04: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 1W4Gaq-0004WA-Rf; Fri, 17 Jan 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 1W4Gap-0004W3-CU for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 21:04:43 +0000 Received: from [85.158.137.68:39842] by server-17.bemta-3.messagelabs.com id D5/0C-15965-AEA99D25; Fri, 17 Jan 2014 21:04:42 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-31.messagelabs.com!1389992681!6190256!1 X-Originating-IP: [93.159.202.52] 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 32557 invoked from network); 17 Jan 2014 21:04:41 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-12.tower-31.messagelabs.com with SMTP; 17 Jan 2014 21:04:41 -0000 Received: (qmail 5376 invoked from network); 17 Jan 2014 21:04:36 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 17 Jan 2014 21:04:36 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 04891-06 for ; Fri, 17 Jan 2014 21:04:35 +0000 (GMT) Received: (qmail 5365 invoked by uid 599); 17 Jan 2014 21:04:35 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 17 Jan 2014 21:04:35 +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 1W4Gak-0005Oe-Rf; Fri, 17 Jan 2014 21:04:38 +0000 From: Richard Mortier To: David Scott Date: Fri, 17 Jan 2014 21:04:37 +0000 Thread-Topic: [MirageOS-devel] has anyone successfully used fat and xen together? Thread-Index: Ac8Tx7uJ1A0n2e+0RyqqsAqT2F+U/A== Message-ID: 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 engine03-20433-8.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] has anyone successfully used fat and xen together? 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 17 Jan 2014, at 21:00, David Scott wrote: > Referencing Unix is not going to work :) didn't think so :) > I checked the META file for fat-filesystem, it depends on: > ``` > requires = "cstruct re re.str mirage-types lwt" > ``` > I think we need to track down where mirage-block-unix is coming from. the _oasis file in `ocaml-fat` expects it for building `Executable fat`, as does the opam package file (for fat-filesystem.0.9.0 at least). > A second observation is that I recently merged Thomas' io-page improvement, so you can now just use "io-page" instead of "io-page-xen". ah cool-- that's merged into mirage/mirage#HEAD? or mirage/ocaml-fat#HEAD? or somewhere else? (or maybe i just bite the bullet and move to v2 at the same time. so many things changing at once, feeling seasick... ;) -- 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 Jan 17 21:04:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 21:04: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 1W4Gaq-0004WA-Rf; Fri, 17 Jan 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 1W4Gap-0004W3-CU for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 21:04:43 +0000 Received: from [85.158.137.68:39842] by server-17.bemta-3.messagelabs.com id D5/0C-15965-AEA99D25; Fri, 17 Jan 2014 21:04:42 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-31.messagelabs.com!1389992681!6190256!1 X-Originating-IP: [93.159.202.52] 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 32557 invoked from network); 17 Jan 2014 21:04:41 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-12.tower-31.messagelabs.com with SMTP; 17 Jan 2014 21:04:41 -0000 Received: (qmail 5376 invoked from network); 17 Jan 2014 21:04:36 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 17 Jan 2014 21:04:36 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 04891-06 for ; Fri, 17 Jan 2014 21:04:35 +0000 (GMT) Received: (qmail 5365 invoked by uid 599); 17 Jan 2014 21:04:35 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 17 Jan 2014 21:04:35 +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 1W4Gak-0005Oe-Rf; Fri, 17 Jan 2014 21:04:38 +0000 From: Richard Mortier To: David Scott Date: Fri, 17 Jan 2014 21:04:37 +0000 Thread-Topic: [MirageOS-devel] has anyone successfully used fat and xen together? Thread-Index: Ac8Tx7uJ1A0n2e+0RyqqsAqT2F+U/A== Message-ID: 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 engine03-20433-8.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] has anyone successfully used fat and xen together? 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 17 Jan 2014, at 21:00, David Scott wrote: > Referencing Unix is not going to work :) didn't think so :) > I checked the META file for fat-filesystem, it depends on: > ``` > requires = "cstruct re re.str mirage-types lwt" > ``` > I think we need to track down where mirage-block-unix is coming from. the _oasis file in `ocaml-fat` expects it for building `Executable fat`, as does the opam package file (for fat-filesystem.0.9.0 at least). > A second observation is that I recently merged Thomas' io-page improvement, so you can now just use "io-page" instead of "io-page-xen". ah cool-- that's merged into mirage/mirage#HEAD? or mirage/ocaml-fat#HEAD? or somewhere else? (or maybe i just bite the bullet and move to v2 at the same time. so many things changing at once, feeling seasick... ;) -- 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 Jan 17 21:37:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 21:37: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 1W4H6g-00061s-C4; Fri, 17 Jan 2014 21:37:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4H6f-00061m-Bi for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 21:37:37 +0000 Received: from [85.158.143.35:2881] by server-2.bemta-4.messagelabs.com id AB/D3-11386-0A2A9D25; Fri, 17 Jan 2014 21:37:36 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1389994654!12451498!1 X-Originating-IP: [209.85.160.45] 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 15074 invoked from network); 17 Jan 2014 21:37:35 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2014 21:37:35 -0000 Received: by mail-pb0-f45.google.com with SMTP id un15so937605pbc.4 for ; Fri, 17 Jan 2014 13:37:33 -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=H0QaCvsu9YzDF06g3CtjlbQzZ1eFHXOC0BFlDDBO/jQ=; b=sso9h9iRIC9htzcM9bO3KXRLoTeYWpsXm4fpvfXEDgBWmqXn7ornVjfQ0CL5LEuGxY 1BrUKMsQz/hFIvgyerxQMP1p92zrxHuVxqjvWif69TxMgluIafjNtnSLucGYzLOkcsZf qaadyDvs2Fk9RiwTOhHFV8gW5qsSOQ1K8H+Qg9RnACTVVqzAQ+WL0BLzxaZaFvivRi2p 0+1G55UuPkXcDHpVIgLOx/f4rHswQuivP/gLqCx9R7IyJvwJa8IbT5mOmyRb4g+hmLte tB54Lfrc/ydUPyQFeHHEQri6FJGBtblbkIpwW/vPwNS92M0mMvlEraTvbIslRwZBmrja YQMA== MIME-Version: 1.0 X-Received: by 10.68.251.133 with SMTP id zk5mr4616145pbc.69.1389994653716; Fri, 17 Jan 2014 13:37:33 -0800 (PST) Received: by 10.70.61.136 with HTTP; Fri, 17 Jan 2014 13:37:33 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Jan 2014 21:37:33 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] has anyone successfully used fat and xen together? 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="===============7993648453845502577==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7993648453845502577== Content-Type: multipart/alternative; boundary=047d7b1630a993171304f0315984 --047d7b1630a993171304f0315984 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jan 17, 2014 at 9:04 PM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > > On 17 Jan 2014, at 21:00, David Scott wrote: > > > Referencing Unix is not going to work :) > > didn't think so :) > > > I checked the META file for fat-filesystem, it depends on: > > ``` > > requires = "cstruct re re.str mirage-types lwt" > > ``` > > I think we need to track down where mirage-block-unix is coming from. > > the _oasis file in `ocaml-fat` expects it for building `Executable fat`, > as does the opam package file (for fat-filesystem.0.9.0 at least). > Yup-- when you 'opam install fat-filesystem' it will also install mirage-block-unix. When you run 'ocamlfind ocamlopt -package fat-filesystem' it should only link with the libraries in the META file. Could you tell me how to replicate your setup? Which branches and commands are you using? Cheers, Dave --047d7b1630a993171304f0315984 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Fri, Jan 17, 2014 at 9:04 PM, Richard Mortier = <R= ichard.Mortier@nottingham.ac.uk> wrote:

On 17 Jan 2014, at 21:00, David Scott wrote:

> Referencing Unix is not going to work :)

didn't think so :)

> I checked the META file for fat-filesystem, it depends on:
> ```
> requires =3D "cstruct re re.str mirage-types lwt"
> ```
> I think we need to track down where mirage-block-unix is coming from.<= br>
the _oasis file in `ocaml-fat` expects it for building `Executable fa= t`, as does the opam package file (for fat-filesystem.0.9.0 at least).
<= /blockquote>

Yup-- when you 'opam install fat-filesy= stem' it will also install mirage-block-unix. When you run 'ocamlfi= nd ocamlopt -package fat-filesystem' it should only link with the libra= ries in the META file.=A0
=A0
Could you tell me how to replicate your setup? Which bra= nches and commands are you using?

Cheers,
Dave
--047d7b1630a993171304f0315984-- --===============7993648453845502577== 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 --===============7993648453845502577==-- From mirageos-devel-bounces@lists.xenproject.org Fri Jan 17 21:37:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 17 Jan 2014 21:37: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 1W4H6g-00061s-C4; Fri, 17 Jan 2014 21:37:38 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4H6f-00061m-Bi for mirageos-devel@lists.xenproject.org; Fri, 17 Jan 2014 21:37:37 +0000 Received: from [85.158.143.35:2881] by server-2.bemta-4.messagelabs.com id AB/D3-11386-0A2A9D25; Fri, 17 Jan 2014 21:37:36 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1389994654!12451498!1 X-Originating-IP: [209.85.160.45] 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 15074 invoked from network); 17 Jan 2014 21:37:35 -0000 Received: from mail-pb0-f45.google.com (HELO mail-pb0-f45.google.com) (209.85.160.45) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Jan 2014 21:37:35 -0000 Received: by mail-pb0-f45.google.com with SMTP id un15so937605pbc.4 for ; Fri, 17 Jan 2014 13:37:33 -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=H0QaCvsu9YzDF06g3CtjlbQzZ1eFHXOC0BFlDDBO/jQ=; b=sso9h9iRIC9htzcM9bO3KXRLoTeYWpsXm4fpvfXEDgBWmqXn7ornVjfQ0CL5LEuGxY 1BrUKMsQz/hFIvgyerxQMP1p92zrxHuVxqjvWif69TxMgluIafjNtnSLucGYzLOkcsZf qaadyDvs2Fk9RiwTOhHFV8gW5qsSOQ1K8H+Qg9RnACTVVqzAQ+WL0BLzxaZaFvivRi2p 0+1G55UuPkXcDHpVIgLOx/f4rHswQuivP/gLqCx9R7IyJvwJa8IbT5mOmyRb4g+hmLte tB54Lfrc/ydUPyQFeHHEQri6FJGBtblbkIpwW/vPwNS92M0mMvlEraTvbIslRwZBmrja YQMA== MIME-Version: 1.0 X-Received: by 10.68.251.133 with SMTP id zk5mr4616145pbc.69.1389994653716; Fri, 17 Jan 2014 13:37:33 -0800 (PST) Received: by 10.70.61.136 with HTTP; Fri, 17 Jan 2014 13:37:33 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Jan 2014 21:37:33 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] has anyone successfully used fat and xen together? 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="===============7993648453845502577==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7993648453845502577== Content-Type: multipart/alternative; boundary=047d7b1630a993171304f0315984 --047d7b1630a993171304f0315984 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jan 17, 2014 at 9:04 PM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > > On 17 Jan 2014, at 21:00, David Scott wrote: > > > Referencing Unix is not going to work :) > > didn't think so :) > > > I checked the META file for fat-filesystem, it depends on: > > ``` > > requires = "cstruct re re.str mirage-types lwt" > > ``` > > I think we need to track down where mirage-block-unix is coming from. > > the _oasis file in `ocaml-fat` expects it for building `Executable fat`, > as does the opam package file (for fat-filesystem.0.9.0 at least). > Yup-- when you 'opam install fat-filesystem' it will also install mirage-block-unix. When you run 'ocamlfind ocamlopt -package fat-filesystem' it should only link with the libraries in the META file. Could you tell me how to replicate your setup? Which branches and commands are you using? Cheers, Dave --047d7b1630a993171304f0315984 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Fri, Jan 17, 2014 at 9:04 PM, Richard Mortier = <R= ichard.Mortier@nottingham.ac.uk> wrote:

On 17 Jan 2014, at 21:00, David Scott wrote:

> Referencing Unix is not going to work :)

didn't think so :)

> I checked the META file for fat-filesystem, it depends on:
> ```
> requires =3D "cstruct re re.str mirage-types lwt"
> ```
> I think we need to track down where mirage-block-unix is coming from.<= br>
the _oasis file in `ocaml-fat` expects it for building `Executable fa= t`, as does the opam package file (for fat-filesystem.0.9.0 at least).
<= /blockquote>

Yup-- when you 'opam install fat-filesy= stem' it will also install mirage-block-unix. When you run 'ocamlfi= nd ocamlopt -package fat-filesystem' it should only link with the libra= ries in the META file.=A0
=A0
Could you tell me how to replicate your setup? Which bra= nches and commands are you using?

Cheers,
Dave
--047d7b1630a993171304f0315984-- --===============7993648453845502577== 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 --===============7993648453845502577==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jan 18 00:28:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 00:28: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 1W4JmF-0007eU-3n; Sat, 18 Jan 2014 00:28:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4JmD-0007eP-Tp for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 00:28:42 +0000 Received: from [85.158.139.211:64114] by server-9.bemta-5.messagelabs.com id 1F/BA-15098-9BAC9D25; Sat, 18 Jan 2014 00:28:41 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-206.messagelabs.com!1390004920!10496844!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 28562 invoked from network); 18 Jan 2014 00:28:40 -0000 Received: from engine05-20433-5.icritical.com (HELO engine05-20433-5.icritical.com) (93.95.15.171) by server-9.tower-206.messagelabs.com with SMTP; 18 Jan 2014 00:28:40 -0000 Received: (qmail 9065 invoked from network); 18 Jan 2014 00:28:35 -0000 Received: from localhost (127.0.0.1) by engine05-20433-5.icritical.com with SMTP; 18 Jan 2014 00:28:35 -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 07233-09 for ; Sat, 18 Jan 2014 00:28:32 +0000 (GMT) Received: (qmail 9056 invoked by uid 599); 18 Jan 2014 00:28:32 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine05-20433-5.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 00:28:32 +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 1W4Jm7-0008Fa-5y for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 00:28:35 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Date: Sat, 18 Jan 2014 00:28:33 +0000 Thread-Topic: xen issues Thread-Index: Ac8T5DiCmWUtLY6GSPa7WYvsk3eivA== Message-ID: <024D82BD-7332-48ED-ABC9-B028EFCD3F69@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 engine05-20433-5.icritical.com Subject: [MirageOS-devel] xen issues 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 having fixed the previous problem (with some assistance from dave :) i can now build a xen image but not successfully start it. this is true of my website and of mirage/lib_test/basic. i get the output appended below (trying to start the combinator example in mirage/mirage). i'm not very familiar with interpreting these logs -- anyone any suggestions? root@greyjay-xen:~/mirage/mirage/lib_test/combinator# xl -v create mux.xl -cd Parsing config from mux.xl {"domid":null,"config":{"c_info":{"type":"pv","hap":"","oos":"","ssidref":0,"name":"mux","uuid":"dd23d957-6739-4215-bba8-313c99f204b5","xsdata":{},"platformdata":{},"poolid":0,"run_hotplug_scripts":"True"},"b_info":{"max_vcpus":0,"avail_vcpus":[],"cpumap":[],"numa_placement":"","tsc_mode":"default","max_memkb":262144,"target_memkb":262144,"video_memkb":-1,"shadow_memkb":2048,"rtc_timeoffset":0,"localtime":"","disable_migrate":"","cpuid":[],"blkdev_start":null,"device_model_version":null,"device_model_stubdomain":"","device_model":null,"device_model_ssidref":0,"extra":[],"extra_pv":[],"extra_hvm":[],"sched_params":{"sched":"unknown","weight":-1,"cap":-1,"period":-1,"slice":-1,"latency":-1,"extratime":-1},"ioports":[],"irqs":[],"u":{"kernel":"/home/mort/mirage/mirage/lib_test/combinator/mir-mux.xen","slack_memkb":-1,"bootloader":null,"bootloader_args":[],"cmdline":"","ramdisk":null,"e820_host":""}},"disks":[],"nics":[],"pcidevs":[],"vfbs":[],"vkbs":[],"on_poweroff":"destroy","on_reboot":"restart","on_watchdog":"destroy","on_crash":"destroy"}} libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate with 1 nodes, 1 cpus and 438 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline="", features="(null)" domainbuilder: detail: xc_dom_kernel_file: filename="/home/mort/mirage/mirage/lib_test/combinator/mir-mux.xen" domainbuilder: detail: xc_dom_malloc_filemap : 3677 kB domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, caps xen-3.0-x86_64 xen-3.0-x86_32p domainbuilder: detail: xc_dom_parse_image: called domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... domainbuilder: detail: loader probe OK xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x1147fe0 xc: detail: elf_parse_binary: memory: 0x0 -> 0x1147fe0 xc: detail: elf_xen_parse: __xen_guest: "GUEST_OS=Mirage,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,LOADER=generic" xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mirage" xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0" xc: detail: elf_xen_parse_guest_info: VIRT_BASE="0x0" xc: detail: elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0" xc: detail: elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2" xc: detail: elf_xen_parse_guest_info: LOADER="generic" xc: detail: elf_xen_addr_calc_check: addresses: xc: detail: virt_base = 0x0 xc: detail: elf_paddr_offset = 0x0 xc: detail: virt_offset = 0x0 xc: detail: virt_kstart = 0x0 xc: detail: virt_kend = 0x1147fe0 xc: detail: virt_entry = 0x0 xc: detail: p2m_base = 0xffffffffffffffff domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 0x1147fe0 domainbuilder: detail: xc_dom_mem_init: mem 256 MB, pages 0x10000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x10000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_malloc : 512 kB domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x0 -> 0x1148000 (pfn 0x0 + 0x1148 pages) domainbuilder: detail: xc_dom_malloc : 103 kB domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x0+0x1148 at 0x7f46660b9000 xc: detail: elf_load_binary: phdr 0 at 0x139940336472064 -> 0x139940337716272 domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0x1148000 -> 0x11c8000 (pfn 0x1148 + 0x80 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x1148+0x80 at 0x7f46695a9000 domainbuilder: detail: xc_dom_alloc_page : start info : 0x11c8000 (pfn 0x11c8) domainbuilder: detail: xc_dom_alloc_page : xenstore : 0x11c9000 (pfn 0x11c9) domainbuilder: detail: xc_dom_alloc_page : console : 0x11ca000 (pfn 0x11ca) domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0x0000000000000000 -> 0x0000ffffffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0x0000000000000000 -> 0x0000007fffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x0000000000000000 -> 0x000000003fffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x0000000000000000 -> 0x00000000013fffff, 10 table(s) domainbuilder: detail: xc_dom_alloc_segment: page tables : 0x11cb000 -> 0x11d8000 (pfn 0x11cb + 0xd pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x11cb+0xd at 0x7f466959c000 domainbuilder: detail: xc_dom_alloc_page : boot stack : 0x11d8000 (pfn 0x11d8) domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x11d9000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x1400000 domainbuilder: detail: xc_dom_boot_image: called domainbuilder: detail: arch_setup_bootearly: doing nothing domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x10000 domainbuilder: detail: clear_page: pfn 0x11ca, mfn 0x6d110 domainbuilder: detail: clear_page: pfn 0x11c9, mfn 0x6d111 domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x11c8+0x1 at 0x7f466959b000 domainbuilder: detail: start_info_x86_64: called domainbuilder: detail: setup_hypercall_page: vaddr=0x2000 pfn=0x2 domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 621 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 3677 kB domainbuilder: detail: domU mmap : 18264 kB domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0x6cecb domainbuilder: detail: shared_info_x86_64: called domainbuilder: detail: vcpu_x86_64: called domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x11cb mfn 0x6d10f domainbuilder: detail: launch_vm: called, ctxt=0x7fffa8c65820 domainbuilder: detail: xc_dom_release: called Daemon running with PID 16748 libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type for domid=10 Unable to attach console libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 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 Sat Jan 18 00:28:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 00:28: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 1W4JmF-0007eU-3n; Sat, 18 Jan 2014 00:28:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4JmD-0007eP-Tp for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 00:28:42 +0000 Received: from [85.158.139.211:64114] by server-9.bemta-5.messagelabs.com id 1F/BA-15098-9BAC9D25; Sat, 18 Jan 2014 00:28:41 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-206.messagelabs.com!1390004920!10496844!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 28562 invoked from network); 18 Jan 2014 00:28:40 -0000 Received: from engine05-20433-5.icritical.com (HELO engine05-20433-5.icritical.com) (93.95.15.171) by server-9.tower-206.messagelabs.com with SMTP; 18 Jan 2014 00:28:40 -0000 Received: (qmail 9065 invoked from network); 18 Jan 2014 00:28:35 -0000 Received: from localhost (127.0.0.1) by engine05-20433-5.icritical.com with SMTP; 18 Jan 2014 00:28:35 -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 07233-09 for ; Sat, 18 Jan 2014 00:28:32 +0000 (GMT) Received: (qmail 9056 invoked by uid 599); 18 Jan 2014 00:28:32 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine05-20433-5.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 00:28:32 +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 1W4Jm7-0008Fa-5y for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 00:28:35 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Date: Sat, 18 Jan 2014 00:28:33 +0000 Thread-Topic: xen issues Thread-Index: Ac8T5DiCmWUtLY6GSPa7WYvsk3eivA== Message-ID: <024D82BD-7332-48ED-ABC9-B028EFCD3F69@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 engine05-20433-5.icritical.com Subject: [MirageOS-devel] xen issues 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 having fixed the previous problem (with some assistance from dave :) i can now build a xen image but not successfully start it. this is true of my website and of mirage/lib_test/basic. i get the output appended below (trying to start the combinator example in mirage/mirage). i'm not very familiar with interpreting these logs -- anyone any suggestions? root@greyjay-xen:~/mirage/mirage/lib_test/combinator# xl -v create mux.xl -cd Parsing config from mux.xl {"domid":null,"config":{"c_info":{"type":"pv","hap":"","oos":"","ssidref":0,"name":"mux","uuid":"dd23d957-6739-4215-bba8-313c99f204b5","xsdata":{},"platformdata":{},"poolid":0,"run_hotplug_scripts":"True"},"b_info":{"max_vcpus":0,"avail_vcpus":[],"cpumap":[],"numa_placement":"","tsc_mode":"default","max_memkb":262144,"target_memkb":262144,"video_memkb":-1,"shadow_memkb":2048,"rtc_timeoffset":0,"localtime":"","disable_migrate":"","cpuid":[],"blkdev_start":null,"device_model_version":null,"device_model_stubdomain":"","device_model":null,"device_model_ssidref":0,"extra":[],"extra_pv":[],"extra_hvm":[],"sched_params":{"sched":"unknown","weight":-1,"cap":-1,"period":-1,"slice":-1,"latency":-1,"extratime":-1},"ioports":[],"irqs":[],"u":{"kernel":"/home/mort/mirage/mirage/lib_test/combinator/mir-mux.xen","slack_memkb":-1,"bootloader":null,"bootloader_args":[],"cmdline":"","ramdisk":null,"e820_host":""}},"disks":[],"nics":[],"pcidevs":[],"vfbs":[],"vkbs":[],"on_poweroff":"destroy","on_reboot":"restart","on_watchdog":"destroy","on_crash":"destroy"}} libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate with 1 nodes, 1 cpus and 438 KB free selected domainbuilder: detail: xc_dom_allocate: cmdline="", features="(null)" domainbuilder: detail: xc_dom_kernel_file: filename="/home/mort/mirage/mirage/lib_test/combinator/mir-mux.xen" domainbuilder: detail: xc_dom_malloc_filemap : 3677 kB domainbuilder: detail: xc_dom_boot_xen_init: ver 4.2, caps xen-3.0-x86_64 xen-3.0-x86_32p domainbuilder: detail: xc_dom_parse_image: called domainbuilder: detail: xc_dom_find_loader: trying multiboot-binary loader ... domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying Linux bzImage loader ... domainbuilder: detail: xc_dom_probe_bzimage_kernel: kernel is not a bzImage domainbuilder: detail: loader probe failed domainbuilder: detail: xc_dom_find_loader: trying ELF-generic loader ... domainbuilder: detail: loader probe OK xc: detail: elf_parse_binary: phdr: paddr=0x0 memsz=0x1147fe0 xc: detail: elf_parse_binary: memory: 0x0 -> 0x1147fe0 xc: detail: elf_xen_parse: __xen_guest: "GUEST_OS=Mirage,XEN_VER=xen-3.0,VIRT_BASE=0x0,ELF_PADDR_OFFSET=0x0,HYPERCALL_PAGE=0x2,LOADER=generic" xc: detail: elf_xen_parse_guest_info: GUEST_OS="Mirage" xc: detail: elf_xen_parse_guest_info: XEN_VER="xen-3.0" xc: detail: elf_xen_parse_guest_info: VIRT_BASE="0x0" xc: detail: elf_xen_parse_guest_info: ELF_PADDR_OFFSET="0x0" xc: detail: elf_xen_parse_guest_info: HYPERCALL_PAGE="0x2" xc: detail: elf_xen_parse_guest_info: LOADER="generic" xc: detail: elf_xen_addr_calc_check: addresses: xc: detail: virt_base = 0x0 xc: detail: elf_paddr_offset = 0x0 xc: detail: virt_offset = 0x0 xc: detail: virt_kstart = 0x0 xc: detail: virt_kend = 0x1147fe0 xc: detail: virt_entry = 0x0 xc: detail: p2m_base = 0xffffffffffffffff domainbuilder: detail: xc_dom_parse_elf_kernel: xen-3.0-x86_64: 0x0 -> 0x1147fe0 domainbuilder: detail: xc_dom_mem_init: mem 256 MB, pages 0x10000 pages, 4k each domainbuilder: detail: xc_dom_mem_init: 0x10000 pages domainbuilder: detail: xc_dom_boot_mem_init: called domainbuilder: detail: x86_compat: guest xen-3.0-x86_64, address size 64 domainbuilder: detail: xc_dom_malloc : 512 kB domainbuilder: detail: xc_dom_build_image: called domainbuilder: detail: xc_dom_alloc_segment: kernel : 0x0 -> 0x1148000 (pfn 0x0 + 0x1148 pages) domainbuilder: detail: xc_dom_malloc : 103 kB domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x0+0x1148 at 0x7f46660b9000 xc: detail: elf_load_binary: phdr 0 at 0x139940336472064 -> 0x139940337716272 domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0x1148000 -> 0x11c8000 (pfn 0x1148 + 0x80 pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x1148+0x80 at 0x7f46695a9000 domainbuilder: detail: xc_dom_alloc_page : start info : 0x11c8000 (pfn 0x11c8) domainbuilder: detail: xc_dom_alloc_page : xenstore : 0x11c9000 (pfn 0x11c9) domainbuilder: detail: xc_dom_alloc_page : console : 0x11ca000 (pfn 0x11ca) domainbuilder: detail: nr_page_tables: 0x0000ffffffffffff/48: 0x0000000000000000 -> 0x0000ffffffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x0000007fffffffff/39: 0x0000000000000000 -> 0x0000007fffffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x000000003fffffff/30: 0x0000000000000000 -> 0x000000003fffffff, 1 table(s) domainbuilder: detail: nr_page_tables: 0x00000000001fffff/21: 0x0000000000000000 -> 0x00000000013fffff, 10 table(s) domainbuilder: detail: xc_dom_alloc_segment: page tables : 0x11cb000 -> 0x11d8000 (pfn 0x11cb + 0xd pages) domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x11cb+0xd at 0x7f466959c000 domainbuilder: detail: xc_dom_alloc_page : boot stack : 0x11d8000 (pfn 0x11d8) domainbuilder: detail: xc_dom_build_image : virt_alloc_end : 0x11d9000 domainbuilder: detail: xc_dom_build_image : virt_pgtab_end : 0x1400000 domainbuilder: detail: xc_dom_boot_image: called domainbuilder: detail: arch_setup_bootearly: doing nothing domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches domainbuilder: detail: xc_dom_compat_check: supported guest type: xen-3.0-x86_32p domainbuilder: detail: xc_dom_update_guest_p2m: dst 64bit, pages 0x10000 domainbuilder: detail: clear_page: pfn 0x11ca, mfn 0x6d110 domainbuilder: detail: clear_page: pfn 0x11c9, mfn 0x6d111 domainbuilder: detail: xc_dom_pfn_to_ptr_retcount: domU mapping: pfn 0x11c8+0x1 at 0x7f466959b000 domainbuilder: detail: start_info_x86_64: called domainbuilder: detail: setup_hypercall_page: vaddr=0x2000 pfn=0x2 domainbuilder: detail: domain builder memory footprint domainbuilder: detail: allocated domainbuilder: detail: malloc : 621 kB domainbuilder: detail: anon mmap : 0 bytes domainbuilder: detail: mapped domainbuilder: detail: file mmap : 3677 kB domainbuilder: detail: domU mmap : 18264 kB domainbuilder: detail: arch_setup_bootlate: shared_info: pfn 0x0, mfn 0x6cecb domainbuilder: detail: shared_info_x86_64: called domainbuilder: detail: vcpu_x86_64: called domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x11cb mfn 0x6d10f domainbuilder: detail: launch_vm: called, ctxt=0x7fffa8c65820 domainbuilder: detail: xc_dom_release: called Daemon running with PID 16748 libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type for domid=10 Unable to attach console libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child [0] exited with error status 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 Sat Jan 18 10:01:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 10:01: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 1W4SiC-0006hP-9Q; Sat, 18 Jan 2014 10:01:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4SiA-0006hH-0U for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 10:01:06 +0000 Received: from [193.109.254.147:26629] by server-6.bemta-14.messagelabs.com id 99/3B-14958-1E05AD25; Sat, 18 Jan 2014 10:01:05 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1390039263!11683606!1 X-Originating-IP: [209.85.220.169] 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 21945 invoked from network); 18 Jan 2014 10:01:04 -0000 Received: from mail-vc0-f169.google.com (HELO mail-vc0-f169.google.com) (209.85.220.169) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 10:01:04 -0000 Received: by mail-vc0-f169.google.com with SMTP id hq11so1988254vcb.14 for ; Sat, 18 Jan 2014 02:01: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=mD4Pd528Y2QmzffH8BAaR1dqWYzMbeuXlP3xK8h9V+k=; b=lSZ+6ApmLWC42rt4Xlw6qLYp/BtfAlDtfeg+E0g/+PzHthtqOykRPwi21hcL2vJi8C pYWZrHsgLBq65i8dkBbYbWkQqxkLVLp+JNRpLyCZRj9kZlCanDCbTbJzMlsSyQ7tzBCX nMrjIiIgYM34RYbRMjRZ8NwqkbKVEodFw935RMkqMdsi02UqVg26OPZwF/J5i49g+Ntw 1KVIRP5LCh4O2DJxIcKYPPgq9Gzxhyqqhfr3tqreiDshM8WIHPLozsQWGVN6Fd9f/XtG wMyIbZWshOLzKYeyAXOep9AI9l7sE1KLiGnhY4YYjKvu0g4fYCPAQKYCY9fA52rC30kq yIIQ== MIME-Version: 1.0 X-Received: by 10.58.255.233 with SMTP id at9mr1548479ved.20.1390039262789; Sat, 18 Jan 2014 02:01:02 -0800 (PST) Received: by 10.221.45.136 with HTTP; Sat, 18 Jan 2014 02:01:02 -0800 (PST) In-Reply-To: <024D82BD-7332-48ED-ABC9-B028EFCD3F69@nottingham.ac.uk> References: <024D82BD-7332-48ED-ABC9-B028EFCD3F69@nottingham.ac.uk> Date: Sat, 18 Jan 2014 10:01:02 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen issues 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="===============2460620537503524560==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2460620537503524560== Content-Type: multipart/alternative; boundary=047d7bf15fc87b8c9f04f03bbc2b --047d7bf15fc87b8c9f04f03bbc2b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sat, Jan 18, 2014 at 12:28 AM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > having fixed the previous problem (with some assistance from dave :) i > can now build a xen image but not successfully start it. this is true of = my > website and of mirage/lib_test/basic. i get the output appended below > (trying to start the combinator example in mirage/mirage). > > i'm not very familiar with interpreting these logs -- anyone any > suggestions? > > root@greyjay-xen:~/mirage/mirage/lib_test/combinator# xl -v create mux.xl > -cd > Parsing config from mux.xl > > {"domid":null,"config":{"c_info":{"type":"pv","hap":"","oos":"","ssidref":0,"name":"mux","uuid":"dd23d957-6739-4215-bba8-313c99f20= 4b5","xsdata":{},"platformdata":{},"poolid":0,"run_hotplug_scripts":"True"}= ,"b_info":{"max_vcpus":0,"avail_vcpus":[],"cpumap":[],"numa_placement":"","tsc_mode":"default","max_memkb":262144,"target_memkb":262144,"vide= o_memkb":-1,"shadow_memkb":2048,"rtc_timeoffset":0,"localtime":"",= "disable_migrate":"","cpuid":[],"blkdev_start":null,"device_model_= version":null,"device_model_stubdomain":"","device_model":null,"de= vice_model_ssidref":0,"extra":[],"extra_pv":[],"extra_hvm":[],"sched_params= ":{"sched":"unknown","weight":-1,"cap":-1,"period":-1,"slice":-1,"latency":= -1,"extratime":-1},"ioports":[],"irqs":[],"u":{"kernel":"/home/mort/mirage/= mirage/lib_test/combinator/mir-mux.xen","slack_memkb":-1,"bootloader":null,= "bootloader_args":[],"cmdline":"","ramdisk":null,"e820_host":""}},= "disks":[],"nics":[],"pcidevs":[],"vfbs":[],"vkbs":[],"on_poweroff":"destro= y","on_reboot":"restart","on_watchdog":"destroy","on_crash":"destroy"}} > libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidat= e > with 1 nodes, 1 cpus and 438 KB free selected > I notice "disks:[]" and "nics:[]" -- are you expecting a disk or network interface? [ snipped domain building spam ] > domainbuilder: detail: launch_vm: called, ctxt=3D0x7fffa8c65820 > It went up ... > domainbuilder: detail: xc_dom_release: called > ... and down again > Daemon running with PID 16748 > libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain typ= e > for domid=3D10 > Unable to attach console > When the VM dies early on, xenconsoled cleans up the console before 'xl' can attach to it. There might be some interesting text on there. You can see it by starting the VM paused: xl create -c -p mux.xl and, in another terminal, unpausing it xl unpause mux Cheers, Dave --047d7bf15fc87b8c9f04f03bbc2b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Sat, Jan 18, 2014 at 12:28 AM, Richard Mortier <= ;Rich= ard.Mortier@nottingham.ac.uk> wrote:
having fixed the previous problem (with some= assistance from dave :) =A0i can now build a xen image but not successfull= y start it. this is true of my website and of mirage/lib_test/basic. =A0i g= et the output appended below (trying to start the combinator example in mir= age/mirage).

i'm not very familiar with interpreting these logs -- anyone any sugges= tions?

root@greyjay-xen:~/mirage/mirage/lib_test/combinator# xl -v create mux.xl -= cd
Parsing config from mux.xl
{"domid":null,"config":{"c_info":{"type&= quot;:"pv","hap":"<default>","oos&= quot;:"<default>","ssidref":0,"name":&q= uot;mux","uuid":"dd23d957-6739-4215-bba8-313c99f204b5&q= uot;,"xsdata":{},"platformdata":{},"poolid":0= ,"run_hotplug_scripts":"True"},"b_info":{&quo= t;max_vcpus":0,"avail_vcpus":[],"cpumap":[],"= numa_placement":"<default>","tsc_mode":"= ;default","max_memkb":262144,"target_memkb":262144= ,"video_memkb":-1,"shadow_memkb":2048,"rtc_timeoff= set":0,"localtime":"<default>","disable= _migrate":"<default>","cpuid":[],"blkde= v_start":null,"device_model_version":null,"device_model= _stubdomain":"<default>","device_model":null= ,"device_model_ssidref":0,"extra":[],"extra_pv&quo= t;:[],"extra_hvm":[],"sched_params":{"sched":= "unknown","weight":-1,"cap":-1,"period&q= uot;:-1,"slice":-1,"latency":-1,"extratime":-= 1},"ioports":[],"irqs":[],"u":{"kernel&q= uot;:"/home/mort/mirage/mirage/lib_test/combinator/mir-mux.xen",&= quot;slack_memkb":-1,"bootloader":null,"bootloader_args= ":[],"cmdline":"","ramdisk":null,"e= 820_host":"<default>"}},"disks":[],"nic= s":[],"pcidevs":[],"vfbs":[],"vkbs":[],&= quot;on_poweroff":"destroy","on_reboot":"rest= art","on_watchdog":"destroy","on_crash":= "destroy"}}
libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate = with 1 nodes, 1 cpus and 438 KB free selected

I notice "disks:[]" and "nics:[]" -- are you exp= ecting a disk or network interface?
=A0
[ snipped domain building spam ]
domainbuilder: detail: launch_vm: called, ctxt=3D0x7fffa8c658= 20

It went up ...
=A0
domainbuilder: detail: xc_dom_release: called

... and down again
=A0
Daemon running with PID 16748
libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type = for domid=3D10
Unable to attach console

When the VM di= es early on, xenconsoled cleans up the console before 'xl' can atta= ch to it. There might be some interesting text on there. You can see it by = starting the VM paused:

xl create -c -p mux.xl

and, in= another terminal, unpausing it

xl unpause mux

Cheers,
Dave
--047d7bf15fc87b8c9f04f03bbc2b-- --===============2460620537503524560== 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 --===============2460620537503524560==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jan 18 10:01:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 10:01: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 1W4SiC-0006hP-9Q; Sat, 18 Jan 2014 10:01:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4SiA-0006hH-0U for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 10:01:06 +0000 Received: from [193.109.254.147:26629] by server-6.bemta-14.messagelabs.com id 99/3B-14958-1E05AD25; Sat, 18 Jan 2014 10:01:05 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1390039263!11683606!1 X-Originating-IP: [209.85.220.169] 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 21945 invoked from network); 18 Jan 2014 10:01:04 -0000 Received: from mail-vc0-f169.google.com (HELO mail-vc0-f169.google.com) (209.85.220.169) by server-6.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 10:01:04 -0000 Received: by mail-vc0-f169.google.com with SMTP id hq11so1988254vcb.14 for ; Sat, 18 Jan 2014 02:01: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=mD4Pd528Y2QmzffH8BAaR1dqWYzMbeuXlP3xK8h9V+k=; b=lSZ+6ApmLWC42rt4Xlw6qLYp/BtfAlDtfeg+E0g/+PzHthtqOykRPwi21hcL2vJi8C pYWZrHsgLBq65i8dkBbYbWkQqxkLVLp+JNRpLyCZRj9kZlCanDCbTbJzMlsSyQ7tzBCX nMrjIiIgYM34RYbRMjRZ8NwqkbKVEodFw935RMkqMdsi02UqVg26OPZwF/J5i49g+Ntw 1KVIRP5LCh4O2DJxIcKYPPgq9Gzxhyqqhfr3tqreiDshM8WIHPLozsQWGVN6Fd9f/XtG wMyIbZWshOLzKYeyAXOep9AI9l7sE1KLiGnhY4YYjKvu0g4fYCPAQKYCY9fA52rC30kq yIIQ== MIME-Version: 1.0 X-Received: by 10.58.255.233 with SMTP id at9mr1548479ved.20.1390039262789; Sat, 18 Jan 2014 02:01:02 -0800 (PST) Received: by 10.221.45.136 with HTTP; Sat, 18 Jan 2014 02:01:02 -0800 (PST) In-Reply-To: <024D82BD-7332-48ED-ABC9-B028EFCD3F69@nottingham.ac.uk> References: <024D82BD-7332-48ED-ABC9-B028EFCD3F69@nottingham.ac.uk> Date: Sat, 18 Jan 2014 10:01:02 +0000 Message-ID: From: David Scott To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen issues 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="===============2460620537503524560==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2460620537503524560== Content-Type: multipart/alternative; boundary=047d7bf15fc87b8c9f04f03bbc2b --047d7bf15fc87b8c9f04f03bbc2b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sat, Jan 18, 2014 at 12:28 AM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > having fixed the previous problem (with some assistance from dave :) i > can now build a xen image but not successfully start it. this is true of = my > website and of mirage/lib_test/basic. i get the output appended below > (trying to start the combinator example in mirage/mirage). > > i'm not very familiar with interpreting these logs -- anyone any > suggestions? > > root@greyjay-xen:~/mirage/mirage/lib_test/combinator# xl -v create mux.xl > -cd > Parsing config from mux.xl > > {"domid":null,"config":{"c_info":{"type":"pv","hap":"","oos":"","ssidref":0,"name":"mux","uuid":"dd23d957-6739-4215-bba8-313c99f20= 4b5","xsdata":{},"platformdata":{},"poolid":0,"run_hotplug_scripts":"True"}= ,"b_info":{"max_vcpus":0,"avail_vcpus":[],"cpumap":[],"numa_placement":"","tsc_mode":"default","max_memkb":262144,"target_memkb":262144,"vide= o_memkb":-1,"shadow_memkb":2048,"rtc_timeoffset":0,"localtime":"",= "disable_migrate":"","cpuid":[],"blkdev_start":null,"device_model_= version":null,"device_model_stubdomain":"","device_model":null,"de= vice_model_ssidref":0,"extra":[],"extra_pv":[],"extra_hvm":[],"sched_params= ":{"sched":"unknown","weight":-1,"cap":-1,"period":-1,"slice":-1,"latency":= -1,"extratime":-1},"ioports":[],"irqs":[],"u":{"kernel":"/home/mort/mirage/= mirage/lib_test/combinator/mir-mux.xen","slack_memkb":-1,"bootloader":null,= "bootloader_args":[],"cmdline":"","ramdisk":null,"e820_host":""}},= "disks":[],"nics":[],"pcidevs":[],"vfbs":[],"vkbs":[],"on_poweroff":"destro= y","on_reboot":"restart","on_watchdog":"destroy","on_crash":"destroy"}} > libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidat= e > with 1 nodes, 1 cpus and 438 KB free selected > I notice "disks:[]" and "nics:[]" -- are you expecting a disk or network interface? [ snipped domain building spam ] > domainbuilder: detail: launch_vm: called, ctxt=3D0x7fffa8c65820 > It went up ... > domainbuilder: detail: xc_dom_release: called > ... and down again > Daemon running with PID 16748 > libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain typ= e > for domid=3D10 > Unable to attach console > When the VM dies early on, xenconsoled cleans up the console before 'xl' can attach to it. There might be some interesting text on there. You can see it by starting the VM paused: xl create -c -p mux.xl and, in another terminal, unpausing it xl unpause mux Cheers, Dave --047d7bf15fc87b8c9f04f03bbc2b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Sat, Jan 18, 2014 at 12:28 AM, Richard Mortier <= ;Rich= ard.Mortier@nottingham.ac.uk> wrote:
having fixed the previous problem (with some= assistance from dave :) =A0i can now build a xen image but not successfull= y start it. this is true of my website and of mirage/lib_test/basic. =A0i g= et the output appended below (trying to start the combinator example in mir= age/mirage).

i'm not very familiar with interpreting these logs -- anyone any sugges= tions?

root@greyjay-xen:~/mirage/mirage/lib_test/combinator# xl -v create mux.xl -= cd
Parsing config from mux.xl
{"domid":null,"config":{"c_info":{"type&= quot;:"pv","hap":"<default>","oos&= quot;:"<default>","ssidref":0,"name":&q= uot;mux","uuid":"dd23d957-6739-4215-bba8-313c99f204b5&q= uot;,"xsdata":{},"platformdata":{},"poolid":0= ,"run_hotplug_scripts":"True"},"b_info":{&quo= t;max_vcpus":0,"avail_vcpus":[],"cpumap":[],"= numa_placement":"<default>","tsc_mode":"= ;default","max_memkb":262144,"target_memkb":262144= ,"video_memkb":-1,"shadow_memkb":2048,"rtc_timeoff= set":0,"localtime":"<default>","disable= _migrate":"<default>","cpuid":[],"blkde= v_start":null,"device_model_version":null,"device_model= _stubdomain":"<default>","device_model":null= ,"device_model_ssidref":0,"extra":[],"extra_pv&quo= t;:[],"extra_hvm":[],"sched_params":{"sched":= "unknown","weight":-1,"cap":-1,"period&q= uot;:-1,"slice":-1,"latency":-1,"extratime":-= 1},"ioports":[],"irqs":[],"u":{"kernel&q= uot;:"/home/mort/mirage/mirage/lib_test/combinator/mir-mux.xen",&= quot;slack_memkb":-1,"bootloader":null,"bootloader_args= ":[],"cmdline":"","ramdisk":null,"e= 820_host":"<default>"}},"disks":[],"nic= s":[],"pcidevs":[],"vfbs":[],"vkbs":[],&= quot;on_poweroff":"destroy","on_reboot":"rest= art","on_watchdog":"destroy","on_crash":= "destroy"}}
libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate = with 1 nodes, 1 cpus and 438 KB free selected

I notice "disks:[]" and "nics:[]" -- are you exp= ecting a disk or network interface?
=A0
[ snipped domain building spam ]
domainbuilder: detail: launch_vm: called, ctxt=3D0x7fffa8c658= 20

It went up ...
=A0
domainbuilder: detail: xc_dom_release: called

... and down again
=A0
Daemon running with PID 16748
libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type = for domid=3D10
Unable to attach console

When the VM di= es early on, xenconsoled cleans up the console before 'xl' can atta= ch to it. There might be some interesting text on there. You can see it by = starting the VM paused:

xl create -c -p mux.xl

and, in= another terminal, unpausing it

xl unpause mux

Cheers,
Dave
--047d7bf15fc87b8c9f04f03bbc2b-- --===============2460620537503524560== 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 --===============2460620537503524560==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jan 18 11:48:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 11:48: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 1W4UNu-0002pb-AP; Sat, 18 Jan 2014 11:48:18 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4UNt-0002pW-QW for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 11:48:18 +0000 Received: from [85.158.139.211:52260] by server-8.bemta-5.messagelabs.com id 74/AA-29838-00A6AD25; Sat, 18 Jan 2014 11:48:16 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-3.tower-206.messagelabs.com!1390045695!10332634!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 27953 invoked from network); 18 Jan 2014 11:48:15 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-3.tower-206.messagelabs.com with SMTP; 18 Jan 2014 11:48:15 -0000 Received: (qmail 13531 invoked from network); 18 Jan 2014 11:48:15 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 18 Jan 2014 11:48:15 -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 13365-01 for ; Sat, 18 Jan 2014 11:48:13 +0000 (GMT) Received: (qmail 13516 invoked by uid 599); 18 Jan 2014 11:48:12 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 11:48:12 +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 1W4UNn-0005m9-V5; Sat, 18 Jan 2014 11:48:11 +0000 From: Richard Mortier To: David Scott Date: Sat, 18 Jan 2014 11:48:10 +0000 Thread-Topic: [MirageOS-devel] xen issues Thread-Index: Ac8UQymOWHoGOqlnTWWBzbogipvwOQ== Message-ID: References: <024D82BD-7332-48ED-ABC9-B028EFCD3F69@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 engine06-20433-6.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen issues 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 18 Jan 2014, at 10:01, David Scott wrote: > On Sat, Jan 18, 2014 at 12:28 AM, Richard Mortier wrote: >> ...libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate with 1 nodes, 1 cpus and 438 KB free selected > > I notice "disks:[]" and "nics:[]" -- are you expecting a disk or network interface? i wasn't, but it turns out i should've been... :) > Daemon running with PID 16748 > libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type for domid=10 > Unable to attach console > > When the VM dies early on, xenconsoled cleans up the console before 'xl' can attach to it. There might be some interesting text on there. You can see it by starting the VM paused: > > xl create -c -p mux.xl > > and, in another terminal, unpausing it > > xl unpause mux thanks-- should've remembered that from earlier posts i think. is xen.org generally the best place for docs on this basic process stuff, or is there a canonical dummies guide online anywhere? fwiw the output from that shows that indeed, it's dying because it's missing a block device (one of many). i'll have a poke at the .xl file... -- 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 Jan 18 11:48:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 11:48: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 1W4UNu-0002pb-AP; Sat, 18 Jan 2014 11:48:18 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4UNt-0002pW-QW for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 11:48:18 +0000 Received: from [85.158.139.211:52260] by server-8.bemta-5.messagelabs.com id 74/AA-29838-00A6AD25; Sat, 18 Jan 2014 11:48:16 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-3.tower-206.messagelabs.com!1390045695!10332634!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 27953 invoked from network); 18 Jan 2014 11:48:15 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-3.tower-206.messagelabs.com with SMTP; 18 Jan 2014 11:48:15 -0000 Received: (qmail 13531 invoked from network); 18 Jan 2014 11:48:15 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 18 Jan 2014 11:48:15 -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 13365-01 for ; Sat, 18 Jan 2014 11:48:13 +0000 (GMT) Received: (qmail 13516 invoked by uid 599); 18 Jan 2014 11:48:12 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 11:48:12 +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 1W4UNn-0005m9-V5; Sat, 18 Jan 2014 11:48:11 +0000 From: Richard Mortier To: David Scott Date: Sat, 18 Jan 2014 11:48:10 +0000 Thread-Topic: [MirageOS-devel] xen issues Thread-Index: Ac8UQymOWHoGOqlnTWWBzbogipvwOQ== Message-ID: References: <024D82BD-7332-48ED-ABC9-B028EFCD3F69@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 engine06-20433-6.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen issues 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 18 Jan 2014, at 10:01, David Scott wrote: > On Sat, Jan 18, 2014 at 12:28 AM, Richard Mortier wrote: >> ...libxl: detail: libxl_dom.c:193:numa_place_domain: NUMA placement candidate with 1 nodes, 1 cpus and 438 KB free selected > > I notice "disks:[]" and "nics:[]" -- are you expecting a disk or network interface? i wasn't, but it turns out i should've been... :) > Daemon running with PID 16748 > libxl: error: libxl_dom.c:35:libxl__domain_type: unable to get domain type for domid=10 > Unable to attach console > > When the VM dies early on, xenconsoled cleans up the console before 'xl' can attach to it. There might be some interesting text on there. You can see it by starting the VM paused: > > xl create -c -p mux.xl > > and, in another terminal, unpausing it > > xl unpause mux thanks-- should've remembered that from earlier posts i think. is xen.org generally the best place for docs on this basic process stuff, or is there a canonical dummies guide online anywhere? fwiw the output from that shows that indeed, it's dying because it's missing a block device (one of many). i'll have a poke at the .xl file... -- 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 Jan 18 15:35:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 15:35: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 1W4Xvx-0005rW-2f; Sat, 18 Jan 2014 15:35:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Xvv-0005rR-Ri for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 15:35:40 +0000 Received: from [85.158.139.211:42745] by server-2.bemta-5.messagelabs.com id 12/94-29392-A4F9AD25; Sat, 18 Jan 2014 15:35:38 +0000 X-Env-Sender: francois.armand.fa@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1390059336!10558233!1 X-Originating-IP: [209.85.223.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,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 4103 invoked from network); 18 Jan 2014 15:35:37 -0000 Received: from mail-ie0-f177.google.com (HELO mail-ie0-f177.google.com) (209.85.223.177) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 15:35:37 -0000 Received: by mail-ie0-f177.google.com with SMTP id at1so3752771iec.36 for ; Sat, 18 Jan 2014 07:35:36 -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=wz11+QF4rgTqcLJ7mlhWDQhEQcQlUKV0Bar3MyyrkIo=; b=l7vLt9Ld4rKipM/cVvEYYEuU5+zuze2sCM0fuId+e1grz7vCu/6zeKXlCU0aomXO4f RLLYR/o65NhAvUfacFmZaOIYcC6tlD3fFYMFBmGLHo6Y18yImqNF2ku6WJjVUE9gGWSZ FSoMUx8ig25RVgPmBygd6o5JiCfRLoKX8MC+DxEK8jTRYm2EUpkR19ItmwD0KXJzNtzS RnypE0gYkLNElbyKjHm6EsilH8RegIPg+FhpCnpn8nEhJ6y4etYTCw9JN9K+aFD2lhb4 kr4TXaFliujIVB9HZtIZQ4hdnVmZs3NHYT13GGuMqZO3AnoY6QqR0PV2JEKtzQ4W+ipr 0nTQ== MIME-Version: 1.0 X-Received: by 10.42.64.17 with SMTP id e17mr6693724ici.26.1390059336475; Sat, 18 Jan 2014 07:35:36 -0800 (PST) Received: by 10.64.26.132 with HTTP; Sat, 18 Jan 2014 07:35:36 -0800 (PST) Date: Sat, 18 Jan 2014 16:35:36 +0100 Message-ID: From: =?ISO-8859-1?Q?Fran=E7ois_Armand?= To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Which version of Xen for MirageOS? 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="===============1052394550196635065==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1052394550196635065== Content-Type: multipart/alternative; boundary=90e6ba3fcdabf7ac0804f040685b --90e6ba3fcdabf7ac0804f040685b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, I apologize if this mailing list is not the right place for my question. I'm starting playing with MirageOS. I succeeded running the "hello Wolrd" as a Posix process and would like to move to Xen. Hence I need to set up a Xen environment... I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveCD be OK to further experiment the MirageOS or will I waste my time? Thanks in advance for your reply, Fran=E7ois --90e6ba3fcdabf7ac0804f040685b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

I apologize if this mai= ling list is not the right place for my question.

I'm star= ting playing with MirageOS. I succeeded=A0 running the "hello Wolrd&qu= ot; as a Posix process and would like to move to Xen. Hence I need to set u= p a Xen environment... I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen= LiveCD be OK to=A0 further experiment the MirageOS or will I waste my time= ?

Thanks in advance for your reply,

Fran=E7ois
--90e6ba3fcdabf7ac0804f040685b-- --===============1052394550196635065== 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 --===============1052394550196635065==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jan 18 15:35:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 15:35: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 1W4Xvx-0005rW-2f; Sat, 18 Jan 2014 15:35:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Xvv-0005rR-Ri for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 15:35:40 +0000 Received: from [85.158.139.211:42745] by server-2.bemta-5.messagelabs.com id 12/94-29392-A4F9AD25; Sat, 18 Jan 2014 15:35:38 +0000 X-Env-Sender: francois.armand.fa@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1390059336!10558233!1 X-Originating-IP: [209.85.223.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,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 4103 invoked from network); 18 Jan 2014 15:35:37 -0000 Received: from mail-ie0-f177.google.com (HELO mail-ie0-f177.google.com) (209.85.223.177) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 15:35:37 -0000 Received: by mail-ie0-f177.google.com with SMTP id at1so3752771iec.36 for ; Sat, 18 Jan 2014 07:35:36 -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=wz11+QF4rgTqcLJ7mlhWDQhEQcQlUKV0Bar3MyyrkIo=; b=l7vLt9Ld4rKipM/cVvEYYEuU5+zuze2sCM0fuId+e1grz7vCu/6zeKXlCU0aomXO4f RLLYR/o65NhAvUfacFmZaOIYcC6tlD3fFYMFBmGLHo6Y18yImqNF2ku6WJjVUE9gGWSZ FSoMUx8ig25RVgPmBygd6o5JiCfRLoKX8MC+DxEK8jTRYm2EUpkR19ItmwD0KXJzNtzS RnypE0gYkLNElbyKjHm6EsilH8RegIPg+FhpCnpn8nEhJ6y4etYTCw9JN9K+aFD2lhb4 kr4TXaFliujIVB9HZtIZQ4hdnVmZs3NHYT13GGuMqZO3AnoY6QqR0PV2JEKtzQ4W+ipr 0nTQ== MIME-Version: 1.0 X-Received: by 10.42.64.17 with SMTP id e17mr6693724ici.26.1390059336475; Sat, 18 Jan 2014 07:35:36 -0800 (PST) Received: by 10.64.26.132 with HTTP; Sat, 18 Jan 2014 07:35:36 -0800 (PST) Date: Sat, 18 Jan 2014 16:35:36 +0100 Message-ID: From: =?ISO-8859-1?Q?Fran=E7ois_Armand?= To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Which version of Xen for MirageOS? 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="===============1052394550196635065==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1052394550196635065== Content-Type: multipart/alternative; boundary=90e6ba3fcdabf7ac0804f040685b --90e6ba3fcdabf7ac0804f040685b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, I apologize if this mailing list is not the right place for my question. I'm starting playing with MirageOS. I succeeded running the "hello Wolrd" as a Posix process and would like to move to Xen. Hence I need to set up a Xen environment... I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveCD be OK to further experiment the MirageOS or will I waste my time? Thanks in advance for your reply, Fran=E7ois --90e6ba3fcdabf7ac0804f040685b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

I apologize if this mai= ling list is not the right place for my question.

I'm star= ting playing with MirageOS. I succeeded=A0 running the "hello Wolrd&qu= ot; as a Posix process and would like to move to Xen. Hence I need to set u= p a Xen environment... I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen= LiveCD be OK to=A0 further experiment the MirageOS or will I waste my time= ?

Thanks in advance for your reply,

Fran=E7ois
--90e6ba3fcdabf7ac0804f040685b-- --===============1052394550196635065== 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 --===============1052394550196635065==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jan 18 15:39:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 15:39:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Y05-0006Ac-F4; Sat, 18 Jan 2014 15:39:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Y03-0006AX-Hg for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 15:39:55 +0000 Received: from [85.158.139.211:2021] by server-11.bemta-5.messagelabs.com id 13/3D-23268-A40AAD25; Sat, 18 Jan 2014 15:39:54 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-206.messagelabs.com!1390059594!10554882!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 1737 invoked from network); 18 Jan 2014 15:39:54 -0000 Received: from engine02-20433-2.icritical.com (HELO engine02-20433-2.icritical.com) (195.62.217.151) by server-10.tower-206.messagelabs.com with SMTP; 18 Jan 2014 15:39:54 -0000 Received: (qmail 18047 invoked from network); 18 Jan 2014 15:39:49 -0000 Received: from localhost (127.0.0.1) by engine02-20433-2.icritical.com with SMTP; 18 Jan 2014 15:39:49 -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 17442-06 for ; Sat, 18 Jan 2014 15:39:47 +0000 (GMT) Received: (qmail 18036 invoked by uid 599); 18 Jan 2014 15:39:47 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 15:39:47 +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 1W4Xzz-0001eH-4x; Sat, 18 Jan 2014 15:39:51 +0000 From: Richard Mortier To: =?iso-8859-1?Q?Fran=E7ois_Armand?= Date: Sat, 18 Jan 2014 15:39:50 +0000 Thread-Topic: [MirageOS-devel] Which version of Xen for MirageOS? Thread-Index: Ac8UY4Y6befVp/q/R4Kn3om2hVvrtA== Message-ID: 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 engine02-20433-2.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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 18 Jan 2014, at 15:35, Fran=E7ois Armand wrote: > I apologize if this mailing list is not the right place for my question. no problem, this is the right place :) > I'm starting playing with MirageOS. I succeeded running the "hello Wolrd= " as a Posix process cool! hopefully the install and hello-world instructions are iterating tow= ards being mostly correct then :) (assuming you used those?) > and would like to move to Xen. Hence I need to set up a Xen environment..= . I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveCD be OK to fur= ther experiment the MirageOS or will I waste my time? as i understand it, either should work -- personally i experiment using Xen= 4.2 on ubuntu 13.04 (inside a Virtualbox VM on my mac)... i'd say give 4.= 0 a try (others have more experience Xen on the list than me though). -- = Cheers, R. This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, 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 Jan 18 15:39:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 15:39:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Y05-0006Ac-F4; Sat, 18 Jan 2014 15:39:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Y03-0006AX-Hg for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 15:39:55 +0000 Received: from [85.158.139.211:2021] by server-11.bemta-5.messagelabs.com id 13/3D-23268-A40AAD25; Sat, 18 Jan 2014 15:39:54 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-206.messagelabs.com!1390059594!10554882!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 1737 invoked from network); 18 Jan 2014 15:39:54 -0000 Received: from engine02-20433-2.icritical.com (HELO engine02-20433-2.icritical.com) (195.62.217.151) by server-10.tower-206.messagelabs.com with SMTP; 18 Jan 2014 15:39:54 -0000 Received: (qmail 18047 invoked from network); 18 Jan 2014 15:39:49 -0000 Received: from localhost (127.0.0.1) by engine02-20433-2.icritical.com with SMTP; 18 Jan 2014 15:39:49 -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 17442-06 for ; Sat, 18 Jan 2014 15:39:47 +0000 (GMT) Received: (qmail 18036 invoked by uid 599); 18 Jan 2014 15:39:47 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 15:39:47 +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 1W4Xzz-0001eH-4x; Sat, 18 Jan 2014 15:39:51 +0000 From: Richard Mortier To: =?iso-8859-1?Q?Fran=E7ois_Armand?= Date: Sat, 18 Jan 2014 15:39:50 +0000 Thread-Topic: [MirageOS-devel] Which version of Xen for MirageOS? Thread-Index: Ac8UY4Y6befVp/q/R4Kn3om2hVvrtA== Message-ID: 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 engine02-20433-2.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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 18 Jan 2014, at 15:35, Fran=E7ois Armand wrote: > I apologize if this mailing list is not the right place for my question. no problem, this is the right place :) > I'm starting playing with MirageOS. I succeeded running the "hello Wolrd= " as a Posix process cool! hopefully the install and hello-world instructions are iterating tow= ards being mostly correct then :) (assuming you used those?) > and would like to move to Xen. Hence I need to set up a Xen environment..= . I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveCD be OK to fur= ther experiment the MirageOS or will I waste my time? as i understand it, either should work -- personally i experiment using Xen= 4.2 on ubuntu 13.04 (inside a Virtualbox VM on my mac)... i'd say give 4.= 0 a try (others have more experience Xen on the list than me though). -- = Cheers, R. This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, 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 Jan 18 15:42:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 15:42: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 1W4Y23-0006VK-MA; Sat, 18 Jan 2014 15:41:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Y22-0006VF-6a for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 15:41:58 +0000 Received: from [85.158.143.35:11936] by server-2.bemta-4.messagelabs.com id B0/27-11386-5C0AAD25; Sat, 18 Jan 2014 15:41:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-21.messagelabs.com!1390059716!12415049!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 11839 invoked from network); 18 Jan 2014 15:41:56 -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; 18 Jan 2014 15:41:56 -0000 Received: (qmail 2608 invoked by uid 634); 18 Jan 2014 15:41:55 -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, 18 Jan 2014 15:41:54 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 18 Jan 2014 15:41:51 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: =?iso-8859-1?Q?Fran=E7ois_Armand?= , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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 18 Jan 2014, at 15:39, Richard Mortier wrote: > = > On 18 Jan 2014, at 15:35, Fran=E7ois Armand wrote: > = >> I apologize if this mailing list is not the right place for my question. > = > no problem, this is the right place :) > = >> I'm starting playing with MirageOS. I succeeded running the "hello Wolr= d" as a Posix process > = > cool! hopefully the install and hello-world instructions are iterating t= owards being mostly correct then :) (assuming you used those?) > = >> and would like to move to Xen. Hence I need to set up a Xen environment.= .. I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveCD be OK to fu= rther experiment the MirageOS or will I waste my time? > = > as i understand it, either should work -- personally i experiment using X= en 4.2 on ubuntu 13.04 (inside a Virtualbox VM on my mac)... i'd say give = 4.0 a try (others have more experience Xen on the list than me though). I'd recommend Xen 4.2 on Ubuntu 13.04 as well... I haven't tried the LiveCD= for quite some time. -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 Jan 18 15:42:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 15:42: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 1W4Y23-0006VK-MA; Sat, 18 Jan 2014 15:41:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Y22-0006VF-6a for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 15:41:58 +0000 Received: from [85.158.143.35:11936] by server-2.bemta-4.messagelabs.com id B0/27-11386-5C0AAD25; Sat, 18 Jan 2014 15:41:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-21.messagelabs.com!1390059716!12415049!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 11839 invoked from network); 18 Jan 2014 15:41:56 -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; 18 Jan 2014 15:41:56 -0000 Received: (qmail 2608 invoked by uid 634); 18 Jan 2014 15:41:55 -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, 18 Jan 2014 15:41:54 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 18 Jan 2014 15:41:51 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: =?iso-8859-1?Q?Fran=E7ois_Armand?= , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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 18 Jan 2014, at 15:39, Richard Mortier wrote: > = > On 18 Jan 2014, at 15:35, Fran=E7ois Armand wrote: > = >> I apologize if this mailing list is not the right place for my question. > = > no problem, this is the right place :) > = >> I'm starting playing with MirageOS. I succeeded running the "hello Wolr= d" as a Posix process > = > cool! hopefully the install and hello-world instructions are iterating t= owards being mostly correct then :) (assuming you used those?) > = >> and would like to move to Xen. Hence I need to set up a Xen environment.= .. I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveCD be OK to fu= rther experiment the MirageOS or will I waste my time? > = > as i understand it, either should work -- personally i experiment using X= en 4.2 on ubuntu 13.04 (inside a Virtualbox VM on my mac)... i'd say give = 4.0 a try (others have more experience Xen on the list than me though). I'd recommend Xen 4.2 on Ubuntu 13.04 as well... I haven't tried the LiveCD= for quite some time. -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 Jan 18 15:53:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 15:53:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YDc-0006xE-L9; Sat, 18 Jan 2014 15:53:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YDb-0006x9-5U for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 15:53:55 +0000 Received: from [85.158.139.211:54298] by server-11.bemta-5.messagelabs.com id 45/41-23268-293AAD25; Sat, 18 Jan 2014 15:53:54 +0000 X-Env-Sender: francois.armand.fa@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1390060431!247489!1 X-Originating-IP: [209.85.223.179] 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 15037 invoked from network); 18 Jan 2014 15:53:53 -0000 Received: from mail-ie0-f179.google.com (HELO mail-ie0-f179.google.com) (209.85.223.179) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 15:53:53 -0000 Received: by mail-ie0-f179.google.com with SMTP id ar20so1923706iec.24 for ; Sat, 18 Jan 2014 07:53:51 -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=obDiWJJOpuF9Cnf0iwRzHjOdqBWG8raOWreIGGl91zI=; b=Jbjt0F+qOLtwSBJxbRlX/kw20LZEnCeylTvH9tecZ65UGNp6N4pWT7TBJOV54pnvZb wNEuolRkr4xHblrNKSj7iWCDws9CUGbFm5Q7gY3lyzEur8zQHNWClIlbUCMPfZSVds8j Iobi14UPvSRaxou0EHfwvKX5nX3Riw6hHxu/m4+qCdTtmt5oGVdjoO/K0fucxs1nAMFa BltiLIjOiA/YEle5jQ9p8rJAHjesWZlgJwFuL5iVb959MrLUUR18bKcvmw6peFFxhZ4X +srnrjwklr9OWksFPb3drEWrkCWHaHUwFWQ4E9At4PnfAwuGHriDOwlkDOgXettOx0Nt LbFg== MIME-Version: 1.0 X-Received: by 10.43.182.74 with SMTP id pl10mr788559icc.70.1390060431635; Sat, 18 Jan 2014 07:53:51 -0800 (PST) Received: by 10.64.26.132 with HTTP; Sat, 18 Jan 2014 07:53:51 -0800 (PST) In-Reply-To: References: Date: Sat, 18 Jan 2014 16:53:51 +0100 Message-ID: From: =?ISO-8859-1?Q?Fran=E7ois_Armand?= To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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="===============7854319852650263149==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7854319852650263149== Content-Type: multipart/alternative; boundary=001a11c357c83e77de04f040aab4 --001a11c357c83e77de04f040aab4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks a lot! Wait! If I understand well enough your own setup, I don't need to run on bare metal! I missed the point, and apologize about that. If I recap: - start a VirtualBox VM with a Linux distrib (presumably 64 bits) - install Xen 4.2 inside that VM, so I guess in your case your Ubuntu 13.04 is running within your Dom0 - run MirageOS inside a Xen VM - which works because it's using the PV approach, I guess - I won't be able to run a native Linux distrib in a DomU... but I don't care. If that works, you saved my day! No need for any Intel-VT or AMD-SVM support! Thanks again Fran=E7ois 2014/1/18 Richard Mortier > > On 18 Jan 2014, at 15:35, Fran=E7ois Armand wrote: > > > I apologize if this mailing list is not the right place for my question= . > > no problem, this is the right place :) > > > I'm starting playing with MirageOS. I succeeded running the "hello > Wolrd" as a Posix process > > cool! hopefully the install and hello-world instructions are iterating > towards being mostly correct then :) (assuming you used those?) > > > and would like to move to Xen. Hence I need to set up a Xen > environment... I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveC= D > be OK to further experiment the MirageOS or will I waste my time? > > as i understand it, either should work -- personally i experiment using > Xen 4.2 on ubuntu 13.04 (inside a Virtualbox VM on my mac)... i'd say gi= ve > 4.0 a try (others have more experience Xen on the list than me though). > > -- > Cheers, > > R. > > > > > This message and any attachment are intended solely for the addressee and > may contain confidential information. If you have received this message i= n > 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 Nottingha= m. > > This message has been checked for viruses but the contents of an attachme= nt > 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. > > > > > --001a11c357c83e77de04f040aab4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Tha= nks a lot!
Wait! If I understand well enough your own setup, I don= 't need to run on bare metal!
I missed the point, and apologiz= e about that.

If I recap:
=A0- start a VirtualBox VM with a Linux dist= rib (presumably 64 bits)
=A0- install Xen 4.2 inside that VM, so I= guess in your case your Ubuntu 13.04 is running within your Dom0
=A0- run MirageOS inside a Xen VM
=A0=A0 - which works because it&= #39;s using the PV approach, I guess
=A0- I won't be able to r= un a native Linux distrib in a DomU... but I don't care.

I= f that works, you saved my day! No need for any Intel-VT or AMD-SVM support= !
Thanks again
Fran=E7ois
=

2014/1/18 Richard Mortier <Richard.Mortier@nottingham.ac.uk>

On 18 Jan 2014, at 15:35, Fran=E7ois Armand wrote:

> I apologize if this mailing list is not the right place for my questio= n.

no problem, this is the right place :)

> I'm starting playing with MirageOS. I succeeded =A0running the &qu= ot;hello Wolrd" as a Posix process

cool! =A0hopefully the install and hello-world instructions are itera= ting towards being mostly correct then :) =A0(assuming you used those?)

> and would like to move to Xen. Hence I need to set up a Xen environmen= t... I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveCD be OK to = =A0further experiment the MirageOS or will I waste my time?

as i understand it, either should work -- personally i experiment usi= ng Xen 4.2 on ubuntu 13.04 (inside a Virtualbox VM on my mac)... =A0i'd= say give 4.0 a try (others have more experience Xen on the list than me th= ough).

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l 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.




--001a11c357c83e77de04f040aab4-- --===============7854319852650263149== 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 --===============7854319852650263149==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jan 18 15:53:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 15:53:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YDc-0006xE-L9; Sat, 18 Jan 2014 15:53:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YDb-0006x9-5U for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 15:53:55 +0000 Received: from [85.158.139.211:54298] by server-11.bemta-5.messagelabs.com id 45/41-23268-293AAD25; Sat, 18 Jan 2014 15:53:54 +0000 X-Env-Sender: francois.armand.fa@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1390060431!247489!1 X-Originating-IP: [209.85.223.179] 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 15037 invoked from network); 18 Jan 2014 15:53:53 -0000 Received: from mail-ie0-f179.google.com (HELO mail-ie0-f179.google.com) (209.85.223.179) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 15:53:53 -0000 Received: by mail-ie0-f179.google.com with SMTP id ar20so1923706iec.24 for ; Sat, 18 Jan 2014 07:53:51 -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=obDiWJJOpuF9Cnf0iwRzHjOdqBWG8raOWreIGGl91zI=; b=Jbjt0F+qOLtwSBJxbRlX/kw20LZEnCeylTvH9tecZ65UGNp6N4pWT7TBJOV54pnvZb wNEuolRkr4xHblrNKSj7iWCDws9CUGbFm5Q7gY3lyzEur8zQHNWClIlbUCMPfZSVds8j Iobi14UPvSRaxou0EHfwvKX5nX3Riw6hHxu/m4+qCdTtmt5oGVdjoO/K0fucxs1nAMFa BltiLIjOiA/YEle5jQ9p8rJAHjesWZlgJwFuL5iVb959MrLUUR18bKcvmw6peFFxhZ4X +srnrjwklr9OWksFPb3drEWrkCWHaHUwFWQ4E9At4PnfAwuGHriDOwlkDOgXettOx0Nt LbFg== MIME-Version: 1.0 X-Received: by 10.43.182.74 with SMTP id pl10mr788559icc.70.1390060431635; Sat, 18 Jan 2014 07:53:51 -0800 (PST) Received: by 10.64.26.132 with HTTP; Sat, 18 Jan 2014 07:53:51 -0800 (PST) In-Reply-To: References: Date: Sat, 18 Jan 2014 16:53:51 +0100 Message-ID: From: =?ISO-8859-1?Q?Fran=E7ois_Armand?= To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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="===============7854319852650263149==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7854319852650263149== Content-Type: multipart/alternative; boundary=001a11c357c83e77de04f040aab4 --001a11c357c83e77de04f040aab4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks a lot! Wait! If I understand well enough your own setup, I don't need to run on bare metal! I missed the point, and apologize about that. If I recap: - start a VirtualBox VM with a Linux distrib (presumably 64 bits) - install Xen 4.2 inside that VM, so I guess in your case your Ubuntu 13.04 is running within your Dom0 - run MirageOS inside a Xen VM - which works because it's using the PV approach, I guess - I won't be able to run a native Linux distrib in a DomU... but I don't care. If that works, you saved my day! No need for any Intel-VT or AMD-SVM support! Thanks again Fran=E7ois 2014/1/18 Richard Mortier > > On 18 Jan 2014, at 15:35, Fran=E7ois Armand wrote: > > > I apologize if this mailing list is not the right place for my question= . > > no problem, this is the right place :) > > > I'm starting playing with MirageOS. I succeeded running the "hello > Wolrd" as a Posix process > > cool! hopefully the install and hello-world instructions are iterating > towards being mostly correct then :) (assuming you used those?) > > > and would like to move to Xen. Hence I need to set up a Xen > environment... I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveC= D > be OK to further experiment the MirageOS or will I waste my time? > > as i understand it, either should work -- personally i experiment using > Xen 4.2 on ubuntu 13.04 (inside a Virtualbox VM on my mac)... i'd say gi= ve > 4.0 a try (others have more experience Xen on the list than me though). > > -- > Cheers, > > R. > > > > > This message and any attachment are intended solely for the addressee and > may contain confidential information. If you have received this message i= n > 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 Nottingha= m. > > This message has been checked for viruses but the contents of an attachme= nt > 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. > > > > > --001a11c357c83e77de04f040aab4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Tha= nks a lot!
Wait! If I understand well enough your own setup, I don= 't need to run on bare metal!
I missed the point, and apologiz= e about that.

If I recap:
=A0- start a VirtualBox VM with a Linux dist= rib (presumably 64 bits)
=A0- install Xen 4.2 inside that VM, so I= guess in your case your Ubuntu 13.04 is running within your Dom0
=A0- run MirageOS inside a Xen VM
=A0=A0 - which works because it&= #39;s using the PV approach, I guess
=A0- I won't be able to r= un a native Linux distrib in a DomU... but I don't care.

I= f that works, you saved my day! No need for any Intel-VT or AMD-SVM support= !
Thanks again
Fran=E7ois
=

2014/1/18 Richard Mortier <Richard.Mortier@nottingham.ac.uk>

On 18 Jan 2014, at 15:35, Fran=E7ois Armand wrote:

> I apologize if this mailing list is not the right place for my questio= n.

no problem, this is the right place :)

> I'm starting playing with MirageOS. I succeeded =A0running the &qu= ot;hello Wolrd" as a Posix process

cool! =A0hopefully the install and hello-world instructions are itera= ting towards being mostly correct then :) =A0(assuming you used those?)

> and would like to move to Xen. Hence I need to set up a Xen environmen= t... I found 2 Xen LiveCD: 3.2 and 4.0, would the 4.0 Xen LiveCD be OK to = =A0further experiment the MirageOS or will I waste my time?

as i understand it, either should work -- personally i experiment usi= ng Xen 4.2 on ubuntu 13.04 (inside a Virtualbox VM on my mac)... =A0i'd= say give 4.0 a try (others have more experience Xen on the list than me th= ough).

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l 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.




--001a11c357c83e77de04f040aab4-- --===============7854319852650263149== 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 --===============7854319852650263149==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jan 18 16:01:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 16:01: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 1W4YKx-0007nz-Cq; Sat, 18 Jan 2014 16:01:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YKv-0007nu-TT for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 16:01:30 +0000 Received: from [193.109.254.147:53954] by server-14.bemta-14.messagelabs.com id E7/90-12628-955AAD25; Sat, 18 Jan 2014 16:01:29 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-27.messagelabs.com!1390060888!9399649!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 29372 invoked from network); 18 Jan 2014 16:01:28 -0000 Received: from engine03-20433-3.icritical.com (HELO engine03-20433-3.icritical.com) (93.95.15.170) by server-13.tower-27.messagelabs.com with SMTP; 18 Jan 2014 16:01:28 -0000 Received: (qmail 6165 invoked from network); 18 Jan 2014 16:02:03 -0000 Received: from localhost (127.0.0.1) by engine03-20433-3.icritical.com with SMTP; 18 Jan 2014 16:02:03 -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 05826-05 for ; Sat, 18 Jan 2014 16:02:02 +0000 (GMT) Received: (qmail 6149 invoked by uid 599); 18 Jan 2014 16:02:02 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 16:02:02 +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 1W4YKs-00008q-24; Sat, 18 Jan 2014 16:01:26 +0000 From: Richard Mortier To: =?iso-8859-1?Q?Fran=E7ois_Armand?= Date: Sat, 18 Jan 2014 16:01:25 +0000 Thread-Topic: [MirageOS-devel] Which version of Xen for MirageOS? Thread-Index: Ac8UZopKeooEtA/mSUO77WnCBeQd4Q== Message-ID: 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 engine03-20433-3.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote: > Thanks a lot! > Wait! If I understand well enough your own setup, I don't need to run on = bare metal! > I missed the point, and apologize about that. = > = > If I recap: > - start a VirtualBox VM with a Linux distrib (presumably 64 bits) > - install Xen 4.2 inside that VM, so I guess in your case your Ubuntu 13= .04 is running within your Dom0 roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, install = Ubuntu 13.04. then use the ubuntu packages to install Xen in that VM-- some= thing like "sudo apt-get install xen-hypervisor-4.2-amd64". (though that w= as for raring; i notice from the package list that saucy has 4.3 now.) you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl (or wha= tever) to create mirage (or indeed, any other you want) VMs given a vm imag= e and a config file. -- = Cheers, R. This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, 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 Jan 18 16:01:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 16:01: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 1W4YKx-0007nz-Cq; Sat, 18 Jan 2014 16:01:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YKv-0007nu-TT for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 16:01:30 +0000 Received: from [193.109.254.147:53954] by server-14.bemta-14.messagelabs.com id E7/90-12628-955AAD25; Sat, 18 Jan 2014 16:01:29 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-27.messagelabs.com!1390060888!9399649!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 29372 invoked from network); 18 Jan 2014 16:01:28 -0000 Received: from engine03-20433-3.icritical.com (HELO engine03-20433-3.icritical.com) (93.95.15.170) by server-13.tower-27.messagelabs.com with SMTP; 18 Jan 2014 16:01:28 -0000 Received: (qmail 6165 invoked from network); 18 Jan 2014 16:02:03 -0000 Received: from localhost (127.0.0.1) by engine03-20433-3.icritical.com with SMTP; 18 Jan 2014 16:02:03 -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 05826-05 for ; Sat, 18 Jan 2014 16:02:02 +0000 (GMT) Received: (qmail 6149 invoked by uid 599); 18 Jan 2014 16:02:02 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 16:02:02 +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 1W4YKs-00008q-24; Sat, 18 Jan 2014 16:01:26 +0000 From: Richard Mortier To: =?iso-8859-1?Q?Fran=E7ois_Armand?= Date: Sat, 18 Jan 2014 16:01:25 +0000 Thread-Topic: [MirageOS-devel] Which version of Xen for MirageOS? Thread-Index: Ac8UZopKeooEtA/mSUO77WnCBeQd4Q== Message-ID: 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 engine03-20433-3.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote: > Thanks a lot! > Wait! If I understand well enough your own setup, I don't need to run on = bare metal! > I missed the point, and apologize about that. = > = > If I recap: > - start a VirtualBox VM with a Linux distrib (presumably 64 bits) > - install Xen 4.2 inside that VM, so I guess in your case your Ubuntu 13= .04 is running within your Dom0 roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, install = Ubuntu 13.04. then use the ubuntu packages to install Xen in that VM-- some= thing like "sudo apt-get install xen-hypervisor-4.2-amd64". (though that w= as for raring; i notice from the package list that saucy has 4.3 now.) you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl (or wha= tever) to create mirage (or indeed, any other you want) VMs given a vm imag= e and a config file. -- = Cheers, R. This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, 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 Jan 18 16:06:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 16:06:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YPt-0007pz-Qw; Sat, 18 Jan 2014 16:06:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YPs-0007pu-OX for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 16:06:36 +0000 Received: from [85.158.143.35:14348] by server-3.bemta-4.messagelabs.com id DD/80-32360-C86AAD25; Sat, 18 Jan 2014 16:06:36 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-2.tower-21.messagelabs.com!1390061195!12501713!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 4607 invoked from network); 18 Jan 2014 16:06:35 -0000 Received: from engine01-20433-9.icritical.com (HELO engine01-20433-9.icritical.com) (151.236.209.34) by server-2.tower-21.messagelabs.com with SMTP; 18 Jan 2014 16:06:35 -0000 Received: (qmail 25674 invoked from network); 18 Jan 2014 16:06:34 -0000 Received: from localhost (127.0.0.1) by engine01-20433-9.icritical.com with SMTP; 18 Jan 2014 16:06:34 -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 25417-06 for ; Sat, 18 Jan 2014 16:06:31 +0000 (GMT) Received: (qmail 25635 invoked by uid 599); 18 Jan 2014 16:06:31 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-9.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 16:06:31 +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 1W4YPm-0000Bq-8a; Sat, 18 Jan 2014 16:06:30 +0000 From: Richard Mortier To: =?iso-8859-1?Q?Fran=E7ois_Armand?= Date: Sat, 18 Jan 2014 16:06:27 +0000 Thread-Topic: [MirageOS-devel] Which version of Xen for MirageOS? Thread-Index: Ac8UZz7Yx/b0M0akT62mYSxPn+t8Zw== Message-ID: 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 engine01-20433-9.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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 18 Jan 2014, at 16:01, Richard Mortier wrote: > = > On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote: > = >> Thanks a lot! >> Wait! If I understand well enough your own setup, I don't need to run on= bare metal! >> I missed the point, and apologize about that. = >> = >> If I recap: >> - start a VirtualBox VM with a Linux distrib (presumably 64 bits) >> - install Xen 4.2 inside that VM, so I guess in your case your Ubuntu 13= .04 is running within your Dom0 > = > roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, instal= l Ubuntu 13.04. then use the ubuntu packages to install Xen in that VM-- so= mething like "sudo apt-get install xen-hypervisor-4.2-amd64". (though that= was for raring; i notice from the package list that saucy has 4.3 now.) > = > you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl (or w= hatever) to create mirage (or indeed, any other you want) VMs given a vm im= age and a config file. ps. i'm starting to put together a blog post describing this and some of th= e other "getting started with mirage on xen" steps -- feel free to email me= (and/or the list) if you come across any problems or gotchas so i can incl= ude them. -- = Cheers, R. This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, 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 Jan 18 16:06:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 16:06:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YPt-0007pz-Qw; Sat, 18 Jan 2014 16:06:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4YPs-0007pu-OX for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 16:06:36 +0000 Received: from [85.158.143.35:14348] by server-3.bemta-4.messagelabs.com id DD/80-32360-C86AAD25; Sat, 18 Jan 2014 16:06:36 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-2.tower-21.messagelabs.com!1390061195!12501713!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 4607 invoked from network); 18 Jan 2014 16:06:35 -0000 Received: from engine01-20433-9.icritical.com (HELO engine01-20433-9.icritical.com) (151.236.209.34) by server-2.tower-21.messagelabs.com with SMTP; 18 Jan 2014 16:06:35 -0000 Received: (qmail 25674 invoked from network); 18 Jan 2014 16:06:34 -0000 Received: from localhost (127.0.0.1) by engine01-20433-9.icritical.com with SMTP; 18 Jan 2014 16:06:34 -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 25417-06 for ; Sat, 18 Jan 2014 16:06:31 +0000 (GMT) Received: (qmail 25635 invoked by uid 599); 18 Jan 2014 16:06:31 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-9.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 18 Jan 2014 16:06:31 +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 1W4YPm-0000Bq-8a; Sat, 18 Jan 2014 16:06:30 +0000 From: Richard Mortier To: =?iso-8859-1?Q?Fran=E7ois_Armand?= Date: Sat, 18 Jan 2014 16:06:27 +0000 Thread-Topic: [MirageOS-devel] Which version of Xen for MirageOS? Thread-Index: Ac8UZz7Yx/b0M0akT62mYSxPn+t8Zw== Message-ID: 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 engine01-20433-9.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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 18 Jan 2014, at 16:01, Richard Mortier wrote: > = > On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote: > = >> Thanks a lot! >> Wait! If I understand well enough your own setup, I don't need to run on= bare metal! >> I missed the point, and apologize about that. = >> = >> If I recap: >> - start a VirtualBox VM with a Linux distrib (presumably 64 bits) >> - install Xen 4.2 inside that VM, so I guess in your case your Ubuntu 13= .04 is running within your Dom0 > = > roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, instal= l Ubuntu 13.04. then use the ubuntu packages to install Xen in that VM-- so= mething like "sudo apt-get install xen-hypervisor-4.2-amd64". (though that= was for raring; i notice from the package list that saucy has 4.3 now.) > = > you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl (or w= hatever) to create mirage (or indeed, any other you want) VMs given a vm im= age and a config file. ps. i'm starting to put together a blog post describing this and some of th= e other "getting started with mirage on xen" steps -- feel free to email me= (and/or the list) if you come across any problems or gotchas so i can incl= ude them. -- = Cheers, R. This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, 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 Jan 18 16:17:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 16:17: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 1W4Ya4-0008JS-P4; Sat, 18 Jan 2014 16:17:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Ya3-0008JK-BU for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 16:17:07 +0000 Received: from [85.158.137.68:49066] by server-7.bemta-3.messagelabs.com id DA/E2-27599-209AAD25; Sat, 18 Jan 2014 16:17:06 +0000 X-Env-Sender: francois.armand.fa@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1390061823!9943205!1 X-Originating-IP: [209.85.213.181] 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 22374 invoked from network); 18 Jan 2014 16:17:05 -0000 Received: from mail-ig0-f181.google.com (HELO mail-ig0-f181.google.com) (209.85.213.181) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 16:17:05 -0000 Received: by mail-ig0-f181.google.com with SMTP id j1so4274970iga.2 for ; Sat, 18 Jan 2014 08:17: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=XUjAvh8tHaz5I5qh+M7GaNpouQY+QFActmkpN9swovg=; b=ip5KkkGM0o7Hya2YZnTPpBa62jCfanPaIYtfujZjngegKhuoKNX8X0A1g2aLl/0IA8 jMW0bdbt2R4g17gxqVDowivqtLIl+FBebxHVunyI4a8ufzxR0F/0nADRt0YxEg6R/PnT DuCeAmxkBOMWJ4vUZot8zCCJOnL8if1IQTfy7kCnPM0sZ+x2NH40k496AjC6UybsYYA6 1tnS/aHMKMRQDVqalPfoQ734EgYmUTWf2vnb1ZAs8EHD8Jh+kyBa5qt/tnjccqs8QpTp 9889ZrPT0Kyhc+21dpWo4DnlASRW5+AuFWvLky7NtAbzG4Ngu/N0rQU+jQHzBnPXbnGR +BsA== MIME-Version: 1.0 X-Received: by 10.42.142.129 with SMTP id s1mr6624120icu.30.1390061823448; Sat, 18 Jan 2014 08:17:03 -0800 (PST) Received: by 10.64.26.132 with HTTP; Sat, 18 Jan 2014 08:17:03 -0800 (PST) In-Reply-To: References: Date: Sat, 18 Jan 2014 17:17:03 +0100 Message-ID: From: =?ISO-8859-1?Q?Fran=E7ois_Armand?= To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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="===============3575693113954268365==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3575693113954268365== Content-Type: multipart/alternative; boundary=90e6ba6e8ce233dc8f04f040fd2e --90e6ba6e8ce233dc8f04f040fd2e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Last week, I had to fight with the Opam environment to get the Hello in Posix generated. This does not relate to Mirage though. - I had to regenerate OPAM from sources, getting it from Ubuntu (12.10) package led me to get Mirage 0.9.something instead of 1.0.3 - Based on Anil's recommandation I had to run apt-get install ocaml-native-compilers Then everything was fine. I'll go further with Xen within the next days / week I'll let you know about my issues/success. 2014/1/18 Richard Mortier > > On 18 Jan 2014, at 16:01, Richard Mortier wrote: > > > > > On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote: > > > >> Thanks a lot! > >> Wait! If I understand well enough your own setup, I don't need to run > on bare metal! > >> I missed the point, and apologize about that. > >> > >> If I recap: > >> - start a VirtualBox VM with a Linux distrib (presumably 64 bits) > >> - install Xen 4.2 inside that VM, so I guess in your case your Ubuntu > 13.04 is running within your Dom0 > > > > roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, > install Ubuntu 13.04. then use the ubuntu packages to install Xen in that > VM-- something like "sudo apt-get install xen-hypervisor-4.2-amd64". > (though that was for raring; i notice from the package list that saucy h= as > 4.3 now.) > > > > you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl (or > whatever) to create mirage (or indeed, any other you want) VMs given a vm > image and a config file. > > ps. i'm starting to put together a blog post describing this and some of > the other "getting started with mirage on xen" steps -- feel free to emai= l > me (and/or the list) if you come across any problems or gotchas so i can > include them. > > -- > Cheers, > > R. > > > > > This message and any attachment are intended solely for the addressee and > may contain confidential information. If you have received this message i= n > 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 Nottingha= m. > > This message has been checked for viruses but the contents of an attachme= nt > 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. > > > > --90e6ba6e8ce233dc8f04f040fd2e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Last week, I had to fight with the Opa= m environment to get the Hello in Posix generated. This does not relate to = Mirage though.

=A0- I had to regenerate OPAM from sources, get= ting it from Ubuntu (12.10) package led me to get Mirage 0.9.something inst= ead of 1.0.3

=A0- Based on Anil's recommandation=A0 I had to run apt= -get install ocaml-native-compilers

Then everything was fine.
I&= #39;ll go further with Xen within the next days / week I'll let you kno= w about my issues/success.


2014/1/18 Ric= hard Mortier <Richard.Mortier@nottingham.ac.uk>

On 18 Jan 2014, at 16:01, Richard Mortier wrote:

>
> On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote:
>
>> Thanks a lot!
>> Wait! If I understand well enough your own setup, I don't need= to run on bare metal!
>> I missed the point, and apologize about that.
>>
>> If I recap:
>> - start a VirtualBox VM with a Linux distrib (presumably 64 bits)<= br> >> - install Xen 4.2 inside that VM, so I guess in your case your Ubu= ntu 13.04 is running within your Dom0
>
> roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, ins= tall Ubuntu 13.04. then use the ubuntu packages to install Xen in that VM--= something like "sudo apt-get install xen-hypervisor-4.2-amd64". = =A0(though that was for raring; i notice from the package list that saucy h= as 4.3 now.)
>
> you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl (o= r whatever) to create mirage (or indeed, any other you want) VMs given a vm= image and a config file.

ps. i'm starting to put together a blog post describing this and = some of the other "getting started with mirage on xen" steps -- f= eel free to email me (and/or the list) if you come across any problems or g= otchas so i can include them.

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l 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.


--90e6ba6e8ce233dc8f04f040fd2e-- --===============3575693113954268365== 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 --===============3575693113954268365==-- From mirageos-devel-bounces@lists.xenproject.org Sat Jan 18 16:17:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 18 Jan 2014 16:17: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 1W4Ya4-0008JS-P4; Sat, 18 Jan 2014 16:17:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W4Ya3-0008JK-BU for mirageos-devel@lists.xenproject.org; Sat, 18 Jan 2014 16:17:07 +0000 Received: from [85.158.137.68:49066] by server-7.bemta-3.messagelabs.com id DA/E2-27599-209AAD25; Sat, 18 Jan 2014 16:17:06 +0000 X-Env-Sender: francois.armand.fa@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1390061823!9943205!1 X-Originating-IP: [209.85.213.181] 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 22374 invoked from network); 18 Jan 2014 16:17:05 -0000 Received: from mail-ig0-f181.google.com (HELO mail-ig0-f181.google.com) (209.85.213.181) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Jan 2014 16:17:05 -0000 Received: by mail-ig0-f181.google.com with SMTP id j1so4274970iga.2 for ; Sat, 18 Jan 2014 08:17: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=XUjAvh8tHaz5I5qh+M7GaNpouQY+QFActmkpN9swovg=; b=ip5KkkGM0o7Hya2YZnTPpBa62jCfanPaIYtfujZjngegKhuoKNX8X0A1g2aLl/0IA8 jMW0bdbt2R4g17gxqVDowivqtLIl+FBebxHVunyI4a8ufzxR0F/0nADRt0YxEg6R/PnT DuCeAmxkBOMWJ4vUZot8zCCJOnL8if1IQTfy7kCnPM0sZ+x2NH40k496AjC6UybsYYA6 1tnS/aHMKMRQDVqalPfoQ734EgYmUTWf2vnb1ZAs8EHD8Jh+kyBa5qt/tnjccqs8QpTp 9889ZrPT0Kyhc+21dpWo4DnlASRW5+AuFWvLky7NtAbzG4Ngu/N0rQU+jQHzBnPXbnGR +BsA== MIME-Version: 1.0 X-Received: by 10.42.142.129 with SMTP id s1mr6624120icu.30.1390061823448; Sat, 18 Jan 2014 08:17:03 -0800 (PST) Received: by 10.64.26.132 with HTTP; Sat, 18 Jan 2014 08:17:03 -0800 (PST) In-Reply-To: References: Date: Sat, 18 Jan 2014 17:17:03 +0100 Message-ID: From: =?ISO-8859-1?Q?Fran=E7ois_Armand?= To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Which version of Xen for MirageOS? 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="===============3575693113954268365==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3575693113954268365== Content-Type: multipart/alternative; boundary=90e6ba6e8ce233dc8f04f040fd2e --90e6ba6e8ce233dc8f04f040fd2e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Last week, I had to fight with the Opam environment to get the Hello in Posix generated. This does not relate to Mirage though. - I had to regenerate OPAM from sources, getting it from Ubuntu (12.10) package led me to get Mirage 0.9.something instead of 1.0.3 - Based on Anil's recommandation I had to run apt-get install ocaml-native-compilers Then everything was fine. I'll go further with Xen within the next days / week I'll let you know about my issues/success. 2014/1/18 Richard Mortier > > On 18 Jan 2014, at 16:01, Richard Mortier wrote: > > > > > On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote: > > > >> Thanks a lot! > >> Wait! If I understand well enough your own setup, I don't need to run > on bare metal! > >> I missed the point, and apologize about that. > >> > >> If I recap: > >> - start a VirtualBox VM with a Linux distrib (presumably 64 bits) > >> - install Xen 4.2 inside that VM, so I guess in your case your Ubuntu > 13.04 is running within your Dom0 > > > > roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, > install Ubuntu 13.04. then use the ubuntu packages to install Xen in that > VM-- something like "sudo apt-get install xen-hypervisor-4.2-amd64". > (though that was for raring; i notice from the package list that saucy h= as > 4.3 now.) > > > > you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl (or > whatever) to create mirage (or indeed, any other you want) VMs given a vm > image and a config file. > > ps. i'm starting to put together a blog post describing this and some of > the other "getting started with mirage on xen" steps -- feel free to emai= l > me (and/or the list) if you come across any problems or gotchas so i can > include them. > > -- > Cheers, > > R. > > > > > This message and any attachment are intended solely for the addressee and > may contain confidential information. If you have received this message i= n > 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 Nottingha= m. > > This message has been checked for viruses but the contents of an attachme= nt > 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. > > > > --90e6ba6e8ce233dc8f04f040fd2e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Last week, I had to fight with the Opa= m environment to get the Hello in Posix generated. This does not relate to = Mirage though.

=A0- I had to regenerate OPAM from sources, get= ting it from Ubuntu (12.10) package led me to get Mirage 0.9.something inst= ead of 1.0.3

=A0- Based on Anil's recommandation=A0 I had to run apt= -get install ocaml-native-compilers

Then everything was fine.
I&= #39;ll go further with Xen within the next days / week I'll let you kno= w about my issues/success.


2014/1/18 Ric= hard Mortier <Richard.Mortier@nottingham.ac.uk>

On 18 Jan 2014, at 16:01, Richard Mortier wrote:

>
> On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote:
>
>> Thanks a lot!
>> Wait! If I understand well enough your own setup, I don't need= to run on bare metal!
>> I missed the point, and apologize about that.
>>
>> If I recap:
>> - start a VirtualBox VM with a Linux distrib (presumably 64 bits)<= br> >> - install Xen 4.2 inside that VM, so I guess in your case your Ubu= ntu 13.04 is running within your Dom0
>
> roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, ins= tall Ubuntu 13.04. then use the ubuntu packages to install Xen in that VM--= something like "sudo apt-get install xen-hypervisor-4.2-amd64". = =A0(though that was for raring; i notice from the package list that saucy h= as 4.3 now.)
>
> you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl (o= r whatever) to create mirage (or indeed, any other you want) VMs given a vm= image and a config file.

ps. i'm starting to put together a blog post describing this and = some of the other "getting started with mirage on xen" steps -- f= eel free to email me (and/or the list) if you come across any problems or g= otchas so i can include them.

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l 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.


--90e6ba6e8ce233dc8f04f040fd2e-- --===============3575693113954268365== 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 --===============3575693113954268365==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jan 20 09:19:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 20 Jan 2014 09:19: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 1W5B0V-0002JC-5F; Mon, 20 Jan 2014 09:18:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5B0S-0002Io-TY for mirageos-devel@lists.xenproject.org; Mon, 20 Jan 2014 09:18:57 +0000 Received: from [85.158.139.211:42645] by server-12.bemta-5.messagelabs.com id 61/18-30017-00AECD25; Mon, 20 Jan 2014 09:18:56 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1390209533!10707220!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_SEX,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4420 invoked from network); 20 Jan 2014 09:18:55 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2014 09:18:55 -0000 Received: by mail-wg0-f47.google.com with SMTP id m15so6497427wgh.26 for ; Mon, 20 Jan 2014 01:18: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 :subject:content-type:content-transfer-encoding; bh=DfSP2czzc9IdvCvH2tQ6nprfgk2OyR/BVtAB4BFQCGw=; b=kdqAOZuQEvURpmBZcDBqAnPGyJw7QkP3OydYo82k58pLQWbOlXByr22tPoKbZ4AMrn Jnsq3grCIw4PlcGaofzw23tETHs3SBlYo0FND1VUn5LKJSrwT8SCuJciEq8G85WcjiHh izicAEbjeb859+H+3qgK9aO8lwbJh1NeLFXmtVqW6o26rbPo/6EW3c/gptNTMk+m0Ezz VytDtH5iAPnLXm/anbWhfEEm8Wl//PXUr92iGHM/kczf33GR1im22+Hu1cMQ+poZjN+Z DQ0QxA4dXnOCkwslKEN9Gj5lUWDwn45c/o9Id7eTdL6Oz3DoiKs4ifiUhvdmbMt90bzR Jbpw== X-Received: by 10.194.63.228 with SMTP id j4mr13538806wjs.34.1390209533631; Mon, 20 Jan 2014 01:18:53 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id eo4sm1090422wib.9.2014.01.20.01.18.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Jan 2014 01:18:52 -0800 (PST) Message-ID: <52DCE9FA.6010400@xen.org> Date: Mon, 20 Jan 2014 09:18:50 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org Subject: [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 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_Projects urgently (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 From mirageos-devel-bounces@lists.xenproject.org Mon Jan 20 09:19:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 20 Jan 2014 09:19: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 1W5B0V-0002JC-5F; Mon, 20 Jan 2014 09:18:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5B0S-0002Io-TY for mirageos-devel@lists.xenproject.org; Mon, 20 Jan 2014 09:18:57 +0000 Received: from [85.158.139.211:42645] by server-12.bemta-5.messagelabs.com id 61/18-30017-00AECD25; Mon, 20 Jan 2014 09:18:56 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1390209533!10707220!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_SEX,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4420 invoked from network); 20 Jan 2014 09:18:55 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Jan 2014 09:18:55 -0000 Received: by mail-wg0-f47.google.com with SMTP id m15so6497427wgh.26 for ; Mon, 20 Jan 2014 01:18: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 :subject:content-type:content-transfer-encoding; bh=DfSP2czzc9IdvCvH2tQ6nprfgk2OyR/BVtAB4BFQCGw=; b=kdqAOZuQEvURpmBZcDBqAnPGyJw7QkP3OydYo82k58pLQWbOlXByr22tPoKbZ4AMrn Jnsq3grCIw4PlcGaofzw23tETHs3SBlYo0FND1VUn5LKJSrwT8SCuJciEq8G85WcjiHh izicAEbjeb859+H+3qgK9aO8lwbJh1NeLFXmtVqW6o26rbPo/6EW3c/gptNTMk+m0Ezz VytDtH5iAPnLXm/anbWhfEEm8Wl//PXUr92iGHM/kczf33GR1im22+Hu1cMQ+poZjN+Z DQ0QxA4dXnOCkwslKEN9Gj5lUWDwn45c/o9Id7eTdL6Oz3DoiKs4ifiUhvdmbMt90bzR Jbpw== X-Received: by 10.194.63.228 with SMTP id j4mr13538806wjs.34.1390209533631; Mon, 20 Jan 2014 01:18:53 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id eo4sm1090422wib.9.2014.01.20.01.18.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Jan 2014 01:18:52 -0800 (PST) Message-ID: <52DCE9FA.6010400@xen.org> Date: Mon, 20 Jan 2014 09:18:50 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org Subject: [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 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_Projects urgently (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 From mirageos-devel-bounces@lists.xenproject.org Tue Jan 21 15:10:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 15:10: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 1W5cxv-0007P5-P4; Tue, 21 Jan 2014 15:10:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5cxt-0007Or-OI for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 15:10:09 +0000 Received: from [193.109.254.147:59417] by server-13.bemta-14.messagelabs.com id 81/59-19374-1DD8ED25; Tue, 21 Jan 2014 15:10:09 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1390317004!12239465!1 X-Originating-IP: [209.85.192.171] 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 16166 invoked from network); 21 Jan 2014 15:10:06 -0000 Received: from mail-pd0-f171.google.com (HELO mail-pd0-f171.google.com) (209.85.192.171) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 15:10:06 -0000 Received: by mail-pd0-f171.google.com with SMTP id g10so7581716pdj.2 for ; Tue, 21 Jan 2014 07:10:04 -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=Qr/Q0S269z9ipawRd1il9PjmgWQ9QYbMc5EzPCQO4TQ=; b=uNUAQh+y84mZpufoaQJJwC9vgNR1C6WCcY70w511aB6ZzAPOnwChfCw6kEnaqpPwXZ l0q2kgg4mZLSrT7A8q+kB057TEUl/OlJy1Bl7aSOVdzVFokOIvkur5EZvfbxBGNXmb3J 5NMii5YDk6Axqy12mN1XFM8V3vOTeA/W+TWIZfpwKr/tEgN5Gifi6Fm2p526lMiKJmks 88E0paoEF7ztIsvijlt6mQ+EW9uuAXzZ8F9FZCDQAW+LVu+pPjeo2RnfbaYfieinimbY xE7esRyDOpTnHfDPxn1XA/K4LWIE8+G9rQODZUtd3TwOzPEyjiknoH4lFFlMOhgN2YGP BO/g== MIME-Version: 1.0 X-Received: by 10.68.248.100 with SMTP id yl4mr25273764pbc.41.1390317004302; Tue, 21 Jan 2014 07:10:04 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 07:10:04 -0800 (PST) Date: Tue, 21 Jan 2014 15:10:04 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today, 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="===============8885145169340943494==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8885145169340943494== Content-Type: multipart/alternative; boundary=047d7b2e14f52aafca04f07c67e2 --047d7b2e14f52aafca04f07c67e2 Content-Type: text/plain; charset=ISO-8859-1 I'm sure there'll be much to discuss, since there are so many repos with unreleased changes! 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 --047d7b2e14f52aafca04f07c67e2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I'm sure there'll be much to discuss, since there are so many repo= s with unreleased changes!

1. =A0Please join my meeting.

2. =A0= Use your microphone and speakers (VoIP) - a headset is recommended. =A0Or, = call in 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
--047d7b2e14f52aafca04f07c67e2-- --===============8885145169340943494== 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 --===============8885145169340943494==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 21 15:10:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 15:10: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 1W5cxv-0007P5-P4; Tue, 21 Jan 2014 15:10:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5cxt-0007Or-OI for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 15:10:09 +0000 Received: from [193.109.254.147:59417] by server-13.bemta-14.messagelabs.com id 81/59-19374-1DD8ED25; Tue, 21 Jan 2014 15:10:09 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1390317004!12239465!1 X-Originating-IP: [209.85.192.171] 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 16166 invoked from network); 21 Jan 2014 15:10:06 -0000 Received: from mail-pd0-f171.google.com (HELO mail-pd0-f171.google.com) (209.85.192.171) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 15:10:06 -0000 Received: by mail-pd0-f171.google.com with SMTP id g10so7581716pdj.2 for ; Tue, 21 Jan 2014 07:10:04 -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=Qr/Q0S269z9ipawRd1il9PjmgWQ9QYbMc5EzPCQO4TQ=; b=uNUAQh+y84mZpufoaQJJwC9vgNR1C6WCcY70w511aB6ZzAPOnwChfCw6kEnaqpPwXZ l0q2kgg4mZLSrT7A8q+kB057TEUl/OlJy1Bl7aSOVdzVFokOIvkur5EZvfbxBGNXmb3J 5NMii5YDk6Axqy12mN1XFM8V3vOTeA/W+TWIZfpwKr/tEgN5Gifi6Fm2p526lMiKJmks 88E0paoEF7ztIsvijlt6mQ+EW9uuAXzZ8F9FZCDQAW+LVu+pPjeo2RnfbaYfieinimbY xE7esRyDOpTnHfDPxn1XA/K4LWIE8+G9rQODZUtd3TwOzPEyjiknoH4lFFlMOhgN2YGP BO/g== MIME-Version: 1.0 X-Received: by 10.68.248.100 with SMTP id yl4mr25273764pbc.41.1390317004302; Tue, 21 Jan 2014 07:10:04 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 07:10:04 -0800 (PST) Date: Tue, 21 Jan 2014 15:10:04 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Mirage weekly call today, 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="===============8885145169340943494==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8885145169340943494== Content-Type: multipart/alternative; boundary=047d7b2e14f52aafca04f07c67e2 --047d7b2e14f52aafca04f07c67e2 Content-Type: text/plain; charset=ISO-8859-1 I'm sure there'll be much to discuss, since there are so many repos with unreleased changes! 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 --047d7b2e14f52aafca04f07c67e2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I'm sure there'll be much to discuss, since there are so many repo= s with unreleased changes!

1. =A0Please join my meeting.

2. =A0= Use your microphone and speakers (VoIP) - a headset is recommended. =A0Or, = call in 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
--047d7b2e14f52aafca04f07c67e2-- --===============8885145169340943494== 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 --===============8885145169340943494==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 21 15:27:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 15:27: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 1W5dF2-0008Fa-LS; Tue, 21 Jan 2014 15:27:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5dF1-0008FV-F2 for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 15:27:51 +0000 Received: from [193.109.254.147:19021] by server-6.bemta-14.messagelabs.com id 4F/9F-14958-6F19ED25; Tue, 21 Jan 2014 15:27:50 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1390318069!8771998!1 X-Originating-IP: [74.125.82.173] 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 18602 invoked from network); 21 Jan 2014 15:27:49 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 15:27:49 -0000 Received: by mail-we0-f173.google.com with SMTP id t60so8287495wes.32 for ; Tue, 21 Jan 2014 07:27:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=Ky5ZrvA3vIiU1GpntjJd3+dms86repgWlpsFHXnPhmw=; b=dAQQOaWLsgKTRgyRiMaQKUWQyaAFwZhQrZiulBQikAE/g4GR5+gkXlZUcesEdJ9iWr XdRnYBOqb+qZlMoRFWeamkWnJJbQCunfZ0vR2h7YmFxYKerUjL0waxpXO/iIJqUz8xYt oFHapBKpH9judOrLej3nXpNA7BF6GDAk1ykUEgSxPy82lTRkZypYBPbgOlcZvVCEhl5R fZ8yWEZV3km9N4GCEWIp1lKiN53Nxo3S89XdB99157itrsON8UiKdtAvltEeGBGEP75d YTjncxd2QeWxYT5FIggC+UMO5//q3MZuuKBIUGZeanS2JAK/dOR1XYYEr2kjdIBc5sc6 t+uw== X-Received: by 10.194.109.68 with SMTP id hq4mr19920294wjb.12.1390318069067; Tue, 21 Jan 2014 07:27:49 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id ev4sm11148729wib.1.2014.01.21.07.27.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jan 2014 07:27:48 -0800 (PST) From: Thomas Gazagnaire Message-Id: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> Date: Tue, 21 Jan 2014 15:27:46 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [MirageOS-devel] irminsule 0.4.0 is 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 am very happy to cut the first 'early-alpha' release of irminsule[1], which should be available in OPAM quite soon. Irminsule is a distributed database with built-in snapshot, branch and revert mechanisms. It is designed to use a large variety of backends, although it is optimized for append-only store. Currently, there are 4 backends implemented: in-memory, custom binary format on disk, CRUD interface (using JSON over HTTP) and Git. Irminsule is written in pure OCaml. It can thus be compiled to Javascript -- and run in the browsers; or into a Mirage microkernel -- and run directly on top of Xen. Currently, though, the package is split into a pure library ('irminsule'), a bunch of backends (called `irmsule.backend`) and a unix HTTP server ('irminsule.server'). The HTTP server and some of the backends works only in unix, but they should be easy to mirage. The package also comes with a command-line tool to experiment with the various backends. $ irmin init -m -d # start a daemon to read and store data in memory $ irmin init -l /path/ -d # start a daemon to read and store data on disk $ irmin init -r -d # start a daemon to read and store data using a JSON protocol to reach the given uri # (another irminsule instance should listen on the given uri) $ irmin init -g -d # start a daemon to read and store data using the Git format You can store the default backend in the IRMIN shell variable. Running 'irmin' will automatically look in that variable to select the right backend. $ export IRMIN=m # memory backend $ export IRMIN=g # Git backend $ export IRMIN=l: # local backend $ export IRMIN=r: # remote backend Use `irmin read` and `irmin write` to read a write keys in the dabase. Use `irmin tree` and `irmin ls` to inspect the database state Use `irmin dump` to dump the database state in a .dot file Use `irmin snapshot` to get the current HEAD Use `irmin revert` to rollback to a previous HEAD Use `irmin clone` and `irmin fetch` to create/update the local disk store from the given backend. For whose interested to write new backends, I suggest to have a look at [3]. If you can provide something which satisfies the `AO_BINARY` signature, it's then easy to build a backend for irminsule (the simplest one being the in-memory one[4]). The command are (poorly) documented using `irmin --help`. Feel free to ask questions on that list, report bugs and request feature on the bugtracker [2]. Best, Thomas [1] https://github.com/samoht/irminsule [2] https://github.com/samoht/irminsule/issues [3] https://github.com/samoht/irminsule/blob/master/lib/core/irminStore.mli [4] https://github.com/samoht/irminsule/blob/master/lib/backend/irminMemory.ml _______________________________________________ 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 Jan 21 15:27:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 15:27: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 1W5dF2-0008Fa-LS; Tue, 21 Jan 2014 15:27:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5dF1-0008FV-F2 for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 15:27:51 +0000 Received: from [193.109.254.147:19021] by server-6.bemta-14.messagelabs.com id 4F/9F-14958-6F19ED25; Tue, 21 Jan 2014 15:27:50 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1390318069!8771998!1 X-Originating-IP: [74.125.82.173] 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 18602 invoked from network); 21 Jan 2014 15:27:49 -0000 Received: from mail-we0-f173.google.com (HELO mail-we0-f173.google.com) (74.125.82.173) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 15:27:49 -0000 Received: by mail-we0-f173.google.com with SMTP id t60so8287495wes.32 for ; Tue, 21 Jan 2014 07:27:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=Ky5ZrvA3vIiU1GpntjJd3+dms86repgWlpsFHXnPhmw=; b=dAQQOaWLsgKTRgyRiMaQKUWQyaAFwZhQrZiulBQikAE/g4GR5+gkXlZUcesEdJ9iWr XdRnYBOqb+qZlMoRFWeamkWnJJbQCunfZ0vR2h7YmFxYKerUjL0waxpXO/iIJqUz8xYt oFHapBKpH9judOrLej3nXpNA7BF6GDAk1ykUEgSxPy82lTRkZypYBPbgOlcZvVCEhl5R fZ8yWEZV3km9N4GCEWIp1lKiN53Nxo3S89XdB99157itrsON8UiKdtAvltEeGBGEP75d YTjncxd2QeWxYT5FIggC+UMO5//q3MZuuKBIUGZeanS2JAK/dOR1XYYEr2kjdIBc5sc6 t+uw== X-Received: by 10.194.109.68 with SMTP id hq4mr19920294wjb.12.1390318069067; Tue, 21 Jan 2014 07:27:49 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id ev4sm11148729wib.1.2014.01.21.07.27.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jan 2014 07:27:48 -0800 (PST) From: Thomas Gazagnaire Message-Id: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> Date: Tue, 21 Jan 2014 15:27:46 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [MirageOS-devel] irminsule 0.4.0 is 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 am very happy to cut the first 'early-alpha' release of irminsule[1], which should be available in OPAM quite soon. Irminsule is a distributed database with built-in snapshot, branch and revert mechanisms. It is designed to use a large variety of backends, although it is optimized for append-only store. Currently, there are 4 backends implemented: in-memory, custom binary format on disk, CRUD interface (using JSON over HTTP) and Git. Irminsule is written in pure OCaml. It can thus be compiled to Javascript -- and run in the browsers; or into a Mirage microkernel -- and run directly on top of Xen. Currently, though, the package is split into a pure library ('irminsule'), a bunch of backends (called `irmsule.backend`) and a unix HTTP server ('irminsule.server'). The HTTP server and some of the backends works only in unix, but they should be easy to mirage. The package also comes with a command-line tool to experiment with the various backends. $ irmin init -m -d # start a daemon to read and store data in memory $ irmin init -l /path/ -d # start a daemon to read and store data on disk $ irmin init -r -d # start a daemon to read and store data using a JSON protocol to reach the given uri # (another irminsule instance should listen on the given uri) $ irmin init -g -d # start a daemon to read and store data using the Git format You can store the default backend in the IRMIN shell variable. Running 'irmin' will automatically look in that variable to select the right backend. $ export IRMIN=m # memory backend $ export IRMIN=g # Git backend $ export IRMIN=l: # local backend $ export IRMIN=r: # remote backend Use `irmin read` and `irmin write` to read a write keys in the dabase. Use `irmin tree` and `irmin ls` to inspect the database state Use `irmin dump` to dump the database state in a .dot file Use `irmin snapshot` to get the current HEAD Use `irmin revert` to rollback to a previous HEAD Use `irmin clone` and `irmin fetch` to create/update the local disk store from the given backend. For whose interested to write new backends, I suggest to have a look at [3]. If you can provide something which satisfies the `AO_BINARY` signature, it's then easy to build a backend for irminsule (the simplest one being the in-memory one[4]). The command are (poorly) documented using `irmin --help`. Feel free to ask questions on that list, report bugs and request feature on the bugtracker [2]. Best, Thomas [1] https://github.com/samoht/irminsule [2] https://github.com/samoht/irminsule/issues [3] https://github.com/samoht/irminsule/blob/master/lib/core/irminStore.mli [4] https://github.com/samoht/irminsule/blob/master/lib/backend/irminMemory.ml _______________________________________________ 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 Jan 21 15:55:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 15:55: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 1W5dfn-00026N-HX; Tue, 21 Jan 2014 15:55:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5dfl-00025z-Jk for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 15:55:29 +0000 Received: from [193.109.254.147:15483] by server-15.bemta-14.messagelabs.com id 96/DC-22186-0789ED25; Tue, 21 Jan 2014 15:55:28 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1390319727!12259105!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 18601 invoked from network); 21 Jan 2014 15:55:27 -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; 21 Jan 2014 15:55:27 -0000 Received: (qmail 30561 invoked by uid 634); 21 Jan 2014 15:55: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; Tue, 21 Jan 2014 15:55:26 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> Date: Tue, 21 Jan 2014 15:55:23 +0000 Message-Id: <386F4EB6-447A-407E-AEC0-123EBA4674CC@recoil.org> References: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> To: Thomas Gazagnaire 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] irminsule 0.4.0 is 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 And in other good news for the Irminsule JavaScript backend, Bigarray support just landed in js_of_ocaml! https://github.com/ocsigen/js_of_ocaml/commit/601be77d4b662793467d89c9ac9dda721a32ea52 -anil On 21 Jan 2014, at 15:27, Thomas Gazagnaire wrote: > I am very happy to cut the first 'early-alpha' release of irminsule[1], which > should be available in OPAM quite soon. > > Irminsule is a distributed database with built-in snapshot, branch and > revert mechanisms. It is designed to use a large variety of backends, > although it is optimized for append-only store. Currently, there are 4 > backends implemented: in-memory, custom binary format on disk, > CRUD interface (using JSON over HTTP) and Git. > > Irminsule is written in pure OCaml. It can thus be compiled to Javascript > -- and run in the browsers; or into a Mirage microkernel -- and run directly > on top of Xen. Currently, though, the package is split into a pure library > ('irminsule'), a bunch of backends (called `irmsule.backend`) and a unix HTTP > server ('irminsule.server'). The HTTP server and some of the backends works > only in unix, but they should be easy to mirage. > > The package also comes with a command-line tool to experiment with the > various backends. > > $ irmin init -m -d # start a daemon to read and store data in memory > $ irmin init -l /path/ -d # start a daemon to read and store data on disk > $ irmin init -r -d # start a daemon to read and store data using a JSON protocol to reach the given uri > # (another irminsule instance should listen on the given uri) > $ irmin init -g -d # start a daemon to read and store data using the Git format > > You can store the default backend in the IRMIN shell variable. Running 'irmin' will automatically look in that variable to select the right backend. > $ export IRMIN=m # memory backend > $ export IRMIN=g # Git backend > $ export IRMIN=l: # local backend > $ export IRMIN=r: # remote backend > > Use `irmin read` and `irmin write` to read a write keys in the dabase. > Use `irmin tree` and `irmin ls` to inspect the database state > Use `irmin dump` to dump the database state in a .dot file > Use `irmin snapshot` to get the current HEAD > Use `irmin revert` to rollback to a previous HEAD > Use `irmin clone` and `irmin fetch` to create/update the local disk store from the given backend. > > For whose interested to write new backends, I suggest to have a look at [3]. If you can provide something which satisfies the `AO_BINARY` signature, it's then easy to build a backend for irminsule (the simplest one being the in-memory one[4]). > > The command are (poorly) documented using `irmin --help`. Feel free to ask questions on that list, report bugs and request feature on the bugtracker [2]. > > Best, > Thomas > > [1] https://github.com/samoht/irminsule > [2] https://github.com/samoht/irminsule/issues > [3] https://github.com/samoht/irminsule/blob/master/lib/core/irminStore.mli > [4] https://github.com/samoht/irminsule/blob/master/lib/backend/irminMemory.ml > > > > > > _______________________________________________ > 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 Jan 21 15:55:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 15:55: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 1W5dfn-00026N-HX; Tue, 21 Jan 2014 15:55:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5dfl-00025z-Jk for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 15:55:29 +0000 Received: from [193.109.254.147:15483] by server-15.bemta-14.messagelabs.com id 96/DC-22186-0789ED25; Tue, 21 Jan 2014 15:55:28 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1390319727!12259105!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 18601 invoked from network); 21 Jan 2014 15:55:27 -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; 21 Jan 2014 15:55:27 -0000 Received: (qmail 30561 invoked by uid 634); 21 Jan 2014 15:55: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; Tue, 21 Jan 2014 15:55:26 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> Date: Tue, 21 Jan 2014 15:55:23 +0000 Message-Id: <386F4EB6-447A-407E-AEC0-123EBA4674CC@recoil.org> References: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> To: Thomas Gazagnaire 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] irminsule 0.4.0 is 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 And in other good news for the Irminsule JavaScript backend, Bigarray support just landed in js_of_ocaml! https://github.com/ocsigen/js_of_ocaml/commit/601be77d4b662793467d89c9ac9dda721a32ea52 -anil On 21 Jan 2014, at 15:27, Thomas Gazagnaire wrote: > I am very happy to cut the first 'early-alpha' release of irminsule[1], which > should be available in OPAM quite soon. > > Irminsule is a distributed database with built-in snapshot, branch and > revert mechanisms. It is designed to use a large variety of backends, > although it is optimized for append-only store. Currently, there are 4 > backends implemented: in-memory, custom binary format on disk, > CRUD interface (using JSON over HTTP) and Git. > > Irminsule is written in pure OCaml. It can thus be compiled to Javascript > -- and run in the browsers; or into a Mirage microkernel -- and run directly > on top of Xen. Currently, though, the package is split into a pure library > ('irminsule'), a bunch of backends (called `irmsule.backend`) and a unix HTTP > server ('irminsule.server'). The HTTP server and some of the backends works > only in unix, but they should be easy to mirage. > > The package also comes with a command-line tool to experiment with the > various backends. > > $ irmin init -m -d # start a daemon to read and store data in memory > $ irmin init -l /path/ -d # start a daemon to read and store data on disk > $ irmin init -r -d # start a daemon to read and store data using a JSON protocol to reach the given uri > # (another irminsule instance should listen on the given uri) > $ irmin init -g -d # start a daemon to read and store data using the Git format > > You can store the default backend in the IRMIN shell variable. Running 'irmin' will automatically look in that variable to select the right backend. > $ export IRMIN=m # memory backend > $ export IRMIN=g # Git backend > $ export IRMIN=l: # local backend > $ export IRMIN=r: # remote backend > > Use `irmin read` and `irmin write` to read a write keys in the dabase. > Use `irmin tree` and `irmin ls` to inspect the database state > Use `irmin dump` to dump the database state in a .dot file > Use `irmin snapshot` to get the current HEAD > Use `irmin revert` to rollback to a previous HEAD > Use `irmin clone` and `irmin fetch` to create/update the local disk store from the given backend. > > For whose interested to write new backends, I suggest to have a look at [3]. If you can provide something which satisfies the `AO_BINARY` signature, it's then easy to build a backend for irminsule (the simplest one being the in-memory one[4]). > > The command are (poorly) documented using `irmin --help`. Feel free to ask questions on that list, report bugs and request feature on the bugtracker [2]. > > Best, > Thomas > > [1] https://github.com/samoht/irminsule > [2] https://github.com/samoht/irminsule/issues > [3] https://github.com/samoht/irminsule/blob/master/lib/core/irminStore.mli > [4] https://github.com/samoht/irminsule/blob/master/lib/backend/irminMemory.ml > > > > > > _______________________________________________ > 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 Jan 21 18:12:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 18:12: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 1W5foM-0003MA-Fl; Tue, 21 Jan 2014 18:12:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5foK-0003La-BP for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 18:12:28 +0000 Received: from [85.158.137.68:18733] by server-9.bemta-3.messagelabs.com id 5E/E2-13104-B88BED25; Tue, 21 Jan 2014 18:12:27 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1390327946!10500902!1 X-Originating-IP: [209.85.212.171] 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 4897 invoked from network); 21 Jan 2014 18:12:26 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 18:12:26 -0000 Received: by mail-wi0-f171.google.com with SMTP id cc10so4743904wib.4 for ; Tue, 21 Jan 2014 10:12:26 -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 :content-transfer-encoding:message-id:references:to; bh=ymq/V/xFHBlAhstxEnaHEYNT7GK86ugKgl8HKea2f6M=; b=iIIDNhJGPvKK0mAdnlqX/6GNXzk0hJ4h3Tfa4IgkALX96zT4KMmTtF8hzhM/vIWa1T syRNvr00cgig0nh2xxsojeGuM7SuT2lAoD/6C31sxxASdAr66Ra0UnZt6HHle6vns2Bl 9HJ/weqCPOHXb0Er3XKppC+DUiTnUwFH+KvaobCjSzQLqF2EeeFgAPLJyaMttgMXeZ2o 8bE1DfUhiczhQho7v0h/LhlMiY0o4hVV15EnhANoUUW26FTvVvebS8dikOQ4GG4TL2Pp PDytUFwV9e171bPMvl+pUVEW3jEIXS9gcY7dzGISI/bwF1mC5Q8BtvPw9gFs4O+rqa7Z Bb+w== X-Received: by 10.180.219.44 with SMTP id pl12mr13374291wic.12.1390327946124; Tue, 21 Jan 2014 10:12:26 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id dd3sm9225767wjb.9.2014.01.21.10.12.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jan 2014 10:12:24 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> Date: Tue, 21 Jan 2014 18:12:24 +0000 Message-Id: References: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1827) Subject: Re: [MirageOS-devel] irminsule 0.4.0 is 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've just put the rough notes of the demo I've done this morning online: https://github.com/samoht/irminsule/wiki/Getting-Started Thomas On 21 Jan 2014, at 15:27, Thomas Gazagnaire wrote: > I am very happy to cut the first 'early-alpha' release of irminsule[1], which > should be available in OPAM quite soon. > > Irminsule is a distributed database with built-in snapshot, branch and > revert mechanisms. It is designed to use a large variety of backends, > although it is optimized for append-only store. Currently, there are 4 > backends implemented: in-memory, custom binary format on disk, > CRUD interface (using JSON over HTTP) and Git. > > Irminsule is written in pure OCaml. It can thus be compiled to Javascript > -- and run in the browsers; or into a Mirage microkernel -- and run directly > on top of Xen. Currently, though, the package is split into a pure library > ('irminsule'), a bunch of backends (called `irmsule.backend`) and a unix HTTP > server ('irminsule.server'). The HTTP server and some of the backends works > only in unix, but they should be easy to mirage. > > The package also comes with a command-line tool to experiment with the > various backends. > > $ irmin init -m -d # start a daemon to read and store data in memory > $ irmin init -l /path/ -d # start a daemon to read and store data on disk > $ irmin init -r -d # start a daemon to read and store data using a JSON protocol to reach the given uri > # (another irminsule instance should listen on the given uri) > $ irmin init -g -d # start a daemon to read and store data using the Git format > > You can store the default backend in the IRMIN shell variable. Running 'irmin' will automatically look in that variable to select the right backend. > $ export IRMIN=m # memory backend > $ export IRMIN=g # Git backend > $ export IRMIN=l: # local backend > $ export IRMIN=r: # remote backend > > Use `irmin read` and `irmin write` to read a write keys in the dabase. > Use `irmin tree` and `irmin ls` to inspect the database state > Use `irmin dump` to dump the database state in a .dot file > Use `irmin snapshot` to get the current HEAD > Use `irmin revert` to rollback to a previous HEAD > Use `irmin clone` and `irmin fetch` to create/update the local disk store from the given backend. > > For whose interested to write new backends, I suggest to have a look at [3]. If you can provide something which satisfies the `AO_BINARY` signature, it's then easy to build a backend for irminsule (the simplest one being the in-memory one[4]). > > The command are (poorly) documented using `irmin --help`. Feel free to ask questions on that list, report bugs and request feature on the bugtracker [2]. > > Best, > Thomas > > [1] https://github.com/samoht/irminsule > [2] https://github.com/samoht/irminsule/issues > [3] https://github.com/samoht/irminsule/blob/master/lib/core/irminStore.mli > [4] https://github.com/samoht/irminsule/blob/master/lib/backend/irminMemory.ml > > > > _______________________________________________ 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 Jan 21 18:12:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 18:12: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 1W5foM-0003MA-Fl; Tue, 21 Jan 2014 18:12:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5foK-0003La-BP for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 18:12:28 +0000 Received: from [85.158.137.68:18733] by server-9.bemta-3.messagelabs.com id 5E/E2-13104-B88BED25; Tue, 21 Jan 2014 18:12:27 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-7.tower-31.messagelabs.com!1390327946!10500902!1 X-Originating-IP: [209.85.212.171] 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 4897 invoked from network); 21 Jan 2014 18:12:26 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 18:12:26 -0000 Received: by mail-wi0-f171.google.com with SMTP id cc10so4743904wib.4 for ; Tue, 21 Jan 2014 10:12:26 -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 :content-transfer-encoding:message-id:references:to; bh=ymq/V/xFHBlAhstxEnaHEYNT7GK86ugKgl8HKea2f6M=; b=iIIDNhJGPvKK0mAdnlqX/6GNXzk0hJ4h3Tfa4IgkALX96zT4KMmTtF8hzhM/vIWa1T syRNvr00cgig0nh2xxsojeGuM7SuT2lAoD/6C31sxxASdAr66Ra0UnZt6HHle6vns2Bl 9HJ/weqCPOHXb0Er3XKppC+DUiTnUwFH+KvaobCjSzQLqF2EeeFgAPLJyaMttgMXeZ2o 8bE1DfUhiczhQho7v0h/LhlMiY0o4hVV15EnhANoUUW26FTvVvebS8dikOQ4GG4TL2Pp PDytUFwV9e171bPMvl+pUVEW3jEIXS9gcY7dzGISI/bwF1mC5Q8BtvPw9gFs4O+rqa7Z Bb+w== X-Received: by 10.180.219.44 with SMTP id pl12mr13374291wic.12.1390327946124; Tue, 21 Jan 2014 10:12:26 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id dd3sm9225767wjb.9.2014.01.21.10.12.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Jan 2014 10:12:24 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> Date: Tue, 21 Jan 2014 18:12:24 +0000 Message-Id: References: <7997D2F6-6B63-4CEC-B497-228CCE8CEB4A@gazagnaire.org> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1827) Subject: Re: [MirageOS-devel] irminsule 0.4.0 is 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've just put the rough notes of the demo I've done this morning online: https://github.com/samoht/irminsule/wiki/Getting-Started Thomas On 21 Jan 2014, at 15:27, Thomas Gazagnaire wrote: > I am very happy to cut the first 'early-alpha' release of irminsule[1], which > should be available in OPAM quite soon. > > Irminsule is a distributed database with built-in snapshot, branch and > revert mechanisms. It is designed to use a large variety of backends, > although it is optimized for append-only store. Currently, there are 4 > backends implemented: in-memory, custom binary format on disk, > CRUD interface (using JSON over HTTP) and Git. > > Irminsule is written in pure OCaml. It can thus be compiled to Javascript > -- and run in the browsers; or into a Mirage microkernel -- and run directly > on top of Xen. Currently, though, the package is split into a pure library > ('irminsule'), a bunch of backends (called `irmsule.backend`) and a unix HTTP > server ('irminsule.server'). The HTTP server and some of the backends works > only in unix, but they should be easy to mirage. > > The package also comes with a command-line tool to experiment with the > various backends. > > $ irmin init -m -d # start a daemon to read and store data in memory > $ irmin init -l /path/ -d # start a daemon to read and store data on disk > $ irmin init -r -d # start a daemon to read and store data using a JSON protocol to reach the given uri > # (another irminsule instance should listen on the given uri) > $ irmin init -g -d # start a daemon to read and store data using the Git format > > You can store the default backend in the IRMIN shell variable. Running 'irmin' will automatically look in that variable to select the right backend. > $ export IRMIN=m # memory backend > $ export IRMIN=g # Git backend > $ export IRMIN=l: # local backend > $ export IRMIN=r: # remote backend > > Use `irmin read` and `irmin write` to read a write keys in the dabase. > Use `irmin tree` and `irmin ls` to inspect the database state > Use `irmin dump` to dump the database state in a .dot file > Use `irmin snapshot` to get the current HEAD > Use `irmin revert` to rollback to a previous HEAD > Use `irmin clone` and `irmin fetch` to create/update the local disk store from the given backend. > > For whose interested to write new backends, I suggest to have a look at [3]. If you can provide something which satisfies the `AO_BINARY` signature, it's then easy to build a backend for irminsule (the simplest one being the in-memory one[4]). > > The command are (poorly) documented using `irmin --help`. Feel free to ask questions on that list, report bugs and request feature on the bugtracker [2]. > > Best, > Thomas > > [1] https://github.com/samoht/irminsule > [2] https://github.com/samoht/irminsule/issues > [3] https://github.com/samoht/irminsule/blob/master/lib/core/irminStore.mli > [4] https://github.com/samoht/irminsule/blob/master/lib/backend/irminMemory.ml > > > > _______________________________________________ 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 Jan 21 21:31:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:31: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 1W5iud-0001dk-CT; Tue, 21 Jan 2014 21:31:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5iuc-0001dc-2t; Tue, 21 Jan 2014 21:31:10 +0000 Received: from [85.158.139.211:48602] by server-4.bemta-5.messagelabs.com id 0A/FF-26791-D17EED25; Tue, 21 Jan 2014 21:31:09 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1390339866!11110709!1 X-Originating-IP: [209.85.192.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16463 invoked from network); 21 Jan 2014 21:31:08 -0000 Received: from mail-pd0-f177.google.com (HELO mail-pd0-f177.google.com) (209.85.192.177) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 21:31:08 -0000 Received: by mail-pd0-f177.google.com with SMTP id x10so7394516pdj.36 for ; Tue, 21 Jan 2014 13:31: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:cc:content-type; bh=79rxb3QmQKspzbzZKLGCBrPahxUfKFeeI97JuiW7RMM=; b=Rf4NzOpBUsj+zWGwJIDM354jObMWw72xSKjWrhSzNTCBWt34pCr54RMKRBsYkqHAz+ u/ijlbr8FapJaG2mCDzJiUPghxzz9HWeX8cvD/7f/zIwBCdULC52vRqpyEHnXfCS7pKj NyvzBU6iO8QX6Shwhsv4zy8Jl0yIvIlBmQ6a+5WVVfTBnr6qo+KulYnHFudilG2xCdCa kvCWBTTATWcuA9fUGGIF9Zt68EalL42e2weIwM1M7d2mtdKQIDUlp0Xy9wZ+5xILDAXF QeFFLHeqts6ASo1S5THnylrO0UeZbnJ6lli6AuRZh2D0UvD47bkWUEGyCzj9OpEsCzZb e64Q== MIME-Version: 1.0 X-Received: by 10.66.154.169 with SMTP id vp9mr26808862pab.39.1390339864215; Tue, 21 Jan 2014 13:31:04 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 13:31:04 -0800 (PST) Date: Tue, 21 Jan 2014 21:31:04 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Cc: xen-api@lists.xenproject.org Subject: [MirageOS-devel] xen event channels, grants, block devices etc 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="===============6561168189579890292==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6561168189579890292== Content-Type: multipart/alternative; boundary=047d7b6dd008b948c404f081b963 --047d7b6dd008b948c404f081b963 Content-Type: text/plain; charset=ISO-8859-1 [cc:d xen-api since the event channel / grant code lives in xapi-project] Hi, I've completed the refactoring I mentioned on the mirage call this afternoon. I've removed the package conflicts between mirage-xen and xenctrl over the virtual package "xenctrl". As a result the packages can be installed in parallel and you can choose between Unix and Xen at application final link-time. If you see any library depend on "xenctrl" or 'xen-event" or "xen-grant", these should be changed to 'xen-evtchn" and "xen-gnt". A Xen application can be built with the "mirage" tool as normal: all the Xen stubs are still in the mirage-xen package. A Unix application which wants to implement a Xen block device (e.g. if you want to boot a regular VM from some fancy new storage type) needs to link with the stubs in the packages: "xen-evtchn.unix" "xen-evtchn.unix.activations" "xen-gnt.unix". For an example of this see: https://github.com/mirage/xen-disk To build this, run: $ opam init git://github.com/mirage/opam-repository#mirage-1.1.0 $ opam install xen-disk NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've misunderstood the meaning of depopts in opam. A workaround is just to install "ipaddr" first. Just to demonstrate that a Mirage Xen kernel can still be built with no conflict: $ opam install mirage $ git checkout git://github.com/avsm/mirage-skeleton $ cd mirage-skeleton/basic $ mirage configure --xen $ mirage build $ sudo xl create -c console.xl Cheers, -- Dave Scott --047d7b6dd008b948c404f081b963 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
[cc:d xen-api since the event channel / grant code li= ves in xapi-project]

Hi,

I've co= mpleted the refactoring I mentioned on the mirage call this afternoon. I= 9;ve removed the package conflicts between mirage-xen and xenctrl over the = virtual package "xenctrl". As a result the packages can be instal= led in parallel and you can choose between Unix and Xen at application fina= l link-time.

If you see any library depend on "xenctrl" or= 'xen-event" or "xen-grant", these should be changed to = 'xen-evtchn" and "xen-gnt". A Xen application can be bui= lt with the "mirage" tool as normal: all the Xen stubs are still = in the mirage-xen package. A Unix application which wants to implement a Xe= n block device (e.g. if you want to boot a regular VM from some fancy new s= torage type) needs to link with the stubs in the packages: "xen-evtchn= .unix" "xen-evtchn.unix.activations" "xen-gnt.unix"= ;. For an example of this see:


To build this, run:=

$ opam install xen-disk

NB: I think I&#= 39;m hitting an opam 1.1.0-beta bug where "mirage-types" optional= ly depends on "lwt & ipaddr"; some other package depends on &= quot;lwt"; but "ipaddr" is not being demanded. Anyone else s= eeing this? Perhaps I've misunderstood the meaning of depopts in opam. = A workaround is just to install "ipaddr" first.

Just to demonstrate that a Mirage Xen kernel can still = be built with no conflict:

$ opam install mirage
$ git checkout git://github.com/avsm/mirage-skeleton
$ cd mirage-skeleton/basic
$ mirage configure --xen
$ mirage build
$ sudo xl create -c console.xl

Cheers,
--=A0
Dave Scott
--047d7b6dd008b948c404f081b963-- --===============6561168189579890292== 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 --===============6561168189579890292==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 21 21:31:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:31: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 1W5iud-0001dk-CT; Tue, 21 Jan 2014 21:31:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5iuc-0001dc-2t; Tue, 21 Jan 2014 21:31:10 +0000 Received: from [85.158.139.211:48602] by server-4.bemta-5.messagelabs.com id 0A/FF-26791-D17EED25; Tue, 21 Jan 2014 21:31:09 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1390339866!11110709!1 X-Originating-IP: [209.85.192.177] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16463 invoked from network); 21 Jan 2014 21:31:08 -0000 Received: from mail-pd0-f177.google.com (HELO mail-pd0-f177.google.com) (209.85.192.177) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 21:31:08 -0000 Received: by mail-pd0-f177.google.com with SMTP id x10so7394516pdj.36 for ; Tue, 21 Jan 2014 13:31: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:cc:content-type; bh=79rxb3QmQKspzbzZKLGCBrPahxUfKFeeI97JuiW7RMM=; b=Rf4NzOpBUsj+zWGwJIDM354jObMWw72xSKjWrhSzNTCBWt34pCr54RMKRBsYkqHAz+ u/ijlbr8FapJaG2mCDzJiUPghxzz9HWeX8cvD/7f/zIwBCdULC52vRqpyEHnXfCS7pKj NyvzBU6iO8QX6Shwhsv4zy8Jl0yIvIlBmQ6a+5WVVfTBnr6qo+KulYnHFudilG2xCdCa kvCWBTTATWcuA9fUGGIF9Zt68EalL42e2weIwM1M7d2mtdKQIDUlp0Xy9wZ+5xILDAXF QeFFLHeqts6ASo1S5THnylrO0UeZbnJ6lli6AuRZh2D0UvD47bkWUEGyCzj9OpEsCzZb e64Q== MIME-Version: 1.0 X-Received: by 10.66.154.169 with SMTP id vp9mr26808862pab.39.1390339864215; Tue, 21 Jan 2014 13:31:04 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 13:31:04 -0800 (PST) Date: Tue, 21 Jan 2014 21:31:04 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Cc: xen-api@lists.xenproject.org Subject: [MirageOS-devel] xen event channels, grants, block devices etc 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="===============6561168189579890292==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6561168189579890292== Content-Type: multipart/alternative; boundary=047d7b6dd008b948c404f081b963 --047d7b6dd008b948c404f081b963 Content-Type: text/plain; charset=ISO-8859-1 [cc:d xen-api since the event channel / grant code lives in xapi-project] Hi, I've completed the refactoring I mentioned on the mirage call this afternoon. I've removed the package conflicts between mirage-xen and xenctrl over the virtual package "xenctrl". As a result the packages can be installed in parallel and you can choose between Unix and Xen at application final link-time. If you see any library depend on "xenctrl" or 'xen-event" or "xen-grant", these should be changed to 'xen-evtchn" and "xen-gnt". A Xen application can be built with the "mirage" tool as normal: all the Xen stubs are still in the mirage-xen package. A Unix application which wants to implement a Xen block device (e.g. if you want to boot a regular VM from some fancy new storage type) needs to link with the stubs in the packages: "xen-evtchn.unix" "xen-evtchn.unix.activations" "xen-gnt.unix". For an example of this see: https://github.com/mirage/xen-disk To build this, run: $ opam init git://github.com/mirage/opam-repository#mirage-1.1.0 $ opam install xen-disk NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've misunderstood the meaning of depopts in opam. A workaround is just to install "ipaddr" first. Just to demonstrate that a Mirage Xen kernel can still be built with no conflict: $ opam install mirage $ git checkout git://github.com/avsm/mirage-skeleton $ cd mirage-skeleton/basic $ mirage configure --xen $ mirage build $ sudo xl create -c console.xl Cheers, -- Dave Scott --047d7b6dd008b948c404f081b963 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
[cc:d xen-api since the event channel / grant code li= ves in xapi-project]

Hi,

I've co= mpleted the refactoring I mentioned on the mirage call this afternoon. I= 9;ve removed the package conflicts between mirage-xen and xenctrl over the = virtual package "xenctrl". As a result the packages can be instal= led in parallel and you can choose between Unix and Xen at application fina= l link-time.

If you see any library depend on "xenctrl" or= 'xen-event" or "xen-grant", these should be changed to = 'xen-evtchn" and "xen-gnt". A Xen application can be bui= lt with the "mirage" tool as normal: all the Xen stubs are still = in the mirage-xen package. A Unix application which wants to implement a Xe= n block device (e.g. if you want to boot a regular VM from some fancy new s= torage type) needs to link with the stubs in the packages: "xen-evtchn= .unix" "xen-evtchn.unix.activations" "xen-gnt.unix"= ;. For an example of this see:


To build this, run:=

$ opam install xen-disk

NB: I think I&#= 39;m hitting an opam 1.1.0-beta bug where "mirage-types" optional= ly depends on "lwt & ipaddr"; some other package depends on &= quot;lwt"; but "ipaddr" is not being demanded. Anyone else s= eeing this? Perhaps I've misunderstood the meaning of depopts in opam. = A workaround is just to install "ipaddr" first.

Just to demonstrate that a Mirage Xen kernel can still = be built with no conflict:

$ opam install mirage
$ git checkout git://github.com/avsm/mirage-skeleton
$ cd mirage-skeleton/basic
$ mirage configure --xen
$ mirage build
$ sudo xl create -c console.xl

Cheers,
--=A0
Dave Scott
--047d7b6dd008b948c404f081b963-- --===============6561168189579890292== 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 --===============6561168189579890292==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 21 21:48:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:48:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jB1-0002N1-Uc; Tue, 21 Jan 2014 21:48:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jB0-0002Mn-6R for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 21:48:06 +0000 Received: from [85.158.137.68:33905] by server-14.bemta-3.messagelabs.com id E5/C7-06105-51BEED25; Tue, 21 Jan 2014 21:48:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-31.messagelabs.com!1390340884!9710787!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 11368 invoked from network); 21 Jan 2014 21:48:04 -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 Jan 2014 21:48:04 -0000 Received: (qmail 7733 invoked by uid 634); 21 Jan 2014 21:48:03 -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.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 21 Jan 2014 21:48:03 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 21 Jan 2014 21:48:01 +0000 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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="===============4472417278043636224==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4472417278043636224== Content-Type: multipart/alternative; boundary="Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419" --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 21 Jan 2014, at 21:31, David Scott wrote: > NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" = optionally depends on "lwt & ipaddr"; some other package depends on = "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? = Perhaps I've misunderstood the meaning of depopts in opam. A workaround = is just to install "ipaddr" first. The intention here is to have: - a 'mirage-types' package that is completely dependency free, and only = has module type definitions with completely abstract types. - a 'mirage-types.lwt' package which specializes the above types with = some concrete common defaults, specifically Lwt for IO and Cstruct for = buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the = module signature, you now need those libraries installed to get the cmi = files for them. The OPAM line of: depopts: [ ("lwt" & "cstruct" & "ipaddr") ] means that if all three of the packages are present, then an optional = dependency (the mirage-types.lwt) will be compiled. However, upstream = users of mirage-types.lwt will thus need to explicitly depend on = lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be = present. -anil --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 21 = Jan 2014, at 21:31, David Scott <scott.dj@gmail.com> = wrote:

NB: I = think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally = depends on "lwt & ipaddr"; some other package depends on "lwt"; but = "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've = misunderstood the meaning of depopts in opam. A workaround is just to = install "ipaddr" first.

The intention = here is to have:

- a 'mirage-types' package = that is completely dependency free, and only has module type definitions = with completely abstract types.
- a 'mirage-types.lwt' package = which specializes the above types with some concrete common defaults, = specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. =  Because these are concrete types in the module signature, you now = need those libraries installed to get the cmi files for = them.

The OPAM line = of:

depopts: [ ("lwt" & "cstruct" & = "ipaddr") ]

means that if all three of the = packages are present, then an optional dependency (the mirage-types.lwt) = will be compiled.  However, upstream users of mirage-types.lwt will = thus need to explicitly depend on lwt/cstruct/ipaddr to ensure that = mirage-types.lwt will actually be = present.

-anil

= --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419-- --===============4472417278043636224== 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 --===============4472417278043636224==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 21 21:48:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:48:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jB1-0002N1-Uc; Tue, 21 Jan 2014 21:48:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jB0-0002Mn-6R for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 21:48:06 +0000 Received: from [85.158.137.68:33905] by server-14.bemta-3.messagelabs.com id E5/C7-06105-51BEED25; Tue, 21 Jan 2014 21:48:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-31.messagelabs.com!1390340884!9710787!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 11368 invoked from network); 21 Jan 2014 21:48:04 -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 Jan 2014 21:48:04 -0000 Received: (qmail 7733 invoked by uid 634); 21 Jan 2014 21:48:03 -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.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 21 Jan 2014 21:48:03 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 21 Jan 2014 21:48:01 +0000 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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="===============4472417278043636224==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4472417278043636224== Content-Type: multipart/alternative; boundary="Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419" --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 21 Jan 2014, at 21:31, David Scott wrote: > NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" = optionally depends on "lwt & ipaddr"; some other package depends on = "lwt"; but "ipaddr" is not being demanded. Anyone else seeing this? = Perhaps I've misunderstood the meaning of depopts in opam. A workaround = is just to install "ipaddr" first. The intention here is to have: - a 'mirage-types' package that is completely dependency free, and only = has module type definitions with completely abstract types. - a 'mirage-types.lwt' package which specializes the above types with = some concrete common defaults, specifically Lwt for IO and Cstruct for = buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the = module signature, you now need those libraries installed to get the cmi = files for them. The OPAM line of: depopts: [ ("lwt" & "cstruct" & "ipaddr") ] means that if all three of the packages are present, then an optional = dependency (the mirage-types.lwt) will be compiled. However, upstream = users of mirage-types.lwt will thus need to explicitly depend on = lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be = present. -anil --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 21 = Jan 2014, at 21:31, David Scott <scott.dj@gmail.com> = wrote:

NB: I = think I'm hitting an opam 1.1.0-beta bug where "mirage-types" optionally = depends on "lwt & ipaddr"; some other package depends on "lwt"; but = "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've = misunderstood the meaning of depopts in opam. A workaround is just to = install "ipaddr" first.

The intention = here is to have:

- a 'mirage-types' package = that is completely dependency free, and only has module type definitions = with completely abstract types.
- a 'mirage-types.lwt' package = which specializes the above types with some concrete common defaults, = specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. =  Because these are concrete types in the module signature, you now = need those libraries installed to get the cmi files for = them.

The OPAM line = of:

depopts: [ ("lwt" & "cstruct" & = "ipaddr") ]

means that if all three of the = packages are present, then an optional dependency (the mirage-types.lwt) = will be compiled.  However, upstream users of mirage-types.lwt will = thus need to explicitly depend on lwt/cstruct/ipaddr to ensure that = mirage-types.lwt will actually be = present.

-anil

= --Apple-Mail=_D85989F7-FDA7-420F-B19E-4E52F5D5F419-- --===============4472417278043636224== 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 --===============4472417278043636224==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 21 21:50:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:50: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 1W5jCq-0002mo-95; Tue, 21 Jan 2014 21:50:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jCp-0002mf-9z for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 21:49:59 +0000 Received: from [85.158.143.35:40996] by server-3.bemta-4.messagelabs.com id 35/B9-32360-68BEED25; Tue, 21 Jan 2014 21:49:58 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1390340996!13182781!1 X-Originating-IP: [93.159.202.52] 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 30724 invoked from network); 21 Jan 2014 21:49:56 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-14.tower-21.messagelabs.com with SMTP; 21 Jan 2014 21:49:56 -0000 Received: (qmail 26320 invoked from network); 21 Jan 2014 21:49:54 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 21 Jan 2014 21:49:54 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 25462-08 for ; Tue, 21 Jan 2014 21:49:52 +0000 (GMT) Received: (qmail 26311 invoked by uid 599); 21 Jan 2014 21:49:52 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 21 Jan 2014 21:49:52 +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 1W5jCi-0004MC-8Z; Tue, 21 Jan 2014 21:49:52 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Tue, 21 Jan 2014 21:49:51 +0000 Thread-Topic: [MirageOS-devel] xen event channels, grants, block devices etc Thread-Index: Ac8W8rZankjaEodDTP2UuK1Xxunksg== Message-ID: 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 engine03-20433-8.icritical.com Cc: "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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 Jan 2014, at 21:48, Anil Madhavapeddy wrote: > The intention here is to have: > > - a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. > - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them. ...and just so i'm clear: the code for the mirage-types.* packages is all going to live in the mirage/mirage repo, correct? -- 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 Jan 21 21:50:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:50: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 1W5jCq-0002mo-95; Tue, 21 Jan 2014 21:50:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jCp-0002mf-9z for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 21:49:59 +0000 Received: from [85.158.143.35:40996] by server-3.bemta-4.messagelabs.com id 35/B9-32360-68BEED25; Tue, 21 Jan 2014 21:49:58 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-14.tower-21.messagelabs.com!1390340996!13182781!1 X-Originating-IP: [93.159.202.52] 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 30724 invoked from network); 21 Jan 2014 21:49:56 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-14.tower-21.messagelabs.com with SMTP; 21 Jan 2014 21:49:56 -0000 Received: (qmail 26320 invoked from network); 21 Jan 2014 21:49:54 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 21 Jan 2014 21:49:54 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 25462-08 for ; Tue, 21 Jan 2014 21:49:52 +0000 (GMT) Received: (qmail 26311 invoked by uid 599); 21 Jan 2014 21:49:52 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 21 Jan 2014 21:49:52 +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 1W5jCi-0004MC-8Z; Tue, 21 Jan 2014 21:49:52 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Tue, 21 Jan 2014 21:49:51 +0000 Thread-Topic: [MirageOS-devel] xen event channels, grants, block devices etc Thread-Index: Ac8W8rZankjaEodDTP2UuK1Xxunksg== Message-ID: 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 engine03-20433-8.icritical.com Cc: "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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 Jan 2014, at 21:48, Anil Madhavapeddy wrote: > The intention here is to have: > > - a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. > - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them. ...and just so i'm clear: the code for the mirage-types.* packages is all going to live in the mirage/mirage repo, correct? -- 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 Jan 21 21:52:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:52:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jF4-0002q7-NN; Tue, 21 Jan 2014 21:52:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jF3-0002pw-FE for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 21:52:17 +0000 Received: from [85.158.137.68:46119] by server-11.bemta-3.messagelabs.com id 93/10-19379-01CEED25; Tue, 21 Jan 2014 21:52:16 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-31.messagelabs.com!1390341135!9711223!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 20526 invoked from network); 21 Jan 2014 21:52:15 -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 Jan 2014 21:52:15 -0000 Received: (qmail 23958 invoked by uid 634); 21 Jan 2014 21:52: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.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 21 Jan 2014 21:52:15 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 21 Jan 2014 21:52:13 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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 Jan 2014, at 21:49, Richard Mortier wrote: > > On 21 Jan 2014, at 21:48, Anil Madhavapeddy wrote: > >> The intention here is to have: >> >> - a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. >> - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them. > > ...and just so i'm clear: the code for the mirage-types.* packages is all going to live in the mirage/mirage repo, correct? That's correct. I have a branch in: https://github.com/avsm/mirage/tree/split-libs/types ...with the unified repository, but it's not ready to merge yet. I'm preparing the patch at the moment and will send a separate update about it. -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 Jan 21 21:52:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:52:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jF4-0002q7-NN; Tue, 21 Jan 2014 21:52:18 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jF3-0002pw-FE for mirageos-devel@lists.xenproject.org; Tue, 21 Jan 2014 21:52:17 +0000 Received: from [85.158.137.68:46119] by server-11.bemta-3.messagelabs.com id 93/10-19379-01CEED25; Tue, 21 Jan 2014 21:52:16 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-31.messagelabs.com!1390341135!9711223!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 20526 invoked from network); 21 Jan 2014 21:52:15 -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 Jan 2014 21:52:15 -0000 Received: (qmail 23958 invoked by uid 634); 21 Jan 2014 21:52: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.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 21 Jan 2014 21:52:15 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 21 Jan 2014 21:52:13 +0000 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "xen-api@lists.xenproject.org" , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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 Jan 2014, at 21:49, Richard Mortier wrote: > > On 21 Jan 2014, at 21:48, Anil Madhavapeddy wrote: > >> The intention here is to have: >> >> - a 'mirage-types' package that is completely dependency free, and only has module type definitions with completely abstract types. >> - a 'mirage-types.lwt' package which specializes the above types with some concrete common defaults, specifically Lwt for IO and Cstruct for buffer, Ipaddr.V4.t for ipaddr. Because these are concrete types in the module signature, you now need those libraries installed to get the cmi files for them. > > ...and just so i'm clear: the code for the mirage-types.* packages is all going to live in the mirage/mirage repo, correct? That's correct. I have a branch in: https://github.com/avsm/mirage/tree/split-libs/types ...with the unified repository, but it's not ready to merge yet. I'm preparing the patch at the moment and will send a separate update about it. -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 Jan 21 21:57:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:57: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 1W5jKD-00035D-8D; Tue, 21 Jan 2014 21:57:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jKC-000350-0Y; Tue, 21 Jan 2014 21:57:36 +0000 Received: from [193.109.254.147:44752] by server-2.bemta-14.messagelabs.com id EC/73-00361-F4DEED25; Tue, 21 Jan 2014 21:57:35 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1390341452!12346542!1 X-Originating-IP: [209.85.192.179] 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 26850 invoked from network); 21 Jan 2014 21:57:33 -0000 Received: from mail-pd0-f179.google.com (HELO mail-pd0-f179.google.com) (209.85.192.179) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 21:57:33 -0000 Received: by mail-pd0-f179.google.com with SMTP id q10so6723146pdj.10 for ; Tue, 21 Jan 2014 13:57:31 -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=rv8mROIxALEi3n6k7/eETegSPmU+TgKw86rsG6RzVhQ=; b=SSzyOSNS28b+29qz38hitQ0YSjG9YvJo61CbxCiy//1L7J7sRs74gvD50ZWkN0Ia/v CTdhCdgLSMHqNV+d1yHu5OxpbIHTlsgjHm2bA8O/WJMPWbIGA6Nr47WBQpcLXkVBeC3b rQAoR0EB/er1lZ/tpB9ACFZfMApQF+5f/Dg55q2jPchVJ+B+1J+4uq2nm8/1YCShjtXB /GXc+Fad7kxG9czHxQUdkSlWg/oRcH3cQc2NTbL6mCPZGYIWN1NwaQH33uB+KWRXbKMI pVVFNKEw0XN1oCFYAHcUvX3H+Uv62K3a0jkMGSV1tt88Ox0W3rSKGEsvhtkKHZmjPMbi 9BPQ== MIME-Version: 1.0 X-Received: by 10.68.248.100 with SMTP id yl4mr27289809pbc.41.1390341451657; Tue, 21 Jan 2014 13:57:31 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 13:57:31 -0800 (PST) In-Reply-To: References: Date: Tue, 21 Jan 2014 21:57:31 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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="===============7583728939762702529==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7583728939762702529== Content-Type: multipart/alternative; boundary=047d7b2e14f557b96d04f08218db --047d7b2e14f557b96d04f08218db Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 21, 2014 at 9:48 PM, Anil Madhavapeddy wrote: > On 21 Jan 2014, at 21:31, David Scott wrote: > > NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" > optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; > but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've > misunderstood the meaning of depopts in opam. A workaround is just to > install "ipaddr" first. > > > The intention here is to have: > > - a 'mirage-types' package that is completely dependency free, and only > has module type definitions with completely abstract types. > - a 'mirage-types.lwt' package which specializes the above types with some > concrete common defaults, specifically Lwt for IO and Cstruct for buffer, > Ipaddr.V4.t for ipaddr. Because these are concrete types in the module > signature, you now need those libraries installed to get the cmi files for > them. > > The OPAM line of: > > depopts: [ ("lwt" & "cstruct" & "ipaddr") ] > > means that if all three of the packages are present, then an optional > dependency (the mirage-types.lwt) will be compiled. However, upstream > users of mirage-types.lwt will thus need to explicitly depend on > lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be present. > Ah ok. In my case the BLOCK signature is being used by mirage-block-xen, so I guess I should explicitly add ipaddr to its depends (I'm sure lwt and cstruct are already there). Pity I can't say it depends on 'mirage-types.lwt' -- I guess that would require yet another package. I notice the new mirage-types.lwt will try to build IFF 'lwt' is present: https://github.com/avsm/mirage/blob/split-libs/build#L3 Perhaps we should change this to IFF 'lwt & cstruct & ipaddr' so the error manifests as a 'mirage-types.lwt' is missing higher up the dependency chain where the missing dependency on 'ipaddr' is? Cheers, Dave --047d7b2e14f557b96d04f08218db Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Tue, Jan 21, 2014 at 9:48 PM, Anil Madhavapeddy <anil@recoil.org<= /a>> wrote:
On 2= 1 Jan 2014, at 21:31, David Scott <scott.dj@gmail.com> wrote:

NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types= " optionally depends on "lwt & ipaddr"; some other packa= ge depends on "lwt"; but "ipaddr" is not being demanded= . Anyone else seeing this? Perhaps I've misunderstood the meaning of de= popts in opam. A workaround is just to install "ipaddr" first.

The intention here is to have:
=
- a 'mirage-types' package that is completely depend= ency free, and only has module type definitions with completely abstract ty= pes.
- a 'mirage-types.lwt' package which specializes the above typ= es with some concrete common defaults, specifically Lwt for IO and Cstruct = for buffer, Ipaddr.V4.t for ipaddr. =A0Because these are concrete types in = the module signature, you now need those libraries installed to get the cmi= files for them.

The OPAM line of:

depopts: [ (= "lwt" & "cstruct" & "ipaddr") ]
=

means that if all three of the packages are present, th= en an optional dependency (the mirage-types.lwt) will be compiled. =A0Howev= er, upstream users of mirage-types.lwt will thus need to explicitly depend = on lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be pres= ent.

Ah ok. In my case the BLOCK signatur= e is being used by mirage-block-xen, so I guess I should explicitly add ipa= ddr to its depends (I'm sure lwt and cstruct are already there). Pity I= can't say it depends on 'mirage-types.lwt' -- I guess that wou= ld require yet another package.

I notice the new mirage-types.lwt will try to build IFF= 'lwt' is present:


Perhaps we should change this to IFF 'lwt &am= p; cstruct & ipaddr' so the error manifests as a 'mirage-types.= lwt' is missing higher up the dependency chain where the missing depend= ency on 'ipaddr' is?

Cheers,
Dave
--047d7b2e14f557b96d04f08218db-- --===============7583728939762702529== 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 --===============7583728939762702529==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 21 21:57:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Jan 2014 21:57: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 1W5jKD-00035D-8D; Tue, 21 Jan 2014 21:57:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W5jKC-000350-0Y; Tue, 21 Jan 2014 21:57:36 +0000 Received: from [193.109.254.147:44752] by server-2.bemta-14.messagelabs.com id EC/73-00361-F4DEED25; Tue, 21 Jan 2014 21:57:35 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1390341452!12346542!1 X-Originating-IP: [209.85.192.179] 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 26850 invoked from network); 21 Jan 2014 21:57:33 -0000 Received: from mail-pd0-f179.google.com (HELO mail-pd0-f179.google.com) (209.85.192.179) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 21 Jan 2014 21:57:33 -0000 Received: by mail-pd0-f179.google.com with SMTP id q10so6723146pdj.10 for ; Tue, 21 Jan 2014 13:57:31 -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=rv8mROIxALEi3n6k7/eETegSPmU+TgKw86rsG6RzVhQ=; b=SSzyOSNS28b+29qz38hitQ0YSjG9YvJo61CbxCiy//1L7J7sRs74gvD50ZWkN0Ia/v CTdhCdgLSMHqNV+d1yHu5OxpbIHTlsgjHm2bA8O/WJMPWbIGA6Nr47WBQpcLXkVBeC3b rQAoR0EB/er1lZ/tpB9ACFZfMApQF+5f/Dg55q2jPchVJ+B+1J+4uq2nm8/1YCShjtXB /GXc+Fad7kxG9czHxQUdkSlWg/oRcH3cQc2NTbL6mCPZGYIWN1NwaQH33uB+KWRXbKMI pVVFNKEw0XN1oCFYAHcUvX3H+Uv62K3a0jkMGSV1tt88Ox0W3rSKGEsvhtkKHZmjPMbi 9BPQ== MIME-Version: 1.0 X-Received: by 10.68.248.100 with SMTP id yl4mr27289809pbc.41.1390341451657; Tue, 21 Jan 2014 13:57:31 -0800 (PST) Received: by 10.70.61.136 with HTTP; Tue, 21 Jan 2014 13:57:31 -0800 (PST) In-Reply-To: References: Date: Tue, 21 Jan 2014 21:57:31 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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="===============7583728939762702529==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7583728939762702529== Content-Type: multipart/alternative; boundary=047d7b2e14f557b96d04f08218db --047d7b2e14f557b96d04f08218db Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 21, 2014 at 9:48 PM, Anil Madhavapeddy wrote: > On 21 Jan 2014, at 21:31, David Scott wrote: > > NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types" > optionally depends on "lwt & ipaddr"; some other package depends on "lwt"; > but "ipaddr" is not being demanded. Anyone else seeing this? Perhaps I've > misunderstood the meaning of depopts in opam. A workaround is just to > install "ipaddr" first. > > > The intention here is to have: > > - a 'mirage-types' package that is completely dependency free, and only > has module type definitions with completely abstract types. > - a 'mirage-types.lwt' package which specializes the above types with some > concrete common defaults, specifically Lwt for IO and Cstruct for buffer, > Ipaddr.V4.t for ipaddr. Because these are concrete types in the module > signature, you now need those libraries installed to get the cmi files for > them. > > The OPAM line of: > > depopts: [ ("lwt" & "cstruct" & "ipaddr") ] > > means that if all three of the packages are present, then an optional > dependency (the mirage-types.lwt) will be compiled. However, upstream > users of mirage-types.lwt will thus need to explicitly depend on > lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be present. > Ah ok. In my case the BLOCK signature is being used by mirage-block-xen, so I guess I should explicitly add ipaddr to its depends (I'm sure lwt and cstruct are already there). Pity I can't say it depends on 'mirage-types.lwt' -- I guess that would require yet another package. I notice the new mirage-types.lwt will try to build IFF 'lwt' is present: https://github.com/avsm/mirage/blob/split-libs/build#L3 Perhaps we should change this to IFF 'lwt & cstruct & ipaddr' so the error manifests as a 'mirage-types.lwt' is missing higher up the dependency chain where the missing dependency on 'ipaddr' is? Cheers, Dave --047d7b2e14f557b96d04f08218db Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Tue, Jan 21, 2014 at 9:48 PM, Anil Madhavapeddy <anil@recoil.org<= /a>> wrote:
On 2= 1 Jan 2014, at 21:31, David Scott <scott.dj@gmail.com> wrote:

NB: I think I'm hitting an opam 1.1.0-beta bug where "mirage-types= " optionally depends on "lwt & ipaddr"; some other packa= ge depends on "lwt"; but "ipaddr" is not being demanded= . Anyone else seeing this? Perhaps I've misunderstood the meaning of de= popts in opam. A workaround is just to install "ipaddr" first.

The intention here is to have:
=
- a 'mirage-types' package that is completely depend= ency free, and only has module type definitions with completely abstract ty= pes.
- a 'mirage-types.lwt' package which specializes the above typ= es with some concrete common defaults, specifically Lwt for IO and Cstruct = for buffer, Ipaddr.V4.t for ipaddr. =A0Because these are concrete types in = the module signature, you now need those libraries installed to get the cmi= files for them.

The OPAM line of:

depopts: [ (= "lwt" & "cstruct" & "ipaddr") ]
=

means that if all three of the packages are present, th= en an optional dependency (the mirage-types.lwt) will be compiled. =A0Howev= er, upstream users of mirage-types.lwt will thus need to explicitly depend = on lwt/cstruct/ipaddr to ensure that mirage-types.lwt will actually be pres= ent.

Ah ok. In my case the BLOCK signatur= e is being used by mirage-block-xen, so I guess I should explicitly add ipa= ddr to its depends (I'm sure lwt and cstruct are already there). Pity I= can't say it depends on 'mirage-types.lwt' -- I guess that wou= ld require yet another package.

I notice the new mirage-types.lwt will try to build IFF= 'lwt' is present:


Perhaps we should change this to IFF 'lwt &am= p; cstruct & ipaddr' so the error manifests as a 'mirage-types.= lwt' is missing higher up the dependency chain where the missing depend= ency on 'ipaddr' is?

Cheers,
Dave
--047d7b2e14f557b96d04f08218db-- --===============7583728939762702529== 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 --===============7583728939762702529==-- From mirageos-devel-bounces@lists.xenproject.org Sun Jan 26 09:55:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Jan 2014 09:55: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 1W7MRK-0006Wb-Lc; Sun, 26 Jan 2014 09:55:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7MRJ-0006WR-33 for mirageos-devel@lists.xenproject.org; Sun, 26 Jan 2014 09:55:41 +0000 Received: from [193.109.254.147:36328] by server-15.bemta-14.messagelabs.com id A1/C7-22186-C9BD4E25; Sun, 26 Jan 2014 09:55:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1390730139!13247813!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11400 invoked from network); 26 Jan 2014 09:55:39 -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; 26 Jan 2014 09:55:39 -0000 Received: (qmail 1934 invoked by uid 634); 26 Jan 2014 09:55:38 -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.108]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 26 Jan 2014 09:55:37 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 26 Jan 2014 09:55:36 +0000 Message-Id: <4C257AB4-AF84-4C3F-AB76-78D5A6CEE281@recoil.org> References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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="===============8088384760884564045==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8088384760884564045== Content-Type: multipart/alternative; boundary="Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3" --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 21 Jan 2014, at 21:57, David Scott wrote: >=20 > I notice the new mirage-types.lwt will try to build IFF 'lwt' is = present: >=20 > https://github.com/avsm/mirage/blob/split-libs/build#L3 >=20 > Perhaps we should change this to IFF 'lwt & cstruct & ipaddr' so the = error manifests as a 'mirage-types.lwt' is missing higher up the = dependency chain where the missing dependency on 'ipaddr' is? Thanks for spotting this. I've pushed a fix to my branch with the = correct dependencies. cheers, Anil= --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 21 = Jan 2014, at 21:57, David Scott <scott.dj@gmail.com> = wrote:


I notice the new mirage-types.lwt = will try to build IFF 'lwt' is present:


Perhaps we should change this to IFF = 'lwt & cstruct & ipaddr' so the error manifests as a = 'mirage-types.lwt' is missing higher up the dependency chain where the = missing dependency on 'ipaddr' = is?

Thanks for spotting this. =  I've pushed a fix to my branch with the correct = dependencies.

cheers,
Anil
= = --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3-- --===============8088384760884564045== 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 --===============8088384760884564045==-- From mirageos-devel-bounces@lists.xenproject.org Sun Jan 26 09:55:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Jan 2014 09:55: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 1W7MRK-0006Wb-Lc; Sun, 26 Jan 2014 09:55:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7MRJ-0006WR-33 for mirageos-devel@lists.xenproject.org; Sun, 26 Jan 2014 09:55:41 +0000 Received: from [193.109.254.147:36328] by server-15.bemta-14.messagelabs.com id A1/C7-22186-C9BD4E25; Sun, 26 Jan 2014 09:55:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1390730139!13247813!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11400 invoked from network); 26 Jan 2014 09:55:39 -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; 26 Jan 2014 09:55:39 -0000 Received: (qmail 1934 invoked by uid 634); 26 Jan 2014 09:55:38 -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.108]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 26 Jan 2014 09:55:37 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 26 Jan 2014 09:55:36 +0000 Message-Id: <4C257AB4-AF84-4C3F-AB76-78D5A6CEE281@recoil.org> References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen event channels, grants, block devices etc 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="===============8088384760884564045==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8088384760884564045== Content-Type: multipart/alternative; boundary="Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3" --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 21 Jan 2014, at 21:57, David Scott wrote: >=20 > I notice the new mirage-types.lwt will try to build IFF 'lwt' is = present: >=20 > https://github.com/avsm/mirage/blob/split-libs/build#L3 >=20 > Perhaps we should change this to IFF 'lwt & cstruct & ipaddr' so the = error manifests as a 'mirage-types.lwt' is missing higher up the = dependency chain where the missing dependency on 'ipaddr' is? Thanks for spotting this. I've pushed a fix to my branch with the = correct dependencies. cheers, Anil= --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 21 = Jan 2014, at 21:57, David Scott <scott.dj@gmail.com> = wrote:


I notice the new mirage-types.lwt = will try to build IFF 'lwt' is present:


Perhaps we should change this to IFF = 'lwt & cstruct & ipaddr' so the error manifests as a = 'mirage-types.lwt' is missing higher up the dependency chain where the = missing dependency on 'ipaddr' = is?

Thanks for spotting this. =  I've pushed a fix to my branch with the correct = dependencies.

cheers,
Anil
= = --Apple-Mail=_F138C001-AAA6-4BF0-A961-7E5E5F3256F3-- --===============8088384760884564045== 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 --===============8088384760884564045==-- From mirageos-devel-bounces@lists.xenproject.org Sun Jan 26 10:02:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Jan 2014 10:02: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 1W7MXw-0006wD-FC; Sun, 26 Jan 2014 10:02:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7MXv-0006w8-8q for mirageos-devel@lists.xenproject.org; Sun, 26 Jan 2014 10:02:31 +0000 Received: from [193.109.254.147:14944] by server-12.bemta-14.messagelabs.com id 16/01-13681-63DD4E25; Sun, 26 Jan 2014 10:02:30 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1390730549!13152727!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21526 invoked from network); 26 Jan 2014 10:02:29 -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; 26 Jan 2014 10:02:29 -0000 Received: (qmail 31445 invoked by uid 634); 26 Jan 2014 10:02:28 -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.108]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 26 Jan 2014 10:02:27 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 26 Jan 2014 10:02:26 +0000 Message-Id: <055420F9-FB9E-44AF-AFEE-9765B50386A1@recoil.org> References: To: =?iso-8859-1?Q?Fran=E7ois_Armand?= 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] Which version of Xen for MirageOS? 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="===============0114653177526740616==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0114653177526740616== Content-Type: multipart/alternative; boundary="Apple-Mail=_F837C935-57BE-4141-AF37-D894A3038D90" --Apple-Mail=_F837C935-57BE-4141-AF37-D894A3038D90 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 18 Jan 2014, at 16:17, Fran=E7ois Armand = wrote: > Last week, I had to fight with the Opam environment to get the Hello = in Posix generated. This does not relate to Mirage though. >=20 > - I had to regenerate OPAM from sources, getting it from Ubuntu = (12.10) package led me to get Mirage 0.9.something instead of 1.0.3 Do you remember which Ubuntu package you used for this? The reason this = goes wrong is because you used OPAM 1.0, which has been end-of-lifed = (and so new packages only show up using OPAM 1.1). Debian unstable (and so eventually Ubuntu) have OPAM 1.1 in their = distribution now, so I'm just making sure that we haven't forgotten an = OPAM 1.0 somewhere. cheers Anil >=20 > - Based on Anil's recommandation I had to run apt-get install = ocaml-native-compilers >=20 > Then everything was fine. > I'll go further with Xen within the next days / week I'll let you know = about my issues/success. >=20 >=20 > 2014/1/18 Richard Mortier >=20 > On 18 Jan 2014, at 16:01, Richard Mortier wrote: >=20 > > > > On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote: > > > >> Thanks a lot! > >> Wait! If I understand well enough your own setup, I don't need to = run on bare metal! > >> I missed the point, and apologize about that. > >> > >> If I recap: > >> - start a VirtualBox VM with a Linux distrib (presumably 64 bits) > >> - install Xen 4.2 inside that VM, so I guess in your case your = Ubuntu 13.04 is running within your Dom0 > > > > roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, = install Ubuntu 13.04. then use the ubuntu packages to install Xen in = that VM-- something like "sudo apt-get install = xen-hypervisor-4.2-amd64". (though that was for raring; i notice from = the package list that saucy has 4.3 now.) > > > > you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl = (or whatever) to create mirage (or indeed, any other you want) VMs given = a vm image and a config file. >=20 > ps. i'm starting to put together a blog post describing this and some = of the other "getting started with mirage on xen" steps -- feel free to = email me (and/or the list) if you come across any problems or gotchas so = i can include them. >=20 > -- > Cheers, >=20 > R. >=20 >=20 >=20 >=20 > 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. >=20 > 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. >=20 >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_F837C935-57BE-4141-AF37-D894A3038D90 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 18 = Jan 2014, at 16:17, Fran=E7ois Armand <francois.armand.fa@gmail.com<= /a>> wrote:

Last week, I had to = fight with the Opam environment to get the Hello in Posix generated. = This does not relate to Mirage though.

 - I had to = regenerate OPAM from sources, getting it from Ubuntu (12.10) package led = me to get Mirage 0.9.something instead of = 1.0.3

Do you = remember which Ubuntu package you used for this?  The reason this = goes wrong is because you used OPAM 1.0, which has been end-of-lifed = (and so new packages only show up using OPAM = 1.1).

Debian unstable (and so eventually = Ubuntu) have OPAM 1.1 in their distribution now, so I'm just making sure = that we haven't forgotten an OPAM 1.0 = somewhere.

cheers
Anil




 - Based on Anil's recommandation  I had to run = apt-get install ocaml-native-compilers

Then everything was = fine.
I'll go further with Xen within = the next days / week I'll let you know about my = issues/success.


2014/1/18 = Richard Mortier <Richard.Mortier@nottingham.ac.uk>

On 18 Jan 2014, at 16:01, Richard Mortier wrote:

>
> On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote:
>
>> Thanks a lot!
>> Wait! If I understand well enough your own setup, I don't need = to run on bare metal!
>> I missed the point, and apologize about that.
>>
>> If I recap:
>> - start a VirtualBox VM with a Linux distrib (presumably 64 = bits)
>> - install Xen 4.2 inside that VM, so I guess in your case your = Ubuntu 13.04 is running within your Dom0
>
> roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, = install Ubuntu 13.04. then use the ubuntu packages to install Xen in = that VM-- something like "sudo apt-get install = xen-hypervisor-4.2-amd64".  (though that was for raring; i notice = from the package list that saucy has 4.3 now.)
>
> you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl = (or whatever) to create mirage (or indeed, any other you want) VMs given = a vm image and a config file.

ps. i'm starting to put together a blog post describing this and = some of the other "getting started with mirage on xen" steps -- feel = free to email me (and/or the list) if you come across any problems or = gotchas so i can include them.

--
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.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_F837C935-57BE-4141-AF37-D894A3038D90-- --===============0114653177526740616== 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 --===============0114653177526740616==-- From mirageos-devel-bounces@lists.xenproject.org Sun Jan 26 10:02:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 26 Jan 2014 10:02: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 1W7MXw-0006wD-FC; Sun, 26 Jan 2014 10:02:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7MXv-0006w8-8q for mirageos-devel@lists.xenproject.org; Sun, 26 Jan 2014 10:02:31 +0000 Received: from [193.109.254.147:14944] by server-12.bemta-14.messagelabs.com id 16/01-13681-63DD4E25; Sun, 26 Jan 2014 10:02:30 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1390730549!13152727!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21526 invoked from network); 26 Jan 2014 10:02:29 -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; 26 Jan 2014 10:02:29 -0000 Received: (qmail 31445 invoked by uid 634); 26 Jan 2014 10:02:28 -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.108]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 26 Jan 2014 10:02:27 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 26 Jan 2014 10:02:26 +0000 Message-Id: <055420F9-FB9E-44AF-AFEE-9765B50386A1@recoil.org> References: To: =?iso-8859-1?Q?Fran=E7ois_Armand?= 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] Which version of Xen for MirageOS? 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="===============0114653177526740616==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0114653177526740616== Content-Type: multipart/alternative; boundary="Apple-Mail=_F837C935-57BE-4141-AF37-D894A3038D90" --Apple-Mail=_F837C935-57BE-4141-AF37-D894A3038D90 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 18 Jan 2014, at 16:17, Fran=E7ois Armand = wrote: > Last week, I had to fight with the Opam environment to get the Hello = in Posix generated. This does not relate to Mirage though. >=20 > - I had to regenerate OPAM from sources, getting it from Ubuntu = (12.10) package led me to get Mirage 0.9.something instead of 1.0.3 Do you remember which Ubuntu package you used for this? The reason this = goes wrong is because you used OPAM 1.0, which has been end-of-lifed = (and so new packages only show up using OPAM 1.1). Debian unstable (and so eventually Ubuntu) have OPAM 1.1 in their = distribution now, so I'm just making sure that we haven't forgotten an = OPAM 1.0 somewhere. cheers Anil >=20 > - Based on Anil's recommandation I had to run apt-get install = ocaml-native-compilers >=20 > Then everything was fine. > I'll go further with Xen within the next days / week I'll let you know = about my issues/success. >=20 >=20 > 2014/1/18 Richard Mortier >=20 > On 18 Jan 2014, at 16:01, Richard Mortier wrote: >=20 > > > > On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote: > > > >> Thanks a lot! > >> Wait! If I understand well enough your own setup, I don't need to = run on bare metal! > >> I missed the point, and apologize about that. > >> > >> If I recap: > >> - start a VirtualBox VM with a Linux distrib (presumably 64 bits) > >> - install Xen 4.2 inside that VM, so I guess in your case your = Ubuntu 13.04 is running within your Dom0 > > > > roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, = install Ubuntu 13.04. then use the ubuntu packages to install Xen in = that VM-- something like "sudo apt-get install = xen-hypervisor-4.2-amd64". (though that was for raring; i notice from = the package list that saucy has 4.3 now.) > > > > you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl = (or whatever) to create mirage (or indeed, any other you want) VMs given = a vm image and a config file. >=20 > ps. i'm starting to put together a blog post describing this and some = of the other "getting started with mirage on xen" steps -- feel free to = email me (and/or the list) if you come across any problems or gotchas so = i can include them. >=20 > -- > Cheers, >=20 > R. >=20 >=20 >=20 >=20 > 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. >=20 > 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. >=20 >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_F837C935-57BE-4141-AF37-D894A3038D90 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 18 = Jan 2014, at 16:17, Fran=E7ois Armand <francois.armand.fa@gmail.com<= /a>> wrote:

Last week, I had to = fight with the Opam environment to get the Hello in Posix generated. = This does not relate to Mirage though.

 - I had to = regenerate OPAM from sources, getting it from Ubuntu (12.10) package led = me to get Mirage 0.9.something instead of = 1.0.3

Do you = remember which Ubuntu package you used for this?  The reason this = goes wrong is because you used OPAM 1.0, which has been end-of-lifed = (and so new packages only show up using OPAM = 1.1).

Debian unstable (and so eventually = Ubuntu) have OPAM 1.1 in their distribution now, so I'm just making sure = that we haven't forgotten an OPAM 1.0 = somewhere.

cheers
Anil




 - Based on Anil's recommandation  I had to run = apt-get install ocaml-native-compilers

Then everything was = fine.
I'll go further with Xen within = the next days / week I'll let you know about my = issues/success.


2014/1/18 = Richard Mortier <Richard.Mortier@nottingham.ac.uk>

On 18 Jan 2014, at 16:01, Richard Mortier wrote:

>
> On 18 Jan 2014, at 15:53, Fran=E7ois Armand wrote:
>
>> Thanks a lot!
>> Wait! If I understand well enough your own setup, I don't need = to run on bare metal!
>> I missed the point, and apologize about that.
>>
>> If I recap:
>> - start a VirtualBox VM with a Linux distrib (presumably 64 = bits)
>> - install Xen 4.2 inside that VM, so I guess in your case your = Ubuntu 13.04 is running within your Dom0
>
> roughly, yes. to elaborate-- start VBox, create a 64 bit linux VM, = install Ubuntu 13.04. then use the ubuntu packages to install Xen in = that VM-- something like "sudo apt-get install = xen-hypervisor-4.2-amd64".  (though that was for raring; i notice = from the package list that saucy has 4.3 now.)
>
> you end up with ubuntu 13.04 in dom0 on xen 4.2, and you can use xl = (or whatever) to create mirage (or indeed, any other you want) VMs given = a vm image and a config file.

ps. i'm starting to put together a blog post describing this and = some of the other "getting started with mirage on xen" steps -- feel = free to email me (and/or the list) if you come across any problems or = gotchas so i can include them.

--
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.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_F837C935-57BE-4141-AF37-D894A3038D90-- --===============0114653177526740616== 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 --===============0114653177526740616==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jan 27 09:36:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Jan 2014 09:36: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 1W7icJ-0000hu-Lv; Mon, 27 Jan 2014 09:36:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7icI-0000hm-8t for mirageos-devel@lists.xenproject.org; Mon, 27 Jan 2014 09:36:30 +0000 Received: from [85.158.137.68:23512] by server-7.bemta-3.messagelabs.com id 71/F9-27599-D9826E25; Mon, 27 Jan 2014 09:36:29 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1390815387!7830829!1 X-Originating-IP: [209.85.128.177] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_10_20, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25460 invoked from network); 27 Jan 2014 09:36:28 -0000 Received: from mail-ve0-f177.google.com (HELO mail-ve0-f177.google.com) (209.85.128.177) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2014 09:36:28 -0000 Received: by mail-ve0-f177.google.com with SMTP id jz11so3317110veb.22 for ; Mon, 27 Jan 2014 01:36:27 -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=Xm27KW0GI1W51AEIs2KVHhTByFcupog/qkSZVSkFlc8=; b=ABbCmRDF6dnWO4hg8YI2qV04OelrxyOJyoWJ4cvWmA4xgMWGutVuL0fhztRJizSG3j JXSQgIGyR0A35b5BN4LYMuz8ywYEd2FW5glP0R75waXfMCavYPdWwZxpcLHzJ+XpOOa+ M4hczCdXoeyUQcVdEgQXW8WlrCpoSScfIMlactt1k1rdjTadnUx5Sb322y8ohDOBBfeb dWiotSYLq4IS3TcFZmXZ+hnjqTI5XCTKT2u11OtXkeB00FCLVq93lV4I65Qfsp3byalI BXe0fEpqTWeOGRF8pii5KPnKqqesadSWpH9A29oNYwCCtmm9Mco+ZeElb+g66iLOwlSR LUPg== MIME-Version: 1.0 X-Received: by 10.220.95.139 with SMTP id d11mr15036368vcn.21.1390815386902; Mon, 27 Jan 2014 01:36:26 -0800 (PST) Received: by 10.221.45.136 with HTTP; Mon, 27 Jan 2014 01:36:26 -0800 (PST) Date: Mon, 27 Jan 2014 09:36:26 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] rough thoughts on mirage block servers 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="===============2591713155046870177==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2591713155046870177== Content-Type: multipart/alternative; boundary=001a11c2ae7615a46a04f0f071c2 --001a11c2ae7615a46a04f0f071c2 Content-Type: text/plain; charset=ISO-8859-1 Hi, I did a bit of work tidying up the "xen-disk" userspace app which allows you to attach a synthetic block device to a xen guest. In particular I functorised it over the V1_LWT.BLOCK interface, so any other mirage block device can be used as the backing store for the synthetic device. I tested this by implementing V1_LWT.BLOCK in the ocaml-vhd library, which allows the synthetic device to be backed by a vhd-format file on the xen host. So far so good! While doing a bit of performance optimisation, I hit a bit of a snag. Currently a mirage app using a block device is encouraged to issue BLOCK requests in parallel. For example, a filesystem would probably parallel write all data blocks, Lwt.bind, and then reset a metadata pointer to make the new data live in a final update; in effect the Lwt.bind acts like a 'barrier', forbidding I/O re-ordering across it. In the "xen-disk" app I receive queues of requests from the VM and then I issued them serially -- unsurprisingly the performance is poor. I think I need to create a library which can operate on these queues of requests, identify conficts (reads following writes), and parallelises them as much as possible. The mirage-block-unix implementation is also pretty terrible, since it serialises everything again. We should probably open the file from parellel threads, or switch to some library like aio. I don't know whether the request-paralleliser should know about any kind of maximum queue depth from the server-side, or whether it should just take all the I/O it can get. Ideas or suggestions welcome! Sorry the above was a bit more of a stream-of-consciousness than a coherent picture :-) Cheers, Dave --001a11c2ae7615a46a04f0f071c2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I did a bit of work tidying up the = "xen-disk" userspace app which allows you to attach a synthetic b= lock device to a xen guest. In particular I functorised it over the V1_LWT.= BLOCK interface, so any other mirage block device can be used as the backin= g store for the synthetic device. I tested this by implementing V1_LWT.BLOC= K in the ocaml-vhd library, which allows the synthetic device to be backed = by a vhd-format file on the xen host. So far so good!

While doing a bit of performance optimisation, I hit a = bit of a snag. Currently a mirage app using a block device is encouraged to= issue BLOCK requests in parallel. For example, a filesystem would probably= parallel write all data blocks, Lwt.bind, and then reset a metadata pointe= r to make the new data live in a final update; in effect the Lwt.bind acts = like a 'barrier', forbidding I/O re-ordering across it. In the &quo= t;xen-disk" app I receive queues of requests from the VM and then I is= sued them serially -- unsurprisingly the performance is poor. I think I nee= d to create a library which can operate on these queues of requests, identi= fy conficts (reads following writes), and parallelises them as much as poss= ible.

The mirage-block-unix implementation is also pretty ter= rible, since it serialises everything again. We should probably open the fi= le from parellel threads, or switch to some library like aio. I don't k= now whether the request-paralleliser should know about any kind of maximum = queue depth from the server-side, or whether it should just take all the I/= O it can get.

Ideas or suggestions welcome! Sorry the above was = a bit more of a stream-of-consciousness than a coherent picture :-)

Cheers,
Dave
--001a11c2ae7615a46a04f0f071c2-- --===============2591713155046870177== 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 --===============2591713155046870177==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jan 27 09:36:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Jan 2014 09:36: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 1W7icJ-0000hu-Lv; Mon, 27 Jan 2014 09:36:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7icI-0000hm-8t for mirageos-devel@lists.xenproject.org; Mon, 27 Jan 2014 09:36:30 +0000 Received: from [85.158.137.68:23512] by server-7.bemta-3.messagelabs.com id 71/F9-27599-D9826E25; Mon, 27 Jan 2014 09:36:29 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1390815387!7830829!1 X-Originating-IP: [209.85.128.177] X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_10_20, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25460 invoked from network); 27 Jan 2014 09:36:28 -0000 Received: from mail-ve0-f177.google.com (HELO mail-ve0-f177.google.com) (209.85.128.177) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2014 09:36:28 -0000 Received: by mail-ve0-f177.google.com with SMTP id jz11so3317110veb.22 for ; Mon, 27 Jan 2014 01:36:27 -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=Xm27KW0GI1W51AEIs2KVHhTByFcupog/qkSZVSkFlc8=; b=ABbCmRDF6dnWO4hg8YI2qV04OelrxyOJyoWJ4cvWmA4xgMWGutVuL0fhztRJizSG3j JXSQgIGyR0A35b5BN4LYMuz8ywYEd2FW5glP0R75waXfMCavYPdWwZxpcLHzJ+XpOOa+ M4hczCdXoeyUQcVdEgQXW8WlrCpoSScfIMlactt1k1rdjTadnUx5Sb322y8ohDOBBfeb dWiotSYLq4IS3TcFZmXZ+hnjqTI5XCTKT2u11OtXkeB00FCLVq93lV4I65Qfsp3byalI BXe0fEpqTWeOGRF8pii5KPnKqqesadSWpH9A29oNYwCCtmm9Mco+ZeElb+g66iLOwlSR LUPg== MIME-Version: 1.0 X-Received: by 10.220.95.139 with SMTP id d11mr15036368vcn.21.1390815386902; Mon, 27 Jan 2014 01:36:26 -0800 (PST) Received: by 10.221.45.136 with HTTP; Mon, 27 Jan 2014 01:36:26 -0800 (PST) Date: Mon, 27 Jan 2014 09:36:26 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] rough thoughts on mirage block servers 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="===============2591713155046870177==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2591713155046870177== Content-Type: multipart/alternative; boundary=001a11c2ae7615a46a04f0f071c2 --001a11c2ae7615a46a04f0f071c2 Content-Type: text/plain; charset=ISO-8859-1 Hi, I did a bit of work tidying up the "xen-disk" userspace app which allows you to attach a synthetic block device to a xen guest. In particular I functorised it over the V1_LWT.BLOCK interface, so any other mirage block device can be used as the backing store for the synthetic device. I tested this by implementing V1_LWT.BLOCK in the ocaml-vhd library, which allows the synthetic device to be backed by a vhd-format file on the xen host. So far so good! While doing a bit of performance optimisation, I hit a bit of a snag. Currently a mirage app using a block device is encouraged to issue BLOCK requests in parallel. For example, a filesystem would probably parallel write all data blocks, Lwt.bind, and then reset a metadata pointer to make the new data live in a final update; in effect the Lwt.bind acts like a 'barrier', forbidding I/O re-ordering across it. In the "xen-disk" app I receive queues of requests from the VM and then I issued them serially -- unsurprisingly the performance is poor. I think I need to create a library which can operate on these queues of requests, identify conficts (reads following writes), and parallelises them as much as possible. The mirage-block-unix implementation is also pretty terrible, since it serialises everything again. We should probably open the file from parellel threads, or switch to some library like aio. I don't know whether the request-paralleliser should know about any kind of maximum queue depth from the server-side, or whether it should just take all the I/O it can get. Ideas or suggestions welcome! Sorry the above was a bit more of a stream-of-consciousness than a coherent picture :-) Cheers, Dave --001a11c2ae7615a46a04f0f071c2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I did a bit of work tidying up the = "xen-disk" userspace app which allows you to attach a synthetic b= lock device to a xen guest. In particular I functorised it over the V1_LWT.= BLOCK interface, so any other mirage block device can be used as the backin= g store for the synthetic device. I tested this by implementing V1_LWT.BLOC= K in the ocaml-vhd library, which allows the synthetic device to be backed = by a vhd-format file on the xen host. So far so good!

While doing a bit of performance optimisation, I hit a = bit of a snag. Currently a mirage app using a block device is encouraged to= issue BLOCK requests in parallel. For example, a filesystem would probably= parallel write all data blocks, Lwt.bind, and then reset a metadata pointe= r to make the new data live in a final update; in effect the Lwt.bind acts = like a 'barrier', forbidding I/O re-ordering across it. In the &quo= t;xen-disk" app I receive queues of requests from the VM and then I is= sued them serially -- unsurprisingly the performance is poor. I think I nee= d to create a library which can operate on these queues of requests, identi= fy conficts (reads following writes), and parallelises them as much as poss= ible.

The mirage-block-unix implementation is also pretty ter= rible, since it serialises everything again. We should probably open the fi= le from parellel threads, or switch to some library like aio. I don't k= now whether the request-paralleliser should know about any kind of maximum = queue depth from the server-side, or whether it should just take all the I/= O it can get.

Ideas or suggestions welcome! Sorry the above was = a bit more of a stream-of-consciousness than a coherent picture :-)

Cheers,
Dave
--001a11c2ae7615a46a04f0f071c2-- --===============2591713155046870177== 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 --===============2591713155046870177==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jan 27 09:57:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Jan 2014 09:57: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 1W7iwr-0001Q8-5g; Mon, 27 Jan 2014 09:57:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7iwp-0001Q0-V7 for mirageos-devel@lists.xenproject.org; Mon, 27 Jan 2014 09:57:44 +0000 Received: from [85.158.137.68:3917] by server-14.bemta-3.messagelabs.com id 14/63-06105-79D26E25; Mon, 27 Jan 2014 09:57:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1390816662!11494070!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 4648 invoked from network); 27 Jan 2014 09:57:42 -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; 27 Jan 2014 09:57:42 -0000 Received: (qmail 8215 invoked by uid 634); 27 Jan 2014 09:57: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 host81-149-102-120.in-addr.btopenworld.com (HELO [10.0.0.108]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 27 Jan 2014 09:57:40 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 27 Jan 2014 09:57:37 +0000 Message-Id: <2CB59461-34DB-4EDC-8D37-323102D70CD9@recoil.org> References: 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] rough thoughts on mirage block servers 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 The BLOCK interface is for IO requests, so reordering in a library makes sense (analogous to elevator algorithms in a conventional stack). On the Xen ring interface, do we do enough to expose the parallelism? Requests that are written can be acked out of order in the protocol, and it's not clear to me what the block backend actually does. When I was writing it, I seem to remember that responses always seem to come back in the order they were written, which doesn't seem very parallel at all. The Ring/Lwt should just work at the moment if requests come in out of order (since there is a id->wakener mapping), and bind will not be a barrier in this case should you do a Lwt_list.map_p. -anil On 27 Jan 2014, at 09:36, David Scott wrote: > Hi, > > I did a bit of work tidying up the "xen-disk" userspace app which allows you to attach a synthetic block device to a xen guest. In particular I functorised it over the V1_LWT.BLOCK interface, so any other mirage block device can be used as the backing store for the synthetic device. I tested this by implementing V1_LWT.BLOCK in the ocaml-vhd library, which allows the synthetic device to be backed by a vhd-format file on the xen host. So far so good! > > While doing a bit of performance optimisation, I hit a bit of a snag. Currently a mirage app using a block device is encouraged to issue BLOCK requests in parallel. For example, a filesystem would probably parallel write all data blocks, Lwt.bind, and then reset a metadata pointer to make the new data live in a final update; in effect the Lwt.bind acts like a 'barrier', forbidding I/O re-ordering across it. In the "xen-disk" app I receive queues of requests from the VM and then I issued them serially -- unsurprisingly the performance is poor. I think I need to create a library which can operate on these queues of requests, identify conficts (reads following writes), and parallelises them as much as possible. > > The mirage-block-unix implementation is also pretty terrible, since it serialises everything again. We should probably open the file from parellel threads, or switch to some library like aio. I don't know whether the request-paralleliser should know about any kind of maximum queue depth from the server-side, or whether it should just take all the I/O it can get. > > Ideas or suggestions welcome! Sorry the above was a bit more of a stream-of-consciousness than a coherent picture :-) > > Cheers, > Dave > _______________________________________________ > 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 Jan 27 09:57:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Jan 2014 09:57: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 1W7iwr-0001Q8-5g; Mon, 27 Jan 2014 09:57:45 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7iwp-0001Q0-V7 for mirageos-devel@lists.xenproject.org; Mon, 27 Jan 2014 09:57:44 +0000 Received: from [85.158.137.68:3917] by server-14.bemta-3.messagelabs.com id 14/63-06105-79D26E25; Mon, 27 Jan 2014 09:57:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1390816662!11494070!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 4648 invoked from network); 27 Jan 2014 09:57:42 -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; 27 Jan 2014 09:57:42 -0000 Received: (qmail 8215 invoked by uid 634); 27 Jan 2014 09:57: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 host81-149-102-120.in-addr.btopenworld.com (HELO [10.0.0.108]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 27 Jan 2014 09:57:40 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 27 Jan 2014 09:57:37 +0000 Message-Id: <2CB59461-34DB-4EDC-8D37-323102D70CD9@recoil.org> References: 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] rough thoughts on mirage block servers 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 The BLOCK interface is for IO requests, so reordering in a library makes sense (analogous to elevator algorithms in a conventional stack). On the Xen ring interface, do we do enough to expose the parallelism? Requests that are written can be acked out of order in the protocol, and it's not clear to me what the block backend actually does. When I was writing it, I seem to remember that responses always seem to come back in the order they were written, which doesn't seem very parallel at all. The Ring/Lwt should just work at the moment if requests come in out of order (since there is a id->wakener mapping), and bind will not be a barrier in this case should you do a Lwt_list.map_p. -anil On 27 Jan 2014, at 09:36, David Scott wrote: > Hi, > > I did a bit of work tidying up the "xen-disk" userspace app which allows you to attach a synthetic block device to a xen guest. In particular I functorised it over the V1_LWT.BLOCK interface, so any other mirage block device can be used as the backing store for the synthetic device. I tested this by implementing V1_LWT.BLOCK in the ocaml-vhd library, which allows the synthetic device to be backed by a vhd-format file on the xen host. So far so good! > > While doing a bit of performance optimisation, I hit a bit of a snag. Currently a mirage app using a block device is encouraged to issue BLOCK requests in parallel. For example, a filesystem would probably parallel write all data blocks, Lwt.bind, and then reset a metadata pointer to make the new data live in a final update; in effect the Lwt.bind acts like a 'barrier', forbidding I/O re-ordering across it. In the "xen-disk" app I receive queues of requests from the VM and then I issued them serially -- unsurprisingly the performance is poor. I think I need to create a library which can operate on these queues of requests, identify conficts (reads following writes), and parallelises them as much as possible. > > The mirage-block-unix implementation is also pretty terrible, since it serialises everything again. We should probably open the file from parellel threads, or switch to some library like aio. I don't know whether the request-paralleliser should know about any kind of maximum queue depth from the server-side, or whether it should just take all the I/O it can get. > > Ideas or suggestions welcome! Sorry the above was a bit more of a stream-of-consciousness than a coherent picture :-) > > Cheers, > Dave > _______________________________________________ > 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 Jan 27 10:38:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Jan 2014 10:38: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 1W7jaa-0004iE-0I; Mon, 27 Jan 2014 10:38:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7jaX-0004hh-VI for mirageos-devel@lists.xenproject.org; Mon, 27 Jan 2014 10:38:46 +0000 Received: from [193.109.254.147:29140] by server-14.bemta-14.messagelabs.com id 38/06-12628-53736E25; Mon, 27 Jan 2014 10:38:45 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1390819122!60802!1 X-Originating-IP: [209.85.220.54] 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 26913 invoked from network); 27 Jan 2014 10:38:43 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2014 10:38:43 -0000 Received: by mail-pa0-f54.google.com with SMTP id fa1so5789767pad.27 for ; Mon, 27 Jan 2014 02:38:40 -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=0YgsBHOJtMcwFMCdcFo/Llv8y7i3SN4Lz4I1A18lA7I=; b=lqJ00j3cMilwXoudc+cSpHoQiXGnb+JMknskCH0H/GJCK2s2k/0p/GUQ41F/HIccDx ZLZ4Z526V9v43v33VzgwP8OfP/N05GJfXTx+PTOy051IMEswTLv56DT2W9l+cqf40k8J uB7gukHik535WAQ6f4quDw3RqflLBdMd7DXkJ1Qn0inJmpFT2WTBJKO34EkfEwBLp2QR HPRDmeVDUIWUPtQNz00XU4Fl8YdzmtaxLXQeux1XglXNzU99CAuOaZEn07Wq5uhI3DVI qaabF6rAFf3xhjTnBOiS/hAyZvyUrawI9EA9R+W2NGDjA2cWD2/3/DnajERfckQHQV+F +dUg== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr29253805pbc.42.1390819118730; Mon, 27 Jan 2014 02:38:38 -0800 (PST) Received: by 10.70.65.68 with HTTP; Mon, 27 Jan 2014 02:38:38 -0800 (PST) In-Reply-To: <2CB59461-34DB-4EDC-8D37-323102D70CD9@recoil.org> References: <2CB59461-34DB-4EDC-8D37-323102D70CD9@recoil.org> Date: Mon, 27 Jan 2014 10:38:38 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] rough thoughts on mirage block servers 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="===============7283736194377288714==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7283736194377288714== Content-Type: multipart/alternative; boundary=e89a8ff1c94c84d75d04f0f14f95 --e89a8ff1c94c84d75d04f0f14f95 Content-Type: text/plain; charset=ISO-8859-1 On Monday, January 27, 2014, Anil Madhavapeddy wrote: > The BLOCK interface is for IO requests, so reordering in a library makes > sense (analogous to elevator algorithms in a conventional stack). > > On the Xen ring interface, do we do enough to expose the parallelism? > Requests that are written can be acked out of order in the protocol, and > it's not clear to me what the block backend actually does. When I was > writing it, I seem to remember that responses always seem to come back in > the order they were written, which doesn't seem very parallel at all. Good question. The userspace grant table interface exposes a "map batch" interface and a corresponding "unmap batch", to amortize the costs of the syscall and potentially the TLB flush (although I bet the user to kernel syscall dwarfs the TLB flush for userspace) At the moment the blkback uses this to the max by mapping the whole ring at once. Unfortunately the requests can't be acknowledged until after the unmap because this confuses the frontend. As a result we pull the requests as a batch and can parallelise within the batch (code currently missing) and they all complete at once. For trivial backends (like a /dev/null) it gets a high throughput. It should improve with indirect descriptors since we'll get a larger batch size. The Ring/Lwt should just work at the moment if requests come in out of > order (since there is a id->wakener mapping), and bind will not be a > barrier in this case should you do a Lwt_list.map_p. Yeah. Btw do you happen to know how POSIX aio works? Does it open the file 'n' times to be able to 'seek' and 'write' from parallel threads? Perhaps mirage-block-unix should implement a pool of open file descriptors per device. Dave > > -anil > > On 27 Jan 2014, at 09:36, David Scott > > wrote: > > > Hi, > > > > I did a bit of work tidying up the "xen-disk" userspace app which allows > you to attach a synthetic block device to a xen guest. In particular I > functorised it over the V1_LWT.BLOCK interface, so any other mirage block > device can be used as the backing store for the synthetic device. I tested > this by implementing V1_LWT.BLOCK in the ocaml-vhd library, which allows > the synthetic device to be backed by a vhd-format file on the xen host. So > far so good! > > > > While doing a bit of performance optimisation, I hit a bit of a snag. > Currently a mirage app using a block device is encouraged to issue BLOCK > requests in parallel. For example, a filesystem would probably parallel > write all data blocks, Lwt.bind, and then reset a metadata pointer to make > the new data live in a final update; in effect the Lwt.bind acts like a > 'barrier', forbidding I/O re-ordering across it. In the "xen-disk" app I > receive queues of requests from the VM and then I issued them serially -- > unsurprisingly the performance is poor. I think I need to create a library > which can operate on these queues of requests, identify conficts (reads > following writes), and parallelises them as much as possible. > > > > The mirage-block-unix implementation is also pretty terrible, since it > serialises everything again. We should probably open the file from parellel > threads, or switch to some library like aio. I don't know whether the > request-paralleliser should know about any kind of maximum queue depth from > the server-side, or whether it should just take all the I/O it can get. > > > > Ideas or suggestions welcome! Sorry the above was a bit more of a > stream-of-consciousness than a coherent picture :-) > > > > Cheers, > > Dave > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > -- Dave Scott --e89a8ff1c94c84d75d04f0f14f95 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Monday, January 27, 2014, Anil Madhavapeddy <anil@recoil.org> wrote:
The BLOCK interface is for IO requests, so reordering in a library makes se= nse (analogous to elevator algorithms in a conventional stack).

On the Xen ring interface, do we do enough to expose the parallelism? =A0Re= quests that are written can be acked out of order in the protocol, and it&#= 39;s not clear to me what the block backend actually does. =A0When I was wr= iting it, I seem to remember that responses always seem to come back in the= order they were written, which doesn't seem very parallel at all.

Good question.

The=A0userspace gran= t table interface exposes a "map batch" interface and a correspon= ding "unmap batch", to amortize the costs of the syscall and pote= ntially the TLB flush (although I bet=A0the user to kernel syscall dwarfs t= he TLB flush for userspace)=A0At the moment the blkback uses this to the ma= x by mapping the whole ring at once. Unfortunately the=A0requests can't= be acknowledged until after the unmap because this confuses the frontend. = As a result we pull the requests as a batch and can parallelise=A0within th= e batch (code currently missing) and they all complete at once.=A0For trivi= al backends (like a /dev/null) it gets a high throughput. It should improve= with indirect descriptors since we'll get a larger batch size.


The Ring/Lwt should just work at the moment if requests come in out of orde= r (since there is a id->wakener mapping), and bind will not be a barrier= in this case should you do a Lwt_list.map_p.

Yeah.

Btw do you happen to know how POSIX aio= =A0works?=A0Does it open the file 'n' times to be able to 'seek= ' and 'write' from parallel threads? Perhaps mirage-block-unix = should implement a pool of open file descriptors per device.

Dave

-anil

On 27 Jan 2014, at 09:36, David Scott <scott.dj@gmail= .com> wrote:

> Hi,
>
> I did a bit of work tidying up the "xen-disk" userspace app = which allows you to attach a synthetic block device to a xen guest. In part= icular I functorised it over the V1_LWT.BLOCK interface, so any other mirag= e block device can be used as the backing store for the synthetic device. I= tested this by implementing V1_LWT.BLOCK in the ocaml-vhd library, which a= llows the synthetic device to be backed by a vhd-format file on the xen hos= t. So far so good!
>
> While doing a bit of performance optimisation, I hit a bit of a snag. = Currently a mirage app using a block device is encouraged to issue BLOCK re= quests in parallel. For example, a filesystem would probably parallel write= all data blocks, Lwt.bind, and then reset a metadata pointer to make the n= ew data live in a final update; in effect the Lwt.bind acts like a 'bar= rier', forbidding I/O re-ordering across it. In the "xen-disk"= ; app I receive queues of requests from the VM and then I issued them seria= lly -- unsurprisingly the performance is poor. I think I need to create a l= ibrary which can operate on these queues of requests, identify conficts (re= ads following writes), and parallelises them as much as possible.
>
> The mirage-block-unix implementation is also pretty terrible, since it= serialises everything again. We should probably open the file from parelle= l threads, or switch to some library like aio. I don't know whether the= request-paralleliser should know about any kind of maximum queue depth fro= m the server-side, or whether it should just take all the I/O it can get. >
> Ideas or suggestions welcome! Sorry the above was a bit more of a stre= am-of-consciousness than a coherent picture :-)
>
> Cheers,
> Dave
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org=
> http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel



--
Dave Scott
--e89a8ff1c94c84d75d04f0f14f95-- --===============7283736194377288714== 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 --===============7283736194377288714==-- From mirageos-devel-bounces@lists.xenproject.org Mon Jan 27 10:38:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Jan 2014 10:38: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 1W7jaa-0004iE-0I; Mon, 27 Jan 2014 10:38:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W7jaX-0004hh-VI for mirageos-devel@lists.xenproject.org; Mon, 27 Jan 2014 10:38:46 +0000 Received: from [193.109.254.147:29140] by server-14.bemta-14.messagelabs.com id 38/06-12628-53736E25; Mon, 27 Jan 2014 10:38:45 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1390819122!60802!1 X-Originating-IP: [209.85.220.54] 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 26913 invoked from network); 27 Jan 2014 10:38:43 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Jan 2014 10:38:43 -0000 Received: by mail-pa0-f54.google.com with SMTP id fa1so5789767pad.27 for ; Mon, 27 Jan 2014 02:38:40 -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=0YgsBHOJtMcwFMCdcFo/Llv8y7i3SN4Lz4I1A18lA7I=; b=lqJ00j3cMilwXoudc+cSpHoQiXGnb+JMknskCH0H/GJCK2s2k/0p/GUQ41F/HIccDx ZLZ4Z526V9v43v33VzgwP8OfP/N05GJfXTx+PTOy051IMEswTLv56DT2W9l+cqf40k8J uB7gukHik535WAQ6f4quDw3RqflLBdMd7DXkJ1Qn0inJmpFT2WTBJKO34EkfEwBLp2QR HPRDmeVDUIWUPtQNz00XU4Fl8YdzmtaxLXQeux1XglXNzU99CAuOaZEn07Wq5uhI3DVI qaabF6rAFf3xhjTnBOiS/hAyZvyUrawI9EA9R+W2NGDjA2cWD2/3/DnajERfckQHQV+F +dUg== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr29253805pbc.42.1390819118730; Mon, 27 Jan 2014 02:38:38 -0800 (PST) Received: by 10.70.65.68 with HTTP; Mon, 27 Jan 2014 02:38:38 -0800 (PST) In-Reply-To: <2CB59461-34DB-4EDC-8D37-323102D70CD9@recoil.org> References: <2CB59461-34DB-4EDC-8D37-323102D70CD9@recoil.org> Date: Mon, 27 Jan 2014 10:38:38 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] rough thoughts on mirage block servers 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="===============7283736194377288714==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7283736194377288714== Content-Type: multipart/alternative; boundary=e89a8ff1c94c84d75d04f0f14f95 --e89a8ff1c94c84d75d04f0f14f95 Content-Type: text/plain; charset=ISO-8859-1 On Monday, January 27, 2014, Anil Madhavapeddy wrote: > The BLOCK interface is for IO requests, so reordering in a library makes > sense (analogous to elevator algorithms in a conventional stack). > > On the Xen ring interface, do we do enough to expose the parallelism? > Requests that are written can be acked out of order in the protocol, and > it's not clear to me what the block backend actually does. When I was > writing it, I seem to remember that responses always seem to come back in > the order they were written, which doesn't seem very parallel at all. Good question. The userspace grant table interface exposes a "map batch" interface and a corresponding "unmap batch", to amortize the costs of the syscall and potentially the TLB flush (although I bet the user to kernel syscall dwarfs the TLB flush for userspace) At the moment the blkback uses this to the max by mapping the whole ring at once. Unfortunately the requests can't be acknowledged until after the unmap because this confuses the frontend. As a result we pull the requests as a batch and can parallelise within the batch (code currently missing) and they all complete at once. For trivial backends (like a /dev/null) it gets a high throughput. It should improve with indirect descriptors since we'll get a larger batch size. The Ring/Lwt should just work at the moment if requests come in out of > order (since there is a id->wakener mapping), and bind will not be a > barrier in this case should you do a Lwt_list.map_p. Yeah. Btw do you happen to know how POSIX aio works? Does it open the file 'n' times to be able to 'seek' and 'write' from parallel threads? Perhaps mirage-block-unix should implement a pool of open file descriptors per device. Dave > > -anil > > On 27 Jan 2014, at 09:36, David Scott > > wrote: > > > Hi, > > > > I did a bit of work tidying up the "xen-disk" userspace app which allows > you to attach a synthetic block device to a xen guest. In particular I > functorised it over the V1_LWT.BLOCK interface, so any other mirage block > device can be used as the backing store for the synthetic device. I tested > this by implementing V1_LWT.BLOCK in the ocaml-vhd library, which allows > the synthetic device to be backed by a vhd-format file on the xen host. So > far so good! > > > > While doing a bit of performance optimisation, I hit a bit of a snag. > Currently a mirage app using a block device is encouraged to issue BLOCK > requests in parallel. For example, a filesystem would probably parallel > write all data blocks, Lwt.bind, and then reset a metadata pointer to make > the new data live in a final update; in effect the Lwt.bind acts like a > 'barrier', forbidding I/O re-ordering across it. In the "xen-disk" app I > receive queues of requests from the VM and then I issued them serially -- > unsurprisingly the performance is poor. I think I need to create a library > which can operate on these queues of requests, identify conficts (reads > following writes), and parallelises them as much as possible. > > > > The mirage-block-unix implementation is also pretty terrible, since it > serialises everything again. We should probably open the file from parellel > threads, or switch to some library like aio. I don't know whether the > request-paralleliser should know about any kind of maximum queue depth from > the server-side, or whether it should just take all the I/O it can get. > > > > Ideas or suggestions welcome! Sorry the above was a bit more of a > stream-of-consciousness than a coherent picture :-) > > > > Cheers, > > Dave > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > -- Dave Scott --e89a8ff1c94c84d75d04f0f14f95 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Monday, January 27, 2014, Anil Madhavapeddy <anil@recoil.org> wrote:
The BLOCK interface is for IO requests, so reordering in a library makes se= nse (analogous to elevator algorithms in a conventional stack).

On the Xen ring interface, do we do enough to expose the parallelism? =A0Re= quests that are written can be acked out of order in the protocol, and it&#= 39;s not clear to me what the block backend actually does. =A0When I was wr= iting it, I seem to remember that responses always seem to come back in the= order they were written, which doesn't seem very parallel at all.

Good question.

The=A0userspace gran= t table interface exposes a "map batch" interface and a correspon= ding "unmap batch", to amortize the costs of the syscall and pote= ntially the TLB flush (although I bet=A0the user to kernel syscall dwarfs t= he TLB flush for userspace)=A0At the moment the blkback uses this to the ma= x by mapping the whole ring at once. Unfortunately the=A0requests can't= be acknowledged until after the unmap because this confuses the frontend. = As a result we pull the requests as a batch and can parallelise=A0within th= e batch (code currently missing) and they all complete at once.=A0For trivi= al backends (like a /dev/null) it gets a high throughput. It should improve= with indirect descriptors since we'll get a larger batch size.


The Ring/Lwt should just work at the moment if requests come in out of orde= r (since there is a id->wakener mapping), and bind will not be a barrier= in this case should you do a Lwt_list.map_p.

Yeah.

Btw do you happen to know how POSIX aio= =A0works?=A0Does it open the file 'n' times to be able to 'seek= ' and 'write' from parallel threads? Perhaps mirage-block-unix = should implement a pool of open file descriptors per device.

Dave

-anil

On 27 Jan 2014, at 09:36, David Scott <scott.dj@gmail= .com> wrote:

> Hi,
>
> I did a bit of work tidying up the "xen-disk" userspace app = which allows you to attach a synthetic block device to a xen guest. In part= icular I functorised it over the V1_LWT.BLOCK interface, so any other mirag= e block device can be used as the backing store for the synthetic device. I= tested this by implementing V1_LWT.BLOCK in the ocaml-vhd library, which a= llows the synthetic device to be backed by a vhd-format file on the xen hos= t. So far so good!
>
> While doing a bit of performance optimisation, I hit a bit of a snag. = Currently a mirage app using a block device is encouraged to issue BLOCK re= quests in parallel. For example, a filesystem would probably parallel write= all data blocks, Lwt.bind, and then reset a metadata pointer to make the n= ew data live in a final update; in effect the Lwt.bind acts like a 'bar= rier', forbidding I/O re-ordering across it. In the "xen-disk"= ; app I receive queues of requests from the VM and then I issued them seria= lly -- unsurprisingly the performance is poor. I think I need to create a l= ibrary which can operate on these queues of requests, identify conficts (re= ads following writes), and parallelises them as much as possible.
>
> The mirage-block-unix implementation is also pretty terrible, since it= serialises everything again. We should probably open the file from parelle= l threads, or switch to some library like aio. I don't know whether the= request-paralleliser should know about any kind of maximum queue depth fro= m the server-side, or whether it should just take all the I/O it can get. >
> Ideas or suggestions welcome! Sorry the above was a bit more of a stre= am-of-consciousness than a coherent picture :-)
>
> Cheers,
> Dave
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org=
> http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel



--
Dave Scott
--e89a8ff1c94c84d75d04f0f14f95-- --===============7283736194377288714== 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 --===============7283736194377288714==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 28 09:55:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 09:55: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 1W85OD-0003FF-8i; Tue, 28 Jan 2014 09:55:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W85OC-0003FA-4w for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 09:55:28 +0000 Received: from [85.158.139.211:56515] by server-4.bemta-5.messagelabs.com id 9B/68-26791-F8E77E25; Tue, 28 Jan 2014 09:55:27 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-206.messagelabs.com!1390902924!61864!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3418 invoked from network); 28 Jan 2014 09:55:25 -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; 28 Jan 2014 09:55:25 -0000 Received: (qmail 19490 invoked by uid 634); 28 Jan 2014 09:55:23 -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; Tue, 28 Jan 2014 09:55:19 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 28 Jan 2014 09:55:18 +0000 Message-Id: <370CFA0A-0F3C-4A1C-990F-256EF14104F8@recoil.org> References: <2CB59461-34DB-4EDC-8D37-323102D70CD9@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] rough thoughts on mirage block servers 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="===============2092962534521520743==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2092962534521520743== Content-Type: multipart/alternative; boundary="Apple-Mail=_812E31F1-C835-478F-8FD3-4D3B953354FE" --Apple-Mail=_812E31F1-C835-478F-8FD3-4D3B953354FE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 27 Jan 2014, at 10:38, David Scott wrote: >=20 >=20 > On Monday, January 27, 2014, Anil Madhavapeddy = wrote: > The BLOCK interface is for IO requests, so reordering in a library = makes sense (analogous to elevator algorithms in a conventional stack). >=20 > On the Xen ring interface, do we do enough to expose the parallelism? = Requests that are written can be acked out of order in the protocol, and = it's not clear to me what the block backend actually does. When I was = writing it, I seem to remember that responses always seem to come back = in the order they were written, which doesn't seem very parallel at all. >=20 > Good question. >=20 > The userspace grant table interface exposes a "map batch" interface = and a corresponding "unmap batch", to amortize the costs of the syscall = and potentially the TLB flush (although I bet the user to kernel syscall = dwarfs the TLB flush for userspace) At the moment the blkback uses this = to the max by mapping the whole ring at once. Unfortunately the requests = can't be acknowledged until after the unmap because this confuses the = frontend. As a result we pull the requests as a batch and can = parallelise within the batch (code currently missing) and they all = complete at once. For trivial backends (like a /dev/null) it gets a high = throughput. It should improve with indirect descriptors since we'll get = a larger batch size. This all makes sense. >=20 > The Ring/Lwt should just work at the moment if requests come in out of = order (since there is a id->wakener mapping), and bind will not be a = barrier in this case should you do a Lwt_list.map_p. >=20 > Yeah. >=20 > Btw do you happen to know how POSIX aio works? Does it open the file = 'n' times to be able to 'seek' and 'write' from parallel threads? = Perhaps mirage-block-unix should implement a pool of open file = descriptors per device. Note that POSIX AIO and the Linux libaio are different. POSIX aio = basically uses userspace threads to simulate blocking I/O, and is = probably not that different from what Lwt_unix does (via = Lwt_preemptive). I'm not sure there would be a lot of benefit in going = down this route. The kernel aio (via io_submit) is the one that is scheduled directly = within the kernel and (last I checked) requires O_DIRECT. -anil= --Apple-Mail=_812E31F1-C835-478F-8FD3-4D3B953354FE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 27 = Jan 2014, at 10:38, David Scott <scott.dj@gmail.com> = wrote:



On Monday, January 27, 2014, Anil Madhavapeddy <anil@recoil.org> = wrote:
The BLOCK interface is for IO requests, so reordering in a = library makes sense (analogous to elevator algorithms in a conventional = stack).

On the Xen ring interface, do we do enough to expose the = parallelism?  Requests that are written can be acked out of order = in the protocol, and it's not clear to me what the block backend = actually does.  When I was writing it, I seem to remember that = responses always seem to come back in the order they were written, which = doesn't seem very parallel at all.

Good = question.

The userspace grant table interface = exposes a "map batch" interface and a corresponding "unmap batch", to = amortize the costs of the syscall and potentially the TLB flush = (although I bet the user to kernel syscall dwarfs the TLB flush for = userspace) At the moment the blkback uses this to the max by = mapping the whole ring at once. Unfortunately the requests can't be = acknowledged until after the unmap because this confuses the frontend. = As a result we pull the requests as a batch and can = parallelise within the batch (code currently missing) and they all = complete at once. For trivial backends (like a /dev/null) it gets a = high throughput. It should improve with indirect descriptors since we'll = get a larger batch size.

This all = makes sense.


The Ring/Lwt should just work at the moment if requests come in = out of order (since there is a id->wakener mapping), and bind will = not be a barrier in this case should you do a = Lwt_list.map_p.

Yeah.

=
Btw do you happen to know how POSIX aio works? Does it = open the file 'n' times to be able to 'seek' and 'write' from parallel = threads? Perhaps mirage-block-unix should implement a pool of open file = descriptors per device.

Note that = POSIX AIO and the Linux libaio are different. POSIX aio basically uses = userspace threads to simulate blocking I/O, and is probably not that = different from what Lwt_unix does (via Lwt_preemptive).  I'm not = sure there would be a lot of benefit in going down this = route.

The kernel aio (via io_submit) is the = one that is scheduled directly within the kernel and (last I checked) = requires O_DIRECT.

-anil
= --Apple-Mail=_812E31F1-C835-478F-8FD3-4D3B953354FE-- --===============2092962534521520743== 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 --===============2092962534521520743==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 28 09:55:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 09:55: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 1W85OD-0003FF-8i; Tue, 28 Jan 2014 09:55:29 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W85OC-0003FA-4w for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 09:55:28 +0000 Received: from [85.158.139.211:56515] by server-4.bemta-5.messagelabs.com id 9B/68-26791-F8E77E25; Tue, 28 Jan 2014 09:55:27 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-206.messagelabs.com!1390902924!61864!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3418 invoked from network); 28 Jan 2014 09:55:25 -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; 28 Jan 2014 09:55:25 -0000 Received: (qmail 19490 invoked by uid 634); 28 Jan 2014 09:55:23 -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; Tue, 28 Jan 2014 09:55:19 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 28 Jan 2014 09:55:18 +0000 Message-Id: <370CFA0A-0F3C-4A1C-990F-256EF14104F8@recoil.org> References: <2CB59461-34DB-4EDC-8D37-323102D70CD9@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] rough thoughts on mirage block servers 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="===============2092962534521520743==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2092962534521520743== Content-Type: multipart/alternative; boundary="Apple-Mail=_812E31F1-C835-478F-8FD3-4D3B953354FE" --Apple-Mail=_812E31F1-C835-478F-8FD3-4D3B953354FE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 27 Jan 2014, at 10:38, David Scott wrote: >=20 >=20 > On Monday, January 27, 2014, Anil Madhavapeddy = wrote: > The BLOCK interface is for IO requests, so reordering in a library = makes sense (analogous to elevator algorithms in a conventional stack). >=20 > On the Xen ring interface, do we do enough to expose the parallelism? = Requests that are written can be acked out of order in the protocol, and = it's not clear to me what the block backend actually does. When I was = writing it, I seem to remember that responses always seem to come back = in the order they were written, which doesn't seem very parallel at all. >=20 > Good question. >=20 > The userspace grant table interface exposes a "map batch" interface = and a corresponding "unmap batch", to amortize the costs of the syscall = and potentially the TLB flush (although I bet the user to kernel syscall = dwarfs the TLB flush for userspace) At the moment the blkback uses this = to the max by mapping the whole ring at once. Unfortunately the requests = can't be acknowledged until after the unmap because this confuses the = frontend. As a result we pull the requests as a batch and can = parallelise within the batch (code currently missing) and they all = complete at once. For trivial backends (like a /dev/null) it gets a high = throughput. It should improve with indirect descriptors since we'll get = a larger batch size. This all makes sense. >=20 > The Ring/Lwt should just work at the moment if requests come in out of = order (since there is a id->wakener mapping), and bind will not be a = barrier in this case should you do a Lwt_list.map_p. >=20 > Yeah. >=20 > Btw do you happen to know how POSIX aio works? Does it open the file = 'n' times to be able to 'seek' and 'write' from parallel threads? = Perhaps mirage-block-unix should implement a pool of open file = descriptors per device. Note that POSIX AIO and the Linux libaio are different. POSIX aio = basically uses userspace threads to simulate blocking I/O, and is = probably not that different from what Lwt_unix does (via = Lwt_preemptive). I'm not sure there would be a lot of benefit in going = down this route. The kernel aio (via io_submit) is the one that is scheduled directly = within the kernel and (last I checked) requires O_DIRECT. -anil= --Apple-Mail=_812E31F1-C835-478F-8FD3-4D3B953354FE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 27 = Jan 2014, at 10:38, David Scott <scott.dj@gmail.com> = wrote:



On Monday, January 27, 2014, Anil Madhavapeddy <anil@recoil.org> = wrote:
The BLOCK interface is for IO requests, so reordering in a = library makes sense (analogous to elevator algorithms in a conventional = stack).

On the Xen ring interface, do we do enough to expose the = parallelism?  Requests that are written can be acked out of order = in the protocol, and it's not clear to me what the block backend = actually does.  When I was writing it, I seem to remember that = responses always seem to come back in the order they were written, which = doesn't seem very parallel at all.

Good = question.

The userspace grant table interface = exposes a "map batch" interface and a corresponding "unmap batch", to = amortize the costs of the syscall and potentially the TLB flush = (although I bet the user to kernel syscall dwarfs the TLB flush for = userspace) At the moment the blkback uses this to the max by = mapping the whole ring at once. Unfortunately the requests can't be = acknowledged until after the unmap because this confuses the frontend. = As a result we pull the requests as a batch and can = parallelise within the batch (code currently missing) and they all = complete at once. For trivial backends (like a /dev/null) it gets a = high throughput. It should improve with indirect descriptors since we'll = get a larger batch size.

This all = makes sense.


The Ring/Lwt should just work at the moment if requests come in = out of order (since there is a id->wakener mapping), and bind will = not be a barrier in this case should you do a = Lwt_list.map_p.

Yeah.

=
Btw do you happen to know how POSIX aio works? Does it = open the file 'n' times to be able to 'seek' and 'write' from parallel = threads? Perhaps mirage-block-unix should implement a pool of open file = descriptors per device.

Note that = POSIX AIO and the Linux libaio are different. POSIX aio basically uses = userspace threads to simulate blocking I/O, and is probably not that = different from what Lwt_unix does (via Lwt_preemptive).  I'm not = sure there would be a lot of benefit in going down this = route.

The kernel aio (via io_submit) is the = one that is scheduled directly within the kernel and (last I checked) = requires O_DIRECT.

-anil
= --Apple-Mail=_812E31F1-C835-478F-8FD3-4D3B953354FE-- --===============2092962534521520743== 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 --===============2092962534521520743==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 28 12:14:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 12:14: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 1W87Yb-0002Wl-TI; Tue, 28 Jan 2014 12:14:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W87Ya-0002We-6C for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 12:14:20 +0000 Received: from [85.158.137.68:45048] by server-16.bemta-3.messagelabs.com id BA/C4-26128-B1F97E25; Tue, 28 Jan 2014 12:14:19 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1390911256!10637270!1 X-Originating-IP: [209.85.220.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20065 invoked from network); 28 Jan 2014 12:14:18 -0000 Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com) (209.85.220.52) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 12:14:18 -0000 Received: by mail-pa0-f52.google.com with SMTP id bj1so290837pad.25 for ; Tue, 28 Jan 2014 04:13:17 -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=tdvZolcp/oi3BaXxl/Qx1V6yO5TKQ4ARNrQnWw6hses=; b=Ll3Bgvux5YwFkDN6/CgRlOzu0OF6UHa9JFnZ6B7C90oZ2snF39R58xDZy3Yt9p7khE DtNEEdW45siaqfPuDOyTl/dHx+txYWxgV4V2WA3+76N/Aj6hFNLWxMtoPnn3q8zDTJmh 4wEP+Oivw/M9vhySS4mEzzlmLcTPKf8N0D2aHOkcx1lJU5pAQZE8JVA+YDuFE6VgaZoH 0LszM14YJ4zeXGU+kevYnDCG1jlfnRKjzXGehLhm3v71897OjMQiHI5a8YTvUgXzPJQi vljc+zGCn5HpG/jRDtZnJdXG/JDQk55aRtJDeHsFPIkniWXtq/An+zQ4Ct59TbW8A+np hK6Q== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr1239543pbc.42.1390911196991; Tue, 28 Jan 2014 04:13:16 -0800 (PST) Received: by 10.70.65.68 with HTTP; Tue, 28 Jan 2014 04:13:16 -0800 (PST) Date: Tue, 28 Jan 2014 12:13:16 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] xen and multiple block devices 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="===============8972328908676672089==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8972328908676672089== Content-Type: multipart/alternative; boundary=e89a8ff1c94ccf95ef04f106bf93 --e89a8ff1c94ccf95ef04f106bf93 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've just changed the way the xen blkfront "connect" function maps BLOCK.ids to xen virtual devices. It uses the following heuristics, first match wins: 1. the id is a "xen virtual disk number" (e.g. "51712"). Each disk has a unique slot number on the "virtual bus" (like what you get with IDE, SCSI). This is the pure but somewhat low-level interface. 2. the id is a "Linux device string (with or without "/dev/" prefix)" (e.g. "xvda"). This is what you normally write in your xl/xm config files. This works because the slot numbers on the xen "virtual bus" were originally derived from Linux device major/minor numbers. This notation has survived as the slightly more human-readable low-level interface. 3. the id uniquely matches the "params" key in a xenstore disk *backend*. This is a bit of a hack, but a potentially convenient one in future. If you BLOCK.connect to "/dev/loop0" then it should find the virtual device backed by "/dev/loop0" (wherever it happens to be on the "virtual bus"). This is likely to work well in simple setups, but advanced users with driver domains won't find it sufficiently reliable. So in mirage-skeleton/basic_block/config.ml you can change the line to: let block = block_of_file "/dev/loop0" in and then your VM console will have lines like: Block.connect /dev/loop0: interpreting /dev/loop0 as a backend params key, translating to 51712 Block.connect /dev/loop0 -> 51712 Blkfront.create; vdev=51712 HTH all the multi-disk users out there! Cheers, -- Dave Scott --e89a8ff1c94ccf95ef04f106bf93 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I've just changed the way the x= en blkfront "connect" function maps BLOCK.ids to xen virtual devi= ces. It uses the following heuristics, first match wins:

1. the id is a "xen virtual disk number" (e.g. "51712&q= uot;). Each disk has a unique slot number on the "virtual bus" (l= ike what you get with IDE, SCSI). This is the pure but somewhat low-level i= nterface.

2. the id is a "Linux device string (with or witho= ut "/dev/" prefix)" (e.g. "xvda"). This is what yo= u normally write in your xl/xm config files. This works because the slot nu= mbers on the xen "virtual bus" were originally derived from Linux= device major/minor numbers. This notation has survived as the slightly mor= e human-readable low-level interface.

3. the id uniquely matches the "params" key i= n a xenstore disk *backend*. This is a bit of a hack, but a potentially con= venient one in future. If you BLOCK.connect to "/dev/loop0" then = it should find the virtual device backed by "/dev/loop0" (whereve= r it happens to be on the "virtual bus"). This is likely to work = well in simple setups, but advanced users with driver domains won't fin= d it sufficiently reliable.

So in mirage-skeleton/basic_block/config.ml you can change the line to:

=
=A0 let block =3D block_of_file "/dev/loop0" in
<= div>
and then your VM console will have lines like:
Block.connect /dev/loop0: interpreting /dev/loop0 as a bac= kend params key, translating to 51712
Block.connect /dev/loop0 -&= gt; 51712
Blkfront.create; vdev=3D51712

HTH all t= he multi-disk users out there!

Cheers,
-= -
Dave Scott
--e89a8ff1c94ccf95ef04f106bf93-- --===============8972328908676672089== 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 --===============8972328908676672089==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 28 12:14:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 12:14: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 1W87Yb-0002Wl-TI; Tue, 28 Jan 2014 12:14:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W87Ya-0002We-6C for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 12:14:20 +0000 Received: from [85.158.137.68:45048] by server-16.bemta-3.messagelabs.com id BA/C4-26128-B1F97E25; Tue, 28 Jan 2014 12:14:19 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1390911256!10637270!1 X-Originating-IP: [209.85.220.52] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20065 invoked from network); 28 Jan 2014 12:14:18 -0000 Received: from mail-pa0-f52.google.com (HELO mail-pa0-f52.google.com) (209.85.220.52) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 12:14:18 -0000 Received: by mail-pa0-f52.google.com with SMTP id bj1so290837pad.25 for ; Tue, 28 Jan 2014 04:13:17 -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=tdvZolcp/oi3BaXxl/Qx1V6yO5TKQ4ARNrQnWw6hses=; b=Ll3Bgvux5YwFkDN6/CgRlOzu0OF6UHa9JFnZ6B7C90oZ2snF39R58xDZy3Yt9p7khE DtNEEdW45siaqfPuDOyTl/dHx+txYWxgV4V2WA3+76N/Aj6hFNLWxMtoPnn3q8zDTJmh 4wEP+Oivw/M9vhySS4mEzzlmLcTPKf8N0D2aHOkcx1lJU5pAQZE8JVA+YDuFE6VgaZoH 0LszM14YJ4zeXGU+kevYnDCG1jlfnRKjzXGehLhm3v71897OjMQiHI5a8YTvUgXzPJQi vljc+zGCn5HpG/jRDtZnJdXG/JDQk55aRtJDeHsFPIkniWXtq/An+zQ4Ct59TbW8A+np hK6Q== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr1239543pbc.42.1390911196991; Tue, 28 Jan 2014 04:13:16 -0800 (PST) Received: by 10.70.65.68 with HTTP; Tue, 28 Jan 2014 04:13:16 -0800 (PST) Date: Tue, 28 Jan 2014 12:13:16 +0000 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] xen and multiple block devices 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="===============8972328908676672089==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8972328908676672089== Content-Type: multipart/alternative; boundary=e89a8ff1c94ccf95ef04f106bf93 --e89a8ff1c94ccf95ef04f106bf93 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've just changed the way the xen blkfront "connect" function maps BLOCK.ids to xen virtual devices. It uses the following heuristics, first match wins: 1. the id is a "xen virtual disk number" (e.g. "51712"). Each disk has a unique slot number on the "virtual bus" (like what you get with IDE, SCSI). This is the pure but somewhat low-level interface. 2. the id is a "Linux device string (with or without "/dev/" prefix)" (e.g. "xvda"). This is what you normally write in your xl/xm config files. This works because the slot numbers on the xen "virtual bus" were originally derived from Linux device major/minor numbers. This notation has survived as the slightly more human-readable low-level interface. 3. the id uniquely matches the "params" key in a xenstore disk *backend*. This is a bit of a hack, but a potentially convenient one in future. If you BLOCK.connect to "/dev/loop0" then it should find the virtual device backed by "/dev/loop0" (wherever it happens to be on the "virtual bus"). This is likely to work well in simple setups, but advanced users with driver domains won't find it sufficiently reliable. So in mirage-skeleton/basic_block/config.ml you can change the line to: let block = block_of_file "/dev/loop0" in and then your VM console will have lines like: Block.connect /dev/loop0: interpreting /dev/loop0 as a backend params key, translating to 51712 Block.connect /dev/loop0 -> 51712 Blkfront.create; vdev=51712 HTH all the multi-disk users out there! Cheers, -- Dave Scott --e89a8ff1c94ccf95ef04f106bf93 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I've just changed the way the x= en blkfront "connect" function maps BLOCK.ids to xen virtual devi= ces. It uses the following heuristics, first match wins:

1. the id is a "xen virtual disk number" (e.g. "51712&q= uot;). Each disk has a unique slot number on the "virtual bus" (l= ike what you get with IDE, SCSI). This is the pure but somewhat low-level i= nterface.

2. the id is a "Linux device string (with or witho= ut "/dev/" prefix)" (e.g. "xvda"). This is what yo= u normally write in your xl/xm config files. This works because the slot nu= mbers on the xen "virtual bus" were originally derived from Linux= device major/minor numbers. This notation has survived as the slightly mor= e human-readable low-level interface.

3. the id uniquely matches the "params" key i= n a xenstore disk *backend*. This is a bit of a hack, but a potentially con= venient one in future. If you BLOCK.connect to "/dev/loop0" then = it should find the virtual device backed by "/dev/loop0" (whereve= r it happens to be on the "virtual bus"). This is likely to work = well in simple setups, but advanced users with driver domains won't fin= d it sufficiently reliable.

So in mirage-skeleton/basic_block/config.ml you can change the line to:

=
=A0 let block =3D block_of_file "/dev/loop0" in
<= div>
and then your VM console will have lines like:
Block.connect /dev/loop0: interpreting /dev/loop0 as a bac= kend params key, translating to 51712
Block.connect /dev/loop0 -&= gt; 51712
Blkfront.create; vdev=3D51712

HTH all t= he multi-disk users out there!

Cheers,
-= -
Dave Scott
--e89a8ff1c94ccf95ef04f106bf93-- --===============8972328908676672089== 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 --===============8972328908676672089==-- From mirageos-devel-bounces@lists.xenproject.org Tue Jan 28 12:35:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 12:35: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 1W87sj-0003gA-CJ; Tue, 28 Jan 2014 12:35:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W87si-0003g1-Lr for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 12:35:08 +0000 Received: from [193.109.254.147:29087] by server-10.bemta-14.messagelabs.com id 3C/05-20752-BF3A7E25; Tue, 28 Jan 2014 12:35:07 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-27.messagelabs.com!1390912507!335680!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 24573 invoked from network); 28 Jan 2014 12:35:07 -0000 Received: from engine01-20433-9.icritical.com (HELO engine01-20433-9.icritical.com) (151.236.209.34) by server-9.tower-27.messagelabs.com with SMTP; 28 Jan 2014 12:35:07 -0000 Received: (qmail 14599 invoked from network); 28 Jan 2014 12:35:24 -0000 Received: from localhost (127.0.0.1) by engine01-20433-9.icritical.com with SMTP; 28 Jan 2014 12:35:24 -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 14459-04 for ; Tue, 28 Jan 2014 12:35:24 +0000 (GMT) Received: (qmail 12867 invoked by uid 599); 28 Jan 2014 12:29:43 -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, 28 Jan 2014 12:29:43 +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 1W87n6-0006vG-Gw; Tue, 28 Jan 2014 12:29:20 +0000 From: Richard Mortier To: David Scott Date: Tue, 28 Jan 2014 12:29:20 +0000 Thread-Topic: [MirageOS-devel] xen and multiple block devices Thread-Index: Ac8cJJEW1S9eJKwURdG0l36IotYiuA== Message-ID: 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 engine01-20433-9.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen and multiple block devices 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 28 Jan 2014, at 12:13, David Scott wrote: > ... > So in mirage-skeleton/basic_block/config.ml you can change the line to: > > let block = block_of_file "/dev/loop0" in > > and then your VM console will have lines like: > > Block.connect /dev/loop0: interpreting /dev/loop0 as a backend params key, translating to 51712 > Block.connect /dev/loop0 -> 51712 > Blkfront.create; vdev=51712 thanks :) out of curiosity, are there any constraints on the "/dev/loop0" parameter, or is it just an opaque key string? -- 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 Jan 28 12:35:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 12:35: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 1W87sj-0003gA-CJ; Tue, 28 Jan 2014 12:35:09 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W87si-0003g1-Lr for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 12:35:08 +0000 Received: from [193.109.254.147:29087] by server-10.bemta-14.messagelabs.com id 3C/05-20752-BF3A7E25; Tue, 28 Jan 2014 12:35:07 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-27.messagelabs.com!1390912507!335680!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 24573 invoked from network); 28 Jan 2014 12:35:07 -0000 Received: from engine01-20433-9.icritical.com (HELO engine01-20433-9.icritical.com) (151.236.209.34) by server-9.tower-27.messagelabs.com with SMTP; 28 Jan 2014 12:35:07 -0000 Received: (qmail 14599 invoked from network); 28 Jan 2014 12:35:24 -0000 Received: from localhost (127.0.0.1) by engine01-20433-9.icritical.com with SMTP; 28 Jan 2014 12:35:24 -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 14459-04 for ; Tue, 28 Jan 2014 12:35:24 +0000 (GMT) Received: (qmail 12867 invoked by uid 599); 28 Jan 2014 12:29:43 -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, 28 Jan 2014 12:29:43 +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 1W87n6-0006vG-Gw; Tue, 28 Jan 2014 12:29:20 +0000 From: Richard Mortier To: David Scott Date: Tue, 28 Jan 2014 12:29:20 +0000 Thread-Topic: [MirageOS-devel] xen and multiple block devices Thread-Index: Ac8cJJEW1S9eJKwURdG0l36IotYiuA== Message-ID: 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 engine01-20433-9.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xen and multiple block devices 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 28 Jan 2014, at 12:13, David Scott wrote: > ... > So in mirage-skeleton/basic_block/config.ml you can change the line to: > > let block = block_of_file "/dev/loop0" in > > and then your VM console will have lines like: > > Block.connect /dev/loop0: interpreting /dev/loop0 as a backend params key, translating to 51712 > Block.connect /dev/loop0 -> 51712 > Blkfront.create; vdev=51712 thanks :) out of curiosity, are there any constraints on the "/dev/loop0" parameter, or is it just an opaque key string? -- 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 Jan 28 13:09:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 13:09: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 1W88QK-0005K1-RZ; Tue, 28 Jan 2014 13:09:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W88QI-0005Jw-QO for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 13:09:51 +0000 Received: from [85.158.139.211:16834] by server-12.bemta-5.messagelabs.com id B8/E4-30017-C1CA7E25; Tue, 28 Jan 2014 13:09:48 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1390914586!119904!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 28415 invoked from network); 28 Jan 2014 13:09:47 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 13:09:47 -0000 X-IronPort-AV: E=Sophos;i="4.95,736,1384300800"; d="scan'208";a="97217296" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 28 Jan 2014 13:09:45 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 28 Jan 2014 08:09:45 -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; Tue, 28 Jan 2014 14:09:43 +0100 From: Dave Scott To: Richard Mortier Thread-Topic: [MirageOS-devel] xen and multiple block devices Thread-Index: AQHPHCKCm59A7WZGM0+cmw0DGCY8x5qaABoAgAAcDBI= Date: Tue, 28 Jan 2014 13:09:43 +0000 Message-ID: References: , 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" Subject: Re: [MirageOS-devel] xen and multiple block devices 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 Jan 28, 2014, at 12:35 PM, "Richard Mortier" wrote: > > >> On 28 Jan 2014, at 12:13, David Scott wrote: >> ... >> So in mirage-skeleton/basic_block/config.ml you can change the line to: >> >> let block = block_of_file "/dev/loop0" in >> >> and then your VM console will have lines like: >> >> Block.connect /dev/loop0: interpreting /dev/loop0 as a backend params key, translating to 51712 >> Block.connect /dev/loop0 -> 51712 >> Blkfront.create; vdev=51712 > > thanks :) > > out of curiosity, are there any constraints on the "/dev/loop0" parameter, or is it just an opaque key string? /dev/loop0 has to be the backing storage mentioned in your .xl file. Xl will put the key in xenstore and Linux kernel blkback (via some horrific udev mess that you don't want to know about) will open / read / write. You can write normal file names in the .xl file, which xl should magically handle. On my Debian laptop it's broken, but I was hoping that if we used the raw file name then it would work under both xen and unix transparently.This may require a bit more tweaking to strip off any prefix which xl might add (like "aio:") Anyway, let me know if this helps. In future I'd also like to add support for "connecting" to a labelled partition, which would help lift us out of this particular rathole altogether :-) Cheers, Dave > > -- > 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 Tue Jan 28 13:09:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 13:09: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 1W88QK-0005K1-RZ; Tue, 28 Jan 2014 13:09:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W88QI-0005Jw-QO for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 13:09:51 +0000 Received: from [85.158.139.211:16834] by server-12.bemta-5.messagelabs.com id B8/E4-30017-C1CA7E25; Tue, 28 Jan 2014 13:09:48 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1390914586!119904!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 28415 invoked from network); 28 Jan 2014 13:09:47 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 13:09:47 -0000 X-IronPort-AV: E=Sophos;i="4.95,736,1384300800"; d="scan'208";a="97217296" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 28 Jan 2014 13:09:45 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 28 Jan 2014 08:09:45 -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; Tue, 28 Jan 2014 14:09:43 +0100 From: Dave Scott To: Richard Mortier Thread-Topic: [MirageOS-devel] xen and multiple block devices Thread-Index: AQHPHCKCm59A7WZGM0+cmw0DGCY8x5qaABoAgAAcDBI= Date: Tue, 28 Jan 2014 13:09:43 +0000 Message-ID: References: , 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" Subject: Re: [MirageOS-devel] xen and multiple block devices 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 Jan 28, 2014, at 12:35 PM, "Richard Mortier" wrote: > > >> On 28 Jan 2014, at 12:13, David Scott wrote: >> ... >> So in mirage-skeleton/basic_block/config.ml you can change the line to: >> >> let block = block_of_file "/dev/loop0" in >> >> and then your VM console will have lines like: >> >> Block.connect /dev/loop0: interpreting /dev/loop0 as a backend params key, translating to 51712 >> Block.connect /dev/loop0 -> 51712 >> Blkfront.create; vdev=51712 > > thanks :) > > out of curiosity, are there any constraints on the "/dev/loop0" parameter, or is it just an opaque key string? /dev/loop0 has to be the backing storage mentioned in your .xl file. Xl will put the key in xenstore and Linux kernel blkback (via some horrific udev mess that you don't want to know about) will open / read / write. You can write normal file names in the .xl file, which xl should magically handle. On my Debian laptop it's broken, but I was hoping that if we used the raw file name then it would work under both xen and unix transparently.This may require a bit more tweaking to strip off any prefix which xl might add (like "aio:") Anyway, let me know if this helps. In future I'd also like to add support for "connecting" to a labelled partition, which would help lift us out of this particular rathole altogether :-) Cheers, Dave > > -- > 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 Tue Jan 28 13:55:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 13:55: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 1W897z-0006U6-Kd; Tue, 28 Jan 2014 13:54:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W897y-0006Tu-ET for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 13:54:58 +0000 Received: from [193.109.254.147:23803] by server-10.bemta-14.messagelabs.com id 77/94-20752-1B6B7E25; Tue, 28 Jan 2014 13:54:57 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1390917296!354706!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_SEX,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1993 invoked from network); 28 Jan 2014 13:54:56 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 13:54:56 -0000 Received: by mail-wg0-f51.google.com with SMTP id z12so836345wgg.30 for ; Tue, 28 Jan 2014 05:54:56 -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=1KZm4BjhqSNlL7j3KoXkcYOsI5joh9Z2wFRDmUrUbnM=; b=Gk21K3oqXclgM6IXLhBFefRObLR54Op9UZgYzrde4UnRUiE9vEY9TyefIFHLINocQ4 qJvZDc66nqJs6IdUSVf6fnMeQCZqzzM64Bog9a9Gms6EZ/HYDmK7qutxxdeuOoCRDgP6 hUCjM+P7qjp+5qOU/OQ8s1FEqjpkLJ+H3cIjolkvbuhCJphGwUdAj7ETs2mOYHc4PLNM MlD1/SlyM6RebilWbtcBw/bqT5INmQVSfcRjOuh7znDY/+vkg2IEjIqEkXlU6B/2CP7z tWe5HBC24iJz6xiXEUQFLwkqEhj/6EVWXyX4Xjn99LKLP9EkxZedeq2ZKU4A6+uz117Z 7M+w== X-Received: by 10.181.13.40 with SMTP id ev8mr2134573wid.16.1390917296523; Tue, 28 Jan 2014 05:54:56 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id fb8sm11574023wic.3.2014.01.28.05.54.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 05:54:55 -0800 (PST) Message-ID: <52E7B6AF.3050604@xen.org> Date: Tue, 28 Jan 2014 13:54:55 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.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> In-Reply-To: <52DCE9FA.6010400@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: 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 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 get = into GSoC 2014 will be relatively slim. 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 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_Projects urgently = > (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 From mirageos-devel-bounces@lists.xenproject.org Tue Jan 28 13:55:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 28 Jan 2014 13:55: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 1W897z-0006U6-Kd; Tue, 28 Jan 2014 13:54:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1W897y-0006Tu-ET for mirageos-devel@lists.xenproject.org; Tue, 28 Jan 2014 13:54:58 +0000 Received: from [193.109.254.147:23803] by server-10.bemta-14.messagelabs.com id 77/94-20752-1B6B7E25; Tue, 28 Jan 2014 13:54:57 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1390917296!354706!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_SEX,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1993 invoked from network); 28 Jan 2014 13:54:56 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Jan 2014 13:54:56 -0000 Received: by mail-wg0-f51.google.com with SMTP id z12so836345wgg.30 for ; Tue, 28 Jan 2014 05:54:56 -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=1KZm4BjhqSNlL7j3KoXkcYOsI5joh9Z2wFRDmUrUbnM=; b=Gk21K3oqXclgM6IXLhBFefRObLR54Op9UZgYzrde4UnRUiE9vEY9TyefIFHLINocQ4 qJvZDc66nqJs6IdUSVf6fnMeQCZqzzM64Bog9a9Gms6EZ/HYDmK7qutxxdeuOoCRDgP6 hUCjM+P7qjp+5qOU/OQ8s1FEqjpkLJ+H3cIjolkvbuhCJphGwUdAj7ETs2mOYHc4PLNM MlD1/SlyM6RebilWbtcBw/bqT5INmQVSfcRjOuh7znDY/+vkg2IEjIqEkXlU6B/2CP7z tWe5HBC24iJz6xiXEUQFLwkqEhj/6EVWXyX4Xjn99LKLP9EkxZedeq2ZKU4A6+uz117Z 7M+w== X-Received: by 10.181.13.40 with SMTP id ev8mr2134573wid.16.1390917296523; Tue, 28 Jan 2014 05:54:56 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id fb8sm11574023wic.3.2014.01.28.05.54.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 05:54:55 -0800 (PST) Message-ID: <52E7B6AF.3050604@xen.org> Date: Tue, 28 Jan 2014 13:54:55 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.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> In-Reply-To: <52DCE9FA.6010400@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: 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 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 get = into GSoC 2014 will be relatively slim. 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 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_Projects urgently = > (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